3:12 p.m.
On 19/07/2020 16:45, Maciej Delmanowski wrote:
I haven't had a chance to play with OpenStack yet, but I know roughly what it
is and what it does.
I've seen that I can create vms inside of OpenStack (like one would do
with Proxmox) but how do they play with Openstack components? This is
still a mistery to me.
I'm nore interested in OpenNebula[1] as the
hypervisor/virtualization layer due to less complexity between the two
solutions and more focused OpenNebula development[2]. The article linked is
a bit old so take that into account. OpenNebula seems to be more focused on
smaller-scale deployments which DebOps excels in at the moment.
I'm interested in OpenStack because of the Enough project
(https://lab.enough.community/main/infrastructure) which, btw, uses
debops. It was Nicolas pointing me at it. The Enough community seems to
have already (successfully?) achieved what I'm trying to do on my own.
There is a solid chance that I can ditch part or all I've done so far
and join the Enough project, however the OpenStack is a barrier for me
and it could also a barrier for many others (given the additional layer
of complexity as Imre has noted). The fact that Enough is tight to OVH
is, most likely, a direct consequence of OpenStack too.
In both cases the installations require a bunch of different underlying
services to function (MariaDB, RabbitMQ, etc.), management roles for these
either are already in DebOps, or can be implemented as needed. Then there are
packages with the software implemented for the OpenStack or OpenNebula
specifically which could also be added in the project.
Are these specific packages needed to split processes across the
OpenStack components? Nova etc... (I'm guessing here)
I imagine that
a separate set of playbooks could be developed to aid deployment of
a production infrastructure in each case, with different types of hosts
(compute, storage, cpu) instead of the default set of playbooks focused on
a per-service general-purpose deployment. The debops scripts can be updated to
acommodate multiple sets of playbooks for that purpose.
There's already the openstack-ansible[3] project that allows deployment of
OpenStack unsing Ansible; we could see what components are still missing in
DebOps for it to function and implement them over time.
If I understand you well, debops would take care of both the OpenStack
infrastructure itself and the vms running inside of it
In the end, I think that DebOps as a solid base to deploy OpenStack,
OpenNebula or Kubernetes in production environment is a good target to aim
for. Many of the underlying components are shared, which should make things
a bit easier.
Cheers,
Maciej
Thanks Maciej