15:01:18 <chandankumar> #startmeeting RDO meeting-2017-01-25
15:01:19 <zodbot> Meeting started Wed Jan 25 15:01:18 2017 UTC.  The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:19 <zodbot> The meeting name has been set to 'rdo_meeting-2017-01-25'
15:01:20 <openstack> Meeting started Wed Jan 25 15:01:18 2017 UTC and is due to finish in 60 minutes.  The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:23 <openstack> The meeting name has been set to 'rdo_meeting_2017_01_25'
15:01:27 <chandankumar> \o/
15:01:45 <jruzicka> \o/
15:01:52 <jpena> o/
15:01:53 <jschlueter> o/
15:01:54 <chandankumar> #topic rollcall
15:01:55 <scsnow> hi
15:01:59 <rbowen> ¯\_(ツ)_/¯
15:02:11 <chandankumar> #chair jruzicka jpena jschlueter scsnow rbowen
15:02:11 <zodbot> Current chairs: chandankumar jpena jruzicka jschlueter rbowen scsnow
15:02:12 <openstack> Current chairs: chandankumar jpena jruzicka jschlueter rbowen scsnow
15:02:29 <chandankumar> can someone mute openstack bot?
15:02:48 <rbowen> Just did.
15:02:53 <dougbtv__> o/
15:02:59 <chandankumar> trown: dmsimard apevec number80 meeting time
15:03:03 <dougbtv> o/
15:03:06 <chandankumar> #chair dougbtv
15:03:06 <zodbot> Current chairs: chandankumar dougbtv jpena jruzicka jschlueter rbowen scsnow
15:03:12 <jruzicka> openstack, SILENCE, FOOL
15:03:15 <jruzicka> err
15:03:24 <chandankumar> rbowen: Thanks!
15:03:32 * apevec partially lurking, doublebooked
15:03:33 <trown> o/
15:03:43 <chandankumar> #chair trown apevec
15:03:43 <zodbot> Current chairs: apevec chandankumar dougbtv jpena jruzicka jschlueter rbowen scsnow trown
15:03:50 <trown> also doublebooked, but will respond if needed
15:04:08 <chandankumar> So starting with the first topic
15:04:33 <chandankumar> #topic Vote on move from fast-forwards only  on review.rdoproject.org
15:05:06 <number80> o/
15:05:43 <chandankumar> We always need to rebase after a merge for that we need to vote for fast forwards only
15:05:46 <chandankumar> #chair number80
15:05:46 <zodbot> Current chairs: apevec chandankumar dougbtv jpena jruzicka jschlueter number80 rbowen scsnow trown
15:05:56 <leifmadsen> o/
15:06:03 <chandankumar> Upstream review.openstack.org is "Merge if necessary"
15:06:14 <chandankumar> This means review.rdoproject.org might have merge commits in git
15:06:19 <jruzicka> That is change to "Rebase if necessary"?
15:06:33 <chandankumar> #chair leifmadsen
15:06:33 <zodbot> Current chairs: apevec chandankumar dougbtv jpena jruzicka jschlueter leifmadsen number80 rbowen scsnow trown
15:06:34 <number80> jruzicka: that's one I'd prefer
15:06:41 <rdogerrit> David Moreau Simard created rdo-infra/rdo-dashboards: Update dashboards with Ocata  https://review.rdoproject.org/r/4505
15:06:57 <jruzicka> yes, I changed rdopkg to "Rebase if Neccessary" and it seems to work fine
15:06:58 <jruzicka> +1
15:07:02 <jruzicka> rebase > merge
15:07:06 <chandankumar> For distgit repos, "Rebase if necessary" is suggested.
15:07:49 <chandankumar> Any more suggestions?
15:07:59 <chandankumar> or we go for a vote?
15:08:01 <dmsimard> Not just distgit, why just distgit ?
15:08:04 <jruzicka> Merge if neccessary: If not, then a merge commit is automatically created. This is identical to the classical git merge behavior, or git merge --ff.
15:08:24 <jruzicka> Rebase if neccessary: If not, then the change is automatically rebased and then the branch is fast-forwarded to the change.
15:08:38 <jruzicka> #link https://gerrit-review.googlesource.com/Documentation/project-configuration.html
15:08:57 <dmsimard> jruzicka: hm, you mean gerrit will rebase the change instead of merging when submitting to repo ?
15:09:15 <jruzicka> dmsimard, I just pasted the doc diff :D
15:09:49 <dmsimard> never seen the rebase if necessary behavior, I suggested merge if necessary since that's what upstream uses
15:09:57 <dmsimard> so out of familiarity, /me shrugs
15:10:08 <matbu> hello, a little question, why there is no python-networking-odl-3.2 in the repo (http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-master-tripleo/)
15:10:26 <matbu> how can we grab the 3.2 (instead of 3.1) ?
15:10:38 <chandankumar> matbu: RDO meeting is going on, :-)
15:10:38 <jruzicka> matbu, please wait after the meeting (<50 mins)
15:10:49 <matbu> ack sorry guys
15:11:11 <dmsimard> I'm willing to try rebase if necessary
15:11:20 <dmsimard> anything other than fast forwards only
15:11:31 <chandankumar> number80: can we have a vote on "Merge if necessary" or 'rebase if necessary'?
15:11:35 <jruzicka> dmsimard, it's not neccessary, it might just be more convenient
15:11:38 <dmsimard> because that forces us to rebase the review
15:11:54 <dmsimard> and rebasing the review forces a re-run of the check jobs
15:13:07 <jruzicka> I cant't see a scenario where auto rebasing is unwanted.
15:13:30 <jruzicka> We can switch few projects with to rebase i.n. and see how that works
15:13:46 <jruzicka> if there are no downsides, we can switch the default?
15:14:13 <chandankumar> jruzicka: what about enabling 'rebase' for code projects and merge for 'distgit' job?
15:14:27 <jruzicka> for distgit it makes sense for sure
15:14:30 <chandankumar> for a week then we decide in next meeting
15:14:32 <jruzicka> that can be changed right now
15:14:52 <number80> yes
15:15:05 <jruzicka> so we can switch distgit now and talk about the rest after we see the impact?
15:15:42 <dmsimard> Well, I think the config is per-project
15:15:51 <dmsimard> Not sure if we can changed everything globally
15:15:56 <chandankumar> jruzicka: +1
15:16:10 <dmsimard> Probably need to script it with gerrit API.
15:16:42 <jruzicka> dmsimard, possibly, so change default for new projects + script change existing
15:17:03 <jruzicka> someone with gerrit scripting fu, #action yourself! :)
15:17:47 <jschlueter> ls
15:18:00 <jruzicka> ./RDO_meeting
15:18:08 * chandankumar donot know who has the access to rdo gerrit
15:18:17 <chandankumar> jpena: dmsimard ^^
15:18:42 <jpena> I can give it a look (never played with gerrit API before)
15:19:03 <chandankumar> jpena: thanks! Please add the Action item.
15:19:31 <jpena> #action jpena to script change existing distgit projects to "rebase if necessary"
15:20:06 <chandankumar> Moving to next topic
15:20:12 <chandankumar> #topic Announcements & calls for participation
15:20:22 <rbowen> ok, announcements - most of you already know this part:
15:20:23 <rbowen> Events:
15:20:23 <rbowen> RDO is at DevConf this weekend - http://devconf.cz/
15:20:23 <rbowen> FOSDEM is Feb 4&5 in Brussels. http://community.redhat.com/blog/2017/01/rdo-at-devconf-cz-fosdem/
15:20:23 <rbowen> The CentOS dojo is on Friday the 3rd immediately before. https://wiki.centos.org/Events/Dojo/Brussels2017
15:20:23 <rbowen> Test day next week, Feb 2, 3 - https://www.rdoproject.org/testday/ocata/milestone3/
15:20:24 <chandankumar> rbowen: please go ahead, stage is yours :-)
15:20:34 <rbowen> Calls for participation:
15:20:47 <rbowen> As you may know, I do a community newsletter every month. It goes out to about 2500 people.
15:21:02 <rbowen> I'd like to get more community participation in what goes in that.
15:21:13 <rbowen> There's a draft at https://review.rdoproject.org/etherpad/p/02-2017-newsletter
15:21:28 <rbowen> If you have ideas of things that we should cover in there, add a bullet point. If you want to actually write content for it, go right ahead.
15:21:57 <rbowen> Final thing: If you're going to be at the PTG, I'm doing video/audio interviews with people that work on RDO and upstream openstack in general.
15:22:11 <rbowen> If you have any interest in participating this, please let me know, and I can sign you up.
15:22:14 <rbowen> rbowen@redhat.com
15:22:15 <rbowen> Thanks.
15:22:28 <chandankumar> rbowen: CFP for openstack summit https://www.openstack.org/summit-login/login?BackURL=%2Fsummit%2Fboston-2017%2Fcall-for-presentations%2F ?
15:23:03 <rbowen> Oh yes, that too!
15:23:08 <chandankumar> the last date is 6th Feb.
15:24:19 <chandankumar> Since RDO test day is coming, please do advertise for more participation
15:24:33 <rbowen> I mentioned that above. but, once again:
15:24:39 <rbowen> Test day next week, Feb 2, 3 - https://www.rdoproject.org/testday/ocata/milestone3/
15:24:57 <rbowen> We'll be testing Ocata 3 milestone
15:25:17 <rbowen> And hopefully we'll see a promotion of that shortly after it drops upstream, so that folks can prepare.
15:26:07 <rbowen> Oh, one more thing, since you're still waiting!
15:26:17 <rbowen> If you're going to be at FOSDEM, we need help at the OpenStack table.
15:26:26 <rbowen> I posted a etherpad link to rdo-list.
15:26:44 <rbowen> Here it is - https://etherpad.openstack.org/p/fosdem-2017
15:26:55 <rbowen> If you can do an hour at the table, it would be hugely appreciated.
15:26:56 <rbowen> Thanks.
15:27:14 <chandankumar> rbowen: Thanks :-)
15:27:24 <chandankumar> so moving to next topic
15:27:32 <chandankumar> #topic centos-ocata worker is alive and working
15:27:44 <chandankumar> jpena: please go ahead
15:28:10 <jpena> the stable/ocata worker is now ready and serving at https://trunk.rdoproject.org/centos7-ocata
15:28:41 <jpena> for now, only libraries (and soon clients) have a stable/ocata branch, so everything else is being built from master
15:28:56 <jpena> if you have a CI that will need to target stable/ocata packages, that's the URL to use
15:29:18 <jpena> https://trunk.rdoproject.org/centos7 will start to diverge as soon as projects shift their focus to pike
15:30:00 <jschlueter> jpena: is there any timewarp between centos7 and centos7-ocata?
15:30:16 <jpena> jschlueter: timewarp?
15:30:31 <jschlueter> were all of the builds re-triggered on the stable/ocata worker? or did it inherit builds and then diverge?
15:31:05 <jpena> jschlueter: ah ok. The worker was created from scratch, so all builds are re-triggered. centos-master is not breaking its timeline, though
15:31:14 <jschlueter> jpena: just asking as someone who consumes the output of RDO X Trunk  ... and wondering what I need to watch for
15:31:42 <radez> jpena: how many people are paying attention to changes like: https://review.rdoproject.org/r/#/c/4477 is that something I should just +1 workflow when I +2 or is it better to have a second person +1 workflow?
15:31:46 <jschlueter> but if we were following cento7-ocata all along (through symlink and now real link) we would see it
15:32:00 <dmsimard> jschlueter: right
15:32:07 <jschlueter> dmsimard: ack
15:32:39 <jschlueter> jpena: when will the centos7-pike symlink be created?
15:33:21 <jruzicka> radez, with our size I consider it lucky to have +1/-1 from other people before +2/+1V myself :)
15:33:59 <jpena> jschlueter: judging from the issues we had in the previous cycle (breaking continuity), I'd create centos7-pike by this time during the next cycle, unless there's a real need to do it before
15:35:43 <jschlueter> jpena: I
15:36:04 <jschlueter> I'd make the request that the symlink is available at the begining of the pike cycle
15:36:22 <rdogerrit> Eric Harney created openstack/cinder-distgit: Bump os-brick dep to >= 1.11.0  https://review.rdoproject.org/r/4506
15:37:19 <apevec> we can create centos7-pike symlink pointing to centos7-master right now
15:37:54 <jpena> jschlueter: ack, as long as we accept the continuity break once the stable/pike worker is created
15:38:41 <rdogerrit> Dan Radez proposed openstack/congress-distgit: Initial import of spec file  https://review.rdoproject.org/r/4487
15:38:42 <jschlueter> jpena: no problems there just want to recognize and note it...
15:39:08 <jpena> perfect then
15:39:26 <jpena> #action jpena to add a centos7-pike symlink pointing to centos7-master
15:39:47 <rdogerrit> Merged openstack/heat-translator-distgit: Empty changelog, force a package rebuild  https://review.rdoproject.org/r/4477
15:40:38 <chandankumar> jpena: can we move to next topic?
15:40:42 <jpena> sure
15:41:03 <chandankumar> #topic Updates on Tempest Packaging
15:41:28 <chandankumar> Last night the openstack-tempest rpm is using upstream tempest as a source
15:41:52 <chandankumar> https://review.rdoproject.org/r/#/q/topic:switch-upstream-tempest
15:42:35 <chandankumar> For ocata and further release, source will be upstream tempest and till newton release source will be github.com/redhat-openstack/tempest
15:42:35 <apevec> chandankumar++ good work on that!
15:43:30 <chandankumar> We have moved out the tempest config tool to a temprory place (will be integrated with refstack) https://github.com/redhat-openstack/python-tempestconf
15:43:42 <chandankumar> python-tempestconf is now available in RDO
15:44:03 <chandankumar> https://review.rdoproject.org/r/#/q/topic:add-tempestconf
15:44:34 <chandankumar> we are working on fixing dependent installers to reflect these changes and they can consume new tempest rpms in CI
15:44:53 <chandankumar> Feel free to ping me any queries on this.
15:45:47 <chandankumar> if not then moving to next topic
15:45:57 <chandankumar> most famous topic of every meeting
15:46:09 <chandankumar> #topic chair for next meeting
15:46:20 <chandankumar> Any volunteer up?
15:46:54 * chandankumar looks to jruzicka.
15:47:15 <jruzicka> yup
15:47:38 * jruzicka 's gonna do it
15:48:02 <chandankumar> #action jruzicka to chair for next meeting
15:48:06 <chandankumar> jruzicka: Thanks!
15:48:17 <chandankumar> #topic open floor
15:48:31 <jruzicka> ktdreyer, wording this one isn't easy, I'm curious what you come up with :D https://github.com/openstack-packages/rdopkg/issues/94
15:48:35 <apevec> I've one for open floor, not sure if it was mentioned under Ocata topic
15:48:51 <chandankumar> if any topic is missed feel free to raise here
15:48:53 <scsnow> hi, I'd like to rise the question regarding virt_type=parallels support in packstack. See https://review.openstack.org/#/c/419514/
15:48:54 <apevec> - status of CI pipelines for Ocata
15:49:46 <apevec> there is https://review.rdoproject.org/r/4503
15:49:49 <scsnow> the question is: is 3rd party CI is must have to get this patchset merged?
15:50:14 <scsnow> the same question is regarding cinder vstorage backend support. See https://review.openstack.org/#/c/419459/
15:50:53 <apevec> scsnow, yes, we need to start enforcing that now - and deprecate previous historical features  w/o current CI coverage
15:50:59 <apevec> I'll reply in the review
15:51:07 <scsnow> apevec, ok, thanks
15:51:56 <apevec> EmilienM, trown, weshay - is https://review.openstack.org/424622 all we need to the get centos7-ocata/current-tripleo ?
15:52:12 <apevec> looks like it won't be merged before tripleo project get stable/ocata branches ?
15:52:28 <apevec> and since ooo is release trailing, that can be up to 2 weeks after GA ?
15:52:38 <EmilienM> apevec: yes and https://review.openstack.org/#/c/424637/
15:52:44 <EmilienM> apevec: it will merge, I'll push for it
15:53:01 <apevec> cool thanks
15:53:17 <apevec> ok, tripleo-ci change is merged already
15:53:46 <EmilienM> apevec: it will land tomorrow
15:53:50 <EmilienM> apevec: when we have the branch
15:54:08 <EmilienM> it's useless to run ocata jobs without the branch
15:54:15 <EmilienM> zuul will failover to master
15:54:21 <apevec> right
15:54:48 <apevec> but we need it as soon as even 1 project has stable/ocata
15:55:05 <EmilienM> I can make it merged tomorrow morning
15:55:18 <EmilienM> we won't have the branch before I say to :-)
15:55:26 <EmilienM> so we'll have this thing merged before for sure
15:55:50 <jpena> btw, if someone could have a look at https://review.rdoproject.org/r/4498, we could bring centos-master and centos-ocata back to a consistent state
15:56:20 <EmilienM> jpena: +2
15:57:11 <apevec> and +W
15:57:21 <jpena> thx :)
15:57:28 <apevec> jpena know how to get attention :)
15:57:37 <jruzicka> :D
15:57:47 <jruzicka> smooooth
15:58:13 <chandankumar> if nothing left, can we end the meeting on a countdown of 3?
15:58:58 <chandankumar> 3
15:59:00 <chandankumar> 2
15:59:02 <chandankumar> 1
15:59:05 <chandankumar> 0
15:59:09 <chandankumar> #endmeeting