cookbook 'dhcp-wrapper', '= 1.1.0', :supermarket
dhcp-wrapper (4) Versions 1.1.0 Follow0
Wrapper around dhcp cookbook
cookbook 'dhcp-wrapper', '= 1.1.0'
knife cookbook site install dhcp-wrapper
knife cookbook site download dhcp-wrapper
Can also configure network interfaces by the use of cookbook network_interfaces_v2, for instance to set a static address at the server and dhcp for the clients.
recipe[dhcp-wrapper::server] in your run-list to install and configure
DHCPD. Configuration will be fetched from attributes
cookbook dhcp documentation
for more information.
recipe[dhcp-wrapper::client] to install a dhcp client.
recipe[dhcp-wrapper::network-interface] to configure your network
interfaces. Configuration is fetched from attributes
node['dhcp-wrapper']['network-interface'] which should match those of
To see an example, look at .kitchen.yml.
This cookbook is fully tested through the installation of a server and a node in docker hosts. This uses kitchen, docker and some monkey-patching.
If you run kitchen list, you will see 2 suites, Each corresponds to a different server:
- server-centos-7: DHCPD server listening on eth1
- node-centos-7: generic node with eth1 configured in dhcp
Note: This configuration need a second interface which is provided by
pipework. Because pipework need
administrative priviledges, sudo access is required to create the dockers
- Initial version with Centos 7 support
- Add support for static routes
Declared in metadata.rb.
Declared in Gemfile.
- RHEL Family 7, tested on Centos
Note: it should work fine on Debian 8 but the official docker image does not allow systemd to work easily, so it could not be tested.
Configuration is done by overriding default attributes. All configuration keys have a default defined in attributes/default.rb. Please read it to have a comprehensive view of what and how you can configure this cookbook behavior.
Install dhclient package.
Create static routes based on
You are more than welcome to submit issues and merge requests to this project.
Your commits must pass
git log --check and messages should be formated
like this (based on this excellent
Summarize change in 50 characters or less Provide more detail after the first line. Leave one blank line below the summary and wrap all lines at 72 characters or less. If the change fixes an issue, leave another blank line after the final paragraph and indicate which issue is fixed in the specific format below. Fix #42
Also do your best to factor commits appropriately, ie not too large with unrelated things in the same commit, and not too small with the same small change applied N times in N different commits. If there was some accidental reformatting or whitespace changes during the course of your commits, please rebase them away before submitting the MR.
All files must be 80 columns width formatted (actually 79), exception when it is not possible.
License and Author
- Author:: Samuel Bernard (email@example.com)
Copyright:: 2015, Sam4Mobile Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
|network_interfaces_v2 >= 0.0.0|
|dhcp >= 0.0.0|
There are no cookbooks that are contingent upon this one.
1.1.0 passed this metric
1.1.0 passed this metric