Data and documentation maintained by the Interop Working Group
Go to file
Daryl Walleck e6c014be2a Flag compute stop/start and lock/unlock tests
In Nova, the various server actions can be limited by the
policy.json file deployed with the API. This policy
file provides the vendor with granular control over the actions
that can be performed by users in different roles. This means
that the “admin-ness” of a feature can be determined by
configuration. For example, in Rackspace’s OpenStack
public cloud the stop/start and lock/unlock behaviors are
not available to standard users and reserved for
administrators only. Because of this, it would be impossible
for these tests to run successfully in the scope of a
public user.

These two pairs of operations are only an example. It is
likely that other vendors would have similar constraints,
so for that reason I’m proposing that these tests be flagged.

Change-Id: I26e012b138e4c78d25f1dd57a4f845e82dc1fdb8
2015-05-07 10:51:25 -05:00
2015.03 Added file of required tests to pass to testr 2015-03-25 10:48:39 -04:00
2015.04 Merge "Fix wrong path to setup_env in procedure" 2015-05-06 15:45:26 +00:00
drafts Complete Havana capabilities as passed by the Board in July 2014 2014-08-23 08:19:41 -05:00
images Merge "Move Governance/PlatformCap into gerrit" 2015-04-11 01:30:30 +00: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
process Fix broken image reference 2015-05-07 09:40:44 -04:00
tools Generate RST Guidelines from JSON source 2015-04-10 16:56:01 -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 Generate RST Guidelines from JSON source 2015-04-10 16:56:01 -05:00
2015.04.json Flag compute stop/start and lock/unlock tests 2015-05-07 10:51:25 -05:00
2015.04.rst Update status of 2015.04 guideline to show approved 2015-04-20 22:58:34 -05:00
2015.next.json Flag compute stop/start and lock/unlock tests 2015-05-07 10:51:25 -05:00
README.rst Housekeeping to move Wiki docs to process/ directory 2015-04-14 15:20:47 -05:00
test-requirements.txt Added tox.ini and test-requirements for testing 2015-04-10 09:21:46 -07:00
tox.ini Added tox.ini and test-requirements for testing 2015-04-10 09:21:46 -07: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.

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

JSON Schema

The JSON files have a specific schema to support

{ "id": "2015.03",        # Spec name (date based)
  "source": "http://git.openstack.org/cgit/openstack/defcore/",   # git repo for files
  "schema": "1.2",        # Schema version
  "status": "approved",   # can be draft, review or approved
  "replaces": "2014.07",  # previous spec
  "releases": ["icehouse"], # array of releases, lower case
  "platform": {           # platform components
    "required": ["compute", "object"],  # array
    "advisory": [],       # incoming array
    "depricated": [],     # outgoing array
    "removed": []         # removed array
    },
  "components": {         # components detail
    "compute": {          # component name
      "required": [       # required array
        "compute-auth"],
      "advisory": [       # incoming array
        "compute-servers-metadata"],
      "deprecated": [],   # outgoing array
      "removed": [        # removed array
        "volume"]
      },
    },
  "criteria" : {          # explains achievements
      "atomic" : { "Description" : "blah blah blah",
      "name" : "Atomic", 
      "weight": 8
      },
  "capabilities": {       # capabilities listed in components
    "example-cap" :       # capability
      { "achievements" :  # array of criteria met
        [ "deployed",
          "future",
          "complete"],
      "admin" : false,    # is admin API
      "status" : "required",  # de-normalized from components
      "description" : "Helpful Description",
      "flagged" : [  ],   # flagged tests array
      "name" : "Friendly Short Name",
      "tests" :           # list of tests (please use UUIDs)
        [ "tempest.api.project.file.class.test_name" ]
    },