21:00:08 #startmeeting nova 21:00:10 Meeting started Thu Apr 26 21:00:08 2018 UTC and is due to finish in 60 minutes. The chair is melwitt. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:13 The meeting name has been set to 'nova' 21:00:17 hello everybody 21:00:23 \o 21:00:31 o/ 21:00:32 o/ 21:00:55 #topic Release News 21:01:02 #link Rocky release schedule: https://wiki.openstack.org/wiki/Nova/Rocky_Release_Schedule 21:01:10 r-1 was last thursday and we did a bunch of releases 21:01:16 #link rocky 18.0.0.0b1 released on 2018-04-20: https://review.openstack.org/562896 21:01:18 patch 562896 - releases - nova: release rocky 18.0.0.0b1 (MERGED) 21:01:24 #link python-novaclient 10.2.0 released on 2018-04-20: https://review.openstack.org/562804 21:01:25 patch 562804 - releases - rocky: release python-novaclient 10.2.0 (MERGED) 21:01:31 #link os-traits 0.6.0 released on 2018-04-19: https://review.openstack.org/562834 21:01:31 patch 562834 - releases - os-traits: rocky release 0.6.0 (MERGED) 21:01:37 #link osc-placement 0.1.0 relased on 2018-04-19: https://review.openstack.org/562787 21:01:38 patch 562787 - releases - osc-placement: release 1.1.0 for rocky (MERGED) 21:01:59 #link Rocky review runways: https://etherpad.openstack.org/p/nova-runways-rocky 21:02:08 current runways status: 21:02:13 #link runway #1: XenAPI: Support a new image handler for non-FS based SRs [END DATE: 2018-05-11] series starting at https://review.openstack.org/#/c/497201 21:02:13 patch 497201 - nova - XenAPI: deprecate the config for image handler cla... 21:02:26 #link runway #2: Consoles database backend [END DATE: 2018-05-01] series starting at https://review.openstack.org/325381 21:02:26 patch 325381 - nova - Add periodic task to clean expired console tokens (MERGED) 21:02:32 #link runway #3: Add host/hostId to instance action events API [END DATE: 2018-05-08] series starting at https://review.openstack.org/#/c/556746 21:02:32 o/ 21:02:32 patch 556746 - nova - Record the host info in EventReporter (MERGED) 21:02:40 that patchbot is kinda distracting 21:03:03 ō/ 21:03:21 there are several blueprints in the queue that are blocked and notes have been made on the etherpad for each 21:03:30 o/ 21:03:42 anyone have anything to add for release news or runways? 21:04:15 #topic Bugs (stuck/critical) 21:04:26 no critical bugs in the link 21:04:31 #link 31 new untriaged bugs (down 4 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 21:04:42 #link 8 untagged untriaged bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 21:05:02 thanks to those who have been helping with triage and getting the untriaged count down 21:05:11 #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags 21:05:22 ^ how-to instructions if you can help out 21:05:37 Gate status: 21:05:43 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 21:05:53 I'm not aware of any issues in the gate lately 21:06:00 3rd party CI: 21:06:05 #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days 21:06:25 some of the third party CIs have been failing for awhile, need to follow up on those 21:06:39 anybody have anything else on bugs or gate status or third party CI? 21:07:04 #topic Reminders 21:07:10 #link Rocky Review Priorities https://etherpad.openstack.org/p/rocky-nova-priorities-tracking 21:07:20 ye olde etherpad for subteams and bugs ^ 21:07:43 any other reminders people want to mention? 21:08:03 #topic Stable branch status 21:08:15 we did a bunch of stable branch releases 21:08:21 #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z 21:08:26 #link queens 17.0.3 released on 2018-04-25: https://review.openstack.org/562806 21:08:27 patch 562806 - releases - nova: release queens 17.0.3 (MERGED) 21:08:32 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 21:08:36 #link pike 16.1.2 released on 2018-04-25: https://review.openstack.org/562879 21:08:37 patch 562879 - releases - nova: release pike 16.1.2 (MERGED) 21:08:41 #link python-novaclient 9.1.2 released on 2018-04-25: https://review.openstack.org/562820 21:08:42 patch 562820 - releases - pike: release python-novaclient 9.1.2 (MERGED) 21:08:47 #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z 21:08:53 #link ocata 15.1.1 proposed: https://review.openstack.org/564044 21:08:53 patch 564044 - releases - nova: release ocata 15.1.1 21:09:42 it's really nice to see those stable review lists caught up, thank you to all who did stable reviews last week and this week 21:10:02 anything else for stable branches? 21:10:21 #topic Subteam Highlights 21:10:51 dansmith: cells v2, we skipped the meeting and belmoreira and tssurya said they're upgrading to cells v2 this week. anything more to add? 21:11:12 nay 21:11:33 edleafe: scheduler 21:11:35 Quick meeting. cdent ran it, as I got pulled into a worthless meeting. 21:11:38 Not much was discussed. They agreed it was better to get back to reviewing, and did just that. 21:11:43 short and sweet 21:11:49 nice 21:11:59 gibi has left some notes on notifications: 21:12:09 "we talked about the bp add-server-group-remove-member-notifications as takashi provided the PoC code we requested. mriedem summarized the problems about the change on the ML #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129804.html" 21:12:38 #link issues with bp add-server-group-remove-member-notifications http://lists.openstack.org/pipermail/openstack-dev/2018-April/129804.html 21:12:50 "we also talked about the bp add-full-traceback-to-error-notifications . I'm busy with the bandwidth spec so we agreed to ask help from Kevin_Zheng and he already proposed a WIP patch for the bp" 21:13:12 #link WIP patch for bp add-full-traceback-to-error-notifications https://review.openstack.org/#/c/564092/ 21:13:12 patch 564092 - nova - WIP 21:13:24 "last but not least the implementation of the bp add-request-id-to-instance-action-notifications has been completed and merged. \o/" 21:13:34 anything else for subteams? 21:13:48 #topic Stuck Reviews 21:14:02 no items in the agenda. does anyone have any stuck reviews to bring up? 21:14:27 #topic Open discussion 21:14:41 no items in the agenda. does anyone have anything they'd like to discuss openly? 21:15:22 going once 21:15:32 going twice 21:15:40 quick question 21:16:02 go ahead 21:16:29 https://review.openstack.org/#/c/560718/ - glance image tratis 21:16:30 patch 560718 - nova-specs - Handle rebuild of instance with new image 21:16:51 is under discussion on the mail chain....i think there was a shoutout to openstack operators ML 21:17:15 i haven't gotten back to the thread since it exploded 21:17:18 how long do we wait for a response before we move forward...just curious 21:17:42 http://lists.openstack.org/pipermail/openstack-dev/2018-April/129726.html 21:17:50 thats the ML for context 21:18:15 #link ML thread about bp/glance-image-traits http://lists.openstack.org/pipermail/openstack-dev/2018-April/129726.html 21:18:49 So at the end of that thread we wound up with two options. 21:19:17 The original #1 - make it an error - and using allocations to figure out which RPs were applicable and getting traits from those and making sure all image traits were therein. 21:19:35 arvindn0_: Does that gel with your understanding? 21:19:54 yup 21:20:14 error in case image traits have changed on the image 21:21:05 make it an error where? api? scheduler? 21:21:27 and making it a clear message saying that the image properties have changed hence a relaunch is recommended 21:21:30 in teh conductor 21:21:35 pew 21:21:45 so the user gets a 202 and then rebuild fails but they don't know why 21:21:46 yay! 21:21:48 tech debt 21:21:55 bauzas did not want addtional validations in scheduler 21:22:14 we should probably not design this here, unless more people are involved; i haven't gotten caught up in the thread 21:22:17 The discussion of where the error happens seems orthogonal. 21:22:27 why is it a 202? should it not follow the same noValidhost exception with a different message? 21:22:32 Because both options will require an error to be generated in certain circumstances. 21:22:35 api casts to conductor 21:22:36 hence 202 21:22:50 202 means "we got your request and are processing it" - it's for async requests. 21:23:08 so can we punt on this until i'm caught up on the ML thread? 21:23:16 i'm assuming most other people in this meeting don't care 21:23:18 yep...thats fine 21:23:52 i would really like to get the operators input as well...but if they dont reply...wanted to set a timer :) 21:24:16 there is no timer, 21:24:17 If they haven't replied by now, they're not gonna, unless you want to follow up and ask. 21:24:25 it's only been a few days, fwiw 21:24:28 the only timer is on me and my priority for it depends on how much people bug me about it 21:24:48 * arvindn0_ bugs mriedem all day :) 21:24:57 okay, so we'll continue on the ML thread and on IRC 21:25:04 yup...thanks 21:25:19 cool. anything else for open discussion? 21:25:55 alright, we'll wrap up then. thanks everyone 21:25:59 #endmeeting