Refactor the logic around use of floating ips in node groups and clusters

Registered by Trevor McKay

Currently, there is a boolean in the configuration file "use_floating_ips" that means multiple things at the same time:

1) All instances must have a floating ip
2) Every node group therefore must supply a floating ip pool when using neutron, and in the nova case nova must be configured to auto-assign floating ips
3) Sahara must use the floating ip for management
4) These requirements are in force for every user, every node group, every cluster!

This logic should be broken apart. As we move toward a world where virtual and baremetal clusters (and even node groups) co-exist, we should have more flexibility in handling floating ips.

When using neutron, individual node gropus should be able to declare a floating ip pool or not. If use_floating_ips is set to True, then Sahara should use the floating ip for management of an instance *if it exists* but not require it.

Blueprint information

Status:
Complete
Approver:
Vitalii Gridnev
Priority:
High
Drafter:
Trevor McKay
Direction:
Approved
Assignee:
Telles Mota Vidal Nóbrega
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Vitalii Gridnev
Completed by
Vitalii Gridnev

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/refactor-use-floating-ip,n,z

Addressed by: https://review.openstack.org/336593
    Refactor the logic around use of floating ips in node groups and clusters

Addressed by: https://review.openstack.org/336597
    Refactor the logic around use of floating ips

Addressed by: https://review.openstack.org/362328
    Updating DOC on floating IPs change

Addressed by: https://review.openstack.org/479837
    Allow proxy_command to optionally use internal IP

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.