Yes, host is from service table and hypervisor is from compute_nodes table,
I think that there are some discussion for this in Paris Summit and there
might be some change for this in Kilo.

   - Detach service from compute node:
   https://review.openstack.org/#/c/126895/ (implementation on a patch
   series
   
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/detach-service-from-computenode,n,z)
   
<https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/detach-service-from-computenode,n,z%29>


   - Goal : Only provide resources to the ComputeNode object, not anything
   else


   - The primary goal of this blueprint is to decouple the servicegroup API
   from the ideas of tracking resources, since they are two wholly separate
   things

I'm not sure if there are some changes for those commands when host was
added to compute_nodes table.


2014-12-30 14:52 GMT+08:00 Lingxian Kong <anlin.k...@gmail.com>:

> Thanks, Jay Pipes and Jay Lau, for your reply!
>
> 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?
>
> 2014-12-29 21:40 GMT+08:00 Jay Lau <jay.lau....@gmail.com>:
> > Does "nova hypervisor-show" help? It already include the host ip address.
> >
> > 2014-12-29 21:26 GMT+08:00 Jay Pipes <jaypi...@gmail.com>:
> >>
> >> On 12/29/2014 06:51 AM, Lingxian Kong wrote:
> >>>
> >>> Hi Stackers:
> >>>
> >>> As for now, we can get the 'host name', 'service' and 'availability
> >>> zone' of a host through the CLI command 'nova host-list'. But as a
> >>> programmer who communicates with OpenStack using its API, I want to
> >>> get the host ip address, in order to perform some other actions in my
> >>> program.
> >>>
> >>> And what I know is, the ip address of a host is populated in the
> >>> 'compute_nodes' table of the database, during the 'update available
> >>> resource' periodic task.
> >>>
> >>> So, is it possible of the community to support it in the future?
> >>>
> >>> I apologize if the topic was once covered and I missed it.
> >>
> >>
> >> Hi!
> >>
> >> I see no real technical reason this could not be done. It would require
> >> waiting until all of the API microversioning bits are done, and a
> >> micro-increment of the API, along with minimal changes of code in the
> hosts
> >> extension to return the host_ip field from the nova.objects.ComputeNode
> >> objects returned to the HostController object.
> >>
> >> Are you interested in working on such a feature? I would be happy to
> guide
> >> you through the process of making a blueprint and submitting code if
> you'd
> >> like. Just find me on IRC #openstack-nova. My IRC nick is jaypipes.
> >>
> >> Best,
> >> -jay
> >>
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> > --
> > Thanks,
> >
> > Jay
> >
> > _______________________________________________
> > 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
>



-- 
Thanks,

Jay
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to