Actions
Bug #9080
openNetworks cannot be ordered for Openstack Compute Hosts
Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - OpenStack
Target version:
-
Description
When provisioning a new host on an openstack compute resource, it is possible to automatically assign a floating IP.
This will fail, if the first network in the list is not connected to a router with an external gateway.
It is common for multiple networks to be completely private, and therefore, not connected to a router. In this case it would be desirable for foreman to allow users to specify the network that should have the floating IP connected.
Further, in the order networks are attached to instances can be important, as the first network attached to the machine is usually used to fetch user-data and bootstrap the other interfaces. If we could order the network list that would be useful.
No data to display
Actions