Earlier  
Posted Nick Remark
#openstack-nova - 2019-02-20
13:29:53 jangutter kashyap, jaypipes: don't get me wrong, I love tripleo. It's also one of the most scarily self-referential things I've ever come across.
13:30:56 mdbooth sean-k-mooney: Through what's almost certainly a bug, but one which goes down a rabbit hole I'm not interested in right now, I've ended up with a port bound on a compute host which neutron doesn't think it's bound on, causing LM failure. What's the best way to kick it so I can get on with my day?
13:31:28 jangutter jaypipes: I presume you're referring to tripleo-quickstart?
13:32:38 openstackgerrit Matt Riedemann proposed openstack/nova master: Check hosts have no instances for AZ rename https://review.openstack.org/509206
13:35:44 sean-k-mooney mdbooth: define bound. you could try a hard reboot but neutron is the souce of truth in this matter
13:35:55 jaypipes jangutter: no, I'm referring to larsks's phrase "tripleo standalone install" in a recent ML post
13:36:25 sean-k-mooney mdbooth: we recently merged a fix to prevent the network info cache form getting out of sync so that should fix nova db periodicaly
13:36:35 mdbooth sean-k-mooney: I suspect it's an agent issue. Bind fails on the destination. I just deleted the instance, though, so I'm guessing the mess is still there but as long as it doesn't affect me I don't care right now :)
13:36:44 jangutter jaypipes: that sounds like a standalone networked computer in my mind.
13:36:57 jaypipes I'm actually not sure what was meant.
13:37:33 mdbooth It was a failed LM. LM failed because ssh keys weren't configured. Haven't looked , but presumably we created ports on the dest prior to LM, then didn't clean them up properly when it failed.
13:37:55 mdbooth So second attempt to LM fails because port is already bound.
13:38:17 jangutter jaypipes: reading the mail, I think this is "standalone" vs "integrating with an external ... " etc.
13:38:53 larsks jaypipes: standalone tripleo: https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/standalone.html
13:39:20 larsks Single node tripleo deployment installed using the 'openstack tripleo deploy' command.
13:39:39 jangutter larsks: aaah, "standalone" vs "ha".
13:39:46 jaypipes interesting.
13:39:56 larsks jangutter: not exactly. "standalone" vs "multinode"
13:40:19 jaypipes probably better to call it "all-in-one" or "single-node", but ok
13:40:29 larsks Eh, I didn't name it :). But yes.
13:40:33 jaypipes :)
13:40:49 jaypipes larsks: k, thx for the heads up. looks like this is relatively new functionality.
13:41:25 larsks I think so. I believe it stems from wanting to handle underlcoud deployment the same way as overcloud deployment.
13:41:54 jaypipes it's all a little too inception-y for me.
13:42:05 jaypipes turtles all the way down ;)
13:42:11 jangutter larsks: and that's why I find tripleo so fascinating, going all in with self-referencing!
13:42:40 jangutter larsks: basically it's a scalability problem, where the problem is "how can I scale down to 1 node".
13:43:47 openstackgerrit Balazs Gibizer proposed openstack/nova master: Refactor _heal_allocations_for_instance (2) https://review.openstack.org/637954
13:43:47 openstackgerrit Balazs Gibizer proposed openstack/nova master: nova-manage: heal port allocations https://review.openstack.org/637955
13:44:54 mdbooth Eurgh. I forgot about that weird F29 iscsi bug when I provisioned this devstack >:(
13:45:21 stephenfin kaisers: sup?
13:46:21 kaisers stephenfin: updates to both CLs
13:46:49 kaisers stephenfin: mostly the open nits but check the is_sysd thing again, pls
13:46:58 stephenfin ack
13:47:35 sean-k-mooney larsks: why does triplo build its docs like that. it makes them really hard to read givent tha that you have 3 or 4 release togehter with 2-3 distros
13:48:24 larsks sean-k-mooney: I have no idea.
13:49:21 sean-k-mooney if it wasnt for the fact i like stephenfin sanity it woul be neice if he had time to fix that...
13:54:05 stephenfin sean-k-mooney: What about my sanity? :D
13:55:18 sean-k-mooney stephenfin: im suggesting that it may be damaged if you were to undertake reworking all the tripplo docs to be readable
13:55:32 stephenfin Oh, yeah, feck that
14:00:24 jangutter sean-k-mooney: once you get used to it, it's not so bad, but covering all the use cases you want to cover is going to drive you batty.
14:05:41 jangutter sean-k-mooney: would be better if the "LIMIT ENVIRONMENT SPECIFIC CONTENT" bit worked....
14:09:42 mriedem dansmith: down cells bp was technically dropped from runways yesterday. can we get the docs change merged since we can follow up with the admin guide stuff and because it's causing issues for other changes that need a new microversion (the rest api history doc means everyone has to rebase on this): https://review.openstack.org/#/c/635147/
14:11:23 NewBruce hey sean-k-mooney!
14:11:39 NewBruce hopefully i can be tied to the desk today! :)
14:13:30 mriedem sean-k-mooney: adrianc: i'm pulling https://blueprints.launchpad.net/nova/+spec/libvirt-neutron-sriov-livemigration from runways
14:14:21 adrianc miredem: ill re-add to queue
14:14:35 sean-k-mooney mriedem: ok.
14:18:59 mriedem jackding: jroll: https://blueprints.launchpad.net/nova/+spec/flavor-extra-spec-image-property-validation and https://blueprints.launchpad.net/nova/+spec/ironic-conductor-groups are in runways now
14:19:50 jroll thanks!
14:22:04 NewBruce sean-k-mooney - to avoid cluttering the main chat here have dropped you full details in a DM
14:23:15 kaisers stephenfin: thnx for seeing this through to the current state
14:23:24 sean-k-mooney NewBruce: just finishing a code review but ill pop over in a miniute
14:23:43 NewBruce no worries mate - working late tonight, so ill be here a while
14:23:53 NewBruce have been talking to mnaser about this as well
14:24:51 mnaser i mean it is kindof a nova bug :)
14:30:32 mriedem artom: replied to your questions about the tests in https://review.openstack.org/#/c/631948/
14:33:50 dansmith mriedem: got it up now
14:35:40 gibi efried, jaypipes: updated https://review.openstack.org/#/c/616239 based on what we agreed on Friday. If you could re-review that patch that would be awesome
14:36:03 openstackgerrit Surya Seetharaman proposed openstack/nova master: API microversion 2.69: Handles Down Cells Documentation https://review.openstack.org/635147
14:36:03 openstackgerrit Surya Seetharaman proposed openstack/nova master: [Doc Fix]Best practices for effectively tolerating down cells https://review.openstack.org/638173
14:36:13 bauzas gibi: I need to jump on your b/w series
14:36:21 bauzas gibi: later today
14:37:38 gibi bauzas: thanks in advance
14:58:52 jackding Need another core to approve https://review.openstack.org/#/c/603844/. It's been too long.
15:00:10 kashyap jackding: Hi, I have something unrelated to chat: CPU models
15:00:38 efried gibi: +2
15:01:48 kashyap jackding: So I recall you filed this one: https://review.openstack.org/#/c/620959/ (Select cpu model from a list of cpu models)
15:02:10 kashyap jackding: I thought you might be interested in this one: https://blueprints.launchpad.net/nova/+spec/cpu-selection-with-hypervisor-consideration
15:04:26 gibi efried_pto: thanks
15:04:39 kashyap I'll file a spec too. In short, the core proposal here is to replace the existing two libvirt APIs with the "hypervisor-literate" APIs, which are far more useful.
15:05:40 kashyap jackding: ^ It maps onto the comment I noted here: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L3900,#L3909
15:07:19 ysandeep #openstack-nova A quick query, If my nova backend of compute nodes is ceph. And I evacuate instance.. Will my root disk of instance (rbd in ceph) will remain intact or the root disk will reimage(Old disk will be deleted and a new disk will be created from image)?
15:08:28 mriedem ysandeep: if you're evacuating to another compute host sharing the same ceph cluster the root disk should remain
15:10:08 ysandeep mriedem, thank you so much .. Do you happen to have idea about - from which branch we have this feature?
15:11:00 mriedem ysandeep: that's been around a long time, that's why the evacuate api has an onSharedStorage parameter https://developer.openstack.org/api-ref/compute/?expanded=evacuate-server-evacuate-action-detail#evacuate-server-evacuate-action
15:11:09 mriedem having said that, i'm sure there have been bug fixes over the years
15:11:15 mriedem mdbooth probably knows best about that
15:11:39 ysandeep mriedem, thank you soo much.. really appreciate your help..
15:11:56 mriedem yw
15:11:57 mdbooth ysandeep: It remains intact.
15:12:13 ysandeep mdbooth, thanks
15:12:20 mdbooth ysandeep: Same for NFS.
15:13:22 openstackgerrit Adrian Chiris proposed openstack/nova master: Add free for claimed, allocated devices https://review.openstack.org/616120
15:13:22 ysandeep mdbooth, thanks, i will test for nfs also
15:13:23 openstackgerrit Adrian Chiris proposed openstack/nova master: Allow per-port modification of vnic_type and profile https://review.openstack.org/607365
15:13:23 openstackgerrit Adrian Chiris proposed openstack/nova master: Add get_instance_pci_request_from_vif https://review.openstack.org/619929
15:13:24 openstackgerrit Adrian Chiris proposed openstack/nova master: SR-IOV Live migration indirect port support https://review.openstack.org/620115
15:13:24 openstackgerrit Adrian Chiris proposed openstack/nova master: libvirt: auto detach/attach sriov ports on migration https://review.openstack.org/629589
15:13:48 jackding kashyap: noted, thanks
15:13:59 mdbooth ysandeep: Same for boot from volume too, fwiw.
15:14:08 kashyap jackding: Just wanted to give a heads-up, so we don't duplicate efforts :-)
15:15:01 jackding kashyap: sure thing.
15:15:02 artom mriedem, yep, saw that. I'll un-1 soon
15:15:16 artom I also reviewed that series ass-backwards by looking at the top one first
15:15:38 ysandeep mdbooth, yes i was aware for boot from volume(cinder volume) but I was not sure of nova disk(on cluster storage) and ephermal disk behavior
15:40:29 mriedem tssurya: i'll poke on your novaclient change https://review.openstack.org/#/c/579563/ later this morning to try and sort out the test issue
15:40:39 tssurya dansmith: feel free to author the documentation patch if its only those changes in your comments that need to change I can respin, but considering mriedem and you removed the votes I guess there are some obvious incorrect wordings
15:41:09 dansmith tssurya: it's fine, just let me finish the call I'm on and then I'll push up a rev
15:41:20 tssurya mriedem: yea thanks I am not sure why that address gets printed in the wrong order

Earlier   Later