Re: migration of services from linode server to phx2 lab

--cz6wLo+OExbGG7q/
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 06/17, Michael Scherer wrote:
> Le mardi 16 juin 2015 =E0 03:38 -0400, Eyal Edri a =E9crit :
> >=20
> > ----- Original Message -----
> > > From: "Karsten Wade" <kwade@redhat.com>
> > > To: infra@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 ther=
e.
> > >=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 m=
any 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 =
them installed last week, and are now in final stages of bringing them up)
> >  - storage issue - currently NFS storage is quite slow, we are testing =
moving to a mixed mode of local + nfs for the jenkins slaves,
> >                    though might be that the production service won't ge=
t affected too much - worth a try.
> >  - lack of monitoring for servers, which might add risk if we hit an is=
sue.
> >=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 rep=
roduce 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)
>=20
> 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 ?


Still using only one branch, but hiera is enabled and ready to start getting
used. It still needs some refactor but if we don't use it we will never do
it... so better using it imo


>=20
>=20
> --=20
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>=20



> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra


--=20
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605

--cz6wLo+OExbGG7q/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVgSCjAAoJEEBxx+HSYmnD96QH/3WWTUFe7MF9iKqpMahKyJke
QCz962SHCaGYdB1I53rYA9sSKF2LUzGhEOpg4VHVMn+FsrV70Ahlo/WLWXKJzkg3
xRmztYAE69xpAAPPbqhOSBJWPEjrQMOICdlFV4ChSLrVBJt2FN44m2GM1wMSYysW
ZcSzGs379pOrFU88gSO+AC1gfUcbQdOKtdOZzMYIurt5spUVplhBQDOzTfUn3fFL
VaydNokNNpMbqdTYnWn7i/XqF6o6zfmSeeMitexSfETn9B/kqQ5PzK4kpFYBHvor
B4krtKbrt+dB9T+HjjV8eiU5z2uJSYuewSFWM+Y5rmwmov9VR2IYvgeSk3RfO5k=
=wREK
-----END PGP SIGNATURE-----

--cz6wLo+OExbGG7q/--