Services with pre-created port-tuples

Registered by Rudra Rugge on 2015-10-12

Launch vm services with pre-created ports. Currently when a service instance is created for a VM based service - service monitor creates one or more VM objects and then creates ports for each of the VM objects. The VM object acts as the placeholder for binding service-instances to the ports. In addition VM object also acts as a placeholder for the instance id in case of ECMP.

The VM object being just a placeholder doesn't add much value other than binding information between service instance object and port objects. Hence the plan is to remove/ignore the VM object and link the service instance directly to the port objects. This decoupling simplifies the implementation and in addition provides advantage for integration with heat templates.

With this change the user can create ports and pass the pre-created port information when creating a service instance. This can also be leveraged in HEAT stacks. On binding of ports to a service instance service monitor can now trigger launching of a VM with the relevant information. New schema object called port-tuple will be added to contain all the ports of a VM.

Sample workflow:
1. User creates a port-tuple
2. User creates ports and marks them left/right/mgmt etc and adds them to a port-tuple.
3. User links the port-tuple to a service instance
4. User launches the virtual-machine using the ports in a port-tuple

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Rudra Rugge
Direction:
Needs approval
Assignee:
Rudra Rugge
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.