15:01:48 <chandankumar> #startmeeting RDO meeting (2015-10-14)
15:01:48 <zodbot> Meeting started Wed Oct 14 15:01:48 2015 UTC.  The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:52 <chandankumar> o/
15:01:59 <number80> o/
15:02:04 <chandankumar> #chair number80
15:02:04 <zodbot> Current chairs: chandankumar number80
15:02:08 <dmsimard> \o
15:02:14 <chandankumar> #chair dmsimard
15:02:14 <zodbot> Current chairs: chandankumar dmsimard number80
15:02:20 <jpena> o/
15:02:26 <chandankumar> #chair jpena
15:02:26 <zodbot> Current chairs: chandankumar dmsimard jpena number80
15:02:45 <trown> o/
15:02:50 <chandankumar> #chair trown
15:02:50 <zodbot> Current chairs: chandankumar dmsimard jpena number80 trown
15:03:04 <number80> #chair apevec
15:03:04 <zodbot> Current chairs: apevec chandankumar dmsimard jpena number80 trown
15:03:06 <rbowen> o/
15:03:10 <apevec> o/
15:03:14 <number80> #chair rbowen
15:03:14 <zodbot> Current chairs: apevec chandankumar dmsimard jpena number80 rbowen trown
15:03:14 <chandankumar> #chair rbowen
15:03:14 <zodbot> Current chairs: apevec chandankumar dmsimard jpena number80 rbowen trown
15:03:16 <eggmaster> ohai
15:03:16 <eggmaster> o/
15:03:23 <chandankumar> #chair egafford
15:03:23 <zodbot> Current chairs: apevec chandankumar dmsimard egafford jpena number80 rbowen trown
15:03:30 <chandankumar> #chair eggmaster
15:03:30 <zodbot> Current chairs: apevec chandankumar dmsimard egafford eggmaster jpena number80 rbowen trown
15:03:37 <number80> :)
15:03:41 <jschlueter> o/
15:03:47 <chandankumar> #chair jschlueter
15:03:47 <zodbot> Current chairs: apevec chandankumar dmsimard egafford eggmaster jpena jschlueter number80 rbowen trown
15:04:06 <chandankumar> so starting with first topic
15:04:17 <jruzicka> o/
15:04:24 <chandankumar> #topic Updates on RDO test day
15:04:28 <chandankumar> #chair jruzicka
15:04:28 <zodbot> Current chairs: apevec chandankumar dmsimard egafford eggmaster jpena jruzicka jschlueter number80 rbowen trown
15:04:46 <chandankumar> rbowen, you can proceed.
15:04:49 <apevec> BTW AI repots is NOT a topic, but I'd like us to report back in agenda on action items from the last meeting
15:04:55 <rbowen> I posted some basic stats about the test day to rdo-list and also to https://www.rdoproject.org/forum/discussion/1043/rdo-test-day-thanks
15:05:09 <rbowen> We had pretty strong participation, particularly compared to last time.
15:05:11 <chandankumar> #link https://www.rdoproject.org/forum/discussion/1043/rdo-test-day-thanks
15:05:24 <rbowen> 23 new issues reported, and a lot of discussion on the mailing list.
15:05:40 <rbowen> If you took notes and haven't added them to either the etherpad or the Tested Setups page, please do so
15:05:46 <rbowen> we don't want to lose that feedback.
15:05:59 <rbowen> </eol?
15:06:01 <rbowen> </eol>
15:06:03 <trown> super thanks to mcornea for all the really good RDO Manager bugs
15:06:06 <apevec> EOF :)
15:06:10 <trown> mcornea++
15:06:11 <chandankumar> mcornea++
15:06:15 <rbowen> Oh, and a huge thank you to trown for herding the cats.
15:06:21 <chandankumar> trown++
15:06:26 <apevec> cats? Lions!
15:06:29 <trown> rbowen: easier than herding the bits
15:06:29 <rbowen> :)
15:06:36 <trown> the bits are unruly
15:07:05 <chandankumar> moving to next topic.
15:07:13 <chandankumar> #topic RDO Liberty GA blockers
15:07:23 <chandankumar> apevec, please go ahead
15:07:40 <apevec> during testday 2 were identified
15:07:46 <apevec> both have fixes
15:08:06 <apevec> so question is: anyone aware of new blocker issues for GA ?
15:08:29 * number80 notes that 2 blockers is excellent
15:08:34 <apevec> trown, dmsimard - looks like current liberty will be promoted today?
15:08:34 <trown> https://bugzilla.redhat.com/show_bug.cgi?id=1271002 could be a blocker if it is supposed to work
15:09:06 <apevec> that's the one on the list
15:09:06 <dmsimard> apevec: yes
15:09:07 <trown> apevec: ya current looks to be working again modulo image building which should be fixed via doc/CI patch
15:09:44 <apevec> potential blocker might be coming:
15:09:54 <trown> apevec: whoops... keep paste failing... https://bugzilla.redhat.com/show_bug.cgi?id=1270910
15:10:09 <apevec> using CBS liberty-testing neither me nor jschlueter is getting cirros to get dhcp
15:10:12 <trown> that is the one that I am not sure if it is NOTABUG
15:10:17 <apevec> to-be-debugged after the meeting
15:10:36 <apevec> BTW -testing will be published soon:
15:10:42 <dmsimard> apevec, jschlueter: I have a lot of experience with that kind of issue :)
15:11:08 <jpena> apevec: I can help debugging as well, just point me to the repo and I'll give it a look
15:11:38 <apevec> #link https://bugs.centos.org/view.php?id=9606
15:11:40 <jschlueter> #link http://trunk.rdoproject.org/centos7-liberty/delorean-deps.repo
15:11:43 <apevec> s/soon/today/
15:12:17 <apevec> jpena, dmsimard - it's cbs repos without delorean and epel
15:12:24 <jpena> apevec: ack
15:13:02 <dmsimard> apevec: the two deps repo will be merged ?
15:13:12 <apevec> yes, it will be single repodata
15:13:32 <dmsimard> ok
15:14:14 <chandankumar> apevec, can i move to next topic?
15:14:23 <apevec> same setup as http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-kilo/
15:14:25 <apevec> chandankumar, ack
15:14:32 <chandankumar> #topic Kilo 2015.1.2 rebases
15:14:43 <apevec> me again
15:14:49 <chandankumar> apevec, :)
15:15:02 <social> oh meeting
15:15:16 <apevec> .2 was released yesterday, all package maintainer please rebase f23 and let me know
15:15:16 <number80> #chair social
15:15:16 <zodbot> Current chairs: apevec chandankumar dmsimard egafford eggmaster jpena jruzicka jschlueter number80 rbowen social trown
15:15:19 <sasha2> trown: so trying to deploy 1+1 (the discovery completed successfully, but during the deployment, one node doesn't get dhcp)
15:15:25 <apevec> I'll do CBS builds
15:15:25 <sasha2> trown: any idea what to check?
15:15:38 <sasha2> trown: basically I believe this is https://bugzilla.redhat.com/show_bug.cgi?id=1271289
15:15:54 <trown> sasha2: meeting
15:16:04 * number80 taking glance cinder
15:16:28 <apevec> that's all for .2 Kilo, I'll open trello card to track it
15:17:33 <apevec> next topic please!
15:17:34 <chandankumar> #topic RDO doc hack day
15:18:07 <chandankumar> RDO Doc hack day is tomorrow, i.e. on 15th Oct, 2015
15:18:08 <elmiko> o/
15:18:29 <chandankumar> Feel free to send your patches on https://github.com/redhat-openstack/website
15:18:33 <dmsimard> egrep "grizzly|havana|icehouse|juno" * -R
15:18:38 <chandankumar> #chair elmiko
15:18:38 <zodbot> Current chairs: apevec chandankumar dmsimard egafford eggmaster elmiko jpena jruzicka jschlueter number80 rbowen social trown
15:18:53 <rbowen> See also the open issues list:
15:19:05 <rbowen> https://github.com/redhat-openstack/website/issues
15:19:14 <rbowen> If you're looking for something specific that you can help with.
15:19:16 <jschlueter> #link https://github.com/redhat-openstack/website/issues
15:19:27 <apevec> rbowen, how are blockers for going live marked?
15:19:34 <rbowen> Also, add stuff there if you are aware of problems that need addressed.
15:19:44 <rbowen> apevec: Just one, and it's something that garrett needs to work on
15:19:44 <coolsvap> rbowen, i have discussed the cinder docs with chandankumar i will pick that up tonight
15:19:49 <rbowen> That is, it's a code-side thing, not a content thing.
15:19:57 <apevec> rbowen, also, to avoid upstream docs situation, we need to include updating upstream docs in the workflow for Mitaka cycle
15:19:58 <garrett> rbowen: which? events?
15:20:00 <chandankumar> coolsvap, Thanks :)
15:20:03 <garrett> rbowen: I've been working on that one non-stop
15:20:04 * Humbedooh notes that the mail archives are still broken..
15:20:04 <rbowen> garrett: Yes, that one.
15:20:13 <rbowen> That's the last thing in the 'Launch' milestone.
15:20:13 <garrett> rbowen: you broke a lot of assumptions
15:20:20 <garrett> rbowen: so I have to implement things to handle it all
15:20:21 <garrett> (:
15:20:21 <rbowen> Yes, he's been working on it for the last few days.
15:20:28 <garrett> it's coming along
15:20:34 <rbowen> If there's something I need to do differently in the data files, I can do that, too.
15:20:36 <garrett> I have a WIP branch on github that's slightly behind mine
15:20:45 <garrett> I was squashing commits, but then stopped when I decided to share it today
15:20:54 <chandankumar> rbowen, how we are going to link ask.openstack.org questions on new website?
15:20:54 <garrett> rbowen: yes, in fact, some things would be more optimal
15:21:05 <chandankumar> #chair coolsvap
15:21:05 <zodbot> Current chairs: apevec chandankumar coolsvap dmsimard egafford eggmaster elmiko jpena jruzicka jschlueter number80 rbowen social trown
15:21:08 <garrett> rbowen: timezones, as I doubt that these are all actually UTC or properly converted to UTC
15:21:24 <rbowen> chandankumar: At the moment it's linked down at the bottom, but I'd like it to be more prominent.
15:21:26 <garrett> rbowen: and end times, if possible (I handled it by adding an hour if it isn't)
15:21:37 <rbowen> garrett: Meetups.com provides all dates/times in UTC, so I believe they are accurate.
15:21:46 <garrett> rbowen: and it'd be nice to have the URL handled differently, and a few other optimal things
15:21:51 <rbowen> And I can certainly make up an end time. I expect that one (or two) hour is probably reasonable.
15:22:15 <rbowen> I'll commit a new data file when we're done here.
15:22:17 <garrett> rbowen: ah ok, if they're indeed UTC, then that's fine; when the calendar is subscribed to, it will convert it to local time on people's calendars
15:22:54 <garrett> rbowen: there's a bunch of things that I have been optimizing, and I had to upgrade to the latest libraries that I depend on, which broke the API
15:23:13 <garrett> rbowen: most of the time has been spent on more-proper series support
15:23:46 <garrett> rbowen: and I implemented some hover "popups" to make the calendar even more useful too
15:23:51 <rbowen> Sweet
15:23:59 <garrett> it's really coming along well
15:24:15 <garrett> rbowen: I need to have this done by next week at the latest, as I go on vacation at the end of the month for a few weeks
15:24:25 <garrett> rbowen: (by this, I mean any blocker for RDO)
15:24:40 <rbowen> Yes, we definitely want the new site up before OpenStack Summit
15:24:46 <rbowen> Anyways, I think that's all for doc day. We look forward to everyone participating
15:24:50 <rbowen> EOL
15:25:02 <garrett> we're in good shape for the end of this week for events; I'd suggest we target next week for launch
15:25:07 <rbowen> +1
15:25:27 <garrett> rbowen: (fwiw: these changes will also go into the community website, and eventually oVirt, so I want to ensure they're done correctly)
15:25:44 <garrett> (well, even if it were just RDO, I'd still want to ensure they're correct)
15:25:50 <rbowen> True. :-)
15:26:07 <garrett> just trying to make sure I'm (hopefully) not making any RDO-specific assumptions
15:26:41 <chandankumar> moving to next topic
15:26:43 <apevec> ack, upstream first is correct
15:26:43 <chandankumar> #topic Package Version Bump
15:26:58 <apevec> so just to repeat:
15:27:00 <apevec> #info Please do NOT update Fedora master to any Mitaka release just yet!
15:27:03 <number80> +2
15:27:07 <number80> :)
15:27:34 <apevec> listed liberty release were done some time ago
15:27:45 <chandankumar> For stable-liberty, all packages are already version bumped, Thanks to apevec :)
15:27:57 <apevec> and we have murano submitted by MOS folks!
15:28:24 <number80> which ticket?
15:28:26 <chandankumar> apevec,they can take care of python-muranoclient also
15:28:31 <apevec> I did initial review and asked them to advertise on rdo-list
15:28:45 <chandankumar> number80, https://trello.com/c/we5K0deF/60-add-murano-and-ec2-api-in-rdo
15:28:45 <apevec> yes, it's murano*
15:28:51 <apevec> or .*murano.*
15:28:52 <apevec> :)
15:29:12 <number80> chandankumar: I meant the review ticket
15:29:23 <chandankumar> oh sorry.
15:29:33 <apevec> number80, I asked to post on some public git first
15:29:53 <apevec> I'll add it to the card
15:30:05 <apevec> I thought cern is doing ec2 api only
15:30:10 <number80> apevec: then, we should add mflobo in the loop
15:30:14 <apevec> ack
15:30:18 <number80> comaintainership!
15:30:26 <number80> less work for each of them :)
15:30:39 <alphacc> let us know if you need something more
15:30:58 <number80> alphacc: thanks :)
15:31:36 <chandankumar> For master openstack packages, i am keeping an eye on that.
15:32:16 <chandankumar> apevec, can we send review for master openstack new packages?
15:32:29 <chandankumar> *package review
15:33:08 <apevec> I've linked to MOS gerrithub with their initial master packaging spec
15:33:18 <apevec> in trello card
15:33:31 <apevec> I think we can split that card in murano and ec2 parts ?
15:33:38 <apevec> s/parts/cards/
15:33:49 <number80> apevec: we can
15:34:08 <number80> mflobo also packaged a dependency for murano (yaql that I just approved)
15:34:15 <apevec> chandankumar, re. master-packaging reviews - number80 was working on new review guidelines
15:34:27 <chandankumar> ack
15:34:32 <apevec> number80, adding initial review on github or gerrithub would be good
15:34:41 <apevec> before opening review BZ ?
15:35:10 <number80> apevec: I'll open the ticket first so that we avoid collision but pre-review could be done in github
15:35:27 <number80> we just need to publish on bugzilla formal reports so that legal team is happy
15:35:37 <apevec> number80, ok makes sense, let's put it in writing in rdo-packaging.txt !
15:36:10 <number80> *nods*
15:36:18 <apevec> I hope to start working on https://trello.com/c/rsZEENKI/57-update-rdo-packaging-doc next week after GA
15:36:27 <apevec> but everybody's PRs are welcome
15:36:57 <apevec> this would come under "Packaging review howto"
15:37:25 <chandankumar> apevec, can i move to next topic?
15:37:29 <apevec> yes please
15:37:42 <chandankumar> #topic updates on verwatch
15:38:17 <chandankumar> i have started playing with verwatch from this monday
15:38:20 <chandankumar> #link https://github.com/yac/verwatch
15:38:52 <chandankumar> thanks for jruzicka for the help.
15:39:13 <chandankumar> i will be updating more on this by next week with improved code and docs
15:39:25 <chandankumar> EOL
15:39:33 <apevec> chandankumar, any ideas if verwatch could be integrated w/ antya
15:39:50 <apevec> or what was it, that pkgdb is using for watch upstreams
15:40:02 <chandankumar> apevec, i will be replacing cnucnu with anitya.
15:40:04 <number80> apevec: it could be
15:40:04 <apevec> also dmsimard has version tracker too
15:40:28 <dmsimard> verwatch is better and does more things, my versiontracker is pretty basic :)
15:40:38 <apevec> would be nice to consolidate version tracking efforts
15:40:42 <dmsimard> #link http://versiontracker.dmsimard.com/compare/liberty
15:41:39 <chandankumar> let me have a look at the versiontracker and jruzicka what about using it in verwatch?
15:41:47 <dmsimard> apevec: was mostly a learning and fun experiment for me in my free time :)
15:42:03 <apevec> that's how good things start :)
15:42:14 <chandankumar> dmsimard++
15:42:14 <zodbot> chandankumar: Karma for dmsimard changed to 2 (for the f22 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:42:49 <dmsimard> chandankumar: the thing about verwatch is that the layout is not great for quickly comparing things (at least afaik)
15:43:15 <dmsimard> in the meantime what I needed was a simple table like this: http://versiontracker.dmsimard.com/compare/master
15:43:41 <apevec> yep, UI needs to be improved
15:43:58 <apevec> for verwatch that is
15:44:34 <dmsimard> Ubuntu has this: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/liberty_versions.html and I needed something just like it
15:44:38 <dmsimard> (But I went a bit overboard)
15:44:47 <dmsimard> next topic? :)
15:45:27 <chandankumar> dmsimard, i will take a look on these, let me see how can i improve verwatch.
15:45:37 <apevec> chandankumar, can you look if table layout can work in verwatch
15:45:59 <chandankumar> #topic OCT RDO bug triage Day.
15:46:07 <chandankumar> apevec, sure
15:46:28 <chandankumar> What about keeping oct rdo bug triage day on 29th and 30th oct, 2015?
15:46:43 <rbowen> That could be tricky, with so many of us at Summit.
15:46:46 <trown> that is the summit
15:46:48 <dmsimard> That's dead in the middle of the summit
15:47:13 <chandankumar> rbowen, any new date?
15:47:22 <trown> triaging immediately post-summit might make sense, maybe we will get some bugs during summit
15:47:23 <rbowen> But it would be great if you could talk about it at the RDO Community Meetup on Wednesday. :-)
15:47:29 <apevec> move it +1week
15:47:34 <rbowen> I think probably just skipping that one would be fine.
15:47:41 <rbowen> Or what apevec said.
15:47:57 <dmsimard> rbowen: We have a meetup on Wednesday in Tokyo ? Is there an eventbrite or something ?
15:48:00 <chandankumar> let move it to Nov, after summit.
15:48:08 <chandankumar> *let's
15:48:36 <rbowen> http://sched.co/4MYy
15:48:39 <chandankumar> rbowen, i am not coming to summit.
15:49:09 <rbowen> #link  http://sched.co/4MYy
15:49:19 <rbowen> #info RDO community meetup at openstack summit
15:49:53 <dmsimard> rbowen: thanks, added it
15:50:04 <apevec> rbowen, take good notes for us not at Summit!
15:50:16 <rbowen> Yes, I will be recording it again, and taking notes.
15:51:01 <chandankumar> moving to next topic
15:51:21 <chandankumar> #topic EOL for Juno?
15:51:36 <rbowen> We should do that when upstream does, right?
15:51:45 <dmsimard> Yeah I just put that up there for general discussion - are we dropping juno support when liberty is released ?
15:51:54 <dmsimard> (this is my first release as a packager)
15:52:06 <number80> yeah but we need to empty the update queue first
15:52:07 <apevec> we follow upstream
15:52:12 <apevec> https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fjuno_releases_.2812_months.29
15:52:13 <rbowen> https://wiki.openstack.org/wiki/Releases
15:52:25 <apevec> Juno EOL is coming in Nov to the repos near you
15:52:37 <apevec> I'll be again upstream undertaker
15:52:49 <apevec> i.e. stable relmgr for EOL release
15:52:50 <trown> lol
15:52:51 <alphacc> :)
15:52:58 <dmsimard> ok, I'll consider adding the mitaka CI when we drop the juno one
15:52:59 <chandankumar> **undertaker**
15:53:05 <apevec> so we'll push 2014.2.4 rebase
15:53:13 <apevec> then move rdo repo under EOL/ folder
15:53:14 * trown imagines apevec painted up Dia de los Muertos style
15:53:45 <chandankumar> moving to next topic
15:53:58 <chandankumar> #topic chair for next meeting
15:54:15 <chandankumar> who is up to chair for next meeting?
15:54:46 <trown> I can chair another one
15:55:04 <chandankumar> fyi, I will be traveling back to my home next week,
15:55:07 <apevec> yay rotation!
15:55:21 <chandankumar> #action trown to chair for next meeting
15:55:31 <chandankumar> #topic open floor
15:55:40 <alphacc> Quick one
15:55:44 <alphacc> New centos -release need to be published for kilo (release should be part of the name, details on github issue) / liberty and upgrade paths tested.
15:56:06 <alphacc> I used the github latest for testing internally and it sounds ok but additionals test needed. (pushing it to buildlogs.c.o would be good too for feedback)
15:56:06 <number80> ack
15:56:12 <alphacc> I can add trello card / launch the builds in cbs if needed. let me know.
15:56:21 <apevec> alphacc, thanks - I'll take care of that
15:56:44 <alphacc> apevec: ok great
15:56:46 <rbowen> Next week I'll be in Raleigh for All Things Open, if any of you are around and want to discuss anything around RDO community stuff and what I can do better/differently/whatever.
15:57:06 <trown> oh cool All Things Open is next week
15:57:07 <apevec> alphacc, I need to test again what we did prepare few months ago
15:57:08 <rbowen> I'll be in the red hat office on Wednesday/Thursday.
15:57:12 <trown> rbowen: I am in Raleigh
15:57:34 <chandankumar> rbowen, visit sometime pune office.
15:57:42 <rbowen> chandankumar: I would love to. Maybe next year.
15:57:55 <chandankumar> cool.
15:58:13 <chandankumar> if not any queries, i am going to close the meeting
15:58:17 <chandankumar> 5
15:58:17 <chandankumar> 4
15:58:18 <chandankumar> 3
15:58:19 <chandankumar> 2
15:58:21 <chandankumar> 1
15:58:29 <chandankumar> #endmeeting