Mike, this has been really fun, but it is starting to feel like a
rabbit hole.
The case for having one feels legitimate. However, at this point, I think
someone will need to actually build it, or the idea is just a pipe dream.
Excerpts from Mike Spreitzer's message of 2013-09-30 19:21:22 -0700:
Clint Byrum cl...@fewbar.com wrote on 10/01/2013 02:38:53 AM:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 10/01/2013 02:40 AM
Subject: Re: [openstack-dev] [scheduler] [heat] Policy specifics
(for holistic infrastructure scheduling)
Mike
On 27/09/13 17:58, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2013-09-27 06:58:40 -0700:
On 27/09/13 08:58, Mike Spreitzer wrote:
I have begun to draft some specifics about the sorts of policies that
might be added to infrastructure to inform a smart unified placement
engine.
Excerpts from Zane Bitter's message of 2013-09-30 03:33:32 -0700:
On 27/09/13 17:58, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2013-09-27 06:58:40 -0700:
On 27/09/13 08:58, Mike Spreitzer wrote:
I have begun to draft some specifics about the sorts of policies that
might be
On 30/09/13 17:33, Clint Byrum wrote:
You are painting cloud providers as uncaring slum lords. Of course there
will be slum lords in any ecosystem, but there will also be high quality
service providers and private cloud operators with high expectations that
can use this type of feature as
OK, let's take the holistic infrastructure scheduling out of Heat. It
really belongs at a lower level anyway. Think of it as something you slap
on top of Nova, Cinder, Neutron, etc. and everything that is going to use
them goes first through the holistic scheduler, to give it a chance to
I have begun to draft some specifics about the sorts of policies that
might be added to infrastructure to inform a smart unified placement
engine. These are cast as an extension to Heat templates. See
https://wiki.openstack.org/wiki/Heat/PolicyExtension . Comments
solicited.
Regards,
On 27/09/13 07:58, Mike Spreitzer wrote:
I have begun to draft some specifics about the sorts of policies that
might be added to infrastructure to inform a smart unified placement
engine. These are cast as an extension to Heat templates. See
Stephen Gran stephen.g...@theguardian.com wrote on 09/27/2013 04:26:37
AM:
Maybe I'm missing something obvious, but I'm not convinced all that
logic belongs in Heat. I would expect nova and related components to
expose grouping information (availability zones in nova, networks in
On 27/09/13 08:58, Mike Spreitzer wrote:
I have begun to draft some specifics about the sorts of policies that
might be added to infrastructure to inform a smart unified placement
engine. These are cast as an extension to Heat templates. See
On 27/09/13 14:27, Mike Spreitzer wrote:
Stephen Gran stephen.g...@theguardian.com wrote on 09/27/2013 04:26:37 AM:
I think that your use case for anti-collocation (which is a very good
and important use case, don't get me wrong) is covered by using
availability zones/cells/regions and
Excerpts from Zane Bitter's message of 2013-09-27 06:58:40 -0700:
On 27/09/13 08:58, Mike Spreitzer wrote:
I have begun to draft some specifics about the sorts of policies that
might be added to infrastructure to inform a smart unified placement
engine. These are cast as an extension to
Stephen Gran stephen.g...@theguardian.com wrote on 09/27/2013 10:46:09
AM:
If the admins of the openstack install wanted users to be able to select
placement by rack, surely the availability zones would be rack1 - rack5
? In this case, the user would write:
Resources : {
MyASG
Clint Byrum cl...@fewbar.com wrote on 09/27/2013 11:58:16 AM:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 09/27/2013 12:01 PM
Subject: Re: [openstack-dev] [scheduler] [heat] Policy specifics
...
Mike,
These are not the kinds
Zane also raised an important point about value. Any scheduler is serving
one master most directly, the cloud provider. Any sane cloud provider has
some interest in serving the interests of the cloud users, as well as
having some concerns of its own. The way my group has resolved this is in
Excerpts from Mike Spreitzer's message of 2013-09-27 11:51:20 -0700:
Clint Byrum cl...@fewbar.com wrote on 09/27/2013 11:58:16 AM:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 09/27/2013 12:01 PM
Subject: Re: [openstack-dev] [scheduler
16 matches
Mail list logo
