Bug#819816: ITP: debops -- Ansible based server management utility
On 05.04.2016 13:39, Maciej Delmanowski wrote:
> Hello,
>
> The base repository contains just scripts which are a frontend and glue
> between Ansible and playbooks/roles. Any ideas how the rest of the project,
> meaning the playbooks and roles themselves, should be handled, if at all, in
> Debian?
>
> Having a .deb package per role (separate git repository) seems a little
> overkill, and the number of roles would only grow over time. On the other
> hand, preparing a 'debian/' directory for easier packaging of all of the roles
> should be easily doable. The roles could alternatively be bundled some broad
> categories which would reduce number of packages involved, however that might
> be tricky when each role is tracked separately with its own version tags.
>
> Is there any precedence in Debian similar to this issue?
>
> Thanks,
> Maciej
Hi Maciej,
yes, I agree, the main advantage would be to have also the playbooks and roles as a package.
I've worked towards this now and prepared two packages, debops containing the scripts [1] and
another one, debops-playbooks [2] containing the playbooks and the roles.
This combination runs (/etc/debops.cfg point to /usr/share/ for the playbooks and roles) out of
the box, but it's going into experimental first because it needs some more fine tuning [3].
However, the debops-playbooks package needs more work, too. Yes, the collected invidivual repos
in roles/ are problematic, I've put unwanted things like the individual LICENSEs into the
Files-Excluded list in deb/copyright to please the Lintian complaints on these to begin with.
Cheers,
DS
[1] https://github.com/debops/debops
[2] https://github.com/debops/debops-playbooks
[3] like fixing the error on "could not create retry file '/usr/share/debops-playbooks/playbooks/site.retry'"
among other things like that
--
4096R/DF5182C8
http://www.danielstender.com/blog/
Reply to: