kolla-ansible

octavia_network_interface naming scheme

Bug #1797755 reported by Eric Miller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Triaged
Low
Unassigned

Bug Description

Just a quick note that the naming scheme for "octavia_network_interface" and "octavia_network_interface_address" is inconsistent with the naming of other interfaces and addresses, such as "cluster_interface", "tunnel_interface", "dns_interface", etc. I would have expected it to be: "octavia_interface" and "octavia_interface_address".

These are in:
etc/kolla/globals.yml
ansible/roles/octavia/templates/octavia.conf.j2
ansible/group_vars/all.yml

Eric

Tags: octavia
Revision history for this message
Dai Dang Van (daikk115) wrote :

Hi Eric,

I have contributed that feature.
At that time, I just thought we had "octavia_network", then we should have "octavia_network_interface" on controller for Octavia to manage amphora instances.

Changed in kolla-ansible:
status: New → Confirmed
Revision history for this message
Radosław Piliszek (yoctozepto) wrote :

oopsie; this is confusing

tags: added: octavia
Changed in kolla-ansible:
status: Confirmed → Won't Fix
status: Won't Fix → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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