15:01:59 <amoralej> #startmeeting RDO meeting - 2018-05-30
15:02:00 <openstack> Meeting started Wed May 30 15:01:59 2018 UTC and is due to finish in 60 minutes.  The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:04 <openstack> The meeting name has been set to 'rdo_meeting___2018_05_30'
15:02:09 <amoralej> #topic roll call
15:02:14 <amoralej> #chair mjturek
15:02:15 <openstack> Current chairs: amoralej mjturek
15:02:22 <ykarel> o/
15:02:24 <PagliaccisCloud> \o
15:02:38 <amoralej> #chair ykarel PagliaccisCloud
15:02:39 <openstack> Current chairs: PagliaccisCloud amoralej mjturek ykarel
15:05:02 <amoralej> if you have any topic, please add it to https://etherpad.openstack.org/p/RDO-Meeting
15:07:06 <amoralej> i'm giving some more minutes for people to join or i'll move to open floor
15:08:25 <PagliaccisCloud> are meetings apropos for discussing rumors?
15:09:01 <amoralej> PagliaccisCloud, let's not leave rumors written :)
15:09:02 <chandankumar> \o/
15:09:08 <amoralej> #chair chandankumar
15:09:09 <openstack> Current chairs: PagliaccisCloud amoralej chandankumar mjturek ykarel
15:09:37 <amoralej> ok, no topics in the agenda
15:09:59 <amoralej> so let's move to open floor
15:10:06 <amoralej> #topic open floor
15:10:18 <amoralej> anyone has anything to bring?
15:10:26 <PagliaccisCloud> SUMMIT WAS AWESOME
15:10:28 <PagliaccisCloud> :D
15:10:38 <amoralej> cool! anything to remark?
15:11:21 <mjturek> yeah me PagliaccisCloud and number80 helped with the booth. I had one or two questions about RDO which I did my best with
15:11:55 <mjturek> it was fun!
15:13:02 <amoralej> i'm sure you did a good job with it
15:13:26 <PagliaccisCloud> i seen't it. he did great
15:14:05 <mjturek> as did PagliaccisCloud !
15:14:30 <amoralej> what was the hot topic in people in the booth?, in openstack booth in fossdem, people was very interested in kubernetes and openstack integration
15:15:21 <mjturek> so my demo was on ironic, and there was interest in TPM support there
15:15:30 <PagliaccisCloud> i got some openshift integration questions
15:16:28 <amoralej> mjturek, was your demo recorded?
15:16:41 <mjturek> it was!
15:17:24 <mjturek> amoralej: I hope to upload it to youtube, but want to scrub through to make sure I'm censoring any sensitive info
15:17:36 <amoralej> ok, cool, i'd like to see it
15:19:08 <mjturek> cool!
15:19:21 <mjturek> I will let you know when I do
15:19:28 <amoralej> yes, please
15:21:09 <amoralej> anything else for open floor?
15:21:16 <amoralej> one from me
15:21:21 <mjturek> so I hate to keep bringing this patch up https://review.rdoproject.org/r/#/c/13606/ but I'm struggling with how to proceed here. If anyone can take a look and advise, I'd appreciate it
15:21:52 <amoralej> let me check
15:22:35 <PagliaccisCloud> WAY over my head but i'll try to help :p
15:22:49 <rdogerrit> Merged rdo-infra/rdo-container-registry master: Temporarily openshift_pkg_version against 3.7  https://review.rdoproject.org/r/13940
15:22:53 <mjturek> https://lists.rdoproject.org/pipermail/dev/2018-May/008711.html
15:22:59 <mjturek> last message in the chain about it ^
15:23:00 <amoralej> mjturek, so, we don't have ppc64le nodes
15:23:38 <mjturek> amoralej right, dmsimard mentioned using cico? does that sound doable for this?
15:23:55 <amoralej> i'm reading the thread
15:25:07 <amoralej> mjturek, so, the point is that we can't use ppc64le from zuul and nodepool in review.rdoproject.org
15:25:16 <amoralej> they are in ci.centos.og
15:25:18 <amoralej> org
15:25:45 <mjturek> right
15:25:50 <amoralej> so my understanding is that what we need is to build the containers in jobs running in ci.centos.org
15:26:05 <amoralej> we configure those jobs using jjb in http://github.com/rdo-infra/ci-config
15:26:23 <mjturek> looking
15:26:37 <amoralej> and from there we requests nodes using cico and use tipically ansible
15:26:42 <amoralej> let me look for an example...
15:26:59 <mjturek> hmmm are there container builds happening there as well?
15:27:25 <amoralej> no
15:27:42 <amoralej> currently, we build the containers for x86_64 in zuul
15:27:45 <mjturek> so it would be a unique job for ci.centos.org
15:27:49 <amoralej> yeah
15:28:00 <amoralej> although you can reuse the existing ansible role for it
15:28:10 <mjturek> ahhh okay
15:28:11 <amoralej> you are using kolla with tripleo-common for overrides to build them?
15:29:13 <mjturek> amoralej: we haven't built the containers (at least through a jenkins job) before
15:29:21 <mjturek> so I'm not sure
15:29:31 <amoralej> have you do local tests?
15:29:40 <amoralej> or something to check if it works fine?
15:29:54 <mjturek> someone on the team has, not me personally. Yes I believe they build fine
15:29:54 <amoralej> this is a script we use to request a node to cico https://github.com/rdo-infra/ci-config/blob/master/jenkins/jobs/scripts/cico-node-get-to-ansible.sh
15:29:58 <amoralej> ok
15:30:28 <mjturek> okay cool!
15:31:08 <amoralej> you'll need something to get ppc64le
15:31:11 <amoralej> but i'm not sure
15:31:32 <mjturek> amoralej: if we were able to get Power hardware specifically to introduce into the RDO cloud, would that be a simpler path?
15:31:48 <mjturek> I can talk to my manager and see if that's something we can do
15:32:10 <mjturek> but if cico seems like the better approach, we can continue this way
15:32:31 <amoralej> yeah, i think it's the best we can do
15:32:54 <amoralej> as said, once you have a way to get a proper node
15:33:28 <amoralej> reusing the ansible role in https://github.com/rdo-infra/ansible-role-rdo-kolla-build should be easy
15:33:29 <mjturek> okay understood, so my todo is to figure out how to get a node from cico
15:33:42 <mjturek> for that ansible role
15:34:05 <amoralej> you can start running it without push
15:34:12 <amoralej> just to check that you can build containers
15:34:21 <amoralej> and then push them
15:34:37 <mjturek> sounds good
15:34:41 <amoralej> mjturek, do you wan to push the containers somewhere?
15:34:58 <mjturek> ideally we want to push them to the same place the x86_64 containers go
15:35:02 <mjturek> which I think is docker hub?
15:35:08 <amoralej> yeah
15:35:17 <amoralej> we temporarily push them to RDO registry
15:35:21 <mjturek> yeah
15:35:30 <amoralej> just as an intermediate step until we validate it, iiuc
15:35:39 <amoralej> then to docker hub
15:35:53 <mjturek> gotcha
15:35:58 <amoralej> i'm not sure if we can have conflicts in namespaces and container names
15:36:16 <amoralej> or different arches have separated namespaces or something
15:36:34 <amoralej> i have no experience at all with containers out of x86_64 world
15:36:37 <mjturek> a ppc64le suffix would work? I guess I'd need to look closer at the containers
15:37:21 <mjturek> anyway amoralej this sounds like a path forward
15:37:36 <amoralej> yeah, i hope it helps to move on
15:37:45 <mjturek> I think it will, thanks!
15:38:12 <amoralej> good luck with it! :)
15:38:19 <mjturek> thanks :)
15:40:50 <amoralej> any volunteer to chair this meeting next week?
15:41:52 <PagliaccisCloud> i can't do it next week - but can anyone volunteer or is it for red hat employees only?
15:42:08 <amoralej> PagliaccisCloud, of course you can
15:42:25 <amoralej> anyone involved in RDO Community can do it
15:42:26 <amoralej> thanks
15:43:16 <PagliaccisCloud> :D cool
15:43:18 <amoralej> oh, you can't do it next week :D, i misread it first time
15:44:23 <amoralej> so, it seems we don't have any volunteers today?, i will take it, then
15:44:31 <mjturek> amoralej I can!
15:44:37 <amoralej> thanks mjturek
15:44:38 <mjturek> sorry was afk\
15:44:40 <amoralej> no prob
15:44:54 <amoralej> #info mjturek will chair the meeting next week
15:45:12 <amoralej> so, if there are no other topics for open floor i'll close the meeting
15:45:21 <amoralej> and give you 15 minutes back
15:45:32 <mjturek> thanks amoralej ttyl!
15:45:54 <amoralej> ok
15:45:56 <amoralej> so
15:45:57 <amoralej> 3
15:45:58 <amoralej> 2
15:46:04 <ykarel> 1
15:46:10 <PagliaccisCloud> LIFTOFF
15:46:10 <amoralej> :)
15:46:12 <amoralej> wclosing
15:46:24 <amoralej> #endmeeting