e4bc036531
From original flag commit message: [1] "While executing the test_get_object_after_expiry_time test from the ObjectExpiryTest, I experienced intermittent test failures. On further investigation, I discovered that this test has a hard coded "sleep for safety" step. While this value is sufficient for test environments, there is higher latency and processing time in a cloud under load. I've filed a Tempest issue (https://bugs.launchpad.net/tempest/+bug/1452915) that offers more reliable solutions to this problem, which I would be more than glad to implement. However, I can very rarely get this test to pass as is, as I suspect others may be having as well. I'd ask to flag this test while this Tempest issue is being worked through." This bug has been fixed, and the flag should be removed[2]. [1] https://review.openstack.org/#/c/181164/ [2] https://review.openstack.org/#/c/192111 Change-Id: Ia0a8fbea97d8d0dea1f31ecb1b4718eb288f41df
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