14:59:59 <jruzicka> #startmeeting RDO meeting (2016-01-20)
14:59:59 <zodbot> Meeting started Wed Jan 20 14:59:59 2016 UTC.  The chair is jruzicka. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:59:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:59:59 <zodbot> The meeting name has been set to 'rdo_meeting_(2016-01-20)'
15:00:18 <elmiko> o/
15:00:22 <trown> cant get much more punctual than that :)
15:00:24 <trown> o/
15:00:27 <elmiko> hehe
15:00:29 <number80> 15:59:59 wow, hero arrived the very last second possible
15:00:40 <rbowen> \0/
15:00:40 <jruzicka> ^^
15:00:42 <jruzicka> o/
15:00:54 <jpena> o/
15:00:55 <apevec> overachiever or wrong clock set? :)
15:00:59 <apevec> o/
15:01:06 <dmsimard> o/
15:01:14 <number80> :)
15:01:15 <imcsk8> O/
15:01:15 <jruzicka> #chair jruzicka apevec number80 rbowen trown elmiko jpena dmsimard
15:01:15 <zodbot> Current chairs: apevec dmsimard elmiko jpena jruzicka number80 rbowen trown
15:01:41 <rbowen> #chair imcsk8
15:01:41 <zodbot> Current chairs: apevec dmsimard elmiko imcsk8 jpena jruzicka number80 rbowen trown
15:01:53 <jruzicka> as always, agenda is @ https://etherpad.openstack.org/p/RDO-Packaging
15:02:34 <apevec> soon to be moved :)
15:02:51 <rbowen> https://etherpad.openstack.org/p/RDO-bettername
15:02:51 <trown> spoiler
15:02:57 <jruzicka> #topic python3 effort status
15:03:13 <number80> ok, quick one
15:03:17 <number80> most of them are merged
15:03:19 <number80> https://review.gerrithub.io/#/q/topic:py3
15:03:29 <number80> the remaining ones requires trivial fixes
15:03:47 <number80> so we should have all oslo libs w/ python3 subpackages quite soon
15:03:55 <number80> EOF
15:04:16 <apevec> for fedora >= 24 rgiht?
15:04:24 <number80> apevec: yes
15:04:40 <apevec> do we set this consistently in the specs? Could it be in rdo-rpm-macros?
15:05:11 <jruzicka> #info most of python3 reviews are merged, rest are trivial issues
15:05:38 <trown> nice one
15:05:39 <number80> in spec files, at some point as EPEL is enabling python3 by default, we'll have to implement a tool to convert spec
15:05:58 <number80> My little finger says that flepied has one usable for us
15:06:11 <number80> or easily adaptable to our use-case
15:06:53 <apevec> interesting, link or not published yet?
15:07:15 <number80> apevec: discussion on fedora lists for now
15:07:24 <jruzicka> to convert what to what exactly?
15:07:29 <apevec> ok, will look for it
15:07:37 <apevec> jruzicka, py2/py3 mess
15:07:49 <number80> jruzicka: disabling with_python3 in spec and add guard where needed
15:07:57 <jruzicka> I see
15:08:15 <number80> e.g I just rebuild python-httplib2 and it enables python3 subpackage on RHEL7
15:08:36 <number80> had to manually fix that before submitting to CBS
15:08:45 <jruzicka> all righty.
15:08:55 <apevec> also there shouldn't be python2-* on EL7
15:09:29 <jruzicka> #topic rdoinfo database format update
15:10:17 <jruzicka> so rdoinfo now supports tags
15:10:31 <apevec> jruzicka++ thanks!
15:10:40 <number80> jruzicka++
15:10:48 <jruzicka> rdopkg support pending
15:10:57 <apevec> looks good, it just needs filtering support
15:11:12 <jruzicka> they are actually tags and overrides in one structure
15:11:15 <apevec> I've added comments in etherpad
15:11:43 <jruzicka> Hmm, filters are implemented on rdopkg level
15:12:01 <jruzicka> rdoinfo is only responsible for providing you the metadata
15:12:17 <gkadam> #chair gkadam
15:12:22 <jruzicka> you should process them yourself.
15:12:44 <jruzicka> #chair gkadam
15:12:44 <zodbot> Current chairs: apevec dmsimard elmiko gkadam imcsk8 jpena jruzicka number80 rbowen trown
15:12:56 <apevec> jruzicka, right, in rdopkg
15:13:02 <apevec> that's what Delorean is using
15:13:36 <jruzicka> yup, that's what I'm working on
15:14:36 <number80> #info jruzicka is implementing rdoinfo metadata filtering in rdopkg
15:14:39 <jruzicka> #action jruzicka to deliver rdopkg tags support including filtering
15:14:42 <jruzicka> eh
15:14:52 <jruzicka> lel
15:14:56 <number80> :)
15:15:20 <jruzicka> #topic dropping early F22/F23 support in Fedora
15:15:28 <jruzicka> #link https://trello.com/c/dGFWubRQ/123-early-retirement-of-fedora-support
15:15:49 <apevec> ^ have a look at reasoning there
15:15:51 <apevec> I'm +1
15:15:52 <number80> all is in the trello card, unless someone has a different idea, I suggest to vote
15:15:57 <number80> +1 too
15:16:09 <jruzicka> +1
15:16:41 <imcsk8> +1
15:16:47 <trown> +1 for me... RDOM does not even work on those releases
15:17:21 <number80> for the record, oslo and clients still remains in Fedora, we're just advancing retirement for services
15:17:24 <rbowen> So, what's the timing on that?
15:17:39 <rbowen> 'cause it would be nice to have a blog post, or some kind of official statement.
15:17:49 <jpena> does it mean we should drop the delorean worker for f22 as well?
15:18:05 <number80> jpena: nope, it will be supported w/ RDO-Liberty copr
15:18:05 <elmiko> i'm also curious about this, is it just dropping the native fedora packages in favor of the rdo repo packages?
15:18:17 <jpena> number80: ack
15:18:17 <number80> elmiko: yes
15:18:25 <elmiko> ack, thanks number80
15:18:26 <dmsimard> jpena: that reminds me, I meant to ask. Am I mistaken or does the delorean worker for fedora process all packages, not just the clients/oslo ?
15:18:30 <apevec> jpena, number80 - we might want to move it to f23
15:18:43 <apevec> but for now, keep it
15:18:46 <rbowen> We need an action on this - someone needs to draft the announcement.
15:19:11 <number80> dmsimard: you're correct but we were speaking about packages available in Fedora repositories
15:19:13 <rbowen> I'm glad to wordsmith and whatever, but someone to write the basic start of an announcement, and why we're doing this.
15:19:27 <number80> #action number80 draft announcement
15:19:36 <number80> #undo
15:19:36 <zodbot> Removing item from minutes: ACTION by number80 at 15:19:27 : number80 draft announcement
15:19:45 <dmsimard> number80: yeah, it was just a question I had to ask before forgetting again, it's a bit wasteful of resources to build everything for fedora but we can think of something later
15:19:48 <rbowen> Thank you.
15:20:03 <number80> #action number80 draft announcement about early retirement for OpenStack F22/23 packages
15:20:15 <jruzicka> number80++
15:20:15 <zodbot> jruzicka: Karma for hguemar changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:20:40 <number80> dmsimard: different beasts, but we can see later
15:20:46 * dmsimard nods
15:21:01 <jruzicka> #topic Magnum integration in Packstack?
15:21:10 <number80> who was it?
15:21:15 <imcsk8> me
15:21:18 <dmsimard> I put my own comments inline in the etherpad but I don't know who the author was
15:21:25 <number80> imcsk8: the stage's yours
15:21:26 <imcsk8> It might be interesting from the PoC point of view since containers are an interesting topic right now
15:21:46 <apevec> so what would packstack do?
15:21:52 <apevec> just install magnum service?
15:21:56 <imcsk8> yup
15:21:57 <apevec> what about images?
15:22:17 <imcsk8> that can be easily done with small images
15:22:59 <number80> imcsk8: doesn't that require packaging kubernetes and swarm?
15:23:05 <imcsk8> just wanted to know if it's worth the effort of adding Magnum to packstack in order to test it
15:23:18 <imcsk8> number80: at least kunbernetes
15:23:22 <dmsimard> I don't think the mitaka cycle is right to work on magnum (if at all) because puppet-magnum is very immature
15:23:28 <number80> ok
15:24:00 <number80> good news is there are people packaging it in CentOS SIG namespace
15:24:03 <trown> I think if it is worth adding to packstack it is worth adding to tripleo
15:24:11 <apevec> yeah, it's late for mitaka
15:24:27 <trown> +1 for too late for mitaka
15:24:34 <number80> yup
15:24:38 <dmsimard> trown: there are probably other projects higher on the priority list for triple o than magnum
15:24:45 <imcsk8> i agree for mitaka is too late
15:24:52 <leifmadsen> +1 too late
15:25:06 <number80> proposal: draft plan to include magnum/packstack support on N release
15:25:08 <trown> dmsimard: maybe... but if someone wanted to work on it I doubt there would be push back against it
15:25:14 <dmsimard> trown: sure
15:25:41 <imcsk8> number80: i can do that
15:25:58 <dmsimard> number80: I would turn that proposal more generic, perhaps something along the lines of "what project would you like in packstack most", maybe even a community vote ?
15:26:17 <number80> imcsk8: thanks, so that we can start checking that we have all components ready by then
15:26:19 <trown> imcsk8: it would be good to identify what is missing to make it work packaging-wise
15:26:39 <rbowen> dmsimard: We need to update the "What's in RDO" page, and ensure that it's correct.
15:26:45 <number80> dmsimard: we can have a poll but if nobody works on implementing the feature, it's a noop
15:26:50 <rbowen> After that, I'd be glad to run a poll.
15:26:55 <rbowen> But - yeah, what number80 said.
15:27:13 <trown> ya, poll is fine, but I would rather just have people volunteer to work on what that want to work on
15:27:15 <number80> at least, it would give us a hint where we can focus our effort
15:27:16 <rbowen> https://www.rdoproject.org/rdo/projectsinrdo/
15:27:27 <dmsimard> number80, rbowen: good point - we could probably reach out to the community to ask what they want regardless though
15:27:37 <rbowen> I think taht page is likely out of date.
15:27:50 <jruzicka> in related news
15:27:53 <jruzicka> #topic doc day today
15:28:01 <trown> seemless
15:28:16 <rbowen> snecklifter did a TON of work on the docs over the last few weeks.
15:28:19 <rbowen> But there's still a lot to do.
15:28:24 <jruzicka> #link https://github.com/redhat-openstack/website/issues
15:28:25 <snecklifter> oh thats nothing
15:28:30 <snecklifter> im just getting warmed up
15:28:31 <number80> I'm hacking on packaging doc on my end and will attempt to submit something for vote next week
15:28:35 <rbowen> A lot of pages are tagged with 'needs-update'
15:28:36 <number80> s/vote/review
15:28:42 <jruzicka> snecklifter, huh, I like the sound of that :)
15:28:43 <number80> snecklifter++
15:28:44 <rbowen> Just tagging a page with 'needs-update' is a useful thing to do.
15:28:48 <jruzicka> snecklifter++
15:28:49 <gkadam> jruzicka, i want to start with openstack definition list , how do i start ? I am a newbie here.
15:28:53 <snecklifter> away for whole of February though FYI
15:28:59 <snecklifter> Honeymoon
15:29:09 <jruzicka> gkadam, first, you need to wait until this meeting is over
15:29:10 <number80> snecklifter: congratulations :)
15:29:14 <rbowen> However, as mentioned on list, OS1 is scheduled for downtime tomorrow, so we kind of lose tomorrow.
15:29:15 <snecklifter> lol
15:29:21 <gkadam> jruzicka, ok.
15:29:48 <snecklifter> Please feel free to raise bugs on the github page and I will address them where I can
15:29:49 <apevec> snecklifter, oh, then that's it, no more hacking for you :)
15:29:51 <jruzicka> snecklifter, missing docs will wait for you I'm sure :)
15:29:51 <rbowen> gkadam: If you want to start writing a definition list, it would be worth trying NOT to duplicate what is already done in the upstream docs.
15:29:58 <number80> ack
15:30:09 <dmsimard> welllllll, github won't go down
15:30:11 <rbowen> gkadam: ie, define only "local" RDO terms, and refer upstream for the full glossary.
15:30:18 <dmsimard> browsing docs through the repo definitely is not optimal but it's there
15:30:18 <number80> dmsimard: I won't be so sure
15:30:21 <gkadam> rbowen, ok
15:30:23 <snecklifter> rbowen, the liberty rdo manager docs are still out of date
15:30:24 <rbowen> Github won't go down, and you can run your own local version of the website.
15:30:24 <jruzicka> gkadam, ooops, sorry, thought you asked about something else :)
15:30:39 <snecklifter> specifically https://repos.fedorapeople.org/repos/openstack-m/rdo-manager-docs/liberty/advanced_deployment/profile_matching.html
15:30:52 <rbowen> If you check out the docs tree and run the start-server script in the root dir, you ahve a full local copy of the site.
15:30:54 <snecklifter> i think you were going to do a manual pull on them or something?
15:31:05 <pradk> number80, is there a gerrit branch for python-tooz? or should i just submit a github pr? getting we dont know where your gerrit is
15:31:08 <apevec> rdo-m is separate subsite, in trown's repo
15:31:24 <trown> apevec: snecklifter, I am thinking of changing that
15:31:26 <snecklifter> ah, maybe trown was going to pull
15:31:42 <rbowen> I think the rdo-manager docs are up to date as of yesterday. csim was working on that earlier this week.
15:31:43 <snecklifter> yes please, I'd happily update but currently no access
15:31:57 <rbowen> But perhaps I'm confusing some things.
15:32:03 <trown> the forked tripleo-docs are not working out as well as I hoped because they target a different audience, and are not actually kept upto date very well
15:32:13 <snecklifter> rbowen, you are i think, I'm referring to the ones at fedorapeople for rdo-m
15:32:15 <number80> pradk pv
15:32:17 <rbowen> oh
15:32:20 <apevec> pradk, OT - but tooz is in gerrithub/openstack-packages
15:32:31 <rbowen> I meant https://www.rdoproject.org/rdo-manager/
15:32:33 <trown> I think it would be better to have the rdom docs on the website git just like everything else
15:32:53 <dmsimard> trown: +1
15:33:00 <snecklifter> trown, +1
15:33:06 <rbowen> +1
15:33:07 <trown> #action trown hack on rdoproject.org rdo-manager docs
15:33:21 <number80> +1
15:33:33 <rbowen> Also https://www.rdoproject.org/packaging/ is pulled from elsewhere.
15:33:36 <trown> my original thought was we could get docs for free from tripleo, but that has not worked out very well
15:33:51 <apevec> rbowen, yes, we should move that to website
15:33:51 <leifmadsen> I pushed a change to the tripleo docs recently
15:34:02 <apevec> https://github.com/redhat-openstack/openstack-packaging-doc
15:34:03 <snecklifter> trown, I really like the format its just keeping it up to date that is the problem
15:34:04 <leifmadsen> is the thought to fork that and maintain separate rather than rebase against upstream tripleo docsk?
15:34:05 <leifmadsen> docs*
15:34:07 <number80> I can take care of that
15:34:43 <apevec> packaging is currently asciidoc, is there a converter ?
15:34:52 <rbowen> Pandoc might?
15:34:57 <rbowen> I think it can.
15:35:10 <trown> leifmadsen: my thought was to create very simple docs for rdo-m on the website, which point to upstream tripleo-docs for further reading
15:35:20 <leifmadsen> ahhh
15:35:22 <leifmadsen> that sounds legit
15:35:25 <leifmadsen> I can help with that
15:35:35 <trown> leifmadsen: if the rdo-m docs are simple they will be easier to keep up to date
15:35:49 <number80> #action number80 submit PR to import packaging doc in website
15:35:50 <snecklifter> trown, might work, I think a lot of people miss the check-box rhel/centos/ceph thing anyway
15:36:20 <apevec> trown, https://www.rdoproject.org/rdo-manager/ is what we have now
15:36:45 <jruzicka> apevec, converting asciidoc to what?
15:36:49 <rbowen> markdown
15:36:54 <apevec> jruzicka, middleman
15:36:54 <jruzicka> asciidoc > makrdown
15:37:03 <apevec> which is yes, md
15:37:23 <csim> iirc, middelamn also support asciidoc
15:37:35 <rbowen> I did not know that.
15:37:35 <jruzicka> well asciidoc is markdown based
15:37:48 <rbowen> I think, however, that we want to stick to a single format, if possible.
15:37:50 <apevec> csim, but better if we keep the same markup
15:37:53 <apevec> rbowen, +1
15:37:54 <rbowen> For the sake of ongoing maintenance.
15:38:14 <jruzicka> indeed
15:38:16 <csim> apevec: yeah, if taht's not a conversion, then no need :)
15:38:49 <apevec> we'll need one-time conversion, but number80 just volunteered :)
15:38:57 <rbowen> we drift from the topic
15:39:05 <rbowen> Unless you're all going to do this as part of doc day. :-)
15:39:18 <apevec> actually why not
15:39:22 <rbowen> ok, excellent.
15:39:30 <number80> apevec: I'm already working on that doc anyway :)
15:39:40 <apevec> yes, it needs big updates
15:39:44 <apevec> so better convert it first
15:40:29 <rbowen> ok, before we push a replacement for /packaging, please make sure you talk with csim about what's in place to automatically update that from elsewhere.
15:41:12 <rbowen> Since that content isn't currently managed in the same way as everything else.
15:41:14 <rbowen> Thanks.
15:41:20 <number80> ack
15:41:57 <jruzicka> #topic Volunteers needed to work the OpenStack table at FOSDEM
15:42:04 <rbowen> Volunteers needed to work the OpenStack table at FOSDEM - https://etherpad.openstack.org/p/fosdem-2016
15:42:10 <jruzicka> #link https://etherpad.openstack.org/p/fosdem-2016
15:42:22 <rbowen> If you're going to be there, and you have a spare hour, please consider spending it at the OpenStack table.
15:42:34 <rbowen> YOu need to be non-partisan, but I think most of us here are good at that.
15:42:34 <apevec> ack, I'll sign up
15:42:50 <rbowen> That is, you're promoting OpenStack, not RDO, while there.
15:42:54 <number80> o/
15:42:57 <rbowen> Of course, if someone asks, ...
15:43:21 <rbowen> That's all on that topic.
15:43:29 <number80> rbowen: I'll send them to the other table ;)
15:43:53 <jruzicka> #topic Other upcoming events
15:43:58 <dmsimard> You can promote OpenStack while wearing your RDO T-Shirt
15:44:00 <dmsimard> :D
15:44:03 <rbowen> I think everyone is aware of the RDO day at FOSDEM.
15:44:15 <jruzicka> #info RDO Day @ FOSDEM Fringe - Jan 29 - https://www.rdoproject.org/events/rdo-day-fosdem-2016/
15:44:18 <rbowen> We also now have an RDO BOF scheduled at DevConf.cs
15:44:20 <rbowen> cz, rather
15:44:29 <jruzicka> #info RDO BOF at DevConf.cz, Feb 6 @15:00
15:44:29 <rbowen> Immediately following jruzicka's rdkpkg talk on Saturday.
15:44:44 <jruzicka> ou yeaaah.
15:44:52 <rbowen> We will have an etherpad agenda for that posted up somewhere soonish, as per usual for these things.
15:45:07 <number80> jruzicka: you're giving the keynote in short
15:45:08 <rbowen> but hopefully a lot of conversation will just naturally flow out of jruzicka's talk.
15:45:10 <rbowen> No pressure.
15:45:11 <rbowen> :-)
15:45:26 <dmsimard> jruzicka's mouth*
15:45:36 <dmsimard> jk, jk.
15:45:38 <jruzicka> lot's of things are generally flowing from my mouth ;)
15:45:50 <jruzicka> no problem with that :-p
15:45:50 <rbowen> Also, alvaro has a mini-conference in Madrid coming up. And various other cool events are listed at http://rdoproject.org/events
15:46:32 <number80> They have a good name MAD
15:46:36 <rbowen> If you have a local meetup, and you want RDO stuff, please tell me.
15:46:44 <rbowen> I can send stickers and the OpenStack CLI bookmarks.
15:46:49 <rbowen> Beyond that, we can negotiate. :-)
15:47:03 <number80> RDO kitkat bars?
15:47:10 <rbowen> ... it could happen
15:47:12 * number80 is dreamin
15:47:18 <rbowen> ok, I'm all done.
15:47:46 <jruzicka> #topic Delorean outage on January 21. Also affects RDO website.
15:47:50 <jruzicka> #info 21-Jan-2016 15:00 UTC/10:00 EST, estimated 8 hours downtime.
15:48:04 <number80> so repo will still be available?
15:48:20 <jpena> so that's mostly about it. Repo will be available, as we'll switch the DNS entry to the backup server
15:48:22 <rbowen> Yes, the repo will be available.
15:48:40 <apevec> rbowen, csim - what about website?
15:48:42 <number80> #info delorean repositories will be available during downtime
15:48:51 <jpena> the only noticeable outage is that new commits will not be processed until the maintenance is finished
15:49:14 <rbowen> We do not have a backup website at this time. :(
15:49:28 <number80> thanks, it's just that people (like upstream CI, OPNFV and more) relying on these repos would want to have that info confirmed :)
15:49:33 <dmsimard> rbowen: do we have a procedure somewhere to setup the website server ?
15:49:37 <jpena> rbowen: any chance we could host it at the delorean website?
15:49:40 <dmsimard> rbowen: I can spin one up somewhere in the meantime
15:49:42 <apevec> could we at least redirect to a page with the outage notice?
15:49:45 <leifmadsen> or what about a github pages site?
15:50:12 <rbowen> My fault. I didn't think to ask csim to set up anything like that. However, if osmeone spins up a site, I'll be glad to point the DNS the right place.
15:50:37 <jpena> we could quickly spin up a site in OpenShift. What's needed?
15:50:38 <dmsimard> I can host it on my personal server if anything but jpena's idea was good too
15:50:51 <apevec> dmsimard, csim has ansible playbook iirc
15:51:00 <rbowen> You check out the rdo-website repo, and you run ./run-server.sh
15:51:07 <trown> ya middleman server on OpenShift should be straightforward
15:51:41 <apevec> who can take action to chase csim for details?
15:52:02 <rbowen> I can try to get the details, but I don't have a place to run the site.
15:52:43 <apevec> #action rbowen to get website setup details from csim
15:52:56 <jruzicka> #topic migrate RDO-packaging etherpad to a new one RDO-Meeting in order to reflect that this is not limited to packaging
15:52:58 <jpena> I'll give it a quick try today on OpenShift. rbowen, I'll let you know if I succeed in replicating it
15:53:05 <rbowen> ok.
15:53:21 <jruzicka> time ticks ticks away
15:53:30 <trown> +1 to etherpad rename
15:53:37 <jpena> +1
15:53:38 <apevec> so new etherpad name: RDO-Team-Meeting ?
15:53:42 <dmsimard> +1
15:53:43 <rbowen> RDO-bettername
15:53:53 <dmsimard> apevec: Just RDO-Meeting is fine
15:53:54 <trown> RDO-Meeting?
15:53:55 <csim> trown: it is a bit annoying due to the way openshift authenticate people with ssh keys :/
15:53:57 <jruzicka> Isn't RDO-Meeting enough?
15:53:57 <rbowen> And we should paint it blue.
15:54:02 <number80> +1
15:54:06 <rbowen> +1 to RDO-Meeting
15:54:11 <leifmadsen> +1 RDO-Meeting
15:54:19 <jpena> +1 RDO-Meeting
15:54:21 <gkadam> +1 RDO-Meeting
15:54:28 <jruzicka> #info we decided to USE RDO-Meeting etherpad
15:54:37 <jruzicka> how much of history do we want to copy?
15:54:46 <apevec> none
15:54:53 <dmsimard> jruzicka: doesn't cost anything to copy it
15:54:54 <dmsimard> apevec: why ?
15:54:55 <number80> jruzicka: links to the old etherpad
15:55:13 <apevec> dmsimard, old etherpad can keep the history
15:55:17 <jruzicka> right
15:55:17 <apevec> in its timeline
15:55:22 <rbowen> Just a link is fine. We send meeting minutes to rdo-list so the history there is more thorough.
15:55:30 <dmsimard> okay.
15:55:39 <apevec> rbowen, that too
15:57:18 <rbowen> Next?
15:58:24 <jruzicka> #topic RDO CI update
15:58:41 <apevec> trown, ^ ?
15:58:45 <trown> I set up https://github.com/redhat-openstack/rdo-infra
15:58:48 <jruzicka> which is the last topic of this meeting and also last one from RDO-packaging etherpad... :)
15:59:07 <number80> trown: you have to make it lasting
15:59:22 <number80> *a lasting memory
15:59:25 <dmsimard> number80: I'll help him !
15:59:26 <apevec> jruzicka, last but not least will be chair for the next meeting :)
15:59:31 <trown> The idea being that we have multiple projects consuming the delorean repos, so we need a neutral place to integrate them all for voting on delorean promotion
16:00:08 <trown> I intend to put some documentation there as well with how to integrate with the promote job
16:00:18 <trown> EOF
16:00:33 <dmsimard> On the general topic of "rdo ci update", Packstack upstream integration gate jobs are almost there, you can follow the work here: https://review.openstack.org/#/q/topic:puppet-and-packstack-jobs
16:01:00 <dmsimard> The only thing preventing weirdo jobs on delorean repositories for puppet-openstack is this review: https://review.openstack.org/#/c/269704/
16:01:03 <apevec> that's good stuff, I've merged packstack part
16:01:16 <dmsimard> and then we can put weirdo puppet and kolla in the promotion pipe
16:01:20 <dmsimard> packstack can be added later
16:01:22 <jruzicka> #info Packstack upstream integration gate jobs are almost there: https://review.openstack.org/#/q/topic:puppet-and-packstack-jobs
16:01:47 <jruzicka> #topic open floor & next chair
16:01:48 <number80> awesome
16:02:03 <trown> I can chair next meeting
16:02:05 <apevec> dmsimard, bribe Monty to merge that :)
16:02:15 <jruzicka> #action trown to chair next meeting
16:02:16 * apevec didn't say that
16:02:41 <dmsimard> apevec: I don't want to poke him too much, he was nice enough to push that out very quickly - I'll get back to him monday if he hasn't provided an update, he's a busy guy :)
16:02:53 <apevec> ack
16:03:04 <jruzicka> As of open floor, we're over time, so please use the IRC channel as you always do to discuss any topics you wish :)
16:03:08 <jruzicka> #endmeeting