Some deployment methods are using the files delivered by the
installation of packages to configure dashboards.
For example, it's possible to pip install heat-dashboard and
use the use local_settings.d files shipped inside the package
to deploy the heat-dashboard.
When the heat dashboard was not a plugin and included in horizon,
it was usable without having to care about the policy file.
This has changed, as the file is not shipped into horizon by
default, and is not available when pip installing the heat
dashboard directly, unlike the other files (above).
This patch follows the pattern set by murano here [1], to be
able to use the default policy file, shipped with the code,
after a pip install of the heat-dashboard.
[1]: 873fd7ff85/muranodashboard/conf/murano_policy.json
Change-Id: I7e1d74bebc97874c9049f6be33cef27806739b11
To enable translate job correctly, deleted heat-dashboard/locale
directory and updated babel-django.cfg accordingly.
Also fixed tox.ini which included wrong commands for docs build.
Change-Id: Idb7996ded645a8bc8bcb3b7eb08c8754a8492873
Heat relevant contents will be split out
from Horizon in Queens release.
After this splitting out, Heat-Dashboard must have
its own settings in Heat-Dashboard repository.
So this review request includes following.
- Create own settings under local_settings.d
- Add procedure for installing above settings.
- Fix installation procedure according to above changes.
Change-Id: I0b9a9907cb0c02aed70e7c1af3d9d07b0ddeffb6
To slit out Heat support from Horizon, migrate Heat relevant docs from
Horizon repo to Heat Dashboard repo.
Change-Id: Ie0334b8af060a8251a649a49d982086709472190
according to Horizon team's advice.
I've changed installation procedure as follows.
(before changing)
1. copy heat_policy.json from Heat-Dashboard directory
to Horizon directory (same as enable files)
2. add orchestration key to POLICY_FILES settings
(after changing)
1. just point Heat-Dashboard policy file path
from POLICY_FILES settings
Change-Id: Idaf2cbfcb716a9aa4c0f43283526302f062ea0a7
After Heat relevant contents will split out from Horiozon,
I guess 'orchestration' key of POLICY_FILES settings will be
removed also.
So I've add procedure for adding this key
so that user can correctly enable heat_policy.json
Change-Id: I77ae6c6f63f5ae0f21e9aa6d33edca458bb17502
Current installation procedure in README.rst and
doc/source/install/installation_contents.rst does not have
installation process of heat-dashboard itself.
I added above procedure by this review request.
Change-Id: I97f7d114c1f1e978286bd218df558ddf5340d901
In future, Heat relevant files(like GUI, api client, policy files, ...)
will be split out from Horizon repository.
But now this repository does not have Heat policy file so I've copied
it from Horizon latest repository.
This review request also includes following changes.
- Added installation procedure document relates to heat_policy.json.
- Modified plugin.sh to install heat_policy.json.
Change-Id: I8dd386e392eb4467b03efd68c7959371d4b9576d
