| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-10-25 | |||
| 17:37:04 | mriedem | this is where the test in mine validates the sample against the actual notification generated by the test https://review.opendev.org/#/c/691129/1/nova/tests/functional/notification_sample_tests/test_aggregate.py@199 | |
| 17:37:28 | mriedem | oh yeah ok that makes sense | |
| 17:39:22 | openstackgerrit | Merged openstack/nova stable/train: libvirt: Ignore volume exceptions during post_live_migration https://review.opendev.org/691281 | |
| 17:40:25 | openstackgerrit | melanie witt proposed openstack/nova stable/train: Remove redundant call to get/create default security group https://review.opendev.org/691403 | |
| 17:40:25 | openstack | bug 1824435 in OpenStack Compute (nova) "fill_virtual_interface_list migration fails on second attempt" [Medium,In progress] https://launchpad.net/bugs/1824435 - Assigned to melanie witt (melwitt) | |
| 17:40:25 | openstackgerrit | melanie witt proposed openstack/nova stable/train: Add regression test for bug 1824435 https://review.opendev.org/691402 | |
| 17:43:35 | openstackgerrit | Merged openstack/nova stable/queens: Fix unit of hw_rng:rate_period https://review.opendev.org/689155 | |
| 17:50:56 | dansmith | mriedem: I don't really understand why we specify the payload in a file, but also some fields of the payload to verify in the doc schema file or whatever | |
| 17:51:25 | dansmith | mriedem: this stuff: https://review.opendev.org/#/c/691129/1/doc/notification_samples/aggregate-cache_images-end.json@5 | |
| 18:04:56 | openstackgerrit | Dan Smith proposed openstack/nova master: Log some stats for image pre-cache https://review.opendev.org/688173 | |
| 18:04:56 | openstackgerrit | Dan Smith proposed openstack/nova master: Add notification sample test for aggregate.cache_images.start|end https://review.opendev.org/691129 | |
| 18:04:57 | openstackgerrit | Dan Smith proposed openstack/nova master: Add Aggregate image caching progress notifications https://review.opendev.org/691390 | |
| 18:21:45 | openstackgerrit | Merged openstack/nova master: Stop building docs with (test-)requirements.txt https://review.opendev.org/691391 | |
| 18:21:55 | mriedem | dansmith: that's an override for what's in the common file | |
| 18:22:06 | mriedem | otherwise you just get what's in "$ref": "common_payloads/AggregatePayload.json#", | |
| 18:22:30 | dansmith | so I can just put my stuff in the common file? I mean, that seemed to work fine, but didn't know if it wasn't "right" | |
| 18:23:11 | dansmith | if so, the rev I just pushed may be acceptable then | |
| 18:24:45 | mriedem | it's a little weird to have that much stuff in the common file but not necessarily wrong, the only field you override is the host one | |
| 18:25:03 | mriedem | i'd probably just leave it until we have more samples that re-use the common payload and it no longer makes sense, | |
| 18:25:13 | mriedem | er yeah, that's it | |
| 18:25:24 | dansmith | yeah, I mean, doesn't seem like much point unless you need to sub things | |
| 18:33:42 | openstackgerrit | Eric Fried proposed openstack/python-novaclient master: Stop supporting and testing python2 https://review.opendev.org/691365 | |
| 18:56:31 | openstackgerrit | Eric Fried proposed openstack/os-vif master: Drop python2 support and testing https://review.opendev.org/691364 | |
| 19:00:06 | openstackgerrit | Eric Fried proposed openstack/os-vif master: Drop python2 support and testing https://review.opendev.org/691364 | |
| 19:00:44 | openstackgerrit | Eric Fried proposed openstack/os-vif master: Drop python2 support and testing https://review.opendev.org/691364 | |
| 19:10:56 | melwitt | I dunno if anyone is looking at the docs job failure yet, looks like psycopg missing libpq-dev package? https://zuul.opendev.org/t/openstack/build/57fdb73f89084fa9b845561ec724e11d/log/job-output.txt#664 | |
| 19:11:37 | dansmith | pretty sure mriedem already had a fix up for that | |
| 19:11:55 | efried | yeah, it merged | |
| 19:12:03 | efried | https://review.opendev.org/#/c/691391/2 | |
| 19:12:17 | efried | you fast approved it dansmith :P "pretty sure" indeed. | |
| 19:12:36 | dansmith | efried: I didn't look at her link before answering, hence my pretty sure | |
| 19:27:42 | melwitt | oh ok, I missed the discussion and didn't see an ML thread | |
| 19:28:32 | melwitt | glad it's fixed | |
| 19:42:03 | mriedem | we SEV1 IPL'ed that APAR | |
| 19:43:10 | mriedem | efried: those py2 removal patches are going to be the end of one of us | |
| 19:43:48 | efried | mriedem: I figured there would be some churn. I'm a zuul dunce to begin with. | |
| 19:44:11 | efried | but I feel like we're ahead of the game anyway, we've got months to get it sorted. | |
| 19:44:42 | mriedem | way to jinx yourself | |
| 19:47:40 | openstackgerrit | Eric Fried proposed openstack/os-vif master: Drop python2 support and testing https://review.opendev.org/691364 | |
| 19:51:02 | melwitt | IPL and APAR, had to google those | |
| 19:57:58 | efried | mriedem: join us in -release if you please? | |
| 19:58:42 | looking4somethin | yes | |
| 19:59:01 | looking4somethin | mriedem are you talking to me? | |
| 20:01:00 | efried | looking4somethin: sorry, you arrived in the middle of a conversation | |
| 20:01:26 | looking4somethin | awesome! | |
| 20:02:04 | efried | looking4somethin: Have you tried randomizing your placement allocation candidates? | |
| 20:02:23 | efried | landing on one compute isn't really a bug | |
| 20:02:40 | efried | I can't remember if we pack or spread by default -- dansmith? | |
| 20:02:47 | looking4somethin | not really | |
| 20:02:51 | looking4somethin | how can I do it. | |
| 20:03:11 | melwitt | efried: pack is default | |
| 20:03:28 | efried | looking4somethin: there you go ^ so by default you'll go to one compute until it's "full". | |
| 20:03:43 | efried | If you prefer to spread, you can do things with weighers. | |
| 20:04:01 | melwitt | you need to adjust some config options if you would prefer VMs to spread first onto compute hosts | |
| 20:04:32 | looking4somethin | that's it then. however I have observed some spreading previously but right now one compute is getting everything. | |
| 20:05:52 | melwitt | you can use https://docs.openstack.org/nova/rocky/configuration/config.html#placement.randomize_allocation_candidates to have placement randomize the computes it returns to nova | |
| 20:06:17 | melwitt | you can use https://docs.openstack.org/nova/rocky/configuration/config.html#filter_scheduler.host_subset_size to make nova choose randomly from a larger subset of hosts | |
| 20:06:19 | efried | melwitt: If there's a weigher in play that packs by default, that won't actually help (unless the deployment is bigger than the ?limit) | |
| 20:06:42 | melwitt | oh, I see | |
| 20:06:48 | melwitt | yeah | |
| 20:07:16 | efried | to spread, I thought you had to implement a weigher that weighs emptier hosts heavier. | |
| 20:07:32 | looking4somethin | efried how I can do that | |
| 20:07:42 | melwitt | you may have to adjust individual weighers multipliers if any of them are doing packing behavior | |
| 20:07:45 | efried | blind leading blind here... | |
| 20:07:48 | looking4somethin | to use the emptier hosts above all others | |
| 20:08:10 | looking4somethin | in nova.conf right? | |
| 20:08:13 | melwitt | there is also https://docs.openstack.org/nova/rocky/configuration/config.html#filter_scheduler.shuffle_best_same_weighed_hosts if you want to randomize hosts that are all weighed the same | |
| 20:08:34 | melwitt | yeah nova.conf | |
| 20:08:37 | efried | hm, CPUWeigher has a docstring that says spread is the default. | |
| 20:09:00 | efried | ditto RAMWeigher | |
| 20:09:18 | melwitt | here's the docs for all the weighers so you have to read those to see which one might be causing behavior you don't like by default https://docs.openstack.org/nova/latest/user/filter-scheduler.html#weights | |
| 20:09:36 | efried | phew, an rtfm answer, thanks melwitt | |
| 20:10:04 | looking4somethin | thanks melwitt | |
| 20:18:32 | looking4somethin | how can I replace (in nova.conf) nova.scheduler.weights.all_weighers by nova.scheduler.weights.CPUWeigher or just to select one weigher | |
| 20:19:12 | looking4somethin | I want to allocate to a node that have the most vcpus available | |
| 20:24:54 | efried | looking4somethin: It looks to me like you would say | |
| 20:24:55 | efried | weight_classes = 'nova.scheduler.weights.cpu.CPUWeigher' | |
| 20:24:55 | efried | [scheduler] | |
| 20:31:03 | looking4somethin | efried I will try it tomorrow, thanks | |
| 20:31:20 | efried | good luck | |
| 20:31:24 | efried | sweet dreams | |
| 20:31:28 | efried | (are made of this) | |
| 20:34:49 | mriedem | melwitt: efried: isn't that twice this week someone has been in here asking how to randomize allocations? wasn't eandersson asking about the same thing? | |
| 20:35:05 | mriedem | maybe we need a more obvious doc about the various knobs used to make that happen | |
| 20:35:12 | mriedem | since it seems like there are a few things to look at | |
| 20:35:17 | efried | except I think in both cases randomize turned out not to be the answer. | |
| 20:35:37 | mriedem | well, i don't mean the actual placement randomize option, | |
| 20:35:45 | mriedem | but shuffling a host within the same weighted subset | |
| 20:36:06 | eandersson | There are three options, and all seem very similar to me (especially if not reading the source code first) | |
| 20:36:37 | mriedem | my point is, can we get people to (1) stop reading source code and (2) find what they are looking for in the docs? | |
| 20:36:49 | eandersson | 100% this ^ | |
| 20:36:54 | mriedem | i'm thinking about it b/c i've been working on a troubleshooting doc for orphaned allocations | |
| 20:37:11 | mriedem | which i'm about to birth | |
| 20:38:57 | eandersson | btw we did like 6k cold migrations and live migrations with Rocky | |
| 20:39:04 | eandersson | Don't ask me why :p | |
| 20:39:19 | eandersson | And 99% were successful | |
| 20:39:27 | eandersson | We had some really bad failures | |
| 20:39:35 | eandersson | The worst was some sort of neutron port corruption | |
| 20:39:51 | eandersson | where the port was on the wrong compute, and in some cases completely corrupt in the neutron db | |
| 20:40:49 | eandersson | But at least no orphaned placement allocations so that is great | |