Hi,
In the recent kolla meeting [1] we discussed the usability of octavia
in kolla ansible. We had feedback at the Denver summit [2] that this
service is difficult to deploy and requires a number of manual steps.
Certificates are one of the main headaches. It was stated that OSA [3]
may have some useful code we could look into.
I second that Octavia is very painful to install. There is a requirement of a bunch of openstack cloud configurations (flavors/images/etc) that must be handled prior to actually configuring the service which means it's complex to deploy. IMHO it would have been beneficial for some of these items to actually have been rolled into the service itself (ie dynamically querying the services for flavor information rather than expecting an ID put into a configuration file). That being said, we have managed to get it integrated into tripleo but it's rather complex. It does use ansible if you want to borrow some of the concepts for os_octavia.
Additionally we're still leveraging some of the puppet-octavia code to manage configs/nova flavors.
Thanks,
-Alex
As a starting point to improving this support, I'd like to gather
information from people who are using octavia in kolla ansible, and
what they have had to do to make it work. Please respond to this
email.
I've also tagged openstack-ansible and Tripleo - if there is any
useful information those teams have to share about this topic, it is
most welcome. Alternatively if your support for octavia also falls
short perhaps we could collaborate on improvements.
Thanks,
Mark
[1] http://eavesdrop.openstack.org/meetings/kolla/2019/kolla.2019-06-19-15.00.log.html#l-86
[2] https://etherpad.openstack.org/p/DEN-train-kolla-feedback
[3] https://opendev.org/openstack/openstack-ansible-os_octavia