<div dir="ltr"><div><div><div>updates:<br></div><div>- lago jobs were migrated, triggering pull request was tested and working, lago-bot commenting and check_merged still needs to be tested.<br></div><div>- 4 new fc23 VMs were added to the new Jenkins instance(fc23-vm04-07)<br></div>- 1 new el7 VM was added (el7-vm25)<br><br></div>I've given admin permissions to all infra members who already enrolled, in case anyone needs access.<br></div><div><br><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 4, 2016 at 12:16 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow:hidden">Just to make sure, don't confuse lago jobs with ovirt-system tests, the<br>
ovirt-system tests use bare metal slaves, those can't be created from templates<br>
so those can only be installed with pxe (or physically on site, as the virtual<br>
media of the ilo does not work so good)<br>
</div></blockquote></div></span>sure, only lago* jobs, either way we can have a final check before I add the github credentials.<span class=""><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span>> We already have a template for <span>fc23</span>, it's just creating a new slave from that<br>
> template (can be done from foreman too, faster than installing from scratch).</span></blockquote></span><div>thought we could migrate all lago jobs with the slaves at once, but because of [1]<br></div><div>NGN needs them too, so either way we need to have fc23 slaves on both jenkins's until<br></div><div>full migration.<span class=""><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div>+1, lets try to install a few new f23 slaves from template then.</div></blockquote></span><div>working on it, will update.<br><br></div><div> <br></div></div><div><br>[1] <a href="https://ovirt-jira.atlassian.net/browse/OVIRT-461" target="_blank">https://ovirt-jira.atlassian.net/browse/OVIRT-461</a> <br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 4, 2016 at 12:10 PM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Apr 4, 2016 at 11:52 AM, David Caro Estevez <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 04/04 11:49, Eyal Edri wrote:<br>
> On Mon, Apr 4, 2016 at 10:38 AM, David Caro Estevez <<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a>><br>
> wrote:<br>
><br>
> > On 04/03 20:27, Nadav Goldin wrote:<br>
> > > Hey David,<br>
> > > as part of the migration to <a href="http://jenkins.phx.ovirt.org" rel="noreferrer" target="_blank">jenkins.phx.ovirt.org</a>,I want to advance with<br>
> > > the Lago jobs. I already migrated<br>
> > > infra-puppet/infra-docs/ovirt-node/appliance/imgbased jobs, and so far<br>
> > they<br>
> > > seem all to work. As far as I understand the Lago jobs are pretty<br>
> > > independent so it should be rather simple. Currently there are 3 slaves<br>
> > > configured (fc23, el7, fc21).<br>
> ><br>
> ><br>
> > There are only 3 fc23 slaves, having one less, duplicates the check run<br>
> > time,<br>
> > and having only one, triplicates it, can you create new slaves instead of<br>
> > moving them from the old jenkins? (lago is not the only one using them, so<br>
> > migrating all of them is not an option)<br>
> ><br>
><br>
> Is it possible to add new slaves with the current state of pxe not working?<br>
> The ideal will be to have all new servers installed with the pxe fixed so<br>
> we can deploy many more slaves.<br>
> This way we can just add lots of slaves to the new jenkins.<br>
<br>
</span>We already have a template for fc23, it's just creating a new slave from that<br>
template (can be done from foreman too, faster than installing from scratch).<br></blockquote><div><br></div></span><div>+1, lets try to install a few new f23 slaves from template then.</div><div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
><br>
><br>
> ><br>
> ><br>
> > ><br>
> > > At the fist stage(until we finish the migration)<br>
> > > jenkins_master_deploy-configs_merged is not running, so we could control<br>
> > > which jobs get migrated. So if a patch to the jenkins yaml will be<br>
> > > introduced during the migration process it will have to be re-run<br>
> > manually.<br>
> > ><br>
> > > After migrating I'll disable the lago jobs in <a href="http://jenkins.ovirt.org" rel="noreferrer" target="_blank">jenkins.ovirt.org</a>, so<br>
> > even if<br>
> > > JJB runs we will have only one jenkins running the CI checks.<br>
> ><br>
> > Don't allow both to run anything at the same time, that will lead to<br>
> > confusion<br>
> > and branches being deleted at strange times on the github repo, if they<br>
> > run on<br>
> > one jenkins master, run them there only.<br>
> ><br>
> > ><br>
> > > One more question is if there are any other jobs which are dependent on<br>
> > the<br>
> > > Lago jobs(like the publishers which are dependent on all build_artifacts<br>
> > on<br>
> > > ovirt-node/appliance/node)<br>
> ><br>
> > Lago is self-contained, anything lago needs (check-build-deploy) is tagged<br>
> > as<br>
> > lago*, any other job that uses lago, get's it from the repos.<br>
> ><br>
> > ><br>
> > > As far as I understand the only thing needed for migration is updating<br>
> > the<br>
> > > github api tokens and running JJB with *lago*.<br>
> ><br>
> > And disabling the jobs on the other jenkins.<br>
> > The github configuration is not trivial though, the api token is valid only<br>
> > once and for a specific url. Also you have to configure the github hooks to<br>
> > point to the new jenkins (or it will not get any events), that is done at<br>
> > the<br>
> > github page, under project configuration.<br>
> ><br>
> > ><br>
> > > What do you think?<br>
> > ><br>
> > ><br>
> > > Thanks<br>
> > ><br>
> > > Nadav.<br>
> ><br>
> > > _______________________________________________<br>
> > > Infra mailing list<br>
> > > <a href="mailto:Infra@ovirt.org" target="_blank">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>
> ><br>
> > --<br>
> > David Caro<br>
> ><br>
> > Red Hat S.L.<br>
> > Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
> ><br>
> > Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605" target="_blank">+420 532 294 605</a><br>
> > Email: <a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a><br>
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
> > Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
> > RHT Global #: 82-62605<br>
> ><br>
> > _______________________________________________<br>
> > Infra mailing list<br>
> > <a href="mailto:Infra@ovirt.org" target="_blank">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>
> ><br>
><br>
><br>
> --<br>
> Eyal Edri<br>
> Associate Manager<br>
> RHEV DevOps<br>
> EMEA ENG Virtualization R&D<br>
> Red Hat Israel<br>
><br>
> phone: <a href="tel:%2B972-9-7692018" value="+97297692018" target="_blank">+972-9-7692018</a><br>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)<br>
<br>
> _______________________________________________<br>
> Infra mailing list<br>
> <a href="mailto:Infra@ovirt.org" target="_blank">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>
<br>
--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605" target="_blank">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a><br>
IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</div></div></blockquote></div></div></div><div><div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:%2B972-9-7692018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div></div></div></div>
<br>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org" target="_blank">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></div>
</div></div></blockquote></div><br></div>