Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-01-22
19:50:11 mriedem those tests all default to send 2.1 so explicitly hard-coding something isn't necessary
19:51:14 melwitt dansmith: do you want to cook up a patch for that or should I?
19:51:32 dansmith melwitt: grilling one currently
19:51:38 melwitt sweet
19:53:58 jaypipes mriedem: that was originally in one of jackie's other patches that was unrelated and I had asked her to split it out.
19:54:07 openstackgerrit Eric Fried proposed openstack/nova master: Report Client: PUT empty (not None) JSON data https://review.openstack.org/536545
19:54:09 efried sdague jaypipes dansmith ^
19:54:47 efried Would rather not put it in the dep chain of the update_provider_tree series, but it's gonna foul my test cases for update_from_provider_tree (which is how I found it)
19:54:48 mriedem jaypipes: ok
19:54:52 jaypipes mriedem: without it, patches that test the new certificates REST API functionality were failing due to the personality stuff still being around for some reason
19:55:19 mriedem new tests should have just overrode the personality files stuff rather than need to hack up old tests
19:56:19 mriedem and...the mailman is stuck outside my house
19:56:37 openstackgerrit Sen Yang proposed openstack/python-novaclient master: Implement hypervisor hostname exact patten match for server cold migrate https://review.openstack.org/520187
19:56:37 mriedem he knows i work from home, so i guess i have to suit up now
19:59:06 openstackgerrit Dan Smith proposed openstack/nova master: Fix update_cell to ignore existing identical cells https://review.openstack.org/536546
19:59:07 dansmith melwitt: owalsh: ^
20:09:36 openstackgerrit Ed Leafe proposed openstack/nova master: Change compute RPC to use alternates for resize https://review.openstack.org/526436
20:09:43 edleafe mriedem: ^^ responded to your comments
20:13:49 dansmith melwitt: I think you meant assertFalse() when you pointed out my mind-o
20:14:46 openstackgerrit Dan Smith proposed openstack/nova master: Fix update_cell to ignore existing identical cells https://review.openstack.org/536546
20:14:56 dansmith melwitt: I had another bug in the test that that uncovered, but the functional code worked thankfully
20:14:57 melwitt dansmith: yes, heh. I was thinking 0 == no error == True for some reason
20:15:12 dansmith aye
20:15:45 mtreinish mriedem: yeah, not yet. But I need get that landed in glance soon
20:22:07 mtreinish mriedem: were you looking to use that option for something?
20:45:34 owalsh melwitt, dansmith: LTGM, thanks!
20:52:40 ildikov gibi: johnthetubaguy: mriedem: thank you!!! :)
20:53:11 bauzas mriedem: dansmith: gibi: rebased https://review.openstack.org/#/c/533642/ for cdent's comments about relnotes
21:03:37 openstackgerrit Eric Berglund proposed openstack/nova master: Add PowerVM to feature-classification https://review.openstack.org/533237
21:06:16 mriedem mtreinish: no, trying to figure out why the ironic multinode grenade job starting having random seg faults since 1/17
21:06:49 pooja Hello! Is it possible to use the Placement API in Newton with a non-cells deployment?
21:07:00 mriedem pooja: yes
21:07:43 pooja mriedem: Thanks! I am trying to go from Newton non-cells to Pike release with cells v2.
21:08:23 pooja So adding placement api in Newton and then upgrading packages to Pike and creating nova_cell0 and nova_cell1 databases would work?
21:09:03 mriedem pooja: placement and cells v2 don't really have anything to do with each other, so yes that should be fine
21:09:48 pooja ah okay, thanks! My understanding was it needed a cell for filtering hosts.
21:13:05 mriedem no placement doesn't know anything about nova internals
21:13:15 mriedem or deployment setup like cellsv2
21:13:23 dansmith and cells are not visible outside nova
21:17:04 mriedem jesus tempest-full is now 2 hours long
21:18:34 mriedem well maybe depends on the node you land on
21:19:40 mriedem rax dfw must be nice and slow
21:19:50 melwitt yeah, I was about to say we've been getting lots more job run fails related to timeouts, and I'm not sure if it's about the nodes or if it's about tempest run time creeping over the timeout line
21:20:11 mriedem one tempest-full i saw was 2 hours and 8 minutes, another was 1 hour and 20 minutes
21:20:18 melwitt ah, okay
21:25:40 mriedem seeing rpc messaging timeouts in cinder logs too on rax dfw
21:28:30 openstackgerrit Carlos Goncalves proposed openstack/os-vif master: [DNM] vif_plug_ovs: add should_provide_port https://review.openstack.org/533713
21:37:54 openstackgerrit Matt Riedemann proposed openstack/nova master: Start moving users of parted to privsep. https://review.openstack.org/519011
21:53:53 hongbin mriedem: hi matt, a question. i am looking at this bug: https://bugs.launchpad.net/neutron/+bug/1723026 , the use case there seems to require nova to add an api to support filter instances by floating ip. do you know if it makes sense to have this api in nova?
21:53:54 openstack Launchpad bug 1723026 in neutron "[RFE]Support get device_ids from floatingips" [Wishlist,Confirmed] - Assigned to Hongbin Lu (hongbin.lu)
22:11:55 mriedem hongbin: that doesn't seem like a nova api change, sounds like a neutron api change
22:13:30 mriedem hongbin: nova has deprecated all of it's floating IP related APIs since they were just proxies to neutron and nova-network is deprecated
22:13:52 hongbin mriedem: ack, i see
22:14:22 mriedem hongbin: is that RFE asking that GET /servers adds a query parameter to filter instances by floating IP substring? like the "ip" filter which filters on the fixed IP?
22:14:24 hongbin mriedem: thanks for the remarks
22:14:59 hongbin mriedem: per my understanding, yes
22:15:49 hongbin mriedem: but if nova thinks this doesn't make sense, i need to re-discuss this ref in neutron
22:16:31 mriedem well, i could see the floatingip filter param to GET /servers maybe, but it's just another proxy;
22:16:47 mriedem the best thing is probably to add something to neutron to allow filtering ports by floating IP substring?
22:17:35 hongbin yes, if nova is removing proxies to neutron, then this request doesn't seem to fit into the scope
22:18:47 hongbin yes, this can be done
22:19:04 hongbin however, the question from neutron team is if this will be used by nova
22:19:13 mriedem it won't,
22:19:20 mriedem unless we plumb something into the compute API to proxy that through when listing servers
22:19:31 hongbin yes, get it
22:20:20 hongbin mlavalle: ping, fyi (above)
22:20:38 mriedem if the requestor says, "well then i get the device_id from the port(s) and then i have to call the compute API to get server details and that's too much work" then i'd ask what they need from the server details beyond just the server uuid
22:21:35 openstackgerrit Merged openstack/nova master: libvirt: Collocate encryptor and volume driver calls https://review.openstack.org/460243
22:21:51 openstackgerrit Merged openstack/nova master: libvirt: Introduce disk encryption config classes https://review.openstack.org/464008
22:22:05 openstackgerrit Merged openstack/nova master: [api] Allow multi-attach in compute api https://review.openstack.org/271047
22:22:20 efried mriedem dansmith Easy fix, one +2 already, can I get a quick look please? https://review.openstack.org/#/c/536545/
22:23:33 hongbin mriedem: my understanding is that they want a new filter in nova (i.e. nova list --floating-ip <xxx>), and under the hook, nova calls neutron api with the device_id to query the floating ips
22:24:12 hongbin and the addition of device_id in neutron side is for nova to query the floating ips fast
22:24:53 mriedem hongbin: we do'nt know the device_id until we get the ports, which would be filtered by the floating IP the user passes in
22:24:54 mriedem right?
22:26:30 hongbin mriedem: yes, so the proposal said "make the device_id of floating ip same as the instance uuid"
22:26:51 hongbin then, nova uses the uuid as the device_id to query
22:27:05 hongbin s/uuid/instance uuid/
22:27:43 mriedem umm
22:28:31 mriedem so (1) list all instances, (2) then call neutron with all of those instance uuids to get the ports AND also filter the floating IPs from that list of ports by the provided floating IP substring match?
22:29:02 mriedem the port.device_id is the same as the instance uuid already
22:29:13 mriedem the port and floating IP have a relationship somewhere
22:29:29 mriedem so if you can list/filter ports by floating IP, you can build a list of server uuids
22:29:40 sean-k-mooney mriedem: i think the owner of teh floating ip in neutron is the port uuid
22:30:36 sean-k-mooney so really what you want to do is say neutron give be the owner of the port that has this uuid
22:30:43 sean-k-mooney * floating ip
22:31:37 hongbin (2) is performed only if users insert the --floating-ip filter when listing the instances
22:36:12 hongbin mriedem: yes, it is confusing, i will ask the bug reportor to clarify
22:38:19 mriedem if the request is just, "do the same thing as the ip filter but for floating ips when listing instances" then that's easy to understand
22:38:42 mriedem the ip filter works on fixed ips, the floating ip filter (being requested) works on floating ips
22:38:45 sean-k-mooney hongbin: mriedem this is the basic workflow today http://paste.openstack.org/show/650595/
22:40:11 sean-k-mooney the device id of the neutron port is the nova instance id so today tyou do a floating ip show by it ip then get the port_id it is bound to look up the port and then get the device id of the port
22:40:14 mriedem sean-k-mooney: the floating IP has a fixed IP on it
22:40:18 mriedem so,
22:40:21 mriedem nova list --ip 172.20.50.10
22:40:22 mriedem done
22:40:32 sean-k-mooney the fixed ips can overlap
22:41:00 sean-k-mooney e.g. one tenant can have two networks with the same subnet
22:41:06 mriedem i have a request,
22:41:12 mriedem can one of you hand me that shotgun in the corner?

Earlier   Later