settingsLogin | Registersettings

[openstack-dev] [Nova] should 'ip address' be retrived when decribe host?

0 votes

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.

--
Regards!


Lingxian Kong
asked Dec 29, 2014 in openstack-dev by Lingxian_Kong (5,600 points)   1 3 7
retagged Feb 25, 2015 by admin

10 Responses

0 votes

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

responded Dec 29, 2014 by Jay_Pipes (59,760 points)   3 11 14
0 votes

Does "nova hypervisor-show" help? It already include the host ip address.

2014-12-29 21:26 GMT+08:00 Jay Pipes :

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 at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Thanks,

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

responded Dec 29, 2014 by Jay_Lau (7,320 points)   1 8 11
0 votes

Thanks, Jay Pipes and Jay Lau, for your reply!

Just as what Jay Lau said, 'nova hypervisor-show '
indeed returns host ip address, and there are more other information
included than 'nova host-describe '. 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.513 at gmail.com>:

Does "nova hypervisor-show" help? It already include the host ip address.

2014-12-29 21:26 GMT+08:00 Jay Pipes :

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 at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Thanks,

Jay


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

--
Regards!


Lingxian Kong
responded Dec 30, 2014 by Lingxian_Kong (5,600 points)   1 3 7
0 votes

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.

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.kong at gmail.com>:

Thanks, Jay Pipes and Jay Lau, for your reply!

Just as what Jay Lau said, 'nova hypervisor-show '
indeed returns host ip address, and there are more other information
included than 'nova host-describe '. 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.513 at gmail.com>:

Does "nova hypervisor-show" help? It already include the host ip address.

2014-12-29 21:26 GMT+08:00 Jay Pipes :

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 at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Thanks,

Jay


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

--
Regards!


Lingxian Kong


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

--
Thanks,

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

responded Dec 30, 2014 by Jay_Lau (7,320 points)   1 8 11
0 votes

On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:
Just as what Jay Lau said, 'nova hypervisor-show '
indeed returns host ip address, and there are more other information
included than 'nova host-describe '. 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.mitchell at rackspace.com>
Rackspace

responded Dec 30, 2014 by Kevin_L._Mitchell (4,550 points)   1 2 2
0 votes

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.mitchell at rackspace.com>:

On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:

Just as what Jay Lau said, 'nova hypervisor-show '
indeed returns host ip address, and there are more other information
included than 'nova host-describe '. 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.mitchell at rackspace.com>
Rackspace


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

--
Regards!


Lingxian Kong
responded Dec 31, 2014 by Lingxian_Kong (5,600 points)   1 3 7
0 votes

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 at IBMCN Internet: jichenjc at cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC

From: Lingxian Kong <anlin.kong at gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"

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.mitchell at rackspace.com>:
On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:

Just as what Jay Lau said, 'nova hypervisor-show '
indeed returns host ip address, and there are more other information
included than 'nova host-describe '. 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.mitchell at rackspace.com>
Rackspace


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

--
Regards!


Lingxian Kong


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL:

responded Dec 31, 2014 by Chen_CH_Ji (3,540 points)   4 8
0 votes

On Wed, 2014-12-31 at 20:56 +0100, Chen CH Ji wrote:
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

The hypervisor hosts the VMs, yes, but the component that sits between
the hypervisor and the rest of nova?that is, nova-compute?does not
necessarily reside on the hypervisor. It is the nova-compute node
(which may be either a VM or a physical host) that is referred to by the
nova term "host". For KVM, I believe the host is often the same as the
hypervisor, meaning that nova-compute runs directly on the hypervisor?
but this is not necessarily the case for all virt drivers. For example,
the host for Xen-based installations is often a separate VM on the same
hypervisor, which would have its own distinct IP address.
--
Kevin L. Mitchell <kevin.mitchell at rackspace.com>
Rackspace

responded Dec 31, 2014 by Kevin_L._Mitchell (4,550 points)   1 2 2
0 votes

ok, that make sense to me , thanks a lot

Best Regards!

Kevin (Chen) Ji ? ?

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM at IBMCN Internet: jichenjc at cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC

From: "Kevin L. Mitchell" <kevin.mitchell at rackspace.com>
To:
Date: 12/31/2014 09:37 PM
Subject: Re: [openstack-dev] [Nova] should 'ip address' be retrived when
decribe host?

On Wed, 2014-12-31 at 20:56 +0100, Chen CH Ji wrote:
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

The hypervisor hosts the VMs, yes, but the component that sits between
the hypervisor and the rest of nova?that is, nova-compute?does not
necessarily reside on the hypervisor. It is the nova-compute node
(which may be either a VM or a physical host) that is referred to by the
nova term "host". For KVM, I believe the host is often the same as the
hypervisor, meaning that nova-compute runs directly on the hypervisor?
but this is not necessarily the case for all virt drivers. For example,
the host for Xen-based installations is often a separate VM on the same
hypervisor, which would have its own distinct IP address.
--
Kevin L. Mitchell <kevin.mitchell at rackspace.com>
Rackspace


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL:
responded Dec 31, 2014 by Chen_CH_Ji (3,540 points)   4 8
0 votes

On Dec 31, 2014, at 12:35 PM, Kevin L. Mitchell <kevin.mitchell at rackspace.com> wrote:

but this is not necessarily the case for all virt drivers. For example,
the host for Xen-based installations is often a separate VM on the same
hypervisor, which would have its own distinct IP address.

This is quite similar to how Openstack / xCat / zVM would work together.

Cheers,
-j

responded Dec 31, 2014 by James_Downs (620 points)   1
...