3 ms·
The problem with OpenStack as a replacement for VMware (outside of the complexity of installation), is that most people using VMware have an expectation of high
by tw04 12y ago
The problem with OpenStack as a replacement for VMware (outside of the complexity of installation), is that most people using VMware have an expectation of high availability being table stakes (a VM automatically being rebooted on a different node in the event of a node failure). OpenStack assumes the software on the front end can tolerate a node going down in it's current form and that the front-end application will just route around a node failure.
- aabbccdd 12y agoSUSE offers High Availability support for the recently released SUSE Openstack Cloud 5 https://www.suse.com/documentation/suse-cloud-5/ https://www.suse.com/documentation/suse-cloud-5/ Additionally it supports some components from vmWare: https://www.suse.com/documentation/suse-cloud-5/book_cloud_deploy/data/app_deploy_vmware.html https://www.suse.com/documentation/suse-cloud-5/book_cloud_d... Disclaimer: I work at SUSE.
- tw04 12y agoWell, since you work there, perhaps you can let them know that while www.suse.com resolves to an IPv6 address, your webserver doesn't actually serve up any pages via IPv6. So for those with native v6 connectivity like myself, the page just won't load.
- Swannie 12y agoAlso available in some commercial distro's of OpenStack, like Metacloud. I always cringe when people believe VMware HA == HA solution. No. It's part of a HA strategy, but 30 seconds to declare a node is dead, and then however long booting up a big server full of VM's takes - if your storage is not that great, that can be quite a while (boot storms are fun). If up to 15 mins of complete downtime counts as HA for you, great! But that's already risking 99.99% SLA.