Changes between Version 71 and Version 72 of GAPI_AM_API_DRAFT


Ignore:
Timestamp:
09/20/12 12:45:34 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API_DRAFT

    v71 v72  
    5959=== Change Set N1: Add `geni_am_code_version` ===
    6060Aggregates use varying ways to identify the software version their AM uses. PlanetLab and ProtoGENI use `code_tag`, Orca uses `orca_version`, and FOAM
    61 uses `foam_version`. Automatically identifying software versions is important for monitoring and GENI operations.
     61uses `foam_version`. Automatically identifying software versions is important for monitoring and GENI operations. Aggregates are therefore strongly encouraged to advertise their current software revision using this standard field, though for security reasons some aggregates may choose not to do so.
    6262
    6363This change set proposes adding `geni_am_code_version` to the return from `GetVersion`.
    64  * The field is required.
     64 * The field is optional.
    6565 * The value is a string.
    6666 * Legal characters are: alphanumeric, space, `-` (hyphen), `.`, `:` (colon), `#`, `_` (underscore), `+`, `(`, `)`
     
    103103
    104104== Change Set O: Refine character restrictions ==
     105
    105106=== Change Set O1: Allow other characters in sliver names ===
    106107Currently we heavily constrain legal characters in the 'name' portion of sliver URNs. See GeniApiIdentifiers. This is awkward. In particular characters like periods, and underscores are not allowed, but are very useful as separators.
     
    112113
    113114=== Change Set O2: Explicitly define legal characters in some strings ===
    114 Various fields in the AM API specification are defined only as strings, without explicit limits on legal characters. This makes it awkward to pass these values to and from scripts. In particular, many fields should only be alphanumeric, plus some limited number of separator characters.
     115Various fields in the AM API specification are defined only as strings, without explicit limits on legal characters. This makes it awkward to pass these values to and from scripts. In particular, many fields should only be alphanumeric, plus some limited number of separator characters.
     116
     117Note that in general, where this API says 'alphanumeric' or explicitly identifies `a-zA-Z`, we would ''like'' to expand this to non-ASCII letters, to support internationalization - making these into unicode strings. Therefore, aggregates are encouraged to support non-ASCII letters as input. However, this change set does not require that aggregates support non-ASCII inputs, and aggregates should not require clients to accept non-ASCII results where the API does not explicitly require it.
    115118
    116119This change set proposes constraining several options/return values that are currently defined only as 'string'.
     
    127130     May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphanumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`
    128131
    129  5. From `getversion` and the `credentials` argument, the credential `geni_version`:
    130      May use only alphanumeric characters plus hyphen, underscore, period, or colon; alphanumeric only in first character. `'^[a-zA-Z0-9][a-zA-Z0-9-_\.:]*$'`
    131 
    132  6. From `getversion`, `geni_allocate`: alphanumeric
    133 
    134  7. From the return of multiple methods, `geni_allocation_status` and `geni_operational_status`: alphanumeric
     132 5. From the return of multiple methods, `geni_operational_status`: alphanumeric
    135133
    136134== Older Proposals ==