Merge lp://qastaging/~anotherjesse/nova/fix-nova-manage-floating-list into lp://qastaging/~hudson-openstack/nova/trunk

Proposed by Jesse Andrews
Status: Work in progress
Proposed branch: lp://qastaging/~anotherjesse/nova/fix-nova-manage-floating-list
Merge into: lp://qastaging/~hudson-openstack/nova/trunk
Diff against target: 28 lines (+5/-10)
1 file modified
bin/nova-manage (+5/-10)
To merge this branch: bzr merge lp://qastaging/~anotherjesse/nova/fix-nova-manage-floating-list
Reviewer Review Type Date Requested Status
Trey Morris (community) Needs Information
Brian Waldon (community) Needs Information
Review via email: mp+69579@code.qastaging.launchpad.net

Description of the change

update nova-manage floating list to show allocation/association status

To post a comment you must log in.
Revision history for this message
Jason Kölker (jason-koelker) wrote :

If the host field isn't used anymore can we get rid of init_host_floating_ips in the FloatingIP mixin and the floating_ip_get_all_by_host in the dbapi?

Revision history for this message
Brian Waldon (bcwaldon) wrote :

Here's one of the rows that comes out of 'nova fixed list' on my nova-compute node 'nova1' using this branch:

network IP address MAC address hostname host
192.168.0.0/25 192.168.0.0 02:16:3e:10:12:37 my_server nova1

The 'host' and 'hostname' labels are synonymous to me. Maybe you can change the hostname label to instance_name? And some capitalization would be nice :)

review: Needs Information
Revision history for this message
Trey Morris (tr3buchet) wrote :

something isn't quite right here. A floating IP's host refers to the network node doing the NAT. This should be getting set. I'm looking into it...

Revision history for this message
Trey Morris (tr3buchet) wrote :

OK i see what's happening. Prior to multi-nic floating IPs were owned by a particular network host. I embraced the concept of floating by not assigning floating IPs to a certain host, but instead referring to the floating IP's fixed IP's network's host whenever it was necessary. This way floating IPs are never tied to a certain host.

I can see two ways to move forward from here. We can set the host at the time the floating IP is associated with a fixed IP in order to refer to it, or we can remove the host column and get to the host as described above. floatin_ip_get_by_host() actually still makes sense because if a floating IP is associated there will be a network host (or a compute host in vish's ha-net, same difference) performing NAT for this address. We may want to find this information for cases where a network host goes down or needs to be replaced.

I guess what I'd like to see are examples of the current uselessness of the command as well as an example of a useful output.

review: Needs Information
Revision history for this message
Jesse Andrews (anotherjesse) wrote :

Trey: I talk about the report issues in the bug:

result:

* output doesn't show who they are allocated to (the project)
* output shows "host" (which is None) since that field doesn't seem to be used any more
* output shows instance hostname, which is unusable since there is no uniqueness constraint

expected:

* show the project (if any) the floating ip is allocated to
* show the instance name instead of hostname if associated with an instance
* don't show host since it isn't used

Unmerged revisions

1337. By Jesse Andrews

Modified the output of nova-manage floating list to show allocation and assocation

Also removed the old "host" semantics since it isn't used anymore

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.