[Debian-rtc-admin] system maintenance

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2019-05-28 12:23:08)
> Hi RTC team (cc Sam offering to help understand DSA-related matters),
> 
> Can someone more knowledgeable than me explain how to administrate our 
> services at vogler and dillon?
> 
> It seems DSA has now granted me membership of LDAP group debvoip 
> (checked by executing command "groups" after logging into either 
> vogler or dillon.
> 
> I found notes abot one single concrete command that seems should be 
> usable for me, at 
> https://salsa.debian.org/rtc-team/rtc.debian.org/blob/master/README.txt
> 
> ...but this fails for me with lots of failed permission errors:
> 
>   DEBIAN_USER=js ./deb-web-publish
> 
> 
> It seems I have read access to e.g. /etc/prosody/prosody.cfg.lua on 
> vogler but not write access to that directory (e.g. making a copy of 
> that file to *.bak fails).
> 
> How to proceed?

Now after my sudo password is properly setup¹ I can succesfully list 
available commands:

On vogler:
  * service {resiprocate-turn-server,repro} restart
  * service prosody {restart,reload,stop,start}

On dillon:
  * static-update-component wnpp-by-tags.debian.net
  * static-update-component mozilla.debian.net
  * static-update-component rtc.debian.org

So apparently the way to update website is _not_ what is documented in 
README of the git, but instead (after pushing changes to git) this:

  ssh dillon.debian.org static-update-component rtc.debian.org


I am still clueless as to how to do other administration tasks, like 
edit service configuration, update packages, introduce different 
services (including gaining sudo access to restart them).

I have made a local dump of /etc on vogler, and will now try sloppily 
delete parts seemingly not customized specifically by our team, but it 
I'd hate to learn later that there was some version tracked 
configuration simewhere and I have wasted my time fumbling in the dark 
here, so please anyone having a clue share some insight!


 - Jonas


¹ I had provided a password at https://db.debian.org/ and confirmed by 
GPG-signed email and received a response that my confirmation was 
processed, but apparently it didn't work as I noticed today it was still 
flagged as unconfirmed.  Not sure if my MUA was to blame - what now 
worked was this (with $COMMAND being the string shown at db.debian.org 
after providing a new sudo password):

  echo "$COMMAND" | gpg --clearsign | mail changes at db.debian.org

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/debian-rtc-team/attachments/20190528/bb879256/attachment.sig>