[
https://issues.apache.org/jira/browse/CLOUDSTACK-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515655#comment-17515655
]
Nicolás Vázquez commented on CLOUDSTACK-10447:
----------------------------------------------
Great [[email protected]] - I would like to remind you that the
application starts on the 4{^}th{^} April and closes on 19{^}th{^} April. If
you are interested in this project please submit your proposal. Can also see
the Github issue for this project:
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, mentor
>
> 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)