Due to Python's GIL [1], we can't use multiple threads for running
OpenStack services without a performance penalty, since the execution
ends up serialized, which defeats the purpose.
Instead, we should use several processes, since this approach doesn't
have this limitation.
[1] https://wiki.python.org/moin/GlobalInterpreterLock
Change-Id: I18c1e796e43a168042900b8202ad3ce8488d3908
This allows the setting of the error and access file logs, as well as
the access log format. This was done in a similar fashion as one can
configure these ones in the keystone wsgi manifest.
Change-Id: I4d82b2d15ae597b8cd2018b6d5c58e9959971daf
Keystone v2 api's are removed in [1], so it's required
to set user_domain_name and project_domain_name otherwise
all requests fallbacks to keystone v2.0 and fails.
[1] https://review.openstack.org/#/c/499783/
Change-Id: Id3737874408887900e1d8b6b87758f64469892b0
The revocation_cache_time is deprecated for removel because of PKI
token format is no longer supported.
Update warning message and add a release note.
Change-Id: Ib7caf25e92ebc2dc11ddc3b952da2f2c9ff616cb
Closes-Bug: #1717144
Leave the version fields blank, since the release notes document
applies to all versions.
That will avoid manual changes in the future like we did until now.
Change-Id: Iee9c3f171ae6e383b3790c69512ba854ace16357
After releasing Pike M3, we need to bump the metadata version
information for the next release with a -dev.
Change-Id: I2252bf5f5f41d70d9078a39196000219a01919f1
The unit tests were broken by a change to openstacklib
Id09c3358c5843510e6a2a8c0e2d4aeb3607e098b which renamed some of the
resources in the openstacklib classes. The problem is that our tests in
this module should not have been testing what occurs within openstacklib
so this fix updates the tests to only check what we are doing within
this module.
Change-Id: Ie985dc8e66d08f7fa5e489888ba8305acafcf876
Depends-On: I9d535ab38afea852559df2b3073bd4b74a2a3947
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: I324be58b3725fa980e28b89d92c91bc51ed5e685
Like we do in other modules, include zaqar::policy class in
zaqar::server so users can define policies without taking care of the
class.
Change-Id: I9f549f11bd4e939ad41ff77c51dd2f32338621c8
Pin reno version to reno!=2.0.0,!=2.3.1,>=1.8.0
Pin sphinx version to sphinx!=1.6.1,>=1.5.1
reno=2.3.1 and sphinx=1.6.1 break releasenotes and doc tests.
Change-Id: I0c76538a0ae3c198636f9fcd20c58d69cd06bee5
We're coming up on the Pike M2 release and we need to prepare the
metadata.json and reno configuration for the release.
Change-Id: Ib2c65d09100ab1ead52edf7c0f93126fb6c01c2a
Update the tox configuration to pull in the openstack
upper-constraints.txt when running releasenotes. This will
fix the releasenotes job that is currently failing due to
a new version of sphinx. Additionally this change includes
updates from puppet-modulesync-configs.
Change-Id: I2692646f2f078a8040625375d69b2c3af98d8a9e
After releasing Pike M1, we need to bump the metadata version
information for the next release with a -dev.
Change-Id: I7ed9782f9598ed1b427102aaf7ea2062168a04de
