Earlier  
Posted Nick Remark
#openstack-nova - 2018-07-11
22:28:08 mriedem instance.availability_zone = (
22:28:08 mriedem availability_zones.get_host_availability_zone(context,
22:28:08 mriedem host.service_host))
22:28:17 mriedem which is an up-call to get aggregates in the api db
22:28:23 mriedem dansmith: ^ add it to the list :)
22:28:59 mriedem hmm, i wouldn't think it's possible to reschedule out of an az once you're initially scheduled into one
22:29:49 melwitt you can if you never requested a specific AZ and went to the default AZ. you won't necessarily stay in the default AZ during a move
22:30:12 mriedem i have a patch to test that..
22:30:22 mriedem https://review.openstack.org/#/c/567701/
22:30:26 melwitt so while a 'nova show' will show you're in the default AZ, your requested AZ is actually "None" aka I don't care what AZ I'm in
22:30:33 melwitt (this came up recently on our bug call)
22:31:51 mriedem https://bugs.launchpad.net/nova/+bug/1771860
22:31:52 openstack Launchpad bug 1771860 in OpenStack Compute (nova) "instance.availability_zone reports wrong az after live migration" [Medium,In progress] - Assigned to Matt Riedemann (mriedem)
22:32:01 mriedem so if you don't specify an az during server create, you can freely move across azs,
22:32:12 mriedem but if you do specify an az during server create, you must be restricted to that az during moves
22:32:26 melwitt right
22:32:33 edmondsw that's what I'd expect
22:32:33 mriedem for live migration if you don't specify an az on create and are live migrated to another one, we aren't updating the instance az
22:32:36 mriedem which is that bug fix
22:33:08 melwitt k, that makes sense
22:36:45 mriedem edmondsw: ok updated comments in your bug
22:36:50 edmondsw mriedem tx
22:37:15 mriedem hmm,
22:37:34 mriedem so we could put the az on the Selection object for a given host while we're in the controller and pass that down to the cell,
22:37:53 mriedem but there would be a window of time where the host could be moved into / out of an aggregate / AZ during the reschedule loop
22:37:59 mriedem not likely, and kind of tough luck if that happens...
22:38:29 mriedem this might also help us resolve up-call #5 at https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#operations-requiring-upcalls
22:38:37 mriedem when [cinder]/cross_az_attach=False
22:38:45 mriedem because the compute could get the host az off the Selection object
22:41:15 mriedem we really need a way to do split mq fixturization in our functional testes
22:41:17 mriedem *tests
22:41:42 edmondsw why does the AZ have to be set if the user didn't specify one? I assume it's to fill that on a later GET, but couldn't it just be populated dynamically there?
22:41:59 mriedem https://review.openstack.org/#/c/446053/
22:43:07 edmondsw so that's what caused it
22:43:11 mriedem yes,
22:43:13 mriedem i believe the reason is,
22:43:29 mriedem set the az on the instance at the top where we can reach aggregates in the api db,
22:43:32 mriedem so we don't need to do that in the computes
22:43:36 mriedem where we can't reach the api db
22:43:45 mriedem but dansmith would have to confirm that
22:44:08 mriedem "which isn't as useful to the things that need to consider what AZ the instance is actually in (without doing all the aggregate math to determine it on the fly)."
22:44:13 mriedem that reads "up call" to me ^
22:44:17 edmondsw but what needs to consider the AZ if the user didn't specify?
22:44:48 edmondsw e.g. we just said migrate wouldn't care about the AZ in that case
22:45:13 mriedem not sure off the top of my head honestly
22:46:10 mriedem maybe [cinder]/cross_az_attach=False ?
22:47:13 mriedem but as far as i know that is still broken
22:49:05 mriedem ugh, so we have a cache in nova.availability_zones,
22:49:15 mriedem but we don't populate it when calling get_host_availability_zone at the top
22:49:46 mriedem so when we get to the compute and check the instance.az (set at the top) against the host az from the cache, the latter is None and we say, 'the cache is invalid, so fetch the host az again'
22:49:47 edmondsw mriedem, actually git blame shows this was introduced with https://github.com/openstack/nova/commit/03b4c67b22f49d325386bc3ebd2ade79b44fa699
22:49:50 mriedem which is the up-call that fails
22:50:10 mriedem edmondsw: that's the same change
22:50:52 mriedem oh but the cache on the compute won't have the az set in it anyway
22:50:55 edmondsw oh, dang it it is... I saw "Updated 9 weeks ago" in that review and thought it was new, whereas the commit was old, and assumed they were different
22:51:00 mriedem b/c we get the host az at in a different process
22:51:14 mriedem unless you have a distributed cache...
23:14:36 mriedem edmondsw: fyi, your bug is also a problem for resize reschedules
23:23:40 openstackgerrit Matt Riedemann proposed openstack/nova master: Add another up-call to the cells v2 caveats list https://review.openstack.org/581910
23:24:46 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (6) https://review.openstack.org/574113
23:24:52 oomichi takashin: hi, can you check my comment on https://review.openstack.org/#/c/570842 ?
23:25:01 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (7) https://review.openstack.org/574974
23:25:56 takashin oomichi: okay. Thanks.
23:26:47 mriedem ha, just found another one
23:27:01 mriedem during a resize reschedule, compute casts to cell conductor's migrate_server method,
23:27:13 mriedem which has the targets_cell decorator on it which gets an instance mapping,
23:27:20 mriedem if you don't have access to the api db, kablammo
23:27:34 mriedem http://logs.openstack.org/27/581727/1/check/tempest-full-py3/15d7fdc/controller/logs/screen-n-cpu.txt#_Jul_11_13_32_54_822996
23:29:15 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (5) https://review.openstack.org/570842
23:31:31 mriedem https://bugs.launchpad.net/nova/+bug/1781300
23:31:32 openstack Launchpad bug 1781300 in OpenStack Compute (nova) "resize reschedule results in CantStartEngineError during up-call to InstanceMappings table" [Medium,Triaged]
23:57:17 openstackgerrit Matt Riedemann proposed openstack/nova master: Short-circuit targets_cell if already targeted https://review.openstack.org/581912
23:57:18 mriedem melwitt: dansmith: ^
23:59:00 openstackgerrit Matt Riedemann proposed openstack/nova master: Short-circuit targets_cell if already targeted https://review.openstack.org/581912
#openstack-nova - 2018-07-12
00:11:19 openstackgerrit melanie witt proposed openstack/nova-specs master: Add a script for counting blueprints https://review.openstack.org/581914
00:22:33 anupn Hi mriedem: I have a problem while launching instance on my baremetal instance inside Devstack.
00:22:59 anupn mriedem: I see a error message of "Failure prepping block device"
00:23:42 anupn when I ran "openstack server show". Any idea, what this could be?
00:24:45 anupn I checked few things like 1. inside n-sch logs is the respective host getting selected (it is). 2. hypervisor stats show, show correct information 3. resource provider are matching
00:42:33 mriedem attaching volumes in compute failed, check cinder and nova-compute logs
00:48:18 gmann mriedem: dansmith alex_xu yikun I agree with point of keeping consistency between API, Object layer. I am ok with 'policy' & 'rules' also. My vote it - "policy_*" is better. "policy & rules" are good (not bad)
01:12:43 arvindn05 mriedem: I updated the glance documentation to reflect the glance-image-traits spec functionality https://review.openstack.org/#/c/581920/
01:13:35 arvindn05 i will try to get the glance core's to approve it...but wanted to make sure you are fine with the amount of detail
01:45:29 mriedem gmann: arvindn05: ack, thanks
02:00:56 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy to InstanceGroup object https://review.openstack.org/563375
02:00:57 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object https://review.openstack.org/563401
02:01:51 yikun gmann: OK, ack~
02:05:36 openstackgerrit lei zhang proposed openstack/nova master: Replace ZeroMQ URL with Qpid URL https://review.openstack.org/581926
02:34:03 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Change the ServerGroupAntiAffinityFilter to adapt to new policy https://review.openstack.org/571166
02:34:04 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model https://review.openstack.org/571465
02:59:21 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (8) https://review.openstack.org/575311
02:59:35 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (9) https://review.openstack.org/575581
02:59:53 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (10) https://review.openstack.org/576017
03:11:28 openstackgerrit Takashi NATSUME proposed openstack/nova master: Transform libvirt.error notification https://review.openstack.org/484851
03:14:31 openstackgerrit Takashi NATSUME proposed openstack/nova master: Transform libvirt.error notification https://review.openstack.org/484851
03:55:53 openstackgerrit Chen proposed openstack/nova master: Clean up group members in db when delete https://review.openstack.org/581403
06:43:27 openstackgerrit jichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver https://review.openstack.org/523387
06:43:28 openstackgerrit jichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver https://review.openstack.org/527658
06:43:29 openstackgerrit jichenjc proposed openstack/nova master: z/VM Driver: add snapshot function https://review.openstack.org/534240
06:43:30 openstackgerrit jichenjc proposed openstack/nova master: z/VM Driver: add power actions https://review.openstack.org/543340

Earlier   Later