Matt Riedemann 23dc48cc02 2018.1 scoring: add compute-keypairs-create-type
This proposes scoring for the 2018.1 guidelines to include
the compute capability to create keypairs with a specified
type.

This microversion is important for Windows guests since it
allows the creation or import of x509 keypairs.

Notes:

- This feature is based on the compute API 2.2 microversion
  and was introduced in the Kilo release:

  https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id2

  https://developer.openstack.org/api-ref/compute/#create-or-import-keypair

- This feature is considered widely deployed since it is
  not configurable or backend-specific.

- It is considered not used by tools given it depends on
  those tools supporting compute API microversions, and it
  is assumed that most tools are still lacking in this area.

- This capability is discoverable since client code can
  determine if the microversion is available on the server
  via version discovery, i.e. compute-list-api-versions.

- While this feature was in the last release, it is not
  considered "required" since microversions are opt-in per
  request by the client.

  NOTE: Since this is the first proposed capability that
  depends on a microversion, it is assumed that the definition
  of what "required" means will need some adjusting to account
  for weighing microversion-based capabilities differently.

- There is an existing Tempest test for this microversion
  with id 89d59d43-f735-441a-abcf-0601727f47b6.

Change-Id: I62554618e38f3f7ca1b508387a1eef190cdcef63
2017-10-10 10:27:48 -04:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2015-03-13 09:21:12 -07:00
2017-06-28 21:57:01 +00:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2017-09-12 09:38:36 -06:00
2017-01-23 21:25:05 -05:00
2017-01-23 21:25:05 -05:00

Understanding the Interoperability Guidelines

This repository contains files managed by the Interop Working Group that provide guidance for the OpenStack community.

NOTE: Changes to file requires approval of the Interop Working Group chair(s).

Interop Working Group Process Documentation

Are you a vendor who wants to get a license to use the OpenStack trademark and logo? Consult OpenStack Interop.

The /doc/source/process directory contains details about the Interop Working Group process.

The /doc/source/schema directory contains details about the JSON schema versions used to express Guidelines.

The /doc/source/guidelines directory contains RST versions of the Interop Guidelines approved by the OpenStack Board of Directors.

Core Definition

doc/source/process/CoreDefinition.rst

Process Goverance

doc/source/process/2015A.rst (please check for latest)

Designated Sections

doc/source/process/DesignatedSections.rst

Core Criteria

doc/source/process/CoreCriteria.rst

Interop WG Governance

doc/source/process/GovernanceProcess.rst

Platform and Components

doc/source/process/PlatformCap.rst

Interop WG Cycles

doc/source/process/ProcessCycles.rst

Terminology

doc/source/process/Lexicon.rst

Description
Data and documentation maintained by the Interop Working Group
Readme 7.3 MiB
Languages
Python 61.3%
Shell 23.3%
JavaScript 10.7%
HTML 4.7%