4:45 p.m.
On lip 19, Damiano Venturin wrote:
I'm just a few videos into openstack. I never read/learn anything
about
it before.
From what I've seen so far it seems like debops could be managing the
architecture underlying openstack.
That's what the Enough community seems be doing
https://lab.enough.community/main/infrastructure/ (thanks Nicolas)
I wonder if any of you has ever worked on openstack with or without
debops. I'd like to exchange a couple of emails (or talk) to get some
guidelines regarding this topic. Anyone?
I haven't had a chance to play with OpenStack yet, but I know roughly what it
is and what it does. 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.
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. 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.
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
[1]: https://opennebula.io/
[2]: https://opennebula.io/opennebula-vs-openstack-user-needs-vs-vendor-driven/
[3]: https://github.com/openstack/openstack-ansible