Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: <CAG97rac-Vy1adRAtPoUQqcp2mtPUn6TNom4gcWD32_Otbf9xXQ@mail.gmail.com>
References: <CADfcUwExS-JJH01AygU==5KADCLEBeNHteLBQeywQXKtJWVRCA@mail.gmail.com>
 <CADfcUwF7RbVxNC=8Q3_C2Ncte+e60U8B5x5uZkiPitL4p7dang@mail.gmail.com> <CAG97rac-Vy1adRAtPoUQqcp2mtPUn6TNom4gcWD32_Otbf9xXQ@mail.gmail.com>
From: =?UTF-8?Q?Rafael_Weing=C3=A4rtner?= <rafaelweingartner@gmail.com>
Date: Wed, 5 Oct 2016 11:12:58 -0300
Message-ID: <CAG97racrezp4-nFtQjRHChu3p7h_bB0VJOON-3X9+94YUxW6Kg@mail.gmail.com>
Subject: Re: Implicit dedication vs Explicit dedication
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c134fd6315fde053e1ec6b2
archived-at: Wed, 05 Oct 2016 14:13:04 -0000

--94eb2c134fd6315fde053e1ec6b2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

[UPDATE] this is the API method that you could use:
https://cloudstack.apache.org/api/apidocs-4.9/apis/dedicatePod.html

On Wed, Oct 5, 2016 at 11:11 AM, Rafael Weing=C3=A4rtner <
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 crea=
te
>> > 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 abl=
e
>> 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 create=
d
>> 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=C3=A4rtner
>


--=20
Rafael Weing=C3=A4rtner

--94eb2c134fd6315fde053e1ec6b2--