bilelmsekni/openstack-folsom-install-guide

A full installation guide for OpenStack Folsom with Quantum

OpenStack-Folsom-Install-guide

You want to install OpenStack Folsom with Quantum and you don't know how ? This is what you are looking for !

It's easy, simple and tested. Can't wait? Go check it by yourself:

Note: Folsom + Quantum on GRE-Tunneling : is available on stable/GRE branch:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst

Note: Folsom + Quantum on VLAN with 3 NICs is available on master branch:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

Note: Folsom + Quantum on GRE with 2 NICs is available through GRE/2NICs branch:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

Note: Folsom + Quantum on VLAN with 2 NICs is available through VLAN/2NICs branch:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

Note: If you want to try the above mentioned on a Virtual Environment follow :

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/Sand-box-your-VMs.rst

openstack-folsom-install-guide's Issues

libvirt-sock no file or directory

Im getting the following error libvirt-sock no file or directory in the nova-compute.log on the compute node, instances do not launch they go directly into error state. Where do i look to troubleshoot this. i have looked around but there is no clues to what is happening, nova-compute is running, and so is libvirt-bin. all configs are as the guide.

Also is it normal not to have direct internet access thru interfaces that have the bridge enabled

update needed - Keystone_Scripts/With Quantum/keystone_endpoints_basic.sh

Similarly to keystone_basic.sh, keystone seems not to accept service-id, instead it expects service_id. I've amended your script and copied it below:

Keystone_Scripts/With Quantum/keystone_endpoints_basic.sh

#!/bin/sh
#
# Keystone basic Endpoints

# Mainly inspired by https://github.com/openstack/keystone/blob/master/tools/sample_data.sh

# Modified by Bilel Msekni / Institut Telecom
#
# Support: [email protected]
# License: Apache Software License (ASL) 2.0
#

# Host address
HOST_IP=localhost
EXT_HOST_IP=localhost

# MySQL definitions
MYSQL_USER=keystoneUser
MYSQL_DATABASE=keystone
MYSQL_HOST=$HOST_IP
MYSQL_PASSWORD=keystonePass

# Keystone definitions
KEYSTONE_REGION=RegionOne
export SERVICE_TOKEN=ADMIN
export SERVICE_ENDPOINT="http://${HOST_IP}:35357/v2.0"

while getopts "u:D:p:m:K:R:E:T:vh" opt; do
  case $opt in
    u)
      MYSQL_USER=$OPTARG
      ;;
    D)
      MYSQL_DATABASE=$OPTARG
      ;;
    p)
      MYSQL_PASSWORD=$OPTARG
      ;;
    m)
      MYSQL_HOST=$OPTARG
      ;;
    K)
      MASTER=$OPTARG
      ;;
    R)
      KEYSTONE_REGION=$OPTARG
      ;;
    E)
      export SERVICE_ENDPOINT=$OPTARG
      ;;
    T)
      export SERVICE_TOKEN=$OPTARG
      ;;
    v)
      set -x
      ;;
    h)
      cat <<EOF
Usage: $0 [-m mysql_hostname] [-u mysql_username] [-D mysql_database] [-p mysql_password]
       [-K keystone_master ] [ -R keystone_region ] [ -E keystone_endpoint_url ] 
       [ -T keystone_token ]

Add -v for verbose mode, -h to display this message.
EOF
      exit 0
      ;;
    \?)
      echo "Unknown option -$OPTARG" >&2
      exit 1
      ;;
    :)
      echo "Option -$OPTARG requires an argument" >&2
      exit 1
      ;;
  esac
done  

if [ -z "$KEYSTONE_REGION" ]; then
  echo "Keystone region not set. Please set with -R option or set KEYSTONE_REGION variable." >&2
  missing_args="true"
fi

if [ -z "$SERVICE_TOKEN" ]; then
  echo "Keystone service token not set. Please set with -T option or set SERVICE_TOKEN variable." >&2
  missing_args="true"
fi

if [ -z "$SERVICE_ENDPOINT" ]; then
  echo "Keystone service endpoint not set. Please set with -E option or set SERVICE_ENDPOINT variable." >&2
  missing_args="true"
fi

if [ -z "$MYSQL_PASSWORD" ]; then
  echo "MySQL password not set. Please set with -p option or set MYSQL_PASSWORD variable." >&2
  missing_args="true"
fi

if [ -n "$missing_args" ]; then
  exit 1
fi

keystone service-create --name nova --type compute --description 'OpenStack Compute Service'
keystone service-create --name cinder --type volume --description 'OpenStack Volume Service'
keystone service-create --name glance --type image --description 'OpenStack Image Service'
keystone service-create --name keystone --type identity --description 'OpenStack Identity'
keystone service-create --name ec2 --type ec2 --description 'OpenStack EC2 service'
keystone service-create --name quantum --type network --description 'OpenStack Networking service'

create_endpoint () {
  case $1 in
    compute)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':8774/v2/$(tenant_id)s' --adminurl 'http://'"$HOST_IP"':8774/v2/$(tenant_id)s' --internalurl 'http://'"$HOST_IP"':8774/v2/$(tenant_id)s'
    ;;
    volume)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':8776/v1/$(tenant_id)s' --adminurl 'http://'"$HOST_IP"':8776/v1/$(tenant_id)s' --internalurl 'http://'"$HOST_IP"':8776/v1/$(tenant_id)s'
    ;;
    image)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':9292/v2' --adminurl 'http://'"$HOST_IP"':9292/v2' --internalurl 'http://'"$HOST_IP"':9292/v2'
    ;;
    identity)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':5000/v2.0' --adminurl 'http://'"$HOST_IP"':35357/v2.0' --internalurl 'http://'"$HOST_IP"':5000/v2.0'
    ;;
    ec2)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':8773/services/Cloud' --adminurl 'http://'"$HOST_IP"':8773/services/Admin' --internalurl 'http://'"$HOST_IP"':8773/services/Cloud'
    ;;
    network)
    keystone endpoint-create --region $KEYSTONE_REGION --service_id $2 --publicurl 'http://'"$EXT_HOST_IP"':9696/' --adminurl 'http://'"$HOST_IP"':9696/' --internalurl 'http://'"$HOST_IP"':9696/'
    ;;
  esac
}

for i in compute volume image object-store identity ec2 network; do
  id=`mysql -h "$MYSQL_HOST" -u "$MYSQL_USER" -p"$MYSQL_PASSWORD" "$MYSQL_DATABASE" -ss -e "SELECT id FROM service WHERE type='"$i"';"` || exit 1
  create_endpoint $i $id
done

Can't start Glance API

When I try to start the API, it quits with the following:

2012-11-04 12:56:19 30466 DEBUG glance.common.config [-] Loading glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app /opt/stack/glance/glance/common/config.py:185
ERROR: Unable to load glance-api-keystone from configuration file /etc/glance/glance-api-paste.ini.
Got: ImportError("<module 'glance.common.wsgi' from '/opt/stack/glance/glance/common/wsgi.pyc'> has no 'app_factory' attribute",)

Any advice?

Cannot ping/ssh to VM

Hi all, I am trying to set up a multi-node configuration following this branch:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/03e02209b5c4d5242648f068c465d246b040b13f/OpenStack_Folsom_Install_Guide_WebVersion.rst

Everything went well up to the point where I have to create my VM.
Reading error logs through horizon, I am told that my VM can not access the metadata, either screaming no route to host or can not reach.

I also stumble into this log messages:
cloud-init-nonet waiting 120 seconds for a network device.

cloud-init-nonet gave up waiting for a network device.

Waiting up to 60 more seconds for network configuration...

Booting system without full network configuration...

This lead me to believe that something is wrong with my br-eth1 used for VM configuration.
I've double checked all my settings and files to match the guide and when I run
nova-manage service list, I get smiley faces matching on both controller + compute nodes.

Currently, I have an unmanaged gigabit switch that connect eth1 on both nodes together.
They are assigned static ip 100.10.10.51 and 100.10.10.52 correspondingly.
The nodes can ping each other fine through this dev and ip.
However after I run ovs-vsctl add-port br-eth1 eth1, I could not ping between nodes anymore.
My main suspicion is in this VM conf bridge (green in the diagram) that I am trying to replicate.

Any help is appreciated. Thanks for reading.

Single-Interface Server

Hey there,

I tried to install the howto on a server with just one interface (and an alias eth0:0).
You used three interfaces in the same subnet, why is that?

Wouldn't it be better to have an private interface eth0:192.168.0/24, an host-only interface eth0:0:172.16/16 and an optional external interface eth1:10.10/16.

If I understand this 'cloud'-thingy right, that would be my aim. :)

Cheers
Christian

Horizon Returns an Internal Service Error

When trying to access the Horizon dashboard, I get an internal service error (500) once I log-in with a correct username/password combination (incorrect usernames and passwords return invalid user as expected).

It looks like a might have an endpoint issue of some sort? Any advice on troubleshooting this? I have gone through the guide (attempting to adapt for a single node, so I installed the compute node on the same node.) Here are the error logs:

root@alpine:/var/log/apache2# tail *
==> access.log <==

==> error.log <==
[Mon Nov 05 22:02:58 2012] [error] EndpointNotFound: Endpoint not found.
[Mon Nov 05 17:07:02 2012] [notice] caught SIGTERM, shutting down
[Mon Nov 05 17:09:18 2012] [notice] Apache/2.2.22 (Ubuntu) mod_wsgi/3.4 Python/2.7.3 configured -- resuming normal operations
[Mon Nov 05 22:23:47 2012] [error] unable to retrieve service catalog with token
[Mon Nov 05 22:23:47 2012] [error] Traceback (most recent call last):
[Mon Nov 05 22:23:47 2012] [error] File "/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 132, in _extract_service_catalog
[Mon Nov 05 22:23:47 2012] [error] endpoint_type='adminURL')
[Mon Nov 05 22:23:47 2012] [error] File "/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py", line 62, in url_for
[Mon Nov 05 22:23:47 2012] [error] raise exceptions.EndpointNotFound('Endpoint not found.')
[Mon Nov 05 22:23:47 2012] [error] EndpointNotFound: Endpoint not found.

==> horizon_access.log <==
192.168.1.119 - - [04/Nov/2012:11:25:59 -0500] "GET /i18n/js/horizon/ HTTP/1.1" 200 2406 "http://192.168.1.108/project/instances/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:26:01 -0500] "GET /admin/ HTTP/1.1" 200 2847 "http://192.168.1.108/project/instances/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:26:02 -0500] "GET /i18n/js/horizon/ HTTP/1.1" 200 2406 "http://192.168.1.108/admin/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /admin/images/images/ HTTP/1.1" 200 2444 "http://192.168.1.108/admin/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /static/dashboard/js/176baabe0b2d.js HTTP/1.1" 200 653 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /i18n/js/horizon/ HTTP/1.1" 200 2407 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /static/dashboard/css/f7c16500d168.css HTTP/1.1" 200 18623 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /static/dashboard/js/72a001aeb8e5.js HTTP/1.1" 200 62520 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /static/dashboard/img/logo.png HTTP/1.1" 200 5381 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
192.168.1.119 - - [04/Nov/2012:11:27:05 -0500] "GET /static/dashboard/fonts/Anivers_Regular-webfont.woff HTTP/1.1" 200 29736 "http://192.168.1.108/admin/images/images/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"

==> horizon_error.log <==
[Sun Nov 04 16:27:05 2012] [error] x-openstack-request-id: req-556771aa-af89-4438-a4a4-5743818abce1
[Sun Nov 04 16:27:05 2012] [error]
[Sun Nov 04 16:27:05 2012] [error] {"images": []}
[Sun Nov 04 16:27:05 2012] [error]
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.001) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.679191 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.679191')
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.001) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.680765 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.680765')
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.002) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.678583 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.678583')
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.002) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.680732 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.680732')
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.001) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.716012 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.716012')
[Sun Nov 04 16:27:05 2012] [error] DEBUG:django.db.backends:(0.001) SELECT "django_session"."session_key", "django_session"."session_data", "django_session"."expire_date" FROM "django_session" WHERE ("django_session"."session_key" = f167a3dd56eb2583e32256a3ddad5259 AND "django_session"."expire_date" > 2012-11-04 16:27:05.744217 ); args=('f167a3dd56eb2583e32256a3ddad5259', u'2012-11-04 16:27:05.744217')

==> other_vhosts_access.log <==
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:36 +0000] "GET /static/dashboard/css/9feb0b911869.css HTTP/1.1" 200 18682 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:36 +0000] "GET /static/dashboard/img/logo.png?bd0a834bae0e HTTP/1.1" 200 3539 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:36 +0000] "GET /static/dashboard/img/favicon.ico HTTP/1.1" 200 1458 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "POST /horizon/auth/login/ HTTP/1.1" 302 2016 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /horizon HTTP/1.1" 302 368 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /horizon/syspanel/ HTTP/1.1" 500 1663 "http://192.168.1.108/horizon" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /static/dashboard/js/176baabe0b2d.js HTTP/1.1" 200 665 "http://192.168.1.108/horizon/syspanel/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /horizon/i18n/js/horizon/ HTTP/1.1" 200 2425 "http://192.168.1.108/horizon/syspanel/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /static/dashboard/js/d17288657b07.js HTTP/1.1" 200 62520 "http://192.168.1.108/horizon/syspanel/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"
127.0.1.1:80 192.168.1.142 - - [05/Nov/2012:22:23:47 +0000] "GET /horizon/syspanel/dashboard/img/favicon.ico HTTP/1.1" 404 1683 "http://192.168.1.108/horizon/syspanel/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14"

Openstack instanance not getting the IP "Folsom cluster on Ubuntu 10.12"

  First of all thank you so much for putting all this together. I followed the following documentation on setting up a 3 node cluster with 2 x nic. My VMz/instance are not getting any IP. 

Folsom + Quantum on GRE with 2 NICs is available through GRE/2NICs branch:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

                Looking at the diagnostics.  I see there is no connection between the bridges, between my network and compute node. Hence I am not getting the dhcp offer from my network node. 

Network-Node:

bridge name bridge id STP enabled interfaces
br-ex 0000.00237d28f814 no eth2
br-int 0000.e6ecd960864d no tapf0241b37-64
br-tun 0000.5680c46e5748 no

netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.0.24.253 0.0.0.0 UG 0 0 0 eth0
10.0.24.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 tapf0241b37-64

Compute Node:

brctl show

bridge name bridge id STP enabled interfaces
br-int 0000.aed7f6580d45 no qvo3609cc1d-00 qvoac592d01-a3
qbr3609cc1d-00 8000.be822f621717 no qvb3609cc1d-00 vnet1
qbrac592d01-a3 8000.c2983a7652b6 no qvbac592d01-a3

netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.0.23.253 0.0.0.0 UG 0 0 0 eth0
10.0.23.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
100.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1

Just wondering if there is any set of IP table rules to be added ?

Thank you
Chakri

There is an Extra Line which is incomplete by itselves and not required -

2.5. Others

Install other services:

apt-get install vlan bridge-utils

Enable IP_Forwarding:

sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf
`# To save you from rebooting, perform the following
sysctl net.ipv4.ip_forward=1`

Suggestion: Add Creds Note

One thing that took a little while to click with me is that once you get into the "Create your first vm phase", any tools won't show what you have created, for examples, cinder list until you update your your creds variables:

Maybe add a note with something like:

root@alpine:~/src# cat user_one_creds 
export OS_TENANT_NAME=project_one
export OS_USERNAME=user_one
export OS_PASSWORD=user_one
export OS_AUTH_URL="http://192.168.1.108:5000/v2.0/"

Glance configuration file instructions may be incorrect...

I've just done a 'apt-get install glance' and the resulting config files in /etc/glance/ are not matching up to what your instructions indicate should be edited. Specifically, doing a 'cat glance-registry-paste.ini' after glance install results in:

# Use this pipeline for no auth - DEFAULT
[pipeline:glance-registry]
pipeline = unauthenticated-context registryapp

# Use this pipeline for keystone auth
[pipeline:glance-registry-keystone]
pipeline = authtoken context registryapp

[app:registryapp]
paste.app_factory = glance.registry.api.v1:API.factory

[filter:context]
paste.filter_factory = glance.api.middleware.context:ContextMiddleware.factory

[filter:unauthenticated-context]
paste.filter_factory = glance.api.middleware.context:UnauthenticatedContextMiddleware.factory

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory

Notice the lack of the SERVICE tenant's name, user and password entries.

I'm not sure if someone changed something upstream, or I've done a prior step incorrectly and installed a strange version of glance without the credential settings in it. Can you confirm we should be adding auth info to this file, and not the glance-registry.conf file?

issue about whe I run "sh keystone_endpoints_basic.sh"

Look, I have some problem run the "sh keystone_basic.sh" and "sh keystone_endpoints_basic.sh"

I can see some error over the output:

Is that right?

root@openstack01:/home/pvillarruel/OpenStack-Folsom-Install-guide/Keystone_Scripts/Without Quantum# sh keystone_basic.sh
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --tenant-id 983d2673144f4208803950908e4cb156
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --tenant-id 983d2673144f4208803950908e4cb156
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --tenant-id 983d2673144f4208803950908e4cb156
usage: keystone user-role-add --user --role
[--tenant_id ]
keystone user-role-add: error: argument --user is required
root@openstack01:/home/pvillarruel/OpenStack-Folsom-Install-guide/Keystone_Scripts/Without Quantum# sh keystone_
keystone_basic.sh keystone_endpoints_basic.sh
root@openstack01:/home/pvillarruel/OpenStack-Folsom-Install-guide/Keystone_Scripts/Without Quantum# sh keystone_endpoints_basic.sh
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | OpenStack Compute Service |
| id | dc082292ba094edda556c7c56bbca8f0 |
| name | nova |
| type | compute |
+-------------+----------------------------------+
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | OpenStack Volume Service |
| id | 86060b0609d749e1b0ed0a0a9b8c433e |
| name | cinder |
| type | volume |
+-------------+----------------------------------+
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | OpenStack Image Service |
| id | 1deac0abcbf5471bb56eb97e04f74a31 |
| name | glance |
| type | image |
+-------------+----------------------------------+
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | OpenStack Identity |
| id | 967ce803138c49e58ee468193655bd51 |
| name | keystone |
| type | identity |
+-------------+----------------------------------+
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | OpenStack EC2 service |
| id | e384c08ebf394cb488e93821eaaa2636 |
| name | ec2 |
| type | ec2 |
+-------------+----------------------------------+
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --service-id dc082292ba094edda556c7c56bbca8f0
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --service-id 86060b0609d749e1b0ed0a0a9b8c433e
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --service-id 1deac0abcbf5471bb56eb97e04f74a31
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --service-id 967ce803138c49e58ee468193655bd51
usage: keystone [--os_username ]
[--os_password ]
[--os_tenant_name ]
[--os_tenant_id ] [--os_auth_url ]
[--os_region_name ]
[--os_identity_api_version ]
[--token ] [--endpoint ]
[--username ] [--password ]
[--tenant_name ] [--auth_url ]
[--region_name ]
...
keystone: error: unrecognized arguments: --service-id e384c08ebf394cb488e93821eaaa2636

Ping test within n/w and compute node failed after creating bridges

Hi ,

Let me give you some background of my setup.
I am ref. this url for my setup :
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

The interface configuration is as below :
Control Node: eth0 (100.10.10.51), eth1 (192.168.100.51)
Network Node: eth0 (100.10.10.52), eth1 (100.20.20.52), eth2 (192.168.100.52)
Compute Node: eth0 (100.10.10.53), eth1 (100.20.20.53)

Issue :
I was able to ping 100.20.20.53 of compute node from n/w node and 100.20.20.52 of n/w node from Compute note.
Now during installation process i added the bridges and from that point of time i was unable to reach n/w node from compute and vise a versa.
Not sure what went wrong , any help is appreciated. !

glance config

Hi

I test your document in ubuntu 12.04

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst

in glance Update /etc/glance/glance-api-paste.ini with:

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
auth_host = 100.10.10.51
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = glance
admin_password = service_pass

seem not right. you need update the /etc/glance/glance-api.conf

the /etc/glance/glance-registry-paste.ini also same.

need update /etc/glance/glance-registry.conf

no IP on VM, Can't reach the metadata server, can't ping & ssh

Great document! But I'm having trouble towards the end and would appreciate if you can provide some insights.

I followed the VLAN/2NICs branch but I'm unable to get an IP allocated to my VM (50.50.1.0/24). VM instance console shows that the instance cannot reach the metadata and followed your recommendations from #22 and confirmed that from my network node I can reach the metadata server.

Below are a few config/outputs from my nodes; appreciate all the help.
Thank you

Controller Node

root@controller:~# route -n
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 0.0.0.0         10.46.200.1     0.0.0.0         UG    100    0        0 eth0
 10.46.200.0     0.0.0.0         255.255.254.0   U     0      0        0 eth0
 50.50.1.0       10.46.200.1     255.255.255.0   UG    0      0        0 eth0
 100.10.10.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1

root@controller:~# ovs-vsctl show
304d97ba-a9b2-499e-b9f0-afefa1eb17a5
    ovs_version: "1.4.0+build0"

root@controller:~# grep -v "#" /etc/quantum/api-paste.ini
[composite:quantum]
/: quantumversions
/v2.0: quantumapi_v2_0

[composite:quantumapi_v2_0]
use = call:quantum.auth:pipeline_factory
noauth = extensions quantumapiapp_v2_0
keystone = authtoken keystonecontext extensions quantumapiapp_v2_0

[filter:keystonecontext]
paste.filter_factory = quantum.auth:QuantumKeystoneContext.factory

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
auth_host = 100.10.10.51
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = quantum
admin_password = openstack

[filter:extensions]
paste.filter_factory = quantum.extensions.extensions:plugin_aware_extension_middleware_factory

[app:quantumversions]
paste.app_factory = quantum.api.versions:Versions.factory

[app:quantumapiapp_v2_0]
paste.app_factory = quantum.api.v2.router:APIRouter.factory

Network Node

root@Network:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.46.200.1     0.0.0.0         UG    100    0        0 br-ex
10.46.200.0     0.0.0.0         255.255.254.0   U     0      0        0 br-ex
100.10.10.0     0.0.0.0         255.255.255.0   U     0      0        0 br-eth1

root@Network:~# ovs-vsctl show
bc8dc4db-e84d-4df9-885d-66547c9411f8
    Bridge br-ex
        Port "qg-9791a7f9-cd"
            Interface "qg-9791a7f9-cd"
                type: internal
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth0"
            Interface "eth0"
    Bridge br-int
        Port "tap0bbc49ed-d6"
            tag: 1
            Interface "tap0bbc49ed-d6"
                type: internal
        Port "qr-e736f376-63"
            tag: 1
            Interface "qr-e736f376-63"
                type: internal
        Port "int-br-eth1"
            Interface "int-br-eth1"
        Port br-int
            Interface br-int
                type: internal
    Bridge "br-eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "eth1"
            Interface "eth1"
    ovs_version: "1.4.0+build0"

root@Network:~# grep -v "#" /etc/quantum/l3_agent.ini
[DEFAULT]

interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver

auth_url = http://100.10.10.51:35357/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = quantum
admin_password = openstack
metadata_ip = 10.46.200.193
metadata_port = 8775

root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf

Compute Node

root@compute:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.46.200.1     0.0.0.0         UG    100    0        0 eth0
10.46.200.0     0.0.0.0         255.255.254.0   U     0      0        0 eth0
100.10.10.0     0.0.0.0         255.255.255.0   U     0      0        0 br-eth1

root@compute:~# ovs-vsctl show
fb3124bd-56fb-46ea-ae56-60d3f7af112a
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
        Port "qvo77fc2e6f-35"
            tag: 1
            Interface "qvo77fc2e6f-35"
        Port "int-br-eth1"
            Interface "int-br-eth1"
        Port "qvo6e4b4d01-18"
            tag: 1
            Interface "qvo6e4b4d01-18"
        Port "qvo3650512e-f8"
            tag: 1
            Interface "qvo3650512e-f8"
    Bridge "br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "eth1"
            Interface "eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
    ovs_version: "1.4.0+build0"

Checking metadata support:

root@network:/etc/quantum# ping 10.46.200.193
PING 10.46.200.193 (10.46.200.193) 56(84) bytes of data.
64 bytes from 10.46.200.193: icmp_req=1 ttl=64 time=0.263 ms
^C
--- 10.46.200.193 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.263/0.263/0.263/0.000 ms

root@network:/etc/quantum# ip netns exec qrouter-91ad119b-83ad-41b9-91ac-04248f943fb6 ping 10.46.200.193
PING 10.46.200.193 (10.46.200.193) 56(84) bytes of data.
64 bytes from 10.46.200.193: icmp_req=1 ttl=64 time=11.3 ms
64 bytes from 10.46.200.193: icmp_req=2 ttl=64 time=0.244 ms

Done with Installation and now facing issues while administrating OpenStack

Hi There,

Have completed my installation using the link mentioned below :
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst

And now its time to administrate my OpenStack.
Here cums the queries I have during administrating the OpenStack :

a)Am able to successfully log-in and launch an instance for image "cirros-0.3.0-x86_64-disk.img" i.e MyFirstImage.
b)Am able to take VNC console of the instance using horizon UI, however on VNC console ,I see "connected to QEMU instance 0009"... etc , Does it [QEMU] means i have installed a simulator and not a real world setup that can be used for production ??
Is the virtual machine really created or its just a simulation, bcoz this instance has no disk attached to it, still it am able to login ??
c)Navigating on horizon UI, I see available disk space as "1000GB" however my compute node has only 500GB hard-disk, So where does this 1000GB points to, again am afraid it its just a simulator and not a real world production setup ??
d)And the last one, am not able to create a volume using UI, the status is shown as "error", not sure how to debug it and where to check the logs??

Think am close but still few tricky things todo !

Regards,
Sanket.

Some questions about GRE/2NIC Setup

Hello,
I want to install openstack on an small testbed with only 2 NICs per Node and a "dumb" switch. I'm not familiar with GRE, my only knowledge about this topic is the wikipedia entry.
Could I deploy the GRE/2NIC setup on a switch without GRE support?

The testbed is for a academic purpose and therefore I want to setup OpenStack once and then use it. It is possible to install the GRE/2NIC setup on Ubuntu 12.04 if I add the folsom repository as mentioned in the official OpenStack documentation?

Regards

p.s. I hope this is the right place for questions about the guide. I don't find any other communication channels like a mailinglist or so on.

iscsitarget setting

Hi,
Thanks for this guide, its very helpful

Cinder installation guide missed some configuration on iscsitarget (/etc/default/iscsitarget)
I think it must be set to "true" right? And you need to start services after that
service iscsitarget start
service open-iscsi start

Network/Compute node connectivity with 2 NICs

So I'm following the guide for: "Folsom + Quantum on VLAN with 2 NICs is available through VLAN/2NICs branch"

Controller node is all setup, no issues. On the network node, I'm having some connectivity issues when adding the bridges. Specifically, when executing the following:

br-int will be used for VM integration

ovs-vsctl add-br br-int

br-eth1 will be used for VM configuration

ovs-vsctl add-br br-eth1
ovs-vsctl add-port br-eth1 eth0

br-ex is used to make to VM accessible from the internet

ovs-vsctl add-br br-ex
ovs-vsctl add-port br-ex eth2

My box stops sending packets back over eth2 when the last one is executed. I have physical NICs for eth2 and eth0.

Is there something I'm missing here? It seems like the br-eth1 tied to eth2 works since br-eth1 has an ip defined in /etc/network/interfaces, but the br-ex has no definition that I can see, is this correct?

Similarly, I'm running into this issue where the NIC no longer send packets back with the compute node when adding the port for the bridge:

br-int will be used for VM integration

ovs-vsctl add-br br-int

br-eth1 will be used for VM configuration

ovs-vsctl add-br br-eth1
ovs-vsctl add-port br-eth1 eth0

Do these ports need anything special done to them, or need any other configuration that I may be missing to allow the traffic?

Thanks.

glance cache manage middleware not enabled

Hello, we have some problems with the glance configuration (from the scripts) on keystone.

We needed to change the API to v1 on the keystone to solve our problem.

https://answers.launchpad.net/glance/+question/222997

Thanks for the docs!

Daniel

Wrong port for testing keystone?

I think you use the wrong port when testing keystone (branch: VLAN/2NICs)

Instead of:

curl http://192.168.100.51:5000/v2.0/endpoints -H 'x-auth-token: ADMIN'

I think you should have:

curl http://192.168.100.51:35357/v2.0/endpoints -H 'x-auth-token: ADMIN'

Public IP Directly to VM

I followed this (3 nic) guide and everything seems to be working correctly but I have a question. Can you add an IP directly to a vm? Meaning can you bypass nat and have a ip address show up inside the vm as eth1 for example.

Thank you!
Josh

Error: No handlers could be found for logger "keystoneclient.client"

Earlier I completed the Folsom installation and I was able to create VM(though I was not able to ping it).
then some issue occurred after deleting tenants and project and I started getting error.
Error: No handlers could be found for logger "keystoneclient.client"
Invalid tenant.

Then I start over installation for controller node.
while executing ./keystone_basic.sh, I am getting these error:
root@controllernode:# ./keystone_basic.sh
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store tenant. (IntegrityError) (1062, "Duplicate entry 'admin' for key 'name'") (HTTP 409)
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store tenant. (IntegrityError) (1062, "Duplicate entry 'service' for key 'name'") (HTTP 409)
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store user. (IntegrityError) (1062, "Duplicate entry 'admin' for key 'name'") (HTTP 409)
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store role. (IntegrityError) (1062, "Duplicate entry 'admin' for key 'name'") (HTTP 409)
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store role. (IntegrityError) (1062, "Duplicate entry 'KeystoneAdmin' for key 'name'") (HTTP 409)
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store role. (IntegrityError) (1062, "Duplicate entry 'KeystoneServiceAdmin' for key 'name'") (HTTP 409)
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
No handlers could be found for logger "keystoneclient.client"
Conflict occurred attempting to store role. (IntegrityError) (1062, "Duplicate entry 'Member' for key 'name'") (HTTP 409)
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
root@controllernode:#

keystone scripts need updating for folsom -- %(tenant_id)s

gmi in #openstack mentions that the keystone endpoints should be using "%(tenant_id)s" vs "$(tenant_id)s" as per the latest install guide.

Nova db sync returns error

i believe that
CREATE DATABASE nova;
is creating problem as there is some charset issue
so instead
create database nova character set latin1;
could may be save the day.

Note the use of the latin1 character set when we created the tables in MySQL. This is so the following command will not cause an error due to the default UTF-8 character set creating indexes that are too big for MySQL to handle.

IPaddress (floating and internal) quantum 3 nic vlan

Using the guide, after everything is setup, ping to the floating ip fails.

i am wondering how i can verify the data link ( green) between the network and compute node.

for now we get the internal ip for VM, and they can ping each other but not the gateway ( router ), when floating ips are applied they dont show up on nova-list is this normal? i cannot ping or ssh to any of the VM.

metadata issues when running UEC images from ubuntu.

Frankly i do not know where to start with the d1bug

Should i use quantum or Should i Not.

Hi,
I have below h/w with me :

Node Role: NICs
Control Node: eth0 (100.10.10.51), eth1 (192.168.100.51)
Network Node: eth0 (100.10.10.52), eth1 (100.20.20.52), eth2 (192.168.100.52)
Compute Node: eth0 (100.10.10.53), eth1 (100.20.20.53)

My Doubt :

After reading "note 3" am bit confused as ...
1)whether i should follow the same guide as it is. ???
OR
2)Whether i should follow the same guide , but follow nova section from the hyper linked guide.

I would prefer to use the same guide as it is, but will it work ??

Please Note : Am beginner in open stack.

can not ssh vm

I set up an environment based on https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst on ubuntu 12.04.

I create a new instance with IP address is 50.50.1.2, and everything is OK except ssh. I had updated secgroup to allow ssh.
when ssh to vm, it show " Received disconnect from 50.50.1.2: 2:"

No handlers could be found for logger "keystoneclient.client"

Hi,

Earlier I completed the Folsom installation and I was able to create VM, and I was able to ping VM, but I was not able to login to dashboard through horizon, so I restarted mysql and apache2,
Then when I am trying to create new VM but I am getting these errors:
"No handlers could be found for logger "keystoneclient.client"
Authorization Failed: Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)"

I tried with fresh keystone DB, these steps
drop database keystone;
create database keystone;

then keystone-manage db_sync
but I when I try to execute scripts (./keystone_basic.sh) I am getting these errors:
root@controllernode:~# ./keystone_basic.sh
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --user-id/--user_id: expected one argument
No handlers could be found for logger "keystoneclient.client"
Unable to communicate with identity service: (403, 'Blocked by Websense'). (HTTP 400)
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument
usage: keystone user-create --name [--tenant-id ]
[--pass ] [--email ]
[--enabled <true|false>]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id --role-id
[--tenant-id ]
keystone user-role-add: error: argument --tenant-id: expected one argument

github source controller in virtual machine

Our develop team has upto 10 i phone application developers. But we are using Virtual machines (VM ware). So can we use github source controller in virtual machine??
If it impossible, what should I do ?
Thanks ,,

Problem during Network Node setup of OpenVSwitch

I believe I have found an issue with setup of the Network Node when setting up OpenVSwitch.

I'm using this guide with Ubuntu 12.10:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

The instant I add a port to each bridge, I lose connectivity to the network on that port. The most telling one was obviously external (eth2) one as my ssh session was lost. After each of the following commands, I lose connectivity on those physical eth ports.

ovs-vsctl add-port br-eth1 eth1
ovs-vsctl add-port br-ex eth2

I found a workaround on OpenVMSwitch guide here under Configuration Problems, the very first problem:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD

I guess physical ports can't have the address, you now need to use the bridge.

ifconfig eth1 0.0.0.0
ifconfig br-eth1 100.20.20.52

ifconfig eth2 0.0.0.0
ifconfig br-ex 192.168.100.52

Naturally, you'll want to make these settings persistent after reboot, and I'm not sure what to recommend there.

Great guide by the way!

Meta-data server can't be reach...

Hi guys,

I need your help. When my vms try to reach the meta-data server, I always have these errors:

2013-03-21 17:08:52,802 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url error [timed out]

2013-03-21 17:09:43,854 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url error [timed out]

2013-03-21 17:10:01,873 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [timed out]

And i already put my rule in IPtables to dnat 169.254.169.254 to my controller node. Here the rule: iptables -t nat -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 192.168.4.74:8775

And also,

2013-03-21 15:19:07 1252 INFO nova.metadata.wsgi.server [-] 192.168.4.74 - - [21/Mar/2013 15:19:07] "GET /latest/meta-data/ HTTP/1.1" 404 278 0.124937

2013-03-21 15:31:17 1252 INFO nova.api.ec2 [-] 0.121127s 192.168.4.74 GET /openstack None:None 404 [curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3] text/plain text/html

2013-03-21 15:31:17 1252 INFO nova.metadata.wsgi.server [-] 192.168.4.74 - - [21/Mar/2013 15:31:17] "GET /openstack HTTP/1.1" 404 278 0.122755

2013-03-21 15:31:33 1267 INFO nova.ec2.wsgi.server [-] 192.168.4.74 - - [21/Mar/2013 15:31:33] "GET /openstack HTTP/1.1" 404 455 0.001182

Did someone has the same problem and solved it ?

Internet access through controller

Hi,
I would like to know why traffic to internet from VMs must go through the controller br-ex interface.
If I need to have a VM to serve as gateway, what changes need to be done.

Thanks,
-Ravi,

VM instance ping/ssh issue - Folsom [Vlan and GRE/TUN]

Hello,

The following GitHub guides were followed.

3 NIC Vlan - https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
2 NIC GRE/TUN - https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

Setup information:

Two/Three vm's created on Vmware ESX. Vswitches [no vmnic attached] created and connected to each vm based on guide.

On both the setup, there is a common problem where the vm instances cannot be pinged and hence unable to ssh.

VM instance fixed ip is 50.50.1.x series
VM instance floating ip is 10.1.0.x series
Gateway for Floating ip is 10.0.0.1

Bit of investigation shows the following:

1. From the Horizon console log:
url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [[Errno 101] Network is unreachable]
2013-02-13 04:41:21,018 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 126 seconds
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
ci-info: eth0  : 1 .               .               fa:16:3e:5a:1d:58
route_info failed
 * Stopping Handle applying cloud-config[74G[ OK ]
Waiting for network configuration...
Waiting up to 60 more seconds for network configuration...
Booting system without full network configuration...

2. Tracepath gets no reply from the Gateway
root@controller:~# tracepath 50.50.1.5
 1:  10.1.0.4                                              0.149ms pmtu 1500
 1:  10.1.0.6                                              0.687ms 
 1:  10.1.0.6                                              0.318ms 
 2:  10.0.0.1                                              0.581ms asymm  1 
 3:  no reply
 4:  no reply
root@controller:~# tracepath 10.1.0.17
 1:  10.1.0.4                                              0.094ms pmtu 1500
 1:  10.1.0.17                                             0.930ms 
 1:  10.1.0.17                                             0.294ms 
 2:  10.0.0.1                                              0.436ms asymm  1 
 3:  no reply
 4:  no reply
3. From the network node openvswitch-agent.log
2013-02-12 08:57:48    DEBUG [quantum.agent.linux.utils] Running command: sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf ovs-ofctl del-flows br-int
2013-02-12 08:57:48    DEBUG [quantum.agent.linux.utils]
Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-ofctl', 'del-flows', 'br-int']
Exit code: 1
Stdout: ''
Stderr: 'ovs-ofctl: br-int is not a bridge or a socket\n'
2013-02-12 08:57:48    ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-ofctl', 'del-flows', 'br-int']. Exception:
Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-ofctl', 'del-flows', 'br-int']
Exit code: 1
              Stdout: ''
              Stderr: 'ovs-ofctl: br-int is not a bridge or a socket\n'

My thought is either there is a network misconfiguration which i'm not able to figure out OR the vm instance is not booting completely into the OS and hence its not getting an IP.

1. In the Horizon vm instance log, what messages is an indication the vm instance has completely booted into the OS?
2. Lets say if the vm instance has booted into the OS, then is it a possible network configuration issue.

Regards,
Sandeep.

modify_iptables_manager.rst - not required

For the latest installations from the launchpad repo. for Folsom - this hack is not required as it is already fixed. Though keeping it is convenient, i believe a note should be added regarding the same.

Instances not Receiving DHCP Offers with Nova-Network Method

After toiling away at Quantum, I threw in the towel and am trying nova-network. However, my instances don't seem to be receiving DHCP offers (for example, the following vm console snippet:

Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed

When I tail syslog on my host machine, I do see Discover requests and offers:

Nov 10 17:10:42 alpine dnsmasq-dhcp[4741]: DHCPDISCOVER(br100) fa:16:3e:59:e5:15 
Nov 10 17:10:42 alpine dnsmasq-dhcp[4741]: DHCPOFFER(br100) 192.168.2.2 fa:16:3e:59:e5:15 
Nov 10 17:10:45 alpine dnsmasq-dhcp[4741]: DHCPDISCOVER(br100) fa:16:3e:59:e5:15 
Nov 10 17:10:45 alpine dnsmasq-dhcp[4741]: DHCPOFFER(br100) 192.168.2.2 fa:16:3e:59:e5:15 

If I manually set the instance IP to 192.168.2.2 from inside the instance, I am able to get networking between the host and the instance - it works.

Not sure what to look at next, here is some information from the host machine:

creation command (tried both with multi_host and without it (I am doing this all one one node, not really sure what multi_host is for):

nova-manage network create my_flat6 --fixed_range_v4=192.168.2.1/24 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=128 --multi_host=T

nova.conf:

root@alpine:~# cat /etc/nova/nova.conf
[DEFAULT]
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/run/lock/nova
verbose=True
api_paste_config=/etc/nova/api-paste.ini
scheduler_driver=nova.scheduler.simple.SimpleScheduler
s3_host=192.168.1.108
ec2_host=192.168.1.108
ec2_dmz_host=192.168.1.108
rabbit_host=192.168.1.108
cc_host=192.168.1.108
nova_url=http://192.168.1.108:8774/v1.1/
sql_connection=mysql://novaUser:[email protected]/nova
ec2_url=http://192.168.1.108:8773/services/Cloud
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
metadata_host=192.168.1.108
metadata_listen=0.0.0.0

# Auth
use_deprecated_auth=false
auth_strategy=keystone
keystone_ec2_url=http://192.168.1.108:5000/v2.0/ec2tokens
# Imaging service
glance_api_servers=192.168.1.108:9292
image_service=nova.image.glance.GlanceImageService

# Vnc configuration
novnc_enabled=true
novncproxy_base_url=http://192.168.1.108:6080/vnc_auto.html
novncproxy_port=6080
vncserver_proxyclient_address=192.168.1.108
vncserver_listen=0.0.0.0

# Network settings
#network_api_class=nova.network.quantumv2.api.API
#quantum_url=http://192.168.1.108:9696
#quantum_auth_strategy=keystone
#quantum_admin_tenant_name=service
#quantum_admin_username=quantum
#quantum_admin_password=service_pass
#quantum_admin_auth_url=http://192.168.1.108:35357/v2.0
#libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
#linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
#firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver

# NETWORK
network_manager=nova.network.manager.FlatDHCPManager
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
force_dhcp_release=True
public_interface=eth0
flat_interface=eth1
flat_network_bridge=br100
connection_type=libvirt
fixed_range=192.168.2.1/24
flat_network_dhcp_start=192.168.2.2
flat_injected=False
network_size=256
#multi_host=True

# Compute #
compute_driver=libvirt.LibvirtDriver

# Cinder #
volume_api_class=nova.volume.cinder.API
osapi_volume_listen_port=5900

nova-compute.conf:

root@alpine:~# cat /etc/nova/nova-compute.conf 
[DEFAULT]
libvirt_type=kvm
#libvirt_ovs_bridge=br-int
#libvirt_vif_type=ethernet
#libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
libvirt_use_virtio_for_bridges=True

ifconfig:

root@alpine:~# ifconfig
br100     Link encap:Ethernet  HWaddr 00:80:8e:8a:8d:f5  
          inet addr:192.168.2.1  Bcast:192.168.2.127  Mask:255.255.255.128
          inet6 addr: fe80::503b:46ff:fe8c:e8ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1644 (1.6 KB)  TX bytes:3270 (3.2 KB)

eth0      Link encap:Ethernet  HWaddr 1c:6f:65:94:ce:a2  
          inet addr:192.168.1.108  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::1e6f:65ff:fe94:cea2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2030 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1785 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:217244 (217.2 KB)  TX bytes:398070 (398.0 KB)

eth1      Link encap:Ethernet  HWaddr 00:80:8e:8a:8d:f5  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20212 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:7956664 (7.9 MB)  TX bytes:7956664 (7.9 MB)

vnet0     Link encap:Ethernet  HWaddr fe:16:3e:59:e5:15  
          inet6 addr: fe80::fc16:3eff:fe59:e515/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:1840 (1.8 KB)  TX bytes:7993 (7.9 KB)

/etc/network/interfaces:

root@alpine:~# cat /etc/network/interfaces 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

#Apparently nova adds this on its own
#auto br100
#iface br100 inet dhcp
    #address 192.168.1.108
    #broadcast 192.168.1.255
    #netmask 255.255.255.0
    #gateway 192.168.1.1
#   bridge_ports    eth1
#   bridge_stp  off
#   bridge_maxwait  0
#   bridge_fd   0

auto eth1
iface eth1 inet static
    address 192.168.2.1
    netmask 255.255.255.0

brctl show:

bridge name bridge id       STP enabled interfaces
br100       8000.00808e8a8df5   no      eth1
                            vnet0

tcpdump during the discover phase tcpdump -i vnet0 -n:

17:43:32.214233 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:43:35.218068 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:43:35.218097 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:43:35.218252 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:43:38.222120 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:43:38.222146 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:43:38.222318 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:44:01.247293 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:01.247318 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:01.247542 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:44:04.251499 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:04.251527 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:04.251753 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:44:07.255714 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:07.255741 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:69:db:ee, length 280
17:44:07.255964 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 307
17:44:12.268108 ARP, Request who-has 192.168.2.3 tell 192.168.2.1, length 28
17:44:13.268106 ARP, Request who-has 192.168.2.3 tell 192.168.2.1, length 28

iptables from the host:

root@alpine:/etc/init.d# iptables -L -n -v
Chain INPUT (policy ACCEPT 81867 packets, 32M bytes)
 pkts bytes target     prot opt in     out     source               destination         
31154   13M nova-compute-INPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
32376   13M nova-network-INPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
40184   16M nova-api-INPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
   68 19152 nova-filter-top  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
   59 17724 nova-compute-FORWARD  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 nova-network-FORWARD  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 nova-api-FORWARD  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT 80912 packets, 33M bytes)
 pkts bytes target     prot opt in     out     source               destination         
81094   33M nova-filter-top  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
30719   14M nova-compute-OUTPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
31941   14M nova-network-OUTPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
39796   17M nova-api-OUTPUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain nova-api-FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-api-INPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            192.168.1.108        tcp dpt:8775

Chain nova-api-OUTPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-api-local (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-compute-FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   59 17724 ACCEPT     all  --  br100  *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  *      br100   0.0.0.0/0            0.0.0.0/0           

Chain nova-compute-INPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-compute-OUTPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-compute-inst-15 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0            state INVALID
  141 11844 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
   57 19095 nova-compute-provider  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
   57 19095 ACCEPT     udp  --  *      *       192.168.2.1          0.0.0.0/0            udp spt:67 dpt:68
    0     0 ACCEPT     all  --  *      *       192.168.2.0/25       0.0.0.0/0           
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:22
    0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0            multiport dports 1:65535
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            multiport dports 1:65535
    0     0 nova-compute-sg-fallback  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain nova-compute-local (1 references)
 pkts bytes target     prot opt in     out     source               destination         
  198 30939 nova-compute-inst-15  all  --  *      *       0.0.0.0/0            192.168.2.3         

Chain nova-compute-provider (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-compute-sg-fallback (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain nova-filter-top (2 references)
 pkts bytes target     prot opt in     out     source               destination         
30976   14M nova-compute-local  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
32000   14M nova-network-local  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
39855   17M nova-api-local  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain nova-network-FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  br100  *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  *      br100   0.0.0.0/0            0.0.0.0/0           

Chain nova-network-INPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   57 17556 ACCEPT     udp  --  br100  *       0.0.0.0/0            0.0.0.0/0            udp dpt:67
    0     0 ACCEPT     tcp  --  br100  *       0.0.0.0/0            0.0.0.0/0            tcp dpt:67
    0     0 ACCEPT     udp  --  br100  *       0.0.0.0/0            0.0.0.0/0            udp dpt:53
    0     0 ACCEPT     tcp  --  br100  *       0.0.0.0/0            0.0.0.0/0            tcp dpt:53

Chain nova-network-OUTPUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain nova-network-local (1 references)
 pkts bytes target     prot opt in     out     source               destination   

Some syslog:

Nov 10 17:09:51 alpine ntpd[4329]: Listen normally on 4 eth0 192.168.1.108 UDP 123
Nov 10 17:09:51 alpine ntpd[4329]: Listen normally on 5 eth1 192.168.2.1 UDP 123
Nov 10 17:09:51 alpine ntpd[4329]: Listen normally on 6 eth0 fe80::1e6f:65ff:fe94:cea2 UDP 123
Nov 10 17:09:51 alpine ntpd[4329]: Listen normally on 7 lo ::1 UDP 123
Nov 10 17:09:51 alpine ntpd[4329]: peers refreshed
Nov 10 17:09:51 alpine ntpd[4329]: Listening on routing socket on fd #24 for interface updates
Nov 10 17:10:33 alpine kernel: [   88.077849] Bridge firewalling registered
Nov 10 17:10:33 alpine NetworkManager[1883]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/br100, iface: br100)
Nov 10 17:10:33 alpine NetworkManager[1883]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/br100, iface: br100): no ifupdown configuration found.
Nov 10 17:10:33 alpine NetworkManager[1883]:  /sys/devices/virtual/net/br100: couldn't determine device driver; ignoring...
Nov 10 17:10:33 alpine kernel: [   88.249681] device eth1 entered promiscuous mode
Nov 10 17:10:33 alpine avahi-daemon[1409]: Withdrawing address record for 192.168.2.1 on eth1.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.2.1.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Interface eth1.IPv4 no longer relevant for mDNS.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Joining mDNS multicast group on interface br100.IPv4 with address 192.168.2.1.
Nov 10 17:10:33 alpine avahi-daemon[1409]: New relevant interface br100.IPv4 for mDNS.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Registering new address record for 192.168.2.1 on br100.IPv4.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Withdrawing address record for 192.168.2.1 on br100.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Leaving mDNS multicast group on interface br100.IPv4 with address 192.168.2.1.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Interface br100.IPv4 no longer relevant for mDNS.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Joining mDNS multicast group on interface br100.IPv4 with address 192.168.2.1.
Nov 10 17:10:33 alpine avahi-daemon[1409]: New relevant interface br100.IPv4 for mDNS.
Nov 10 17:10:33 alpine avahi-daemon[1409]: Registering new address record for 192.168.2.1 on br100.IPv4.
Nov 10 17:10:34 alpine dnsmasq[4741]: started, version 2.63rc6 cachesize 150
Nov 10 17:10:34 alpine dnsmasq[4741]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack
Nov 10 17:10:34 alpine dnsmasq-dhcp[4741]: DHCP, static leases only on 192.168.2.2, lease time 2m
Nov 10 17:10:34 alpine dnsmasq[4741]: reading /etc/resolv.conf
Nov 10 17:10:34 alpine dnsmasq[4741]: using nameserver 192.168.1.1#53
Nov 10 17:10:34 alpine dnsmasq[4741]: read /etc/hosts - 7 addresses
Nov 10 17:10:34 alpine dnsmasq-dhcp[4741]: read /var/lib/nova/networks/nova-br100.conf
Nov 10 17:10:35 alpine avahi-daemon[1409]: Joining mDNS multicast group on interface br100.IPv6 with address fe80::503b:46ff:fe8c:e8ab.
Nov 10 17:10:35 alpine avahi-daemon[1409]: New relevant interface br100.IPv6 for mDNS.
Nov 10 17:10:35 alpine avahi-daemon[1409]: Registering new address record for fe80::503b:46ff:fe8c:e8ab on br100.*.
Nov 10 17:10:35 alpine kernel: [   90.165680]  nbd15: p1
Nov 10 17:10:35 alpine kernel: [   90.165705] nbd15: p1 size 64260 extends beyond EOD, truncated
Nov 10 17:10:35 alpine kernel: [   90.219127] kjournald starting.  Commit interval 5 seconds
Nov 10 17:10:35 alpine kernel: [   90.219147] EXT3-fs (nbd15p1): warning: checktime reached, running e2fsck is recommended
Nov 10 17:10:35 alpine kernel: [   90.232089] EXT3-fs (nbd15p1): using internal journal
Nov 10 17:10:35 alpine kernel: [   90.232093] EXT3-fs (nbd15p1): mounted filesystem with ordered data mode
Nov 10 17:10:35 alpine kernel: [   90.738082] block nbd15: NBD_DISCONNECT
Nov 10 17:10:35 alpine kernel: [   90.738289] block nbd15: Unexpected reply (ffff88058abb7c48)
Nov 10 17:10:35 alpine kernel: [   90.738392] block nbd15: queue cleared
Nov 10 17:10:36 alpine ntpd[4329]: Listen normally on 8 br100 fe80::503b:46ff:fe8c:e8ab UDP 123
Nov 10 17:10:36 alpine ntpd[4329]: peers refreshed
Nov 10 17:10:36 alpine ntpd[4329]: new interface(s) found: waking up resolver
Nov 10 17:10:37 alpine kernel: [   92.375660] audit_printk_skb: 51 callbacks suppressed
Nov 10 17:10:37 alpine kernel: [   92.375663] type=1400 audit(1352585437.501:35): apparmor="STATUS" operation="profile_load" name="libvirt-514cb028-e3b1-4301-8c4e-56345445c707" pid=4930 comm="apparmor_parser"
Nov 10 17:10:37 alpine NetworkManager[1883]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)
Nov 10 17:10:37 alpine NetworkManager[1883]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown configuration found.
Nov 10 17:10:37 alpine NetworkManager[1883]:  /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
Nov 10 17:10:37 alpine kernel: [   92.454158] device vnet0 entered promiscuous mode
Nov 10 17:10:37 alpine kernel: [   92.460433] br100: port 2(vnet0) entered forwarding state
Nov 10 17:10:37 alpine kernel: [   92.460454] br100: port 2(vnet0) entered forwarding state
Nov 10 17:10:38 alpine avahi-daemon[1409]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc16:3eff:fe59:e515.
Nov 10 17:10:38 alpine avahi-daemon[1409]: New relevant interface vnet0.IPv6 for mDNS.
Nov 10 17:10:38 alpine avahi-daemon[1409]: Registering new address record for fe80::fc16:3eff:fe59:e515 on vnet0.*.
Nov 10 17:10:39 alpine dnsmasq-dhcp[4741]: DHCPDISCOVER(br100) fa:16:3e:59:e5:15 
Nov 10 17:10:39 alpine dnsmasq-dhcp[4741]: DHCPOFFER(br100) 192.168.2.2 fa:16:3e:59:e5:15 
Nov 10 17:10:41 alpine ntpd[4329]: Listen normally on 9 vnet0 fe80::fc16:3eff:fe59:e515 UDP 123
Nov 10 17:10:41 alpine ntpd[4329]: peers refreshed
Nov 10 17:10:41 alpine ntpd[4329]: new interface(s) found: waking up resolver
Nov 10 17:10:42 alpine dnsmasq-dhcp[4741]: DHCPDISCOVER(br100) fa:16:3e:59:e5:15 
Nov 10 17:10:42 alpine dnsmasq-dhcp[4741]: DHCPOFFER(br100) 192.168.2.2 fa:16:3e:59:e5:15 
Nov 10 17:10:45 alpine dnsmasq-dhcp[4741]: DHCPDISCOVER(br100) fa:16:3e:59:e5:15 
Nov 10 17:10:45 alpine dnsmasq-dhcp[4741]: DHCPOFFER(br100) 192.168.2.2 fa:16:3e:59:e5:15 
Nov 10 17:15:01 alpine CRON[5818]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 10 17:17:01 alpine CRON[6088]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Not able to ping the gateway 192.168.100.1

Hi,

I completed the Open Stack setup successfully using the following guide https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

I was able to provision a VM . Also, eth0 is getting created on VM but no IP is getting assigned to VM. How ever I can see the IP on Open Stack Horizon UI. So I assigned the same IP manually to the VM.But I am not able to ping/ssh the VM from controller or network.

I have a query regarding the dhcp server agent and gateway.

We have mentioned an IP : 192.168.100.1 as a gateway in controller and network node. So my question is that, where that gateway machine is ? we havent specified any where about it and we should be able to ping that gateway from network node. But in my case , I am not able to ping the gateway. Please assist me on this issue.

Thanks,
Sandeep

iscsi/Cinder Error When Launching Instances

When I try to launch an instance for the Horizon interface, it eventually errors out. In dmesgI see the following:

[  398.221717] iscsi_trgt: open_path(120) Can't open /dev/cinder-volumes/volume-7e279626-ce64-40fd-98f8-8268ae632ca4 -2
[  398.221722] iscsi_trgt: fileio_attach(220) -2
[  488.494103] scsi14 : iSCSI Initiator over TCP/IP
[  488.499525]  connection1:0: detected conn error (1019)
[  506.472712]  connection1:0: detected conn error (1019)
[  523.698659]  connection1:0: detected conn error (1019)
[  540.924327]  connection1:0: detected conn error (1019)
[  558.149168]  connection1:0: detected conn error (1019)
[  575.375072]  connection1:0: detected conn error (1019)
[  592.598646]  connection1:0: detected conn error (1019)

When I look at the volume I created for the instance in Horizon, the ID is: ddaa51f1-01cf-4b09-a34a-5e8a810fbca1. I see that volume in /dev/cinder-volumes:

root@alpine:/dev/cinder-volumes# ls -l
total 0
lrwxrwxrwx 1 root root 7 Nov  9 08:37 volume-78ab331e-6e48-4336-b41f-febfd57caf0e -> ../dm-1
lrwxrwxrwx 1 root root 7 Nov  9 08:37 volume-9da7a1b9-f73e-45d2-989f-166894d6fce5 -> ../dm-0
lrwxrwxrwx 1 root root 7 Nov  9 08:45 volume-ddaa51f1-01cf-4b09-a34a-5e8a810fbca1 -> ../dm-2

So maybe it is the /volume-7e279626-ce64-40fd-98f8-8268ae632ca4 vs ddaa51f1-01cf-4b09-a34a-5e8a810fbca1 mismatch? If that is the case, any idea why that might happen?

some question about document

Hi

thanks for your document, I have some question

1: glance

I have check devstack, the modify as below. whether is same with your document .

cat <>/etc/glance/glance-api.conf
flavor = keystone+cachemanagement
EOF
cat <>/etc/glance/glance-registry.conf
flavor = keystone
EOF

2: quantum

seem need restart the service

service quantum-plugin-openvswitch-agent restart

3:cinder

seem lack the open-iscsi package

so can not find the open-iscsi service
service open-iscsi start

4: network
eth1, seem no need setting IP, right? the quantum setting have no relate the IP of eth1. whether can setting as below. in control node and compute node.

auto eth1
iface eth1 inet manual
up ifconfig eth1 up

5: compute nova

seem lack the novnc nova-novncproxy

also the vnc setting seem no working. I would try to fix it.

instances no acquire IP

I use GRE tutorial. Everythins is OK until run an instance.
nova boot --image 353b5983-ddcf-4942-9f8e-015a91a9ff66 --flavor 1 mv1
+-------------------------------------+----------------------------------------------------------+
| Property | Value |
+-------------------------------------+----------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host | d2 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | d2 |
| OS-EXT-SRV-ATTR:instance_name | instance-00000007 |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | P8yyDLiBc4X4 |
| config_drive | |
| created | 2013-01-15T04:53:05Z |
| flavor | m1.tiny |
| hostId | 74206baca932d6195094df587e8285ad89a00ce0803f3d20756ef989 |
| id | e56a3c07-3886-4446-bd89-82663a41417a |
| image | myFirstImage |
| key_name | None |
| metadata | {} |
| name | mv1 |
| progress | 0 |
| security_groups | [{u'name': u'default'}] |
| status | BUILD |
| tenant_id | 02541303b9904517adf4589d39876375 |
| updated | 2013-01-15T04:53:05Z |
| user_id | 85c4db6d2301403698ff6f854dd641d7 |
+-------------------------------------+----------------------------------------------------------+

nova list
+--------------------------------------+-------+---------+----------+
| ID | Name | Status | Networks |
+--------------------------------------+-------+---------+----------+
| e56a3c07-3886-4446-bd89-82663a41417a | mv1 | ACTIVE | |
+--------------------------------------+-------+---------+----------+

All my log files are fine. Please help me. Why instances don't catch an IP?

In GRE tutorial shown how to create a network
quantum net-create --tenant-id $put_id_of_project_one ext-red

root@d1:~# quantum net-show 949c0aa9-94af-4252-9a74-d0535da18689
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 949c0aa9-94af-4252-9a74-d0535da18689 |
| name | ext_red |
| provider:network_type | vlan |
| provider:physical_network | physnet1 |
| provider:segmentation_id | 3 |
| router:external | True |
| shared | False |
| status | ACTIVE |
| subnets | 6ec6805f-f79a-4ae5-9e59-4f237ba57503 |
| tenant_id | 6c0be957b5e4404daedf42e0491b8c26 |
+---------------------------+--------------------------------------+

That command create net with vlan parameters. Is correct in GRE environment?

Glance update - adding the image

Your guide:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst

2.7 Glance

NEW
glance add name="myFirstImage" is_public=true disk_format=qcow2 container_format=bare < cirros-0.3.0-x86_64-disk.img

OLD
glance image-create --name myFirstImage --is-public true --container-format bare --disk-format qcow2 < cirros-0.3.0-x86_64-disk.img

Issue:
Even when glance accepts new command it gives me this error:

root@folsom-controller:/home/controller/images# glance add name="myFirstImage" is_public=true disk_format=qcow2 container_format=bare < cirros-0.3.0-x86_64-disk.img
Uploading image 'myFirstImage'
Failed to add image. Got error:
The request returned a 302 Multiple Choices. This generally means that you have not included a version indicator in a request URI.

The body of response returned:
{"versions": [{"status": "CURRENT", "id": "v1.1", "links": [{"href": "http://localhost:9292/v1/", "rel": "self"}]}, {"status": "SUPPORTED", "id": "v1.0", "links": [{"href": "http://localhost:9292/v1/", "rel": "self"}]}]}
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.

Could anybody help me with this one?

unable to ping the vm

Hi,

Although I could create a new vm , I am unable to ping the same.
I have strictly followed the steps and topology provided in the installation guide:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

Also please find the logs of the vm creation as attachment.

Thanks & Best Regards,
Upendra.

metadata_host question

Hi

in control node, nova.conf

metadata_host=100.10.10.51

but in network node
/etc/quantum/l3_agent.ini:

metadata_ip = 192.168.100.51

whether have problem?

Instances are not able to acquire IP via flat DHCP

I followed your "Folsom + Quantum on VLAN with 2 NICs is available through VLAN/2NICs branch" document to deploy OpenStack but my instances are not able to acquire IP via flat DHCP that we have configured as per doc.Neither i'm able to communicate from compute node with instances after assigning static IP.

Now,I request you a brief explanation How we communicate with instances which are associated with "br-int" from compute node.

I am Newbie to Cloud-networking part.So, please do reply to my query.

Thanks.
Kumar M.

br without port??

Hi, I have a little question.

On compute host, is not necessary add a port to br-int?

Can you help me with information about openvswitch and how quantum use it for give connectivity to VMs.

Thanks alot.

Errata

Cinder install section, include package open-iscsi.

NTP install section both control and compute nodes, command: sed -i 's/server ntp.ubuntu.com/server 192.168.100.232' /etc/ntp.conf is not properly constructed and errors. sed -i 's/server ntp.ubuntu.com/server 192.168.100.232/g' /etc/ntp.conf is correct.

IP Forwarding instructions on both compute & controller nodes: Adding "echo 1 > /proc/sys/net/ipv4/ip_forward" would save a reboot.

On the compute node, Keystone credentials should really be added to root .bashrc as you did on the controller node so that the nova-manage service list command you attempt to run in step 11 will work properly.

Step 12 - Your first vm, there's a typo in the router create command. --tenant_id should be --tenant-id

After creating the external network and editing l3_agent.ini, need to add instructions to restart quantum-l3-agent service on controller node.

It's also not clear in Step12 that these commands should really be getting issued from the controller node, especially when you get to for the floating ip area:

ip addr flush dev br-ex
ip addr add 192.168.100.100/28 dev br-ex
ip link set br-ex up

Also, do the above commands need to be put in a startup job or something or is it a one-time event?

Keeping the guide simple and short

Installing OpenStack is great experience but it often comes with multiple situations where you need the help of others to pull it out.

In this context, i wrote this guide to share my knowledge about how to install OS. The feedbacks are great which motivated me to aim at extending this work to cover many features that an OpenStack admin might need or a cloud software developer may encounter.

Yet, extending doen't just mean richer and better but also longer and could get too complicated.

This is where i ask for help and advices. I would like to start a new repository named Tricks&Ideas where we share what we used to pimp our OpenStacks (such as DNS servers, Quantum configurations, linking to SAN storage disks, ...etc) but i am wondering what will be the reaction of my guide's reviewers: would they like it or not ?

Can't wait to hear from you.

Cheers !

update needed - Keystone_Scripts/With Quantum/keystone_basic.sh

When going through your nice guide I've noticed that provided script gives me several errors. After checking with openstack keystone docs I've found out, that when working with tenant id there need to be underscore not a dash (tenant-id -> tenant_id) can you please update it in your guide for others.

Keystone_Scripts/With Quantum/keystone_basic.sh

#!/bin/sh
#
# Keystone basic configuration 

# Mainly inspired by https://github.com/openstack/keystone/blob/master/tools/sample_data.sh

# Modified by Bilel Msekni / Institut Telecom
#
# Support: [email protected]
# License: Apache Software License (ASL) 2.0
#
HOST_IP=localhost
ADMIN_PASSWORD=${ADMIN_PASSWORD:-admin_pass}
SERVICE_PASSWORD=${SERVICE_PASSWORD:-service_pass}
export SERVICE_TOKEN="ADMIN"
export SERVICE_ENDPOINT="http://${HOST_IP}:35357/v2.0"
SERVICE_TENANT_NAME=${SERVICE_TENANT_NAME:-service}

get_id () {
    echo `$@ | awk '/ id / { print $4 }'`
}

# Tenants
ADMIN_TENANT=$(get_id keystone tenant-create --name=admin)
SERVICE_TENANT=$(get_id keystone tenant-create --name=$SERVICE_TENANT_NAME)


# Users
ADMIN_USER=$(get_id keystone user-create --name=admin --pass="$ADMIN_PASSWORD" [email protected])


# Roles
ADMIN_ROLE=$(get_id keystone role-create --name=admin)
KEYSTONEADMIN_ROLE=$(get_id keystone role-create --name=KeystoneAdmin)
KEYSTONESERVICE_ROLE=$(get_id keystone role-create --name=KeystoneServiceAdmin)

# Add Roles to Users in Tenants
keystone user-role-add --user $ADMIN_USER --role $ADMIN_ROLE --tenant_id $ADMIN_TENANT
keystone user-role-add --user $ADMIN_USER --role $KEYSTONEADMIN_ROLE --tenant_id $ADMIN_TENANT
keystone user-role-add --user $ADMIN_USER --role $KEYSTONESERVICE_ROLE --tenant_id $ADMIN_TENANT

# The Member role is used by Horizon and Swift
MEMBER_ROLE=$(get_id keystone role-create --name=Member)

# Configure service users/roles
NOVA_USER=$(get_id keystone user-create --name=nova --pass="$SERVICE_PASSWORD" --tenant_id $SERVICE_TENANT [email protected])
keystone user-role-add --tenant_id $SERVICE_TENANT --user $NOVA_USER --role $ADMIN_ROLE

GLANCE_USER=$(get_id keystone user-create --name=glance --pass="$SERVICE_PASSWORD" --tenant_id $SERVICE_TENANT [email protected])
keystone user-role-add --tenant_id $SERVICE_TENANT --user $GLANCE_USER --role $ADMIN_ROLE

QUANTUM_USER=$(get_id keystone user-create --name=quantum --pass="$SERVICE_PASSWORD" --tenant_id $SERVICE_TENANT [email protected])
keystone user-role-add --tenant_id $SERVICE_TENANT --user $QUANTUM_USER --role $ADMIN_ROLE

CINDER_USER=$(get_id keystone user-create --name=cinder --pass="$SERVICE_PASSWORD" --tenant_id $SERVICE_TENANT [email protected])
keystone user-role-add --tenant_id $SERVICE_TENANT --user $CINDER_USER --role $ADMIN_ROLE```

Unauthorized (401)

Hey,

tanks for this assome walkthrough...
I have the issue that I am not able to login to horizon.
==> /var/log/apache2/error.log <== [Tue Oct 16 17:45:39 2012] [error] \x1b[31;1mUnauthorized: n/a (HTTP 401)\x1b[0m [Tue Oct 16 17:45:39 2012] [error] Traceback (most recent call last): [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/horizon/usage/base.py", line 110, in get_quotas [Tue Oct 16 17:45:39 2012] [error] self.quotas = api.nova.tenant_quota_usages(self.request) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/horizon/utils/memoized.py", line 33, in __call__ [Tue Oct 16 17:45:39 2012] [error] value = self.func(*args) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/horizon/api/nova.py", line 431, in tenant_quota_usages [Tue Oct 16 17:45:39 2012] [error] volumes = volume_list(request) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/horizon/api/nova.py", line 516, in volume_list [Tue Oct 16 17:45:39 2012] [error] return cinderclient(request).volumes.list(search_opts=search_opts) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/cinderclient/v1/volumes.py", line 171, in list [Tue Oct 16 17:45:39 2012] [error] "volumes") [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/cinderclient/base.py", line 63, in _list [Tue Oct 16 17:45:39 2012] [error] resp, body = self.api.client.get(url) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/cinderclient/client.py", line 138, in get [Tue Oct 16 17:45:39 2012] [error] return self._cs_request(url, 'GET', **kwargs) [Tue Oct 16 17:45:39 2012] [error] File "/usr/lib/python2.7/dist-packages/cinderclient/client.py", line 135, in _cs_request [Tue Oct 16 17:45:39 2012] [error] raise ex [Tue Oct 16 17:45:39 2012] [error] Unauthorized: n/a (HTTP 401)

What do I miss?

Cheers
Christian

instances get no IP

Hi,

I have a 3 node setup following this guide

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst

When I start an instance I don't see any ip on it. When I look from horizon, I can see the ip. This is what i see on the instance log.

wget: can't connect to remote host (169.254.169.254): Network is unreachable

Full, log: http://pastebin.com/FQyBFFs1

I have l3 agent and dhcp running on network code.

How do I start to debug this?

Thanks
Paras.

Guide error

Great work! This guide helps a LOT You should accept donations.

In the guide you say:

Create a new user and assign the admin role to it in the new tenant:

keystone user-create --name=user_one --pass=user_one --tenant-id $put_id_of_project_one --email=[email protected]
keystone user-role-add --tenant-id $put_id_of_project_one --user-id $put_id_of_user_one --role-id $put_id_of_member_role

You never say where to get the member role id though ($put_id_of_member_role)

Thanks!
-- Alex