Earlier  
Posted Nick Remark
#openstack-nova - 2018-08-08
06:25:39 alex_xu but it only say 'year out of range', maybe the code doesn't see the 2018, it will be another value
06:25:43 alex_xu yea
06:26:31 gmann let's move to next bug
06:26:43 gmann there is one high priority bug for href things
06:26:46 openstack Launchpad bug 1705663 in OpenStack Compute (nova) "Wrong href link returned when providing non-existed version in GET version API" [High,In progress] - Assigned to Zhenyu Zheng (zhengzhenyu)
06:26:46 gmann #link https://bugs.launchpad.net/nova/+bug/1705663
06:27:02 gmann i have not got chance to review Kevin_Zheng patch yet, alex_xu did you?
06:27:07 gmann i think he update the PS
06:27:41 alex_xu gmann: no, I forget that one, probably try it today
06:27:45 Kevin_Zheng o/
06:27:58 gmann alex_xu: thanks, i will also check but tomorrow only.
06:29:18 gmann that's all from me on bug things, anything from your side ?
06:29:59 alex_xu gmann: nothing from me
06:30:04 gmann #topic Open Discussion
06:30:30 gmann there is nothing on agend under open. if nothing we can close office houre early
06:35:16 gmann alex_xu: anything else ?
06:37:14 alex_xu nothing from me
06:37:26 gmann let's close then. thanks
06:37:32 gmann #endmeeting
06:37:34 openstack Meeting ended Wed Aug 8 06:37:32 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
06:37:35 openstack Minutes: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-08-08-06.02.html
06:37:36 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-08-08-06.02.txt
06:37:37 openstack Log: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-08-08-06.02.log.html
07:05:02 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: api-ref: fix min_version for parent_provider_uuid in responses https://review.openstack.org/579577
07:05:03 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: [placement] api-ref: add description for 1.29 https://review.openstack.org/589407
07:30:08 gibi good morning nova
08:10:47 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use placement 1.28 in scheduler report client https://review.openstack.org/583667
08:14:30 openstack Launchpad bug 1783635 in OpenStack Compute (nova) pike "Live migration failed.: AttributeError: 'Guest' object has no attribute 'migrate_configure_max_speed'" [High,Fix committed] - Assigned to Lee Yarwood (lyarwood)
08:14:30 ivve hey guys.. the new migrate_configure_max_speed in guest.py (fix in pike https://bugs.launchpad.net/nova/+bug/1783635) but from queens.. bandwidth=0 but is capped @ 1024KB/sec
08:15:02 ivve i've applied it manually for pike. 0 should be unlimited?
08:15:59 ivve domain_xml=None, bandwidth=0):
08:15:59 ivve def migrate(self, destination, migrate_uri=None, params=None, flags=0,
08:16:20 ivve seems to set itself to 1
08:16:39 ivve im no good at debugging this so asking for help :)
08:18:41 ivve note: cap is for entire host, not per vm
08:18:46 ivve instance..
08:21:13 lyarwood sahid: ^ I think bandwidth=0 is unlimited right?
08:21:23 lyarwood https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainMigrateSetMaxSpeed doesn't help
08:22:04 ivve it should be, but my migrations are 1024KB/sec capped
08:22:32 ivve just evacuated a host and watched my bridge.. 1024KB
08:22:41 ivve so it seems to set itself to 1
08:22:48 ivve 1MB/sec
08:24:33 lyarwood ivve: live_migration_bandwidth isn't set in nova.conf?
08:24:43 ivve is it meant to be set via nova configuration and/or metadata for hosts/instances?
08:24:51 ivve lyarwood: let me check!
08:25:43 ivve kinda stumbled upon this when i updated a pike
08:25:47 lyarwood ivve: https://github.com/openstack/nova/blob/stable/pike/nova/virt/libvirt/driver.py#L6939-L6942 - you should see it logged here as well btw
08:26:45 openstack bug 1783635 in OpenStack Compute (nova) pike "Live migration failed.: AttributeError: 'Guest' object has no attribute 'migrate_configure_max_speed'" [High,Fix committed] https://launchpad.net/bugs/1783635 - Assigned to Lee Yarwood (lyarwood)
08:26:45 ivve so im guessing more issues will follow, not only the fix in bug 1783635
08:27:12 ivve well actually im wrong
08:27:18 sahid lyarwood: yes but that can be overidden by the api call migrateToUri
08:27:20 ivve thats for openstack-ansible to fix
08:27:23 ivve i guess
08:28:08 lyarwood ivve: that's the only other fix on top of 16.1.4 to do with migration AFAIK
08:28:34 ivve lyarwood: you are right, the option is not even in nova.conf
08:29:23 ivve setting it now and restarting, sec for confirmation
08:30:05 lyarwood ivve: it should default to 0
08:30:17 lyarwood ivve: I was trying to ensure it wasn't set to 1
08:31:14 ivve it wasn't in the libvirt stanza at all
08:31:14 lyarwood sahid: it defaults to 0 there as well so I have no idea where 1 is coming from for ivve
08:31:21 ivve so im guessing defaults to 1 ? :D
08:31:41 sahid 1 is comming is you are using linux bridge
08:31:46 sahid to slow the migration
08:32:40 sahid to let neutron configure the network on destination node
08:32:49 sahid then neutron is sending an event to nova
08:33:00 sahid and the migration can run at full speed
08:33:43 lyarwood https://github.com/openstack/nova/blob/stable/pike/nova/virt/libvirt/driver.py#L6913-L6922 - yup my bad
08:34:41 lyarwood sahid: does LB send events back once it's done?
08:34:49 lyarwood sahid: is that why we are stuck at 1MB/s
08:36:29 ivve yeah im using linux bridges
08:38:21 ivve it seems it never speeds up
08:39:00 ivve i will confirm
08:41:58 sahid there are some fix in neutron as well
08:42:00 ivve perhaps neutron doesn't send the event. did it used to in pike 16.0.16?
08:42:23 ivve aye feels like im missing some dep. fixes :D
08:42:48 ivve i went from 16.0.16 -> 16.0.17
08:43:04 ivve there is also some issue between CPU i think
08:43:40 ivve different cpu hosts are whining and don't want to migrate at all ;)
08:44:12 lyarwood ivve: which version of neutron do you have?
08:44:24 lyarwood ivve: as sahid says this needs >=11.0.5
08:44:35 lyarwood ivve: https://review.openstack.org/#/c/510013/
08:47:44 ivve neutron-server 11.0.6.dev47
08:48:18 ivve possibly some configuration then?
08:49:19 lyarwood sahid: ^?
08:49:29 lyarwood ivve: are you seeing the debug line logged by the agent? `Port %s not found, will not notify nova.`
08:54:04 mdbooth owalsh: Did you see the Trilio thing on the ml?
08:55:14 ivve checking
08:58:23 sahid ivve: this part is in the agent, did you well upgrade neutron on the compute nodes?
08:59:50 ivve yes it seems to be the same version
08:59:59 ivve 11.0.6.dev47
09:00:12 ivve ah wait
09:00:16 ivve you mean agent version
09:01:05 ivve all agents pointing to that version
09:01:12 ivve 11.0.6.dev47
09:01:35 ivve however since i think backport was missed to pike on the migration guest.py perhaps more things were missed?
09:01:45 sahid hum..
09:02:06 sahid can you confiugre nova.conf in debug adn then start a live migration, then share the logs
09:02:07 ivve i can't see any port not found error messages related to the migrations...
09:02:18 ivve aye
09:02:40 sahid thanks

Earlier   Later