Hi, Would you like to correct me if I understand that watcher will not consider server groups when it does jobs? If I am right, do we have any solutions to this problem? Thank you. Regards Nguyen Huu Khoi
Hi, On Tue, Sep 23, 2025 at 1:30 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hi,
Would you like to correct me if I understand that watcher will not consider server groups when it does jobs?
Yes, that's correct, but note that watcher does not always define the destination for migrations in the actionplan. In some of the strategies it will simply request nova to define the destination node.
If I am right, do we have any solutions to this problem?
Solution is being implemented based on
https://specs.openstack.org/openstack/watcher-specs/specs/2025.2/approved/ex... Part of it has been already implemented (exposing additional attributes in nova api and cluster model https://review.opendev.org/c/openstack/watcher/+/955827 )
Thank you. Regards
Nguyen Huu Khoi
Just adding more context about these limitations. The implementation of server_groups and scheduler_hints in Watcher's cluster data model[1] was deferred to future releases, until we have it integrated with openstacksdk, as a replacement of python-novaclient library. Even if we add information about server_groups and policies, strategies would also need to be updated to properly deal with these new constraints (which was not covered in this spec) If you want to avoid failures due to affinity policy, you can try to exclude instances using audit scope[2]. [1] https://docs.openstack.org/watcher/latest/glossary.html#cluster-data-model-d... [2] https://docs.openstack.org/api-ref/resource-optimization/#create-audit-templ... On Tue, Sep 23, 2025 at 4:03 AM Alfredo Moralejo Alonso <amoralej@redhat.com> wrote:
Hi,
On Tue, Sep 23, 2025 at 1:30 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hi,
Would you like to correct me if I understand that watcher will not consider server groups when it does jobs?
Yes, that's correct, but note that watcher does not always define the destination for migrations in the actionplan. In some of the strategies it will simply request nova to define the destination node.
If I am right, do we have any solutions to this problem?
Solution is being implemented based on
https://specs.openstack.org/openstack/watcher-specs/specs/2025.2/approved/ex...
Part of it has been already implemented (exposing additional attributes in nova api and cluster model https://review.opendev.org/c/openstack/watcher/+/955827 )
Thank you. Regards
Nguyen Huu Khoi
-- Douglas Viroel - dviroel
Thank you for the clarification. Solution is being implemented based on https://specs.openstack.org/openstack/watcher-specs/specs/2025.2/approved/ex...
I am looking for it.
If you want to avoid failures due to affinity policy, you can try to exclude instances using audit scope>> I think it is just a workaround because it is hard for the public cloud environment. Nguyen Huu Khoi On Tue, Sep 23, 2025 at 7:53 PM Douglas Viroel <viroel@gmail.com> wrote:
Just adding more context about these limitations. The implementation of server_groups and scheduler_hints in Watcher's cluster data model[1] was deferred to future releases, until we have it integrated with openstacksdk, as a replacement of python-novaclient library. Even if we add information about server_groups and policies, strategies would also need to be updated to properly deal with these new constraints (which was not covered in this spec) If you want to avoid failures due to affinity policy, you can try to exclude instances using audit scope[2].
[1] https://docs.openstack.org/watcher/latest/glossary.html#cluster-data-model-d... [2] https://docs.openstack.org/api-ref/resource-optimization/#create-audit-templ...
On Tue, Sep 23, 2025 at 4:03 AM Alfredo Moralejo Alonso < amoralej@redhat.com> wrote:
Hi,
On Tue, Sep 23, 2025 at 1:30 AM Nguyễn Hữu Khôi < nguyenhuukhoinw@gmail.com> wrote:
Hi,
Would you like to correct me if I understand that watcher will not consider server groups when it does jobs?
Yes, that's correct, but note that watcher does not always define the destination for migrations in the actionplan. In some of the strategies it will simply request nova to define the destination node.
If I am right, do we have any solutions to this problem?
Solution is being implemented based on
https://specs.openstack.org/openstack/watcher-specs/specs/2025.2/approved/ex...
Part of it has been already implemented (exposing additional attributes in nova api and cluster model https://review.opendev.org/c/openstack/watcher/+/955827 )
Thank you. Regards
Nguyen Huu Khoi
-- Douglas Viroel - dviroel
participants (3)
-
Alfredo Moralejo Alonso
-
Douglas Viroel
-
Nguyễn Hữu Khôi