Is any discussion on this topic scheduled during the summit ?
Thanks,
Meghal
On Apr 9, 2014, at 9:03 AM, Sylvain Bauza
sylvain.ba...@gmail.commailto:sylvain.ba...@gmail.com wrote:
2014-04-07 23:11 GMT+02:00 Sylvain Bauza
sylvain.ba...@gmail.commailto:sylvain.ba...@gmail.com:
Hi Phil,
There is a good talk happening today at 2pm @ room B.206 in a Breakout
session :
Divide and conquer: Resource Segregation in OpenStack
(I'm sorry, I can't provide the sched.org link, site seems to be down)
-Sylvain
Le 13/05/2014 11:12, Meghal Gosalia a écrit :
Is any discussion on this topic
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 08 April 2014 14:25
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: 08 April 2014 15:19
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On 04/08/2014 07:25 AM, Jay Pipes wrote:
On Tue
On 04/09/2014 03:55 AM, Day, Phil wrote:
I would guess that affinity is more likely to be a soft requirement
that anti-affinity, in that I can see some services just not meeting
their HA goals without anti-affinity but I'm struggling to think of a
use case why affinity is a must for the
2014-04-07 23:11 GMT+02:00 Sylvain Bauza sylvain.ba...@gmail.com:
Hi Phil,
2014-04-07 18:48 GMT+02:00 Day, Phil philip@hp.com:
Hi Sylvain,
There was a similar thread on this recently - which might be worth
reviewing:
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: 09 April 2014 15:37
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On 04/09/2014 03:55 AM, Day, Phil wrote:
I
- Original Message -
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: 09 April 2014 15:37
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On 04/09
01:02
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On 3 April 2014 08:21, Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
wrote:
Otherwise we cannot provide redundancy to client except
[mailto:ijw.ubu...@cack.org.uk]
Envoyé : mardi 8 avril 2014 01:02
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
On 3 April 2014 08:21, Khanh-Toan Tran
khanh-toan.t
the affinity criteria.
Best,
-jay
From: Khanh-Toan Tran [mailto:khanh-toan.t...@cloudwatt.com]
Sent: 08 April 2014 11:32
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability
Zones : possible or not ?
“Abusive usage
-Message d'origine-
De : Jay Pipes [mailto:jaypi...@gmail.com]
Envoyé : mardi 8 avril 2014 15:25
À : openstack-dev@lists.openstack.org
Objet : Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible
or not ?
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote
- Original Message -
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
On a large cloud you’re protect against this to some extent if the
number of servers is number of instances in the quota.
However it does feel that there are a couple of things missing to
really provide
On 04/08/2014 07:25 AM, Jay Pipes wrote:
On Tue, 2014-04-08 at 10:49 +, Day, Phil wrote:
On a large cloud you’re protect against this to some extent if the
number of servers is number of instances in the quota.
However it does feel that there are a couple of things missing to
really
) might be useful.
Phil
From: Murray, Paul (HP Cloud Services)
Sent: 03 April 2014 16:34
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
Hi Sylvain,
I would go with keeping AZs exclusive
On Mon, 2014-04-07 at 16:48 +, Day, Phil wrote:
Hi Sylvain,
There was a similar thread on this recently – which might be worth
reviewing:
http://lists.openstack.org/pipermail/openstack-dev/2014-March/031006.html
Some interesting use cases were posted, and a I don’t think a
...@cloudwatt.com]
*Sent:* 03 April 2014 15:53
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Nova] Hosts within two Availability Zones
: possible or not ?
+1 for AZs not sharing hosts.
Because it's the only mechanism that allows us
On 3 April 2014 08:21, Khanh-Toan Tran khanh-toan.t...@cloudwatt.comwrote:
Otherwise we cannot provide redundancy to client except using Region which
is dedicated infrastructure and networked separated and anti-affinity
filter which IMO is not pragmatic as it has tendency of abusive usage.
Hi all,
2014-04-03 18:47 GMT+02:00 Meghal Gosalia meg...@yahoo-inc.com:
Hello folks,
Here is the bug [1] which is currently not allowing a host to be part of
two availability zones.
This bug was targeted for havana.
The fix in the bug was made because it was assumed
that openstack
I am fine with taking the approach of user passing multiple avail. zones
Az1,Az2 if he wants vm to be in (intersection of AZ1 and Az2).
It will be more cleaner.
But, similar approach should also be used while setting the
default_scheduling_zone.
Since, we will not be able to add host to
Hi,
I'm currently trying to reproduce [1]. This bug requires to have the same
host on two different aggregates, each one having an AZ.
IIRC, Nova API prevents hosts of being part of two distinct AZs [2], so
IMHO this request should not be possible.
That said, there are two flaws where I can
On 04/03/2014 07:51 AM, Sylvain Bauza wrote:
Hi,
I'm currently trying to reproduce [1]. This bug requires to have the
same host on two different aggregates, each one having an AZ.
IIRC, Nova API prevents hosts of being part of two distinct AZs [2], so
IMHO this request should not be possible.
: OpenStack Development Mailing List (not for usage questions)
Objet : [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
Hi,
I'm currently trying to reproduce [1]. This bug requires to have the same
host on two different aggregates, each one having an AZ.
IIRC, Nova
-
De : Chris Friesen [mailto:chris.frie...@windriver.com]
Envoyé : jeudi 3 avril 2014 16:51
À : openstack-dev@lists.openstack.org
Objet : Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible
or not ?
On 04/03/2014 07:51 AM, Sylvain Bauza wrote:
Hi,
I'm currently
Development Mailing List (not for usage questions)
Objet : RE: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible
or not ?
+1 for AZs not sharing hosts.
Because its the only mechanism that allows us to segment the
datacenter.
Otherwise we cannot provide redundancy
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Hosts within two Availability Zones :
possible or not ?
+1 for AZs not sharing hosts.
Because it's the only mechanism that allows us to segment the datacenter.
Otherwise we cannot provide redundancy to client except
- Original Message -
Hi,
I'm currently trying to reproduce [1]. This bug requires to have the same
host on two different aggregates, each one having an AZ.
IIRC, Nova API prevents hosts of being part of two distinct AZs [2], so
IMHO this request should not be possible.
That said,
- Original Message -
Currently host aggregates are quite general, but the only ways for an
end-user to make use of them are:
1) By making the host aggregate an availability zones (where each host
is only supposed to be in one availability zone) and selecting it at
instance
Hello folks,
Here is the bug [1] which is currently not allowing a host to be part of two
availability zones.
This bug was targeted for havana.
The fix in the bug was made because it was assumed
that openstack does not support adding hosts to two zones by design.
The assumption was based on
29 matches
Mail list logo
