This is my work in progress to setup a build environment to build baseboxes with Packer for VMware vCloud to be used with Vagrant and the vagrant-vcloud plugin. The basebox build environment itself can be built with the same tools and created inside the vCloud, eating and creating its own dogfood.
On your host machine you will need the following tools installed:
- Vagrant 1.7.1
- vagrant-vcloud plugin 0.4.4 (pre-release) with the command
vagrant plugin install vagrant-vcloud-0.4.4.gem - Your vCloud access informations in your global
~/.vagrant.d/Vagrantfile
After that you should clone this repo and have some customizations. See below for more details.
Now you can build the vApp 'the Vagrant way':
vagrant up --provider=vcloudThis will spin up an vApp with three VMs:
The basebox-jenkins VM is an Ubuntu 14.04 server with a Jenkins server installed. This server has the IP address 176.16.32.2 and the HTTP port of Jenkins web interface listens on port 80.
A port forwarding is done even through your vCloud edge gateway if you have to use it.
Check out for the forwarded port while spinning up the vApp, or check it later with
vagrant vcloud -nSo you can retrieve the correct IP address and port number to access the Jenkins web interface from your host machine.
You can login to your jenkins server with just the following command:
vagrant ssh basebox-jenkinsThe vmware-slave VM is a Windows machine (I use a windows_2008_r2). This machine has the IP address 176.16.32.3 and has RDP, SSH and WinRM ports opened. This VM will build baseboxes for the vCloud provider, but could also be used to build baseboxes for the VMware Workstation/Fusion provider.
You can login to your jenkins slave with RDP with the following command:
vagrant rdp vmware-slaveAfter creating the vmware-slave VM you have to licsense the installed VMware Workstation manually. I have added a command in the ./scripts/provision-vmware-slave.bat script to directly enter the VMware license, but I cannot put that into the repo.
This is a good situation to test the vagrant rdp vmware-slave which works nice.
The software installed in the vmware-slave is:
- Chocolatey - package like installations on Windows
- packer 0.7.5 or optional packer from source
- packer-post-processor-vagrant-vmware-ovf 0.2.1
- VMware Workstation 10.0.4
- Vagrant 1.7.1
- vagrant-vcloud 0.4.4
- optional global Vagrantfile from host (
./resources/Vagrantfile-global) - msysgit
- wget
- Java + Jenkins Swarm Client (Node labels: windows + vmware)
The vbox-slave VM is a Windows machine (I use a windows_2008_r2). This machine has the IP address 176.16.32.4 and has RDP, SSH and WinRM ports opened. This VM will build baseboxes for the VirtualBox provider.
Notice: My intended hostname was virtualbox-slave, but that is too long for windows, and guest customizations of vCloud aborts with an error.
You can login to your jenkins slave with RDP with the following command:
vagrant rdp vbox-slaveThe software installed in the vbox-slave is:
- Chocolatey - package like installations on Windows
- packer 0.7.5
- VirtualBox 4.3.16
- msysgit
- wget
- Java + Jenkins Swarm Client (Node labels: windows + virtualbox)
As I have started the project much smaller with simple shell provisioning scripts, it still has its roots in plain shell scripts. Perhaps in the future there will be some higher level solution with Chef, Puppet, Ansible, ...
In the Vagrantfile you may adjust the boxes and box_urls used for the three VMs.
As I cannot make the Windows VM public, I will change at least the box_url of the Ubuntu VM to one pointing to the vagrantcloud soon.
Edit the file ./scripts/install-jenkins-server.sh to change the smtpHost
Notice: Manual step: Log into the vmware-slave machine and enter the license of VMware Workstation. If you start jobs from Jenkins without entering a license or the trial, the vmware-slave will hang.
In the vmware-slave box also Vagrant will be installed to test and upload the generated vcloud boxes.
Your user credentials to access the vCloud org could be passed with an optional global Vagrantfile.
This file must be placed at ./resources/Vagrantfile-global and will be copied on provisioning into %USERPROFILE%\.vagrant.d\Vagrantfile.
A sample Vagrantfile-global looks like this:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
if Vagrant.has_plugin?("vagrant-vcloud")
# vCloud Director provider settings
config.vm.provider :vcloud do |vcloud|
vcloud.hostname = "https://YOUR-VCLOUD"
vcloud.username = "vagrant"
vcloud.password = 'S@perS$cretP1ass'
vcloud.org_name = "YOUR-ORG"
vcloud.vdc_name = "YOUR-VDC"
vcloud.catalog_name = "BASEBOX-TESTING"
vcloud.vdc_network_name = "YOUR-NETWORK"
# we do not need a edge gateway as the vmware-slave already is inside the vCloud
# vcloud.vdc_edge_gateway = "YOUR-EDGE"
# vcloud.vdc_edge_gateway_ip = "10.100.50.4"
end
end
endI suggest a BASEBOX-TESTING catalog for test uploads in the Jenkins build jobs.
In the vmware-slave the upload of the generated basebox will be done with ovftool. The script for the upload also needs your connection data and credentials to connect to your vCloud org.
This file must be placed at ./resources/test-box-vcloud-credentials.bat and will be used in the Jenkins jobs in the script bin/test-box-vcloud.bat (see my ubuntu-vm Repo).
A sample test-box-vcloud-credentials.bat looks like this:
@set vcloud_hostname=YOUR-VCLOUD
@set vcloud_username=vagrant
@set vcloud_password=S@perS$cretP1ass
@set vcloud_org=YOUR-ORG
@set vcloud_catalog=BASEBOX-TESTING
@set vcloud_vdc=YOUR-VDCI use the @ sign in the script to hide it in Jenkins console logs.
I suggest a BASEBOX-TESTING catalog for test uploads in the Jenkins build jobs.
This is done with the file ./resources/test-box-vcloud-credentials.bat provided from the host
In the vmware-slave the upload of the tested basebox will be done with ovftool. The script for the upload also needs your connection data and credentials to connect to your global vCloud org.
This file must be placed at ./resources/upload-vcloud-credentials.bat and will be used in the upload *Jenkins jobs in the inlined script.
A sample upload-vcloud-credentials.bat looks like this:
@set vcloud_hostname=YOUR-VCLOUD
@set vcloud_username=YOUR-UPLOAD-USER
@set vcloud_password=S@perS$cretP1ass
@set vcloud_org=YOUR-GLOBAL-ORG
@set vcloud_catalog=YOUR-GLOBAL-CATALOG
@set vcloud_vdc=YOUR-GLOBAL-VDCI use the @ sign in the script to hide it in Jenkins console logs.
I suggest a COM-BUILD-CATATLOG catalog for test uploads in the Jenkins build jobs.
This is done with the file ./resources/upload-vcloud-credentials.bat provided from the host.
I use grunt-jenkins to customize and backup the Jenkins configuration. So my Jenkins box is only a throw away product to be set up again with Jenkins job configurations from source control.
My current Jenkins jobs are stored in this repo as well in the directory jenkins-configuration.
On your host machine, you will need node, npm and grunt:
brew update
brew install node
npm install -g grunt-cli
On you host machine, you have to call
npm install
to install grunt-jenkins and other Node dependencies.
In the Gruntfile.js you have to enter the Jenkins IP address and port to connect from your host to the Jenkins VM.
In my case this is 10.100.50.4 as you can see in the Gruntfile.js. With grunt-jenkins 0.5.0 or above you can backup and restore through your vCloud Edge Gateway.
You can install my prebuilt Jenkins job configuration using:
grunt jenkins-install
When you added / removed plugins you must restart Jenkins:
curl -X POST http://10.100.50.4/safeRestart
Have a look at the Jenkins jobs, there you can see how I build the baseboxes and from with GitHub Repos they come from. See below for more details.
After each time you made changes to the global Jenkins configuration, plugins or jobs just do:
grunt jenkins-backup
git add jenkins-configuration
git commit
This will backup all stuff to the jenkins-configuration folder. You may put it under version control, yay!
So the whole Jenkins server could be destroyed and rebuilt with another vagrant up --provider=vcloud.
If you build packer baseboxes you propably know that a successful build is one thing, but a tested basebox would be even better.
All of my Jenkins jobs you can find in this repo do some tests within the vCloud. Each Jenkins job looks like this:
- Build the Linux/Windows basebox with packer for the vcloud provider
- Add the basebox to vagrant with
vagrant add box - Upload the basebox with ovftool into a
BASEBOX-TESTINGcatalog in vCloud - Create a test vApp with the new Linux/Windows box with a minimal Vagrantfile and
vagrant up --provider=vcloud - Run some Serverspec tests for both Linux/Windows with the vagrant-serverspec plugin 1.0.1
- Windows serverspec tests are in windows_vcloud.rb
- Linux serverspec tests are in ubuntu_vcloud.rb
- Destroy the vApp again with
vagrant destroy -f - Remove the basebox from vagrant with
vagrant box remove - Upload the tested basebox into a global catalog.
If you just want to view into Jenkins use this command:
open http://10.100.50.4/
You also can see the automatically added Jenkins node vmware-slave in the list of nodes:
After successfully running some Jenkins jobs to build baseboxes, vagrant-vcloud even can eat its own dogfood. The workspace of the vmware-slave is accessible through the Jenkins server, as shown here:
So pick up the URL of the generated box file and feed vagrant on your host:
vagrant box add ubuntu1404-desktop http://10.100.50.4/job/ubuntu1404-desktop_vmware/ws/ubuntu1404-desktop_vmware.boxBut Jenkins could also be used to test the basebox and upload it to your basebox repo or to the Vagrant Cloud.
Copyright (c) 2014 Stefan Scherer
MIT License, see LICENSE for more details.