Ever tried installing it? It's an incredibly complex piece of work with boatloads of services to configure and debug... and upgrade.
At the time I last tried it (some two or three years ago):
- most of the documentation was written assuming an rpm-based distro and not Ubuntu or Debian (I remember especially having had trouble with subtle differences in iptables/nftables between the distributions)
- on top of that it was right in the middle of a python2 => 3 migration with the result of shit breaking left and right
- it was/still is written in Python which means a second or more for every CLI command to initialize, much less actually do something
- half the instructions in the documentation seem to never have been actually tested, which combined with the two points above made for a really punishing "experience", especially with more rarely-used features such as k8s-in-openstack
- the documentation itself still is (just looked it up) badly organized, with you needing to read four guides (Install, User, Configuration, Ops/Administration) per OpenStack component. Ideally, there should only be one guide for Installation/Upgrade (including Configuration and everything from Ops/Admin) that has everything in it to get all supported parts of the component up and running, one User's Guide that shows how the component is used and what the best practices are, and one Troubleshooting guide.
If you can set it up into a working configuration, it's a nice project for sure. But the road to that point is rough, and you will likely not even want to think about an upgrade simply because of how complex it is.
It's basically consultingware for IBM/Redhat. It tries to be everything you could ever possibly need, the interactions between the components are brittle, and it has all the complexity of a huge k8s deployment except your ability to affect what's going on underneath is like trying to control an angry beehive with a 20 ft pole.
Think Urbit but for sysadmins and you pretty much get the vibe.
At the time I last tried it (some two or three years ago):
- most of the documentation was written assuming an rpm-based distro and not Ubuntu or Debian (I remember especially having had trouble with subtle differences in iptables/nftables between the distributions)
- on top of that it was right in the middle of a python2 => 3 migration with the result of shit breaking left and right
- it was/still is written in Python which means a second or more for every CLI command to initialize, much less actually do something
- half the instructions in the documentation seem to never have been actually tested, which combined with the two points above made for a really punishing "experience", especially with more rarely-used features such as k8s-in-openstack
- the documentation itself still is (just looked it up) badly organized, with you needing to read four guides (Install, User, Configuration, Ops/Administration) per OpenStack component. Ideally, there should only be one guide for Installation/Upgrade (including Configuration and everything from Ops/Admin) that has everything in it to get all supported parts of the component up and running, one User's Guide that shows how the component is used and what the best practices are, and one Troubleshooting guide.
If you can set it up into a working configuration, it's a nice project for sure. But the road to that point is rough, and you will likely not even want to think about an upgrade simply because of how complex it is.