06:02:30 #startmeeting nova api 06:02:31 Meeting started Wed Oct 17 06:02:30 2018 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:02:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:02:34 The meeting name has been set to 'nova_api' 06:02:57 who else here today ? 06:04:01 #link https://wiki.openstack.org/wiki/Meetings/NovaAPI#Agenda_for_next_Office_hours 06:04:04 agenda ^^ 06:04:11 #topic API Subteam Tracking 06:04:23 #link https://etherpad.openstack.org/p/stein-nova-subteam-tracking 06:06:05 1. Boot instance specific storage backend 06:06:10 this is merged which was in runway 06:06:20 yup, we done last week 06:06:47 yeah 06:06:54 https://review.openstack.org/#/q/topic:bp/api-extensions-merge-stein+status:open 06:07:06 this is also next in runway but i saw you already reviewed most of them 06:07:39 yea, part of review for the last patch 06:08:04 https://review.openstack.org/#/c/607088/5/nova/api/openstack/compute/views/servers.py 06:08:13 gmann: I guess you just forget to remove one line code 06:09:19 yeah, i am sure i did but got restore from rebse form PS4 to 5 06:10:35 Ghanshyam Mann proposed openstack/nova master: Remove more code related to extensions and testing https://review.openstack.org/607088 06:10:47 alex_xu: ^^ done 06:10:53 alex_xu: thanks for reviewing that series. 06:11:25 gmann: np, I'm done also :) 06:11:36 alex_xu: thanks :) 06:11:46 other than that there is no updated from other BP code. 06:11:55 spec review is soemthing we can do. 06:12:25 melwitt set the 23rd as spec review day. 06:12:42 yea 06:12:53 i will cover those during spec day 06:13:26 that is all from tracking topic, alex_xu you have anything else 06:13:34 no more from me 06:15:01 ok 06:15:03 #topic Bug Triage/Discussion 06:16:41 no response from previous bug we discussed so i marked incomplete as of now 06:19:18 ok 06:20:22 i'm planning to trigger this by a fake cell timeout exception, but I didn't get a chance 06:21:13 this one ? https://bugs.launchpad.net/nova/+bug/1789382 06:21:13 Launchpad bug 1789382 in OpenStack Compute (nova) "openstack server list error" [Undecided,Incomplete] 06:21:21 yes 06:23:19 ok, not sure it will be reproducible on that but god to give try 06:23:21 good 06:24:39 next is new bug 06:24:41 https://bugs.launchpad.net/nova/+bug/1791478 06:24:41 Launchpad bug 1791478 in OpenStack Compute (nova) "nova-api get 504 when keepalived restart" [Undecided,New] 06:24:49 this is 504 gateway timeout 06:26:42 Brin Zhang proposed openstack/nova master: Add restrictions on updated_at when getting instance action records https://review.openstack.org/607801 06:27:44 it seems nova-api does not recognize the new node 06:27:50 untill it is running on old node 06:28:19 i am not sure why, alex_xu you ? 06:29:30 also not sure if this is nova-api isssue, or keepalive switch ip issue 06:29:37 why nova api should recognize the new node? 06:31:47 might be he means keepalive does not recognize the new node nova-api service (and does not switch the vip)? 06:33:03 doesn't sounds like nova api problem, it should be his ha configuration problem 06:33:24 yea, sounds like 06:35:12 added the comment on bug 06:35:31 and keeping it open until next week and then we can make it invalid or incomplete 06:35:56 last new bug is this- https://bugs.launchpad.net/nova/+bug/1793606 06:35:57 Launchpad bug 1793606 in OpenStack Compute (nova) "Setting vendordata_providers to DynamicJSON causes config drive to stop working" [Undecided,New] 06:37:55 i remember, there was some fix for DynamicJSON option. 06:39:34 i'm not familar with this one 06:41:20 me too, but i can try to reproduce this on local tomorrow and see whats happening 06:43:23 its default value is StaticJSON https://github.com/openstack/nova/blob/042f08ee968fc83b80e554efe58270c8dfd6265c/nova/conf/api.py#L84 06:44:21 i will check this later and reply on bug 06:44:32 that's all on bug side for today 06:44:59 alex_xu: you have any bug to discuss or we can move to open discussion 06:45:55 we can move on 06:46:53 #topic Open Discussion 06:47:03 i have 1 quick topic 06:47:13 policy related change in upgrade-check CLI 06:47:15 #link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135779.html 06:47:50 ^^ i replied to matt email on upgrade-check and i feel most of the policy changes are candidate for upgrade-check CLi 06:48:03 alex_xu: what you say ? 06:48:20 that is good idea 06:48:34 better than operator to read the boring release note 06:49:02 they can be checked by comparing the previous release policy sample file json and new one and build the upgrade msg 06:49:08 yeah 06:49:40 or some more optimize way. 06:49:56 and some action to take for their custom policy config 06:50:53 yeah 06:51:41 that's all on this from my side. 06:51:54 me too 06:51:56 anything else alex_xu or we can close the office hour 06:51:58 ok 06:52:06 thank alex_xu for joining 06:52:10 #endmeeting