| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-19 | |||
| 14:46:45 | sean-k-mooney | when you add a trait to the image or flavor as required you will guarentte that you willl land on a host with that trait | |
| 14:46:45 | sean-k-mooney | when you add a trait to the image or flavor as required you will guarentte that you willl land on a host with that trait | |
| 14:46:57 | alexe9191 | I thought the placement prefilter was enabled by default? do I need to explicitly enable it? | |
| 14:46:58 | alexe9191 | I thought the placement prefilter was enabled by default? do I need to explicitly enable it? | |
| 14:47:11 | sean-k-mooney | when you add the required trait to the aggreate you will guarentee you will only land in that aggreate if you asked for the requited trait | |
| 14:47:11 | sean-k-mooney | when you add the required trait to the aggreate you will guarentee you will only land in that aggreate if you asked for the requited trait | |
| 14:47:31 | sean-k-mooney | alexe9191: its disable by default so you have to enable it yes | |
| 14:47:32 | sean-k-mooney | alexe9191: its disable by default so you have to enable it yes | |
| 14:49:09 | alexe9191 | Apologies for the question but it's not mentioned anywhere in nova.conf nor do I see a placement filter in the scheduler/filter source tree. | |
| 14:49:09 | alexe9191 | Apologies for the question but it's not mentioned anywhere in nova.conf nor do I see a placement filter in the scheduler/filter source tree. | |
| 14:49:11 | alexe9191 | How would I enable it? | |
| 14:49:11 | alexe9191 | How would I enable it? | |
| 14:49:34 | sean-k-mooney | its covered in the doc | |
| 14:49:34 | sean-k-mooney | its covered in the doc | |
| 14:49:36 | sean-k-mooney | https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html | |
| 14:49:36 | sean-k-mooney | https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html | |
| 14:49:54 | sean-k-mooney | you enable https://docs.openstack.org/nova/latest/configuration/config.html#scheduler.enable_isolated_aggregate_filtering | |
| 14:49:54 | sean-k-mooney | you enable https://docs.openstack.org/nova/latest/configuration/config.html#scheduler.enable_isolated_aggregate_filtering | |
| 14:50:47 | alexe9191 | aha. I though about placement as a whole not that specific pre-filter. | |
| 14:50:47 | alexe9191 | aha. I though about placement as a whole not that specific pre-filter. | |
| 14:50:51 | sean-k-mooney | alexe9191: placemetn filter are what we call prefilter they are not implemented in scheduler/filters since they work differently | |
| 14:50:52 | sean-k-mooney | alexe9191: placemetn filter are what we call prefilter they are not implemented in scheduler/filters since they work differently | |
| 14:51:24 | sean-k-mooney | pre-filter modify the quiery we pass to placment before the normal filters run to be more strict | |
| 14:51:24 | sean-k-mooney | pre-filter modify the quiery we pass to placment before the normal filters run to be more strict | |
| 14:51:52 | sean-k-mooney | alexe9191: they are implemented in https://github.com/openstack/nova/blob/master/nova/scheduler/request_filter.py | |
| 14:51:52 | sean-k-mooney | alexe9191: they are implemented in https://github.com/openstack/nova/blob/master/nova/scheduler/request_filter.py | |
| 14:52:04 | alexe9191 | Thank you:) | |
| 14:52:04 | alexe9191 | Thank you:) | |
| 14:52:37 | alexe9191 | That being said. I am wondering if there are any known bugs in scheduler in nova rocky? | |
| 14:52:37 | alexe9191 | That being said. I am wondering if there are any known bugs in scheduler in nova rocky? | |
| 14:52:42 | sean-k-mooney | most of them are disable by default although some are always on and we will be move more to on by default as we continue | |
| 14:52:42 | sean-k-mooney | most of them are disable by default although some are always on and we will be move more to on by default as we continue | |
| 14:52:57 | sean-k-mooney | in the schduler in general proably | |
| 14:52:57 | sean-k-mooney | in the schduler in general proably | |
| 14:53:16 | sean-k-mooney | in this code not that im direclty aware of that would affect your usecase | |
| 14:53:17 | sean-k-mooney | in this code not that im direclty aware of that would affect your usecase | |
| 14:53:30 | alexe9191 | Allow me to be more specific. | |
| 14:53:30 | alexe9191 | Allow me to be more specific. | |
| 14:53:55 | alexe9191 | We have availability zones and we have aggregates to group some hosts that has certain properties like I mentioned. | |
| 14:53:55 | alexe9191 | We have availability zones and we have aggregates to group some hosts that has certain properties like I mentioned. | |
| 14:54:20 | alexe9191 | For some reason. the scheduling works just fine till it stops. And then the solution to that would be removing one host from the aggregates and readding it. And then scheduling would work again. | |
| 14:54:21 | alexe9191 | For some reason. the scheduling works just fine till it stops. And then the solution to that would be removing one host from the aggregates and readding it. And then scheduling would work again. | |
| 14:54:44 | sean-k-mooney | that is odd | |
| 14:54:45 | sean-k-mooney | that is odd | |
| 14:54:54 | alexe9191 | It seems to fail mostly on the availability zone filter or the extra spec filter. The other day it said that property defined in the flavor does not match the metadata on the aggregate. But it does | |
| 14:54:54 | alexe9191 | It seems to fail mostly on the availability zone filter or the extra spec filter. The other day it said that property defined in the flavor does not match the metadata on the aggregate. But it does | |
| 14:55:06 | sean-k-mooney | well you can disable that if you enabel https://github.com/openstack/nova/blob/stable/rocky/nova/scheduler/request_filter.py#L63 | |
| 14:55:06 | sean-k-mooney | well you can disable that if you enabel https://github.com/openstack/nova/blob/stable/rocky/nova/scheduler/request_filter.py#L63 | |
| 14:55:31 | sean-k-mooney | alexe9191: you do not have the issolated aggrate feature in rocky that we were discussing | |
| 14:55:31 | sean-k-mooney | alexe9191: you do not have the issolated aggrate feature in rocky that we were discussing | |
| 14:55:42 | sean-k-mooney | but you you have access to using placment for AZs | |
| 14:55:42 | sean-k-mooney | but you you have access to using placment for AZs | |
| 14:55:46 | sean-k-mooney | instead of teh az filter | |
| 14:55:46 | sean-k-mooney | instead of teh az filter | |
| 14:56:06 | alexe9191 | Indeed. This is why I am investigating moving what I can move to the placement. Also for performance reasons. | |
| 14:56:07 | alexe9191 | Indeed. This is why I am investigating moving what I can move to the placement. Also for performance reasons. | |
| 14:56:33 | sean-k-mooney | alexe9191: https://docs.openstack.org/nova/latest/admin/availability-zones.html#availability-zones-with-placement | |
| 14:56:33 | sean-k-mooney | alexe9191: https://docs.openstack.org/nova/latest/admin/availability-zones.html#availability-zones-with-placement | |
| 14:57:14 | sean-k-mooney | alexe9191: that is still not enabled by default upstream but that is becasue we ment to do it in victoria and we got distrated | |
| 14:57:14 | sean-k-mooney | alexe9191: that is still not enabled by default upstream but that is becasue we ment to do it in victoria and we got distrated | |
| 14:57:36 | sean-k-mooney | alexe9191: ill be enableing it by defualt this cycle and deprecating the AZ filter for removal in the Y release | |
| 14:57:37 | sean-k-mooney | alexe9191: ill be enableing it by defualt this cycle and deprecating the AZ filter for removal in the Y release | |
| 14:57:46 | alexe9191 | may I ask what issues has been faced when it was enabled by default? | |
| 14:57:46 | alexe9191 | may I ask what issues has been faced when it was enabled by default? | |
| 14:58:10 | sean-k-mooney | none that im aware of | |
| 14:58:11 | sean-k-mooney | none that im aware of | |
| 14:58:28 | sean-k-mooney | we have not enabled it by default yet | |
| 14:58:29 | sean-k-mooney | we have not enabled it by default yet | |
| 14:58:35 | alexe9191 | ah I misread. Apologies. | |
| 14:58:35 | alexe9191 | ah I misread. Apologies. | |
| 14:59:15 | sean-k-mooney | i submited https://review.opendev.org/c/openstack/nova/+/745605 | |
| 14:59:15 | sean-k-mooney | i submited https://review.opendev.org/c/openstack/nova/+/745605 | |
| 14:59:21 | alexe9191 | enabling this pre-filter will not have an effect on the extraspecs aggregate I assume? As I intend to slowly migrate the users to new flavors. | |
| 14:59:21 | alexe9191 | enabling this pre-filter will not have an effect on the extraspecs aggregate I assume? As I intend to slowly migrate the users to new flavors. | |
| 14:59:35 | sean-k-mooney | to do it last year but i got distracted | |
| 14:59:36 | sean-k-mooney | to do it last year but i got distracted | |
| 14:59:47 | sean-k-mooney | alexe9191: correct it will not | |
| 14:59:47 | sean-k-mooney | alexe9191: correct it will not | |
| 15:00:17 | sean-k-mooney | what it will do is map all AZ to plamcent aggrate and then include the aggreate uuid in the query | |
| 15:00:17 | sean-k-mooney | what it will do is map all AZ to plamcent aggrate and then include the aggreate uuid in the query | |
| 15:01:20 | sean-k-mooney | so if you as for AZ X it will tell placment to only look at host that are in AZ x by mapping those host to a placment aggaet and stating the canidat hosts must be a member_of the AZ | |
| 15:01:20 | sean-k-mooney | so if you as for AZ X it will tell placment to only look at host that are in AZ x by mapping those host to a placment aggaet and stating the canidat hosts must be a member_of the AZ | |
| 15:01:59 | alexe9191 | That is the desired behaviour. | |
| 15:01:59 | alexe9191 | That is the desired behaviour. | |
| 15:02:27 | sean-k-mooney | we have been very carful to ensure that you can opt into the new plamcent feature gradulally | |
| 15:02:27 | sean-k-mooney | we have been very carful to ensure that you can opt into the new plamcent feature gradulally | |
| 15:02:56 | sean-k-mooney | placment should never break any of the exisitng filters | |
| 15:02:56 | sean-k-mooney | placment should never break any of the exisitng filters | |
| 15:03:51 | sean-k-mooney | but it should narrow down thte host passed to it so the filters have to check less host by moveing more of the filtering to placment and sql instead of python | |
| 15:03:51 | sean-k-mooney | but it should narrow down thte host passed to it so the filters have to check less host by moveing more of the filtering to placment and sql instead of python | |
| 15:04:49 | alexe9191 | Excellent. | |
| 15:04:49 | alexe9191 | Excellent. | |
| 15:05:00 | alexe9191 | The mentioned bug about the scheduling, is it fixed in releases after rocky? | |
| 15:05:01 | alexe9191 | The mentioned bug about the scheduling, is it fixed in releases after rocky? | |
| 15:05:36 | alexe9191 | Does not seem to be: https://bugs.launchpad.net/nova/+bug/1677217 | |
| 15:05:37 | openstack | Launchpad bug 1677217 in OpenStack Compute (nova) " AggregateImagePropertiesIsolation filter return unwanted compute nodes" [Low,Triaged] | |
| 15:05:37 | openstack | Launchpad bug 1677217 in OpenStack Compute (nova) " AggregateImagePropertiesIsolation filter return unwanted compute nodes" [Low,Triaged] | |
| 15:05:37 | alexe9191 | Does not seem to be: https://bugs.launchpad.net/nova/+bug/1677217 | |
| 15:06:28 | sean-k-mooney | alexe9191: no its not really a bug | |
| 15:06:28 | sean-k-mooney | alexe9191: no its not really a bug | |