cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cs user <acldstk...@gmail.com>
Subject Re: Implicit dedication vs Explicit dedication
Date Wed, 05 Oct 2016 14:14:10 GMT
Hi Rafael,

Thanks for responding. It is possible to force them to only be able to use
that pod however?

So that when the create a machine, these machines are forced to launch in
that pod.

Cheers

On Wed, Oct 5, 2016 at 3:11 PM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:

> You can dedicate a pod to a user account or domain.
> Have you tried that?
>
> On Wed, Oct 5, 2016 at 11:09 AM, cs user <acldstkusr@gmail.com> wrote:
>
> > Hi All,
> >
> > I asked this a while back and never got a response. With the latest
> version
> > of Cloudstack, is it possible to force an account to launch in a
> particular
> > pod?
> >
> > Cheers!
> >
> > On Mon, Mar 21, 2016 at 12:59 PM, cs user <acldstkusr@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > Question regarding dedicating a Pod to an account......
> > >
> > > If I dedicate a Pod to an account, login as that account and then
> create
> > > an instance, when it comes to the affinity screen, I get the following:
> > >
> > > "Please select any affinity groups you want this VM to belong to"
> > >
> > > However, what I really want to do is force this account to only be able
> > to
> > > create hosts in this pod. If this is not possible then it should
> default
> > to
> > > this being ticked. Is there a way to accomplish this?
> > >
> > > I've also tried creating a new service offering and creating it with
> > ImplicitDedicationPlanner,
> > > with planner mode strict. However, all this appears to do is the
> > > following......
> > >
> > > When the account selects this service offering, the instance is created
> > on
> > > an empty host. Addition instances created with this service offering
> then
> > > get put onto the same host, rather than looking for other free hosts
> > within
> > > the same pod.
> > >
> > > So to summarize.... I want to either force an account to only launch
> > > instances in one Pod, or for this option to be the default. Is there a
> > way ?
> > >
> > > Thanks!
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message