Hi
Sorry If I didn't understand clearly about it , looks to me
the hypervisor itself hosts the instances and it should have a IP with it
(like Linux host KVM instances, Linux is the hypervisor, the PC is the
host)
while the host is physical node and only to be used by
'hypervisor' concept ,so I think maybe we don't need ip for the 'host' ?
thanks a lot
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
From: Lingxian Kong <anlin.k...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 12/31/2014 07:22 AM
Subject: Re: [openstack-dev] [Nova] should 'ip address' be retrived when
decribe host?
Thanks Kevin for your clarification, which further affirms my belief
that ip address should be included in the host info.
I will contact Jay Pipes on IRC, to see what can I help towards this
effort, soon after the New Year's Day in China. :)
2014-12-31 0:34 GMT+08:00 Kevin L. Mitchell <kevin.mitch...@rackspace.com>:
> On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:
>> Just as what Jay Lau said, 'nova hypervisor-show <hypervisor_id>'
>> indeed returns host ip address, and there are more other information
>> included than 'nova host-describe <hostname>'. I feel a little
>> confused about the 'host' and 'hypervisor', what's the difference
>> between them? For cloud operator, maybe 'host' is more usefull and
>> intuitive for management than 'hypervisor'. From the implementation
>> perspective, both 'compute_nodes' and 'services' database tables are
>> used for them. Should them be combined for more common use cases?
>
> Well, the host and the hypervisor are conceptually distinct objects.
> The hypervisor is, obviously, the thing on which all the VMs run. The
> host, though, is the node running the corresponding nova-compute
> service, which may be separate from the hypervisor. For instance, on
> Xen-based setups, the host runs in a VM on the hypervisor. There has
> also been discussion of allowing one host to be responsible for multiple
> hypervisors, which would be useful for providers with large numbers of
> hypervisors.
> --
> Kevin L. Mitchell <kevin.mitch...@rackspace.com>
> Rackspace
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Regards!
-----------------------------------
Lingxian Kong
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
