vagrant-tiktalik 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1e2eae2923158eb685917eacadbb737ec8ee747c
-  data.tar.gz: f4970f0c612f94007f6100eb6d0f7bd874e864d9
+  metadata.gz: f456716376d5e63c7b37333c0ccc1f639bdd53cf
+  data.tar.gz: 407f7c942914a6f10a74f873381bdf68e924b67b
 SHA512:
-  metadata.gz: 0231889c46e50da2c64f7b6c7db035f338313ae0dce1fc24d427e238e659d9bb98d3602f9e2f36ca23d5d99a78fb079f1675fd47316778b2061bc69d8243b025
-  data.tar.gz: c444050382f5ffe76320fe08993e1dd17fe634059a8f0615d9302f231be14505a24ba5e39745267a657b34864e380a06c44e3a46e72f42a79717eaabf325b1df
+  metadata.gz: 1466932aa634bfc17b8f460dd3385988c70b44fe280a4d7b9762471690bfec28425453d0e875ea56964a724cdaa413953869528ce32f64cd8afca41da3bc0db1
+  data.tar.gz: f7219b9d4a3797d94a9f050948bdf3f55e52c9b2bbe21044e36b2e7d9cbba337ad2f8e734673b1dd0e14a2edc281d6ee55ccfd5bdd43987728012176c9db375c

data/README.md

@@ -1,84 +1,127 @@
-# This is Vagrant Tiktalik.com Provider WORK IN PROGRESS
+# Vagrant Tiktalik.com Provider
 
-Our plugin is based on excellent Vagrant AWS Provider plugin.
-We'll come up with our own README file but for now please read the original one provided below.
-Don't forget you that our plugin is called vagrant-tiktalik so please adapt commands accordingly.
-
-``
-$ vagrant plugin install vagrant-tiktalik
-...
-$ vagrant up --provider=tiktalik
-``
-
-# Vagrant AWS Provider
-
-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.
+This is a [Vagrant](http://www.vagrantup.com) 1.2+ plugin that adds an [Tiktalik.com](https://tiktalik.com)
+provider to Vagrant, allowing Vagrant to control and provision machines in Tiktalik cloud.
 
 **NOTE:** This plugin requires Vagrant 1.2+,
 
 ## Features
 
-* Boot EC2 or VPC instances.
+* Boot Tiktalik instances.
 * SSH into the instances.
-* Provision the instances with any built-in Vagrant provisioner.
+* Provision the instances with any built-in Vagrant provisioner, ie. ansible
 * Minimal synced folder support via `rsync`.
-* Define region-specifc configurations so Vagrant can manage machines
-  in multiple regions.
 
 ## Usage
 
-Install using standard Vagrant 1.1+ plugin installation methods. After
-installing, `vagrant up` and specify the `aws` provider. An example is
-shown below.
+Install using standard Vagrant 1.1+ plugin installation methods.
 
 ```
-$ vagrant plugin install vagrant-aws
-...
-$ vagrant up --provider=aws
-...
+$ vagrant plugin install vagrant-tiktalik
+
+Installing the 'vagrant-tiktalik' plugin. This can take a few minutes...
+Installed the plugin 'vagrant-tiktalik (0.0.1)'!
 ```
 
-Of course prior to doing this, you'll need to obtain an AWS-compatible
+After installing, run `vagrant up` and specify the `tiktalik` provider.
+
+```
+$ vagrant up --provider=tiktalik
+
+Bringing machine 'default' up with 'tiktalik' provider...
+[default] Launching an instance with the following settings...
+[default]  -- Image: 4a2b3e72-47f1-4e88-b482-1834478ade28
+[default]  -- Hostname: vagrant-default
+[default]  -- Size: 0.5
+[default]  -- SSH key: d5c6b671-6cba-41fe-9020-5d5e1dda85f9
+[default]  -- Networks: ["212c7fd1-6018-41ff-9a01-a37956517237"]
+[default] Waiting for instance to become "ready"...
+[default] Waiting for SSH to become available...
+[default] Machine is booted and ready for use!
+[default] Rsyncing folder: /root/f/ => /vagrant
+```
+
+Of course prior to doing this, you'll need to obtain an Tiktalik-compatible
 box file for Vagrant.
 
+## SSL issues
+
+If you get the following error:
+
+```
+connect': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (Faraday::Error::ConnectionFailed)
+```
+
+It means that you are missing root certificates, at least ruby is missing them.
+
+This problem has been described on Faraday's (a vagrant-tiktalik and tiktalik-ruby dependency) wiki:
+
+[https://github.com/lostisland/faraday/wiki/Setting-up-SSL-certificates](https://github.com/lostisland/faraday/wiki/Setting-up-SSL-certificates)
+
+The quick fix is to:
+
+ * set SSL_CERT_FILE environment variable and point it to Certificate Authority (CA) file. Please note that CA file might not be installed on your system and the actuall file path might differ!
+ 
+   ```
+   $ SSL_CERT_FILE=/opt/vagrant/embedded/cacert.pem vagrant status
+   ```
+ * set CA file path as a provider configuration variable in Vagrantfile.  Please see sample configuration file below.
+
+
 ## Quick Start
 
 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
+started is to actually use a dummy Tiktalik box and specify all the details
 manually within a `config.vm.provider` block. So first, add the dummy
 box using any name you want:
 
 ```
-$ vagrant box add dummy https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
-...
+$ vagrant box add dummy https://github.com/tiktalik-cloud/vagrant-tiktalik/raw/master/box/tiktalik.box
+
+Downloading or copying the box...
+Extracting box...e: 0/s, Estimated time remaining: --:--:--)
+Successfully added box 'dummy' with provider 'tiktalik'!
 ```
 
 And then make a Vagrantfile that looks like the following, filling in
 your information where necessary.
 
-```
-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"
+```ruby
+Vagrant.configure('2') do |config|
+  config.vm.provider :tiktalik do |provider, override|
+    # path to private ssh key, public one has to me uploaded to
+    # tiktalik.com and it's UUID provided below as `provider.ssh_key`
+    # please note that DSA key will work just fine
+    override.ssh.private_key_path = '~/.ssh/id_rsa'
+
+    override.vm.box = 'tiktalik'
+
+    # hostname for your instance, ie vagrant-host.youraccount.p2.tiktalik.com
+    # override.vm.hostname = 'vagrant-host'
+
+    # api credentials, get them from https://tiktalik.com/panel/#apikeys
+    provider.api_key = 'api key'
+    provider.api_secret = 'api secret'
+
+    # system image UUID, this one is for Ubuntu 12.04.3 LTS 64-bit
+    # get more ids from https://tiktalik.com/panel/#templates
+    provider.image = '4a2b3e72-47f1-4e88-b482-1834478ade28'
+    
+    # in case of SSL related problems (ie. ruby 1.9 missing CA file)
+    # uncomment following line. don't forget to provide valid CA file path.
+    # on Ubuntu, CA file comes with Vagrant deb package
+    # provider.ca_file = '/opt/vagrant/embedded/cacert.pem'
+
+    # your SSH key UUID, get one from https://tiktalik.com/panel/#sshkeys
+    provider.ssh_key = 'here goes ssh key uuid'
   end
 end
 ```
 
-And then run `vagrant up --provider=aws`.
+And then run `vagrant up --provider=tiktalik`.
 
-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
+This will start an Ubuntu 12.04 instance 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
@@ -88,143 +131,41 @@ 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.
-* `subnet_id` - The subnet to boot the instance into, for 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
-```
-
-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
-```
-
-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.
+* `image` - System image UUID, full list available at:
+  https://tiktalik.com/panel/#templates
+* `size` - Instance size, ie. 0.25, 0.5, 1, ...
+  Check out our pricing list for other sizes:
+  https://tiktalik.com/pricing#unit/2
+* `ssh_key` - SSH key UUID.  Key has to be uploaded beforehand.
+  Admin panel URL is https://tiktalik.com/panel/#sshkeys
+* `api_key` - API key and ...
+* `api_secret` - ... secret are required API creditentials.
+  Go to admin panel to get them: https://tiktalik.com/panel/#apikeys
 
 ## Networks
 
 Networking features in the form of `config.vm.network` are not
-supported with `vagrant-aws`, currently. If any of these are
+supported with `vagrant-tiktalik`, currently. If any of these are
 specified, Vagrant will emit a warning, but will otherwise boot
-the AWS machine.
+the Tiktalik instance.
 
 ## Synced Folders
 
 There is minimal support for synced folders. Upon `vagrant up`,
-`vagrant reload`, and `vagrant provision`, the AWS provider will use
+`vagrant reload`, and `vagrant provision`, the Tiktalik 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:
-
-```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
-
-You can specify user data for the instance being booted.
-
-```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"
-
-    # Option 2: use a file
-    aws.user_data = File.read("user_data.txt")
-  end
-end
-```
-
 ## Development
 
-To work on the `vagrant-aws` plugin, clone this repository out, and use
+To work on the `vagrant-tiktalik` plugin, clone this repository out, and use
 [Bundler](http://gembundler.com) to get the dependencies:
 
 ```
@@ -242,9 +183,13 @@ 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"
+Vagrant.require_plugin "vagrant-tiktalik"
 ```
 Use bundler to execute Vagrant:
 ```
-$ bundle exec vagrant up --provider=aws
+$ bundle exec vagrant up --provider=tiktalik
 ```
+
+## Thanks
+
+Our plugin is based on excellent Vagrant AWS Provider plugin.

data/box/metadata.json

@@ -1,3 +1,3 @@
 {
-    "provider": "tiktalik.com"
+    "provider": "tiktalik"
 }

data/lib/vagrant-tiktalik/action/power_off.rb

@@ -18,6 +18,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           i = Tiktalik::Computing::Instance
           instance = i.find env[:machine].id

data/lib/vagrant-tiktalik/action/power_on.rb

@@ -18,6 +18,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           i = Tiktalik::Computing::Instance
           instance = i.find env[:machine].id

data/lib/vagrant-tiktalik/action/read_ssh_info.rb

@@ -24,6 +24,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           i = Tiktalik::Computing::Instance
           instance = i.find machine.id

data/lib/vagrant-tiktalik/action/read_state.rb

@@ -20,6 +20,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           env[:machine_state_id] = :not_created
 

data/lib/vagrant-tiktalik/action/run_instance.rb

@@ -43,6 +43,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           begin
             networks = []

data/lib/vagrant-tiktalik/action/terminate_instance.rb

@@ -21,6 +21,7 @@ module VagrantPlugins
           t = Tiktalik
           t.api_key = @config.api_key
           t.api_secret_key = @config.api_secret
+          t.ca_file = @config.ca_file
 
           i = Tiktalik::Computing::Instance
           instance = i.find env[:machine].id

data/lib/vagrant-tiktalik/config.rb

@@ -8,6 +8,7 @@ module VagrantPlugins
       attr_accessor :size
       attr_accessor :ssh_key
       attr_accessor :api_secret
+      attr_accessor :ca_file
       #attr_accessor :network
 
       def initialize
@@ -16,6 +17,7 @@ module VagrantPlugins
         @size       = UNSET_VALUE
         @ssh_key    = UNSET_VALUE
         @api_secret = UNSET_VALUE
+        @ca_file    = UNSET_VALUE
         #@network    = UNSET_VALUE
       end
 
@@ -25,6 +27,7 @@ module VagrantPlugins
         @size       = 0.5 if @size == UNSET_VALUE
         @ssh_key    = nil if @ssh_key == UNSET_VALUE
         @api_secret = ENV['TIKTALIK_API_SECRET'] if @api_secret == UNSET_VALUE
+        @ca_file    = nil if @ca_file == UNSET_VALUE
         #@network    = nil if @network == UNSET_VALUE
       end
 

data/lib/vagrant-tiktalik/plugin.rb

@@ -19,12 +19,12 @@ module VagrantPlugins
       machines in Tiktalik.com.
       DESC
 
-      config(:"tiktalik.com", :provider) do
+      config(:tiktalik, :provider) do
         require_relative "config"
         Config
       end
 
-      provider(:"tiktalik.com", parallel: true) do
+      provider(:tiktalik, parallel: true) do
         # Setup logging and i18n
         setup_logging
         setup_i18n

data/lib/vagrant-tiktalik/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module TiktalikVagrant
-    VERSION = "0.0.1"
+    VERSION = "0.0.2"
   end
 end

data/vagrant-tiktalik.gemspec

@@ -16,7 +16,7 @@ Gem::Specification.new do |s|
   s.rubyforge_project         = "vagrant-tiktalik"
 
   # s.add_runtime_dependency "fog", "~> 1.10.0"
-  s.add_runtime_dependency "tiktalik", "~> 1.0.3"
+  s.add_runtime_dependency "tiktalik", "~> 1.0.4"
 
   s.add_development_dependency "rake"
   s.add_development_dependency "rspec-core", "~> 2.12.2"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-tiktalik
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors:
 - Aleksander Piotrowski
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-03 00:00:00.000000000 Z
+date: 2013-10-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: tiktalik
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.0.3
+        version: 1.0.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.0.3
+        version: 1.0.4
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement