[DEV] Create a plugin that populates host information for use with jinja templates

[alexlovelltroy]

This task is to get us enough information to generate host-specific files.

example :

hostnames:
interfaces:
  - eth0
     name:
     mac: 
     ip:
     desc:
     netmask:
     hostnames:
  - eth1
     name:
     mac: 
     ip:
     description:
     netmask:
     hostnames:
  - eth2
     name:
     mac: 
     ip:
     description:
     netmask:
     hostnames:

[alexlovelltroy]

Let's be sure to validate the yaml structure in the comments here as well.

[alexlovelltroy]

Adding different network types to SMD may be necessary to get enough information for this plugin.

[alexlovelltroy]

@travisbcotton can you add a jinja template here that you would like to use?

[travisbcotton]

ospfd.conf example:

password testpass123
enable password testpass123

interface {{ host.internal_interface }}
    no ip ospf authentication-key
    ip ospf dead-interval 40
    ip ospf hello-interval 10
    ip ospf priority 0

interface {{ host.external_interface }}
    no ip ospf authentication-key
    ip ospf priority 0
    ip ospf dead-interval 40
    ip ospf hello-interval 10
    ip ospf retransmit-interval 5
    ip ospf transmit-delay 1

router ospf
    ospf router-id {{ host.external_ip }}
    network {{ host.external_subnet }} area 0.0.0.15
    network {{ host.internal_subnet }} area 0.0.0.15
    area 0.0.0.15 stub no-summary

[travisbcotton]

zebra.conf example:

hostname {{ host.name }}
password testpass123
enable password testpass123

interface lo
  description loopback

interface {{ host.internal_interface }}
  description internal Infiniband
  ip address {{ host.internal_ip }}/{{ host.internal_netmask }}

interface {{ host.external_interface }}
  description external Ethernet
  ip address {{ host.external_ip }}/{{ host.external_netmask }}

[davidallendj]

Quick questions:

• Is the {{ host.external_interface }} and {{ host.internal_interface }} just expecting the interface name?
• Is the /{{ host.external_netmask }} in CIDR notation? I'm guessing that whenever you're getting the IP, it's just the IP by itself.

[travisbcotton]

For the first one, yeah that would be the interface name. Which I don't think is available in SMD at /Inventory/EthernetInteraces. Could make the interface names just be a part of the templates, but that would reduce their portability

The second one is the /24 or whatever notation. At least for these templates. Which is also not something inherit in SMD. But appears you can add IPAddresses with the form 192.168.1.1/24 to /Inventory/EthernetInteraces, but that may have an effect on other applications reading those endpoints

[davidallendj]

I was under the impression that the ID was supposed to be the interface name, but I guess not.

That may be the way to go with the IP address since I don't see the net mask stored anywhere. We can try storing the IP addresses in CIDR notation and see if anything breaks.

[davidallendj]

Also, should we expect more than one internal and/or external interface?