the controllers. The default retry timeouts
> (some are up to 25 minutes) are very long (it will keep trying to
> accomplish the request) to accommodate very slow (virtual box) hosts
> and the test gates. You will want to tune those down for a production
> deployment.
>
> Michael
>
For the records, I’m actually working on a fairly large overhaul of our
Openstack services deployement using Kolla-Ansible. We’re leveraging
kolla-ansible to as smoothly as possible migrate all ou legacy architecture
to a shiny new using exactly the same topology as described upper (Using
Hi guys,
I'm finishing to work on my POC for Octavia and after solving few issues
with my configuration I'm close to get a properly working setup.
However, I'm facing a small but yet annoying bug with the health-manager
receiving amphora heartbeat UDP packet which it consider as not correct and
Doing the same documentation process here as well (except that I’m using
kolla). The only annoying thing is the doc submission process :-/.
Le lun. 22 oct. 2018 à 16:50, Erik McCormick a
écrit :
> Oops, dropped Operators. Can't wait until it's all one list...
> On Mon, Oct 22, 2018 at 10:44 AM
Hi eric!
Glad I’m not the only one having this issue with the ssl communication
between the amphora and the CP.
Even if I don’t yet get a clear answer regarding that issue, I think your
second issue is not an issue as the interface is mounted on a namespace and
so you’ll need to list all nic
Hi guys,
I'm back to business with Octavia after a long time but I'm facing an issue
that seems a little bit tricky.
When trying to create a LB using either APIs (cURL/postman) calls or
openstack-client the request finish with an error such as:
`Network c0d40dfd-123e-4a3c-92de-eb7b57178dd3 not
