Ask Your Question

How to enable Heat-ui on Havana

asked 2013-11-05 07:15:19 -0600

simone.tiraboschi gravatar image

Hello, as far as I can read in the Havana release notes, Horizon should include a kind on panel to launch heat stacks.

Unfortunately I'm not able to configure it neither to find any sort of documentation about how to enable it.

I already tried to add to put

     'dashboards': ('project', 'admin', 'settings', 'heat' ),




in my /etc/openstack-dashboard/local_settings configuration file but I can only get an exception: Dashboard with slug "heat" is not registered.

Does anybody know how can I enable it?

I'm working on Havana 2013.2 on Centos 6.4 with RDO.

ciao, Simone

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-11-05 07:39:16 -0600

I have got it enabled by default on 6.4 Havana from packages. There is my /etc/openstack-dashboard/local_settings

import os

from django.utils.translation import ugettext_lazy as _

from openstack_dashboard import exceptions

DEBUG = True

# Required for Django 1.5.
# If horizon is running in production (DEBUG is False), set this
# with the list of host/domain names that the application can serve.
# For more information see:
ALLOWED_HOSTS = ['', 'localhost']

# Set SSL proxy settings:
# For Django 1.4+ pass this header from the proxy after terminating the SSL,
# and don't forget to strip it from the client's request.
# For more information see:

# If Horizon is being served through SSL, then uncomment the following two
# settings to better secure the cookies from security exploits

# Overrides for OpenStack API versions. Use this setting to force the
# OpenStack dashboard to use a specfic API version for a given service API.
# NOTE: The version should be formatted as it appears in the URL for the
# service API. For example, The identity service APIs have inconsistent
# use of the decimal point, so valid options would be "2.0" or "3".
#     "identity": 3
# }

# Set this to True if running on multi-domain model. When this is enabled, it
# will require user to enter the Domain name in addition to username for login.

# Overrides the default domain used when running on single-domain model
# with Keystone V3. All entities will be created in the default domain.

# Set Console type:
# valid options would be "AUTO", "VNC" or "SPICE"

# Default OpenStack Dashboard configuration.
    'dashboards': ('project', 'admin', 'settings',),
    'default_dashboard': 'project',
    'user_home': 'openstack_dashboard.views.get_user_home',
    'ajax_queue_limit': 10,
    'auto_fade_alerts': {
        'delay': 3000,
        'fade_duration': 1500,
        'types': ['alert-success', 'alert-info']
    'help_url': "",
    'exceptions': {'recoverable': exceptions.RECOVERABLE,
                   'not_found': exceptions.NOT_FOUND,
                   'unauthorized': exceptions.UNAUTHORIZED},

# Specify a regular expression to validate user passwords.
# HORIZON_CONFIG["password_validator"] = {
#     "regex": '.*',
#     "help_text": _("Your password does not meet the requirements.")
# }

# Disable simplified floating IP address management for deployments with
# multiple floating IP pools or complex network requirements.
# HORIZON_CONFIG["simple_ip_management"] = False

# Turn off browser autocompletion for the login form if so desired.
# HORIZON_CONFIG["password_autocomplete"] = "off"

# Set custom secret key:
# You can either set it to a specific value or you can let horizion generate a
# default secret key that is unique on this machine, e.i. regardless of the
# amount of Python WSGI workers (if used behind Apache+mod_wsgi): However, there
# may be situations where you would want to set this explicitly, e.g. when
# multiple dashboard instances are distributed on different machines (usually
# behind a load-balancer). Either you have to make sure that a session gets all
# requests routed to the same dashboard instance or you set the same SECRET_KEY
# for all of them.
from horizon.utils import secret_key
LOCAL_PATH = '/var/lib/openstack-dashboard'
SECRET_KEY = secret_key.generate_or_read_from_file(os.path.join(LOCAL_PATH, '.secret_key_store'))

# We recommend ...
edit flag offensive delete link more


It's not so different from mine. I'm looking for a completely new heat panel as the one I can see in this screencast: Are you in this situations?

simone.tiraboschi gravatar imagesimone.tiraboschi ( 2013-11-05 08:19:20 -0600 )edit

I got my "stacks" menu right in place. Do you have heat endpoint configured?

laboshinl gravatar imagelaboshinl ( 2013-11-05 08:33:05 -0600 )edit

I think that my endpoint should be ok. I can use heat from CLI without problems. Now I can only see a new sub-menu called Orchestration-Stacks under the Project dashboard, I think I should also have a new dashboard called Heat where I can also edit templates and create new ones.

simone.tiraboschi gravatar imagesimone.tiraboschi ( 2013-11-05 08:57:26 -0600 )edit

You should only have this. The dashboard extension "thermal" was created by enthusiast and availble on github. Im not shure it is compatible with Havana

laboshinl gravatar imagelaboshinl ( 2013-11-05 09:08:51 -0600 )edit

So I'll have, thanks.

simone.tiraboschi gravatar imagesimone.tiraboschi ( 2013-11-05 09:35:21 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-11-05 07:15:19 -0600

Seen: 1,586 times

Last updated: Nov 05 '13