openinfra/interop
Code Issues Proposed changes

Changed extensions to add-ons

Browse Source 
Change-Id: Ieb0769ec0b78cd8c9edee9ef2de3685301a0f80b
This commit is contained in:
Chris Hoge 2017-09-06 10:03:35 -07:00
parent d8eb66d166
commit b3d697fe21
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/schema/2.0.json
View File

@ -119,7 +119,7 @@
} }
} }
}, },
"extensions": { "add-ons": {
"type": "object", "type": "object",
"patternProperties": { "patternProperties": {
"^\\w+$": { "^\\w+$": {

20
doc/source/schema/2.0.rst
View File

@ -95,28 +95,28 @@ source
Optional, a reference to the guideline where the component is Optional, a reference to the guideline where the component is
defined. defined.
extensions add-ons
---------- ----------
A dictionary of all of the Extension objects that are defined in this A dictionary of all of the add-on objects that are defined in this
guideline. Extensions are collections of capabilities that provide guideline. add-ons are collections of capabilities that provide
additional services and functionality on top of an existing platform. additional services and functionality on top of an existing platform.
An example might be orchestration on top of OpenStack Powered An example might be orchestration on top of OpenStack Powered
Platform. In addition to defining what capabilities make up the Platform. In addition to defining what capabilities make up the
extension, components that are required to be present for the program add-on, components that are required to be present for the program
to run may be specified. In this way, implicit compatibility with to run may be specified. In this way, implicit compatibility with
multiple platforms can be established. For example, a DNS extension multiple platforms can be established. For example, a DNS add-on
might require a compute component to work, but not a storage might require a compute component to work, but not a storage
component. This would make that particular extension implicitly component. This would make that particular add-on implicitly
compatible with OpenStack Powered Platform and OpenStack Powered compatible with OpenStack Powered Platform and OpenStack Powered
compute, but not OpenStack Powered Storage. compute, but not OpenStack Powered Storage.
description description
~~~~~~~~~~~ ~~~~~~~~~~~
An optional description of the extension. An optional description of the add-on.
components components
~~~~~~~~~~ ~~~~~~~~~~
A list of all of the components that belong in this extension. Each A list of all of the components that belong in this add-on. Each
component is an object with the following two fields: component is an object with the following two fields:
name name
@ -130,7 +130,7 @@ source
required_platform_components required_platform_components
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A list of all of the components that are required to be present in the A list of all of the components that are required to be present in the
host platform for the extension. Each component is an object with the host platform for the add-on. Each component is an object with the
following two fields: following two fields:
name name
@ -144,7 +144,7 @@ source
optional_platform_components optional_platform_components
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A list of all of the components that, if present in the host platform, A list of all of the components that, if present in the host platform,
is compatible with this extension. Each component is an object with the is compatible with this add-on. Each component is an object with the
following two fields: following two fields:
name name