15:01:34 #startmeeting RDO meeting - 2017-04-26 15:01:34 Meeting started Wed Apr 26 15:01:34 2017 UTC. The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:34 The meeting name has been set to 'rdo_meeting_-_2017-04-26' 15:01:35 Meeting started Wed Apr 26 15:01:34 2017 UTC and is due to finish in 60 minutes. The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:40 The meeting name has been set to 'rdo_meeting___2017_04_26' 15:01:53 #topic rollcall 15:01:56 o/ 15:01:57 Yo 15:01:59 o/ 15:02:03 \o 15:02:06 o/ 15:02:20 #chair jpena rbowen apevec chandankumar dmsimard ykarel 15:02:20 Current chairs: amoralej apevec chandankumar dmsimard jpena rbowen ykarel 15:02:22 Current chairs: amoralej apevec chandankumar dmsimard jpena rbowen ykarel 15:02:24 ahoy 15:02:40 #chair weshay 15:02:40 Current chairs: amoralej apevec chandankumar dmsimard jpena rbowen weshay ykarel 15:02:41 Current chairs: amoralej apevec chandankumar dmsimard jpena rbowen weshay ykarel 15:02:54 number80: jruzicka meeting time 15:03:54 ok, let's start with topics in agenda 15:04:06 #topic upstream openstack/rpm-packaging spec templates (toabctl) 15:04:18 [sensu] NEW: master.monitoring.rdoproject.org - check-delorean-ocata-current-passed-ci @ http://tinyurl.com/l55tjpn |#| Build failure on centos7-ocata/current-passed-ci: tripleo-ui: http://trunk.rdoproject.org/centos7-ocata/report.html 15:04:26 toabctl ^ 15:04:53 oh. in another meeting. sorry.l can we postpone it? 15:05:13 toabctl, i can move the topic to the last one if that's ok for you 15:05:20 or move it to next meeting 15:05:25 basically it is about using the spec files from openstack/rpm-packaging in rdo 15:05:30 let's move it to the next meeting. 15:05:31 thanks 15:05:34 ok 15:05:36 o/ 15:05:38 o/ 15:05:42 #undo 15:05:42 Removing item from minutes: 15:05:43 Removing item from minutes: #topic upstream openstack/rpm-packaging spec templates (toabctl) 15:05:53 o/ 15:05:57 #chair number80 trown jschluet 15:05:57 Current chairs: amoralej apevec chandankumar dmsimard jpena jschluet number80 rbowen trown weshay ykarel 15:05:59 Current chairs: amoralej apevec chandankumar dmsimard jpena jschluet number80 rbowen trown weshay ykarel 15:06:13 #otpic Tempest-16.0.0 tag update in RDO [chandankumar] 15:06:21 #topic Tempest-16.0.0 tag update in RDO [chandankumar] 15:06:30 chandan stage is yours 15:06:45 so Tempest-16.0.0 is now available for RDO ocata 15:06:59 Merged rdopkg: Add support for buildsys-tags in info-tags-diff https://review.rdoproject.org/r/6120 15:07:08 rdo-trunk created openstack/vitrage-dashboard-distgit: openstack-vitrage-ui: failed to build 0fe376f https://review.rdoproject.org/r/6397 15:07:19 we have almost fixed all the tempest plugins issues related with this tag upstream 15:07:43 currently due to gate failure magnum and vitrage [stable/ocata] fixed is not merged 15:07:53 projects are working ont hat to fix it 15:07:56 https://review.rdoproject.org/r/#/q/topic:tempest16 15:08:23 thanks chandankumar 15:08:31 Next Action item from here : i am working on adding a upstream gate to do sanity of tempest plugins 15:08:44 will be available soon 15:08:46 nice 15:08:55 15:09:12 next topic 15:09:20 #topic To use or not to use the buildlogs CDN 15:09:23 dmsimard ^ 15:09:30 hi 15:09:35 apevec: you there ? 15:09:55 trown, ^ 15:10:01 I'll get started anyway 15:10:30 The buildlogs CDN has historically been a bunch of problems and I won't get into the details here 15:10:30 this is in the context of DLRN? 15:10:43 trown: yes, and images to an extent 15:10:52 dmsimard: k 15:11:13 we are already not using it where we can 15:11:23 Considering our move to RDO cloud imminent, the buildlogs CDN is something we won't be able to use in the short-ish term in any case 15:11:24 b/c images sync is not working >1month 15:11:27 apevec: right 15:11:37 now, we're actually shipping buildlogs URLs in rdo-release 15:11:47 apevec: ya, with no reply on the bugs for it 15:11:55 dmsimard, for images? 15:12:01 so I'd like to formalize that we /really/ stop using it and move away from it 15:12:11 +1 to just giving up on it 15:12:11 you men for the trunk-...-tested 15:12:12 right? 15:12:22 apevec: https://github.com/rdo-infra/rdo-release/blob/ocata-rdo/rdo-testing.repo#L16 15:12:24 +1 15:12:25 it would be really nice if it worked 15:12:29 but it doesnt 15:12:34 +1 control our own destiny 15:12:42 ah -tested 15:12:49 yeah, that is also not syncing 15:13:00 ack, let's move that to trunk.rdo 15:13:11 +1 15:13:28 and what should be the official repo for images?, images.r.o? 15:13:35 FWIW, I'm in the process of refreshing the rdo infra ansible roles (base config, monitoring, etc.) to bring up the different new servers we'll be using in RDO cloud (images, docker registry, etc.) 15:13:44 or ci.centos artifacts? 15:13:50 I would way images.r.o -- it'll be migrated to RDO cloud in the near future 15:13:55 also once we move DLRN builders out of ci.c.o, we are not able to push to buildlogs.c.o anyway 15:14:04 [sensu] NEW: master.monitoring.rdoproject.org - check-delorean-master-current @ http://tinyurl.com/zqowcwb |#| Build failure on centos7-master/current: vitrage-dashboard: http://trunk.rdoproject.org/centos7-master/report.html 15:14:14 ci.centos artifacts has bandwidth rate limiting and is not an option 15:14:17 (it has to be built within centos.org to be able to push there) 15:14:52 trown, weshay: fyi off-meeting I'll share a doc with what's our current plan for new servers in rdo cloud (docker registry, images.rdo, logs.rdo, etc.) 15:15:02 cool 15:15:06 yes, cico artifacts is only for internal cico access 15:15:06 we'll keep public trunk.rdoproject.org in aws? 15:15:12 or moving to rdo-cloud? 15:15:20 amoralej: I think we'll want to keep it as a mirror 15:15:23 mirror/backup 15:15:25 amoralej, tbd 15:15:29 ok 15:15:34 I'd *really* like to provide a mirrorlist for built-in redundancy 15:15:35 jpena will start DR plan doc 15:15:40 that'd be nice 15:15:56 so 15:15:56 in light of recent DC outage, we NEED one 15:16:12 Fair to say everyone agrees ? 15:16:16 for buildlogs 15:16:17 yes 15:16:18 +1 from me 15:16:22 o/ 15:16:24 who wants to send PR to rdo-release ? 15:16:26 +1 15:16:36 +1 \0/ 15:16:38 actually review.rdo is now 15:16:40 +1 15:16:43 +1 15:16:46 #agreed Stop using buildlogs as a CDN for trunk packages and tripleo-quickstart images 15:17:01 #action dmsimard to send a review to update rdo-release packages to substitute buildlogs repos 15:17:16 That's it for me 15:17:28 +1 :) 15:17:31 just for the record 15:17:34 thanks dmsimard, let's move to next topic 15:17:52 #topic DLRN moving to https://softwarefactory-project.io, new git URL is github.com/softwarefactory-project/DLRN [jpena] 15:17:59 that's mine 15:19:05 this is mostly information. We are working on having DLRN more integrated with softwarefactory-project, so we have moved the repo to github.com/softwarefactory-project/DLRN (redirection is in place, so scripts using older git clone will still work) 15:19:25 also, its Gerrit is now on https://softwarefactory-project.io 15:19:53 nothing should change, unless you did git clone from review.rdo.o 15:20:07 if something breaks, just give me a shout and I'll fix it asasp 15:20:12 s/asasp/asap/ 15:20:45 about integration between sf and dlrn, what's the goal? 15:21:08 what kind of use cases?, like the old idea of running it in nodepool jobs? 15:21:20 amoralej: dlrn is the software 15:21:25 the goal is to have expanded dlrn usage beyond the RDO case 15:21:34 the package building will occur in review.rdo 15:21:46 ok, nice 15:21:48 as in, this is just for DLRN code review 15:21:58 jpena, will it be removed from review.rdo ? 15:22:05 already removed 15:22:06 apevec: it has been already 15:22:09 i.e. how will existing users notice? 15:22:16 ok, so it will be noticed 15:22:30 I still need to update the .gitreview contents, btw 15:22:38 but that'll happen soon 15:22:53 fatal: No remote repository specified. Please, specify either a URL or a 15:22:53 remote name from which new revisions should be fetched. 15:23:00 ack 15:23:06 rdopkg will follow this path once I see how it went with DLRN :) 15:23:35 jruzicka: smart move, let me get the blame first ;) 15:23:57 but rdopkg is not RDO specific? 15:23:58 jpena++ 15:24:18 amoralej, good question :) 15:24:57 it is used by other projects already 15:24:59 It tries to get more general so it makes sense. 15:25:05 it's just name 15:25:14 and some defaults 15:25:19 for example this blog post is about general usage not tied by RDO: 15:25:20 https://www.rdoproject.org/blog/2017/03/let-rdopkg-manage-your-RPM-package/ 15:25:22 like rdoinfo 15:25:35 yeah the name becomes a little confusing... 15:25:43 legacy let's say :) 15:26:02 just historical 15:26:07 ok, nice 15:26:15 jpena, also change description in github 15:26:16 Rename of a project ripples waves of destruction across the ecosystem, I'd rather not do that. 15:26:35 yeah 15:26:51 we had one rename with dlrn 15:27:17 It's always surprising what seemingly-unrelated things get broken by renames. 15:27:32 indeed 15:28:04 ok, lets move to next topic 15:28:17 #topic Help needed at RDO booth at upcoming events 15:28:26 Red Hat Summit - https://etherpad.openstack.org/p/rdo-boston-red-hat-summit-booth (next week) 15:28:26 OpenStack Summit - https://etherpad.openstack.org/p/rdo-boston-summit-booth (2 weeks) 15:28:35 #info Red Hat Summit - https://etherpad.openstack.org/p/rdo-boston-red-hat-summit-booth (next week) 15:28:40 /EOM 15:28:49 #info OpenStack Summit - https://etherpad.openstack.org/p/rdo-boston-summit-booth (2 weeks) 15:30:01 ok, that's it from agenda topics 15:30:22 #topic open floor 15:30:47 hmm, no volunteers 15:30:56 I can chair next week 15:31:14 #action jpena will chair next meeting 15:31:24 other topics you want to arise? 15:31:42 I meant for the booth 15:31:52 :) 15:32:11 apevec: you have to be at the summit to be able to be at the booth, that restricts our options :) 15:32:23 it does indeed :) 15:33:59 Yeah, I have received zero responses 15:34:01 Who's going to the summit btw ? 15:34:26 I'll be at OpenStack summit as I have a talk 15:35:21 I need to check schedule but I'll definitively take rounds 15:35:36 yeah same here 15:35:44 I need yet to define my sched 15:36:09 So, the big difficulty here is that I will not actually be present, and I'm not entirely certain that Rain is going to make it either. 15:36:23 If Rain can't come, I may change my other plans and come anyway, but that will be expensive last minute. 15:36:39 She intended to come, but something has come up. 15:36:43 rbowen: who'll be organizing meetup? 15:36:44 ok, keep us posted 15:36:56 Oh! Yeah, I should have mentioned that! 15:37:05 So, Wednesday night, at OpenSTack Summit, 6:30 - 9pm 15:37:10 Marriott Hotel 15:37:10 rbowen, let's sync offline? 15:37:15 I think that we can manage at the booth by taking some more rounds 15:37:16 ack 15:37:17 Drinks, snacks, and RDO social time. 15:37:38 So that's arranged and done, but I may need to lean on someone here to be the person that says hello at the door. 15:37:40 David Moreau Simard proposed rdo-infra/ansible-role-rdobase: Default ansible_port to 22 https://review.rdoproject.org/r/6392 15:38:02 rbowen: I can say hello in 20 languages, should be good 15:38:04 #link https://www.eventbrite.com/e/rdo-social-at-openstack-summit-boston-tickets-33896358922 15:38:04 rbowen, number80 and I will be there for hostpitality 15:38:29 apevec: yeah got to relief number80 from hello duty so he can get food 15:38:36 I am trying to verify now for certain whether Rain will be present, in which case it's less of a concern. 15:38:49 But of course your help is always hugely appreciated. 15:39:02 dmsimard: you haven't seen me since Barcelona, that's right 15:39:09 I was in Westford 15:39:18 :) 15:39:27 oh, my brain wanted to forgot the snow tempest 15:39:59 hum, meeting is still going -- I guess we have no more topics ? 15:40:28 i can close the meeting if there are no more topics 15:40:45 I'm all done. 15:41:17 Jakub Ruzicka created rdopkg: patch: new -B/--no-bump option to only sync patches https://review.rdoproject.org/r/6399 15:41:35 ok, i'll give you 20 minutes back 15:41:41 #endmeeting