It'd be great if you opened an issue in github and signal that the UI
is
not capable of selecting a cluster.
Unsure whether this would be a bug or an improvement at this point,
maybe the latter.
On 2024-12-09 13:22, Jeroen Kleijer wrote:
> Hi all,
>
> Thanks for the responses.
> I'll have to look into the tags and service offerings but I've done
> some
> tests using some ansible code and using my user account, I was able to
> deploy VMs in both cluster CL01 and CL02 and properly tell it to create
> the
> instance in that cluster. When I tried to specifically state on which
> host
> it should be created, I get the message back that "Parameter hostid can
> only be specified by a Root Admin, permission denied"
>
> I'll have a look to see if service offerings and tags can bring me
> something but I'm getting a feeling that, out of the box, granting
> users
> additional permissions (API calls), won't make the POD/Cluster/Host
> selection appear while creating a new instance. Given that I am able to
> (manually) select the cluster while using the API, I'm inclined to say
> that
> it's in the GUI. (but I'd be more than happy to be proven wrong :) )
>
> Kind regards,
>
> Jeroen Kleijer
>
> On Mon, Dec 9, 2024 at 12:54 PM Nux <n...@li.nux.ro> wrote:
>
>> If you try to deploy a VM via the API or cmk/cloudmonkey, can the user
>> select the host or cluster? Trying to determine if it's a UI problem
>> or
>> more general.
>> Also, if you put AccountA in DomainA and then dedicated the cluster to
>> DomainA (generically), does that change anything?
>>
>>
>> On 2024-12-09 11:01, Jeroen Kleijer wrote:
>> > Hi all,
>> >
>> > We've set up Apache CloudStack (4.19.1.2), users are able to login and
>> > we
>> > were able to dedicate resources to their accounts.
>> > We basically created an Account A and dedicated two clusters to it,
>> > called
>> > CL01 and CL02.
>> > Our Account A has been assigned the role of "User" since all user
>> > accounts
>> > only need to be able to create VMs, delete them and stop and start
>> > them.
>> > However, we would like the people in Account A, when deploying a new
>> > instance, to be able to choose between cluster CL01 and CL02 (and
>> > perhaps
>> > even the individual hosts if possible)
>> >
>> > I've looked into the role "User", created a copy of it and added
>> > several
>> > "list" API calls to it, such as listPods, listClusters, listHosts,
>> > listDedicatedClusters and listDedicatedHosts, but when a user creates
a
>> > new
>> > instance through the GUI, the selection of the pod, cluster or host is
>> > not
>> > offered. (the selection of zone is offered though)
>> >
>> > How would I go about doing this where an end-user is restricted and
>> > doesn't
>> > need to see more than they should but still have the option of
choosing
>> > between the resources that belong to them? (if this is even possible
at
>> > all)
>> >
>> > Kind regards,
>> >
>> > Jeroen Kleijer
>>
