5 ms·
Openstack created a lot of possibilities for the way it "could" work or "should" work, but almost no methods where it does work. The problem with Openstack is
by johngalt 10y ago
Openstack created a lot of possibilities for the way it "could" work or "should" work, but almost no methods where it does work.
The problem with Openstack is it had too many moving parts, and no standard/reference implementation. It was destroyed by it's own grandiose goals. The project wanted to say 'yes' to every permutation of software. Making it a disaster from an operational standpoint. Everything promised, but nothing verified.
- yeukhon 10y agoI second this many times. The APIs were so inconsistent. I had to go through many hooks just to get the data I wanted. Openstack is nice, but Openstack community tried to create an open AWS. The problem is, everything gets so modular and too many components to deploy just to get Openstack working. It's a PaaS for IaaS foundation. Unless you have the resources to line up and support Openstack, I recommend just build on AWS/Google/Azure/Rackspace/Heroku/DigitalOcean, you name one. I wonder if big customers such as Bloomberg ever regret / think of moving to public/private IaaS.
- detaro 10y agoAgreed. Many moving parts, and every vendor could (and did) add their own variant of the moving parts, to integrate with their hardware/software/... And of course they then try to sell that and not the "standard" implementations, so not enough engineering work goes into those and the core components. It's a "collaborative" project with stakeholders that try to compete where they can... Visible also in things like the installation process (which for ages didn't have an "official" answer, so you had pay one of the big vendors to do it if you didn't want to try automate it yourself)