No dialogue to configure networks when Network Isolation is selected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiri Tomasek |
Bug Description
There is an option in the UI to enable Network Isolation. In order to utilize Network Isolation, specific configuration must exist for each of the following networks, according to http://
IPMI* (IPMI System controller, iLO, DRAC)
Provisioning* (Undercloud control plane for deployment and management)
Internal API (OpenStack internal API, RPC, and DB)
Tenant (Tenant tunneling network for GRE/VXLAN networks)
Storage (Access to storage resources from Compute and Controller nodes)
Storage Management (Replication, Ceph back-end services)
External (Public OpenStack APIs, Horzizon dashboard, optionally floating IPs)
Floating IP (Optional, can be combined with External)
IPMI networks are managed outside of the Undercloud or Overcloud, and as such may not require specific network configurations other than those used for reference in conjunction with node provisioning in the UI.
The Provisioning network, which is defined in undercloud.conf, generally gets established on the default VLAN and is referenced by undercloud.conf's 'local_interface' parameter, and may not require specific network configurations in the UI.
The External network is utilized for Public API, and optionally may be used for Floating IPs, but separate networks may also be used, so the assumption needs to be that these may be different networks.
For the other networks, reasonable networks are configured in the default supporting templates for the following networks:
Internal API (172.16.2.0/24)
Tenant (172.16.0.0/24)
Storage (172.16.1.0/24)
Storage Management (172.16.3.0/24)
External (10.0.0.0/24)
It is not safe to assume that these networks will be available for use during a deployment. A configuration dialogue must exist to allow the user to configure the properties of these networks individually, overriding any defaults. This configuration dialogue should only be available when Network Isolation is enabled, since there is no need for it when Network Isolation is not enabled.
Another common use case of when configuraiton of Network Isolation is only selecting a subset of networks to be isolated. In such a case, this dialogue should also be capable of generating a ServiceNetMap that provides for which subset of networks are in fact isolated, and which networks are combined.
Moving forward, Customizable Networks (https:/
description: | updated |
summary: |
- No dialogue to configure networks when Network Isolation is slsected + No dialogue to configure networks when Network Isolation is selected |
Changed in tripleo: | |
assignee: | nobody → Jiri Tomasek (jtomasek) |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Undecided → High |
status: | In Progress → Fix Released |
milestone: | none → ocata-1 |
Reviewed: https:/ /review. openstack. org/387285 /git.openstack. org/cgit/ openstack/ tripleo- ui/commit/ ?id=fb6cdb3405c 10ca14305adc3e5 98808fc513973a
Committed: https:/
Submitter: Jenkins
Branch: master
commit fb6cdb3405c10ca 14305adc3e59880 8fc513973a
Author: Jiri Tomasek <email address hidden>
Date: Mon Oct 17 11:12:09 2016 +0200
Provide roles network configuration
Partial-Bug: 1626755 d1165d3fcbf497f 5b8a5acb3a5
Change-Id: I37ed7a848d00d2