It's very easy to create a Kickstart tree in Spacewalk and that to in a Automated fashion for provisioning hosts. All you have to do is create a Base Channel for CentOS and then create a Repo and then marry both and then at the time of Repo sync choose the option of "Creating a kickstartable tree".

Add a comment

Its possible to configure Puppetdb with PostgreSQL as its much more manageable as compared to the in-built DB that comes with Puppetdb i.e. HSQLDB. Plus its much easier to query and troubleshoot any issues you comes across especially when using Puppet Hiera and exported resources. Follow this easy to follow guide and you should be up and running with a basic config of Puppetdb in no time.

Add a comment

Its possible to run a script via Alias command. All you need is to modify the .bashrc and then source the script in the required user profile. Alias commands are very useful when it comes to running shortened versions of commands or a complex script to be run using just a single line of command. Currently I use this to run 2 of my custom scripts for waking up a ESXi server via WOL (Wake-ON-LAN).

Add a comment

Wake-On-LAN (WOL) is a very useful feature if you have got a LAB at home and want to make it energy efficient. I have written a small BASH script to automate the Wake-On-LAN (WOL) procedure which can be used in an instance where there is a ESXi server which can turned on as and when required and then shutdown when not needed. Believe me it saves a lot on electric bills as the Servers are not running 24/7 and powered on only when required.

Add a comment

It’s possible to enable DNS forwarding using BIND and including reverse lookup for the zone. Once you are done with the config of a basic bind server, all you need to do is configure "/etc/bind/named.conf.options and conf.local" with the following options and restart the service.

In this example we have got 2 DNS server's resolving.

SERVER1 = raspi-qud.hm.local = domain : HM.LOCAL : IP: 172.16.64.1

SERVER 2 = viz-raspi-st.dev.local = domain : DEV.LOCAL :IP: 172.16.66.212

We need to resolve local requests for "hm.local" on SERVER 1 and forward any "dev.local" domain requests (forward and reverse lookups) to SERVER 2 and hence need to configure SERVER 1  to achieve this.

To start with add the zone dev.local to "/etc/bind/named.conf.local" and add the forward zone to the config file.

Add a comment