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: I2d7566a35b532afdf538d7c0a5fa4095d0bc899b
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: I955d004865fd24c999ab68a15c12e934532c2565
Story: #2002586
Task: #24319
In case where /etc/network/interfaces already contains a similar
line, it is superseeded.
Change-Id: I38f244d093e002f8bc90412c1eacd254ffe31514
(cherry picked from commit 42d14389b0)
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Icc8300de4846d407a4090fa24e8ed2bb5f5acfcb
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: I9b52f68cee57732fb3f664d0bf67b2508ceae061
these tools are not stable and still being developed in master
Change-Id: I47771027550ede7ce68f0bdd54701a844284eca9
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
cinder-manage service list does not output a usable, full, hostname;
just the short hostname is output. To fix this we need to query the
database directly.
We also change the behavior of this operation to drop all services. We
do this at the recommendation of upstream cinder. This is safe because
all cinder services are stopped and the services will re-register when
restarted.
Related-Bug: #1712372
Change-Id: I6d845165ec22d4c2aeece0636a550e0b57050c22
When using environment variables to setup a proxy, it checks whether
global_environment_variables (for permanent proxy) or
deployment_environment_variables (for playbooks only) is in use and
sets up matching user_variables for OSA. Previously, it only setup
global environment variables.
Added | bool filters as suggested in review.
Change-Id: I6554cd28f817ab0d128a1a469a6007b043851c07
more headers were needed, also, revert the kilo release change.
eol-kilo has swift in upper-constraints, which causes problems for venv
building, it was removed from future releases for this exactly this
reason.
Change-Id: I1f8c8ea4681ab63dd67851235f405d1cbd478eae
The comment on the bug in setuptools was fixed a while ago upstream and
evrardjp also mentioned that comment could be removed. Branches other
than newton have an EOL release, so change to use those.
Change-Id: I80cf1fc929e86c3498760ad4b342964c7f82ea5f
In some cases a deployer may want to make a running backup of all
containers within an environment. This playbook will index all
containers and arhive them in the /opt/archives directory on the
physical host the container is running on.
Change-Id: I94880d4c00f89d5c678a1903f35120917561aa51
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
add tmux configuration on infra1 to raise up the history-limit to
20000, which helps troubleshooting the deployment.
Change-Id: I075364868c0b74a297ad6b8ca7dbfec71ca91c27
Adding even more dynamic user config options and a compute preseed.
Change-Id: Ieccbd61a45a77b7dff9e228fc6fdaf92df852abb
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
During leapfrog all containers are deleted, and ceph containers
are no exception.
This adds exceptions into the process:
- One on the generic container delete;
- One on the Juno container delete of any remnant container.
Change-Id: I34812f4472594998f3e40b4a5cb650e396a80421
* added ip alias for interfaces
* Update settings and improve vm performance
* Change the VG name in VMs. The VG name was changed so that the volume
which is being used by VMs can be mounted on a physical host, and not
conflict, with standard volume group naming. This is usful when a VM
is DOA and a deployer wants to disect the instance.
Change-Id: If4d10165fe08f82400772ca88f8490b01bad5cf8
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
HAProxy should not have an init that loads conf.d files, like it
was done on K, and removed in N, during the haproxy installation.
Else the installation of the package will fail, because it will
load the conf.d files.
Change-Id: I345089cc3493b90c1c4fbd2d47c51f83c65c94f4
In case of an included playbook fail (let's say the repo playbook),
a restart of the leap script will restart the whole upper level
playbook (because it hasn't been marked as successful yet), and
therefore will re-run all the included playbooks again.
This change will make sure the process restarts exactly where it
failed.
Change-Id: I5790f3bdb57d6f17ba32346a00d096ead15babf3
RPC is using r11 and 11 for kilo, same for upper branches.
We should be more lenient to the version allowed, whether it's
starting with a r or not, as long as the major version is the
same number.
Change-Id: I42053681fdc5e0b2c16060d8a51b4a620569f38c
If we interrupt the process in unarchive, we'll have a broken
idempotency state: The leapfrog process will run again the venv
prep, the synchronize will be unchanged, and the unarchive
rewire will never run.
Change-Id: I8e91ef39d4ecbc9ff5a6a4a73cd0ce4679d6ecf0
If a user is using a REDEPLOY_EXTRA_SCRIPT to migrate additional
variables before re-deploying, it's maybe best to re-run all the
playbooks that happen in a deploy. All the playbooks are already
there, excepted the openstack-hosts-setup, so we add it here.
Change-Id: I64bade46cb1ece6f21ed42c7622bd6e39f2420fe