Project

General

Profile

Feature #2089

Expose network configuration via ENC

Added by Brian Rak over 6 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
External Nodes
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

I'd like to see the hosts network information exposed as parameters in the ENC output. Currently we have to duplicate all this information via host parameters (we use things like main_ip => 10.0.0.5, main_gateway => 10.0.0.1, main_subnet_mask => 255.255.255.0). It would be nice to not have to duplicate all this.

Basically, everything on the subnet page would be nice to have access to from puppet classes.


Related issues

Related to Foreman - Feature #2240: Full Multiple Interface SupportClosed2013-02-20
Related to Foreman - Tracker #2409: NetworkingNew

Related to Foreman - Bug #8546: New ENC output for iinterfaces clashes with FacterClosed2014-12-02
Related to Foreman - Bug #8433: Humanized name (type) of NIC works only for managed interfaces in ENC outputClosed2014-11-18
Related to Foreman - Feature #8685: Netmask in ENC outputClosed2014-12-12
Related to Foreman - Bug #8779: VLAN_ID - Subnet Foreman 1.7.1Closed2014-12-22

Associated revisions

Revision a1b2ee53 (diff)
Added by Marek Hulán over 4 years ago

Fixes #2089 - Add network configuration to ENC

History

#1 Updated by Benjamin Papillon over 5 years ago

  • Description updated (diff)
  • Status changed from New to Feedback

Hi,

It is possible from 1.2 or 1.3 I don't remember exactly. You have to define the parameters like gateway and DNS in the corresponding Subnet.
Then you can access these informations using the instructions on this wiki page : http://projects.theforeman.org/projects/foreman/wiki/TemplateWriting

Tell me if this solution is workign for you or if you are waiting for full resolution of #2240.

Regards

#2 Updated by Marek Hulán almost 5 years ago

#3 Updated by Marek Hulán almost 5 years ago

  • Category set to External Nodes
  • Status changed from Feedback to New

We should publish all networking (not just subnet) info we have in ENC, namespacing it with a configurable string so users can avoid potential clashes with other networking facts.
We should also add some helpers to that existing puppet classes can be fed with data in a better form that <%= @host.interfaces.first.subnet.gateway %>

#4 Updated by Marek Hulán almost 5 years ago

  • Status changed from New to Assigned
  • Assignee set to Marek Hulán
  • Target version set to 1.7.2

#5 Updated by The Foreman Bot almost 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/1862 added
  • Pull request deleted ()

#6 Updated by Marek Hulán almost 5 years ago

I decided not to make key name configurable. We can collide only with custom global parameters and facts which still comes from Foreman. We already add a lot of other information so if this is needed we should either move all (with some backward compatibility) or none. Feel free to add your comments to the PR if you don't agree.

#7 Updated by Marek Hulán over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#8 Updated by Dominic Cleal over 4 years ago

  • Legacy Backlogs Release (now unused) set to 21

#9 Updated by Bryan Kearney over 4 years ago

  • Bugzilla link set to 1166162

#10 Updated by Dominic Cleal over 4 years ago

  • Related to Bug #8546: New ENC output for iinterfaces clashes with Facter added

#11 Updated by Dominic Cleal over 4 years ago

  • Related to Bug #8433: Humanized name (type) of NIC works only for managed interfaces in ENC output added

#12 Updated by Dominic Cleal over 4 years ago

#13 Updated by Dominic Cleal over 4 years ago

  • Related to Bug #8779: VLAN_ID - Subnet Foreman 1.7.1 added

Also available in: Atom PDF