13:00:09 <alex_xu> #startmeeting nova api
13:00:10 <openstack> Meeting started Wed May  3 13:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:13 <openstack> The meeting name has been set to 'nova_api'
13:00:18 <johnthetubaguy> o/
13:00:20 <alex_xu> who is here today?
13:01:12 <mriedem> o/
13:02:04 <alex_xu> today is quiet, I think we just need quick go through the status
13:02:13 <alex_xu> #topic priorities
13:02:25 <alex_xu> #link https://review.openstack.org/457715
13:02:46 <alex_xu> ^ i guess this is the last patch nova api via wsgi
13:03:18 <alex_xu> #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-docs
13:03:20 <mriedem> yeah, the nova changes are merged or approved,
13:03:25 <mriedem> the grenade change has a +2,
13:03:33 <mriedem> i can ask dansmith to take a look at the grenade patch when he's around
13:03:42 <alex_xu> mriedem: cool
13:03:53 <alex_xu> mriedem: do you have the link for grenade change?
13:04:16 <mriedem> alex_xu: https://review.openstack.org/#/c/460543/
13:04:27 <alex_xu> mriedem: thanks
13:04:51 <johnthetubaguy> ah, I see, the depends-on for that devstack patch
13:05:31 <johnthetubaguy> mriedem: should we reach out to the new deployment team about this move? maybe thats been done already?
13:05:53 <mriedem> johnthetubaguy: was just thinking about pinging EmilienM for that
13:06:17 <EmilienM> o/
13:06:35 <alex_xu> what is the new deployment team?
13:06:56 <johnthetubaguy> EmilienM: wondering about the uwsgi stuff, and if you are are about it
13:06:57 <EmilienM> alex_xu: it's a Working Group where Deployment tool projects work together
13:07:08 <alex_xu> EmilienM: cool
13:07:12 <EmilienM> johnthetubaguy: I learnt about it yesterday
13:07:15 <EmilienM> how can TripleO help?
13:07:24 <EmilienM> do you want us to test the feature in Nova?
13:07:27 <mriedem> EmilienM: we've said in the past that when we make changes to grenade that we should give the deployment teams a heads up, do you think this change warrants that https://review.openstack.org/#/c/460543/ ?
13:07:33 <mriedem> that's needed for using uwsgi for nova in devstack on master https://review.openstack.org/#/c/457715/
13:08:03 <mriedem> this isn't a required change so i'd think we don't need to email the world about it
13:08:07 <sdague> mriedem: the grenade change is mostly a pin so we're not changing deployment infrastructure during upgrade
13:08:31 <johnthetubaguy> EmilienM: its all part of this, basically: https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
13:08:41 <EmilienM> mriedem: yes this change is useful for us, I'll take action in TripleO and see what can we do on our side
13:08:43 <sdague> the assumption is that upgrade happens first, then deployment changes post upgrade
13:08:58 <EmilienM> please keep pinging us on this kind of thing
13:09:08 <mriedem> do we need to email the ML about this?
13:09:21 <sdague> mriedem: about which thing?
13:09:39 <EmilienM> mriedem: most probably, with [nova][deployment] tags if you could
13:09:45 <mriedem> EmilienM: ok
13:09:52 <EmilienM> so deployment tools can learn about this information
13:10:09 <johnthetubaguy> sounds like a good plan
13:10:28 <mriedem> sdague: the note here https://docs.openstack.org/developer/grenade/readme.html#theory-of-upgrade
13:10:48 <mriedem> this isn't an exceptional upgrade change, but the fyi is good too i suppose
13:10:59 <sdague> mriedem: sure, I'm trying to understand what the issue is
13:11:04 <EmilienM> mriedem: I agree, thanks
13:11:22 <sdague> there are lots of pronouns (this) in the log here, but I lost the subject
13:12:13 <mriedem> https://review.openstack.org/#/c/460543/
13:12:17 <mriedem> this ^
13:12:36 <mriedem> we've just said in the past (ocata) that when making changes to grenade we'd inform the deployment teams
13:12:52 <mriedem> specifically for exception scripts like when we add something to a from_newton script,
13:12:56 <mriedem> which isn't the case here,
13:12:59 <sdague> mriedem: ok, the subject is "change needed to grenade to bypass new default in devstack master?"
13:13:03 <mriedem> but a courtesy fyi is ok too here
13:13:20 <mriedem> let's just move on
13:13:38 <alex_xu> #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-docs
13:13:47 <sdague> ok, I just want to make sure we don't confuse things more with people assuming they need to do something there
13:14:00 <alex_xu> I guess all the patches for policy doc are ready
13:14:02 <sdague> the actual deployer heads up is attempting to run wsgi by default
13:15:20 <johnthetubaguy> yeah, I plan on going through policy docs after the meeting
13:15:28 <alex_xu> after we merge those patches, we will know whether we stil left something
13:15:35 <alex_xu> s/stil/still/
13:16:07 <alex_xu> thanks to gmann's help
13:16:21 <alex_xu> #topic open
13:16:34 <alex_xu> #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-no-more-extensions-pike
13:16:58 <alex_xu> a lot of patch for this also, thanks to jichen, gmann and Kevin_Zheng
13:17:31 <sdague> looks like a lot of test failures right now, any ideas on those?
13:17:39 <sdague> most of them don't seem to be the live migration failure
13:17:40 <mriedem> probably the cells job
13:18:01 <mriedem> the cells job has been failing with unicodedecodeerror in the journal logger handler since we switched to systemd
13:18:12 <mriedem> http://status.openstack.org/elastic-recheck/#1580728
13:18:24 <johnthetubaguy> yeah, lots of cells failures I think
13:19:01 <alex_xu> I have seen a function test failure
13:20:21 <alex_xu> I will check whether we have bug for that later
13:21:51 <alex_xu> I also should take a look at other API impact BP, avoid all of those cleanup patch hide other stuff
13:22:51 <sdague> mriedem: oh, that's only on the cells job?
13:24:12 <alex_xu> here is the functional test failure http://logs.openstack.org/32/461732/2/check/gate-nova-tox-functional-ubuntu-xenial/83038b5/testr_results.html.gz
13:25:08 <johnthetubaguy> seems a related on here I guess: http://logs.openstack.org/09/460509/3/gate/gate-nova-tox-functional-ubuntu-xenial/9ca81aa/console.html
13:25:29 <johnthetubaguy> 2017-05-03 11:52:15,349 WARNING [nova.scheduler.client.report] Unable to refresh my resource provider record
13:26:08 <mriedem> sdague: it shows up primarily in the cells v1 job,
13:26:13 <mriedem> i have no idea why
13:27:32 <alex_xu> johnthetubaguy: here is the bug for functional test https://bugs.launchpad.net/nova/+bug/1674809
13:27:32 <openstack> Launchpad bug 1674809 in OpenStack Compute (nova) "test_create_server_with_pci_dev_and_numa functional test randomly fails with "OpenStackApiNotFoundException: Item not found"" [Medium,Confirmed]
13:29:27 <alex_xu> ok, anything more we want to talk about?
13:29:55 <alex_xu> I probably catch a time to take a look at that functional test failure
13:30:48 <alex_xu> ok, I guess no... next week probably most of people are in the summit, we probably just cancel the meeting
13:31:27 <alex_xu> 3...
13:31:32 <alex_xu> 2..
13:31:36 <alex_xu> 1.
13:31:50 <alex_xu> thanks all, let us back to nova channel
13:31:55 <alex_xu> #endmeeting