Retrieving the IP Address of an interface is too difficult

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 0.2.0
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

ipaddress_eth0 = host["network"]["interfaces"]["eth0"]["addresses"].select { |address, data| data["family"] == "inet" }[0][0]

["ipaddress"] tends to be the last address found? Currently eth1 in my test case.

You could do ipaddress as a hash with interface names as a key, if you want to stick with ipv4 being what we usually want.

Issue Links

clone of

Improvement - An improvement or enhancement to an existing feature or task. OHAI-286 Network plugin has no specs

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.
is duplicated by

New Feature - A new feature of the product, which has yet to be developed. OHAI-411 Ohai should populate an ipaddress attribute with an array of addresses.

  • Unknown - Issue untriaged, priority unassigned or questioned
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Toomas Pelberg added a comment -

Please merge https://github.com/toomasp/ohai/tree/OHAI-88

getting the ip of the interface is as easy as ipaddress_eth0 = @ohai.get_interface_ip("eth0")

Show
Toomas Pelberg added a comment - Please merge https://github.com/toomasp/ohai/tree/OHAI-88 getting the ip of the interface is as easy as ipaddress_eth0 = @ohai.get_interface_ip("eth0")
Hide
Permalink
Bryan McLellan [Opscode] added a comment -

This is a larger issue that needs some discussion. Rather than providing a wrapper method, we'd like to find a better solution.

It may not be possible. What would be great is some kind of pointer reference in JSON to connect to the ipv4 address of an interface. Or at least, it may sound great until we saw it.

Another option would be putting ipv4 addresses in two location, and living with the duplication.

If someone feels strongly about this they are encouraged to bring it up on the chef-dev mailing list.

Show
Bryan McLellan [Opscode] added a comment - This is a larger issue that needs some discussion. Rather than providing a wrapper method, we'd like to find a better solution. It may not be possible. What would be great is some kind of pointer reference in JSON to connect to the ipv4 address of an interface. Or at least, it may sound great until we saw it. Another option would be putting ipv4 addresses in two location, and living with the duplication. If someone feels strongly about this they are encouraged to bring it up on the chef-dev mailing list.

People

  • Assignee:
    Unassigned
    Reporter:
    Bryan McLellan [Opscode]
Vote (0)
Watch (3)

Dates

  • Created:
    Updated: