Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-07-19
15:32:07 mriedem yes i've seen the timeout exception holding the lock in the compute update_available_resource
15:32:07 cdent yeah, that’s probably a good idea
15:32:09 bauzas mriedem: it's ocata, so anyway you have to change that
15:32:25 mriedem the PlacementFixture was turned on relatively global for functional tests recently
15:32:34 mriedem so it's running in a lot more functional tests, whether we need it to or not
15:32:57 mriedem sdague: semi related we also did this globally https://review.openstack.org/#/c/483972/
15:33:25 mriedem we didn't have a fingerprint for it, but it seems to have helped a little bit from anecdotal evidence, meaning me not having to recheck on weird wsgi errors as much
15:33:55 sdague mriedem: yeh, I think I'd stop doing placement globally, that seems like a lot of complexity when you don't need it
15:35:52 mriedem TheJulia: does a 'vendor driver' in ironic mean an out of tree driver?
15:36:34 mriedem if the limitation is on fibrechannel support, then why not just say, iscsi is currently the only supported volume type
15:37:45 ftersin mdbooth: hi. could you please review that (https://review.openstack.org/#/c/407440/) again? i addressed your comments and wait for new ones.
15:39:15 openstackgerrit John Haan proposed openstack/nova-specs master: Support volume_type with BDM paramter https://review.openstack.org/466595
15:40:46 TheJulia mriedem: anything produced by a vendor, so it could be in or out of tree, in the terms I wrote, I meant in-tree vendor drivers.
15:41:15 mriedem ok, not sure why 'vendor' is even a distinction then
15:41:19 TheJulia mriedem: I'd prefer to just drop the tag completely due to confusion at this point
15:41:19 mriedem what's a non-vendor driver in ironic?
15:41:36 mriedem the ironic coop driver :)
15:41:43 TheJulia mriedem: agent_ipmitool, pxe_ipmitool, or the ipmi, redfish hardware types
15:41:47 mriedem bm traded for hemp
15:41:50 mriedem ok
15:41:52 TheJulia lol
15:42:31 mriedem ok, so if the iscsi volume type is the only one that's currently supported, that's what i'd clarify in the support matrix and release note
15:42:37 jaypipes jangutter: 483921 approved.
15:42:50 TheJulia mriedem: those are the drivers we're able to test in the gate since we can emulate the BMC of baremetal hardware in those cases.
15:43:41 TheJulia mriedem: okay, I just want to make sure or at least hopefully make sure nobody freaks out when we ask to amend the support matrix later without putting code in nova :)
15:44:07 jangutter jaypipes, sean-k-mooney: the people in the office just looked at me really oddly. I don't think they expected that kind of sound emitting from human vocal cords.
15:44:17 TheJulia mriedem: that being, when we have that support in place in our reference drivers
15:44:21 jaypipes jangutter: :)
15:44:32 _ix Good morning folks. I'm having a heck of a time migrating a host after a hypervisor failure.
15:44:40 mriedem TheJulia: meaning you can do this with other volume types
15:44:42 mriedem like fibrechannel
15:44:43 mriedem right?
15:44:55 _ix Waiting some 30 minutes for a single migration only to find an unsatisfying 401 error in the logs.
15:45:04 mriedem TheJulia: i think when there is >1 supported type, we'll just drop the note from the support matrix
15:45:21 mriedem _ix: token timeout?
15:45:24 mriedem cold or live migration?
15:45:31 _ix Cold.
15:45:38 mriedem if it's a cold migration of a large image, then the token probably timed out
15:45:53 mriedem which you should find in the nova-compute logs
15:46:02 TheJulia mriedem: yes, I'll revise that patch then in the next little bit to pull out the fc support in the matrix
15:46:32 mriedem TheJulia: ok there were other issues in there i pointed out, like the versioning thing, but i assume you're on top of all that
15:46:45 jaypipes TheJulia: don't forget to take the red pill.
15:46:53 mriedem _ix: fyi https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/use-service-tokens.html
15:46:58 _ix mriedem: I'll take a look. Thanks for the direction!
15:46:59 TheJulia mriedem: in the reno?
15:46:59 sean-k-mooney jaypipes: jangutter i think https://review.openstack.org/#/c/485125 is the last patch that is needed before we can make the os-vif release
15:47:12 mriedem _ix: in ocata, you could configure nova to provide a service token for long-running tasks that involved cinder or neutron,
15:47:12 jaypipes sean-k-mooney: yup, got that up in gertty now.
15:47:15 mriedem that was expanded to glance in pike
15:47:24 TheJulia jaypipes: I took the red pill a long time ago.
15:47:29 jaypipes :)
15:47:30 _ix mriedem: This is... Juno.
15:47:40 mriedem _ix: well then you're f'ed :)
15:47:44 _ix Ha!
15:47:49 mriedem _ix: increase the token timeout i guess?
15:47:51 mriedem idk
15:47:59 _ix Is that in the nova.conf of the losing host?
15:48:06 mriedem yeah
15:48:17 mriedem but that service token stuff relies on things in keystone too
15:48:23 mriedem so you likely can't backport any of that to juno
15:48:42 mriedem TheJulia: yeah, >= 8.0 is wrong
15:49:19 TheJulia mriedem: any objection to just saying pike release?
15:49:41 mriedem ironic doesn't have a "pike" release does it? i thought ironic was too cool for such naming and boundaries
15:49:46 mriedem hence the release with intermediary tag
15:50:07 _ix mriedem: Is an 80gb ephemeral considered large?
15:50:18 mriedem _ix: 80gb is pretty large
15:50:36 _ix I suspected as much. Seems like the 20gb ephemerals migrated without issue.
15:51:06 jangutter sean-k-mooney, jaypipes: thanks. I think it's wise for the Mellanox CI to have the final say.
15:51:07 TheJulia mriedem: well, we've not cut 9.0 yet, so saying 9.0.0 is technically invalid as well
15:51:13 mriedem jaypipes: you have a handle on https://review.openstack.org/#/c/483565/ today?
15:51:28 mriedem TheJulia: that's why i said, >8.0
15:51:56 TheJulia ahh, yeah, that actually works
15:52:00 mriedem if there is 8.0.1 or 8.1 then idk
15:52:02 TheJulia because there is not an 8.x
15:52:05 mriedem ok
15:53:34 jaypipes mriedem: yeah.
15:53:52 jaypipes TheJulia: do you ever wish there was a --ffs-only option? :)
15:53:57 openstackgerrit Merged openstack/os-vif master: Add support for VIFPortProfileOVSRepresentor https://review.openstack.org/483921
15:54:11 TheJulia jaypipes: many times
15:54:17 _ix mriedem: I'm not seeing anything regarding timeout options for keystone_authtoken. Any other ideas?
15:54:49 TheJulia jaypipes: only reason I don't have an alias to bring the repo to the current state of master is because I may loose my current mental state of where things are at
15:54:56 ralonsoh stephenfin: hi. Can you take a look at https://review.openstack.org/#/c/449257/ and https://review.openstack.org/#/c/451777/? It could be a pity not to have this for Pike
15:55:03 jaypipes TheJulia: yup, same.
15:55:23 _ix mriedem: It also has a large volume attached in addition. Perhaps I need to detach before attempting to migrate?
15:56:08 mriedem _ix: the volume should be fine
15:56:24 mriedem nova will detach the volume on the source host and attach it on the target host
15:56:32 _ix Maybe a red herring, but the 401 appears to becoming from cinder?
15:57:19 mriedem _ix: at this point debugging a juno problem is beyond the realm of time i can spend on this
15:57:33 _ix mriedem: I understand. I appreciate the time you did give me.
15:57:36 mriedem what i can tell you is,
15:57:42 mriedem if the call is coming from within the house, get out
15:57:51 _ix To be fair, we're preparing for an upgrade in the coming months!
15:57:55 mriedem good luck
15:58:10 _ix Thanks.
15:58:16 jaypipes edleafe: hi! would you mind providing your opinion on ralonsoh's os-traits patch here? https://review.openstack.org/#/c/483451
15:58:35 jaypipes edleafe: I suppose I could go either way, but would appreciate another opinion.
15:58:40 jaypipes alex_xu: you too ^^
15:59:27 edleafe jaypipes: ok, will look in a bit
15:59:39 jaypipes edleafe: cheers
16:00:51 cdent can I look too jaypipes or is it seeekrit?

Earlier   Later