Changes between Version 21 and Version 22 of GAPI_AM_API_V3/CommonConcepts
- Timestamp:
- 05/31/12 15:57:05 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GAPI_AM_API_V3/CommonConcepts
v21 v22 165 165 AMs may have their own operational states/state-machine internally. AMs are however required to advertise such states and actions that experimenters may see or use, by using an advertisement RSpec extension (if an AM does not advertise operational states, then tools can not know whether any actions are available). Operational states which the experimenter never sees, need not be advertised. Operational states and actions are generally by resource type. The standard RSpec extension attaches such definitions to the `sliver_type` element of RSpecs. 166 166 167 The standard advertisement RSpec extension for advertising operational states and actions can be found [http://www. protogeni.net/resources/rspec/ext/opstate/1 here], with an example with comments [https://www.protogeni.net/trac/protogeni/wiki/RspecAdOpState here].167 The standard advertisement RSpec extension for advertising operational states and actions can be found [http://www.geni.net/resources/rspec/ext/opstate/1 here], with an example with comments [https://www.protogeni.net/trac/protogeni/wiki/RspecAdOpState here] (it is version-controlled in the standard GENI RSpecs git repository as well). 168 168 169 169 States should be defined in terms of