Changes between Version 11 and Version 12 of GENIResources


Ignore:
Timestamp:
02/17/15 10:48:51 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIResources

    v11 v12  
    77== Slices ==
    88
    9 In GENI, aggregates that supply compute resources generally make available both virtual and bare metal nodes (check the wiki:GeniAggregate page for details that vary for some aggregates).  You may request any of these resources as part of a slice, which is a container for all your requested resources.  Each slice has an expiration date associated with it. When the slice expires, all your resources are released.  The slice expiration defines to the amount of time your resources are allocated to you. Note, that the slice expiration is an overall expiration, but does not necessarily reflect the duration of your reservation at each aggregate.  If you want to know when your slice expires, you can use the omni command as follows:
     9In GENI, aggregates that supply compute resources generally make available both virtual and bare metal nodes (check the [wiki:GeniAggregate GENI Aggregates] page for details that vary for some aggregates).  You may request any of these resources as part of a slice, which is a container for all your requested resources.  Each slice has an expiration date associated with it. When the slice expires, all your resources are released.  The slice expiration defines to the amount of time your resources are allocated to you. Note, that the slice expiration is an overall expiration, but does not necessarily reflect the duration of your reservation at each aggregate.  If you want to know when your slice expires, you can use the omni command as follows:
    1010{{{
    1111$ omni print_slice_expiration my-slice-name