| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-09-08 | |||
| 16:15:22 | mikal | mriedem: it would be good to explain the underlying ideas to core so that they know what to look for | |
| 16:15:23 | cdent | mordred: cool. we put it on the api room etherpad, so it is a known topic but I suspect we’ll have to chat about it multiple times to get all the right people | |
| 16:15:51 | mikal | mriedem: but it is my pleasure to serve and you can just wake me up from my nap whenever you need me | |
| 16:16:03 | mikal | Us funemployed bums only go to sessions which look personally interesting | |
| 16:16:07 | mikal | Or have snacks | |
| 16:16:52 | alaski | The issue as I saw it is that the scheduler was extensible, but that extensibility had ramifications on the API. So there was no way, given what was in place, to enforce uniformity across deployments. e.g. cloudA could have an 'affinity' hint and cloudB could have a 'closeness' hint that meant the same thing, or two cloud could have an 'affinity' hint that meant different things. | |
| 16:17:55 | alaski | Discovery of what is available is a big help, but there's a second layer issue of understanding what the discovered capability actually means | |
| 16:18:39 | mriedem | alaski: yeah, exactly | |
| 16:19:30 | mriedem | so you can maybe write something that understands how the common hints in nova work, and then at least check if they are available in cloud A and B (which are your preferred clouds in this case), | |
| 16:19:48 | mriedem | and then if you also know that cloud B has this other "fancy" hint, you can use that if it's available, otherwise you dont | |
| 16:22:36 | alaski | yeah. Understanding and discovering in-tree hints would be a huge boon. And then discovery of "custom" hints would be a nice addition for those who understand what they mean | |
| 16:24:37 | mriedem | sean-k-mooney: i could have sworn you had something about bandwidth-based scheduling in the nova ptg etherpad, linking to the neutron spec https://review.openstack.org/#/c/396297/ | |
| 16:24:41 | mriedem | but i can't find it now | |
| 16:24:52 | mriedem | oh it's in here https://etherpad.openstack.org/p/nova-ptg-queens-generic-device-management | |
| 16:25:01 | cdent | the etherpad that consumes all topics | |
| 16:27:23 | mriedem | yeah no crap | |
| 16:27:33 | mriedem | some of that is going to be during the neutron slot | |
| 16:27:39 | mriedem | otherwise friday morning probably | |
| 16:39:45 | tonygunk | softball question: I recently changed to shared nfs for /var/lib/nova/instances on compute nodes for live migration. Getting this error and want to know where to look: | |
| 16:39:46 | tonygunk | http://paste.openstack.org/raw/620738/ | |
| 16:40:19 | tonygunk | nova.compute.manager Stderr: u'qemu-img: Could not open \'/var/lib/nova/instances/b1b9c5c9-da00-4b2c-bc11-784c0da18b32/disk\': Failed to get shared "write" lock | |
| 16:40:55 | openstackgerrit | Ildiko Vancsa proposed openstack/nova master: WIP: Allow multi-attach in compute api https://review.openstack.org/271047 | |
| 16:40:57 | openstackgerrit | Ildiko Vancsa proposed openstack/nova master: libvirt: Allow multiple volume attachments https://review.openstack.org/267587 | |
| 16:44:31 | cdent | tonygunk: are you sure you have all your necessary daemons running? I can’t remember the details on linux, but maybe rpc.lockd? | |
| 16:44:51 | cdent | or rpc.statd | |
| 16:49:22 | tonygunk | I'll look into that thanks | |
| 16:58:41 | openstackgerrit | Sean Dague proposed openstack/nova master: Refactor ServerMovingTests for non-move tests https://review.openstack.org/498596 | |
| 17:00:51 | openstackgerrit | Matthew Booth proposed openstack/nova master: Automatically revert resize which fails on destination https://review.openstack.org/462521 | |
| 17:00:52 | openstackgerrit | Matthew Booth proposed openstack/nova master: Use Migration object in ComputeManagerMigrationTestCase https://review.openstack.org/502126 | |
| 17:00:52 | openstackgerrit | Matthew Booth proposed openstack/nova master: Ensure errors_out_migration errors out migration https://review.openstack.org/479802 | |
| 17:15:43 | tonygunk | all daemons running fine on nfs server | |
| 17:18:06 | cdent | tonygunk: I’m not certain but I think you need some of it on the client too, but my info may be out of date | |
| 17:59:47 | mriedem | huh, horizon has a page for selecting scheduling hints when creating a vm | |
| 17:59:57 | mriedem | so i guess that must be plugged into the dashboard config somewhere | |
| 18:00:22 | cburgess | mriedem It comes from glance. | |
| 18:00:22 | mriedem | the fun things i find when i use horizon once per year | |
| 18:00:31 | mriedem | cburgess: scheduler hints? | |
| 18:00:35 | mriedem | you mean image meta? | |
| 18:00:59 | cburgess | mriedem Yeah... there is some facility in glance now to load up a bunch of arbitrary metadata that horizon then pulls to display all that. | |
| 18:01:02 | cburgess | Let me find it... | |
| 18:01:06 | mriedem | yes i know about that | |
| 18:01:08 | mriedem | this isn't that | |
| 18:01:22 | mriedem | https://github.com/openstack/glance/tree/master/etc/metadefs | |
| 18:01:27 | mriedem | ^ is the glance image meta stuff | |
| 18:01:51 | cburgess | mriedem You sure horizon isn't just pulling data from there for the scheduler hits as well? | |
| 18:02:06 | mriedem | glance image meta has nothing to do with scheduler hints in nova | |
| 18:02:33 | cburgess | mriedem I know that.. glance metaref has nothing to do with nova at all. YOu can load any arbittary thin you want. But its how horizon populates all those fancy pull downs. | |
| 18:02:57 | mriedem | chet, who is on first? | |
| 18:03:05 | cburgess | mriedem LOL | |
| 18:03:07 | cburgess | Fair | |
| 18:03:40 | cburgess | mriedem I haven't used horizon in a while either.. what panel is that being displayed in? | |
| 18:04:35 | mriedem | there is a scheduler hints sub-panel during 'launch instance'o | |
| 18:04:39 | mriedem | it's empty | |
| 18:04:48 | mriedem | so it must be something an admin can configure in horizon | |
| 18:07:49 | cburgess | mriedem I see glance metarefs that have a type association of OS::Nova::Server and a target of "scheduler_hint". | |
| 18:08:07 | cburgess | https://github.com/openstack/glance/blob/master/etc/metadefs/cim-processor-allocation-setting-data.json#L25-L28 | |
| 18:08:36 | cburgess | I don't actually see anything that is a hint in that file though. | |
| 18:08:47 | mriedem | i don't know what "CIM Processor Allocation Setting" has to do with that | |
| 18:10:50 | cburgess | mriedem All I'm saying is that if you look under the hood I suspect that horizon is pulling a list from the metaref some how. | |
| 18:12:17 | mriedem | robcresswell: question! | |
| 18:12:20 | openstackgerrit | Merged openstack/nova master: Amend the code review guide for microversion API https://review.openstack.org/494173 | |
| 18:12:25 | mriedem | i don't know where under the hood to look | |
| 18:13:21 | cburgess | mriedem Thats my problem too :( | |
| 18:13:55 | cfriesen | is anyone aware of an issue where snapshotting a boot-from-volume instance results in a valid image but with a reported size of 0? | |
| 18:14:15 | cburgess | cfriesen Define valid? | |
| 18:14:25 | cfriesen | cburgess: you can boot an instance from it | |
| 18:14:43 | mriedem | cfriesen: i think that's 0 because, | |
| 18:14:54 | mriedem | the image snapshot meta has some block device mapping stuff in it, | |
| 18:14:55 | cburgess | cfriesen Well thats cute, no I've not seen that.. I've seen snapshooting a BFV instance and you end up with a 0 size image that contains no data. | |
| 18:15:00 | mriedem | so when you use that image to create another server, | |
| 18:15:03 | mriedem | it does boot from volume | |
| 18:15:09 | mriedem | and creates a new volume from the volume snapshot | |
| 18:15:14 | mriedem | we have a test like that in tempest | |
| 18:15:54 | mriedem | https://github.com/openstack/tempest/blob/master/tempest/scenario/test_volume_boot_pattern.py#L196 | |
| 18:15:58 | cfriesen | mriedem: okay, I'll try to reproduce and see exactly what's going on....could be our testers aren't testing what they think they are. :) | |
| 18:16:10 | mriedem | ^ has caused me lots of pain in the past | |
| 18:16:17 | mriedem | we used to have a really nasty race fail with that one | |
| 18:16:35 | openstackgerrit | Merged openstack/nova master: Move libvirt usages of chown to privsep. https://review.openstack.org/471972 | |
| 18:16:37 | mriedem | in the compute api code, it's called something like an image-defined bdm | |
| 18:16:48 | mriedem | https://github.com/openstack/nova/blob/master/nova/compute/api.py#L624 | |
| 18:17:18 | mriedem | cfriesen: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L2802 | |
| 18:17:20 | mriedem | is the 0 size thing | |
| 18:18:10 | cfriesen | mriedem: sweet, thanks. | |
| 18:21:29 | openstackgerrit | Merged openstack/nova master: Move execs of touch to privsep. https://review.openstack.org/489190 | |
| 18:34:51 | openstackgerrit | Sean Dague proposed openstack/nova master: Avoid chowning console logs in libvirt https://review.openstack.org/472229 | |
| 18:36:07 | sdague | ok, I'm super confused what just happened there | |
| 18:38:29 | sdague | I think mikal's stack got funky | |
| 19:33:18 | mikal | sdake: yes, I think I've gotten lost in a rebase somewhere | |
| 19:33:31 | mikal | Sorry, sdague even | |
| 19:33:46 | mikal | sdague: I'm about to run a session, I'll eyeball the rest of the stack after that | |
| 19:41:14 | sdague | mikal: yeh, I hit the rebase button and it became a zero length patch, so I abandoned it | |
| 19:52:43 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the TraitList object https://review.openstack.org/502152 | |
| 19:52:44 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the ResourceClassList object https://review.openstack.org/502154 | |
| 19:52:44 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the Trait object https://review.openstack.org/502153 | |
| 19:52:45 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the UsageList object https://review.openstack.org/502156 | |
| 19:52:45 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the ResourceClass object https://review.openstack.org/502155 | |
| 19:52:46 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the AllocationList object https://review.openstack.org/502158 | |
| 19:52:46 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the Usage object https://review.openstack.org/502157 | |
| 19:52:47 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the InventoryList object https://review.openstack.org/502160 | |
| 19:52:47 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] Unregister the Allocation object https://review.openstack.org/502159 | |