Instead of every team member working on their own local server with own configuration, you can configure a portable dev workstation which is identical to your QA/Production environment.Any one at any time can spin their own dev workstation without making any configuration/application changes in their actual machine.
You can find list of available Vagrant boxes here[1]. These are available in various flavors such as VirtualBox, VMware, AWS etc...
I'm going to try ubuntu/trusty32 on VirtualBox where I'm going to configure apache server to host a simple webapp. Before that we need to install Vagrant & VirtualBox on the host machine.
sudo apt-get install vagrant
VirtualBox : https://www.virtualbox.org/wiki/Linux_Downloads
1. Add required Vagrant box to the host machine. This will be an one-time download after this you can spin any number of vagrant virtual machines using this box.
vagrant box add ubuntu/trusty32udara@udara-home:~/workspace/vagrant$ vagrant box add ubuntu/trusty32
==> box: Loading metadata for box 'ubuntu/trusty32'
box: URL: https://vagrantcloud.com/ubuntu/trusty32
==> box: Adding box 'ubuntu/trusty32' (v14.04) for provider: virtualbox
box: Downloading: https://vagrantcloud.com/ubuntu/boxes/trusty32/versions/14.04/providers/virtualbox.box
==> box: Successfully added box 'ubuntu/trusty32' (v14.04) for 'virtualbox'!
2. Initialize current directory as a Vagrant environment
vagrant init ubuntu/trusty32udara@udara-home:~/workspace/vagrant$ vagrant init ubuntu/trusty32
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
init command will create the Vagrantfile config with the following properties within the current working directory.
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "ubuntu/trusty32"
3. Spin up trusty32 box.
vagrant upudara@udara-home:~/workspace/vagrant$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Setting the name of the VM: vagrant_default_1418340978158_41043
.....
.....
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /home/udara/workspace/vagrant
This command will start your VM using the configuration provided within the
Vagrantfile(here we are using default) You can see the running Vagrant box if you open the VirualBox application.
4. Access shell of our vagrant machine.
vagrant sshudara@udara-home:~/workspace/vagrant$ vagrant ssh
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-43-generic i686)
* Documentation: https://help.ubuntu.com/
System information as of Thu Dec 11 23:36:38 UTC 2014
System load: 0.74 Processes: 88
Usage of /: 2.6% of 39.34GB Users logged in: 0
Memory usage: 11% IP address for eth0: 10.0.2.15
Swap usage: 0%
Graph this data and manage this system at:
https://landscape.canonical.com/
Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud
0 packages can be updated.
0 updates are security updates.
vagrant@vagrant-ubuntu-trusty-32:~$
This command will SSH into the running Vagrant machine.
5. Assign IP Adress to our guest machine.
Go back to your host machine by using command exit.
Update existing Vagrantfile with the following content. I'm using Guest IP Address as 33.33.3.3 here.
config.vm.network "private_network", ip: "33.33.3.3"In order to reflect this change to our Vagarnt box we have to use reload command,
vagrant reloadudara@udara-home:~/workspace/vagrant$ vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
==> default: Booting VM...
.....
.....
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
This will restart the existing box and load the new configuration.
6. Let's install Apache web server on our Vagrant box. SSH again using the vagrant ssh command as in step 4. Then run following command to install apache2.
sudo apt-get install apache2This command will install and start the apache server with default configs. Now if you browse 33.33.3.3 from your host machine you will get the defualt "It Works" page,
7. Sync directories between the host & Guest OSs.
a) Create sample file sync.txt within your host's vagrant workspace.
udara@udara-home:~/workspace/vagrant$ ls
sync.txt Vagrantfile
b) SSH in to the guest machine using vagrant ssh.
c) Change directory in to /vagrant using cd /vagrant/ . If you list files within this directory you can find the sync.txt created on your host machine inside the guest as well.
vagrant@vagrant-ubuntu-trusty-32:/vagrant$ ls
Vagrantfile sync.txt
Vagrant keep the folders in sync so you can use the host machine to update your project and keep sync without any hassle. By default, Vagrant shares your project directory but you can add any additional directories using.
config.vm.synced_folder "<host_directory_path>", "<guest_directory_path>"
8. Share and collaborate environments, This allows you to share Vagrant environment to anyone by providing a unique URL which routes to your vagrant box.
a) Create account at hashicorp.
b) Use vagrant command within your teminal to get access.
vagrant loginudara@udara-home:~/workspace/vagrant$ vagrant login
In a moment we'll ask for your username and password to Vagrant Cloud.
After authenticating, we will store an access token locally. Your
login details will be transmitted over a secure connection, and are
never stored on disk locally.
If you don't have a Vagrant Cloud account, sign up at vagrantcloud.com
Username or Email: udarar@wso2.com
Password (will be hidden):
You're now logged in!
c) Share using vagrant share command.
vagrant shareudara@udara-home:~/workspace/vagrant$ vagrant share
==> default: Detecting network information for machine...
default: Local machine address: 33.33.3.3
default: Local HTTP port: 80
default: Local HTTPS port: disabled
==> default: Checking authentication and authorization...
==> default: Creating Vagrant Share session...
default: Share will be at: entertaining-camel-5130
==> default: Your Vagrant Share is running! Name: entertaining-camel-5130
==> default: URL: http://entertaining-camel-5130.vagrantshare.com
By using the provided URL we can browse our apache server from anywhere now :)
You can terminate this session by pressing ctrl+c.
9. Remove environment
vagrant destroy
udara@udara-home:~/workspace/vagrant$ vagrant destroy
default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Destroying VM and associated drives...
[1] https://vagrantcloud.com/boxes/search
No comments:
Post a Comment