Vox Pupuli Tasks

Repo Checks ( 16 of 22 successfull )

passed

failed

passed

failed

passed

failed

passed

failed

passed

failed

passed

add parameters option for hosts

needs-work

merge-conflicts

Pull Request (PR) description

A parameters option should be added to the host resource. There are some use-cases in which this can be very helpful if you want to overwrite global parameters for a single host. (for instance the filename parameter) This implementation is very flexible.
Thank you in advance!

Open PR in GitHub

puppetlabs/stdlib: Allow 9.x

enhancement

Open PR in GitHub

Adding a variable to allow the declaration of the next-server IP

needs-work

merge-conflicts

We use the parameters variable to have next-server statement which is used to specify the host address of the server from which the initial boot file (specified in the filename statement) is to be loaded (TFTP). Server-name is a numeric IP address on our primary DataCenter. Will be very helpful for us if this variable can be added and we can use fully the externale module:

example:
dhcpd::host { 'vh16-la':
mac => 'AC:1F:6B:41:6C:FA',
ip => 'vh16-la.vlan3',
options => { 'host-name' => 'vh16-la'},
parameters => { 'next-server' => '192.168.3.253'},
}

Thanks

Open PR in GitHub

Allow passing hostnames to $dhcp::host::ip

merge-conflicts

bug

needs-work

Pull Request (PR) description

This changes the $ip validation so that you can use a valid fqdn value in addition to ipv4 and ipv6 to determine which IP should be allocated to a host. This uses DNS lookups based on the fqdn in the fixed-address field. The result is that you can manage all of your IP allocation from DNS instead of having to duplicate the same information in DHCP.

I also added an optional parameter that allows you to specify the max-lease-time in the each DHCP pools scope, which will override the default value in dhcpd.conf. This allows you to have different lease times for different pools.