d8fb682a2b
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
1.4 KiB
Platform Capabilities
Platform and Program Capabilities
The following was approved by the OpenStack Board.Extend the Interop WG principles to allow for multiple levels: programs and platforms. Programs represent subsections of the overall platform. In some cases, it is acceptable for a program identified without being included in the platform. New programs are added at Foundation recommendation via board approval. Programs are added to the platform via board approval.
The initial programs will be Compute & Object. The Platform will require the Compute program, Object program and additional capabilities.
Havana Approved: The Compute Program will consist of the following capabilities:
- compute-servers
- compute-volume
- compute-quotas
- compute-flavors
- compute-auth
- compute-keypairs
- compute-servers-metadata
- compute-floating-ips
- compute-images
- compute-instance-actions
- compute-security-groups
Havana Approved: The Object Program will consist of the following capabilities:
- objectstore-object,
- objectstore-container
Havana Approved:: The Platform will consist of all the capabilities in the Compute and Object programs and the following capabilities:
- images-v1
- volume
- volume-snapshots
Platform and Components Illustration
