Changes between Version 91 and Version 92 of GAPI_AM_API_DRAFT


Ignore:
Timestamp:
10/26/13 13:10:48 (8 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API_DRAFT

    v91 v92  
    467467Note that this would be a new option that AMs are not required to honor - making things backwards compatible.
    468468
     469=== Comments ===
     470Nick and Leigh provided some feedback:
     471 - Maybe there should be different proposals for use with AM API v2 and with v3+, to let v3+ AMs take advantage of the sliver expiration already being reported.
     472 - Maybe we should not try to convey AM local policy in the return from `Renew`, but instead include that in `GetVersion` or the Ad RSpec ('before' you try to reserve or renew the resources).
     473
     474To accommodate these, we could modify the proposal's specification of the `output` field as follows:
     475 - For AM API v2 aggregates, the `output` slot of the AM API triple should be the new sliver expiration time - either the time requested, or the 'as long as possible' time. This expiration time should be a standard [wiki:GAPI_AM_API_V3/CommonConcepts#datetimedatatype GENI AM API datetime] complying with RFC 3339.
     476
     477Note that this string allows APIv2 AMs to report the new expiration time since that cannot be reliably known otherwise.
     478
    469479== Older Proposals ==
    470480Older proposals, withdrawn, superseded, or postponed: