Running horizon/dashboard from git (round 2)

Cole Robinson crobinso at
Fri Jan 13 18:00:36 UTC 2012

So I got horizon working from git last week. Here's steps if anyone wants to
give it a spin. This uses nova, glance, and keystone from get, so a
prerequisite here is that no packaged versions are already running.

I'm not sure if running all this from git is a requirement or not, but since
horizon won't likely ever be packaged for f16 I figured I'd try and use the
code that is closest to what horizon will eventually be packaged against.

(and now that I try and reproduce the steps, I'm actually getting some horizon
errors. Seems to be causde by some change in nova in the past week, see end of
the mail for details.)

Again, as a precursor, set selinux to permissive and disable the firewall :)

# Get keystone from git and run it
git clone git://
cd keystone
python tools/
(optionally enable 'debug' and 'verbose' in ./etc/keystone.conf)

# Set up keystone configuration (doesn't require daemon running)
sudo bin/keystone-manage database sync

# Tenants
sudo bin/keystone-manage tenant add admin
sudo bin/keystone-manage tenant add demo

# Users
sudo bin/keystone-manage user add admin admin
sudo bin/keystone-manage user add demo admin

# Roles
sudo bin/keystone-manage role add Admin
sudo bin/keystone-manage role add Member
sudo bin/keystone-manage role grant Admin admin admin
sudo bin/keystone-manage role grant Member demo demo
sudo bin/keystone-manage role grant Admin admin demo
sudo bin/keystone-manage role grant Admin admin

# Services
sudo bin/keystone-manage service add nova compute "Nova Compute Service"
sudo bin/keystone-manage service add glance image "Glance Image Service"
sudo bin/keystone-manage service add keystone identity "Keystone Identity Service"

# endpointTemplates
sudo bin/keystone-manage endpointTemplates add RegionOne \
    nova \ \ \ \
    1 1
sudo bin/keystone-manage endpointTemplates add RegionOne \
    glance \ \ \ \
    1 1
sudo bin/keystone-manage endpointTemplates add RegionOne \
    keystone \ \ \ \
    1 1

# Tokens
sudo bin/keystone-manage token add 999888777666 admin admin 2015-02-05T00:00

# Run the daemon
sudo ./tools/ bin/keystone --config-file etc/keystone.conf

# Now let's do glance
git clone git://
cd glance
python tools/
enable the line after 'NOTE: use the following pipeline for keystone'

# Run glance
sudo ./tools/ bin/glance-api --config-file etc/glance-api.conf
sudo ./tools/ bin/glance-registry --config-file

# Clone devstack, we are going to need some files from here
git clone git://

# Run nova from git
git clone git://
cd nova
python tools/

# Set up nova keystone integration
cp etc/nova/api-paste.ini .
cat ../devstack/files/nova-api-paste.ini >> api-paste.ini
sed -i -e "s/%SERVICE_TOKEN%/999888777666/" api-paste.ini

# Have nova use openstackx admin API plugin, required for a lot of
# horizon functionality
git clone git://
ln -s openstackx/extensions extensions

# This will be where our nova instance stores state
mkdir -p /tmp/nova-local/instances

# Make a local nova.conf with required changes. Drop it in the top level
# 'nova' dir and the daemons will use it automatically. This is basically
# the f16 nova.conf with the state directories change to /tmp/nova-local
# and some added bits to use the openstackx extension

$ cat nova.conf

# Set up the nova db
sudo ./tools/ bin/nova-manage db sync

# Run all the nova services (requires many different terminal tabs :) )
sudo ./tools/ bin/nova-api
sudo ./tools/ bin/nova-network
sudo ./tools/ bin/nova-objectstore
sudo ./tools/ bin/nova-compute
sudo ./tools/ bin/nova-scheduler
sudo ./tools/ bin/nova-volume

# At this point, go through the openstack F16 quickstart to setup a VM for
# this nova instance

# Finally lets try horizon
git clone git://
cd horizon
python ./tools/
cp openstack-dashboard/local/
set QUANTUM_ENABLED=False in openstack-dashboard/local/
./tools/ python openstack-dashboard/ runserver:9000

firefox localhost:9000
login with admin:admin

And that should work! ... Or at least it did, as of nova commit
8b79dae67ca2686780d3e3b5863d0578264e92a5 on Jan 4. However with current up to
date nova I'm getting errors like:

Error: Unable to get usage info: Malformed request url

in horizon. There is a recent nova bug filed with a similar error but I'm not
sure if it's the issue I'm currently hitting:


More information about the cloud mailing list