Feature #388
Add new Slice Manager AM to allow slice creation/deletion and resource association to slice
| Status: | New | Start date: | 06/09/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 25/10/2010 | |
| Assignee: | Jolyon White | % Done: | 100% |
|
| Category: | OMF Software | |||
| Target version: | OMF 5.3.GEC9 |
Description
Features for GEC9 Demos are described on this page.
Detailed description of this feature is available of this page.
The following new Slice Manager AM is required:
- Slice Manager AM will accept the following requests and perform the following tasks for now:
- Create_Slice:
- Inputs: "slice name" and "PubSub server hosting the slice"
- Tasks: create the pubsub groups
OMF/sliceXYZandOMF/sliceXYZ/resourceson the given PubSub server
- Associate_Resource_to_Slice:
- Inputs: "slice name" and "resource list" and "PubSub server hosting the slice"
- Tasks: create the PubSub group
OMF/sliceXYZ/resources/resourceXfor each resource in the list, and send a request to the AM services responsible for the resources in the list to associate with the sliceXYZ on the given PubSub server - Note: in PlanetLab/ProtoGENI, a RSPEC (Resource Specification) is used instead of the "resource name"
- the RSPEC allows the definition of a list of resources & some initial configuration parameters for these resources
- our initial implementation will simply use "resource list", however it should be developed so that replacing this by an RSPEC-like form would require minimal changes
- Delete_Slice:
- Inputs: "slice name" and "PubSub server hosting the slice"
- Tasks: request all the AMs subscribed to this slice to leave it (i.e. send a broadcast "Deassociate_from_Slice" to
OMF/sliceXYZ/resources, and delete the pubsub groupsOMF/sliceXYZandOMF/sliceXYZ/resourceson the given PubSub server
- Create_Slice:
- Note: The Slice Manager AM will need to keep records of the current active slices if it ever gets stopped and restarted
- Open question:
- Who creates the PubSub group
/OMF/sliceXYZ/resources/resourceA?- Either the Slice Manager AM (on a Associate_Resource_to_Slice) request or the other AMs (on a Associate_to_Resource_At_Slice)
- if other AMs, then we have a potential issue when deleting the slice's PubSub groups as, only the group creator can delete it, thus we would have to keep track of which AM created the group
- if Slice Manager AM, only this AM has to keep track of which PubSub group it created
- solution: Slice Manager AM?
- Who creates the PubSub group
Related issues
| related to Feature #389: Extend existing AM service to allow subscription to Slice... | New | 06/09/2010 | 25/10/2010 |
History
Updated by Thierry Rakotoarivelo over 1 year ago
- Due date changed from 22/09/2010 to 08/10/2010
After conf-call with Ivan, the OML disconnect/reconnect has now a higher priority. Thus the due date for this feature is pushed for 2 weeks.
Updated by Thierry Rakotoarivelo over 1 year ago
- Due date changed from 08/10/2010 to 25/10/2010
Updated by Jolyon White 10 months ago
- % Done changed from 0 to 100
Now implemented on master branch.