Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-06-12
15:52:05 dansmith oh
15:52:07 dansmith sweet
15:52:15 mriedem that's queens<>rocky live migration both ways
15:52:35 dansmith yeah, but still, you're not going to always configure file-backed memory for that job, just a one-off yeah?
15:52:44 mriedem we could do it in a one off
15:52:48 mriedem or an experimental queue job
15:52:50 mriedem that's run on demand
15:52:54 dansmith aye
15:53:08 mriedem if someone wants to work on the devstack changes for that we could link it up
15:53:45 dansmith okay
15:54:04 zcorneli Would we be able to validate that old -> new+file_backed fails?
15:54:09 zcorneli ( / is rejected )
15:54:29 dansmith zcorneli: well, that's why it needs to be a one-off or something special I think
15:55:04 dansmith mriedem: in case it's not clear, because the sending host's libvirt gets to choose the xml for the destination, if it's old and doesn't know about this,
15:55:12 zcorneli dansmith: Ah. Wasn't catching that.
15:55:14 dansmith it will generate xml that violates the config of the remote side
15:55:29 dansmith mriedem: so we have to make sure to refuse to let an older node send to us if we're configured for this on,
15:55:37 dansmith basically a "don't turn this on until all your nodes are updated" kind of thing
15:56:10 kmalloc efried: +2 on the KSA change,
15:56:23 efried kmalloc: Nice, thanks. cdent ^
15:56:26 mriedem dansmith: isn't that this compute version check? https://review.openstack.org/#/c/567876/11/nova/virt/libvirt/driver.py@6529
15:56:31 cdent woot
15:56:36 kmalloc efried: once zuul weighs in, we can get it merged and (pending lbragstad's ok) released
15:56:46 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
15:56:47 openstackgerrit Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
15:56:48 efried kmalloc: Schweet
15:56:49 kmalloc efried: thanks for making it easy and maintaining base behavior(s)
15:56:49 openstackgerrit Chris Dent proposed openstack/nova master: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
15:56:54 stephenfin dansmith: If I set a default for an o.vo field, should I be able to do instance.field without needing the "if 'field' in instance" check?
15:56:56 dansmith mriedem: that's the dest checking the source
15:57:00 mriedem dansmith: zcorneli: but yeah - as noted in the change, i'd like to see admin config guide docs for this feature
15:57:09 mriedem which can explain the libvirt-only nature of it, and upgrade implications
15:57:19 dansmith stephenfin: no, obj_set_defaults()
15:58:14 mriedem dansmith: right, but check_can_live_migrate_destination is checking the service version of the source compute and if it's too old to know about this, it fails
15:58:27 dansmith mriedem: right
15:59:02 mriedem anyway, seems we're in violent agreement
15:59:06 dansmith mriedem: I'm saying failing is all it can do, it can't fix the xml later and still allow the migration or anything like that
15:59:11 mriedem also, channel topic needs to be updated for current runways
15:59:19 mriedem dansmith: i think that's fine
15:59:24 stephenfin dansmith: Ah. Before I do something that will make you cry, any reason not to do that in __init__? https://github.com/openstack/nova/blob/master/nova/objects/diagnostics.py#L107
16:00:14 openstackgerrit Merged openstack/nova master: Extract part of PlacementFixture to placement https://review.openstack.org/568359
16:00:21 dansmith stephenfin: in general I'm very much opposed to it, yeah, because if you have half an object (think fields not lazy-loaded yet) and you always do that, you'll blow away things in the DB you would have otherwise left as-is
16:00:52 dansmith stephenfin: so it depends on the type of object.. if it's stored as a blob, then *might* be okay to do that, but it is then confusing for other people when they find examples like you linked
16:01:38 stephenfin dansmith: I figured (else this would be done by default). What's the best practice, in that case?
16:01:45 stephenfin Call 'obj_set_defaults()' every time I need to create a new object or don't use defaults, perhaps?
16:01:49 cdent oh this is fun: AssertionError: u'host3' == u'host3' in http://logs.openstack.org/08/574408/3/gate/nova-tox-functional/39c1a57/testr_results.html.gz
16:01:53 cdent wtf?
16:02:21 dansmith stephenfin: well, defaults were really introduced for something else kinda stupid, and honestly we probably shouldn't have left that in when we moved to oslo, but alas
16:02:46 dansmith stephenfin: if you want to do it in init and you're sure you're always going to be right, just throw a scary comment on it or something
16:02:47 gibi cdent: assertNotEqual :)
16:02:55 cdent yeah, got there
16:02:57 cdent eventually
16:03:06 dansmith stephenfin: or use it whenever you instantiate, or when you need them to be set
16:03:11 gibi cdent: I also saw this test fails infrequently locally
16:03:28 dansmith stephenfin: or, how about you call it in obj_load_attr() ? then, it'll set defaults if you touch something that isn't set
16:03:37 dansmith stephenfin: but still, scary comment I tink
16:04:59 stephenfin dansmith: I can do that. Cheers :)
16:05:02 openstackgerrit Eric Fried proposed openstack/nova master: Provide a direct interface to placement https://review.openstack.org/572576
16:05:11 sahid efried: i hink you made good point for the ut here
16:05:21 sahid https://review.openstack.org/#/c/571030/
16:05:55 openstackgerrit Merged openstack/nova master: placement: Use INNER JOIN for requied traits https://review.openstack.org/573113
16:06:04 mriedem cfriesen: that's a known issue on a bug you've already investigated
16:06:13 mriedem http://status.openstack.org/elastic-recheck/#1763181
16:06:24 efried sahid: Yeah, figured that wasn't enough to hold it up, I would fast-approve a fup to fix that if you're so inclined.
16:08:19 sahid efried: i'm not
16:08:24 efried :)
16:08:33 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Add method to get cpu traits https://review.openstack.org/560317
16:09:32 cfriesen mriedem: sorry, you referring to the swap size thing?
16:09:44 mriedem cfriesen: no, the "wtf test failure" thing
16:10:05 mriedem oh oops
16:10:07 mriedem cdent: ....
16:10:10 mriedem sorry, too many c's
16:10:41 mriedem cfriesen: for the ceph swap size thing, i'd ask mnaser
16:10:50 mnaser hi
16:10:50 cfriesen no worries, I thought I had missed some context. :)
16:11:42 openstackgerrit Brianna Poulos proposed openstack/nova master: Implement certificate_utils https://review.openstack.org/479949
16:11:44 openstackgerrit Brianna Poulos proposed openstack/nova master: Plumb trusted_certs through libvirt driver image paths https://review.openstack.org/561262
16:11:44 openstackgerrit Brianna Poulos proposed openstack/nova master: Add trusted_image_certificates to REST API https://review.openstack.org/486204
16:11:45 openstackgerrit Brianna Poulos proposed openstack/nova master: Add notification support for trusted_certs https://review.openstack.org/563269
16:11:46 openstackgerrit Brianna Poulos proposed openstack/nova master: Add certificate validation docs https://review.openstack.org/560158
16:11:49 mnaser cfriesen, mriedem: we don't use swap (swap on ceph sounds rough) but do you have a bit more context or bug #?
16:12:19 mriedem mnaser:
16:12:20 mriedem (10:15:56 AM) cfriesen: is anyone aware of an issue where an RBD-backed swap disk is not restored to the initial size after a resize/revert? We're hitting this on Pike.
16:12:20 mriedem (10:16:47 AM) cfriesen: also, we're seeing a second issue where the guest has to manually re-run "mkswap" after a resize/confirm otherwise it still keeps using the old size of swap
16:12:36 cfriesen mnaser: haven't opened a bug yet, wanted to see if it was a known issue
16:12:54 mriedem mnaser: you use the rbd imagebackend don't you for ephemeral local disks?
16:12:58 mnaser mriedem: yes
16:13:05 mriedem how do you prevent users from attaching swap devices?
16:13:18 mnaser well, they could do it themselves by adding a volume
16:13:32 mriedem right, it's part of the block_device_mapping_v2 request when creating a server
16:13:32 mnaser i thought we're talking about the swap flavor attribute (that's a thing.. right?)
16:13:40 mriedem it's related
16:13:55 mriedem the swap bdm gets it's size from the swap value in the flavor
16:14:31 sahid efried: actually it would have been better to use a constant instead of 0, also since we have changed the method name it would have been better to refer a name with xen
16:14:58 cfriesen in the second case, I'm wondering whether we're copying/expanding the original ceph volume and not re-running mkswap on it, so the guest's on-disk data structures still show the "old" size
16:15:10 efried sahid: I can pull it out of the gate if you like.
16:15:41 mriedem https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1368
16:15:47 mnaser i think resize doesn't touch the underlying devices
16:15:50 mriedem i think you can create swap bdms with their own size not from the flavor
16:15:57 mriedem https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1375

Earlier   Later