17:00:13 <tdawson> #startmeeting CentOS PaaS SIG
17:00:13 <centbot> Meeting started Wed Aug  2 17:00:13 2017 UTC.  The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:13 <centbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:20 <tdawson> #topic roll call
17:00:30 <kbsingh> hello
17:00:41 <tdawson> Hi kbsingh
17:01:16 * _ari_ here
17:01:16 * jdetiber waves
17:01:28 <tdawson> Hi _ari_ and jdetiber
17:04:43 <sdodson> hello
17:04:54 <tdawson> Hi sdodson
17:05:23 <tdawson> #chair tdawson jdetiber sdodson _ari_ kbsingh
17:05:23 <centbot> Current chairs: _ari_ jdetiber kbsingh sdodson tdawson
17:05:29 <tdawson> #topic OpenShift on CentOS Current Status
17:05:42 <tdawson> Starting with rpms
17:06:05 <tdawson> Origin relesed 3.6.0 this past week.
17:06:23 <tdawson> We're currently working on getting it built.
17:06:36 <jdetiber> tdawson: awesome work as always
17:07:11 <tdawson> jdetiber: Well, I haven't gotten it built ... and we're going to try to get it built with the jenkins server ... so no congratulations yet.
17:07:45 <jdetiber> heh
17:08:33 <tdawson> Looks like we're having some version issues ... and I'm really just saying that to sound smart.  _ari_ said there were some version issues. :)
17:08:52 <_ari_> tdawson: this is a candidate build so this job must be used  https://ci.centos.org/job/paas-bfs-candidate-matrix/
17:09:30 <jdetiber> _ari_: anything I can help with on the version issues?
17:09:36 <_ari_> the future one was set to 3.7 for some reason for both origin and openshift-ansible
17:10:09 <_ari_> jdetiber: we will need an automatic way to monitor version updates and just use them for the playbooks
17:10:10 <jdetiber> _ari_: I set the future one to 3.7, since master is now on track to be 3.7, and was working through some build issues there
17:10:27 <tdawson> _ari_: Oh, you missed that while you were gone.  Master has switched to 3.7, so we ( jdetiber ) tried to switch the future to 3.7 ... what jdetiber said.
17:10:36 <_ari_> jdetiber: but I don't think that would just work for CBS in doig scratch or official builds
17:10:51 <_ari_> but doesn't CBS have to be aware of that
17:11:13 <tdawson> We got the 3.7 build targets created last week as well.
17:11:15 <_ari_> also that is not a release that is master future stuff so that wouldn't help you in building the release
17:11:31 <_ari_> tdawson: well it seems to be failing in CBS from the link I sent you
17:11:39 <jdetiber> correct, was not intended to affect the candidate job
17:12:40 * jdetiber is looking at the failed candidate job now
17:12:52 <_ari_> jdetiber: tdawson ok for future the failure was in CBS https://ci.centos.org/job/paas-bfs-future-matrix/PYTHON=system-CPython-2.7,TOPOLOGY=duffy_3node_cluster,nodes=paas-sig-ci-slave01/180/console
17:13:06 <_ari_> https://cbs.centos.org/koji/taskinfo?taskID=201725
17:13:30 <_ari_> jdetiber: tdawson so that seems to be the culprit unless there is something to change when I build with CBS
17:13:56 <jdetiber> _ari_: as an aside the output from running the build scripts/tests with ansible is pretty horrible to read
17:14:34 <_ari_> jdetiber: feel free to make it look better if you want to update the playbooks
17:14:51 <_ari_> https://github.com/CentOS-PaaS-SIG/paas-sig-ci
17:16:41 <tdawson> _ari_ I don't know what your schedule is like, but I have some non-crazy busy time this afternoon ... did you want me to work on getting the candidate builds working, or do you think you've already got it?
17:17:07 <_ari_> tdawson: it is running now https://ci.centos.org/job/paas-bfs-candidate-matrix/11/PYTHON=system-CPython-2.7,TOPOLOGY=duffy_3node_cluster,nodes=paas-sig-ci-slave01/console
17:17:37 <_ari_> jdetiber: is there something to make the ansible output cleaner I was able to see the issue pretty easily
17:18:09 <tdawson> _ari_ Cool ... that's great.
17:18:38 <_ari_> tdawson: keep in mind someone has to kick the candidate job for a release and make it non-scratch
17:18:46 <jdetiber> _ari_: not that I'm aware of, but maybe just adding colored output would help
17:19:00 <tdawson> _ari_: OK, I think I can do that.
17:19:32 <_ari_> jdetiber: weird it should have ansicolor on but let me check the setting
17:20:42 <tdawson> So, I'm goign to summarize, at least on the rpm side.  We're currently working on origin and openshift-ansible 3.6 builds.  They will hopefully be done today.
17:20:51 <jdetiber> _ari_: might be ansible not outputting ansi output as well, I think there is a config setting for that
17:21:11 <tdawson> When they are we'll give them very basic tests (will they install) and tag them into -testing.
17:22:09 <tdawson> I'll send out an email when they are in testing, and by beginning of next week, if they've passed all our tests, we'll tag them into release and out they go.
17:23:05 <tdawson> _ari_:  I know we've already talked a bunch about automation while we were talking about rpms, did you have anything else to add for automation?
17:23:09 <_ari_> tdawson: cool I will monitor the jobs and let you guys know what happens I believe you should get email as well
17:23:30 <tdawson> Yep, I usually get the emails, I haven't filtered them yet.
17:23:42 <_ari_> tdawson: no my plan is to make the candidate releases automatic, convert to Jenkins Pipeline, re-enable e2e tests
17:24:26 <tdawson> _ari_: Sounds good.  I know you just got back from some time off, do you have any type of estimate for that?
17:24:35 <tdawson> time estimate I mean
17:25:09 <_ari_> tdawson: probably next couple of weeks
17:25:48 <tdawson> OK, moving on to multi-arch
17:26:00 <tdawson> jdetiber: How are we doing on multi-arch ?
17:26:40 <bstinson> probably still waiting on me somewhat. i'm making progress
17:27:27 <jdetiber> I've been slowly making progress on the internal pipeline, so not completely held up on bstinson :)
17:27:49 <tdawson> jdetiber: What are your thought for us turning aarch64 on the normal builds (3.7) ?
17:27:52 <kbsingh> what are the main holdups ? just the arch machine availability in ci ?
17:28:30 <jdetiber> kbsingh: and also landing some dev tooling changes, and the pipeline work
17:28:55 <kbsingh> is this documented somewhere ? what dev tooling changes are needed ?
17:29:45 <jdetiber> kbsingh: I can dig up the PR #'s, but they wouldn't affect post-rpm testing, only pre-build testing
17:30:57 <jdetiber> tdawson: only worry I'd have there is that any testing for aarch64 would be manual still and I wouldn't want to hold up x86_64 candidates for that
17:31:05 <kbsingh> ok
17:31:14 <tdawson> jdetiber: That's a good point.
17:31:29 <jdetiber> kbsingh: https://github.com/openshift/origin/pull/14938 is the PR for master/3.7
17:32:12 <kbsingh> jdetiber: ack
17:33:16 <tdawson> Anything else for multi-arch?
17:33:35 <jdetiber> not unless there is any updates from kbsingh or bstinson on s390x
17:33:56 <kbsingh> not from my side no
17:34:31 <tdawson> OK then, moving on to Documentation
17:34:47 <tdawson> I don't have anything new for Documentation
17:35:17 <tdawson> I was going to wait for 3.6 release before going over all the docs again, although last time they all looked fairly generic and didn't need any updating.
17:36:05 <tdawson> Moving on to Images and Image building
17:36:43 <tdawson> I introduced mzee1000 and bamachrn to skuznets during the week.
17:37:10 <tdawson> mzee1000 is moving ahead with the Dockerfile.centos work, from what I can tell from the email exchanges.
17:37:34 <kbsingh> thats what it looked like to me as well, from the emails i was on
17:38:47 <tdawson> This is something I'm very grateful for
17:39:05 <tdawson> kbsingh: Please tell him / them (if it's a group effort) thanks from me.
17:39:14 <kbsingh> willdo!
17:39:26 <tdawson> kbsingh: Is there anything else we need to discuss about images this week?
17:39:50 <kbsingh> one thing is that the container build guys are now talking into the atomic SIG as well
17:40:04 <kbsingh> so there will be some cross pollination through there, which should be good
17:40:22 <tdawson> Very good
17:40:33 <kbsingh> nothing else
17:40:48 <tdawson> Well then, moving on.
17:41:14 <tdawson> lalatenduM: Anything new on the minishift front that you want to talk about at the Paas SIG meeting?
17:41:58 <tdawson> tkral: Anything new with kompose that you want to talk about at the Paas SIG meeting?
17:42:16 <tdawson> I'll give them a minute or two to respond before moving on to Open Floor.
17:44:05 <kbsingh> i think they are both victims of timezone
17:44:51 <tdawson> Yep
17:45:00 <tdawson> OK, moving on to Open Floor
17:45:09 <tdawson> #topic Open Floor
17:45:48 <jdetiber> I'm working on a higher level document for the pipeline work that I'm doing to try and bridge the PaaS SIG, Fedora, and internal efforts
17:46:04 <tdawson> I have one thing.  My replacement has finally been hired.  So it's possible that I might be able to step down as chairman at some forseeable future.
17:46:10 <tdawson> jdetiber: awesome
17:46:15 <jdetiber> Also trying to integrate with the work Ari is doing on atomic CI as well as the fedora-next work
17:46:27 <kbsingh> sounds good
17:46:39 <kbsingh> i know there is interest in having cico client be usable from a Jenkinsfile / pipeline as well
17:46:44 <tdawson> The bad new I have is that when I talked to my replacement, he hadn't heard anything about the SIG.  The good news is he didn't run away screaming. :)
17:46:49 <jdetiber> Hoping to have a external project page ready to start gathering feedback from the communities next week
17:46:49 <kbsingh> would be great to see that work come together with whatyou are doing jdetiber
17:47:08 <kbsingh> unfortunately, i just dont have the time in day to get this done - although i cant imagine it being more than a few hrs ( cico in jenkinsfiles )
17:47:40 <bstinson> that work will be happening here: https://github.com/CentOS/cico-pipeline-library
17:47:42 <jdetiber> kbsingh: with all the efforts in place from different places is the exact reason I want to do this as an external project and gather feedback from all the other groups :)
17:48:07 <kbsingh> +1
17:48:08 <jdetiber> tdawson: great news about your replacement, though you will be highly missed :)
17:49:31 <bstinson> jdetiber: if you're writing pipeline libs, care to send some PRs there? _ari_ and vpavlin are going to put some things up there also
17:49:49 <bstinson> note: this just got done...so we don't have a structure or a readme yet
17:50:13 <jdetiber> bstinson: so far I haven't written any separate libs, but will definitely keep that in mind
17:50:45 <_ari_> jdetiber: we plan have this for cico so we can add libs for reuse
17:51:52 <jdetiber> _ari_: good to hear
17:52:10 <kbsingh> bstinson: cool!
17:52:28 <kbsingh> unsure if we want to let tdawson go actually.
17:53:15 <tdawson> kbsingh: I'll probrubly still be around, and I'm sure this will take a several months
17:53:17 <kbsingh> bstinson: _ari_: if the very first PR isnt setting up a Jenkinsfile for the git repo itself, i am going to be disapointed.
17:53:30 <jdetiber> kbsingh: maybe we can convince tdawson to stick around, just not as chair :)
17:53:36 <kbsingh> jdetiber: +1
17:53:58 <tdawson> But my new job is taking more and more of my time, and I'm not as in touch with origin as I used to be.
17:53:59 <jdetiber> _ari_: oh, I did want to ask about the process for updating the jenkins jobs from the repo
17:54:23 <_ari_> kbsingh: well this isn't for a pipeline this is for libs only
17:54:46 <_ari_> kbsingh: or do you mean a pipeline to test the libs
17:55:01 <_ari_> jdetiber: in which repo
17:55:11 <tdawson> We're still manually tagging the packages from -candidate to -testing to -release
17:55:17 <jdetiber> It would be kind of cool to deploy and update the libs using a jenkins pipeline :)
17:55:37 <jdetiber> _ari_: paas-sig-ci
17:56:28 <bstinson> ^for that, can we do a service job for you?
17:56:33 <_ari_> jdetiber: I run this locally to update but will add a service job that when jobs are changed in the repo then they get updated automatically
17:56:42 <_ari_> I was not doing that since we are going to move to pipelines
17:56:52 <_ari_> bstinson: that would be great
17:56:56 <_ari_> jdetiber: ^^^
17:57:03 <kbsingh> _ari_: yeah, first PR -> setup the test infra, PR 2 -> write tests, PR 3 -> write code :)
17:57:05 <jdetiber> bstinson: _ari_: awesome!
17:57:53 <bstinson> ok, i'll take the action to do a managed service job on https://github.com/CentOS-PaaS-SIG/paas-sig-ci
17:58:03 <_ari_> kbsingh: I will see what I can do I am not a groovy expert I will see how fabric8 did it
17:58:13 <_ari_> gotta run guys
17:58:19 <tdawson> _ari_: Bye
17:58:25 <jdetiber> _ari_: thanks! Have a good one
17:58:27 <tdawson> And, it looks like we're getting to the end of our time
17:58:51 <tdawson> It's been a great meeting ... I'll talk to ya'll next week.
17:59:19 <tdawson> #endmeeting