Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-05-31
20:28:18 mriedem https://github.com/openstack/releases/blob/master/deliverables/ocata/os-vif.yaml#L29
20:28:28 mriedem https://github.com/openstack/releases/commit/1534b7016c66ba6707b299d58d938c93b6346e65
20:28:41 jaypipes hmmm.
20:28:46 mriedem we need a 1.4.2 for pike
20:28:48 mriedem to uncap pbr
20:28:57 mriedem that's what the reqs team is asking for anyway
20:29:21 jaypipes mriedem: doh. sorry. ok, coming up.
20:29:31 jaypipes mriedem: sorry, I'm out of my element with the release tooling.
20:30:18 mriedem dansmith: i imagine you're going to run a thrilling cells v2 meeting in 30 minutes?
20:31:10 jaypipes mriedem: so you're saying https://review.openstack.org/#/c/467173/ needs to be merged and then cut a 1.4.2 release of os-vif, yes?
20:32:46 mriedem idk, let me ask
20:32:59 jaypipes mriedem: or are they just asking to cut an os-vif release (i.e. push a 1.4.2 tag on os-vif)?
20:33:09 jaypipes mriedem: on the current sha
20:33:15 openstackgerrit dane-fichter proposed openstack/nova master: Add trusted certificates to InstanceExtras https://review.openstack.org/457711
20:33:21 mriedem i think ^ but it's unclear to me what pbr cap is being discussed
20:33:29 mriedem since i don't see pbr being capped
20:33:47 mriedem oh it was capped in 1.4.1 https://github.com/openstack/os-vif/blob/1.4.1/requirements.txt#L5
20:33:51 mriedem something at some point uncapped it
20:33:54 mriedem which is unreleased
20:34:20 mriedem yes so release for current sha
20:35:30 mriedem i don't see where that was uncapped so i'm a bit lost
20:37:48 dansmith mriedem: I imagine so
20:38:12 mriedem jaypipes: it's going to have to be 1.5.0
20:38:16 mriedem because 1.4.x is the ocata series
20:38:33 mriedem yeah https://github.com/openstack/os-vif/blob/stable/ocata/requirements.txt#L5
20:38:39 mriedem it's ocata that has pbr capped
20:39:06 jaypipes mriedem: https://review.openstack.org/469649
20:40:01 mriedem thanks - found the weirdo ocata change https://review.openstack.org/#/c/431683/
20:43:01 cdent mriedem: because clearly you don't have enough to think about, your devstack test of os-traits didn't seem to work: http://logs.openstack.org/36/469636/1/check/gate-tempest-dsvm-py35-ubuntu-xenial/94685c6/logs/devstacklog.txt.gz#_2017-05-31_19_56_23_031
20:44:27 mriedem cdent: i know, just pushed https://review.openstack.org/469636
20:44:50 cdent gold star
20:44:59 mriedem root beer scratch n snifff
20:45:06 mriedem the extra f is for fun
20:45:51 cdent I was hoping your previous attempt was going to work because it was so...tidy
20:48:19 openstackgerrit Merged openstack/nova master: Remove mox from nova/tests/unit/api/openstack/compute/test_virtual_interfaces.py https://review.openstack.org/448377
21:11:19 mriedem jgriffith: ildikov: it works http://logs.openstack.org/18/469618/2/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/39938f9/logs/screen-n-api.txt.gz?level=TRACE#_May_31_19_39_07_441549
21:14:16 ildikov mriedem: yep, sweet, I was looking into the logs too
21:14:22 ildikov mriedem: tnx!
21:18:21 openstackgerrit Matt Riedemann proposed openstack/nova master: Replace messaging.get_transport with get_rpc_transport https://review.openstack.org/469659
21:19:55 melwitt cdent, edleafe: I've got the initial code (tests are in the works) for the placement project/user stuff at https://review.openstack.org/#/q/topic:placement-project-user if you could sanity check that for things I've gotten wrong, I would appreciate it muchly
21:33:18 mriedem think i finally got the os-traits LIBS_FROM_GIT devstack patch working
21:33:51 edleafe melwitt: looking now...
21:34:17 melwitt thanks edleafe
21:35:29 melwitt dansmith: looking at the live migration hook thing, what was failing and how do we see it fixed by https://review.openstack.org/#/c/458537 ?
21:35:39 openstackgerrit Merged openstack/nova master: PowerVM Driver: SSP emphemeral disk support https://review.openstack.org/443189
21:35:55 dansmith melwitt: you only see it when you run with the devstack patch.. that one had a depends-on that devstack patch until the latest rev,
21:36:06 dansmith so you can look at some of the early patches,
21:36:18 dansmith or we can do a dummy patch that depends on the devstack patch and not this one if you want to see it
21:36:25 melwitt oh, I see. I'll do that, just haven't been in the loop of what is going on there
21:36:29 dansmith but this has to go before that one, so I broke the link now that it's clear it's good
21:36:31 dansmith yeah
21:36:35 dansmith s'all good
21:38:50 mriedem dansmith: heh, and since then,
21:38:58 mriedem we've disabled running ceph in the live migration job anyway
21:39:05 dansmith ah
21:39:14 mriedem https://github.com/openstack/nova/commit/994caa464efdbed3d684354d699cd79e41d7eb0f
21:39:18 dansmith well, this is correctness of devstack stuff, so probably still useful, but whatever you want to do
21:39:20 mriedem oh wait,
21:39:21 mriedem only for grenade
21:39:38 mriedem still runs for master live migration job non-grenade
21:42:30 mriedem dansmith: shouldn't NOVA_CPU_CONF default to NOVA_CONF and then default to the hard-coded path?
21:42:32 mriedem to be compatible?
21:42:56 mriedem ${NOVA_CPU_CONF:-${NOVA_CONF:-/etc/nova/nova.conf}}
21:42:59 mriedem or something
21:43:33 mriedem chances of that being a real world problem are slim to none though
21:44:15 dansmith not as of my patch in devstack
21:44:21 dansmith unless you mean before the patch in devstack lands?
21:44:30 mriedem correct
21:44:44 dansmith Hmm, I dunno I guess
21:44:50 dansmith I guess we wait and see if it fails?
21:46:46 mriedem cdent: passed http://logs.openstack.org/36/469636/3/check/gate-swift-dsvm-functional-ubuntu-xenial-nv/2f34544/logs/devstacklog.txt.gz#_2017-05-31_21_14_48_452
21:47:44 melwitt mriedem: which log file in the live migration job shows where ceph runs? I can never remember
21:47:56 mriedem console
21:48:14 melwitt ah, there we go. thanks
21:48:34 melwitt I missed it the first time I looked, somehow
21:49:26 mriedem jaypipes: +W on https://review.openstack.org/#/c/469625/
21:49:32 mriedem we'll get a release out once that's merged
21:56:51 openstackgerrit Matt Riedemann proposed openstack/nova master: Skip micorversion discovery check for update/delete volume attachments https://review.openstack.org/469668
21:57:11 openstackgerrit Matt Riedemann proposed openstack/nova master: Skip microversion discovery check for update/delete volume attachments https://review.openstack.org/469668
21:57:18 dansmith eff
21:57:20 dansmith gdi
21:57:23 dansmith so wanted to -1 mriedem for a typo
21:57:24 mriedem ha
21:57:40 mriedem you've got to be fast
21:57:52 dansmith 20 seconds seemed pretty fast
21:58:34 cfriesen speaking of typos, how's his test covfefe?
21:59:39 mriedem it's excellent
21:59:47 mriedem fabulous
21:59:48 mriedem the best
22:02:23 mriedem jaypipes: here you go https://review.openstack.org/469670
22:04:53 jaypipes mriedem: danke
22:24:18 mriedem efried: does https://review.openstack.org/#/c/443189/ mean we can close that bp for pike?
22:24:23 mriedem or is it carte blanche?
22:25:11 efried mriedem I wouldn't mind getting more function in; does closing the bp preclude that?
22:25:57 efried mriedem Also, there will be some small followup work on the already-merged codebase (from code comments in previous changes, following community stuff like resource provider work, etc.) - assume that stuff just gets to be regular non-bp-linked change sets.
22:27:01 mriedem the follow up cleanups are fine to be separate from the bp,
22:27:18 mriedem and i think the get_inventory() stuff can be tracked under whatever was used for the same thing in the libvirt driver
22:29:45 efried mriedem So if we want to propose more function, and the bp is closed, will those changes automatically get -2ed and punted to queens? (By "automatically" I of course refer to the turd in your pocket.)
22:32:58 mriedem i wouldn't close it then, but i'd rather it not churn on forever either
22:33:18 mriedem i want to close things out so we can focus reviews on stuff that's not done yet

Earlier   Later