- Who we are
- What we know
- What we've created
- Hints and Kinks
- Checking Corosync cluster membership
- Configuring radosgw to behave like Amazon S3
- Downgrading to DRBD 8.3
- Fencing in Libvirt/KVM virtualized cluster nodes
- Fencing in VMware virtualized Pacemaker nodes
- GFS2 in Pacemaker (Debian/Ubuntu)
- Interleaving in Pacemaker clones
- Maintenance in active Pacemaker clusters
- Managing cron jobs with Pacemaker
- Mandatory and advisory ordering in Pacemaker
- Migrating virtual machines from block-based storage to RADOS/Ceph
- Network connectivity check in Pacemaker
- OCFS2 in Pacemaker (Debian/Ubuntu)
- Solid-state drives and Ceph OSD journals
- Solve a DRBD split-brain in 4 steps
- Testing Pacemaker clusters
- Totem "Retransmit List" in Corosync
- Turning Ceph RBD Images into SAN Storage Devices
- Which OSD stores a specific RADOS object?
- Presentations
- Ceph Tutorial (LCA 2013)
- Ceph: The Storage Stack for OpenStack (OpenStack Israel 2013)
- Die eigene Cloud mit OpenStack Essex (German, LinuxTag 2012)
- Fencing (LCE 2011)
- GlusterFS in HA Clusters (LCEU 2012)
- GlusterFS und Ceph (German, CeBIT 2012)
- Hands-On With Ceph (LCEU 2012)
- High Availability Update (OpenStack Summit Fall 2012)
- High Availability in OpenStack (CloudOpen 2012)
- High Availability in OpenStack (OpenStack Conference Spring 2012)
- Highly Available Cloud: Pacemaker integration with OpenStack (OSCON 2012)
- Mit OpenStack zur eigenen Cloud (German, CLT 2012)
- Mit OpenStack zur eigenen Cloud (German, OSDC 2012)
- More Reliable, More Resilient, More Redundant (OpenStack Summit April 2013)
- MySQL HA Deep Dive (MySQL Conference 2012)
- MySQL High Availability Deep Dive (PLUK 2012)
- MySQL High Availability Sprint (PLUK 2011)
- OpenStack Essex im Praxistest (German, Linuxwochen Wien 2012)
- OpenStack High Availability Update (Grizzly and Havana)
- Roll Your Own Cloud (LCA 2011)
- Storage Replication in HPHA (LCA 2012)
- Zen of Pacemaker (LCA 2012)
- hastexo in 100 Seconds
- Technical documentation
- News releases
- Hints and Kinks
- What we do
- What we charge
- What others say
Step 7: The OpenStack Dashboard
Submitted by martin on Fri, 2012-03-23 22:39
We can use Nova to start and stop virtual machines now, but up to this point, we can only do it on the command line. That's not good, because typically, we'll want users without high-level administrator skills to be able to start new VMs. There's a solution for this on the OpenStack ecosystem called Dashboard, codename Horizon. Horizon is OpenStack's main configuration interface. It's django-based.
Let's get going with it:
apt-get install apache2 libapache2-mod-wsgi openstack-dashboard
Note: Make sure to install at least the version 2012.1-0ubuntu6 of the openstack-dashboard package, as it contains some changes important for the dashboard to work properly.
Then, open /etc/openstack-dashboard/local_settings.py in an editor. Go to the line starting with CACHE_BACKEND and make sure it looks like this:
CACHE_BACKEND = 'memcached://127.0.0.1:11211/'
Now restart Apache with
service apache2 restart
After this, point your webbrowser to the Nova machine's IP address and you should see the OpenStack Dashboard login prompt. Login with admin and the password you specified. That's it - you're in!


Comments
login error
what the default password? and login
vnc console not responding to keyboard input
I am able to connect to Vnc console .. but its not responding to my keyboard input.. only mouse is working.
should i make any entry in nova.conf so that keyboard input works..
Login Error
I used admin and password hastexo for the configure and recive in the dashboard login error user our password
Getting "Internal Server Error"
After dashboard login in the Projects tab "Instances and Volumes" link is showing
Internal Server Error
An unexpected error occurred while processing your request. Please try your request again.
Same with Images and Snapshots.
Where am I going wrong. while volumes are showing up in hybridfox and also I am able to see the instances in Admin panel of Dashboard
VNC not working
Hi,
When I try to use VNC, it doesn'd work. After a while it says: "Error: Unable to get VNC console for instance "b89ba58f-2dc2-4bcb-a81d-cca8bd71791d"
I did reinstall everything from the beginning, but no luck so far. Has anyone had the same problem?
Regards,
HD
I'll update the howto to fix
I'll update the howto to fix this issue. Meanwhile, here's how you do it: Make sure you've got the "novnc" package installed and make sure that "novnc" is started; also make sure that nova.conf contains these entries:
--novnc_enabled=true
--novncproxy_base_url=http://10.42.0.6:6080/vnc_auto.html
--vncserver_proxyclient_address=10.42.0.6
--vncserver_listen=10.42.0.6
10.42.0.6 must be replaced with your actual IP, of couse. After doing these changes to nova.conf, restart all nova services and log in into the Dashboard again. VNC should now be working.