The original purpose behind sharing the HostID with a customer was to allow
a customer to identify situations where they had two VMs placed on the same
host. This knowledge is extremely critical if a customer is trying to setup
two VMs in an HA configuration. Because this use case does not
Right so we should really be hashing this with the tenant ID as well.
-jOrGe W.
On Jul 15, 2011, at 6:16 PM, Chris Behrens wrote:
I think it's sensitive because one could figure out how many hosts a SP has
globally... which a SP might not necessarily want to reveal.
- Chris
On Jul
I understand that we're all familiar with virtualization and its benefits.
However, in the Real World, those of us who run clouds often need to work with
physical devices. I've proposed a blueprint and spec for a /hosts admin API
resource that would return information on physical hosts.
I see the v1.1 API spec talks about a 'hostId' item returned when you list your
instances (section 4.1.1 in the spec). These should be the same thing, IMO.
I think you're right, though. I don't believe we have any sort of 'hostId'
today, since hosts just become available by attaching to AMQP.
On Fri, Jul 15, 2011 at 11:31 PM, Chris Behrens chris.behr...@rackspace.com
wrote:
Nevermind. Just found a comment in the API spec that says hostID is
unique per account, not globally. Hmmm...
This is weird ! I can't find anything in the code that says so !! hostID is
just a hashed version
I think it's sensitive because one could figure out how many hosts a SP has
globally... which a SP might not necessarily want to reveal.
- Chris
On Jul 15, 2011, at 3:34 PM, karim.allah.ah...@gmail.com wrote:
On Fri, Jul 15, 2011 at 11:31 PM, Chris Behrens chris.behr...@rackspace.com
6 matches
Mail list logo
