15:02:30 <number80> #startmeeting RDO meeting - 2016-09-07
15:02:30 <zodbot> Meeting started Wed Sep  7 15:02:30 2016 UTC.  The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:30 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:30 <zodbot> The meeting name has been set to 'rdo_meeting_-_2016-09-07'
15:02:31 <openstack> Meeting started Wed Sep  7 15:02:30 2016 UTC and is due to finish in 60 minutes.  The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:35 <openstack> The meeting name has been set to 'rdo_meeting___2016_09_07'
15:02:35 <number80> #topic roll call
15:02:40 <chandankumar> \o/
15:02:40 <number80> who's here
15:02:42 <jruzicka> o/
15:02:44 <myoung> o/
15:02:45 <dmellado> o/ hi guys!
15:02:46 <flepied> o/
15:02:47 <snarwade> o/
15:02:47 <imcsk8> \o/
15:02:49 <snarwade> hi
15:02:53 <number80> agenda is here, please complete: https://etherpad.openstack.org/p/RDO-Meeting
15:02:54 <jpena> o/
15:03:08 <number80> #chair chandankumar jruzicka myoung dmellado flepied snarwade imcsk8  jpena
15:03:08 <zodbot> Current chairs: chandankumar dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade
15:03:08 <openstack> Current chairs: chandankumar dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade
15:03:10 * Duck o/
15:03:15 <coolsvap> o/
15:03:19 <number80> #chair Duck coolsvap apevec
15:03:19 <zodbot> Current chairs: Duck apevec chandankumar coolsvap dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade
15:03:19 <openstack> Current chairs: Duck apevec chandankumar coolsvap dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade
15:03:26 <number80> ok, we have quorum
15:03:31 <trown> o/
15:03:39 <number80> #chair trown
15:03:39 <zodbot> Current chairs: Duck apevec chandankumar coolsvap dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade trown
15:03:41 <openstack> Current chairs: Duck apevec chandankumar coolsvap dmellado flepied imcsk8 jpena jruzicka myoung number80 snarwade trown
15:04:02 * social_ is here but also in other meeting so...
15:04:19 <number80> trown: wants to take over?
15:04:59 <trown> sure... forgot :P
15:05:11 <number80> trown: then starts with the next topic :)
15:05:22 <trown> #topic Test day readiness
15:05:42 <apevec> tl;dr we don't know yet :(
15:05:58 <apevec> current job failed on expired certs
15:06:01 <apevec> as luck would have it
15:06:02 <trown> ya, I am fairly hopeful though
15:06:24 <apevec> jpena is fixing certs as we type
15:06:33 <number80> yeah, previous promotion was 11 days ago
15:06:41 <trown> we have all of the image hosting setup, just need to get a promote
15:06:54 <number80> though, it shouldn't be much different from actual M3
15:06:55 <apevec> but we'll lett current #705 run to see 3o quickstart jobs
15:07:12 <trown> anything else on this?
15:07:17 * number80 ok
15:07:18 <apevec> trown, how is the speed from new d/l ?
15:07:29 <trown> apevec: variable... because it is OS1
15:07:43 <trown> yesterday it was taking 45 minutes to get the image for me, today 5
15:07:48 <atarakt> hello guys, I from software-factory, flepied said you have an issue with cert ?
15:08:11 <trown> both of which are better than 3 hours though
15:08:13 <apevec> atarakt, we do, CC jpena
15:08:24 <trown> ok moving on
15:08:30 <trown> #topic Moving redhat-openstack/tempest reviews from gerrithub to r.o.o (chandankumar)
15:08:32 <apevec> atarakt, jpena found http://softwarefactory-project.io/redmine/issues//1303
15:08:56 <apevec> #undo
15:08:56 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x997fe10>
15:09:06 <apevec> atarakt, jpena found http://softwarefactory-project.io/redmine/issues//1303
15:09:16 <apevec> atarakt, but can you PM jpena
15:09:20 <jschlueter> o/
15:09:30 <apevec> so we keep topics going (meeting now)
15:09:35 <trown> #chair jschlueter
15:09:35 <zodbot> Current chairs: Duck apevec chandankumar coolsvap dmellado flepied imcsk8 jpena jruzicka jschlueter myoung number80 snarwade trown
15:09:37 <trown> #topic Moving redhat-openstack/tempest reviews from gerrithub to r.o.o (chandankumar)
15:09:52 <apevec> I think chandankumar left for dinner
15:10:01 <atarakt> apevec: ok, I will check with jpena
15:10:01 <dmellado> apevec: I can take over otherwise
15:10:10 <apevec> my concern is in etherpad, why don't we just get rid of it :)
15:10:11 <chandankumar> I and dmellado was thinking about moving redhat-openstack/tempest from gerrithub to r.o.o
15:10:19 <apevec> I mean tempest fork
15:10:38 <chandankumar> dmellado: go ahead.
15:10:49 <dmellado> chandankumar: I thought you were gone, but that's basically it
15:11:08 <dmellado> as of now the tempest fork is hosted on gerrithub and we were thinking about having it moved under the rdo gerrit
15:11:30 <apevec> that would make it look like endorsed, which is not the right message
15:11:42 <trown> what is the time frame to split out just the config tool?
15:11:47 <apevec> I'd keep old branches where they are and remove the fork asap
15:11:49 <dmellado> mmm apevec I see your point there
15:11:51 <apevec> trown, it was already split
15:12:03 <trown> oh
15:12:12 <dmellado> trown: the config tool split it's ongoing
15:12:22 <dmellado> I'm creating a repo under git.openstack
15:12:24 <dmellado> for that
15:12:39 <dmellado> WIP, didn't have that much time this week, but there's a roadmap for it
15:13:06 <apevec> dmellado, this one? https://github.com/redhat-openstack/python-tempestconf
15:13:27 <dmellado> apevec: yep, but that need to be done
15:13:37 <dmellado> it's not still complete by any means
15:13:43 <apevec> right, and then all jobs changed to actually use it?
15:13:44 <trown> k, so consensus is to leave tempest fork where it is with the idea that we want to remove it soon?
15:13:58 <dmellado> and I'd prefer for that to leave under git.openstack
15:14:07 <chandankumar> dmellado: +1
15:14:12 <number80> *nods*
15:14:18 <apevec> dmellado, yes, I understood redhat-openstack is just a PoC >
15:14:19 <apevec> ?
15:14:22 <dmellado> fine from my side if we're meant to deprecate it
15:14:25 <dmellado> apevec: exactly
15:14:54 <dmellado> then consensus for the fork to stay where it is
15:15:05 <apevec> +1
15:15:18 <imcsk8> +1
15:15:29 <dmellado> +1
15:15:31 <chandankumar> we need to make sure we will be sending tempest config patches to the new repos if anyone have.
15:15:39 <chandankumar> *repo
15:15:44 <trown> #agreed leave tempest fork where it is and deprecate as soon as possible
15:16:08 <dmellado> chandankumar: I'll send an email to the ML when that's done
15:16:17 <dmellado> until then, keep sending any patches to the in-tree
15:16:53 <trown> moving on?
15:17:07 <dmellado> yep
15:17:10 <chandankumar> yup!
15:17:12 <trown> #topic Adding repo files for CI-tested repos in buildlogs CDN
15:17:37 <trown> #info Background: https://bugs.centos.org/view.php?id=11090
15:17:51 <jpena> this is mine
15:18:10 <jpena> Some time ago we tried to get some .repo files for our current-passed-ci repos under buildlogs
15:18:19 <jpena> somehow it got forgotten, until today
15:18:27 <jpena> do we still think it's a good idea to have them?
15:19:24 <trown> I am kind of confused what the use case is
15:19:28 <apevec> we could also have those in rdo-release.rpm
15:19:34 <jruzicka> goal?
15:19:40 <number80> yes and no
15:19:43 <apevec> trown, make jobs actually use CDN
15:19:46 <afazekas> jschlueter, because of the '-maxdepth 2' we did not collected the 2th subdirs like manifest, ill. change it to 3
15:19:52 <apevec> otherwise they just take delorean.repo from CDN
15:19:58 <apevec> which is waste
15:20:18 <number80> those .repo files still references snapshots
15:20:29 <trown> ah, the delorean.repo points to non-CDN files... got it
15:20:29 <apevec> yeah, on trunk.rdoproject.org
15:20:52 <apevec> trown, weshay so question is for CI folks:
15:20:55 <number80> http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-master-tested/delorean.repo
15:21:06 <apevec> could jobs be modified easily to take .repo from rdo-release.rpm ?
15:21:22 <apevec> we have current-passed-ci aka -tested in there
15:21:43 <apevec> https://github.com/redhat-openstack/rdo-release/blob/newton/rdo-testing.repo
15:22:01 <trown> hmm... it is a bit tricky with the image-based deploy we have now
15:22:07 <apevec> not -tripleo, not sure where put that one
15:22:13 <weshay> running everything would be fairly easy, I think we would just need to add something to find the hash for other purposes
15:22:20 <number80> ok, we were speaking about rdo-testing.repo
15:22:32 <apevec> trown, oh, you mean .repo ends up in the image
15:22:33 <weshay> apevec, it's worth creating a card for it
15:22:40 <trown> because we need to use trunk.rdoproject.org to actually validate, but we then use that same image for gate jobs later
15:22:47 <apevec> weshay, ack
15:23:10 <apevec> weshay, there's also task to capture the whole repo inside the image?
15:23:16 <apevec> iiuc
15:23:55 <trown> apevec: that needs further discussion. I would like to bring it up on openstack-dev[TripleO] and come to some consensus about the undercloud image
15:23:56 <apevec> jpena, can you take an action to create a card for CI part of this and assign to weshay ?
15:24:03 <jpena> apevec: sure
15:24:25 <jpena> #action jpena to create cart for CI part of using CDN, assign to weshay
15:25:46 <weshay> trown, so is the plan to let the rdo-master job complete, then rekick w/ the same pin?
15:25:51 <trown> weshay: ya
15:26:04 <apevec> from #705 - all 3 packastack jobs are green
15:26:08 <apevec> so looks good
15:26:15 <apevec> ok next topic?
15:26:27 <trown> #topic
15:26:32 <trown> #undo
15:26:32 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x217c4cd0>
15:26:38 <trown> #topic newton-rdo branching status [hguemar]
15:27:11 <apevec> number80 ^
15:27:22 <apevec> number80, good progress on that!
15:27:41 <apevec> do you see anything which could be partitioned and distributed among us?
15:27:48 <number80> #info oslo libs are getting forked for newton
15:28:24 <number80> apevec: as of now, I'd rather have people take over other reviews, it's quite tedious and error-prone
15:28:36 <apevec> ack
15:28:49 <apevec> #info everybody take over RDO-NEWTON reviews
15:28:57 <number80> *nodes*
15:29:01 <apevec> https://bugzilla.redhat.com/show_bug.cgi?id=RDO-NEWTON
15:29:57 <apevec> #action apevec to report RDO-NEWTON progress for the next meeting
15:29:57 <number80> tomorrow will be clients
15:30:01 <number80> EOL
15:30:32 <apevec> expect beg/borrow/steal from me ;)
15:30:44 <number80> yup
15:31:04 <apevec> ok, next topic
15:31:05 <trown> #topic anouncements
15:31:20 <trown> #info Newton milestone 3 test day is this Thursday and Friday. Please participate.https://www.rdoproject.org/testday/newton/milestone3/
15:31:39 <trown> #info Demos/Q&A at RDO booth at OpenStack Summit Barcelonad - signup at https://etherpad.openstack.org/p/rdo-barcelona-summit-booth
15:31:51 <rbowen> Barcelona, without the d
15:31:53 <rbowen> :-)
15:31:54 <trown> #info Ping me (rbowen) ASAP if there's anything you want in the newsletter (going out later today) - https://github.com/rbowen/rdo-website/blob/master/source/newsletter/2016-september.html.md
15:31:58 <rbowen> Thanks.
15:32:06 <trown> :)
15:32:16 <number80> ack
15:34:20 <apevec> anything else?
15:34:32 <trown> #topic open floor
15:34:42 <social_> I'd like to ask about tripleo update job, do we have such job? Can we add at least no-op ideally from ci-tested to new-ci-tested as part of promotion job?
15:35:05 <weshay> yes
15:35:08 <weshay> several
15:35:30 <apevec> no-op ?
15:35:46 <social_> apevec: tripleo update where yum update won't update anything :)
15:35:54 <weshay> the history on update/upgrade jobs folks is that historically they take too long to run.. 4-5 hrs
15:36:24 <weshay> we can add mitaka -> master to the current-tripleo rdo pipeline but just looking for a good time to do it
15:36:52 <social_> weshay: the update(not upgrade) job shouldn't take that long
15:37:06 <weshay> mitaka -> master has been passing.. failed in the most recent runs, matbu and apetrich are getting upstream to work atm..
15:37:20 <apevec> yum update which doesn't update anything, isn't that FAIL ? :)
15:37:46 <apevec> that means there are no new packages
15:37:54 <jpena> btw, review.rdoproject.org is now back
15:38:00 <number80> jpena++
15:38:08 <apevec> jpena++ thanks
15:38:15 <imcsk8> jpena++
15:38:15 <zodbot> imcsk8: Karma for jpena changed to 6 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:38:17 <apevec> jpena, make sure to document the steps
15:39:17 <trown> anything else for the meeting, or should we call it?
15:39:30 <weshay> social_, there are update and upgrade jobs available, just waiting on the right time to gate a promotion on it.. I don't think today is the day.. but I do have matbu and apetrich reporting back to us if the hash we promote for newton 3 works w/ upgrades
15:39:38 <chandankumar> trown: chair call pending.
15:39:42 <apevec> trown, next chair!
15:39:46 <trown> chandankumar: ah thanks :)
15:39:57 <trown> #topic next chair
15:41:01 <apevec> anyone? :)
15:41:03 <trown> did my IRC drop :P
15:41:19 <chandankumar> if not then i can take it.
15:41:25 <apevec> deafening /dev/null :)
15:41:42 <trown> thanks chandankumar
15:41:49 <trown> #info chandankumar to chair next meeting
15:41:58 <chandankumar> trown: Thanks :-)
15:42:00 <trown> #endmeeting