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

[joy <jo...@gmail.com>]

The zone,pod,cluster is running on the same server.
All adding is successful(add primary ,add secondary, add pod, add zone all
successful).But only add hosts failed.
Also I tried to remove cloudstack and reinstall to fix the problem.But it
does not work.
I also tried to set ca.plugin.root.auth.strictness to false but still not
work.

Nicolás Vázquez (Jira) <ji...@apache.org>於 2022年3月14日 週一，下午7:30寫道：

>
>      [
> https://issues.apache.org/jira/browse/CLOUDSTACK-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Nicolás Vázquez updated CLOUDSTACK-10447:
> -----------------------------------------
>     Labels: gsoc2022 mentor  (was: gsoc2022)
>
> > 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)
>