Changes between Version 103 and Version 104 of GAPI_AM_API_DRAFT

Timestamp:

02/03/14 16:34:10 (10 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_DRAFT

@@ -456 +456 @@
 
 Note 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.
+
+Sample JSON value for the `geni_users` option to be supplied:
+{{{
+{
+ "geni_users": [
+  {
+   "urn": "urn:publicid:IDN+ch.geni.net+user+jdoe",
+   "keys": ["ssh-rsa jdoegoodkey"]
+  },
+  {
+   "urn": "urn:publicid:IDN+ch.geni.net+user+jsmith",
+   "keys": ["somekey", "someotherkey"]
+  }
+ ]
+}
+}}}
 
 2. `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.