This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I3f8ed2ad7e1b2485278afe2f431ccdcfce4005d4
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I35e3d136ecb4719c65620d6aa3208830a6053cd9
Story: #2002586
Task: #24319
In stable/pike release, all git install branches are pointing to master
but should be pointing to stable/pike.
Change-Id: I61c3ca4795495307db1597a5c41e9edc6d5dc327
Ansible's Jinja2 templater reporting an error when encounters with
non-ascii characters:
An exception occurred during task execution.
To see the full traceback, use -vvv. The error was: UnicodeDecodeError:
'ascii' codec can't decode byte 0xe2 in position 278:
ordinal not in range(128)
fatal: [infra1_monasca_container-ba51ad87]: FAILED! =>
{"failed": true,
"msg": "Unexpected failure during module execution.", "stdout": ""}
Change-Id: I4021b46dfe30cd51656dd4c7c68edd2f04b8f6fd
(cherry picked from commit 4774c28f71)
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I6a31da768005238e624e2be3d14a61d5b4c7d1d7
Given that the functional build for this repo
rarely passes and the repo itself is only
maintained by those who use it, we can set the
functional test to non-voting in order to allow
general pattern changes to be implemented
without delay.
This does mean that reviewers applying functional
changes will have to be disciplined about checking
the results, but I think that is OK in this case.
Depends-On: https://review.openstack.org/556280
Change-Id: I1a236b88a8c80d82f162a92f6cdfeb9368b6eea7
(cherry picked from commit f3713f98f5)
Use stable/pike as the default project and requirements
install branch among monasca services.
Change-Id: I1dfcef1ccf0386d458e3cef08312c28a35ec1d1f
Signed-off-by: kaiokassiano <kaiokmo@lsd.ufcg.edu.br>
We need to add openstack ansible information in the role
metadata to be able to track role maturity. With it,
we can create a role maturity table and take decisions about
role deprecations.
The role maturity state is "incubated", conformly to our
role maturity guidelines. This role work has been started in
ocata and can therefore still have the incubated status in Pike.
Change-Id: Ia2ca7803115547931b452eee778afd02d3e54137
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: I73558ce52761381a3b61ff50f3394f2f1e50fa8f
This change fixes monasca modules to work with the latest version
of monascaclient.
Other minor changes:
- Use cryptography instead of pycrypto
- Removed duplicate variable for monasca_api_port
- Added static paths for dashboards
Change-Id: Ib4fe27c276413bb2e1e5da3fe532d824745c5b99
In order to do a developer mode that allows installation of packages
from local file, which take precedence over the developer_mode
constraints, we need to allow the order of the constraints to be
changed.
This patch adds a "pip_install_developer_constraints" var which is used
to set the developer mode constraints. By default this will leave the
same behaviour but will allow additional constraints to be added, or the
developermode constraints file to be overriden altogether.
Change-Id: I9fc7e0d9be83af274bb7cd02fff7010d58e908f1
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: I14aee62cd006c3a55758d965a9572c7431e05778
This patch refactors the whole monasca role by bringing consistency
with the other openstack-ansible roles. Main changes include:
- Install services on its specific cointainer;
- monasca-thresh, monasca-notification and monasca-persister was
not being installed/configured, now it is;
- Tempest tests are ran for the whole monasca-api;
- The service should be fully functional;
- Added documentation.
The extras directory contains the changes necessary to openstack-
ansible to setup monasca.
Change-Id: Ib53d4311c4b4aa722c7cdf7b18632e23b8639a56
Currently the role tests use whatever versions of pip,
setuptools and wheel are already installed on the host.
When a version of these tools changes it often causes
problems for our testing.
This will ensure that we use a known good set of pins
which is maintained in the general SHA bumping process.
Change-Id: I26067405d4acc93da9a74cabfd05b11d5ee6aa5b
Consolidate distro package install tasks into a
single task using the package module and pass
the package list into the name instead of using
a with_items loop.
The minimum Ansible version is raised to 2.2 due to a
known bug [1] in Ansible's apt module which does not
update the cache properly if the cache update and the
install are combined in a single task.
[1] https://github.com/ansible/ansible-modules-core/issues/1497
Change-Id: I5d87e5e5d11bd1dcffb6a6187733f6d8e4e72fbf
We use an SSH bastion host which we do our deployment through. The
deployment host doesn't have direct access to the same network as the
host. As a result the venv local checksum lookup fails.
I have described this here:
https://bugs.launchpad.net/openstack-ansible/+bug/1689283
This is a simple fix for this problem, assuming everything is good it
will need repeating in multiple places in the code base.
Change-Id: I240605a8cd76b6ee2dfebde8eb47d577c4f93c95
When executing the tests repo clone in OpenStack-CI,
use zuul-cloner instead of git to enable cross-repo
testing. This ensures that if a dependent patch from
the tests repo is noted using 'Depends-On: <change-id>'
in the commit message, that patch will be included.
Depends-On: Idce7abebf32f24c356a27e099fbca954d917402b
Depends-On: I5da7802d61d2ab6b03908138e3a3ed2db22e3d29
Change-Id: I2fff63afb27266c2ade1ab70d86a423cc5235f21
The systemd unit 'TimeoutSec' value which controls the time
between sending a SIGTERM signal and a SIGKILL signal when
stopping or restarting the service has been reduced from 300
seconds to 120 seconds. This provides 2 minutes for long-lived
sessions to drain while preventing new ones from starting
before a restart or a stop.
The 'RestartSec' value which controls the time between the
service stop and start when restarting has been reduced from
150 seconds to 2 seconds to make the restart happen faster.
These values can be adjusted by using the *_init_config_overrides
variables which use the config_template task to change template
defaults.
Change-Id: Ie14d80dd4134bd7bb9cd5467503e634fb5bd7b9d
Add 'become' and root 'user' options to the playbook instead of using
'ansible_become' through an inventory variable.
Change-Id: Id5018a0cf8f0190655cd6a6b0a342e7918c29dd0
This creates a specific slice which all OpenStack services will operate
from. By creating an independent slice these components will be governed
away from the system slice allowing us to better optimise resource
consumption.
See the following for more information on slices:
* https://www.freedesktop.org/software/systemd/man/systemd.slice.html
See for following for more information on resource controls:
* https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html
Tools like ``systemd-cgtop`` and ``systemd-cgls`` will now give us
insight into specific processes, process groups, and resouce consumption
in ways that we've not had access to before. To enable some of this reporting
the accounting options have been added to the [Service] section of the unit
file.
Change-Id: I619ab58574eedece7e00e323f91aeaec4c5b5a6e
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
OpenStack Proposal Bot