Answers inline On 04/06/14 8:48 PM, "Girish Chaudhari" <girish.chaudh...@sungardas.com> wrote:
>Thanks Nitin for immediate response. > >"... I see that some more first class entities have gotten added but >the underlying concept remains the same." > >=> Can you please name the newly added first class entities if >possible, or what could be the best way to figure it out. > Is there any criteria which is used to decided whether particular CS >resource is first class candidate or not. Or every resource can be >taken as first class object and hiding can be applied to it. >Can you please let me know what steps/efforts will be involved in >hiding new CS first class object using this feature? You can check the create/update/list apis and they should have display flag as a parameter. > >"I would think that would be a bug. Please file it and I will try and >look into it." > >=> I will double check on it and try the same steps with another >mentioned resource. Will file the bug accordingly. > >>Also like to check whether Admin can update this feature flags or >>provide the meta data through UI? > > >"Yes, admin can update the display flag during creation time or using >update apis. Check deployvm and updateVm apis." > >-> You mean to say current CS UI(4.3 or upcoming 4.4) has ability to >mark the existing VM as hidden or create new VM with hide flag? I >could try it, using API programatically only. API doesn't have the ability currently. You can file a bug for that if it doesn't already exist. > >As well I have follow up extended questions as: > >Do this feature only applied to Root Admin vs the users Or even >equally applied to "Any Sub Domain Admin User" vs its non admin users? > Only for ROOT admins as far as hiding/exposing the resources are concerned. The reason being the ROOT admin is the owner of the cloud and should have this ability. If you have a use case other than this please bring it forward and we can discuss. > >Thanks, >Girish > >On Wed, Jun 4, 2014 at 8:19 PM, Nitin Mehta <nitin.me...@citrix.com> >wrote: >> >> >> On 04/06/14 4:52 AM, "Girish Chaudhari" <girish.chaudh...@sungardas.com> >> wrote: >> >>>Hi Team, >>> >>>I am looking into the CS first class object hiding feature to verify >>>how the Admin user has better control over the display of CS resources >>>to end users. >>> >>>The only reference link I could find is >>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Ability+to+have+b >>>et >>>ter+control+over+first+class+objects+in+CS >>> >>>Is there any other documentation available around this feature >>>providing more use cases and examples..etc. >> >> This is the functional spec and should provide you most of the >> information. I see that some more first class entities have gotten added >> but the underlying concept remains the same. >> >>> >>>Whereas I have tried to verify this feature by creating the >>>resources(VM) by Admin and associated it with the account. In usual >>>case Account user as well the admin user can retrieve the VM using the >>>listVMs call. When I am trying to set the display_vm flag as false, as >>>expected the account user don't see the VM. But even the Admin user >>>can't see the VM in list. >>> >>>Not sure whether I am following the right steps or its buggy behavior. >> >> I would think that would be a bug. Please file it and I will try and >>look >> into it. >> >> >> >>> >>>Also like to check whether Admin can update this feature flags or >>>provide the meta data through UI? >> >> Yes, admin can update the display flag during creation time or using >> update apis. Check deployvm and updateVm apis >> >>> >>>Curious to know whether anyone is using this feature in production and >>>how? >>> >>>Thanks, >>>Girish >>
