Data and documentation maintained by the Interop Working Group
Go to file
Mark T. Voelker 1bdc541f2d Flag test that makes assumption about image creation
...in 2015.05.  Original commit message [1]:
"The Images v2 API ListImages test creates images to appear in the image
list, using the Glance image-create call to do this.  There is, however,
an alternative route to image creation in the Images v2 API, namely, to
use an import task.  A cloud provider may wish to restrict the standard
image-create to admin use only, for example, and restrict regular end
users to use of the import task (which allows an opportunity to perform
validation or security scanning on the image data before creating an
image in Glance).  It is also reasonable for a provider not to allow
any upload of external images into a cloud and instead only allow image
creation via the Nova image-create server action.  The key point is
that given that the ListImages test is supposed to test that the image
list functionality is present and working correctly, the test should be
agnostic as to how the images got into Glance in the first place.  The
test should be flagged until it can be modified to take into account the
various legitimate restrictions that providers may wish to place on how
images are introduced into their OpenStack clouds.

This is also reported as tempest bug:

  https://bugs.launchpad.net/tempest/+bug/1453265 "

The Tempest folks have rejected the bug, but a larger discussion on
the defcore-committee ML [2] has ultimately indicated that there's simply
not an interoperable solution today.  The discussion will hopefully
lead to a more interoperable future, but we're not there yet.  Thus,
we should carry this flag forward to 2015.05.

[1] https://review.openstack.org/#/c/181280/
[2]
http://lists.openstack.org/pipermail/defcore-committee/2015-June/000823.html

Change-Id: If2c6528af24f19881dd30106437bd4253dcc1a1a
2015-06-26 13:07:05 -04:00
2015.03 Added file of required tests to pass to testr 2015-03-25 10:48:39 -04:00
2015.04 Merge "Put the proper URL for the refstack-client repo" 2015-05-12 21:54:55 +00:00
doc/source Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00
drafts Complete Havana capabilities as passed by the Board in July 2014 2014-08-23 08:19:41 -05:00
js Add GET test results and add report page output 2015-01-20 13:54:38 -08:00
legacy Initial draft of 2015.03 guideline 2015-03-13 09:21:12 -07:00
tools Fixing generator to output doc8 compliant rst 2015-06-08 10:26:19 -05:00
.gitignore Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00
.gitreview Initial draft of 2015.03 guideline 2015-03-13 09:21:12 -07:00
2015.03.json Flag test_get_console_output 2015-04-30 16:43:51 -04:00
2015.03.rst Fixing generator to output doc8 compliant rst 2015-06-08 10:26:19 -05:00
2015.04.json Merge "Flagging missed stop test" 2015-05-12 21:49:53 +00:00
2015.04.rst Fixing generator to output doc8 compliant rst 2015-06-08 10:26:19 -05:00
2015.05.json Flag test that makes assumption about image creation 2015-06-26 13:07:05 -04:00
2015.05.rst Fixing generator to output doc8 compliant rst 2015-06-08 10:26:19 -05:00
2015.next.json Flag compute resize tests 2015-06-09 16:19:27 -07:00
flagged_list Flag compute resize tests 2015-06-09 16:19:27 -07:00
HACKING.rst Re-introduce test removal clause 2015-06-12 08:40:26 -04:00
README.rst Update tox.ini to test all rst, fix tox errors 2015-06-08 10:36:37 -05:00
setup.cfg Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00
setup.py Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00
test-requirements.txt Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00
tox.ini Moving documentation over to sphinx build process 2015-06-11 12:06:53 -05:00

Understanding the DefCore Guidelines

This repository contains DefCore committee managed files that provide guidance for the OpenStack community.

NOTE: Changes to file requires approval of the DefCore committee chair(s).

DefCore Process Documentation

The /process directory contains details about the DefCore process.

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

Core Definition

process/CoreDefinition.rst

Process Goverance

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

Designated Sections

process/DesignatedSections.rst

Core Criteria

process/CoreCriteria.rst

DefCore Governance

process/GovernanceProcess.rst

Platform and Components

process/PlatformCap.rst

DefCore Cycles

process/ProcessCycles.rst

Terminology

process/Lexicon.rst