15:00:14 #startmeeting RDO meeting - 2018-06-06 15:00:14 Meeting started Wed Jun 6 15:00:14 2018 UTC. 15:00:14 This meeting is logged and archived in a public location. 15:00:14 The chair is mjturek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:14 The meeting name has been set to 'rdo_meeting_-_2018-06-06' 15:00:15 Meeting started Wed Jun 6 15:00:14 2018 UTC and is due to finish in 60 minutes. The chair is mjturek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:18 The meeting name has been set to 'rdo_meeting___2018_06_06' 15:00:26 Hey everyone it's time for the RDO meeting 15:00:31 hi 15:00:38 #chair mjturek amoralej 15:00:38 Current chairs: amoralej mjturek 15:00:39 Current chairs: amoralej mjturek 15:00:41 o/ 15:00:51 #topic roll call 15:00:56 #chair jpena 15:00:56 Current chairs: amoralej jpena mjturek 15:00:57 Current chairs: amoralej jpena mjturek 15:01:21 anyone else here for the meeting? 15:01:56 o/ 15:02:00 o/ 15:02:14 #chair leanderthal number80 15:02:14 Current chairs: amoralej jpena leanderthal mjturek number80 15:02:15 Current chairs: amoralej jpena leanderthal mjturek number80 15:02:29 awesome! let's move to the first topic on today's agenda https://etherpad.openstack.org/p/RDO-Meeting 15:02:43 #topic Test Day Prep 15:03:06 leanderthal: this was you right? 15:03:12 mjturek, the first one is sort of mine, sort of everyone's - that's the promotion; that we'll be green for test days next thursday 15:03:28 ahhh okay looks like Newton promotion is red? 15:04:00 newton is mostly dead 15:04:01 afaik, the only one we *really* care about for test days is the master 15:04:14 and then queens 15:04:18 we haven't promoted in two days... 15:04:18 and then pike 15:04:19 got it, Master RDO is currently yellow 15:04:27 so, no, we don't care about newton 15:04:44 yuppers; does anyone know why? and whether we'll be green for next week? 15:05:06 but most current run is green, maybe it's from that period of red last week? 15:05:51 i'm trying to find out 15:05:58 thx amoralej 15:06:28 it has failed in containers build 15:07:26 amoralej: can you link to the failed build? 15:07:26 is someone working on it? 15:07:42 https://review.rdoproject.org/jenkins/job/periodic-tripleo-centos-7-master-containers-build/981/ 15:08:25 #link https://review.rdoproject.org/jenkins/job/periodic-tripleo-centos-7-master-containers-build/981/ 15:08:42 I just found out I have a conflict (meeting fell off my calendar) can anyone take over? 15:08:58 mjturek, no worries 15:09:04 i'll take over 15:09:10 sorry :( 15:09:21 thanks leanderthal! 15:09:22 mjturek, be next week's chair to make it up to me 15:09:32 #info current blocker is https://bugs.launchpad.net/tripleo/+bug/1775199 15:09:34 Launchpad bug 1775199 in tripleo "Failure in tripleo undercloud install no such option collect_timing in keystone_authtoken group" [Critical,Triaged] 15:09:37 sure! 15:09:41 cool cool 15:09:51 awesome, amoralej - thanks for the info 15:10:38 oof; that bug isn't assigned, but it's also triaged, so... 15:10:39 it's the only known issue 15:10:48 someone is working on it 15:10:55 i'd expect to get it fixed soon 15:11:01 ok, cool cool 15:11:07 but we don't know if there may be others once this get merged 15:11:07 i'll follow up tomorrow 15:11:11 right. 15:11:13 as it is. 15:11:20 we've been consistently promoting before this blocker 15:11:28 oh, nice 15:11:35 so, it looks in good shape 15:11:49 okay, very cool 15:12:49 in that case, the next subitems within this topic are social media / website / etherpad prep... 15:13:34 i'm handling this right now; i'll finish prepping the website / etherpads tomorrow and write / post a blog tomorrow as well as send email / posts everywhere and follow up next week as well. 15:13:37 but! 15:13:58 i'm also going to document all these steps on rdoproject.org/testday so that others can also do these steps in the future. 15:14:13 which brings me to the next step which is the test cloud environment that dmsimard is leading 15:14:34 dmsimard, are you available to report what you've arranged so far? 15:16:26 (mebbe not because he was absent from rolecall) 15:18:32 in case anyone has missed the email, dmsimard is moving to a new role within red hat http://post-office.corp.redhat.com/archives/rh-openstack-dev/2018-May/msg00403.html 15:19:07 and one of the ways that i'm prepping for future test days is to capture what he's done to set up past cloud environments 15:19:19 so that we can arrange for it or something comparable in the future. 15:19:33 and i'll also make that documentation public so that others can take over in the future 15:19:59 at this time, i believe, we're working on a tripleo all in one for next week's test environment 15:20:25 but since details aren't worked out yet, i don't want to confirm that fo sho 15:20:54 any questions about next week's test days? 15:21:04 the tripleo all in one installer is only supporting keystone at the moment, so I guess we will have to wait a bit to use it 15:22:28 ah, sad. so that's clear. 15:23:14 do we have someone willing to set up a tripleo environment as the test cloud? 15:23:44 (hopefully we can do the tripleo all in one by august's test days) 15:23:46 if there is no option for tripleo, we can do a packstack deployment 15:23:57 fair 15:24:19 i'll follow up with the DF DFG 15:24:42 #action leanderthal follow up with the DF DFG re: next week's test cloud environment 15:25:19 any other questions / comments / concerns on test days? 15:27:25 #action mjturek chair next week's meeting 15:27:37 #topic open floor 15:27:42 then anything for open floor? 15:28:29 The zuul-migration to sf.io should be starting this week, this means jobs will now be ansible 15:28:34 first project will be weirdo 15:29:14 this means, we'll be landing changes to remove JJB in config project 15:30:47 https://review.rdoproject.org/r/13951/ is our mapping for zuul-migrate, plus some changes to JJB which is used to generate https://review.rdoproject.org/r/13964/ 15:30:50 so reviews are welcome 15:30:59 https://review.rdoproject.org/r/#/q/status:open+branch:master+topic:zuulv3-init (more reviews here) 15:31:17 https://review.rdoproject.org/r/14042/ is a working example of a zuulv3 job, see Zuul CI user 15:32:41 #link https://review.rdoproject.org/r/13951/ 15:32:52 weshay, rfolco ^ you'll have zuul v3 playground for tripleoci 15:32:53 #link https://review.rdoproject.org/r/13964/ 15:33:05 #link https://review.rdoproject.org/r/#/q/status:open+branch:master+topic:zuulv3-init 15:33:14 #link https://review.rdoproject.org/r/14042/ 15:33:25 i might be ridiculously excited about the move to ansible... 15:34:52 anything else for open floor? 15:35:01 we'll run stage changes to zuul-migrate over all the projects, but I expect it to happen pretty quickly. Last project will be tripleo-ci bits 15:35:06 apevec, woot 15:36:34 apevec, we are also planning on using the int sf to do that 15:41:12 int sf? 15:41:43 internal SF instance, out of scope for #rdo :) 15:42:10 ya, this is public SF.io for zuul-migrate 15:42:45 i'm preparing to add a fedora-stabilized image to sf zuul also to use with zuulv3 15:42:50 reviews in https://softwarefactory-project.io/r/#/c/12458/ are welcome 15:44:29 yes, all nodepool images would need to move to sf.io. I've only done rdo-centos-7 ATM 15:47:35 #link https://softwarefactory-project.io/r/#/c/12458/ 15:48:32 anything else for open floor? 15:50:45 aiight, then we'll call it a meeting 15:50:46 #endmeeting