tenant_network_types should be configurable

Bug #1399684 reported by Bjoern
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Expired
Low
Unassigned
Kilo
Expired
Low
Unassigned
Trunk
Expired
Low
Unassigned

Bug Description

Currently tenant_network_types is dynamically set from the available network type group in ansible.
We actually prefer to tie down one network type instead of accidentally creating vxlans over vlans as example

See code:

rpc_deployment/roles/neutron_common/templates/plugins/ml2/ml2_conf.ini
tenant_network_types = {{ network_types|join(',') }}

Revision history for this message
Kevin Carter (kevin-carter) wrote :

Would this be something that you'd want to be able to have an optional override for and have it dynamically created if the override was not set, or should do you think it should be a required option that must be set by the user for the deployment?

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
milestone: none → next
Revision history for this message
Bjoern (bjoern-t) wrote :

I think we should set it to vlan per default and only override at all if no default is set

Changed in openstack-ansible:
milestone: next → none
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Setting back to a new state in order to cover it in the next triage discussion.

Changed in openstack-ansible:
status: Confirmed → New
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

I think the order in tenant_network_types depends on the order in which you define networks in openstack_user_config.yml.

Changed in openstack-ansible:
status: New → Confirmed
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

Only the first value in tenant_network_types matters because it defines the default project network type for both administrative and regular (non-privileged) projects. Without changes to the default policy, regular projects can only create this type of network.

Revision history for this message
Nolan Brubaker (nolan-brubaker) wrote :

Is this still relevant in Kilo? Could this be defined in a consuming project rather than in openstack-ansible?

Revision history for this message
Bjoern (bjoern-t) wrote :

I don't know what a consuming project means but I guess it refers to rpc-openstack. This is still an issue under Kilo but we might be able to install standard overrides whith reveres the order or does not configure vxlan by default

Revision history for this message
Kevin Carter (kevin-carter) wrote :

Just as a quick aside the variable is generated from data found in the provider_networks array set in the openstack_user_config.yml it is possible however to override this default by setting the following in user_variables.yml

neutron_ml2_conf_ini_overrides:
  ml2:
    tenant_network_types: <SOME-NETWORK-TYPE>

In this way you can control the exact type of networks available via neutron.

Revision history for this message
Major Hayden (rackerhacker) wrote :

Bjoern -- did you still need this bug open? Feel free to re-open if needed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-ansible kilo because there has been no activity for 60 days.]

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-ansible trunk because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.