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