Vox Pupuli Tasks Repositories About
Log in

GitHub puppet-dhcp
Puppet module for deploying dhcp

Repo Checks ( 16 of 22 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Archlinux
No translation
failed
Supports Latest Archlinux
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Debian
No translation
passed
Supports Latest Debian
No translation
passed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
failed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

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
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.

This Pull Request (PR) fixes the following issues

Fixes #224

Open PR in GitHub
modulesync 5.4.0
modulesync

modulesync 5.4.0

Open PR in GitHub
dhcpd.conf.ddns: allow overriding zone primary nameserver

Add 2 parameters, ddnszonenameservers and ddnszonenameserversipv6, which defaults to nameservers and nameserversipv6, but can be changed for scenarios where the nameserver for DDNS updates is not the same as the nameserver the DHCP server provides to DHCP clients.

Open PR in GitHub