14:06:47 <bauzas> #startmeeting nova
14:06:48 <openstack> Meeting started Thu Jan 12 14:06:47 2017 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:06:51 <openstack> The meeting name has been set to 'nova'
14:07:06 <bauzas> #chair johnthetubaguy mriedem
14:07:07 <openstack> Current chairs: bauzas johnthetubaguy mriedem
14:07:15 <takashin> o/
14:07:19 <efried> o/
14:07:24 <gibi> o/
14:07:24 <bauzas> \o
14:07:28 <edleafe> \o
14:07:36 <johnthetubaguy> #link https://wiki.openstack.org/wiki/Meetings/Nova
14:07:45 <raj_singh> o/
14:07:50 <rfolco> o/
14:07:56 <bauzas> cool, let's begin
14:07:59 <thorst_> o/
14:08:02 <bauzas> #topic Release News
14:08:08 <bauzas> #info Jan 19: final non-client library release (oslo)
14:08:11 * cdent is incapable of using a calendar
14:08:13 <bauzas> #info Jan 26: o-3 milestone, final python-novaclient release, FeatureFreeze, Soft StringFreeze
14:08:22 <bauzas> which means 2 weeks from now
14:08:40 <bauzas> so in case you don't have patches uploaded, don't wait for us reviewing
14:08:58 <bauzas> which goes to...
14:09:00 <bauzas> #link Ocata blueprints https://blueprints.launchpad.net/nova/ocata
14:09:05 <bauzas> #info 70 total blueprints, 22 implemented, 3 not started, 31 need code review
14:09:14 <bauzas> #link Details on remaining blueprints: https://etherpad.openstack.org/p/nova-ocata-feature-freeze
14:09:30 <bauzas> we had a good sprint day yesterday with 5 BPs implemented
14:09:36 <bauzas> congrats to those who helped nova
14:10:13 <diana_clarke> o/
14:10:24 <bauzas> in case you're working on a BP, I urge you to make sure there is no merge conflict and Jenkins is happy with your changes
14:11:08 <bauzas> any questions about the above ?
14:11:36 <bauzas> just remember that the FeatureFreeze will be in two weeks
14:11:43 <johnthetubaguy> looks like a good summary
14:11:44 <johnthetubaguy> I guess we keep using that etherpad as we burn down?
14:11:50 <bauzas> yup, we should
14:12:07 <bauzas> in case folks think the etherpad is not looking good for their BPs, please update it
14:12:17 <bauzas> with details
14:12:22 <bauzas> anyhow
14:12:24 <bauzas> moving on
14:12:33 <bauzas> #topic Bugs
14:12:47 <bauzas> I haven't hard of recent criticals
14:13:12 <bauzas> and the gate... well
14:13:22 <bauzas> #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
14:13:47 <bauzas> we had recent non-voting jobs that were unhappy
14:13:57 <bauzas> at least the py35 job and the placement one
14:14:23 <bauzas> but well, nothing really blocking us AFAIK
14:14:52 <johnthetubaguy> the placement one, is that the only job running placement right now? I lost track :(
14:15:01 <bauzas> johnthetubaguy: not really
14:15:17 <bauzas> johnthetubaguy: we merged some devstack change that added the placement service by default
14:15:26 <johnthetubaguy> I thought that, whats different about the placement job now?
14:15:39 <bauzas> well
14:15:51 <mriedem> placement is on by default in ocata
14:15:55 <mriedem> the newton job was busted
14:15:55 <bauzas> that
14:15:57 <mriedem> but that's fixed now
14:16:04 <bauzas> yup
14:16:08 <johnthetubaguy> ah, that makse sense
14:16:10 <johnthetubaguy> gotcha
14:16:11 <bauzas> hence why it's a different job
14:16:14 <bauzas> anyway
14:16:23 <bauzas> mriedem:  Overall Categorization Rate: 20.2%
14:16:33 <johnthetubaguy> hmm
14:16:35 <bauzas> mriedem: do you need any help ?
14:16:44 <bauzas> for categorizing more ?
14:16:51 <bauzas> or are those like new problems ?
14:17:02 <mriedem> bauzas: wrong page
14:17:03 <mriedem> http://status.openstack.org//elastic-recheck/data/integrated_gate.html
14:17:05 <mriedem> over 60%
14:17:07 <mriedem> which is fine
14:17:20 <bauzas> oh my internet is sooooo terrible
14:17:27 <bauzas> I'm lagging a while
14:17:34 <bauzas> so I clicked on the wrong tab
14:17:36 <bauzas> moving on then
14:17:45 <bauzas> #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days
14:18:10 <bauzas> I haven't seen problems recently
14:18:18 <bauzas> but do folks agree with ^
14:19:09 <bauzas> I take the silence as a green
14:19:22 <bauzas> #topic Reminders
14:19:27 <bauzas> #link Ocata review priorities https://etherpad.openstack.org/p/ocata-nova-priorities-tracking
14:19:51 <bauzas> folks can amend their sections to point changes they want to be reviewed here ^
14:19:59 <bauzas> now, the question I have is :
14:20:23 <bauzas> should we keep that for the next 2 weeks or focus on https://etherpad.openstack.org/p/nova-ocata-feature-freeze ?
14:20:33 <bauzas> that sounds a bit duplicating info
14:20:48 <bauzas> personnally, I try to look at the latter
14:20:51 <johnthetubaguy> yeah, I was thinking that too
14:20:56 <johnthetubaguy> I added a note at the top of the etherpad
14:21:08 <johnthetubaguy> I mean if you run out of the feature freeze pad, sure...
14:21:28 <bauzas> honestly, I think we should focus on blueprints for the next 10 working days :)
14:21:46 <bauzas> that priorities etherpad is also good for commenting bugs
14:22:04 <johnthetubaguy> just need to make sure everyone updates the new one, thats all
14:22:08 <bauzas> but I tend to prefer seeing what's really important for the project in the feature-freeze etherpad
14:22:15 <bauzas> consensus ?
14:22:16 <bauzas> mriedem: $
14:22:18 <bauzas> oops
14:22:19 <bauzas> mriedem: ^
14:22:26 <mriedem> umm,
14:22:33 <mriedem> doesn't matter much to me,
14:22:40 <mriedem> i created the feature freeze etherpad for my own tracking
14:22:52 <mriedem> but happy to have people using it
14:23:20 <bauzas> mriedem: okay, I just want to know where people can put things to review in order to get traction, that's it
14:23:56 <bauzas> mriedem: I don't honestly have an opinion between both that said
14:24:43 <bauzas> anyway
14:24:48 <bauzas> let's not overthink that
14:25:05 <bauzas> let's keep the existing track
14:25:23 <bauzas> and use the priorities etherpad
14:25:42 <bauzas> #topic Stable branches status
14:26:08 <bauzas> #link https://etherpad.openstack.org/p/stable-tracker
14:26:30 <bauzas> I'm glad to see that the placement job is now back green in stable/newton
14:26:45 <bauzas> mriedem: thanks for that
14:26:50 <mriedem> woot
14:26:57 <mriedem> i'm backporting several placement related fixes to newton
14:27:05 <mriedem> to fix ironic reporting in newton
14:27:16 <mriedem> then will probably do a release after that series is in
14:27:28 <bauzas> okay
14:27:42 <bauzas> we also have some change related to placement that should be proposed against stable/newton
14:27:56 <bauzas> the one avoiding to try-once calling the placement service
14:28:02 <mriedem> i already have that up
14:28:05 <bauzas> cool
14:28:12 <mriedem> anyway, i've got to run, be back later
14:28:20 <bauzas> #info stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z
14:28:41 <bauzas> #info  stable/mitaka: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/mitaka,n,z
14:28:54 <bauzas> stable/newton would require some pass
14:29:11 <bauzas> I'll try to help here
14:29:45 <bauzas> I don't know when matt is planning a point release
14:29:48 <bauzas> for newton
14:29:55 <bauzas> lyarwood: do you know that ?
14:30:29 <bauzas> ideally, I'd like to see a point release including https://review.openstack.org/#/c/419217/
14:30:47 <bauzas> as it would help operators to have a nice upgrade path for ocata
14:30:59 <bauzas> in case they haven't run the placement service in newton yet
14:31:06 <bauzas> (because it's optional)
14:31:29 <bauzas> other thoughts on stable ?
14:31:54 <bauzas> okay, tic-tac
14:32:04 <bauzas> #topic Subteam highlights
14:32:14 <bauzas> edleafe: the floor is yours
14:32:27 <edleafe> Discussed placement client. Decided that while needed, it was premature to spend time on it now. Definitely Pike, though.
14:32:30 <edleafe> Talked about whether 'can_host' is needed, but since jaypipes wasn't present and is the one who has expressed a need for it, tabled that until next week.
14:32:33 <edleafe> Determined the need for a set of tests for the more complex cases, such as shared resources that require digging into the aggregate relationships. None of us are confident that the code as is can properly handle that yet. I agreed to start working on a test that should fail now, but pass when aggs are properly supported.
14:32:38 <edleafe> There were several other efforts discussed that seem to be on track.
14:32:41 <edleafe> That's it
14:32:49 <bauzas> cool, great summary
14:32:53 <bauzas> you prepared it ?
14:32:58 <edleafe> always!
14:33:01 <bauzas> edleafe: <3
14:33:10 <bauzas> dansmith: you around ?
14:33:19 <bauzas> dansmith: about the cellsv2 meeting held yesterday
14:33:50 <bauzas> I was there but I was just laying at the corner
14:34:11 * cdent needs to run; waves
14:34:17 <bauzas> cdent: \o
14:34:31 <bauzas> okay, about the cellsv2 meeting, let's try to summarize
14:34:33 <kaisers_> \o
14:34:47 <bauzas> thoughts on integrating cellsv2 with cellsv1, which is busted AFAIK
14:35:27 <bauzas> a few open reviews
14:35:57 <bauzas> and the decision to focus on merging the quota changes before the FeatureFreeze
14:36:23 <bauzas> details can be shown in the priorities etherpad
14:36:40 <bauzas> oh, and next week's meeting is cancelled due to the host being on PTO :)
14:36:45 <bauzas> moving on
14:36:48 <johnthetubaguy> I keep meaning to hit those, just not got to the bottom of my TOOD list :(
14:37:12 <bauzas> johnthetubaguy: yeah, your insights would be appreciated for the quota changes
14:37:25 <bauzas> I'm pretty sure it's old greek to me
14:37:31 <bauzas> (the quota stuff)
14:37:38 <bauzas> but I can try to sneak peek it
14:37:56 <bauzas> so, the live-migration subteam held no meeting this week
14:38:31 <bauzas> API subteam, alex_xu, sdague?
14:39:25 <bauzas> I wasn't there but I can read logs :)
14:39:51 <bauzas> mostly discussion on https://review.openstack.org/#/c/408571/
14:40:07 <bauzas> johnthetubaguy: I saw you were discussing on it this EU morning with alex_xu right?
14:40:20 <johnthetubaguy> yeah, I was at the meeting, let me summarize a bit
14:40:33 <johnthetubaguy> basically focusing on the validation of filters passed into list servers
14:40:37 <bauzas> right
14:40:43 <johnthetubaguy> we have a way to validate the good things
14:40:46 <johnthetubaguy> and ignore some of the bad
14:40:57 <johnthetubaguy> currently looking at rejecting the really bad with 400 errors
14:41:02 <johnthetubaguy> without the code looking a total mess
14:41:08 <johnthetubaguy> not totally getting to there yet
14:41:17 <johnthetubaguy> but close ish
14:41:26 <johnthetubaguy> thats all really
14:41:40 <bauzas> johnthetubaguy: okay, does that mean a new iteration of https://review.openstack.org/#/c/408571/ ?
14:41:55 <bauzas> AFAICT, it's an ocata prio, righT?
14:42:08 <bauzas> so I'd love to review it as soon as it is ready
14:42:18 <johnthetubaguy> it is a priority
14:42:24 <johnthetubaguy> been working hard on it for several weeks
14:42:32 <johnthetubaguy> just struggling to reach consensus on the direction
14:42:36 <bauzas> okay
14:42:53 <johnthetubaguy> code is all up for review, if folks have a preference
14:43:01 <bauzas> anyway, will ping you after this meetingh
14:43:09 <bauzas> moving on
14:43:24 <bauzas> moshele isn't there
14:43:36 <bauzas> lbeliveau neither
14:43:43 <bauzas> so I can't talk for the SRIOV meeting
14:44:03 <bauzas> gibi: I'm unsure, do you folks had meeting ?
14:44:09 <gibi> bauzas: we had
14:44:17 <bauzas> gibi: nice, take the mic
14:44:23 <gibi> in short
14:44:32 <gibi> the flavor notification has been completed yesterday
14:44:40 <gibi> just some follow up refactor patch remains
14:44:50 <bauzas> cool
14:45:01 <bauzas> yeah I remember some thoughts
14:45:11 <bauzas> do you folks have other things to review before FF ?
14:45:21 <gibi> the json schema work is still suffers for ovo dependencies
14:45:30 <gibi> so that will spill over
14:45:31 <gibi> to Pike
14:45:39 <gibi> I suggest looking at the searchlight bp
14:45:45 <bauzas> I saw some nova command for priting the notification schema
14:45:54 <bauzas> is that deferred to Pike as well ?
14:45:54 <gibi> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/additional-notification-fields-for-searchlight
14:46:16 <gibi> bauzas: jest the json schema printing has little chance due to ovo dependency
14:46:21 <bauzas> gibi: k
14:46:31 <bauzas> gibi: thanks
14:46:39 <gibi> and if time allows there is a lot of transformation patch up for review
14:46:45 <bauzas> #topic PTG planning
14:47:02 <bauzas> matt made an etherpad for putting thoughts to discuss during the PTG
14:47:04 <bauzas> #link Pike PTG planning: https://etherpad.openstack.org/p/nova-ptg-pike
14:47:59 <bauzas> AFAICU, the PTG schedule for nova will mostly be meetup style with no scheduled sessions
14:48:21 <bauzas> we'll just consume the etherpad, priority after priority
14:48:36 <bauzas> and friday being like our regular friday contributors meetup
14:49:16 <bauzas> we have a bit more of 10 mins lefy
14:49:18 <bauzas> left
14:49:23 <bauzas> any questions about the PTG ?
14:49:53 <bauzas> just keep in mind that mon-tues will be cross-project
14:50:06 <bauzas> and wed-fri being allocated to nova
14:50:16 <johnthetubaguy> I think its cross project teams
14:50:29 <bauzas> yeah, there are a number of identified teams
14:50:31 <johnthetubaguy> like architecture has a full day, SWG has a full day, Infra, etc
14:50:53 <bauzas> yup, we can see them in http://www.openstack.org/ptg
14:51:05 <johnthetubaguy> yeah, just saying its not like the old one
14:51:12 <bauzas> correct
14:51:20 <bauzas> sorry for being unclear
14:51:35 <bauzas> #topic stuck reviews
14:52:08 <bauzas> I haven't seen any controversial change that was requiring some help here
14:52:38 <bauzas> and the agenda is free from thaty
14:52:41 <bauzas> so...
14:52:42 <bauzas> moving on
14:52:51 <bauzas> #topic open discussion
14:52:59 <bauzas> nothing in the agenda too
14:53:16 <bauzas> so, given I have nothing to say here, should we just consider saving 7 mins of our time ?
14:53:52 <edleafe> +1
14:54:06 <bauzas> my coffee machine has to be refueled
14:54:19 <bauzas> so thanks folks for letting me doing that
14:54:21 <bauzas> #endmeeting