15:02:17 <chandankumar> #startmeeting RDO meeting - 2017-04-12
15:02:17 <openstack> Meeting started Wed Apr 12 15:02:17 2017 UTC and is due to finish in 60 minutes.  The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:21 <openstack> The meeting name has been set to 'rdo_meeting___2017_04_12'
15:02:26 <chandankumar> #topic rollcall
15:02:28 <chandankumar> \o/
15:03:10 <chandankumar> apevec: rbowen number80 trown meeting time
15:03:35 <number80> o/
15:03:39 <trown> o/
15:03:50 <chandankumar> #chair trown number80
15:03:51 <openstack> Current chairs: chandankumar number80 trown
15:03:53 <trown> chandankumar: you running it? sorry I was late
15:03:53 <rbowen> o/
15:04:00 <chandankumar> #chair rbowen
15:04:00 <openstack> Current chairs: chandankumar number80 rbowen trown
15:04:04 <chandankumar> trown: no problem
15:04:27 <trown> rbowen: I think it is PTO overlap the last couple weeks
15:04:52 <chandankumar> yes, holiday is coming on Friday that is also the reason.
15:05:22 <chandankumar> let me start with the first topic
15:05:45 <chandankumar> #topic pike Milestone 1 test days
15:05:50 <chandankumar> rbowen: please go ahead
15:06:03 <rbowen> Upstream Milestone 1 is tomorrow, according to releases.openstack.org
15:06:17 <rbowen> We plan to do a test day next Thursday, Friday, if we've had a promotion by then.
15:06:30 <rbowen> Are there any concerns about hitting that date that anyone is aware of?
15:06:34 <chandankumar> dmsimard: meeting time
15:06:41 <leanderthal> o/
15:06:47 <chandankumar> jruzicka: \o/
15:06:50 <chandankumar> #chair leanderthal
15:06:50 <openstack> Current chairs: chandankumar leanderthal number80 rbowen trown
15:06:59 <leanderthal> d'awww, thx chandankumar
15:07:51 <rbowen> ok, well, if there's no delays, we should have a test day next week. I've put up the test matrix
15:07:57 <trown> only blocker I know of is https://bugs.launchpad.net/tripleo/+bug/1682001
15:07:57 <openstack> Launchpad bug 1682001 in tripleo "[promotion] nova hypervisors/detail fails when host is not mapped to any cell" [Critical,Triaged]
15:08:03 <rbowen> We also want to test upstream install docs.
15:08:05 <chandankumar> i think tripleo pike-1 was released http://lists.openstack.org/pipermail/openstack-dev/2017-April/115300.html
15:08:31 <dmsimard> \o
15:08:31 <rbowen> As usual, any ongoing help to improve our test matrix would be appreciated.
15:08:40 <rbowen> https://www.rdoproject.org/testday/tests/
15:09:02 <rbowen> In particular, more detailed testing instructions will greatly lower the bar to new participants.
15:09:41 <rbowen> Also, it looks like a lot of the links in that doc are out of date. So I'll try to get that fixes ASAP
15:10:05 <rbowen> That's all I have, until we know whether we'll get a promotion.
15:10:50 <chandankumar> number80: dmsimard apevec may know about pike promotion
15:12:11 <alphacc> number80, apevec : can someone check why we don't have this security issue fixed in newton http://seclists.org/oss-sec/2017/q1/205
15:12:24 <dmsimard> I don't feel like we're too far off a pike promotion look at the past few runs
15:12:35 <chandankumar> #chair dmsimard
15:12:36 <openstack> Current chairs: chandankumar dmsimard leanderthal number80 rbowen trown
15:12:50 <dmsimard> I'll try to follow up and ping where appropriate
15:13:09 <chandankumar> dmsimard: Thanks :-)
15:13:16 <chandankumar> moving to next topic
15:13:23 <chandankumar> #topic python-tempestconf
15:13:36 <jruzicka> o/
15:13:49 <chandankumar> python-tempestconf-1.1.0 is out for ocata
15:13:59 <chandankumar> with 3 new shiny features:
15:14:13 <chandankumar> * Add os-client-config support
15:14:16 <chandankumar> * Enable keystone feature flags
15:14:18 <chandankumar> * Add ability to remove any option from tempest.conf
15:14:20 <chandankumar> * Synced with python-tempest-15.0.0
15:14:22 <chandankumar> https://github.com/redhat-openstack/python-tempestconf/tree/1.1.0
15:14:34 <chandankumar> #chair jruzicka
15:14:35 <openstack> Current chairs: chandankumar dmsimard jruzicka leanderthal number80 rbowen trown
15:15:01 <chandankumar> thanks to tosky mkopec and dmellado for getting these features :-)
15:15:13 <chandankumar> that's it from my side
15:15:24 <DrBacchus> Sorry, network dropped.
15:15:33 <chandankumar> #chair DrBacchus
15:15:33 <openstack> Current chairs: DrBacchus chandankumar dmsimard jruzicka leanderthal number80 rbowen trown
15:15:38 <leanderthal> no worries DrBacchus / rbowen
15:15:41 <jruzicka> I have quick addition to agenda since we have so liitle topics :)
15:15:51 <chandankumar> jruzicka: yup go ahead
15:16:42 <chandankumar> jruzicka: making rdoinfo as a topic
15:16:54 <chandankumar> #topic rdoinfo parser from rdoinfo/rdopkg into a separate module
15:17:21 <chandankumar> jruzicka: please go ahead
15:17:23 <jruzicka> #info rdoinfo data format is stable enough, it's time to release rdoinfo parser as a proper module
15:18:05 <jruzicka> #action jruzicka will merge rdoinfo parser and rdopkg.actionmods.rdoinfo into a separate module
15:18:23 <jruzicka> my main question is about naming
15:19:09 <jruzicka> how shall we call the current rdoinfo repo with the data and the python module repo to not cause confusion
15:19:34 <chandankumar> jruzicka: what about name proposal on a etherpad followed by volting in a next meeting
15:19:35 <apevec> distroinfa ?
15:19:42 <apevec> err, distroinfo
15:19:52 <apevec> it would be generic parser
15:20:03 <jruzicka> cool idea apevec :)
15:20:10 <apevec> but yes let's start bikeshedding etherpad!
15:20:16 <chandankumar> #chair apevec
15:20:17 <openstack> Current chairs: DrBacchus apevec chandankumar dmsimard jruzicka leanderthal number80 rbowen trown
15:21:07 <jruzicka> apevec, OK.
15:21:55 <jruzicka> I'm just letting you know this is going to happen sooner or later. It's not a pressing matter but it would be nice.
15:22:02 <jruzicka> That's it from me.
15:22:43 <chandankumar> ack, moving ahead, i wanted to talk about mitaka EOl
15:23:02 <chandankumar> but after one more topic
15:23:12 <chandankumar> #topic Contributor survey
15:23:19 <chandankumar> rbowen: please go ahead
15:23:27 <rbowen> just a reminder that we are conducting a contributor survey, at https://goo.gl/forms/SYVo9gbacsMfe8Ov2
15:23:41 <rbowen> The response has been very disappointing - less than 20 so far.
15:23:52 <rbowen> But the feedback, even in just that, looks very valuable.
15:24:04 <rbowen> So, if people could participate, that would be great.
15:24:06 <leanderthal> i'll post it on groningenrain.nl and cross link on twitter
15:25:21 <chandankumar> leanderthal: cool!
15:25:55 <rbowen> that's all I wanted to say there.
15:26:09 <chandankumar> circulating the survey link to centos fedora or openstack list might help us getting more response
15:26:18 <leanderthal> exactly ^
15:26:22 <rbowen> That's a very good idea, I'll do that too.
15:26:38 <rbowen> Get the people that have been occasional contributors but aren't very connected right now.
15:26:45 <rbowen> Thanks.
15:26:54 <chandankumar> rbowen: Thanks :-)
15:27:02 <chandankumar> moving to my own topic
15:27:07 <chandankumar> #topic Mitaka EOL
15:27:27 <chandankumar> upstream has started tagging Mitaka as EOL http://lists.openstack.org/pipermail/openstack-dev/2017-April/115308.html
15:27:28 <apevec> it is happening upstream
15:27:31 <apevec> [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL
15:27:41 <rbowen> Oh, that was this week, wasn't it. I forgot.
15:27:44 <chandankumar> what are the plans for RDO?
15:28:06 <rbowen> We have historically followed closely behind upstream in EOL'ing releases.
15:28:07 <apevec> we'll remove mitaka trunk as soon as eol tags are merged
15:28:27 <rbowen> We need to announce this various places. Who would like to write that announcement?
15:28:28 <apevec> and I've action to define EOL procedure for repos on mirror.c.o
15:28:35 <apevec> we're few release behind
15:28:43 <chandankumar> from very long time, we have not closed the bulk EOL bug, time for a grand bug triage day in between pike m1 and m2.
15:28:48 <chandankumar> any thoughts?
15:29:00 <apevec> it was raised on #centos-devel that we still have EOL releases around
15:29:16 <apevec> chandankumar, I don't think it was well receieved last time
15:29:34 <rbowen> You mean bulk closing tickets against EOL releases?
15:29:38 <apevec> so I don't think we should do mass-closing
15:29:56 <rbowen> I've been gradually closing ask.openstack.org questions against long-EOL'ed releases, but I've typically stayed one behind.
15:30:00 <apevec> rbowen, yeah, but release info in BZ might not be correct
15:30:15 <chandankumar> apevec: rbowen mass closing would not be good, but traiging should be good and closing them manually
15:30:15 <rdogerrit> Merged openstack/tempestconf-distgit: Added python-os-client-config as BR and Requires  https://review.rdoproject.org/r/6241
15:30:34 <apevec> chandankumar, ack for scheduling triage day
15:30:46 <leanderthal> chandankumar, i have a topic if there's time....
15:30:56 <chandankumar> leanderthal: we have lots of time
15:31:00 <apevec> rbowen, re. announcement - I don't think upstream did one
15:31:16 <rbowen> Really? Seems like a good thing to mention to people.
15:31:28 <rbowen> But, no, I didn't see an announcement. Perhaps because it's not complete yet?
15:31:29 <chandankumar> feel free to jump after that,
15:31:31 <apevec> it is just put on the schedule in advance
15:31:35 <apevec> so folks can plan
15:31:54 <apevec> EOL dates are published at http://releases.openstack.org/
15:32:17 <apevec> we know them up to Ocata
15:32:20 <chandankumar> 2017-04-10 is the EOL date for the mitaka
15:32:28 <rbowen> Yeah, but seems like an announcement is a good idea, too, as not everyone is looking there. But, hey, not my circus. :-)
15:33:17 <apevec> ok, I'll draft something
15:33:22 <apevec> for cloud sig
15:33:26 <rbowen> +1
15:34:08 <apevec> #action apevec to draft Mitaka EOL annoucement for Cloud SIG repos
15:34:21 <apevec> next topic?
15:34:44 <leanderthal> #topic TryStack FreeIPA
15:34:55 <chandankumar> leanderthal: please go ahead
15:35:37 <leanderthal> Trystack would like to shift to using FreeIPA / not facebook as their user technology and would love any help
15:36:25 <leanderthal> if you're keen and available, please visit #trystack and reach out to wfoster
15:36:43 <leanderthal> rbowen, what is kambiz' irc nick?
15:36:54 <dmsimard> rbowen: kosh ?
15:36:57 <dmsimard> leanderthal: ^
15:37:01 <rbowen> kambiz I believe
15:37:06 <rbowen> There's a kambiz on #trystack
15:37:08 <leanderthal> ah, that's easy.
15:37:09 <wfoster> kambiz on freenode, kosh internally
15:37:11 <leanderthal> HA!
15:37:12 <leanderthal> nice
15:37:15 <leanderthal> oh hello wfoster
15:37:20 <leanderthal> i'm getting you help ;-)
15:37:29 <wfoster> \o/
15:37:35 <rbowen> And that's what's blocking moving Trystack to a more recent release.
15:37:37 <leanderthal> do you want to say anything to add to that request?
15:37:47 <rbowen> So this would be a very, very nice thing to have behind us.
15:37:55 <leanderthal> +1
15:38:02 <dmsimard> wfoster: I guess our keystone and IPA hero ayoung is no longer a good fit for this considering his new role ?
15:38:22 <wfoster> we also synced with openstack infra team upstream (fungi, pbelanger) and they have hooked us up wiith some ipsilon developers to see about tying into openstackid and their auth infrastructure.
15:39:11 <wfoster> smarcet and jpmaxman in #openstack-infra are the main openstackid maintainers
15:39:28 <wfoster> (this was last tuesdays upstream infra meeting)
15:40:19 <wfoster> time permitting on our side, i'll be on PTO until 2017-04-27 and kambiz is generally always busy with perf/scale, QUADS development, etc.
15:41:42 <wfoster> leanderthal: dmsimard nkinder is our freeIPA contact (hoping to maybe move the v4 FreeIPA self-service stuff past POC state?)  we can use trystack as a working environment for this and everyone would benefit from it
15:42:11 <wfoster> kambiz: ^^
15:42:41 <leanderthal> wfoster, would it help to have those interested in helping reach out to you / kambiz so that you two can make the email introductions?
15:42:54 <leanderthal> with nkinder, i mean
15:44:22 <wfoster> leanderthal: sure, though I think he's been on the various threads about this in the past.  One mutually beneficial point here is that it'll help FreeIPA development in general to have a real world usage evironment to develop/improve things for the self-service parts of FreeIPA.  Maybe this is something PM can get on board with?
15:44:58 <wfoster> then if they think it's a good cause they can push to allocate official resources
15:45:06 <leanderthal> schweet.
15:45:15 <wfoster> our parallel deployment is available for anyone to use for this, it's public and live.
15:45:33 <wfoster> once it works nicely we can merge the two
15:46:38 <leanderthal> do you want to provide the link here so that the RDO community can provide you with testing / patches / feedback / documentation / publicity / anything else in the meantime?
15:47:05 <apevec> leanderthal, wfoster - better to post it on rdo-list
15:47:14 <leanderthal> +1
15:47:29 <leanderthal> wfoster, would you send out an email or give me the link and i'll take care of it?
15:51:32 <chandankumar> leanderthal: i think wfoster is not around, moving to next topic
15:51:38 <leanderthal> no worries
15:51:41 <leanderthal> i'll follow up
15:52:07 <chandankumar> leanderthal: wfoster thanks for bringing up the discussion related to trystack and FreeIPA :-)
15:52:14 <leanderthal> #action leanderthal email rdo-list re: trystack freeipa
15:52:21 <rbowen> For going into it with no agenda, this was the longest meeting we've had in a long time. :-)
15:52:21 <chandankumar> leanderthal: :-)
15:52:34 <chandankumar> rbowen: yes
15:52:35 <leanderthal> :-)
15:52:49 <chandankumar> before moving to open floor
15:52:58 <chandankumar> #topic chair for next meeting
15:53:10 <chandankumar> Anyone up for volunteering for next meeting
15:53:13 <chandankumar> ?
15:53:43 <leanderthal> I can do it in two weeks, but not on 19 april
15:54:05 <chandankumar> leanderthal: counted for next to next week
15:54:23 <apevec> so wasn't trown supposed to chair today? :)
15:54:28 <chandankumar> apevec: yes
15:54:57 * chandankumar looks at trown .
15:55:08 <trown> k, I can do it next week :P
15:55:14 <chandankumar> trown: thanks :-)
15:55:14 <leanderthal> :-D
15:55:25 <trown> I did it last week as well :P
15:55:26 <chandankumar> #action trown to chair for next meeting.
15:55:41 <chandankumar> #topic Open Floor
15:55:59 <chandankumar> feel free to any topic which is missing from agenda in Open floor.
15:56:08 <chandankumar> *bring any
15:56:33 <chandankumar> Just a general query how can we bring more people to RDO meeting?
15:57:03 <apevec> have agenda in advance? :)
15:57:17 <apevec> to lure in interested folks
15:57:30 <chandankumar> currently meeting reminder sent 2 days before.
15:57:46 <rbowen> Perhaps rather than just posting a transcript to rdo-list, taking individual decision points to new threads will remind people that they're missing out on where these decisions are getitng made.
15:57:48 <chandankumar> but people still miss out to add agenda
15:57:50 <leanderthal> with the agenda etherpad linked...
15:58:40 <chandankumar> for making new thread might be a good idea
15:59:11 <chandankumar> another thing is revisiting action items from previous meeting might attract people ?
15:59:19 <rbowen> It's a little extra work, but would bring attention to specific decisions that have been made, or discussions that they're missing.
16:00:12 <chandankumar> rbowen: what about starting from upcoming meeting? let's see how it goes?
16:00:20 <rbowen> Sure.
16:00:36 <rdogerrit> Merged rdoinfo: Bump python-tempestconf to 1.1.0 for ocata  https://review.rdoproject.org/r/6242
16:00:38 <rbowen> Although we have at least one item from this meeting that is going back to the list - Trystack and FreeIPA
16:00:51 <rbowen> Oh, and jruzicka's task.
16:00:52 <chandankumar> i will send a mail thread for next week meeting.
16:00:58 <rbowen> So we'll have some of that already for this time around, too.
16:01:28 <chandankumar> rbowen: times up, ending meeting now
16:01:35 <chandankumar> #endmeeting