[
https://issues.apache.org/jira/browse/CLOUDSTACK-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506899#comment-17506899
]
Nicolás Vázquez commented on CLOUDSTACK-10447:
----------------------------------------------
Hi [~joy224961...@gmail.com] - which hypervisor is the host you are trying to
add? Can you share the management server logs with the error you are getting?
Have you tried using the simulator?
[https://docs.cloudstack.apache.org/en/latest/developersguide/developer_guide.html#using-the-simulator]
> 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)
