Changes between Version 103 and Version 104 of GAPI_AM_API_DRAFT


Ignore:
Timestamp:
02/03/14 16:34:10 (6 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API_DRAFT

    v103 v104  
    456456
    457457Note that as described [wiki:GAPI_AM_API_V3/CommonConcepts#SliverOperationalActions here], aggregates supporting this action and operational state will advertise this fact in their advertisement RSpec.
     458
     459Sample JSON value for the `geni_users` option to be supplied:
     460{{{
     461{
     462 "geni_users": [
     463  {
     464   "urn": "urn:publicid:IDN+ch.geni.net+user+jdoe",
     465   "keys": ["ssh-rsa jdoegoodkey"]
     466  },
     467  {
     468   "urn": "urn:publicid:IDN+ch.geni.net+user+jsmith",
     469   "keys": ["somekey", "someotherkey"]
     470  }
     471 ]
     472}
     473}}}
    458474
    4594752. `geni_updating_users_cancel`: This action requires no options. It cancels any pending `geni_update_users` action on the named slivers, returning those slivers to the `geni_ready` operational state. This action is only legal on slivers in the `geni_updating_users` operational state. This action may be used on slivers which fail to complete the `geni_update_users` action. After a successful `geni_updating_users_cancel`, the state of users and keys on the sliver(s) is not defined; some may have the same users/keys as they had prior to beginning the `geni_update_users` action, and others may have already updated to the new set of users and keys.