You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nicolás Vázquez (Jira)" <ji...@apache.org> on 2022/02/25 03:25:00 UTC

[jira] [Updated] (CLOUDSTACK-10447) GSoC 2022: More granularity on affinity/anti-affinity groups

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolás Vázquez updated CLOUDSTACK-10447:
-----------------------------------------
    External issue URL: https://github.com/apache/cloudstack/issues/6039

> GSoC 2022: More granularity on affinity/anti-affinity groups
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10447
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10447
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Management Server
>            Reporter: Nicolás Vázquez
>            Priority: Major
>              Labels: gsoc2022
>
> Currently, defining an affinity or anti-affinity rule works only at hosts level. I would like to have more detail on the affinity group, extending it at different levels (cluster, pod, zone,..) and also within the same level, being able to add or remove resources from the group.
> For hosts and storage pools, administrators can make use of host tags or storage tags to get a similar result. However, the extension of affinity/anti-affinity groups would make the administration easier.
> Size of the project: Medium (~175hs)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)