Since version 10 (Buster) the package openstack-dashboard installs its
files to different directories than it used to. With version 11
(Bullseye) just about to reach stable status, it might be time to update
the defaults - for Debian proper anyway, since judging from the contents
of relevant Ubuntu 21.04 packages that distro has decided to go their
own way here.
Note that this also changes the handling of some of the paths for RHEL
- there used to be two hard-coded paths in the recipes/horizon.rb which
still work under RHEL and Ubuntu but not under modern Debian, requiring
a switch to attribute-defined paths.
PS. The permission change on dash_state_dir is part of this too,
since without o+x Apache complains
access to /static/foo denied (filesystem path '/var/lib/openstack-dashboard/static') because search permissions are missing on a component of the path
whenever any static dashboard content is to be retrieved.
Signed-off-by: Marek Szuba <m.szuba@gsi.de>
Change-Id: I345b4894f1243db77856303d97538914dc6cf9be
Also pull bind cookbook from git to fix version pinning issues.
Change-Id: Ia90e7cc967a8ac300a3dec984f6e89b3feb122b3
Signed-off-by: Lance Albertson <lance@osuosl.org>
RHEL finally includes a proper RPM package for the horizon LBaaS plugin in
Stein. This removes the dependency on poise.
Change-Id: If3d2729c013125bd75441c50fc7de5d5cc9c3221
- Cookstyle fixes
- Refactor Berksfile to use groups so we can exclude integration testing
cookbooks
- Update documentation
- Cleanup line wraps
- Update delivery configuration to exclude integration cookbooks
- Fix ChefSpec output.
- Add missing ChefSpec tests
- Switch package installations to send packages as arrays instead of individual
package resources. This generally speeds up chef runs.
- Cleanup array syntax using %w() instead of []
- Remove FWaaS recipe as it's been unmaintained upstream.
Depends-On: https://review.opendev.org/701027
Depends-On: https://review.opendev.org/706101
Depends-On: https://review.opendev.org/706151
Change-Id: Ie3b65b701235bae65a1797d63d6a55dd6fc9958e
This brings us up to date with the latest apache2 cookbook which
included a major refactor in 6.0.0 removing all of the definitions and
recipe with proper resources. Instead of using the apache2_default_site
resource, directly use a template and then enable the config file using
the apache2_site resource. This gives us the most flexibility.
Additional fixes:
- Remove or replace references to node['apache'] attributes
- Install mod_wsgi as a package on RHEL since there is no built-in
resource for it.
- Don't set SELinux to permissive on RHEL (I tested this works properly
with it set to enforcing).
- Remove hack for restarting apache.
- Convert web_app to template and subscribe to restarting apache.
- Remove resources to restore SELinux contexts since this taken care of
by Chef now automatically.
- Include additional cookbooks in Berksfile required for CI
Depends-On: https://review.opendev.org/702772
Depends-On: https://review.opendev.org/701824
Change-Id: Ib82595c27f03a7b456d5d5bfecc466f5ac199a5c
This updates all references of let(:chef_run) to cached(:chef_run) to
speed up tests. By doing this, we have to create a new cached(:chef_run)
block whenever we need to adjust node attributes for testing.
Speed was improved from 56 minutes 34 seconds to 8 minutes 43 seconds
Change-Id: Ic7cf02200cf9d09beb66f6aa0d27cadffa65f7c9
- Replace git.openstack.org with opendev.org
- Update some documentation
- Move README.md to README.rst for better rendering
- Drop obsolete bootstrap.sh script
- Drop obsolete openstack-identity::default recipe
Change-Id: If98eef94a31bd0f082a869dc2278d21abcf47b59
The following is included in django.wsgi:
```
Use of this 'djano.wsgi' file has been deprecated since the Rocky
release in favor of 'wsgi.py' in the 'openstack_dashboard' module. This
file is a legacy naming from before Django 1.4 and an importable
'wsgi.py' is now the default. This file will be removed in the T release
cycle.
```
Change-Id: Ic188e6ec87cb59d9311787fa36defd193116c2b0
Signed-off-by: Lance Albertson <lance@osuosl.org>
Python2.7 is going EOL soon, let us deploy python3 for Rocky from the
start, so we avoid having to switch later.
Add a workaround because the apache2::mod_wsgi recipe hardcodes python2 deployment.
Install neutron-*aas-dashboard plugins as distro packages and not from pypi.
Depends-On: https://review.opendev.org/682918
Change-Id: Ia994665c69b64725e7e5369ceb93ee9608620d2b
The other apache2 site config files that are created via the ``web_app``
resource from the apache cookbook use a node attribute to determine the
the unix group that the template should belong to. Use the same
attribute in our local template so that all ownerships are consistent.
Change-Id: I4933f9dd5293b30c5b2597055debc2c9c659aca2
- Use role "member" for keystone_default_role instead of "_member_"
- Package "openstack-dashboard-ubuntu-theme" doesn't exist anymore
- Drop attributes that aren't used anymore
Change-Id: I5c6bc5b64d65e89ef599959015865661f92ee6e3
The node['openstack']['api']['auth']['version'] was deprecated and should no
longer be used. Default to version 3 for keystone since that's currently what's
supported.
Change-Id: I655e19e31f026be4fe92cbfbbf9d41f37cc6208d
Signed-off-by: Lance Albertson <lance@osuosl.org>
In Chef 13+, resource duplication behaves differently. By centralizing
python_runtime to openstack-common, the resource executes once in a
given Chef run, instead of attempting to reinstall python multiple
times.
Change-Id: I2e17d655c86fac63e02aaadf5321bc95e2c7aa0b
* remove postgres references
* update lbaas url to stable/queens
* update logging handler to reflect the current state of things
Change-Id: Ie298fec4dc1ed35119ffe844f356d1c72cfaa6f8
* use git.openstack.org instead of github for berks dependency
resolution
Depends-On: https://review.openstack.org/549345
Change-Id: I8e129e0716b647422773949711acefc5c2df5b48
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I2909f09759e58817848d76f7545ac5a3df8bbdd2
- there was a bug in the 'misc-section'
when value is a boolean it would've been printed in ticks.
In Python boolean is treated as Reference, this means it is
written uppercase
Change-Id: Idc03f2bd1f7ee519e404e5a30711a81493acf522
- python-neutron-lbaas-dashboard version was outdated
updated to latest stable/pike release version
Change-Id: I103e9747439841063f1a926ef9d7883287f63999