Changes between Version 106 and Version 107 of GAPI_AM_API_DRAFT
- Timestamp:
- 02/11/14 21:01:33 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GAPI_AM_API_DRAFT
v106 v107 506 506 507 507 == Change Set S: More info from `GetVersion` == 508 `GetVersion` should return an additional `geni_urn` specifying the URN of the Aggregate Manager at this endpoint. 508 `GetVersion` should return an additional field indicate the URN(s) of the Aggregate Manager at this endpoint. This corresponds to the URN IDs of the `component_manager` or `component_manager_id` from the advertisement RSpec produced by this aggregate. 509 510 At many aggregates, this is a single URN. But at some aggregates that proxy for multiple component managers, this may be a list of URNs. 511 512 '''FIXME''': 513 - `geni_urn`? `geni_component_manager_urn`? 514 - Presumably this must be a list? 515 - Do aggregates ever have a single URN identifier? 509 516 510 517 == Change Set T: Long Lived Slices == … … 613 620 614 621 Some general notes: 615 - Disk images are created with snapshots of the disk of an existing compute resource622 - Disk images are typically created with snapshots of the disk of an existing compute resource. At some aggregates this might disrupt the state of the compute resource. 616 623 - Images exist local to an aggregate: They are created, listed and deleted at a particular aggregate 617 624 - Images are identified by a URN. At some aggregates, they are also identifiable by a URL (for purposes of exporting an image to another aggregate) … … 649 656 This function should return quickly, asynchronously snapshotting the disk. While the disk is being snapshotted, do not modify the state of your VM - results will be unpredictable. 650 657 651 Only slivers in the `geni_ready` state may be imaged. While the image is being created, the sliver will be in a new operational state, `geni_imaging`. While the sliver is in this state, no operational actions are permitted . When imaging is complete (successfully or due to error), the operational state transitions back to `geni_ready`.658 Only slivers in the `geni_ready` state may be imaged. While the image is being created, the sliver will be in a new operational state, `geni_imaging`. While the sliver is in this state, no operational actions are permitted, and at some aggregates, the sliver may be inaccessible. Note that at some aggregates, creating an image may disrupt the running and state of the resource. When imaging is complete (successfully or due to error), the operational state transitions back to `geni_ready`. 652 659 653 660 The aggregate will email the user who created the snapshot at the email address found in the user's certificate, providing status and results.