Re: PHX updates - hypervisors in Jenkins datacenter
--Y5rl02BVI9TCfPar
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 06/02 05:40, Evgheni Dereveanchin wrote:
Hi all,
=20
As part of the upgrade process to 3.6 I will be rebuilding
all hypervisors to CentOS7, and I'm starting with the Jenkins
Datacenter. For this, I am evacuating slave VMs by shutting
them down and restarting in the new cluster with CentOS hosts.
=20
I'm currently working on ovirt-srv04 so please don't schedule
any VMs on that host until it's rebuilt.
=20
I found several VMs running on that host which are not listed
on Jenkins so I can't mark them offline there for the update period:
=20
fc21-vm01.phx.ovirt.org
el6-vm06.phx.ovirt.org
=20
If anyone knows what these VMs are used for - please tell me,
otherwise I will just restart them as well.
=20
Also this VM is present on this hypervisor:
artifactory.phx.ovirt.org
=20
Is it used by the slaves? Can it be shut down for a few minutes?
I'm not sure I will be able to live migrate it even as the F20
hosts we have in the old cluster have issues with live migration
even to other F20 hosts.
This vm is quite critical actually, I'd move it to the prod cluster.
It's used by all the engine jobs, to pull the jar dependencies from, and al=
so
to publish some ovirt jars.
The jobs should fallback to the official maven repos if it's not available,=
but
some might not use that fallback config. I'd say it's ok to take it out for=
a
few minutes, just send an email to the devel list so they are not surprised=
if
any jobs fail during that time.
=20
Regards,=20
Evgheni Dereveanchin=20
=20
_______________________________________________
Infra mailing list
Infra(a)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(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
--Y5rl02BVI9TCfPar
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJXT//rAAoJEEBxx+HSYmnDWdoH/R/Tg1nYTWBAVE1LgkG7xHdS
IlLG+IrMNgnuaLV9KKiXE5+NhBQs9BHlTCtnnQyVJt4RkUwejMzNRY74AhxVobhg
3cZTHAuwljYG+aVREtJmU7nX40bFAy/uPqhHMpr/AfyKISzGypa/VYnsqjc4hMdY
T1yH48yUwRKPcn8mRvumRcs/9/fyTGmMw3y0veWZBC4Ygk5EkY8Ry79Iz5zoYHHd
T7x8PBPCYL0t9tHpT1UF+/hGg6oZwk97qr+KSquVVKGx61gM798vY3BvgNTGrBad
nuxr91v2nes73kHQDX/8tJ+HIzwi/hb5Q4AZ0XRHKp5zco9rW5lFxw+Tx8uec2o=
=CQUY
-----END PGP SIGNATURE-----
--Y5rl02BVI9TCfPar--
Attachments:
- attachment.bin (multipart/signed — 2.6 KB)