Use floating ip in VM runcommand scenario

Registered by bsemp on 2014-04-17

Currently the VM runcommand scenario use the fixed ip to ssh connect to the instance.
This could only works if fixed ip range is directly accessible with is the case in very limited deployments.

This blueprint proposes to support attachment of a floating ip to the instance allowing connection in most deployments.

Floating ips management requires to modify current scenario parameters:
    - Currently the network used to connect to the instance is referred as "network".
    - The concept of fixed and floating network should be introduced: parameter "network" will be renamed in "fixed_network" and parameter "floating_network" will be added.
    - To maintain compatibility with current implementation, a new parameter "use_floatingip" will be added. This parameter will be defaulted to "true" as the use of floating ips is generally preferred.

def boot_runcommand_delete(self, image_id, flavor_id,
         script, interpreter,
         fixed_network='private',
         floating_network='public',
         username='ubuntu', ip_version=4,
         port=22, use_floatingip=True, **kwargs):

Blueprint information

Status:
Complete
Approver:
Boris Pavlovic
Priority:
Medium
Drafter:
bsemp
Direction:
Approved
Assignee:
bsemp
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
bsemp on 2014-04-23
Completed by
bsemp on 2014-07-15

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/benchmark-scenarios-vm-floating-ip,n,z

Addressed by: https://review.openstack.org/89555
    Add nova floating ip management in VM scenario

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.