Thanks for a great tutorial. I have one slight issue. I need to access my virtuals remotely so I need to allocate/associate floating ips to them. How do I do that with your setup? Can I do it without disturbing the 6 virtual machines I have currently running?

Thanks,

Thomas

It’s a bug – you’re using the very latest trunk PPA to install your packages, and it looks like there’s a problem with that package. You can either use one of the “released” packages, or you can wait a bit until the bug gets resolved. I’d recommend at least reporting this bug at https://bugs.launchpad.net/glance/+filebug

thanks for a nice & clear tutorial; however, when installing glance (apt-get install glance) I have some issues, not sure if it’s my setup of a bug; I get
———————————————————————————————
Setting up glance (2012.1~e2~20111110.1090-0ubuntu0ppa1~maverick1) …
Traceback (most recent call last):
File “/usr/bin/glance-manage”, line 44, in
from glance import version as glance_version
ImportError: No module named glance
dpkg: error processing glance (–configure):
subprocess installed post-installation script returned error exit status 1
————————————————————————————————-
(I’m on a ubuntu 10.10);

Thanks!
/nico

Any chance, you are planning on doing on addendum to this post explaining keystone and dashboard installation. Due to Keystone issues, that has been a real challenge with to know which version and how to get all that properly installed.

I was unable to get your config to work on 10.10 following your steps exactly. In the end I had to use this doc: _http://cssoss.files.wordpress.com/2011/08/openstackbookv1-0_csscorp.pdf when it came to the creation of the user, project and credentials. When I followed your steps I did not receive any errors until trying to publish the tarball. I would then run a simple euca command and get:

nova@licof038:~$ euca-describe-images
Warning: failed to parse error message from AWS: :1:0: syntax error
EC2ResponseError: 403 Forbidden
403 Forbidden

Access was denied to this resource.

I knew it was a credentials issue which is why I tried another document which had a variant of the procedure. It think it was a combination of the different syntax as well as restarting all the services after the sourcing of novarc which this document did not mention. Can you think of any other reason why following the steps herein ended in the credentials issue for me? These steps were far easier and straightforward so I would prefer to use it in the future.

Thanks.

Darren

node 1:
nova.conf
http://pastebin.com/YkdRHN55
network card:
root@openstack2:/home/cloud# ip addr
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet 169.254.169.254/32 scope link lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1d:60:e8:75:74 brd ff:ff:ff:ff:ff:ff
inet 10.2.76.3/24 brd 10.2.76.255 scope global eth0
inet6 fe80::21d:60ff:fee8:7574/64 scope link
valid_lft forever preferred_lft forever
3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1d:60:e8:76:6e brd ff:ff:ff:ff:ff:ff
inet 10.2.77.3/24 brd 10.2.77.255 scope global eth1
inet6 fe80::21d:60ff:fee8:766e/64 scope link
valid_lft forever preferred_lft forever
4: eth2: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1d:60:e8:72:99 brd ff:ff:ff:ff:ff:ff
5: eth3: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1d:60:e8:74:29 brd ff:ff:ff:ff:ff:ff
6: virbr0: mtu 1500 qdisc noqueue state UNKNOWN
link/ether 8a:50:e4:60:e4:49 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

node 2:
nova.conf
http://pastebin.com/Has60MVg
network card
cloud4@openstack4:~$ ip addr
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet 169.254.169.254/32 scope link lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:14:5e:7b:aa:8e brd ff:ff:ff:ff:ff:ff
3: eth1: mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:14:5e:7b:aa:8f brd ff:ff:ff:ff:ff:ff
inet6 fe80::214:5eff:fe7b:aa8f/64 scope link tentative dadfailed
valid_lft forever preferred_lft forever
4: eth2: mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:11:0a:61:0e:a0 brd ff:ff:ff:ff:ff:ff
inet 10.2.76.4/24 brd 10.2.76.255 scope global eth2
inet6 fe80::211:aff:fe61:ea0/64 scope link
valid_lft forever preferred_lft forever
5: eth3: mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:11:0a:61:0e:a1 brd ff:ff:ff:ff:ff:ff
inet 10.2.77.4/24 brd 10.2.77.255 scope global eth3
inet6 fe80::211:aff:fe61:ea1/64 scope link
valid_lft forever preferred_lft forever
6: virbr0: mtu 1500 qdisc noqueue state UNKNOWN
link/ether 0e:41:57:f3:05:73 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

Thanks,
Phucvdb

The file:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 172.17.0.133
netmask 255.255.255.0
gateway 172.17.0.1


By default (and this example), the outside world doesn’t have access to ping these VMs directly. For that you need to define and set up floating IP addresses, which I skipped in this walk through. The virtualization host has access to that 10.0.0.0/8 network, so you can SSH into your hosts from there once you’ve given appropriate permissions to access port 22 (it’s at the very end of the writeup, in not very documented steps)

First can you put your /etc/network/interfaces here.
And then how can vms access to the internal ? Do you use iptables for nat?