OpenStack provider support?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenStack provider support?

Benjamin Krein
I'm wondering if anyone is working on an OpenStack provider or if anyone has had any luck in getting the AWS provider to work with the OpenStack compatibility API?  I started poking at it today and didn't get very far.



Here's the relavent parts of my Vagrantfile:

Vagrant.configure("2") do |config|
config.vm.box = "cirros"
config.vm.provider :aws do |aws|
aws.access_key_id = "#{ENV['EC2_ACCESS_KEY']}"
aws.secret_access_key = "#{ENV['EC2_SECRET_KEY']}"
aws.keypair_name = "bk-os-test1"
aws.ssh_private_key_path = "#{ENV['EC2_PRIVATE_KEY']}"
    aws.region = "nova"
aws.ssh_username = "cirros"
end
end


Here's the relavent parts of my Base Box I created:

Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.provider :aws do |aws|
    aws.ami = "ami-00000001"
  end
end

metadata.json:

{
  "provider": "aws"
}

When I attempt a 'vagrant up --provider=aws' I get the following error:

$ vu --provider=aws
Bringing machine 'default' up with 'aws' provider...
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.0
[default] Warning! The AWS provider doesn't support any of the Vagrant
high-level network configurations (`config.vm.network`). They
will be silently ignored.
[default] Launching an instance with the following settings...
[default]  -- Type: m1.small
[default]  -- AMI: ami-00000001
[default]  -- Region: nova
[default]  -- Keypair: bk-os-test1
/Users/benk/.vagrant.d/gems/gems/excon-0.20.0/lib/excon/socket.rb:42:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError)

Some of the euca2ools output:

$ euca-describe-availability-zones
AVAILABILITYZONE	nova	available

$ euca-describe-regions
REGION	nova	http://10.x.x.x:8773/services/Cloud

$ euca-describe-images
IMAGE	aki-00000002	None (cirros-0.3.0-x86_64-uec-kernel)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			kernel	 	 	instance-store
IMAGE	ari-00000003	None (cirros-0.3.0-x86_64-uec-ramdisk)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			ramdis	 	 	instance-store
IMAGE	ami-00000001	None (cirros-0.3.0-x86_64-uec)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	aki-00000002	ari-00000003	instance-store
IMAGE	ami-00000004	None (lucid-base-chef10)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000006	None (precise-server-amd64)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000007	None (CentOS 6.0)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: OpenStack provider support?

Simon McCartney
I've been meaning to take a look at that, the RackSpace/OpenStack provider should do everything you need?

--
Simon McCartney

On Tuesday, 19 March 2013 at 20:52, Benjamin Krein wrote:

I'm wondering if anyone is working on an OpenStack provider or if anyone has had any luck in getting the AWS provider to work with the OpenStack compatibility API?  I started poking at it today and didn't get very far.



Here's the relavent parts of my Vagrantfile:

Vagrant.configure("2") do |config|
config.vm.box = "cirros"
config.vm.provider :aws do |aws|
aws.access_key_id = "#{ENV['EC2_ACCESS_KEY']}"
aws.secret_access_key = "#{ENV['EC2_SECRET_KEY']}"
aws.keypair_name = "bk-os-test1"
aws.ssh_private_key_path = "#{ENV['EC2_PRIVATE_KEY']}"
    aws.region = "nova"
aws.ssh_username = "cirros"
end
end


Here's the relavent parts of my Base Box I created:

Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.provider :aws do |aws|
    aws.ami = "ami-00000001"
  end
end

metadata.json:

{
  "provider": "aws"
}

When I attempt a 'vagrant up --provider=aws' I get the following error:

$ vu --provider=aws
Bringing machine 'default' up with 'aws' provider...
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.0
[default] Warning! The AWS provider doesn't support any of the Vagrant
high-level network configurations (`config.vm.network`). They
will be silently ignored.
[default] Launching an instance with the following settings...
[default]  -- Type: m1.small
[default]  -- AMI: ami-00000001
[default]  -- Region: nova
[default]  -- Keypair: bk-os-test1
/Users/benk/.vagrant.d/gems/gems/excon-0.20.0/lib/excon/socket.rb:42:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError)

Some of the euca2ools output:

$ euca-describe-availability-zones
AVAILABILITYZONE	nova	available

$ euca-describe-regions
REGION	nova	http://10.x.x.x:8773/services/Cloud

$ euca-describe-images
IMAGE	aki-00000002	None (cirros-0.3.0-x86_64-uec-kernel)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			kernel	 	 	instance-store
IMAGE	ari-00000003	None (cirros-0.3.0-x86_64-uec-ramdisk)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			ramdis	 	 	instance-store
IMAGE	ami-00000001	None (cirros-0.3.0-x86_64-uec)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	aki-00000002	ari-00000003	instance-store
IMAGE	ami-00000004	None (lucid-base-chef10)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000006	None (precise-server-amd64)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000007	None (CentOS 6.0)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: OpenStack provider support?

Benjamin Krein
Is there a Rackspace/Openstack provider already?  I was thinking the AWS provider would be compatible, but I haven't had luck with it yet.

Ben

On Tuesday, March 19, 2013 6:49:22 PM UTC-4, Simon McCartney wrote:
I've been meaning to take a look at that, the RackSpace/OpenStack provider should do everything you need?

--
Simon McCartney

On Tuesday, 19 March 2013 at 20:52, Benjamin Krein wrote:

I'm wondering if anyone is working on an OpenStack provider or if anyone has had any luck in getting the AWS provider to work with the OpenStack compatibility API?  I started poking at it today and didn't get very far.



Here's the relavent parts of my Vagrantfile:

Vagrant.configure("2") do |config|
config.vm.box = "cirros"
config.vm.provider :aws do |aws|
aws.access_key_id = "#{ENV['EC2_ACCESS_KEY']}"
aws.secret_access_key = "#{ENV['EC2_SECRET_KEY']}"
aws.keypair_name = "bk-os-test1"
aws.ssh_private_key_path = "#{ENV['EC2_PRIVATE_KEY']}"
    aws.region = "nova"
aws.ssh_username = "cirros"
end
end


Here's the relavent parts of my Base Box I created:

Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.provider :aws do |aws|
    aws.ami = "ami-00000001"
  end
end

metadata.json:

{
  "provider": "aws"
}

When I attempt a 'vagrant up --provider=aws' I get the following error:

$ vu --provider=aws
Bringing machine 'default' up with 'aws' provider...
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.0
[default] Warning! The AWS provider doesn't support any of the Vagrant
high-level network configurations (`config.vm.network`). They
will be silently ignored.
[default] Launching an instance with the following settings...
[default]  -- Type: m1.small
[default]  -- AMI: ami-00000001
[default]  -- Region: nova
[default]  -- Keypair: bk-os-test1
/Users/benk/.vagrant.d/gems/gems/excon-0.20.0/lib/excon/socket.rb:42:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError)

Some of the euca2ools output:

$ euca-describe-availability-zones
AVAILABILITYZONE	nova	available

$ euca-describe-regions
REGION	nova	http://10.x.x.x:8773/services/Cloud

$ euca-describe-images
IMAGE	aki-00000002	None (cirros-0.3.0-x86_64-uec-kernel)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			kernel	 	 	instance-store
IMAGE	ari-00000003	None (cirros-0.3.0-x86_64-uec-ramdisk)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			ramdis	 	 	instance-store
IMAGE	ami-00000001	None (cirros-0.3.0-x86_64-uec)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	aki-00000002	ari-00000003	instance-store
IMAGE	ami-00000004	None (lucid-base-chef10)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000006	None (precise-server-amd64)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000007	None (CentOS 6.0)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="M28wmljwpF0J">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: OpenStack provider support?

Simon McCartney
https://github.com/mitchellh/vagrant-rackspace, not sure how RackSpace specific it is, but I'd love to help out on any OpenStack work required (I work for an OpenStack provider, HP Cloud Service.)


On 20 March 2013 14:01, Benjamin Krein <[hidden email]> wrote:
Is there a Rackspace/Openstack provider already?  I was thinking the AWS provider would be compatible, but I haven't had luck with it yet.

Ben


On Tuesday, March 19, 2013 6:49:22 PM UTC-4, Simon McCartney wrote:
I've been meaning to take a look at that, the RackSpace/OpenStack provider should do everything you need?

--
Simon McCartney

On Tuesday, 19 March 2013 at 20:52, Benjamin Krein wrote:

I'm wondering if anyone is working on an OpenStack provider or if anyone has had any luck in getting the AWS provider to work with the OpenStack compatibility API?  I started poking at it today and didn't get very far.



Here's the relavent parts of my Vagrantfile:

Vagrant.configure("2") do |config|
config.vm.box = "cirros"
config.vm.provider :aws do |aws|
aws.access_key_id = "#{ENV['EC2_ACCESS_KEY']}"
aws.secret_access_key = "#{ENV['EC2_SECRET_KEY']}"
aws.keypair_name = "bk-os-test1"
aws.ssh_private_key_path = "#{ENV['EC2_PRIVATE_KEY']}"
    aws.region = "nova"
aws.ssh_username = "cirros"
end
end


Here's the relavent parts of my Base Box I created:

Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.provider :aws do |aws|
    aws.ami = "ami-00000001"
  end
end

metadata.json:

{
  "provider": "aws"
}

When I attempt a 'vagrant up --provider=aws' I get the following error:

$ vu --provider=aws
Bringing machine 'default' up with 'aws' provider...
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.0
[default] Warning! The AWS provider doesn't support any of the Vagrant
high-level network configurations (`config.vm.network`). They
will be silently ignored.
[default] Launching an instance with the following settings...
[default]  -- Type: m1.small
[default]  -- AMI: ami-00000001
[default]  -- Region: nova
[default]  -- Keypair: bk-os-test1
/Users/benk/.vagrant.d/gems/gems/excon-0.20.0/lib/excon/socket.rb:42:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError)

Some of the euca2ools output:

$ euca-describe-availability-zones
AVAILABILITYZONE	nova	available

$ euca-describe-regions
REGION	nova	http://10.x.x.x:8773/services/Cloud

$ euca-describe-images
IMAGE	aki-00000002	None (cirros-0.3.0-x86_64-uec-kernel)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			kernel	 	 	instance-store
IMAGE	ari-00000003	None (cirros-0.3.0-x86_64-uec-ramdisk)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			ramdis	 	 	instance-store
IMAGE	ami-00000001	None (cirros-0.3.0-x86_64-uec)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	aki-00000002	ari-00000003	instance-store
IMAGE	ami-00000004	None (lucid-base-chef10)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000006	None (precise-server-amd64)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store
IMAGE	ami-00000007	None (CentOS 6.0)	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	available	public			machine	 	 	instance-store

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Simon McCartney
M: +44 7710 836 915

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.