Project

General

Profile

Feature #8556

Resolve interface.name when instantiating ProxyAPI::BMC

Added by Nacho Barrientos over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
BMC
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hi,

When a ProxyAPI::BMC object is created for a given host in order to do for instance power operations on it, the 'host_ip' attribute is initialized directly with the value of the 'ip' attribute of the Nic::BMC object (see app/models/nic/bmc.rb).:

15       ProxyAPI::BMC.new({ :host_ip  => ip,
16                           :url      => proxy.url,
17                           :user     => username,
18                           :password => password })

In our environment, we heavily rely on DNS to know the IP address of the BMC, especially during IP renumbering campaigns (when the IP address of the management interface changes, basically). It would be indeed reasonable to ask the people who are responsible for the network operation to update the IP field in Foreman at the same time however we'd like to keep their workflow as tiny as possible.

So, I'd like to propose to (maybe optionally via a configuration switch) resolve the FQDN of the interface when creating the proxy to avoid this problem. Or, alternatively, to pass the FQDN directly to the Foreman proxy and let the resolving happen on the other end.

Not sure I've explained myself clearly or if I've justified what I'm asking for enough, so feel free to ask whatever thing you'd like :)


Related issues

Related to Foreman - Refactor #7456: Extract primary interface from hostClosed2014-09-16

History

#1 Updated by Dominic Cleal over 7 years ago

  • Category set to BMC

#2 Updated by Greg Sutcliffe over 7 years ago

  • Status changed from New to Feedback

We're currently working on a big refactor of the networking system, and I think it'll fix your problem. Perhaps you could watch https://www.youtube.com/watch?v=xmYmMQONq_0 and let us know if that would do the trick?

Thanks!

#3 Updated by Greg Sutcliffe over 7 years ago

  • Related to Refactor #7456: Extract primary interface from host added

#4 Updated by Daniel Lobato Garcia over 7 years ago

Almost, after close inspection the open pull request for #7456 does add the FQDN support for BMC interfaces (any interface in fact), but the proxy API is not using it. After #7456 is merged, which I expect it to happen in early January (it's a really big contribution) we can sort this issue out quite easily, most likely in time for a 1.8 release provided #7456 is merged early.

Take a look at the deep dive though :)

#5 Updated by Nacho Barrientos over 7 years ago

Okay, thanks for the update :)

#6 Updated by Dominic Cleal over 7 years ago

  • Status changed from Feedback to New

Also available in: Atom PDF