[Debian-rtc-admin] RFA: rtc.debian.org

[Victor Seva]

Hi,

On Thu, 30 May 2019 at 07:46, gustavo panizzo <gfa at zumbi.com.ar> wrote:

> On Tue, May 28, 2019 at 06:09:09PM +0200, Victor Seva wrote:
> >As already mentioned long ago, We should first "move" the current prosody
> >manual config to dsa-puppet.
> >
>
> I don't think prosody management should be under DSA, puppet is great if
> you have root-level access to the server, which we don't.
>
> If we take the puppet route, every change will have to go through DSA.
> How are we going to troubleshot issues? add new features?
> Will DSA own the service then?
>
> What I like about puppet is that is hands-free, after merging into git
> the deploy happends by itself, that part I want to replicate.
>

Sorry but  management is already through DSA. DSA owns the service.
And the proper way to ask for changes is via PR to dsa-puppet.
Changing manually the config was just possible due to the kindness of one
nice DSA admin.

Every time I had to change something it was a pain. We must follow
dsa-puppet road.


> >Initial work, just adding the prosody module is here [0]. Next step would
> the module does not support [1] the puppet version DSA is using
>

0.4.0 version does [2]


> >be to use the module to generate the configs We need. And modify it if
> >something is missing and try to push those changes upstream.
> >
> TBH i'd prefer a module that doesn't hardcode the settings
> in its code but takes them from hiera as key values (e.g. $ssl_key:
> /path/to/file).
> but this is only a piece of opinion
>

We are free to modify the module to our needs. It's a starting point.
Nothing was done.

>But, I have no idea how to test this and see what the result would be. I
> >would need to investigate how to play with dsa-puppet in a local
> >development environment. Any hints?
>
> again, not owning the deployment makes hard for us to test stuff,
> we don't even have access to hiera to do a puppet apply --noop
> from a local checkout of the code
>

Indeed, We have to figure out how to test it. We need to ask dsa for advise.


> >[0] https://salsa.debian.org/vseva/dsa-puppet/commits/vseva/xmpp
>
> [1] https://github.com/mayflower/puppet-prosody/blob/master/metadata.json


[2]
https://salsa.debian.org/vseva/dsa-puppet/blob/vseva/xmpp/3rdparty/modules/prosody/metadata.json

Cheers,
Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-rtc-team/attachments/20190530/443b4694/attachment.html>