vagrant-xenserver 0.0.0 → 0.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3e71a5e7cadb1956653b86df342189d60b6da468
-  data.tar.gz: 6f2128e6f3fdea3108dadc8c8f40cb4d0bd3f694
+  metadata.gz: 9d1cc23a51d274952345b4ed8f1f3c9f8e9a2a58
+  data.tar.gz: c8120a254299c1ac2fe863f25b6a1fb0606efe13
 SHA512:
-  metadata.gz: 7c7df81ce4a9603ccc52c8e43913a38a297e8b3993e80ff593f5af43b506439decb9c1a46d8ab12fb26f4f9fd0a892c4af2596abb2ee21168a18d1f99be83f91
-  data.tar.gz: a982ff961439ce2c9043fac119fb07288ca348122fec58770df9ace0f6cd4ef49d2de1e24ddac59abac02721cc50ee73314dfa973d770959134248028794b51e
+  metadata.gz: 9c37ac03de57c2361c481530cbc95e69d73918a498f513d872fd152a166fcdc8b45fa7d9c69f240f3b0e0992d7a4159260d7b51d95f27860f5595bb5ecac67e9
+  data.tar.gz: 04e395b2f77f141d45e083c0826f8ae690ca27db6fba83794568ba6d8790944c4e88e148f47c5dcc978715748c490c54445744fb3920fb2e83bf45e9423d6d1b

data/CHANGELOG.md

@@ -1,3 +1,9 @@
-# 0.1.0 (Unreleased)
+# 0.0.1 (7 July 2014)
+
+* Use the md5 of the first meg of VHD to tag the base VDI
+  This is much more unique than the name/version pair
+
+# 0.0.0 (1 July 2014)
 
 * Initial release.
+

data/README.md

@@ -1,251 +1,92 @@
-# Vagrant AWS Provider
+# Vagrant XenServer Provider
 
-<span class="badges">
-[![Gem Version](https://badge.fury.io/rb/vagrant-aws.png)][gem]
-[![Dependency Status](https://gemnasium.com/mitchellh/vagrant-aws.png)][gemnasium]
-</span>
+This is a Vagrant plugin that adds a XenServer provider, allowing Vagrant to
+control and provision machines on a XenServer host.
 
-[gem]: https://rubygems.org/gems/vagrant-aws
-[gemnasium]: https://gemnasium.com/mitchellh/vagrant-aws
+## Dependencies
+* Vagrant >= 1.5(?) (http://www.vagrantup.com/downloads.html)
 
-This is a [Vagrant](http://www.vagrantup.com) 1.2+ plugin that adds an [AWS](http://aws.amazon.com)
-provider to Vagrant, allowing Vagrant to control and provision machines in
-EC2 and VPC.
-
-**NOTE:** This plugin requires Vagrant 1.2+,
-
-## Features
-
-* Boot EC2 or VPC instances.
-* SSH into the instances.
-* Provision the instances with any built-in Vagrant provisioner.
-* Minimal synced folder support via `rsync`.
-* Define region-specifc configurations so Vagrant can manage machines
-  in multiple regions.
-
-## Usage
+## Installation
+```shell
+vagrant plugin install vagrant-xenserver
+# Make your linux box look like a Mac :) (maybe)
+sudo ln -s /bin/tar /bin/bsdtar
+```
 
-Install using standard Vagrant 1.1+ plugin installation methods. After
-installing, `vagrant up` and specify the `aws` provider. An example is
-shown below.
+## XenServer host setup
+N.B. Currently this will only work on a trunk build of XenServer:
+```shell
+# Install netcat
+yum install --enablerepo=base,extras --disablerepo=citrix -y nc
+# Setup NAT - NB, this _disable the firewall_ - be careful!
+echo 1 > /proc/sys/net/ipv4/ip_forward
+/sbin/iptables -F INPUT
 
+/sbin/iptables -t nat -A POSTROUTING -o xenbr0 -j MASQUERADE
+/sbin/iptables -A INPUT -i xenbr0 -p tcp -m tcp --dport 53 -j ACCEPT
+/sbin/iptables -A INPUT -i xenbr0 -p udp -m udp --dport 53 -j ACCEPT
+/sbin/iptables -A FORWARD -i xenbr0 -o xenapi -m state --state
+RELATED,ESTABLISHED -j ACCEPT
+/sbin/iptables -A FORWARD -i xenapi -o xenbr0 -j ACCEPT
 ```
-$ vagrant plugin install vagrant-aws
-...
-$ vagrant up --provider=aws
-...
-```
-
-Of course prior to doing this, you'll need to obtain an AWS-compatible
-box file for Vagrant.
 
-## Quick Start
+# Usage
 
-After installing the plugin (instructions above), the quickest way to get
-started is to actually use a dummy AWS box and specify all the details
-manually within a `config.vm.provider` block. So first, add the dummy
-box using any name you want:
+## Converting a VirtualBox box file
 
+* Download the box file (e.g. https://vagrantcloud.com/ubuntu/trusty64/version/1/provider/virtualbox.box)
+* Unpack it:
+```shell
+mkdir tmp
+cd tmp
+tar xvf ../virtualbox.box
 ```
-$ vagrant box add dummy https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
-...
+* Convert the disk image using qemu-img
+```shell
+qemu-img convert *.vmdk -O vpc box.vhd
 ```
-
-And then make a Vagrantfile that looks like the following, filling in
-your information where necessary.
-
+* Remove the other files
+```shell
+rm -f Vagrantfile box.ovf metadata.json 
 ```
-Vagrant.configure("2") do |config|
-  config.vm.box = "dummy"
-
-  config.vm.provider :aws do |aws, override|
-    aws.access_key_id = "YOUR KEY"
-    aws.secret_access_key = "YOUR SECRET KEY"
-    aws.keypair_name = "KEYPAIR NAME"
-
-    aws.ami = "ami-7747d01e"
-
-    override.ssh.username = "ubuntu"
-    override.ssh.private_key_path = "PATH TO YOUR PRIVATE KEY"
-  end
-end
+* Make a new metadata file
+```shell
+echo "{\"provider\": \"xenserver\"}" > metadata.json
 ```
-
-And then run `vagrant up --provider=aws`.
-
-This will start an Ubuntu 12.04 instance in the us-east-1 region within
-your account. And assuming your SSH information was filled in properly
-within your Vagrantfile, SSH and provisioning will work as well.
-
-Note that normally a lot of this boilerplate is encoded within the box
-file, but the box file used for the quick start, the "dummy" box, has
-no preconfigured defaults.
-
-If you have issues with SSH connecting, make sure that the instances
-are being launched with a security group that allows SSH access.
-
-## Box Format
-
-Every provider in Vagrant must introduce a custom box format. This
-provider introduces `aws` boxes. You can view an example box in
-the [example_box/ directory](https://github.com/mitchellh/vagrant-aws/tree/master/example_box).
-That directory also contains instructions on how to build a box.
-
-The box format is basically just the required `metadata.json` file
-along with a `Vagrantfile` that does default settings for the
-provider-specific configuration for this provider.
-
-## Configuration
-
-This provider exposes quite a few provider-specific configuration options:
-
-* `access_key_id` - The access key for accessing AWS
-* `ami` - The AMI id to boot, such as "ami-12345678"
-* `availability_zone` - The availability zone within the region to launch
-  the instance. If nil, it will use the default set by Amazon.
-* `instance_ready_timeout` - The number of seconds to wait for the instance
-  to become "ready" in AWS. Defaults to 120 seconds.
-* `instance_type` - The type of instance, such as "m1.small". The default
-  value of this if not specified is "m1.small".
-* `keypair_name` - The name of the keypair to use to bootstrap AMIs
-   which support it.
-* `private_ip_address` - The private IP address to assign to an instance
-  within a [VPC](http://aws.amazon.com/vpc/)
-* `region` - The region to start the instance in, such as "us-east-1"
-* `secret_access_key` - The secret access key for accessing AWS
-* `security_groups` - An array of security groups for the instance. If this
-  instance will be launched in VPC, this must be a list of security group
-  IDs.
-* `iam_instance_profile_arn` - The Amazon resource name (ARN) of the IAM Instance
-    Profile to associate with the instance
-* `iam_instance_profile_name` - The name of the IAM Instance Profile to associate
-  with the instance
-* `subnet_id` - The subnet to boot the instance into, for VPC.
-* `associate_public_ip` - If true, will associate a public IP address to an instance in a VPC.
-* `tags` - A hash of tags to set on the machine.
-* `use_iam_profile` - If true, will use [IAM profiles](http://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
-  for credentials.
-
-These can be set like typical provider-specific configuration:
-
-```ruby
-Vagrant.configure("2") do |config|
-  # ... other stuff
-
-  config.vm.provider :aws do |aws|
-    aws.access_key_id = "foo"
-    aws.secret_access_key = "bar"
-  end
-end
+* Create the box:
+```shell
+tar cf ../xenserver.box .
 ```
-
-In addition to the above top-level configs, you can use the `region_config`
-method to specify region-specific overrides within your Vagrantfile. Note
-that the top-level `region` config must always be specified to choose which
-region you want to actually use, however. This looks like this:
-
-```ruby
-Vagrant.configure("2") do |config|
-  # ... other stuff
-
-  config.vm.provider :aws do |aws|
-    aws.access_key_id = "foo"
-    aws.secret_access_key = "bar"
-    aws.region = "us-east-1"
-
-    # Simple region config
-    aws.region_config "us-east-1", :ami => "ami-12345678"
-
-    # More comprehensive region config
-    aws.region_config "us-west-2" do |region|
-      region.ami = "ami-87654321"
-      region.keypair_name = "company-west"
-    end
-  end
-end
+* Add the box:
+```shell
+vagrant box add ubuntu xenserver.box
 ```
 
-The region-specific configurations will override the top-level
-configurations when that region is used. They otherwise inherit
-the top-level configurations, as you would probably expect.
-
-## Networks
-
-Networking features in the form of `config.vm.network` are not
-supported with `vagrant-aws`, currently. If any of these are
-specified, Vagrant will emit a warning, but will otherwise boot
-the AWS machine.
-
-## Synced Folders
-
-There is minimal support for synced folders. Upon `vagrant up`,
-`vagrant reload`, and `vagrant provision`, the AWS provider will use
-`rsync` (if available) to uni-directionally sync the folder to
-the remote machine over SSH.
-
-This is good enough for all built-in Vagrant provisioners (shell,
-chef, and puppet) to work!
-
-## Other Examples
-
-### Tags
-
-To use tags, simply define a hash of key/value for the tags you want to associate to your instance, like:
+## Create a Vagrantfile
 
 ```ruby
-Vagrant.configure("2") do |config|
-  # ... other stuff
-
-  config.vm.provider "aws" do |aws|
-    aws.tags = {
-	  'Name' => 'Some Name',
-	  'Some Key' => 'Some Value'
-    }
-  end
-end
-```
-
-### User data
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
 
-You can specify user data for the instance being booted.
+# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
+VAGRANTFILE_API_VERSION = "2"
 
-```ruby
-Vagrant.configure("2") do |config|
-  # ... other stuff
-
-  config.vm.provider "aws" do |aws|
-    # Option 1: a single string
-    aws.user_data = "#!/bin/bash\necho 'got user data' > /tmp/user_data.log\necho"
+Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
+  config.vm.box = "ubuntu"
 
-    # Option 2: use a file
-    aws.user_data = File.read("user_data.txt")
+  config.vm.provider :xenserver do |xs|
+  xs.xs_host = "st29.uk.xensource.com"
+  xs.xs_username = "root"
+  xs.xs_password = "xenroot"
+  xs.pv = true
+  xs.memory = 2048
   end
 end
-```
 
-## Development
-
-To work on the `vagrant-aws` plugin, clone this repository out, and use
-[Bundler](http://gembundler.com) to get the dependencies:
-
-```
-$ bundle
 ```
 
-Once you have the dependencies, verify the unit tests pass with `rake`:
+and then you can do
 
-```
-$ bundle exec rake
-```
-
-If those pass, you're ready to start developing the plugin. You can test
-the plugin without installing it into your Vagrant environment by just
-creating a `Vagrantfile` in the top level of this directory (it is gitignored)
-and add the following line to your `Vagrantfile` 
-```ruby
-Vagrant.require_plugin "vagrant-aws"
-```
-Use bundler to execute Vagrant:
-```
-$ bundle exec vagrant up --provider=aws
+```shell
+vagrant up --provider=xenserver
 ```

data/lib/vagrant-xenserver/action/upload_vhd.rb

@@ -24,8 +24,11 @@ module VagrantPlugins
 
           # Find out if it has already been uploaded
           vdis = env[:xc].call("VDI.get_all_records", env[:session])['Value']
-          
-          vdi_tag = "vagrant:" + env[:machine].box.name.to_s + "/" + env[:machine].box.version.to_s
+          md5=`dd if=#{box_vhd_file} bs=1M count=1 | md5sum | cut '-d ' -f1`.strip
+
+          @logger.info("md5=#{md5}")
+
+          vdi_tag = "vagrant:" + env[:machine].box.name.to_s + "/" + md5
 
           vdi_ref_rec = vdis.find { |reference,record|
                 @logger.info(record['tags'].to_s)

data/lib/vagrant-xenserver/version.rb

@@ -1,6 +1,6 @@
 module VagrantPlugins
   module XenServer
-    VERSION = "0.0.0"
+    VERSION = "0.0.1"
   end
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-xenserver
 version: !ruby/object:Gem::Version
-  version: 0.0.0
+  version: 0.0.1
 platform: ruby
 authors:
 - Jon Ludlam
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-02 00:00:00.000000000 Z
+date: 2014-07-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake