-dev] [nova] [scheduler] blueprint for host/hypervisor
location information
Maybe the answer is hiding in plain sight: host aggregates. This is a concept
we already have, and it allows identification of arbitrary groupings for
arbitrary purposes
Mike Spreitzer mspre...@us.ibm.com wrote on 01/10/2013 06:58:10 AM:
Alex Glikson glik...@il.ibm.com wrote on 09/29/2013 03:30:35 PM:
Mike Spreitzer mspre...@us.ibm.com wrote on 29/09/2013 08:02:00 PM:
Another reason to prefer host is that we have other resources to
locate besides
Maybe the answer is hiding in plain sight: host aggregates. This is a
concept we already have, and it allows identification of arbitrary
groupings for arbitrary purposes.___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Alex Glikson glik...@il.ibm.com wrote on 09/29/2013 03:30:35 PM:
Mike Spreitzer mspre...@us.ibm.com wrote on 29/09/2013 08:02:00 PM:
Another reason to prefer host is that we have other resources to
locate besides compute.
Good point. Another approach (not necessarily contradicting)
Host not hypervisor I think; consider nova baremetal, where hypervisor
== machine that runs tftpd and makes IPMI calls, and host == place
where the user workload will execute.
-Rob
On 29 September 2013 17:52, Mike Spreitzer mspre...@us.ibm.com wrote:
I have begun drafting a blueprint about more
Robert Collins robe...@robertcollins.net wrote on 09/29/2013 02:21:28
AM:
Host not hypervisor I think; consider nova baremetal, where hypervisor
== machine that runs tftpd and makes IPMI calls, and host == place
where the user workload will execute.
In nova baremetal, is there still a
On 09/29/2013 01:02 PM, Mike Spreitzer wrote:
Robert Collins robe...@robertcollins.net wrote on 09/29/2013 02:21:28 AM:
Host not hypervisor I think; consider nova baremetal, where hypervisor
== machine that runs tftpd and makes IPMI calls, and host == place
where the user workload will
Monty Taylor mord...@inaugust.com wrote on 09/29/2013 01:38:26 PM:
On 09/29/2013 01:02 PM, Mike Spreitzer wrote:
Robert Collins robe...@robertcollins.net wrote on 09/29/2013
02:21:28 AM:
Host not hypervisor I think; consider nova baremetal, where
hypervisor
== machine that runs tftpd
Mike Spreitzer mspre...@us.ibm.com wrote on 29/09/2013 08:02:00 PM:
Another reason to prefer host is that we have other resources to
locate besides compute.
Good point. Another approach (not necessarily contradicting) could be to
specify the location as a property of host aggregate rather
I have begun drafting a blueprint about more detailed host/hypervisor
location information, to support the sort of policy-informed placement
decision-making that Debo, Yathi, and I have been talking about. The
blueprint is at
10 matches
Mail list logo
