After my previous issues, I decided to download and install Fedora 20 for my Puppet server VM. A friend had mentioned he prefers Linux distros with a v3 kernel. I installed it and downloaded Puppet Enterprise 3.2.2 for RHEL. I found out, however, that even though there’s mention of supported packages for Fedora, you can’t use the tarball because they say Fedora changes too often to be stable. If you run the installer it says “Unsupported Platform”. Oh well.
So, I downloaded and installed Ubuntu server. My friend also recommends this.
Read more »
Wow! It’s such an adventure. I may have to give the AWS stuff a skip and just use local machines. A friend has offered me an old laptop which I’m going to install CentOS on.
Now I wish to use Ruby 1.8.7 again as Puppet will (hopefully) be happy! A post on a support mailing list said RVM can be used to switch between multiple installed Rubys. Neat! Let’s give it a go:
[root@centos ~]# rvm use 1.8.7
ruby-1.8.7-p374 is not installed.
To install do: 'rvm install ruby-1.8.7-p374'
Read more »
So I wanted to make sure Puppet only supports Ruby 1.8 as I’d seen on a support mailing list. It turns out the main Puppet Supported Platforms page says Puppet 3.5.1 supports Ruby 2.1. Epic win! So I installed it:
First, I need to install the Ruby Version Manager (RVM):
[root@centos ~]# curl -L get.rvm.io | bash -s stable
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 20511 100 20511 0 0 15003 0 0:00:01 0:00:01 --:--:-- 770k
Creating group 'rvm'
Installing RVM to /usr/local/rvm/
cp: cannot stat `/usr/local/rvm/src/rvm/bin/rake': No such file or directory
cp: cannot stat `/usr/local/rvm/src/rvm/bin/bundle': No such file or directory
Installation of RVM in /usr/local/rvm/ is almost complete:
* First you need to add all users that will be using rvm to 'rvm' group,
and logout - login again, anyone using rvm will be operating with `umask u=rwx,g=rwx,o=rx`.
* To start using RVM you need to run `source /etc/profile.d/rvm.sh`
in all your open shell windows, in rare cases you need to reopen all shell windows.
# Thank you for using RVM!
# We sincerely hope that RVM helps to make your life easier and more enjoyable!!!
# ~Wayne, Michal & team.
In case of problems: http://rvm.io/help and https://twitter.com/rvm_io
Read more »
Recently, I’ve decided to start learning Puppet from PuppetLabs.
I created a CentOS VM using VMWare Player and have been setting up an environment in which I can use Puppet to provision an AWS EC2 server and set up services, etc.
Unfortunately, I’ve had some issues with getting the Cloud Provisioner to work.
The Puppet website says to install the Cloud Provisioner, you install Puppet and it asks you if you wish to install the Provisioner during installation. However, their site recommends installing Puppet using YUM and not the tarball. The YUM installer does not ask if you wish to install the Cloud Provisioner so that does not help. The website also says you can post-install it by downloading the tarball and use YUM to install it from the ‘packages’ directory in the tarball. Unfortunately, the tarball does not have a ‘packages’ directory in it, so that does not help.
I did find a Cloud Provisioner Puppet module which could be installed to provide the Cloud Provisioner node_aws. This breaks the ‘puppet node’ command as I discovered after many attempts to get it to work. I found on the Puppet discussion group a post a couple of years ago, which apparently has not been resolved.
[Puppet – Bug #16651] Installing the cloud provisioner module breaks the node subcommand
Read more »