cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [cloudstack-documentation] andrijapanicsb commented on a change in pull request #62: Template sharing doc update
Date Mon, 05 Aug 2019 14:32:32 GMT
andrijapanicsb commented on a change in pull request #62: Template sharing doc update
URL: https://github.com/apache/cloudstack-documentation/pull/62#discussion_r310635096
 
 

 ##########
 File path: source/adminguide/templates.rst
 ##########
 @@ -295,6 +295,57 @@ Example GUI dialog of uploading Template/ISO from local (browser) is
given below
 
 Note that uploading multi-disk templates is also supported.
 
+Sharing templates with other accounts/projects
+----------------------------------------------
+
+When adding a template, the owner can choose to make template public or to keep it private.
Once the template is created, the owner can choose to share this template so that other accounts/projects
can also use the template. 
+
+Currently, the template owner can share his template with:
+  - other accounts inside his own domain (i.e. can't share the template with other accounts
in the subdomain of his domain or any other domains)
+  - projects where he belongs to (i.e. if he is the owner/creator or projects of other users
where he has been joined)
+
+Template permissions can be changed via updateTemplatePermissions API call or via GUI. It
is supported to add, remove or reset (remove all) template permissions.
+
+When adding or removing permissions to/from a template, it is required to specify account/project
name which is being added/removed from the template permissions. 
+
+Global setting "allow.user.view.all.domain.accounts" has a default value of "false". This
makes sure that when the user wants to share a template via GUI, he will not be shown the
list of all accounts in his domain and he will need to know the name of the destination account
with which he is sharing the template. This makes sense in public clouds where each account
of a single domain is a different tenant/customer and privacy is imperative. In this case,
the user will be presented with an input field to enter the account name, as on the images
below:
 
 Review comment:
   resolved as suggested, thx

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message