Thanks Geoff, will give it a try. What's the usual process for creating a feature request - just create it in Jira (did that - https://issues.apache.org/jira/browse/CLOUDSTACK-5058 ) and then it will be vetted automatically by the team, or create it and post a review request to dev@ ?
Thanks again for helping with this. Octavian >-----Original Message----- >From: Geoff Higginbottom [mailto:[email protected]] >Sent: 06 November 2013 13:13 >To: [email protected] >Subject: RE: domains/subdomains headaches > >I did some testing last night (before seeing Nitin's response) and using the >updateTemplatePermissions command could work for you but with caveats. > >updateTemplatePermissions does the following (from API page) " Updates a >template visibility permissions. A public template is visible to all accounts >within the same domain. A private template is visible only to the owner of the >template. A priviledged template is a private template with account >permissions added. Only accounts specified under the template permissions >are visible to them" > >Full details can be found here >http://cloudstack.apache.org/docs/api/apidocs- >4.2/root_admin/updateTemplatePermissions.html > >The command assumes it is being run by an account within the same Domain >as the target account so you cannot run it as Root. > >You would have to create an account within the domain you want to allocated >the Template to, then import the Template, but do NOT make it Public. > >Then using the updateTemplatePermissions API call whilst authenticated as >the account who imported the Template (suggest you use CloudMonkey for >this) assign permissions to the other Accounts within the Domain. > >This does not filter down to Sub Domains, so you would need to repeat the >process for every Domain. > >Suggest you log a feature request to get this enhanced to allow you to 'Specify >the Domain ID' when assigning permissions. > >You could also log a 2nd Feature Request to 'Enable allocation of a Template to >a Domain and optionally its Sub Domains' > >Regards > >Geoff Higginbottom > >D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 > >[email protected] > >-----Original Message----- >From: Nitin Mehta [mailto:[email protected]] >Sent: 05 November 2013 18:17 >To: [email protected] >Subject: Re: domains/subdomains headaches > >I don¹t think CS has that functionality at the moment. I am guessing RBAC >work might factor that. >That said there is a workaround of adding the accounts you want the template >to be visible through updateTemplatePermissions API. >See that works for you > >Thanks, >-Nitin > >On 05/11/13 8:41 AM, "Octavian Popescu" ><[email protected]> >wrote: > >>Thanks Geoff but it's still not working... >> >>>-----Original Message----- >>>From: Geoff Higginbottom [mailto:[email protected]] >>>Sent: 05 November 2013 17:31 >>>To: [email protected] >>>Subject: RE: domains/subdomains headaches >>> >>>Octavian, >>> >>>If I remember rightly, login as a Domain Admin for 'Base_Domain', and >>>then publish the Template as a 'Featured' template, this should then >>>be available to Sub-Domians >>> >>>Regards >>> >>>Geoff Higginbottom >>> >>>D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 >>> >>>[email protected] >>> >>>-----Original Message----- >>>From: Octavian Popescu [mailto:[email protected]] >>>Sent: 05 November 2013 15:20 >>>To: [email protected] >>>Subject: domains/subdomains headaches >>> >>>Hi, >>> >>>Have a look at the following structure: >>> >>>BASE_DOMAIN >>> \_ CHILD_1 >>> \_ CHILD_2 >>> >>>Assuming I'm using an account created in BASE_DOMAIN, I'm trying to >>>find a way to publish templates from that account so that they're also >>>accessible to accounts created on the child subdomains - is there any >>>way to do this and set up some sort of inheritance for the templates? >>>The default behavior seems to be total isolation - if you create a >>>template via an account from the BASE_DOMAIN, the subdomains are not >>>able to access it (and the other way around, if you create it from an >>>account in the child domains, the BASE_DOMAIN account is not able to >>>access them) I don't want to declare the templates as public as >>>everyone will be able to access them then. >>> >>>Thanks, >>>Octavian >>> >>> >>> >>>This email and any attachments to it may be confidential and are >>>intended solely for the use of the individual to whom it is addressed. >>>Any views or opinions expressed are solely those of the author and do >>>not necessarily represent those of Shape Blue Ltd or related >>>companies. If you are not the intended recipient of this email, you >>>must neither take any action based upon its contents, nor copy or show >>>it to anyone. Please contact the sender if you believe you have >>>received this email in error. Shape Blue Ltd is a company incorporated >>>in England & Wales. ShapeBlue Services India LLP is a company >>>incorporated in India and is operated under license from Shape Blue Ltd. >>>Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil >>>and is operated under license from Shape Blue Ltd. ShapeBlue is a >>>registered trademark. > >This email and any attachments to it may be confidential and are intended >solely for the use of the individual to whom it is addressed. Any views or >opinions expressed are solely those of the author and do not necessarily >represent those of Shape Blue Ltd or related companies. If you are not the >intended recipient of this email, you must neither take any action based upon >its contents, nor copy or show it to anyone. Please contact the sender if you >believe you have received this email in error. Shape Blue Ltd is a company >incorporated in England & Wales. ShapeBlue Services India LLP is a company >incorporated in India and is operated under license from Shape Blue Ltd. >Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is >operated under license from Shape Blue Ltd. ShapeBlue is a registered >trademark.
