It has been a while since I last looked at running Packer locally, when I did CentOS 8 had just been released. Since then, there has been a little drama around the on-going support of CentOS which is best summed up by the following post in /r/sysadmin/: Off the back of this announcement the Rocky Linux project has been announced, developed and then released. The project describes itself as follows:...
It has been a while as I have been busy writing, I thought I would spend some of my freetime having a very quick play with Ansible AWX, which is the Open Source version of Ansible Tower. I created the following Vagrantfile to launch a CentOS 7 server; # -*- mode: ruby -*- # vi: set ft=ruby : VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "centos/7" config.vm.provider :virtualbox do |v| v....
I have a need to create both some Ubuntu and CentOS Vagrant boxes for a project I am working on. Normally I would have created them on my local machine, uploaded the artifacts to an Amazon S3 bucket and then published them using Atlas (formally Vagrant Cloud). However in the past month HashiCorp have updated Atlas so that you can now build Packer templates directly within Atlas and publish the artifacts as Vagrant Boxes, all free of charge....
I am going to be playing with OpenStack over the next few weeks so I decided to create a Vagrant script which would bootstrap a working OpenStack Kilo installation using RedHat RDO. It uses my CentOS 7 Vagrant box and works with both VirtualBox and VMWare Fusion. To get it up and running create a folder for the Vagrantfile to live; mkdir -p ~/Machines/OpenStack/ Download a copy of the Vagrantfile;...
Vagrant allows developers to bring up local development machines in a controlled method using pre-built configuration files called boxes. Once a box has been installed on the developers local machine it can be powered on with the following command; vagrant up When the box is brought up it automatically provisions itself using a number of provisioners including Puppet, this means that the production deployment scripts can also be run on local development copies of the instances....