<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 10, 2016 at 7:45 AM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div>Hi all,<br></div>I installed yesterday a fresh Jenkins VM in the PHX datacenter at <a href="http://jenkins.phx.ovirt.org" target="_blank">jenkins.phx.ovirt.org</a> running centos 7.2, few details:<br></div><div>1. It is puppetized, but still needs some verification[1], I was able to auto-generate the plugins list from <a href="http://jenkins.ovirt.org" target="_blank">jenkins.ovirt.org</a> into the puppet manifest, so it has exactly the same plugins installed. the concept might also work for future migrations we do between the instances.<br></div><div>2. the jenkins data directory is 500gb configured with lvm and xfs. I was able to do "live" storage incrase by adding a new volume to the LVM group in the following procedure:<br><ul><li> created new virtio volume in the VM from phx-engine<br></li><li> fdisk /dev/vdd then: n -> p -> 1 -> enter -> enter -> t -> 8e -> w</li><li> vgextend jenkins_lvm /dev/vdd1</li><li> lvextend /dev/mapper/jenkins_lvm-data -L28G</li><li> xfs_growfs /dev/mapper/jenkins_lvm-data</li></ul><p>I was unable to increase the volume size from the engine, and then increase the partition size(only create a new partition on the same volume with the new increased space in the volume), not sure if that is possible.<br></p></div></div></blockquote><div><br></div><div>We need to allocate it enough memory & cpu as well, if the current hypervisors can't support it, we need to move another hypervisor into the production DC.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><p></p><p>3. authentication - same as <a href="http://jenkins.ovirt.org" target="_blank">jenkins.ovirt.org</a> for now: self enrol and adding permissions(ping me)<br></p></div></div></blockquote><div><br></div><div>For now might be OK, but we need to think if we want to change it before the migration, SSO will probably take time to implement so I wouldn't block on it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><p></p><p>4. there is much more configuration that needs to be done to make it functional, but i guess we can start by testing it :)<br></p></div><div>[1] <a href="https://gerrit.ovirt.org/#/c/53309/" target="_blank">https://gerrit.ovirt.org/#/c/53309/</a><br><br></div></div></blockquote><div><br></div><div>Indeed. one thing we need to make sure it to yamelize all the jobs that are not in yaml yet, before the migration.</div><div><br></div><div>I also created a ticket [1], so lets continue tracking progress there.</div><div><br></div><div><br></div><div><br></div><div>[1] <a href="https://ovirt-jira.atlassian.net/browse/OVIRT-401">https://ovirt-jira.atlassian.net/browse/OVIRT-401</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div><br></div><div><br></div></div>
<br>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Eyal Edri<br>Associate Manager<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div>
</div></div>