Openstack Horizon Themes Download
Quirino Palomo
To use a custom theme, set AVAILABLE_THEMES in local_settings.py toa list of themes. If you wish to run in a mode similar to legacy Horizon,set AVAILABLE_THEMES with a single tuple, and the theme toggle will notbe available at all through the application to allow user configuration themes.
Both the Dashboard custom variables and Bootstrap variables can be overridden.For a full list of the Dashboard SCSS variables that can be changed,see the variables file atopenstack_dashboard/static/dashboard/scss/_variables.scss.
By default, all of the themes configured by AVAILABLE_THEMES setting arecollected by horizon during the collectstatic process. By default, the themesare collected into the dynamic static/themes directory, but this location canbe customized via the local_settings.py variable: THEME_COLLECTION_DIR
All themes will need to be configured in AVAILABLE_THEMES to allowinheritance. If you wish to inherit from a theme, but not show that themeas a selectable option in the theme picker widget, then simply configure theSELECTABLE_THEMES to exclude the parent theme. SELECTABLE_THEMES mustbe of the same format as AVAILABLE_THEMES. It defaults toAVAILABLE_THEMES if it is not set explicitly.
Any Django template that is used in Horizon can be overridden through a theme.This allows highly customized user experiences to exist within the scope ofdifferent themes. Any template that is overridden must adhere to the samedirectory structure that the extending template expects.
For example, if you wish to customize the sidebar, Horizon expects the templateto live at horizon/_sidebar.html. You would need to duplicate thatdirectory structure under your templates directory, such that your overridewould live at theme_path /templates/horizon/_sidebar.html.
If you need to do more to customize the logo than simply replacing the existingSVG, then you can also override the _brand.html through a custom theme. To usethis technique, simply add a templates/header/_brand.html to the root ofyour custom theme, and add markup directly to the file. For an example of howto do this, seeopenstack_dashboard/themes/material/templates/header/_brand.html.
Both the Dashboard custom variables and Bootstrap variables can be overridden.For a full list of the Dashboard SCSS variables that can be changed, see thevariables file at openstack_dashboard/static/dashboard/scss/_variables.scss.
If you need to do more to customize the logo than simply replacing the existingPNG, then you can also override the _brand.html through a custom theme. To usethis technique, simply add a templates/header/_brand.html to the root ofyour custom theme, and add markup directly to the file. For an example of howto do this, seeopenstack_dashboard/themes/material/templates/header/_brand.html.
Horizon uses icon fonts to represent checkboxes. In order to customizethis, you simply need to override the standard scss. For an example ofthis, see themes/material/static/horizon/components/_checkboxes.scss
The logo also acts as a hyperlink. The default behavior is to redirect tohorizon:user_home. By adding the attribute SITE_BRANDING_LINK withthe desired url target e.g., -company.com inlocal_settings.py, the target of the hyperlink can be changed.
Default Horizon panels are loaded based upon files within the openstack_dashboard/enabled/folder. These files are loaded based upon the filename order, with space left for morefiles to be added. There are some example files available within this folder, with the.example suffix added. Developers and deployers should strive to use this method ofcustomization as much as possible, and support for this is given preference over moreexotic methods such as monkey patching and overrides files.
The OpenStack dashboard for Red Hat OpenStack Platform uses a default theme (RCUE), which is stored inside the horizon container. You can customize the look and feel of the OpenStack dashboard by adding your own theme to the container image and customizing certain dashboard parameters. With this customization, you can modify the following elements:
You must obtain a copy of the horizon container image. You can pull this image either into the undercloud or a separate client system running podman. To pull the horizon container image, run the following command:
To enable your theme in the dashboard container, you must create a file to override the AVAILABLE_THEMES parameter. Create a new file called _12_mytheme_theme.py in the horizon-themes directory and add the following content:
When your custom theme is ready, you can create a new container image that enables and uses your theme. Use a dockerfile to generate a new container image using the original horizon image as a basis. The following is an example of a dockerfile:
Red Hat OpenStack Platform director provides a set of horizon parameters you can modify using environment files. You can also use the ExtraConfig hook to set Puppet hieradata. For example, the default help URL points to -hat-openstack-platform. You can modify this URL with the following environment file content:
Hi I am following the official tutorial of openstack dashboard layout customization here. It says that I need to remove openstack-dashboard-ubuntu-theme. But wouldn't removing this theme before customization will break anything? Also after removing the theme what do I need do...do I need to install some other theme to replace it?
The SUSE OpenStack Cloud Dashboard theme can now be customized. The default SUSE OpenStack Cloud theme is available in the openstack-dashboard-theme-SUSE package. If you want to replace it with a custom theme, you can explore the package contents as an example. When using a custom theme, make sure the resulting package name starts with openstack-dashboard-theme-. Apart from that, go to the horizon barclamp in Crowbar, switch to the Raw view and adjust the site_theme attribute accordingly. For details about the barclamps in Crowbar, see the Deployment Guide using Crowbar.
We have been having a recurrence of this with Q->R and R->S where the openstack-dashboard package removal seems to perhaps remove the custom theme, or move the directory where the custom theme is unpacked?
Run the following on all three units to unpack the theme:
sudo mkdir /usr/share/openstack-dashboard/openstack_dashboard/themes/custom
sudo tar -xf /home/ubuntu/theme.tgz -C /usr/share/openstack-dashboard/openstack_dashboard/themes/custom/
Then re-run the dist-upgrade to allow openstack-dashboard package to complete configuration:
sudo apt-get --assume-yes --option Dpkg::Options::=--force-confnew --option Dpkg::Options::=--force-confdef dist-upgrade
Horizon is based on a Django module called django-openstack. Both the django-openstack module as well as a reference implementation of a fully functional Django site called openstack-dashboard are part of this project. As of the Diablo release, Horizon is now an OpenStack Core project and is a fully supported OpenStack offering.
The OpenStack Dashboard is a web application to control an OpenStackcloud. It connects to OpenStack services such as Nova, Swift, or Keystoneusing the OpenStack REST API just as you would with the command lineclients. Other Packages Related to openstack-dashboard
- depends
- recommends
- suggests
- enhances
- dep:adduser add and remove users and groups
- dep:debconf (>= 0.5) Debian configuration management system or debconf-2.0 virtual package provided by cdebconf, cdebconf-udeb, debconf
- dep:libjs-jquery JavaScript library for dynamic web applications
- dep:libjs-jquery-cookie jQuery cookie plugin
- dep:python3 interactive high-level object-oriented language (default python3 version)
- dep:python3-django-horizon (= 3:14.0.2-3+deb10u3) Django module providing web interaction with OpenStack
- sug:memcached high-performance memory object caching system
- sug:openstack-dashboard-apache web application to control an OpenStack cloud - Apache support Download openstack-dashboard Download for all available architectures ArchitecturePackage SizeInstalled SizeFiles all52.6 kB262.0 kB [list of files] This page is also available in the following languages (How to set the default document language):
Many resource properties have previously been documented as DEPRECATED. 15 of these properties are now flagged as HIDDEN, which means they will no longer be documented, but existing stacks and templates will continue to work after a heat upgrade. The [ _guide/openstack.html Resource Type Reference] should be consulted to determine available resource properties and attributes.
Developed by more than 330 contributors who implemented 185 different features, the OpenStack Folsom release continues the themes of stability and extensibility, while adding significant new features like Networking, Block Storage and Hyper-V support. There was also signficiant progress made with localization efforts, including a new translation framework for user-facing guides and documentation.
760c119bf3