:: Re: [devuan-dev] ci.devuan.org is d…
Top Pagina
Delete this message
Reply to this message
Auteur: Ralph Ronnquist
Datum:  
Aan: devuan developers internal list
Onderwerp: Re: [devuan-dev] ci.devuan.org is down
Daniel Reurich wrote on 24/4/19 9:04 am:
> [snip]
> ... Therefore I
> propose if there is a consensus to set up a new instance with jenkins
> with a temporary url from a domain/subdomain we do have control of. (If
> need be I can use a subdomain of devuan.nz as a temp url as I have that
> domain registered and full control of that zone file) until we can get
> the dns issue sorted.
>
> If I can get access to a backup of the old jenkins instance, even if
> it's fairly old, then I can quickly get that service back on line
> functioning in the same fashion as it had been previously.


There is the VM "ci.ganeti1.devuan.org" (vnc 127.0.0.1:5128) which I
believe is/was set up for this purpose. It's one of those VMs I don't
have access to, but maybe jaromil can open it up.

In full, nash have the following instances, where I've indicated the
ones seemingly having access (afaics).

backup  (192.168.97.85,-) centurion evilham katolaz rrq
ci      (192.168.97.91,?) ?
dak     (192.168.97.90,?) ?
doc     (192.168.97.86,54.36.142.178) blinkdog katolaz rrq
gitea   (192.168.97.89,54.36.142.180) katolaz rrq
repo    (192.168.97.84,54.36.142.177) katolaz rrq
web     (192.168.97.87,54.36.142.179) evilham jrml katolaz rrq sucker


I'm not totally sure about what all those VMs are intended for other
than gitea and web (for the coming gitea, and for the new www).

I think "doc" was created for a devuan documentation effort instigated
by blinkdog some while ago (not happening atm). "ci", "dak" and "repo" I
believe were set up to replace the current of those, presently running
on cluster01.nexlab.thc (I think).

"backup" is/was probably intended for some backup aspect.

If "ci" and "dak" are not actually servicing anything, it's doable (with
some effort) to turn them off, then mount their file systems and add
access. Or anyone currently with access (esp katolaz) can add open them
to all. I can deal with those I have access to, eg using the keys from
web and backup.

The table for newtonia looks like this for me:

amprolla   (192.168.97.80,?) ?
galaxy     (192.168.97.88,5.196.38.19) centurion evilham flux katolaz
pmeade rrq
pkgmirror  (192.168.97.81,?) ?
fw         ?
gitlab     (192.168.97.79,5.196.38.17) centurion evilham jaromil katolaz rrq
ns1        (192.168.97.83,?) ?


And the table for napier is:
files (192.168.97.82,5.135.82.177) centurion katolaz parazyd fsmithred
rrq evilham jaromil

As for cluster01.nexlab.thc, I only have access to www.devuan.org, with
the following set up:
"www.devuan.org" (192.168.16.2,46.105.191.76) bardo jaromil nextime rrq
evilham hellekin katolaz parazyd

Ralph.