Bug#819816: ITP: debops -- Ansible based server management utility
On Thu, 7 Apr 2016 09:27:52 +0200 Maciej Delmanowski <drybjed@drybjed.net> wrote:
> On Apr 06, Daniel Stender wrote:
> > 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.
>
> I was worried for a bit, but it looks like the debops-playbooks package works
> fairly well... Do you get the 'master' branch of all of the roles, or do you
> grab the last tagged commit? Some of the roles are not tagged yet.
Thanks for appreciation. That way it runs out of the box, plus the user could
run debops-update on individual projects to get the latest snapshot. Collecting
deb/copyright was painful, but it's worth it ...
The upstream tarball actually is the result of debops-update, manually stripped
and tar-ed with --exclude-vcs. That appears to be the only way to get also the
roles right now ...
> The project is in a transition period at the moment where I clean up some of
> the roles. How will the debops-playbooks be updated when a new role is added
> or an existing role is updated?
I don't have a clue yet how to create a get-orig-source target. For packaging,
the most convenient way would be if the roles are included in the project repo,
could that be possible somehow?
> I've had an idea to do something similar to
> https://wiki.debian.org/AutomaticPackagingTools and create a script that could
> package Ansible Galaxy roles instead of bundling everything in one huge
> package. Although apart from DebOps itself I'm not sure if other Galaxy users
> are writing roles to work together, or separately.
Thanks for pointer, I'll check that out ... So far everything works but needs
only some more fine tuning but there might be other perspectives for packaging
Ansible stuff generally.
> I'm switching the project mailing list to a self-hosted one (on DebOps,
> obviously), at https://lists.debops.org/ (mailing list address would be
> <debops-users@lists.debops.org>. Can you change that in the package
> description, or should I make the changes in the documentation first?
Please go ahead. When it's in experimental, I'll add this and much more
information to the package.
> As for the documentation of various roles, there's a separate
> http://docs.debops.org/ page generated by Sphinx, code can be found in
> https://github.com/debops/docs/ repository. Perhaps a separate debops-docs
> package could be made using that?
Yes, sure, a separate docs package would be an option ... That could be done.
> One more thing, some of DebOps roles require Ansible v2.0+, can you set the
> required Ansible package version accordingly?
Thx for pointer. On the to-do list. :-)
Thx,
Daniel
--
4096R/DF5182C8
http://www.danielstender.com/blog/
Reply to: