Changes between Version 36 and Version 37 of GAPI_AM_API_V3/CommonConcepts


Ignore:
Timestamp:
08/22/12 16:31:38 (12 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GAPI_AM_API_V3/CommonConcepts

    v36 v37  
    207207AMs 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.
    208208
    209 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].
     209The 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].
    210210
    211211Tools must use the operational states and actions advertisement to determine what operational actions to offer to experimenters, and what actions to perform for the experimenter. Tools may choose to offer actions which the tool itself does not understand, relying on the experimenter to understand the meaning of the new action.