Network architectures in openstack-ansible

[phonix6]

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [x] This doc is inaccurate in this way: The information is in accurate and also unclear.
The information suggested to use /etc/network/interfaces which is obsolete and not being used in ubuntu anymore instead the information should suggest the use of netplan to configure interfaces
For the Centos 8, the info is also outdated.
In addition the guide speaks about using the following ip address:
IP address: 10.0.0.11
Network mask: 255.255.255.0 (or /24)
Default gateway: 10.0.0.1

The Ip range is 172.29.236.0/22 and not 10.0.0.0/24

It makes enormous incompatibility issues for someone who just follows the guide.

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack: https://ask.openstack.org
 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 22.0.1.dev9 on 2019-02-05 19:19:26
SHA: 3512f89b98b71f8ab1eaab27becc04f0534bea5a
Source: https://opendev.org/openstack/openstack-ansible/src/doc/source/user/network-arch/example.rst
URL: https://docs.openstack.org/openstack-ansible/victoria/user/network-arch/example.html

[Jonathan Rosser (jrosser)]

Hi,

Lots of things going on here so i'll try to address them in turn.

* You can still use ifupdown on ubuntu focal systems by installing the 'ifupdown' package. That may have been necessary until recently as there were network configurations which could not be achieved with netplan as there were functionality gaps. This situation is improved though.

* There is a netplan example in the openstack-ansible repo already at https://github.com/openstack/openstack-ansible/tree/master/etc/netplan and i've just made a patch to update the documentation to point to that. https://review.opendev.org/c/openstack/openstack-ansible/+/774425

* Could you give a specific reference to which Centos-8 documentation is out of date?

* The only references that I can find in the master branch to 10.x networks are

grep -nir 10.0.0.1 .
./source/reference/inventory/generate-inventory.rst:68: ip: 10.0.0.10
./source/reference/inventory/generate-inventory.rst:70: ip: 10.0.0.11
./source/reference/inventory/generate-inventory.rst:72: ip: 10.0.0.12

The documentation already states 'The CIDRs and VLANs listed for each network are examples and may be different in your environment'. I'm not sure there is anything particularly wrong with the generate-inventory reference using the 10.x CIDR as it is a valid example. Is there somewhere else you are seeing these network ranges used?

Thanks for the feedback,
Jonathan.

[phonix6 (phonix6-deactivatedaccount-deactivatedaccount)]

found the original link:

https://docs.openstack.org/openstack-ansible/latest/user/l3pods/example.html

Here the pod with the /24 are definitely overlapping!
This wouldn't be a problem in case all pods have their "own" network in their own namespace.
But if it's being routed, the issues with Network id, broadcast id, etc. could occur.

Moving from:
Management: 172.29.236.0/22
Tunnel: 172.29.240.0/22
Storage: 172.29.244.0/22

Will require additional 18 dedicated Network and broadcast addresses, in addition to the already 6 in place.