On 03/28/2014 05:01 AM, Jesse Pretorius wrote:
On 27 March 2014 20:52, Chris Friesen mailto:chris.frie...@windriver.com>> wrote:
It'd be nice to be able to do a heat template where you could
specify things like "put these three servers on separate hosts from
each other, and these oth
On Fri, 2014-03-28 at 19:38 +, CARVER, PAUL wrote:
> Jay Pipes wrote:
> >I'm proposing getting rid of the host aggregate hack (or maybe evolving
> >it?) as well as the availability zone concept and replacing them with a
> >more flexible generic container object that may be hierarchical in
> >n
Jay Pipes wrote:
>I'm proposing getting rid of the host aggregate hack (or maybe evolving
>it?) as well as the availability zone concept and replacing them with a
>more flexible generic container object that may be hierarchical in
>nature.
Is the thing you're proposing to replace them with someth
On Fri, 2014-03-28 at 11:01 +, Day, Phil wrote:
> >> Personally, I feel it is a mistake to continue to use the Amazon concept
> >> of an availability zone in OpenStack, as it brings with it the
> >> connotation from AWS EC2 that each zone is an independent failure
> >> domain. This characterist
On Fri, 2014-03-28 at 13:56 +0100, Belmiro Moreira wrote:
> +1 for Phil comments.
> I agree that VMs should spread between different default avzs if user
> doesn't define one at boot time.
> There is a blueprint for that feature that unfortunately didn't make
> it for icehouse.
> https://blueprints
+1 for Phil comments.
I agree that VMs should spread between different default avzs if user
doesn't define one at boot time.
There is a blueprint for that feature that unfortunately didn't make it for
icehouse.
https://blueprints.launchpad.net/nova/+spec/schedule-set-availability-zones
Belmiro
On 27 March 2014 20:52, Chris Friesen wrote:
> It'd be nice to be able to do a heat template where you could specify
> things like "put these three servers on separate hosts from each other, and
> these other two servers on separate hosts from each other (but maybe on the
> same hosts as the firs
>> Personally, I feel it is a mistake to continue to use the Amazon concept
>> of an availability zone in OpenStack, as it brings with it the
>> connotation from AWS EC2 that each zone is an independent failure
>> domain. This characteristic of EC2 availability zones is not enforced in
>> OpenStack
On Mar 26, 2014 6:46 PM, "Jay Pipes" wrote:
> Personally, I feel it is a mistake to continue to use the Amazon concept
> of an availability zone in OpenStack, as it brings with it the
> connotation from AWS EC2 that each zone is an independent failure
> domain. This characteristic of EC2 availabi
On 03/27/2014 12:49 PM, Day, Phil wrote:
-Original Message- From: Chris Friesen
[mailto:chris.frie...@windriver.com]
On 03/27/2014 11:48 AM, Day, Phil wrote:
nova boot --availability-zone az1 --scheduler-hint want-fast-cpu
--scheduler-hint want-ssd ...
Does this actually work? T
On 3/27/14, 11:03 AM, "Day, Phil" wrote:
>>
>> The need arises when you need a way to use both the zones to be
>>used for
>> scheduling when no specific zone is specified. The only way to do that
>>is
>> either have a AZ which is a superset of the two AZ or the other way
>>could be
>> if t
On 03/27/2014 12:28 PM, Day, Phil wrote:
Personally I'm a bit worried about users having too fine a
granularity over where they place a sever - AZs are generally few and
big so you can afford to allow this and not have capacity issues, but
if I had to expose 40 different rack based zones it woul
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: 27 March 2014 18:15
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
> aggregates..
>
> On 03/27/2014 1
> -Original Message-
> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
> Sent: 26 March 2014 20:33
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
> aggregates..
>
On 03/27/2014 11:48 AM, Day, Phil wrote:
Sorry if I'm coming late to this thread, but why would you define AZs
to cover "othognal zones" ?
See Vish's first message.
AZs are a very specific form of aggregate - they provide a particular
isolation schematic between the hosts (i.e. physical hosts
>
> The need arises when you need a way to use both the zones to be used for
> scheduling when no specific zone is specified. The only way to do that is
> either have a AZ which is a superset of the two AZ or the other way could be
> if the default_scheduler_zone can take a list of zones inste
same
thing - that would break what everyone (including folks used to working with
AWS) expects from an AZ
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: 27 March 2014 13:18
> To: openstack-dev@lists.openstack.org
> Subject: Re: [
On 03/27/2014 05:03 AM, Khanh-Toan Tran wrote:
Well, perhaps I didn't make it clearly enough. What I intended to say is
that user should be able to select a set of AZs in his request, something
like :
nova boot --flavor 2 --image ubuntu --availability-zone
Z1 --availability-zone AZ2
> -Message d'origine-
> De : Sylvain Bauza [mailto:sylvain.ba...@bull.net]
> Envoyé : jeudi 27 mars 2014 11:05
> À : OpenStack Development Mailing List (not for usage questions)
> Objet : Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
> aggrega
Le 27/03/2014 10:37, Khanh-Toan Tran a écrit :
- Original Message -
From: "Sangeeta Singh"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, March 26, 2014 6:54:18 PM
Subject: Re: [openstack-dev] [nova][scheduler] Availab
: OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..
Hi Toan,
Is what you say related to :
https://blueprints.launchpad.net/nova/+spec/schedule-set-availability-zone
s ?
2014-03-27 10:37 GMT+01:00
ailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Wednesday, March 26, 2014 6:54:18 PM
> > Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and
> Host aggregates..
> >
> >
> >
> > On 3/2
- Original Message -
> From: "Sangeeta Singh"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Wednesday, March 26, 2014 6:54:18 PM
> Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
> agg
)" <mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, March 26, 2014 at 1:34 PM
To: "OpenStack Development Mailing List (not for usage questions)"
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and
Hos
tack Development Mailing List (not for usage
> questions)"
> Date: Wednesday, March 26, 2014 at 4:45 PM
> To: "openstack-dev@lists.openstack.org"
>
> Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and
> Host aggregates..
>
>
>
>
e: Wednesday, March 26, 2014 at 4:45 PM
To:
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..
On Wed, 2014-03-26 a
On Wed, 2014-03-26 at 13:33 -0700, Vishvananda Ishaya wrote:
> On Mar 26, 2014, at 11:40 AM, Jay Pipes wrote:
>
> > On Wed, 2014-03-26 at 09:47 -0700, Vishvananda Ishaya wrote:
> >> Personally I view this as a bug. There is no reason why we shouldn’t
> >> support arbitrary grouping of zones. I kn
to:openstack-dev@lists.openstack.org>>
Date: Wednesday, March 26, 2014 at 1:34 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..
I can&#
I can't agree more on this. Although the name sounds identical to AWS, Nova
AZs are *not* for segregating compute nodes, but rather exposing to users a
certain sort of grouping.
Please see this pointer for more info if needed :
http://russellbryantnet.wordpress.com/2013/05/21/availability-zones-and
On Mar 26, 2014, at 11:40 AM, Jay Pipes wrote:
> On Wed, 2014-03-26 at 09:47 -0700, Vishvananda Ishaya wrote:
>> Personally I view this as a bug. There is no reason why we shouldn’t
>> support arbitrary grouping of zones. I know there is at least one
>> problem with zones that overlap regarding
Yes, Vish description describes the uses cases and the need for multiple
overlapping
availability zones nicely.
If multiple availability zone can be specified in the launch command that
will allow
End user to select hosts that satisfy all there constraints.
Thanks,
Sangeeta
On 3/26/14, 11:00 AM
On Wed, 2014-03-26 at 09:47 -0700, Vishvananda Ishaya wrote:
> Personally I view this as a bug. There is no reason why we shouldn’t
> support arbitrary grouping of zones. I know there is at least one
> problem with zones that overlap regarding displaying them properly:
>
> https://bugs.launchpad.n
On 03/26/2014 11:17 AM, Khanh-Toan Tran wrote:
I don't know why you need a
compute node that belongs to 2 different availability-zones. Maybe
I'm wrong but for me it's logical that availability-zones do not
share the same compute nodes. The "availability-zones" have the role
of partition your co
On 3/26/14, 10:17 AM, "Khanh-Toan Tran"
wrote:
>
>
>- Original Message -
>> From: "Sangeeta Singh"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Sent: Tuesday, March 25, 2014 9:50:00 PM
>> Subject: [openstack-dev] [nova][scheduler] Availability Zones and H
On 3/26/14, 10:17 AM, "Khanh-Toan Tran"
wrote:
>
>
>- Original Message -
>> From: "Sangeeta Singh"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Sent: Tuesday, March 25, 2014 9:50:00 PM
>> Subject: [openstack-dev] [nova][scheduler] Availability Zones and H
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..
I would say that the requirement is not valid. A host aggregate con only have
one availability zone so what you actually can have is
- Original Message -
> From: "Sangeeta Singh"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, March 25, 2014 9:50:00 PM
> Subject: [openstack-dev] [nova][scheduler] Availability Zones and Host
> aggregates..
>
> Hi,
>
> The availability Zones
On 03/26/2014 10:47 AM, Vishvananda Ishaya wrote:
Personally I view this as a bug. There is no reason why we shouldn’t
support arbitrary grouping of zones. I know there is at least one
problem with zones that overlap regarding displaying them properly:
https://bugs.launchpad.net/nova/+bug/127723
Personally I view this as a bug. There is no reason why we shouldn’t support
arbitrary grouping of zones. I know there is at least one problem with zones
that overlap regarding displaying them properly:
https://bugs.launchpad.net/nova/+bug/1277230
There is probably a related issue that is causi
On 03/25/2014 02:50 PM, Sangeeta Singh wrote:
What I am trying to achieve is have two AZ that the user can select
during the boot but then have a default AZ which has the HV from both
AZ1 AND AZ2 so that when the user does not specify any AZ in the boot
command I scatter my VM on both the AZ in
t: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggregates..
Sounds like an extra weighter to try and balance load between your two AZs
might be a nicer way to go.
The easiest way might be via cells, one for each AZ . But not sure we merged
that support yet. But there are patche
Sounds like an extra weighter to try and balance load between your two AZs
might be a nicer way to go.
The easiest way might be via cells, one for each AZ . But not sure we
merged that support yet. But there are patches for that.
John
On 25 Mar 2014 20:53, "Sangeeta Singh" wrote:
> Hi,
>
> Th
42 matches
Mail list logo
