weizhouapache commented on issue #9322: URL: https://github.com/apache/cloudstack/issues/9322#issuecomment-2848556122
> > Apologies if I make it sound like this is something we wanted. This isn't something being asked for. I just was using it as an example for hierarchy. Technically, you could adherently make a private template public this way. IE take a volume (containing private data) and turn it into a Template and make it public. Assuming both values are set to true. This is an unlikely scenario, but possible if we are talking about public vs private. > > From my viewpoint `root/Domain 1` and `root/Domain 2` should under no circumstances be able to see any resources under each other (including templates/isos) which matches the behavior of instances/networks/etc in Cloudstack. > It is true. > I was trying to use this to support why I think uploading an iso/template to Domain1 and it being visible from Domain 2 and Sub 2 is a bug since I have found no way to deploy or attach them as they don't appear in the instance creation wizard or attachable as an ISO to an instance. > If the template/iso is public, and global setting is true, the template/iso should be visible and usable by other domains. It might be an api or ui issue if the behavior is different. Need testing. > In our case we just are not allowing Public Templates in Sub-domains because of the above. The problem in our use case is certain use cases where there are many subdomains under a domain, and you have to upload that ISO/Template to every single subdomain. and this consumes resources. > > -- 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
