search

apache / cloudstack

Apache CloudStack is an opensource Infrastructure as a Service (IaaS) cloud computing platform
https://cloudstack.apache.org/
Apache License 2.0
2.09k stars 1.11k forks source link

template visibility in subdomains #9322

Open andre-pf opened 4 months ago

andre-pf commented 4 months ago
ISSUE TYPE
COMPONENT NAME
UI
CLOUDSTACK VERSION
4.19.0.0
SUMMARY

We are a school and use domains for different groups of classes. It would be good if there was an option for public templates/ISOs to be visible in subdomains as well. We cannot find a way to display templates/ISOs in the parent domain and in the subdomains. With the setting share.public.templates.with.other.domains we can share templates with all domains or only with the current domain. However, there is no way to share the template only in the parent domain and in the subdomain. This would be a good extension function. With shared networks, for example, this is possible. With a parameter such as share.public.templates.with.sub.domains this could be achieved. For example: share.public.templates.with.other.domains=false share.public.templates.with.sub.domains=true

boring-cyborg[bot] commented 4 months ago

Thanks for opening your first issue here! Be sure to follow the issue template!

DaanHoogland commented 4 months ago

@andre-pf , valid request but can you expand on what you want with the share.public.templates.with.other.domains=false , please? it does not seem to add value to you functionality.

andre-pf commented 4 months ago

This was an example. If share.public.templates.with.other.domains=false public templates are only visible in the current domain of the template (and not in subdomains). This is how it is implemented now. If the new parameter is e.g. share.public.templates.with.sub.domains=true public templates are also visible in subdomains. This allows us to achieve consistent behavior. For shared networks (or even domain admins) it is already like this. They can be made visible in the subdomains too. But are not visible in other domains. For us this will be very useful because we have many independent domains with subdomains. All parent domains have their own template for educational purposes. These templates are important for the parent domains and subdomains. The other domains do not need to see these public templates.

DaanHoogland commented 4 months ago

This was an example. If share.public.templates.with.other.domains=false public templates are only visible in the current domain of the template (and not in subdomains). This is how it is implemented now. If the new parameter is e.g. share.public.templates.with.sub.domains=true public templates are also visible in subdomains. This allows us to achieve consistent behavior. For shared networks (or even domain admins) it is already like this. They can be made visible in the subdomains too. But are not visible in other domains. For us this will be very useful because we have many independent domains with subdomains. All parent domains have their own template for educational purposes. These templates are important for the parent domains and subdomains. The other domains do not need to see these public templates.

ok, it seems you are using two switches for the same functionality, but I get it now.

tom-osz commented 4 months ago

@DaanHoogland Hi, I'm a colleague of @andre-pf, we had set up and now manage our cloustack implementation together. It's not two switches for the same functionality, there should be two switches.

First one, already implemented in Cloudstack:
share.public.templates.with.other.domains : If true, template is visible in all other domains. If false, Template is visible only in the current domain.

We would like to have a template visible in the current domain and if the "new" switch is "true", also in subdomains from the current domain.

Wish: Second, not actually implemented Switch would be great: share.public.templates.with.sub.domains: If true, template is visible in current and all subdomains of the current domain. If false, Template is visible just in current domain.

So, two switches for two functionalities.

The actual behavior is not understandable, at least for us. If a Domain Admin today is creating a template and set it visible to all domains, the admin ist sharing the template system wide. Why is this?

Have a great Day and thanks in advance!