Earlier  
Posted Nick Remark
#openstack-nova - 2018-04-09
17:02:27 dansmith which is local delete nuking allocations
17:04:39 edleafe jaypipes: no dice on default="0"
17:04:43 edleafe jaypipes: same error
17:05:34 jaypipes :(
17:12:31 mriedem dansmith: yeah that's a latent bug, which i've had sitting in my todo list,
17:12:36 mriedem i'll tackle it at 3pm on friday :)
17:12:58 dansmith that's fine, just don't expect me to be around for it :)
17:13:14 mriedem you said you'd always be there for me
17:14:16 mriedem avolkov: some easy changes to make in https://review.openstack.org/#/c/511183/ - just got feedback from dtroyer too
17:14:35 mriedem although i know it's late in the day for you
17:23:21 mriedem dansmith: when you get a sec, there is a mini debate in my patch to wait for vif plugged events before starting live migration that could use your input https://review.openstack.org/#/c/558001/ - some of it around whether or not we should even fail if we timeout, which thinking back on sahid's recent patch for linuxbridge, that doesn't fail on timout, it just logs a warning and continues
17:23:34 openstackgerrit Merged openstack/nova-specs master: mirror nova host aggregates to placement API https://review.openstack.org/545057
17:23:51 dansmith mriedem: no, I made him fail if it times out
17:24:09 mriedem yeah i see that now https://github.com/openstack/nova/blob/e2d5dc4e2c5f69fcbcb04c29b2ed469725122787/nova/virt/libvirt/driver.py#L7429
17:24:21 mriedem so it's totally unconditional based on the CONF.vif_plugging_is_fatal option
17:24:58 dansmith if we're expecting an event and don't get it, we should fail just about anything, IMHO, except if we're waiting during delete or something
17:25:08 mriedem that was basically my reply in my patch
17:25:13 mriedem if i set this, i expect an event
17:25:26 mriedem fail if it doesn't happen
17:25:55 dansmith totes
17:33:30 mriedem dansmith: on https://review.openstack.org/#/c/558059/4/nova/compute/manager.py@368 did you want to update that and add yourself as co-author?
17:33:34 mriedem otherwise the change lgtm
17:33:54 mriedem ill leave it up to efried and jaypipes to love up on it otherwise
17:35:34 dansmith mriedem: I don't care, but if you want blame-sharing I'll be glad to
17:35:47 mriedem updated that comment, event.key is probably ok
17:36:00 mriedem so just drop the wip if you don't want co-blame
17:36:20 dansmith done
17:41:39 efried mriedem, dansmith: +2. Who's gonna be the second +2?
17:42:00 mriedem i only mentioned two people to love up on it
17:50:08 zzzeek_ jaypipes: server_default in SQLAlchemy for a DEFAULT clause
17:50:36 dansmith ah, now that does sound familiar
18:09:22 edleafe zzzeek_: Hey, can you take a look at a migration issue I'm having?
18:09:47 jaypipes zzzeek_: we've tried adding and removing server_default with no luck...
18:10:35 edleafe jaypipes: I tried the recreate, import, drop, rename dance, but it seems to have a problem with the autoincrement
18:11:01 mriedem dansmith: just need a simple unit test add to https://review.openstack.org/#/c/539590/ and i'm +2
18:11:14 mriedem i know that's an older series
18:14:41 dansmith oh yeah, forgot about that
18:16:41 hanish_ hi all, i am trying to launch vm, but i am facing timed out error in nova conductor, can someone help me on thos
18:20:27 esberglu mriedem: Should I put the new powervm conf group in the features category or upgrade category in the release note?
18:20:31 esberglu All the other conf related stuff is in upgrade, but I haven't found any adding new group, just moving existing groups
18:20:42 esberglu Feature seems more accurate to me
18:24:13 openstackgerrit Merged openstack/nova master: libvirt: Block swapping to an encrypted volume when using QEMU to decrypt https://review.openstack.org/544238
18:27:06 mriedem esberglu: let me check to see what this is actually doing
18:28:33 esberglu mriedem: Allows a user to specify how much of a physical proc to assign each vCPU
18:29:40 mriedem yeah, don't worry, i've got the fine toothed comb out now
18:33:36 openstackgerrit Merged openstack/nova master: Avoid dumping stack on BuildAbortException https://review.openstack.org/559751
18:34:00 mriedem esberglu: comments inline
18:35:27 mriedem esberglu: what's with the flavor extra spec mention?
18:35:35 mriedem is that something yet to be added?
18:40:14 esberglu mriedem: Added that flavor extra spec mention after comments from edmondsw
18:40:56 edmondsw what commit?
18:41:21 esberglu edmondsw: https://review.openstack.org/#/c/554688/3/nova/conf/powervm.py@30
18:42:45 mriedem i'm ok with blaming things on edmondsw
18:42:51 edmondsw works for me :)
18:43:24 edmondsw yeah, we shouldn't mention that if it's only an OOT thing
18:43:38 mriedem i don't even see it in the out of tree driver
18:43:39 edmondsw I didn't realize that was only OOT
18:43:47 edmondsw looking...
18:44:00 openstackgerrit Matt Riedemann proposed openstack/nova master: Log a warning and add nova-status check for old API service versions https://review.openstack.org/557506
18:44:10 mriedem https://github.com/openstack/nova-powervm/search?utf8=%E2%9C%93&q=proc_unit_factor&type=
18:44:55 zzzeek_ jaypipes edleafe I can look later, though Im not sure SQLite even supports ALTER TABLE for a server default if that's your target DB
18:44:56 mriedem i found https://github.com/openstack/nova-powervm/commit/4bad1ec1654b757c70100fbcc6f51505719d79d9 - and this setting is in the pypowervm lib
18:45:36 esberglu proc_units_factor not proc_unit_factor
18:45:51 zzzeek_ jaypipes edleafe oh but if this is nova / sqlalchemy-migrate then that's another wrinkle
18:46:01 edleafe zzzeek_: it's in one of the functional tests
18:46:08 edmondsw mriedem esberglu misnamed: https://github.com/openstack/nova-powervm/blob/1dc302b7198ad749dc14cc69cf8f2e45e929d132/nova_powervm/virt/powervm/vm.py#L248-L250
18:46:26 zzzeek_ edleafe: add me to the review and ill try to look later
18:46:50 edleafe zzzeek_: k - thanks
18:46:59 mriedem edmondsw: esberglu: ok, so...
18:47:09 mriedem you're upstreaming a thing from the out of tree driver,
18:47:10 edmondsw and those are in nova as well as nova-powervm
18:47:13 edmondsw no
18:47:15 mriedem for a flavor extra spec that's not part of the same series
18:47:22 edmondsw is is already in nova
18:47:41 mriedem ok powervm:proc_units is in nova yeah i see
18:47:52 mriedem ok can we unclusterfudge the commit message on this along with the config option help and such?
18:47:59 edmondsw https://github.com/openstack/nova/blob/master/nova/virt/powervm/vm.py#L379-L381
18:48:16 edmondsw yeah, we'll get the right extraspec(s) mentioned
18:48:22 edmondsw good catch, tx
18:48:25 mriedem the default matches what's in the out of tree driver,
18:48:30 mriedem but not what you'd get today with the in-tree driver
18:48:36 mriedem i don't know how you want to resolve that
18:48:42 edmondsw mriedem that's part of the reason for this change
18:48:42 mriedem i'm inclined to not care about the out of tree default
18:49:03 edmondsw the default in the nova driver was not great... and we definitely want it to be consistent
18:49:43 edmondsw it was always meant to be 0.1 by default
18:49:59 mriedem why not change the default in the library?
18:51:19 edmondsw mriedem because pypowervm is used by folks, whereas the powervm driver in nova isn't yet
18:51:54 mriedem if folks are using the out of tree driver, they are getting the out of tree default config opt value, not what's in the library
18:51:55 mriedem yeah?
18:52:00 mriedem but lowly in-tree driver is
18:52:51 edmondsw I mean folks are using pypowervm directly, not only via the oot driver
18:53:02 mriedem folks == powervm?
18:53:05 mriedem *powervc
18:53:19 edmondsw not powervc... it uses nova-powervm
18:53:20 edmondsw but others
18:53:26 mriedem oVirt on Power
18:53:27 mriedem got it :)
18:53:38 edmondsw non-OpenStack folks
18:54:21 edmondsw basically, this is a goof, we release changing the default in nova is lousy, but it was just the best solution in this case

Earlier   Later