This is a partial revert of 05c16e2e that removes special casing around
the openstack-health/openstack_health repo.
Change-Id: I832f1b764a34c128d737a467fa568cc064226c5a
This used to live in puppet-phabricator but as it has nothing to
do with the puppet module, it is being moved here.
Change-Id: I17d7cbcd3f7bb0147305bcd1d2976dd7c409fec8
Implements: spec maniphest migration
This commit adds the puppet config for running an openstack-health
api instance. It'll use the subunit2sql trove db node as a data
source. The puppet-openstack-health module is incorrectly named which
is causing issues, a workaround to rename the repo is added to
install_modules.sh. This is a temporary measure until the gerrit
rename is completed. There is also a workaround in the apply test.
Change-Id: I7e6d9664d087e7bdc21d92624991d0d5f86c0c99
Currently, all hiera calls need to have default values in order for the
apply test to work. This is done by using sed to replace the hiera call
with the default value in the call, i.e. 'hiera("foo", "bar")' is
replaced with '"bar"'.
This adds another sed command that replaces a hiera call that has no
default value specified with the name of the key appended with
NoDefault, i.e. 'hiera("foo")' will become '"fooNoDefault"'.
By making the hiera default values optional, we no longer need to pass
in a default value to every hiera call, and so we can remove the
placeholder XXX that were previously needed by the apply tests but not
by puppet itself.
Change-Id: Ibdeb0c2e49245ea05116e8043936d5b012f46666
In I54db78b028017500b58693ec717c23eaf6a220b6 I added some handy values
that are intendend to go into public log files to help you establish
when an image-build has started or stopped (for example, [1] is
currently ~300MiB of looping build log data and it's really hard to
pick out where things are going wrong).
The problem is, I put them in at DEBUG level and the image loggers are
only set to INFO level. So the messages aren't making it into the
public logfiles as hoped, and thus not available to help people
diagnose issues with their builds.
I think the best idea is to turn these up to DEBUG level to capture
these, and any other low-level messages from this logger, in the
public output.
[1] http://nodepool.openstack.org/image.log
Change-Id: Ib9ac5fc81ccef73f1b1e20b8381bdd1afac4bcae
The Infra Cloud project uses a different set of puppet modules than the
standard infra ones in order to avoid possible dependency conflicts[1].
Currently the puppet-apply test hard-codes the entry-point puppet
manifest and module list. This patch makes the manifest, currently
manifests/site.pp, and the module file, currently modules.env,
configurable, so that we can add a new job to test just these nodes
with the correct modules installed.
[1] https://review.openstack.org/#/c/209617/
Change-Id: I744123befef0bf27a1eb2a79f5d814e0cefe81f5
The test slaves that the apply tests run on have puppet modules
installed from the initial slave configuration. Delete the previously
installed modules before re-installing to ensure that the apply test
only uses the modules listed in the current change's modules.env.
Change-Id: Ie62b64133c480c05968ab554185527ac5e432858
This tool assumes that diskimages option is always present on
nodepool configuration. For downstream consumption, it may not
be the case, so checking if setting is present.
Change-Id: I901e044ae9ec37eb64bc662e4182d317cf4a7647
Our repo shortnames are unique across all namespaces, so remap
governance repo names to Gerrit repo names by matching them in any
namespace. This works around asynchronous namespace moves which may
take effect independently in project-config and governance repos at
different times.
Change-Id: Ia70202bb874b6671950f4033d974087a2ee531d5
In I2aa729d1b4278743a5e99b41178dc2d11b3e1348 the projects.yaml file
of the governance repo was reorganized to support a new
"deliverables" concept which provides a subgrouping of related repos
under each project team. This requires adjustments in the scripts
consuming that file, specifically email_stats.py and
who-approves.py.
Change-Id: I041a62fd86a776279536f003724cb8c289922080
It does not appear these jobs actually require the project-config repo
for anything. It was added in
I3a772e84a1bc6028caeabcc8e09a0942f44b8612 without a lot of
explaination of why, but as it stands I don't see the project-config
affects the outcome of these jobs?
Change-Id: I85111afbbce497c86f4f6d8dfe74944c32a77b80
Literal $ characters in the template which are not part of a
substitution variable should be doubled to to avoid raising a
ValueError exception.
Change-Id: I14fd33571d63d50fc65e8c87fb10577e691b6c8e
The script that is run by find on each apply test file has -e set,
yet, it attempts to save the exit code from puppet apply and keep
running even in error. Remove -e so that it does not immediately
exit and can continue as designed.
Change-Id: I1a24e80f42be8d028ecc3eb02df54b49f811fff4
Otherwise, there is a case where the results are not rendered properly
because the shell exits.
Change-Id: Ica05615cad4fcc15c9d941d16f74cb4f68bc5a99
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This script closely follows the script in
openstack/puppet-openstack-integration to provide installation of
modules in both testing contexts: zuul and local development.
Change-Id: I517954d26409f2fbe96588f40f6f07316d85843d
Co-Authored-By: Colleen Murphy <colleen@gazlene.net>
Every repo should have a core group that includes infra-core, and
each of those core groups should be members of the infra-council.
Change-Id: Ibc02900cf2d885fa513a78b83b902dd0c4273e72
This tool will create or modify groups as specified on the command
line. It is useful for mass-updating a large number of groups.
In particular, setting the owner of an existing group is only
available in the REST API, rather than SSH.
Change-Id: I56762b16701ca96b45c8a626edca4cbc26e2859f