7:35 p.m.
--=-Be7faPQe1vIfreVF1FcP
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Le mardi 16 juin 2015 =C3=A0 03:38 -0400, Eyal Edri a =C3=A9crit :
=20
----- Original Message -----
> From: "Karsten Wade" <kwade(a)redhat.com>
> To: infra(a)ovirt.org
> Sent: Tuesday, June 16, 2015 6:29:04 AM
> Subject: Re: migration of services from linode server to phx2 lab
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hi,
>=20
> Between myself (original linode01.ovirt.org admin) and Michael (misc,
> aka knower-of-stuff), what can we do to get us off this Linode
> instance? From what I can tell, at least Mailman is running from there.
>=20
> If we still need service failover, can we switch to another Red
> Hat-provided service such as an OpenShift or OpenStack instance?
=20
Hi Karsten,
I know this has been taking for too long, but unfortunately there are man=
y
reasons
and obstacles that prevented us from moving, which i'll explain
below,
while there is a risk right now of moving services to PHX, but i think we=
can
try.
=20
Blocking items:
- were missing more hypervisors to the production DC ( we finally got th=
em
installed last week, and are now in final stages of bringing them up)
- storage issue - currently NFS storage is quite slow, we are
testing mo=
ving to a mixed mode of local + nfs for the jenkins slaves,
though might be that the production service
won't get =
affected too much - worth a try.
- lack of monitoring for servers, which might add risk if we hit an
issu=
e.
=20
there are some other issues, but not blocking imo.
=20
Here is what needs to be done (per service to migrate off linode), and we=
'd
appreciate any help given.
1. create new VM on production DC in PHX (assign dns/ip/etc.. )
2. create puppet manifests to manage that vm, so it will be easy to repro=
duce it
and maintain it
3. install the relevant software on it (for e.g
mailman/ircbot/etc...)
4. test to see it works
5. do the actual migration (downtime of existing service, and bringing up=
the new
one)
So, last time I did look, the puppet setup was a bit "unfinished" rather
overkill ( using r10k to deploy count as overkill when you do not have
stage/prod/qa, at least for me ). Did stuff changed, or should first
some effort be made to fix/automate/improve the puppet setup ?
--=20
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS
--=-Be7faPQe1vIfreVF1FcP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAABAgAGBQJVgMDXAAoJEE89Wa+PrSK9qo4P/jyKeWkR59sVLdz/CxcAzJXa
U3DRgLcp3Ejesv06Jd6OGwWVtFJCxWZX83ME13nqIWUWABk+GIVFJn69qgb/sK+n
CP41CUHlobTsQMndSeirdPUMQZ9TJLxPjxJyTEmiPYyGulM75dQ8pk/g71oNb8JR
GwpHtyxp5Lr87pyezMrHUyA/mlVm9PBQrV2W/3b9YVo7hZjwK35k33wA46A05Een
kTDN/PpW33j6w2giskUERG9PpaSUt5+vG2qTfMjc/37XDFm+nLpjmLdW7lZWJ6+H
OwA0U21VydImSzn3o+erng4qPDtSCqB7S+wF0E+lxpBIjKAePI2u793t8YszYEh9
Y2g3oacS2/qQ7LYk+/VrM8fvn21IsHUkURl3aVfYsWBHv40KdCqufJ4lH72VPBVE
9ZrOkfwtlPnPqHvhh5c9BlpfGAGcKRir2nGQU1vVSS1Fk8bl21QAbDpFbKMfn82v
unDNMLr4oT0It1ueAscupUaIE0jkVF0IJDV2eXeRhvTXFj9rN7BMuAdxI+bem3Z5
Ic71cxdH1xYNO6InboQTj93p6m0jYLzByIv8gjuEK4CcJybMk+ytNeLj7sCAlrzI
lnJ7eJxGoW1kW/LdCIDWQFzKt+Lx+ImND/FuDNMs7p1E2K3iyAtDZwDL94uDDib+
bHHKmOKUt85nv/mJg+NU
=aZNh
-----END PGP SIGNATURE-----
--=-Be7faPQe1vIfreVF1FcP--