[Gluster-infra] More proxy cleanup coming

[Michael Scherer]

Hi,

So now we have a new proxy (yes, I am almost as proud of it as the
firewall), I need to move the old service on the old proxy to the new
one. It will imply some time of unavailability, because DNS has latency
to propagate, and we need DNS in place for letsencrypt before
deploying. And we still have DNS issue on the server side that make
change take far more longer than before.

While I can manually do some magic, I rather avoid manual fiddling when
I can, so I would like people to tell how critical are each of theses
domain so I can figure the best way, e.g, can they be down for 10 to 20
minutes for a while, do people want to know some time in advance, etc:

- bits.gluster.org
- ci-logs.gluster.org
- softserve.gluster.org
- fstat.gluster.org

I also plan to move jenkins (so build.gluster.org) on the said proxy,
and the jenkins stage instance, and later move the VM to the internal
network. 

While the stage instance is not a problem, I guess we need to find some
time for the prod one.


-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.gluster.org/pipermail/gluster-infra/attachments/20180315/7c0adb2f/attachment.sig>