| *** Apoorva_ has joined #openstack-third-party-ci | 01:37 | |
| *** Apoorva has quit IRC | 01:40 | |
| *** Apoorva_ has quit IRC | 01:42 | |
| *** stakeda has joined #openstack-third-party-ci | 01:54 | |
| *** esberglu has quit IRC | 01:56 | |
| *** esberglu has joined #openstack-third-party-ci | 01:57 | |
| *** esberglu has quit IRC | 01:58 | |
| *** esberglu has joined #openstack-third-party-ci | 01:58 | |
| *** s-shiono has joined #openstack-third-party-ci | 02:08 | |
| *** esberglu has quit IRC | 02:43 | |
| *** esberglu has joined #openstack-third-party-ci | 03:13 | |
| *** esberglu has quit IRC | 03:17 | |
| *** esberglu has joined #openstack-third-party-ci | 05:44 | |
| *** esberglu has quit IRC | 05:49 | |
| *** esberglu has joined #openstack-third-party-ci | 07:55 | |
| *** esberglu has quit IRC | 08:16 | |
| *** fdegir has quit IRC | 08:47 | |
| *** TheJulia has quit IRC | 08:47 | |
| *** stakeda has quit IRC | 08:47 | |
| *** krtaylor has quit IRC | 08:47 | |
| *** mmedvede has quit IRC | 08:47 | |
| *** hamzy has quit IRC | 08:47 | |
| *** patrickeast has quit IRC | 08:47 | |
| *** fungi has quit IRC | 08:47 | |
| *** jungleboyj has quit IRC | 08:47 | |
| *** anthonyper has quit IRC | 08:47 | |
| *** pots has quit IRC | 08:47 | |
| *** strigazi has quit IRC | 08:47 | |
| *** lennyb has quit IRC | 08:47 | |
| *** xinliang has quit IRC | 08:47 | |
| *** ChanServ has quit IRC | 08:47 | |
| *** rfolco has quit IRC | 08:47 | |
| *** rajinir has quit IRC | 08:47 | |
| *** s-shiono has quit IRC | 08:56 | |
| *** openstack has joined #openstack-third-party-ci | 13:55 | |
| *** Apoorva has joined #openstack-third-party-ci | 15:47 | |
| *** Sukhdev_ has joined #openstack-third-party-ci | 15:58 | |
| *** robcresswell has joined #openstack-third-party-ci | 16:05 | |
| robcresswell | o/ Hey all, running into an issue with nodepools images not having Java installed. I'm assuming this is because I'm using newer elements from upstream, and have either missed an element, or used one that has since had java installation removed. Any thoughts on how I fix this? | 16:07 |
|---|---|---|
| mmedvede | hey robcresswell | 16:08 |
| robcresswell | o/ | 16:08 |
| mmedvede | I am checking my image build | 16:11 |
| mmedvede | robcresswell: the java was installed during puppet apply, iirc puppet-jenkins module | 16:13 |
| mmedvede | I believe upstream infra no longer uses puppet during image build, this is why you did not find it | 16:13 |
| robcresswell | mmedvede: Any idea where that install comes from? Its not default in the ubuntu-xenial images. | 16:14 |
| robcresswell | Just trying to figure out what prompts it to install | 16:14 |
| *** sambetts has joined #openstack-third-party-ci | 16:17 | |
| mmedvede | robcresswell: I think this is the part you want https://github.com/openstack-infra/puppet-jenkins/blob/89d89683e3af408d99a86c349e6da27daace5d6e/manifests/slave.pp#L33-L47 | 16:24 |
| mmedvede | robcresswell: you want jenkins::slave if you intend to use nodepool + jenkins. If you plan on zuulv3, then it is different | 16:26 |
| robcresswell | mmedvede: nodepool + jenkins for now | 16:26 |
| robcresswell | mmedvede: Mostly just using the content from puppet-openstackci | 16:27 |
| sambetts | nodepool doesn't build images with puppet any more as we understand it, so we're wondering how we install java | 16:27 |
| sambetts | https://github.com/openstack-infra/project-config/tree/master/nodepool/elements/jenkins-slave my understanding was that this element should handle all the jenkins slave requirements | 16:28 |
| robcresswell | Yeah, this is all a bit of a headache since upstream diverges from the 3rd party ci so much and lots of the content it outdated :( Ah well. | 16:28 |
| sambetts | but there are no package dependencies there | 16:29 |
| robcresswell | ergo, no java :) | 16:29 |
| mmedvede | yes, you got to look at project-config pre cleanup | 16:29 |
| mmedvede | i.e. before puppet was pulled from their images | 16:29 |
| mmedvede | https://review.openstack.org/#/c/460728/ | 16:29 |
| sambetts | This commit implies we shouldn't have too https://github.com/openstack-infra/project-config/commit/2fe9c2125dc57c1d5a60e1492afd5d483a6abe4c | 16:30 |
| robcresswell | Right, that makes me think we should just use the jenkins_slave element; but it doesnt work :) | 16:31 |
| robcresswell | jenkins-slave* sorry | 16:31 |
| sambetts | it seems like the jenkins-slave element wasn't updated as puppet was removed :( | 16:31 |
| mmedvede | so maybe you found a bug then. I see no element there that install jdk/java | 16:32 |
| robcresswell | So now we're trying to figure out where Java is supposed to be installed in this process on a Xenial image, built by Nodepool | 16:32 |
| robcresswell | mmedvede: Any thoughts on where / how we would make that happen? | 16:32 |
| mmedvede | yes, if you want to use the VM with jenkins, you need java | 16:32 |
| robcresswell | mmedvede: We know, we just don't know how to make nodepool do that. | 16:32 |
| mmedvede | robcresswell: do you have a good image, and it is just missing java? | 16:32 |
| robcresswell | mmedvede: Yup | 16:33 |
| mmedvede | you can either do it during image build (it seems current upstream project-config element does not do that, so you could create your own custom element to install java, or fix upstream) | 16:34 |
| mmedvede | Or, you can install java on nodepool boot, with 'ready-script' | 16:34 |
| robcresswell | So, is -infra still using Jenkins? Or just zuul v3? | 16:35 |
| * robcresswell is confused by things. | 16:35 | |
| mmedvede | jenkins is in name only, I believe | 16:35 |
| mmedvede | but there is no jenkins server | 16:36 |
| mmedvede | the "jenkins" username was kept just because it is easier to keep the same username | 16:36 |
| mmedvede | I could be wrong | 16:36 |
| robcresswell | Oh right, so upstream *is* zuulv3? | 16:36 |
| mmedvede | not yet, zuul2.5 | 16:36 |
| mmedvede | fungi: correct me if I am wrong please | 16:37 |
| * robcresswell is even more confused. | 16:37 | |
| robcresswell | I thought Jenkins was still needed in a pre-zuulv3 world | 16:37 |
| mmedvede | they use ansible runners | 16:37 |
| *** persia has joined #openstack-third-party-ci | 16:38 | |
| mmedvede | But I was not following the most recent changes closely | 16:38 |
| mmedvede | but the fact that the name "jenkins" is still around makes it confusing, yes :) | 16:38 |
| robcresswell | Okay | 16:38 |
| sambetts | I didn't relise that zuul pre-v3 could operate without jenkins | 16:38 |
| mmedvede | I am not sure what to recommend, I almost feel like it would be better to wait for v3 to be a bit more tested, and base your third-party CI on that | 16:42 |
| sambetts | mmedvede: are these ansible runners avaible for us to use in 3rd party CI? and get rid of jenkins? | 16:42 |
| robcresswell | mmedvede: Waiting is not really an option | 16:42 |
| mmedvede | because right now if you spend time with jenkins+nodepool, you'll be kind of wasting it if you would later be switching to v3 | 16:42 |
| mmedvede | sambetts: I am not aware of any third-party CI that use ansible runner | 16:42 |
| robcresswell | Well, v3 won't be available for at least a few months, and then likely have issues | 16:42 |
| mmedvede | yeah | 16:43 |
| mmedvede | So if you would want to use jenkins + nodepool, you got to use elements in the older checkout of project-config | 16:44 |
| fungi | mmedvede: correct, upstream zuul.openstack.org is continuously deployed from the master branch of zuul and uses an experimental ansible-launcher feature instead of relying on jenkins, but using jenkins with the latest releases of zuul (e.g. 2.5.2) is still intended to be supported and the recommended deployment configuration | 16:49 |
| fungi | we have a preliminary zuulv3.openstack.org deployment running from the feature/zuulv3 branch tip where we're trying to finish getting it functional and ready to start using in production in a few weeks, but that's still an unsupported beta basically | 16:50 |
| fungi | once zuul 3.0.0 is released, we don't intend to support the experimental ansible-launcher that's part of zuul 2.5.x, since that was just a stop-gap for us | 16:52 |
| mmedvede | thanks for the clarification, so using ansible-launcher is a bad idea for third-party CI. Either got to stick with jenkins, or wait for v3 | 16:53 |
| fungi | so upstream zuul recommendation would be to deploy 2.5.2 with jenkins for now, and look at the tools we provide for migrating to zuul 3.x once we have 3.0.0 released and in production | 16:53 |
| fungi | we want to be able to support people switching from 2.x+jenkins to 3.x, but can't really easily support 2.x+ansible-launcher | 16:54 |
| sambetts | fungi: the problme we're facing is that the https://github.com/openstack-infra/project-config/tree/master/nodepool/elements/jenkins-slave element doesn't seem to install java into our image, and without reverting to an older element still using puppet we're either going to end up creating a custom element or hacking java install into the ready script | 16:55 |
| fungi | but really, it's hard for us to provide migration recommendations/workflow/utilities for others until we've gone through getting 3.x working ourselves | 16:55 |
| fungi | sambetts: we use a very lightweight dib element to add packages we need, which should be pretty easy to adapt: http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/infra-package-needs | 16:57 |
| sambetts | fungi: yeah thats the element we're trying to modify to add java at the moment | 16:58 |
| fungi | you could either stick it into that package-installs.yaml file in a fork of that element, or make a similar element with a different name which just adds the packages you need that we aren't already including in the infra-package-needs element | 16:59 |
| fungi | might make sense to include in the project-config-example repo even | 17:00 |
| fungi | from a puppet-openstackci perspective | 17:00 |
| sambetts | yeah its not to bad to do now we know whats missing, we're just a little frustrated because we spent a good amount of time trying to work out what we were doing wrong compared to upstream because we thought you guys were still using jenkins so you must have been installing java somehow in the project-config elements | 17:01 |
| sambetts | and the jenkins-slave element in project-config seems to have been put in place for just the reason of providing the backwards compat for third party CI | 17:01 |
| *** krtaylor has quit IRC | 17:05 | |
| *** Sukhdev_ has quit IRC | 17:09 | |
| *** dmsimard has joined #openstack-third-party-ci | 17:14 | |
| dmsimard | another channel to idle in /o/ | 17:18 |
| mmedvede | :) | 17:22 |
| *** sambetts is now known as sambetts|afk | 17:32 | |
| *** Sukhdev_ has joined #openstack-third-party-ci | 17:54 | |
| *** xinliang has quit IRC | 18:26 | |
| fungi | sambetts|afk: i believe what happened there is that the jenkins::slave class never explicitly installed java, and after we stopped using jenkins we were still baking java into our images unnecessarily (for us) for a while which we eventually cleaned up not realizing that people still deploying the jenkins::slave class had been relying on it. one option might be to just add a package resource | 19:03 |
| fungi | to that puppet class | 19:03 |
| *** krtaylor has joined #openstack-third-party-ci | 19:08 | |
| *** Sukhdev_ has quit IRC | 19:48 | |
| *** krtaylor has quit IRC | 21:01 | |
| *** krtaylor has joined #openstack-third-party-ci | 21:04 | |
| *** esberglu has quit IRC | 21:48 | |
| *** esberglu has joined #openstack-third-party-ci | 21:48 | |
| *** Sukhdev_ has joined #openstack-third-party-ci | 21:49 | |
| *** esberglu has quit IRC | 21:53 | |
| *** esberglu has joined #openstack-third-party-ci | 22:12 | |
| *** Apoorva_ has joined #openstack-third-party-ci | 22:20 | |
| *** Apoorva has quit IRC | 22:23 | |
| *** krtaylor has quit IRC | 22:52 | |
| *** krtaylor has joined #openstack-third-party-ci | 23:40 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!