Changes between Version 62 and Version 63 of GAPI_AM_API_DRAFT
- Timestamp:
- 09/12/12 14:54:02 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GAPI_AM_API_DRAFT
v62 v63 58 58 59 59 === Change Set N1: Add `geni_am_version` === 60 Aggregates use varying ways to identify the software version their AM uses. SFA and PGuse `code_tag`, Orca uses `orca_version`, and FOAM60 Aggregates use varying ways to identify the software version their AM uses. PlanetLab and ProtoGENI use `code_tag`, Orca uses `orca_version`, and FOAM 61 61 uses `foam_version`. Automatically identifying software versions is important for monitoring and GENI operations. 62 62 … … 75 75 * The value is a string. 76 76 * Legal characters: alphanumeric 77 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. ( E.G. one of `orca`, `foam`, `protogeni`, `sfa`.)77 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`. More GENI AM types may be added in the future.) 78 78 79 79 === Change Set N3: Use consistent types and prefixes === … … 92 92 * The value is a string. 93 93 * Legal characters: alphanumeric 94 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. ( E.G. one of `orca`, `foam`, `protogeni`, `sfa`.)94 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`. More GENI AM types may be added in the future.) 95 95 96 96 Aggregate specific options and return attributes should be named with a prefix denoting the aggregate type. It should be the same as the `am_type` and `geni_am_type` for this aggregate. Therefore, character restrictions are: 97 97 * The value is a string. 98 98 * Legal characters: alphanumeric 99 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. ( E.G. one of `orca`, `foam`, `protogeni`, `sfa`.)99 * Values should be one of the defined geni AM types if applicable, as defined by the AM API [http://groups.geni.net/wiki/attachment/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml geni-am-types.xml]. (As of this proposal, one of `orca`, `foam`, `protogeni`, `sfa`. More GENI AM types may be added in the future.) 100 100 101 101 == Change Set O: Refine character restrictions == … … 106 106 107 107 '''Slice''': 108 * Slice names are <=19 characters, only alphanumeric plus hyphen, underscore, period, or colon (alphanumeric only in first character): '^[a-zA-Z0-9][-\._:a-zA-Z0-9]\{0,18\}$'108 * Slice names are <=19 characters, only alphanumeric plus hyphen, underscore, period, or colon (alphanumeric only in first character): `'^[a-zA-Z0-9][-\._:a-zA-Z0-9]\{0,18\}$'` 109 109 110 110 '''Sliver''': … … 117 117 118 118 1. From `getversion` and `listresources` and `describe`, the RSpec `type`: 119 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`119 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'` 120 120 121 121 2. From `getversion` and `listresources` and `describe`, the RSpec `version`: 122 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`122 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'` 123 123 124 124 3. From `getversion`, the RSpec `schema`, and `namespace`: Any character valid in a URL (see e.g. http://www.w3.org/Addressing/URL/url-spec.txt) 125 125 126 126 4. From `getversion` and the `credentials` argument, the credential `geni_type`: 127 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`127 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'` 128 128 129 129 5. From `getversion` and the `credentials argument, the credential `geni_version`: 130 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`130 May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphaumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'` 131 131 132 132 6. From `getversion`, `geni_allocate`: alphanumeric