Changes between Version 55 and Version 56 of GAPI_AM_API_V3/CommonConcepts


Ignore:
Timestamp:
08/15/14 10:34:36 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API_V3/CommonConcepts

    v55 v56  
    223223 - `geni_restart`: This action results in the sliver becoming `geni_ready` eventually. The operation may fail (move to `geni_failed`), or move through some number of transition states. During this operation, the resource may or may not remain accessible. Dynamic state associated with this resource may be lost by performing this operation. For example, re-booting a VM.
    224224 - `geni_stop`: This action results in the sliver becoming `geni_notready` eventually. The operation may fail (move to `geni_failed`), or move through some number of transition states. For example, powering down a VM.
     225 * `geni_update_users`: This action changes the users and SSH keys installed on existing slivers that are `geni_ready`.
     226  * This action requires the [#geni_users geni_users option] specifying in JSON the users and keys that should be installed.
     227  * This struct may add new users or change installed SSH keys, but will not remove existing users. Omitting an existing user means apply no changes.
     228  * While this change is in process (may be several minutes), the slivers will be in the `geni_updating_users` state. Therefore, other actions that require the `geni_ready` state will be illegal and will result in an error code of `REFUSED`.
     229  * Full details and semantics on this action are defined on the [wiki:GAPI_AM_API_DRAFT/Adopted#ChangeSetQ:Supportchangingusersandkeysonexistingcomputeslivers AM API Adopted Changes page].
     230 * `geni_updating_users_cancel`: Cancel any pending `geni_update_users` action; callable on a sliver in the `geni_updating_users` state.
     231  * Full details and semantics on this action are defined on the [wiki:GAPI_AM_API_DRAFT/Adopted#ChangeSetQ:Supportchangingusersandkeysonexistingcomputeslivers AM API Adopted Changes page].
     232 
     233Other operational actions that have not been fully adopted or implemented:
     234 * `geni_sharelan` and `geni_unsharelan`: These actions allow you to change a reserved LAN at an aggregate into a shared LAN that other slices can connect to, or to change such a LAN back to a private LAN. Required options:
     235  * `geni_sharelan_lanname`: The `client_id` of the existing reserved LAN.
     236  * `geni_sharelan_token`: Name that the new shared LAN will be known by.
     237  * Note:
     238   * The LAN to share cannot be between 2 VMs on the same physical host - i.e. Use at least 2 VMs with different `component_id`s.
     239   * The original LAN will still expire or can be deleted as usual, causing the shared LAN to go away as well.
     240   * Support is very limited.
     241   * For usage instructions, see http://groups.geni.net/geni/wiki/HowTo/ShareALan
     242 * `geni_console_url`: Get a URL for access to the console of a resource.
     243  * You must supply a single sliver URN identifying the resource whose console is desired.
     244  * This command is only known to work at InstaGENI/ProtoGENI Xen VMs and some bare metal machines at Emulab.
     245  * This URL expires within a few minutes.
    225246
    226247=== Return Struct ===