Alex, my understanding is that the motivation for rack-awareness in Hadoop
is optimizing availability rather than networking. The good news, for
those of us who favor a holistic scheduler, is that it can take both sorts
of things into account when/where desired.
Yes, the case of a public
To:OpenStack Development Mailing List
openstack-dev@lists.openstack.org,
Date:13/09/2013 08:54 AM
Subject:Re: [openstack-dev] [nova] [savanna] Host information for
nonadminusers
From: Nirmal Ranganathan rnir
Hi folks,
Currently Nova doesn’t provide information about the host of virtual
machine for non admin users. Is it possible to change this situation? This
information is needed in Hadoop deployment case. Because now Hadoop aware
about virtual environment and this knowledge help Hadoop to achieve a
You can use hostId which is a hash of the host and tenant and part of the
core nova api as well.
On Thu, Sep 12, 2013 at 10:45 AM, Alexander Kuznetsov
akuznet...@mirantis.com wrote:
Hi folks,
Currently Nova doesn’t provide information about the host of virtual
machine for non admin users.
Not host capacity, just a opaque reference to distinguish a host is enough.
Hadoop can use that information to appropriately place block replicas. For
example if the replication count is 3, and if a host/rack topology is
provided to Hadoop, it will place each replica on a different host/rack
From: Nirmal Ranganathan rnir...@gmail.com
...
Not host capacity, just a opaque reference to distinguish a host is
enough. Hadoop can use that information to appropriately place block
replicas. For example if the replication count is 3, and if a host/
rack topology is provided to Hadoop, it
On Fri, Sep 13, 2013 at 12:05 AM, Mike Spreitzer mspre...@us.ibm.comwrote:
From: Nirmal Ranganathan rnir...@gmail.com
...
Not host capacity, just a opaque reference to distinguish a host is
enough. Hadoop can use that information to appropriately place block
replicas. For example if