4 ms·
> The APIs are pretty slow since they're all in python That and that everything is so goddamn brittle. It's incredibly hard to debug Openstack because there ar
by mschuster91 4y ago
> The APIs are pretty slow since they're all in python
That and that everything is so goddamn brittle. It's incredibly hard to debug Openstack because there are soooooooo many different components involved in simply hosting a couple KVM-based VMs, and the fact that I tried that right during the Python 2->3 conversion didn't help either.
Also, everyone of the myriad subcomponents needs their own database, their own user accounts, there are no shared configuration files. I get why it is so highly modularized (because of high-availability demand for each component), but FFS they could provide something like "kubeadm" that does all the tiny steps involved into setting up a cluster and joining a new node for you.
Once you get it running, it is pretty much smooth sailing until upgrade time, at which it gets really nasty yet again.
> The docs are not great and sometimes do not get updated.
One cannot help but feel that the docs sometimes haven't even been tested in real life.
- jetbalsa 4y agoSo the main methods of deploying openstack right now are Openstack-Ansible and Openstack Kolla, Both use Ansible to deploy everything and get the cluster up, but you /really/ have to dig into how things are setup if you are going to get a complicated install online. adding a new node into Kolla isn't too bad but can lead to the stack exploding at times. Upgrading is a huge PITA and I do opt to just wipe and replace most of the time.
- neverartful 4y ago"and the fact that I tried that right during the Python 2->3 conversion didn't help either" The huge and painful Python 2->3 transition could not have come at a worse time for OpenStack adoption. I believe it's one of the major reasons why OpenStack was found to be difficult to use, brittle, and documentation not up-to-date.