JoaoJandre commented on PR #7489: URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1538269766
> @JoaoJandre could a global setting and its use in the deployment planner be enough to make the deployment and related lifecycles are strictly or non-strictly allowed the by deployment planner? This would be the simplest solution, however, it would be limited as well. A setting like that would either make all hosts accept or not accept offerings without tags (same with storage pools). The solution proposed in this PR makes the hosts and storage tags much more flexible; for instance, you could have hosts that accept untagged offerings, while others do not. Furthermore, being able to write a rule in JS opens space for operator creativity, and they would have a much finer control over their cloud environment. Also, the current behavior is kept, therefore, the use of tag as rules is optional. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
