Refactoring to Ansible Collection

[mkbrechtel]

Refactoring of the repo to an Ansible Collection.

We now have three roles that basically do the same that the old playbooks did.

The ansible collection is now on top level of the repo.

Also i provided a playbook to recreates the terraform test environment for fast development iteration.

[mkbrechtel]

I will first proceed on putting the 3 playbooks for ceph, ovn and incus into 3 roles named the same. We might split that up later, but i first want to do the refactoring without changing the original logic.

[mkbrechtel]

Ok, this seems to have done it. The setup now runs on my server and from what i can tell everything works.

I think we still need to do some restructuring, but this brings everything in collection form and preserves the original logic.

This is a good point to merge now so we can iterate upon this.

[stgraber]

Hey, just to let you know that I'm not ignoring this :)

I've looked through it a couple of times so far and got a bit overwhelmed by it and have been crazy busy with other work so haven't had the time to start picking things up from this and merging, sorry!

[mkbrechtel]

Hey, just to let you know that I'm not ignoring this :)

I've looked through it a couple of times so far and got a bit overwhelmed by it and have been crazy busy with other work so haven't had the time to start picking things up from this and merging, sorry!

Thank you! :)

I reviewed your latest changes, i am trying on getting the refactoring-branch to include all those.

[mkbrechtel]

Hi @stgraber, i would suggest us having a little chat and make up a plan how we proceed. This is a big change and since the work is ongoing in the repo it would be complex to track all the changes, since the new structure is very much different from the old one. :)

[stgraber]

@mkbrechtel sure, we can arrange a quick chat. You can use https://calendar.app.google/5FghtnkVaYiLn8JK6 to book 30min with me when you have some time.

Keep in mind that I'm quite a noob when it comes to Ansible and effectively never played with collections, so I don't have much in the way of opinion on the matter other than obviously wanting to keep the current capability of this repository to just set some variables in an inventory, run a playbook and get the whole thing developed.

If we can keep things working that way and make it easier for folks to import that logic, or part of it into their own Ansible environment, that'd be great!

[mttjohnson]

I don't know if it would be possible for me to also attend any discussion on this, but I am also interested in helping here.

If not, it would be very helpful to know what ended up being discussed and any decisions that were determined to get a better sense of the direction and plan for incorporating changes into the repo.

[stgraber]

@mttjohnson we'll definitely want to update the PR/issue with whatever we come up with, but I can also let you know here about the time we end up picking and see if you happen to be available.

Given @mkbrechtel is based in Germany, I suspect it'll end up being a morning thing for us on the other side of the pond :)