leap_platform.git/puppet/modules/site_config/templates, branch 0.2.2 [leap_platform] Fix 'Failed to call refresh: /usr/local/sbin/reload_dhclient returned 2 instead 2013-06-30T23:35:32+00:00 Micah Anderson micah@riseup.net 2013-06-30T23:35:32+00:00 1d91ef608855059dbb7938dbd59adf2f70220139 of one of [0]' by putting in the missing closing single quote. Change-Id: I86feb5d06dd25e28ea67da0b5627e7be4174e01e 
of one of [0]' by putting in the missing closing single quote.

Change-Id: I86feb5d06dd25e28ea67da0b5627e7be4174e01e
disable dhclient from modifying the /etc/resolv.conf file on openstack/amazon instances 2013-06-19T17:41:23+00:00 Micah Anderson micah@riseup.net 2013-06-19T17:41:23+00:00 d9614163ed327fc17d27ac623dfd639ce00a43ce The dhclient in these environments is quite aggressive and overwrites the nameservers we've deliberately chosen to use with google's nameservers. This commit attempts to fix that. The dhclient methodology for altering these things is particularly unpleasant. We effectively redefine the functions that mess with this file to be noops in the /etc/dhcp/dhclient-enter-hooks.d directory and then we are forced to restart dhclient by shipping a script that tries to determine the correct PID and arguments that it was running as before killing and restarting it with the same arguments. See debian bugs #681698, #712796 for further discussion about how to make this less difficult Change-Id: I51cf40cf98eaddcefd8180e157b6e3ca824173f0 
The dhclient in these environments is quite aggressive and overwrites the
nameservers we've deliberately chosen to use with google's nameservers. This
commit attempts to fix that.

The dhclient methodology for altering these things is particularly
unpleasant. We effectively redefine the functions that mess with this file to be
noops in the /etc/dhcp/dhclient-enter-hooks.d directory and then we are forced
to restart dhclient by shipping a script that tries to determine the correct PID
and arguments that it was running as before killing and restarting it with the
same arguments.

See debian bugs #681698, #712796 for further discussion about how to make this
less difficult

Change-Id: I51cf40cf98eaddcefd8180e157b6e3ca824173f0
/etc/hosts must not have commas!! 2013-06-12T06:22:57+00:00 elijah elijah@riseup.net 2013-06-12T06:22:57+00:00 722ff7da46de4e656b3a110a65b9ccaa57f82898 






use hiera hashes for source data for /etc/hosts
2013-06-11T23:33:03+00:00

elijah
elijah@riseup.net

2013-06-11T23:33:03+00:00

95d0c71fa4017a7908ccda0adae8057e2115cc42












configure fqdn for host
2013-01-20T14:26:26+00:00

varac
varacanero@zeromail.org

2013-01-20T14:26:26+00:00

d7f7bad9b6d4a45aa06c74a1f630b38a534092e0












configure fqdn for host
2013-01-20T13:09:50+00:00

varac
varacanero@zeromail.org

2013-01-20T13:09:50+00:00

fc59f6c6a22a4659cefa29e18a658c852c6e89f7












test to see if the hosts value is empty before trying to reference it in a template
2012-12-11T20:41:17+00:00

Micah Anderson
micah@riseup.net

2012-12-11T20:37:15+00:00

cbb834da5de7e2abe7399e34766492bfab48fa9c

also set the hostname to what the hiera 'name' is set to





also set the hostname to what the hiera 'name' is set to







setup /etc/hosts based on a template and the hiera value 'hosts'
2012-12-11T18:10:30+00:00

Micah Anderson
micah@riseup.net

2012-12-11T18:10:30+00:00

090dca27921efe22fdc39c8598356bfb74e5fe99

This will replace the existing /etc/hosts, so we will want to make this more smart later





This will replace the existing /etc/hosts, so we will want to make this more smart later