Re: debops and openstack
hvjunk wrote:
Looking at the Enough project “quickly” you might be stuck with an
OVH solution as it
seems they cater/work-inside OVH’s tweaks of the stack.. and yes, there are some (I’m
using OVH so I know the “funs” too ;( )
Enough is based on OpenStack and relies on its API which is not
proprietary. Unlike AWS, you're not stuck with a single provider by
using their proprietary API. If OVH becomes less hospitable, an
organization using Enough could migrate to another OpenStack
provider[0]. This is in theory but, as you observed, Enough has a few
OVH specific elements. I'm hoping we'll get rid of them over time but
we're not there yet.
BEFORE you consider a OpenStack/OpenNebula deployment, ask
yourself these questions:
1) do I need allocation across hypervisors?
2) Do I have the network bandwidth from the compute nodes to the storages nodes?
3) do I have very-very fast storage nodes?
Right. People running Enough don't need any of this. Enough does not
require nor help anyone willing to deploy an OpenStack cluster: it
assumes there is one available. Enough depends on OpenStack for:
* Provisionning machines (although one could also manually add in the list of Ansible
hosts the IP to a machine provided by any means as long as there is an ssh access)
* Firewall
* Performing backups (VMs and/or volume snapshots)
* Restoring backups
* Destroying machines
[0] https://www.openstack.org/marketplace/public-clouds/