| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-05-18 | |||
| 14:57:19 | gibi | gmann: PoC is even better :) | |
| 14:57:23 | gibi | bnemec: thanks | |
| 14:58:07 | openstackgerrit | Jiri Suchomel proposed openstack/nova-specs master: Add spec for downloading images via RBD https://review.opendev.org/572805 | |
| 16:06:46 | openstackgerrit | Merged openstack/nova-specs master: Add spec for downloading images via RBD https://review.opendev.org/572805 | |
| 16:17:53 | openstackgerrit | Andreas Jaeger proposed openstack/nova master: Add link to PDF document https://review.opendev.org/728939 | |
| 16:20:05 | openstackgerrit | Andreas Jaeger proposed openstack/python-novaclient master: Add link to PDF document https://review.opendev.org/728941 | |
| 17:42:41 | openstack | bug 1869050 in OpenStack Compute (nova) ussuri "migration of anti-affinity server fails due to stale scheduler instance info" [Low,In progress] https://launchpad.net/bugs/1869050 - Assigned to Balazs Gibizer (balazs-gibizer) | |
| 17:42:41 | openstackgerrit | Merged openstack/nova stable/ussuri: Reproduce bug 1869050 https://review.opendev.org/728781 | |
| 17:51:36 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove remaining '_LW' instances https://review.opendev.org/728964 | |
| 17:51:36 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove remaining '_LE' instances https://review.opendev.org/728963 | |
| 17:51:37 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove log translations https://review.opendev.org/728966 | |
| 17:51:37 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove remaining '_LI' instances https://review.opendev.org/728965 | |
| 17:51:38 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Remove hooks https://review.opendev.org/728968 | |
| 17:51:38 | openstackgerrit | Stephen Finucane proposed openstack/nova master: hacking: Modify checks for translated logs https://review.opendev.org/728967 | |
| 18:18:26 | openstackgerrit | Ghanshyam Mann proposed openstack/python-novaclient stable/ussuri: DNM: testing https://review.opendev.org/728975 | |
| 18:37:25 | josephillips | hi | |
| 18:37:37 | josephillips | im trying to perform a Host aggregate with some spec | |
| 18:37:46 | josephillips | i put on the flavor and work great | |
| 18:37:58 | josephillips | but all another flavors can choose the server that is part of extra spec | |
| 18:38:01 | josephillips | this is normal | |
| 18:38:02 | josephillips | ? | |
| 18:38:49 | sean-k-mooney | you are trying to require that a specific flavor extra spec must be requested to have the schduler select a host in a given aggreate correct | |
| 18:39:04 | josephillips | yes | |
| 18:39:20 | josephillips | is workign with the flavor with the extra spec | |
| 18:39:39 | josephillips | my problem is all the other flavors without the extra specs can choose the server that is on host aggregate | |
| 18:40:12 | sean-k-mooney | unfortunetly that AggregateInstanceExtraSpecsFilter does not support that usecase | |
| 18:40:27 | sean-k-mooney | nor does plamement today | |
| 18:40:35 | josephillips | to be more specific | |
| 18:40:53 | josephillips | at this point im right | |
| 18:40:53 | josephillips | m2.flavor can choose m2.server only | |
| 18:41:03 | josephillips | but using m1.flavor is choosing m1.server and m2.server too | |
| 18:41:10 | sean-k-mooney | yes | |
| 18:41:18 | josephillips | i want m1.flavor just choose m1 flavors | |
| 18:41:21 | sean-k-mooney | so i dont know if this filter still works but https://opendev.org/x/nfv-filters | |
| 18:41:21 | josephillips | m1.servers | |
| 18:41:33 | sean-k-mooney | contains a filter that will support the behavior you want | |
| 18:41:58 | sean-k-mooney | specificaly the AggregateInstanceTypeFilter | |
| 18:42:27 | josephillips | but using m1.flavor is choosing m1.server and m2.server too (im not looking this behaivor) | |
| 18:42:36 | openstackgerrit | Andreas Jaeger proposed openstack/nova master: Add link to PDF document https://review.opendev.org/728939 | |
| 18:42:39 | josephillips | im looking m1.flavor only choose m1 servers | |
| 18:42:47 | josephillips | and m2 choose m2 servers | |
| 18:43:02 | josephillips | to be more simple | |
| 18:43:18 | sean-k-mooney | josephillips: so you could try using the AggregateTypeAffinityFilter | |
| 18:43:29 | sean-k-mooney | that will allow you to map flavor to aggreates by name | |
| 18:44:13 | sean-k-mooney | that does not look at the extra spec so you have to manually map each flavor to a host aggreate | |
| 18:44:14 | josephillips | and all another flavors without extra specs use the all servers wihtout m2 servers | |
| 18:44:34 | josephillips | without extra specs | |
| 18:44:49 | sean-k-mooney | josephillips: yes as i said the intree filter dont support that behavior | |
| 18:45:19 | AJaeger | melwitt: https://review.opendev.org/#/c/728941 is correct, test places PDF file differently than we do in production. | |
| 18:45:59 | sean-k-mooney | you can use the AggregateTypeAffinityFilter to map flavor by name to speficic host aggreates or you can use the out of tree AggregateInstanceTypeFilter to get the ablity to require specific extra spec to be requested to land on a host aggreate | |
| 18:46:19 | melwitt | AJaeger: no it's ok, I will change my vote | |
| 18:46:49 | josephillips | sean-k-mooney: ok so the correct way is create host-aggregates for all the nodes? | |
| 18:47:02 | josephillips | or use another filter | |
| 18:47:47 | sean-k-mooney | josephillips: yes so if you can change your workflow slightly to be based on flavor name you dont need to create aggreates for all host. you just need to create aggretes for the hosts that need special handeling | |
| 18:48:00 | sean-k-mooney | the same is true for the our of tree filter | |
| 18:48:01 | AJaeger | thanks, melwitt | |
| 18:48:14 | AJaeger | melwitt: and thanks for double-checking! | |
| 18:48:21 | sean-k-mooney | you just need aggreate for the special hosts | |
| 18:50:19 | josephillips | using this filter sean-k-mooney right AggregateTypeAffinityFilter? | |
| 18:50:35 | sean-k-mooney | josephillips: once hack you can do is to add a custom trait to all flavor with a specific value e.g. CUSTOM_AGGREATE=General or CUSTOM_AGGREATE=M2 | |
| 18:51:33 | sean-k-mooney | if you use the AggregateTypeAffinityFilter you do not need to modfiy all your flavors only the one that need specail handeling | |
| 18:52:32 | sean-k-mooney | using AggregateTypeAffinityFilter you basicaly list what flavor may land on a give agggreate using aggreate metadata | |
| 18:52:50 | josephillips | ok let me try with this filter | |
| 18:52:58 | josephillips | AggregateTypeAffinityFilter | |
| 18:54:14 | sean-k-mooney | if you use AggregateInstanceExtraSpecsFilter then you need to add aggregate_instance_extra_specs:CUSTOM_AGGREATE=General to all your normal flavor and aggregate_instance_extra_specs:CUSTOM_AGGREATE=MY_SPECIAL_AGGREATE to your specil flavor | |
| 18:54:42 | sean-k-mooney | so the AggregateInstanceExtraSpecsFilter requires you to modify all flavor to get teh behavior you want | |
| 18:57:36 | josephillips | and is requiered for the host aggregate have the extra filtes for ram allocation cpu allocation? | |
| 18:57:47 | josephillips | or just with the normal filters this functionality works too | |
| 18:57:48 | josephillips | ? | |
| 18:58:03 | sean-k-mooney | josephillips: we do not support setting it via the aggreate anymore | |
| 18:58:15 | sean-k-mooney | we removed that a few release ago | |
| 18:59:02 | sean-k-mooney | josephillips: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008118.html | |
| 18:59:04 | openstackgerrit | Andreas Jaeger proposed openstack/os-vif master: Switch to newer openstackdocstheme and reno versions https://review.opendev.org/728612 | |
| 18:59:40 | sean-k-mooney | josephillips: actully i ment to link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126283.html | |
| 18:59:59 | josephillips | great | |
| 19:00:16 | sean-k-mooney | we deprecated the Aggregate[Core|Ram|Disk]Filter in ocata and remvoed them in train i think | |
| 19:00:30 | sean-k-mooney | josephillips: what release of openstack are you using | |
| 19:00:33 | josephillips | train | |
| 19:01:07 | sean-k-mooney | josephillips: ok in train you have two options. you can manage this via config file by setting the allcaotion ratios in the compute node config or via the api via placment | |
| 19:02:16 | sean-k-mooney | josephillips: this is the spec that cover why we made this change https://specs.openstack.org/openstack/nova-specs/specs/stein/implemented/initial-allocation-ratios.html let me see if i can get the docs link | |
| 19:02:59 | melwitt | note that the --aggregate and --amend options were added to osc-placement cli to help with this https://docs.openstack.org/osc-placement/latest/cli/index.html#cmdoption-openstack-resource-provider-inventory-set-aggregate | |
| 19:03:10 | sean-k-mooney | josephillips: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#scheduling-considerations | |
| 19:03:43 | sean-k-mooney | melwitt: the were added in stien right | |
| 19:03:55 | openstackgerrit | Merged openstack/nova master: compute: Allow snapshots to be created from PAUSED volume backed instances https://review.opendev.org/728011 | |
| 19:03:59 | sean-k-mooney | so it should be avilable in train | |
| 19:04:24 | melwitt | looks like train https://docs.openstack.org/releasenotes/osc-placement/train.html#relnotes-1-7-0-stable-train | |
| 19:06:25 | openstackgerrit | Merged openstack/nova stable/ussuri: Update scheduler instance info at confirm resize https://review.opendev.org/728782 | |
| 19:06:32 | openstackgerrit | Merged openstack/nova master: compute: Remove snapshot quiesce tests for STOPPED and SUSPENDED instances https://review.opendev.org/728012 | |
| 19:17:06 | josephillips | sean-k-mooney: looks like work with the filterAggregateTypeAffinityFilter | |
| 19:17:34 | josephillips | so for live migrations this host aggregate respect this? | |
| 19:17:50 | sean-k-mooney | yes it will | |
| 19:18:15 | josephillips | so i can move only on nodes that meets the host aggregate specs | |
| 19:18:28 | sean-k-mooney | i cant recall if we support --force on live migrtion if we do that might bypass it | |
| 19:18:45 | josephillips | i will try on my lab | |
| 19:18:54 | sean-k-mooney | so yes and no | |
| 19:19:45 | sean-k-mooney | the limitation of the AggregateTypeAffinityFilter is that if flavor X is the only flavor that you allow for host aggreate X the Flavor y can land in host aggreate X | |
| 19:20:05 | sean-k-mooney | but flavor X can still land on a host not in host aggreate X | |
| 19:20:05 | josephillips | now im just have to check how ubuntu openstack is handling the ratio of memory or cpu if is on placement | |
| 19:20:33 | sean-k-mooney | josephillips: that is not disto specfic | |
| 19:21:09 | sean-k-mooney | although the charms may or may not configure the plament aggreats for you i have not really looked at how they work in a few years | |