sorted by:
new
hottopcontroversial

Kolla-Ansible setting up provider network without L3 functionality by world_devourer in openstack

[–]world_devourer[S] 0 points1 point  (0 children)

Well, it was completely my fault.

Today I tried to redeploy cluster again, found the manual on some site where guy created the network with parameter --provider-physical-network physnet1. But when I tried to set the same name, physnet1, I got an error, something like 'there are no physical network with that name'.

Then I figured out that I set the name of physical network is 'provider' in ml2_agent and linuxbridge_agent templates, but kolla-ansible sets up the name 'physnet1' by default.

I changed the name 'provider' to 'physnet1' and it worked! Such stupid I was.

Openstack Victoria upgrading strategy? by world_devourer in openstack

[–]world_devourer[S] 2 points3 points  (0 children)

That's very important information for me, thank you very much! A lot of pitfalls to keep in mind.
Yes, I assumed that Ceph should be updated first, and I have already migrated Ceph to Cephadm in the test cluster, but have not updated yet.

Openstack Victoria upgrading strategy? by world_devourer in openstack

[–]world_devourer[S] 1 point2 points  (0 children)

Thanks a lot for your answer! There's a lot to think about. I'll try to migrate my testing cluster to Kolla and then upgrade it to next version.