Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-23
21:00:51 andreykurilin diana_clarke: https://github.com/openstack/python-novaclient/blob/master/novaclient/tests/functional/test_auth.py
21:01:00 andreykurilin there is only one place of testing auth stuff
21:04:46 diana_clarke andreykurilin: I'm only 50% sure that change is correct given the bazillion kwargs and similar environment variables. But if you're okay with it, I trust you :)
21:05:09 diana_clarke andreykurilin: I did manually test it, and it does indeed make the warnings go way.
21:05:49 diana_clarke And I suppose it does have all of pike to stew.
21:07:38 mriedem sfinucan: replied to your question in https://review.openstack.org/#/c/429413/
21:08:01 andreykurilin diana_clarke: actually, it looks like there is no need to transmit all those kwargs now. lol
21:09:01 andreykurilin they are ignored in case of sessionclient which we obtain via keystoneauth1 at cli layer
21:09:37 mriedem alex_xu: gmann: is the -1 on https://review.openstack.org/#/c/429476/ still just because of the nested decorated function or something else, like the allowed states?
21:10:55 andreykurilin diana_clarke: https://github.com/openstack/python-novaclient/blob/master/novaclient/shell.py#L748-L751 creates keystone session. session_constructor do not process anything in that case - https://github.com/openstack/python-novaclient/blob/master/novaclient/client.py#L135
21:11:32 openstackgerrit Lee Yarwood proposed openstack/nova master: db: Add attachment_id to block_device_mapping https://review.openstack.org/437597
21:11:33 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP objects: Add attachment_id to BlockDeviceMapping https://review.openstack.org/437665
21:12:45 mriedem lyarwood: i guess you got started early on that huh
21:13:20 andreykurilin diana_clarke: maybe it is time to simplify cli layer ;)
21:13:39 mriedem lyarwood: can you track those attachment_id changes against this blueprint? https://blueprints.launchpad.net/nova/+spec/cinder-new-attach-apis
21:16:14 thorst mriedem: hey, probably a common issue, but I’ve got a flight out tomorrow afternoon. If possible, think we could hit the PowerVM update item sometime in the AM?
21:16:35 mriedem thorst: yes
21:16:40 thorst thx
21:17:50 diana_clarke andreykurilin: So.... stupid question, but is this only in the devstack case, or are actual users going to see this warning for every nova command on ocata deploys?
21:18:47 alex_xu mriedem: i'm -1 for the allowed states as i remember
21:19:02 mriedem alex_xu: ok i replied again in there
21:19:13 alex_xu mriedem: checking just
21:19:18 alex_xu s/just/that
21:21:47 diana_clarke andreykurilin: I feel like the answer is yes, but honestly I'm really tired today & my brain is only half working.
21:22:25 gmann mriedem: alex_xu yea same me too for resize state. i am testing that on https://review.openstack.org/#/c/430587/
21:22:37 gmann and seems like 500, let me check compute log
21:23:12 mriedem gmann: note that won't hit this API unless it's using an FS style volume driver, like nFS
21:23:14 mriedem *NFS
21:23:28 andreykurilin diana_clarke: yes, everybody will see that warning in 100% of CLI usage
21:23:43 diana_clarke andreykurilin: So backport?
21:24:27 alex_xu mriedem: I agree we should fix it without microversion. Just think the case when states == PAUSED, isn't the case would return 500 to the user. we only fix the case without microversion which return 500
21:24:33 diana_clarke actually my brain does get why now :)
21:24:37 alex_xu s/when/like
21:25:01 mriedem alex_xu: w/o testing a snapshot of a volume-backed paused instance with NFS i can't assume that works
21:25:08 andreykurilin diana_clarke: I think yes, but I'm not a "stable maintainer", so it is better to ask mriedem.
21:25:09 mriedem we don't allow paused for normal volume-backed snapshot today
21:25:17 andreykurilin diana_clarke: Btw, can you extend your patch with release note?
21:25:46 gmann mriedem: humm yea, difficult to check the behavior
21:26:00 mriedem gmann: we have an NFS job
21:26:11 mriedem i just don't know if it's in the tempest experimental queue
21:26:21 gmann let me check
21:26:22 mriedem gmann: it is in the nova experimental queue though so you could probably test all of this with some depends-on
21:26:23 diana_clarke andreykurilin: Sure! (tomorrow) And then I'll backport too. Thanks for your time. Have fun at PTG!
21:27:30 andreykurilin diana_clarke: thanks! hope to see you at one of the next openstack events ;)
21:30:07 gmann mriedem: yea not on tempest side.
21:30:35 mriedem gmann: you could post a nova change that depends on my change and the tempest test and run the experimental queue
21:30:43 gmann yea
21:33:05 diana_clarke andreykurilin: Did they announce at the PTG where the next one will be? Is it in the US>
21:33:09 diana_clarke ?
21:33:32 andreykurilin diana_clarke: no, they do not have a final decision
21:34:18 diana_clarke Ah, that's the last I heard too. I just wondered if it was going to be a announced there.
21:36:46 andreykurilin diana_clarke: they made an announcement yesturday that they do not know when and where the next PTG will be helt
21:37:39 diana_clarke andreykurilin: Ah, thanks. Interesting times...
21:37:40 andreykurilin *held
21:37:46 openstackgerrit John Garbutt proposed openstack/nova-specs master: Enable cold migration with target host https://review.openstack.org/426636
21:37:58 andreykurilin yes)
21:58:10 mriedem everyone: in the nova PTG room: big ted's montana grill at 6:30 tonight, or meet in the lobby of the sheraton at 6:15 if you want to walk together
#openstack-nova - 2017-02-24
00:13:02 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/437732
00:20:22 openstackgerrit Li Yingjun proposed openstack/nova master: Error message should not include SQL command https://review.openstack.org/436773
00:51:40 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/437732
02:10:28 openstackgerrit m4cr0v proposed openstack/nova master: Fix spice channel type https://review.openstack.org/410076
02:46:33 openstackgerrit Balazs Gibizer proposed openstack/nova master: Short circuit notifiations when not enabled https://review.openstack.org/428260
08:19:58 danpawli1 Good morning. Could you review my PS https://review.openstack.org/#/c/436953/ ? Please :0
10:51:00 rcarrillocruz heya folks
10:51:32 rcarrillocruz i'm reviewing a PR for Ansible os_quota
10:52:10 rcarrillocruz didn't know there'sa 'floating-ips' quota on Nova
10:52:17 rcarrillocruz but there's also 'floatingip' in Neutron
10:52:21 rcarrillocruz how they are different
10:52:28 rcarrillocruz are floating-ips only relevant when using nova-net ?
10:53:01 rcarrillocruz mordred: ^ in regards to https://github.com/ansible/ansible/pull/21471
11:02:49 jaosorior gibi: what's the way to configure the notification topic for the versioned notifications?
13:30:19 openstackgerrit Ghanshyam Mann proposed openstack/nova master: DNM: testing 1657585 https://review.openstack.org/437898
13:51:46 johnthetubaguy rcarrillocruz: basically the Nova one was there for nova-network, this may help with extra context: http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/deprecate-api-proxies.html#limits-and-quotas
14:01:32 gibi jaosorior: hi! today it is hardcoded to 'versioned_notifications'
14:03:43 mriedem takashin: i thought there was a spec for this in ocata? https://review.openstack.org/#/c/407237/ or was that part of the abort cold migration spec and you split it out?
14:06:11 EmilienM sdague, mriedem: FYI https://bugs.launchpad.net/tripleo/+bug/1667679
14:06:11 openstack Launchpad bug 1667679 in tripleo "Setting quota fails saying admin project is not a valid project" [High,Triaged]
14:06:19 EmilienM https://github.com/openstack/nova/commit/f6fbfc7ff07b790ef052a759552c69429b3d79c7 broke us
14:06:53 takashin mriedem: It was a part of the abort cold migration spec and I split it out.
14:08:09 takashin mriedem: I proposed https://review.openstack.org/#/c/407237/ for Ocata, but it was not approved.
14:09:00 takashin mriedem: sorry, I proposed https://review.openstack.org/#/c/407237/ for Pike.
14:11:21 mriedem takashin: ok yeah i remember talking about this in ocata so i thought there was a spec for it before
14:13:08 takashin mriedem: "List/Show all server migration types" was included in "Abort cold migration" spec at first. It is PS 22 in https://review.openstack.org/#/c/334732/ .
14:13:29 takashin mriedem: But I split it out to another spec.
14:16:59 mriedem EmilienM: does tripleo setup a keystone v3 endpoint in the service catalog?
14:17:09 EmilienM mriedem: I'm pretty sure yes
14:17:29 mriedem where in the tripleo log haystack can i find the endpoints be created?
14:17:33 EmilienM in our stackrc, we just don't force v3 because in the past ironic inspector didn't support v3 auth
14:17:52 EmilienM mriedem: we're in design sessio now with my team, I need to focus on the session
14:18:03 EmilienM mriedem: maybe we can meet face 2 face during the morning
14:19:14 EmilienM mriedem: http://logs.openstack.org/65/437365/3/check/gate-tripleo-ci-centos-7-nonha-multinode/bcbd374/logs/var/log/httpd/keystone_wsgi_main_access.txt.gz
14:19:28 EmilienM we enable v3 for sure
14:21:47 sdague yeh, looking at it
14:25:11 sdague EmilienM: I wonder if keystone isn't reacting as expected - https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=list-projects-detail#list-projects
14:25:40 sdague actually - https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=show-project-details-detail#show-project-details
14:26:01 mriedem takashin: did you talk to vmware or xenapi virt driver people about abort cold migration?
14:26:42 mriedem to see if that was possible for them?
14:28:02 sfinucan tonyb: You know requirements stuff. Any chance you could explain why we need to install from upper-constraints [1] when we have an auto-generated requirements.txt file in-tree?
14:28:04 sfinucan [1] https://github.com/openstack/nova/blob/master/tox.ini#L13
14:30:31 tonyb sfinucan: u-c.txt is our statement about testing and compatibilty it specifies the exact version as opposed to requiremenst which give you a range

Earlier   Later