17:00:44 <tdawson> #startmeeting CentOS PaaS SIG
17:00:44 <centbot> Meeting started Wed Mar 15 17:00:44 2017 UTC.  The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:44 <centbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:49 * jdetiber waves
17:00:53 <tdawson> #topic roll call
17:00:57 <tdawson> Sorry for being a bit late.
17:01:11 <tdawson> still getting used to daylight savings.
17:01:32 * jdetiber is here
17:01:41 * kbsingh here too
17:01:43 * _ari_ here
17:01:52 * sdodson here
17:03:09 * herlo here
17:03:28 <tdawson> #chair tdawson sdodson _ari_ kbsingh jdetiber herlo
17:03:28 <centbot> Current chairs: _ari_ herlo jdetiber kbsingh sdodson tdawson
17:03:37 <tdawson> #topic OpenShift on CentOS Current Status
17:03:45 <tdawson> Starting with rpms
17:04:35 <tdawson> openvswitch-devel-2.6.1-3.git20161206.el7 has been added to future, regular common, and openshift-origin15 ... all in the testing areas
17:05:05 <tdawson> Since that is for 1.5 and above, it won't get pushed to the regular release until 1.5 is relesed.
17:05:28 <sdodson> tdawson: Awesome, thanks for getting to that so quickly.
17:06:15 <tdawson> sdodson: My biggest issue was that the cloud sig had already built it, and I wasn't paying attention to the cbs errors.  In the end I just tagged their version in.
17:06:54 <tdawson> I don't have any other rpm news, unless someone else has some.
17:07:38 <tdawson> Well, I guess minishift will be some news, but that is later on the agenda.
17:07:56 <tdawson> Moving on to Documentation
17:08:40 <tdawson> kbsingh: Were you able to get any of those docs ... and now I can't remember what they were ... created.
17:09:46 <tdawson> Anyway, I don't see anything new for documentation.
17:10:03 <tdawson> Moving on to Automated rpm building and testing
17:10:11 <tdawson> _ari_: herlo: Any news on that front?
17:10:44 <_ari_> tdawson: talked more with skuznets this week I will be updating the jobs today now that the infrastructure is back up on centos CI
17:11:09 <tdawson> Ya!! ... for both updated jobs and infrastructure.
17:11:11 <_ari_> tdawson: I need to test my changes and then we should have things in place for future and release
17:12:04 <tdawson> Cool
17:12:22 <_ari_> tdawson: that is all I have
17:12:44 <tdawson> _ari_: Does a week seem reasonable before things are in place?
17:13:13 <_ari_> tdawson: should be I will know better at the beginning of next week
17:13:24 <tdawson> OK, sounds great.
17:13:38 <tdawson> And once again, thanks to you, and herlo, for all your work.
17:13:50 <tdawson> Moving on to images and image building.
17:13:51 <_ari_> tdawson: np
17:14:19 <tdawson> I know there was an infrastructure outage/update ... so I'm suspecting they were down.
17:14:39 <tdawson> kbsingh: Anything to report about images and or image building?
17:15:46 <tdawson> While kbsingh makes it back to us, I'm going to move forward.
17:15:56 <tdawson> Multi-Arch
17:16:22 <tdawson> How do people feel about moving our "future" target to be multi-arch, at least build aarch64
17:17:17 <kbsingh> not a lot happening in the image building side
17:17:26 <kbsingh> i believe 1.3 and 1.4 images are live on the registry
17:17:41 <kbsingh> I'm +1 for alt arch support
17:17:44 <jdetiber> tdawson: no objections from me
17:17:46 <tdawson> I'd like to also get ppc53le as a build target too, but I figured we'd start with just one extra arch to start.
17:18:17 <tdawson> kbsingh: I assume I'd just create a ticket for that?  Or should I ping someone as well?
17:18:52 <tdawson> /ppc53le/ppc64le/
17:20:20 <kbsingh> alphacc is your man for that
17:20:37 <tdawson> kbsingh: OK, I'll do both.
17:20:41 <kbsingh> do you know yet if you are going to add more tag's to keep the arch specific problems isolated
17:20:51 <kbsingh> r do you want to extend the existing tag's to include other arch's as well
17:21:13 <kbsingh> that way an arch fail causes your entire job to fail
17:21:19 <tdawson> kbsingh: I was thinking of just using our future tag
17:21:23 <kbsingh> ok
17:21:42 <kbsingh> that might mean you need to check and ensure the docker / kube story is well unified
17:22:15 <tdawson> kbsingh: With out new "each release has it's own tag" way of doing things, we should be able to do our next releases into their own targets/tags/
17:22:30 <tdawson> Which leaves future for really future stuff, like multi-arch
17:22:56 <tdawson> Which brings us to our next subject, the seperate repo work.
17:23:13 <sdodson> Clayton asked if we could have this, he's getting ready to tag the first 3.6 alpha
17:23:36 <tdawson> We've got the new tags and we can build into them.  But when I tag things into -testing, it never makes it there.
17:24:19 <tdawson> sdodson: Cool, well that give me ever more incentive ... I'll make sure I get the ticket created today.
17:25:24 <tdawson> kbsingh: Isn't this where I should expect the things like the openshift-origin14 to be at https://buildlogs.centos.org/centos/7/paas/x86_64/ ?
17:25:41 <sdodson> tdawson: He says he wants it to mirror the OCP channels, but I think we can skip all the s2i dependencies. As those are all legacy from when openshift built s2i images, now those are all RHSCL images.
17:26:08 <kbsingh> tdawson: that is
17:26:38 <kbsingh> tdawson: i think bstinson and Arrfab have been busy with the DC move these last few days, they just need to create the entries and it should stay flowing
17:26:39 <tdawson> kbsingh: OK, I guess I'll need to ping alphacc on that as well.
17:26:47 <jdetiber> tdawson: sdodson: would it be worth it to try and push the image building deps to a separate repo as well?
17:26:50 <tdawson> kbsingh: OK
17:27:20 <jdetiber> tdawson: sdodson: always seemed odd to me for us to ship the image building deps in our main repos for the product
17:27:34 <tdawson> jdetiber: Well, the metrics and logging stuff, I thought was in a different Paas
17:27:51 <tdawson> jdetiber: And possibly for the jenkins images as well.
17:28:01 <jdetiber> ah, that might be the case
17:28:33 <tdawson> jdetiber: sdodson: If we can have their paas provide the metrics and logging rpms and stuff, that would go a long way to keeping our repo's clean.
17:28:57 <sdodson> what do we mean differen PaaS?
17:28:58 <tdawson> The vast vast majority of the rpms in the OCP channels are for metrics and logging.
17:29:39 <tdawson> sdodson:  https://wiki.centos.org/SpecialInterestGroup/OpsTools
17:30:02 <sdodson> tdawson: ahh, ok
17:30:14 <tdawson> sdodson: They meeting right after this meeting.
17:31:52 <tdawson> Talking about different groups/products ... lalatenduM ... how is MiniShift on CentOS doing?
17:32:30 <tdawson> lalatenduM: Sent a very good email to centos-devel ... I was just wondering if he wanted to give an update during the meeting.
17:34:16 <kbsingh> might be a bit late for him
17:34:27 <tdawson> Ya, I guess I'll give a summary
17:35:10 <tdawson> Umm ... he's working on getting minishift into the Paas repo's. :)  He also sent the 1.0.0-beta5 release notes.
17:35:24 <kbsingh> jdetiber: w.r.t things like jenkins etc, we should certainly work that out - also, I've been looking for the most popular deps and quickstarts to get them all building in the container pipelines
17:35:34 <tdawson> I guess the last thing we have is Open Floor
17:35:41 <tdawson> #topic Open Floor
17:35:51 <tdawson> Does anyone have anything to discuss that wasn't on the agenda?
17:36:19 <sdodson> tdawson: skuznets would like the l atest docker and container-selinux from brew in cento paas sig repos for CI jobs.
17:36:40 <marcindulak> I have: yesterday I responded to lalatenduM email: https://lists.centos.org/pipermail/centos-devel/2017-March/015724.html - any hints how can I help?
17:36:47 <sdodson> tdawson: I assume that means we'd need to get them re-built via CBS? I don't know if maybe we can push lsm5 to handle this?
17:37:19 <tdawson> sdodson: I guess it depends on what he means by "latest"
17:37:42 <tdawson> sdodson: If it's the latest released, then I think we should wait for the main CentOS extras to have them.
17:38:11 <tdawson> sdodson: If it's newer than that, we'll have to build it ourselves.
17:38:14 <lsm5> sdodson: sorry, what exactly you looking for?
17:38:16 <sdodson> tdawson: unfortunately it's the latest internal rhel builds that he's after, though maybe there's some way to build directly from projectatomic github?
17:38:19 <tdawson> marcindulak: Hi, and welcome
17:38:37 <tdawson> marcindulak: I saw your reply to lalatenduM's email
17:38:55 <sdodson> lsm5: skuznets wants latest internal rhel builds rebuilt for centos paas sig future repo, or some other equivalent that he can install which matches the versions you build for rhel
17:39:12 <tdawson> marcindulak: At the moment, he's been the spearhead for that, so I'm not sure what work he needs help with.
17:39:52 <lsm5> sdodson: any reason the fedora builds won't do? I'm already doing fedora rawhide rebuilds for Virt SIG
17:40:12 <tdawson> marcindulak: He's here at this meeting about 50% of the time, but as was said earlier, it's fairly late for him.
17:40:13 <sdodson> lsm5: Are they for EL7 what's the delta between those and rhel builds?
17:40:13 <lsm5> sdodson: i can check with skuznets on that
17:40:25 <sdodson> lsm5: ok, that'd be great, i feel like a middleman here
17:40:32 <lsm5> sdodson: cool, np
17:41:04 <tdawson> lsm5: sdodson: If he just needs some of those builds tagged into future, that shouldn't be much of a problem.
17:42:51 <sdodson> tdawson: that may be it, will see what lsm5 says after discussing with skuznets
17:44:02 <sdodson> no more questions from me :-)
17:44:48 <tdawson> anything else before we close this meeting?
17:45:01 <kbsingh> i have 1 thing
17:45:04 <kbsingh> same thing as last time
17:45:13 <kbsingh> the atomic installer is still unable to deploy a working openshift origin cluster
17:45:29 <kbsingh> one easy fix is that it needs python-six as a dependancy
17:46:03 <kbsingh> but even beyond that, i think the ansible bits under the hood need a bit of tweaking
17:46:11 <kbsingh> whats the best way to work through this
17:47:01 * tdawson checks repos to see if we have python-six
17:47:17 <kbsingh> should be in base
17:47:51 <jdetiber> ansible should pull in python-six, I'm wondering if the issue is related to python-six on the remote host, which should be fixed now
17:48:14 <jdetiber> well, maybe not...  they might just use the vendored versions...
17:48:31 <jdetiber> but latest spec updates should have python-six as a dep for the installer
17:51:06 <tdawson> Yep ... I'm seeing that even our version should be pulling in python-six - https://cbs.centos.org/koji/rpminfo?rpmID=86055
17:51:15 <sdodson> kbsingh: what's the best way for us, in the specfile to make something conditional if we're building on centos?
17:51:25 <sdodson> kbsingh: regarding enabling origin in the quick installer or not
17:51:45 <jdetiber> tdawson: the issue could very well have been related to when we weren't installing python-six on the remote hosts when needed
17:51:58 <jdetiber> tdawson: should be fixed in master now at least
17:52:06 <tdawson> jdetiber: OK
17:55:27 <tdawson> OK, looks like things have quieted down, and the next meeting is about to start, so I'm going to wrap things up.
17:55:52 <tdawson> I'll send out meeting notes.
17:56:05 <tdawson> I'll talk to ya'll next week.
17:56:29 <tdawson> #endmeeting