Fixing a few links as the original ones were returning 404.
The commit fixes .rst syntax issues to make the pages
render "nicer". The commit changes only format of the .rst
code, the content of the pages is not changed at all.
Change-Id: Icf0da2d7d1b42b065639c9105fbc16e1999bf630
Hacking provides valuable standard checks such as imports in
alphabetical order. Having this included in our pep8 check/job
the quality and readability of the code will be improved.
Change-Id: Ieedfcd340e9b700bdead0073bac39a505c8628b5
This mostly fixes print statements and some pep8 issues.
Change-Id: Ie4fb0ac8955759954d882988d698fb4aace61de1
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch adds a new capability for Nova: the "create multiple
servers" API [1], which allows a user to create multiple servers with
a single API call. Although this API is not widely used by tools such
as gophercloud, libcloud, or Terraform, it meets most other criteria
and is not specific to any particular backend.
[1]
https://developer.openstack.org/api-ref/compute/#create-multiple-servers
Change-Id: I5bdbc1504fb088392e55b76c2ce70f19d6aa69c6
The change over to schema 2.0 broke the tabulate scores script,
updated it to handle the new format.
Change-Id: I44726703a2abf41c57451ed17256f7bb4e2d531c
NOTE: This is just a precursory pass, still need to reach out to
PTL and check for new/removed capabilities and client updates
Change-Id: I7fa0e5ba84c32f919aa8865704b729705e594432
This adds a high-level assessment of the remaining candidates for the
NFV vertical. This assessments primarily aim at triggering discussions
and shall not be regarded a final scoring.
Change-Id: I206989d01b26f4c95ca5df6b4560c658a9db5ccc
Scoring, notes and guideline updates for the networking-bgpvpn project.
From a scoring perspective, this looks fine for inclusion in the NFV
vertical. One of the capabilities is an admin-only API but this
criterion might be relaxed for the NFV vertical. The test coverage needs
to be discussed and potentially extended.
Change-Id: I415bcd3d5bc66708c12af6c8988d1f4f101c51e1
This is the first attempt at scoring the Neutron trunk port
feature as initial capability for the new NFV vertical program.
Moreover, a first version of a NFV guideline based on the 2.0
schema definition is included.
Since the NFV program is a vertical, I scored all 12 criteria -
in contrast to the add-on programs which are limited to 9
criteria.
I scored the 'widely deployed' criterion' with 1 in the context
of NFV-focused deployments. Since those are mostly private
cloud deployments, it is hard to determine actual availability.
Change-Id: I496ff4abb9c2510f0676f2f849414be785fb162b
first pass at cinder scoring for the new guideline. It includes
the addition of a new volumes-v3 snapshot capability, which i'd
like to discuss a little in order to sanity check a few of the
scoring decisions.
Change-Id: I29fdb7d293bae88d1c6d323ff27a6ebf34f520dd
Just a quick first pass at this, looking forward to getting a bit
of input. Only a few existing capabilities needed updates, but
there are two new capabilities, objectstore-slo-support and
objectstore-dlo-support. Obviously, these may require some
discussion, and I will need to write new tests for the dlo
capability.
Change-Id: Ie658f499a21e4f0bb92d7aeba1387f0497752989
The Additional Properties Wavier on Nova responses was intended
to be cancelled in the 2017.01 guideline. This required official
removal from the board approved guideline. This patch removes the
Additional Properties Waiver from next.json, to be approved for
the 2018.01 guideline and officially cancelling the waiver.
Change-Id: Ia65eb241d5e82ac4dd91c3e3b41f5b69dbdb8a43
There are a few loose ends on this one, to tie up, but
this is my first draft. There have not been a great number
of changes to Glance in the last cycle. The greatest change
that may be in the works is the finalization of the images-v2-import
capability. I will be checking up on whether or not that has, as of
yet, been finalized.
Change-Id: Ie318ac37833dd4836fd08b27e7ec738694a399db
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#id2https://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
Scoring Keystone for guideline 2018.01
Changes: Update notes on the working materials folder.
Items To Be Discussed:
identity-v3-list-projects capability was marked required 2017.09.
But the only TC available was flagged since it needs 2 users.
Q. Should we move the capability back to advisory until TC is fixed?
or until other suitable TCs are added?
Change-Id: Ic84cbe834474e579345e22256f2e956ad2b4b897
Note: waiting for additional comments from PTL.
Add keystone get catalog capability in next.json. Non-admin test case was
added in tempest
Change-Id: Ie28ca460cf4a11a9431dfa01e216396f5787acc3
Depends-On: Ia745dff050f35cc5a3fc3744d58c6fe1e875e56f
Add keystone validate token capability into next.json/ 2017.08.
non-admin test case is now available in tempest. Further
details on commit Ice1a241445d532ee2c4b1ad8d2c4c896d755798d
TC call GET on /v3/auth/tokens API.
Depends-On: Ice1a241445d532ee2c4b1ad8d2c4c896d755798d
Change-Id: I062e6148e90ae84d34f2df4577eb581ce76d021b
This patch adds Neutron scoring for the 2017.08 Guideline. The only
major change is moving subnet pools from advisory to required status.
Change-Id: I9149d7409f47f212a22b2a7df5436ca1bce173c3
Added availability zones, and flavor listing capabilities.
Restored matrix with all capabilities and updated scoring.
Change-Id: I2bb062e71566e424ae9f5fc40b6c3bd67309f9b6
At the Board of Directors meeting on April 24, 2016 the Board of
Directors indicated that as DefCore has evolved it's focus on
interoperability and it's working structure, it's name may be a source
of some confusion to those outside of the community or who are new to
the community. The Board made an informal request that the DefCore
Committee consider changing it's name to more clearly reflect it's focus
and structure.
This patch is the first step in that process. It updates references
in various documents to change the name "DefCore Committee" to
"Interop Working Group" as agreed at the summer 2016 DefCore Committee
Sprint [1].
It should be noted that this patch should be considered a work in
progress to generate discussion until the new name is approved by
the DefCore Committee and the Board of Directors. Should we elect
to go forward with the new name, some other actions will also need
to be taken, including but not limited to:
1. We will need to consider updating references on the OpenStack wiki.
2. We will need to consider updating the name of our IRC channel,
mailing list, Launchpad project, and git repository. Most of these
changes will need to be carefully coordinated with the OpenStack
Infrastructure team.
3. We will need to take into account external resources that point to
DefCore artifacts, such as Foundation-maintained websites (such as:
http://www.openstack.org/interop ).
4. We will need to coordinate with RefStack to minimize impact.
5. We will need to clearly communicate the name change to the rest of the
community.
Note also that I've intentionally left many historical documents that
have been superceded (such as the 2015A process docs, Guidelines that
are no longer used, etc) in tact. There seemed little value in
spending time on them and cluttering the patch with them since they're
now obsolete.
[1] https://etherpad.openstack.org/p/DefCoreSummer2016Sprint
Change-Id: I79d337c193e75c54d49f1d847468f6347e2ef2b3
This change constitutes a first pass at scoring Nova capabilities
for the 2017.01 Guideline. It adds three new capabilities: listing
flavors, availability zone operations, and suspend/resume. There
are no new designated sections in this update.
Change-Id: I9970c9789ca972b4d2cc53e57dcee97b87525e48
Martin Kopec