These role docs aren't exactly War and Peace, but I think longer term
as we fiddle about making things generic or not and moving them
around, we'll be better off having kept ourselves to writing
*something*.
Add terse README.rst files for all existing roles, and add simple
linter check to ensure new roles get them too.
Change-Id: Ibc836310fb8a45e12c2e31f112d92509ac350413
We don't run a cloud anymore and don't use these. With the cfg
management update effort, it's unlikely we'd use them in the form they
are in even if we did get more hardware and decide to run a cloud again.
Remove them for clarity.
Change-Id: I88f58fc7f2768ad60c5387eb775a340cac2c822a
This is not a variable describing the system-under-management
bridge.openstack.org - it's a variable that is always true for all
systems in the puppet group.
As a result, update the puppet apply test to figure out which directory
we should be copying modules _from_ - since the puppet4 tests will be
unhappy otherwise.
Change-Id: Iddee83944bd85f69acf4fcfde83dc70304386baf
The puppet playbooks were some of the first we wrote, so they're
slightly wonky.
Remove '---' lines that are completely unnecessary.
Fix indentation.
Move some variables that are the same everywhere into
ansible variables.
Put puppet related variables into the puppet group_vars.
Stop running puppet on localhost in the git playbook.
Change-Id: I2d2a4acccd3523f1931ebec5977771d5a310a0c7
The production directory is a relic from the puppet environment concept,
which we do not use. Remove it.
The puppet apply tests run puppet locally, where the production
environment is still needed, so don't update the paths in the
tools/prep-apply.sh.
Depends-On: https://review.openstack.org/592946
Change-Id: I82572cc616e3c994eab38b0de8c3c72cb5ec5413
Load our various cloud configuration files into openstacksdk for a
basic sanity check of the configuration.
Change-Id: Ieedb3439533f3162d2b5cecca4b7fc07b631019e
Map the modules to the correct path depending on whether this is running
under puppet 4. Currently, acceptance tests for puppet 4 will always
explicitly set PUPPET_VERSION.
Also clean up an unused variable to avoid confusion.
Change-Id: I9bd36a277411c72ef77ce157f8364845acc2e923
Running against localhost by default with kick.sh means that if you have
disabled puppet crons on the puppet master to test things you will
reenable them automatically creating potentially bad side effects. Avoid
this problem by forcing people to explicitly puppet localhost if this is
what they want.
Change-Id: Id4212005735cac13e6d26439f309569d7567206c
There are some assumptions made about the puppet config paths that
aren't applicable for puppet 4. Configuration, including modules,
belongs under /etc/puppetlabs. It's also no longer necessary to fix up
the templatedir or server configs in puppet.conf.
Change-Id: I3b544b6ce4a96a7a2478522a78402f77ff86a5a5
Change Ia7415d2fbbb320f8eddc4e46c3a055414df5f997 removed per-image
logging from nodepool; it now keeps a series of named log files. The
"image" logger is removed, along with all the specific build logs.
I972a66f9c153f52df934d25ab2f77596bb2e5429 removed the
image_log_document_root argument; which wasn't doing anything in
nodepool::builder, but was actually being used to fill-out the
builder-logging.conf file. Thus we need this to not have a bad path
in the config file.
Change-Id: I6fdc3b622454b069f3ad2cf42da584d8df23a110
Update our nodepool_log_config.py script and remove support for
snapshots.
Generate latest version of nodepool-builder logging.
Change-Id: Ib87e8c352b56f63ca44668f43fa440645fab9f37
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Currently puppetdb and puppetboard have been broken for some time (+1
year) and with ubuntu precise becoming EOL it is prime for deleting.
This leaves openstack-infra with a gap in reporting for non-root
users. As such, as proposal is in the works to maybe use ARA.
Change-Id: Ifc73a2dba3b37ebe790a29c0daa948d6bad0aa33
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We use zuul cloner + zuul to set up /etc/project-config for integration
testing with rsprec. As of zuulv3 this no longer results in an origin
remote being set which the puppet vcsrepo resource expects.
Address this expectation by manually configuring an origin remote after
we clone the repo.
Change-Id: I83e7088c36b1b57279bb32e44c9f74730da582cf
The change which just merged to incorporate recent retired
deliverables and removed projects in active contributor analysis was
written prior to the gitweb->cgit transition, so fix up that feature
to also use the new cgit-based function call.
Change-Id: Ifde87147399967c43f3e4c93de4347acd31e73cc
Because we are running tests in the gate, we can skip downloading pip,
as our images have already been setup to use the latest version.
Change-Id: I3d235334e0457b70bb69a8fe4b475e69d84c3407
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Missing the original I920e1bc134d1283e2019f4389a5491e9b746cca0
implementation, also filter the per-team PTL electorates to only
include OpenStack Foundation Individual Members. The previous change
did this correctly for the full (Technical Committee) electorate but
failed to apply a similar conditional constraint to Project Team
Lead electoral rolls.
Change-Id: I03e90e5c512ee463cfcc49f147ff523806ae05c7
Story: #2001094
Task: #4877
Since the foundation sometimes needs to deduplicate subsequent
invitations for the same foundation member against invitations sent
by another system, use the member ID as the first field of the
invite instead of using the Gerrit username now that we have that
information available. Use a default member ID of 0 to indicate
non-member invitees who may require additional manual deduplication
or vetting. Also log the member ID in the output of the invite mass
mailer script.
Change-Id: I86d879a5f06144a0889eb852f2cf3d555a12a7aa
If a deliverable or entire project is retired within the qualifying
period for an election, those contributions still count toward
defining the electorate. Merge them into the list of official
projects under those circumstances, but check for any possible
duplicates in case of partial deliverable retirement for a
multi-repo deliverable.
Change-Id: If626373cdbc6ca9ad7d016b2e18b4d82a4ceaa23
Depends-On: I7ca3c9294d325085ce9139f3a86b55e5b31c79c7
In an effort to be more consistent about encoding parameters for GET
requests made in the script which generates electoral rolls and some
event invite lists, centralize calls to the requests module. This
has the added benefit of encapsulating retry logic for potential
reuse in later additions to the script.
Also generalize the query_gerrit() function to flexibly handle both
Gerrit REST API which return neutered JSON and Gerrit Gitweb queries
for retrieving YAML with its own special character encoding
challenges.
Further extract out the JSON decoder error handling so it can be
reused for other APIs than Gerrit's in future feature additions.
Change-Id: Ibda65d41c17416eb28eb326e2cdd28c90153f108
Puppet is now throwing an error about this for centos-7 unit tests.
Add empty SSH key for krotscheck.
We also need to make sure puppet has been properly installed, this is
because we have recently removed puppet from our diskimages.
Change-Id: I8bcaddd045be3f81de5c2481e0de6a8526c97a91
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Be explicity with our inventory file, to avoid ansible-playbook from
skipping hosts.
Change-Id: I29260bd97432a443e5989fa4a883e8e8d37307fd
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The version of puppet 3.x in Debian Jessie is 3.7.2, which seems to be
unable to read the modulepath setting from environment.conf. Since we
only have the one environment, the quick fix is to link the module into
the standard module path.
Change-Id: I6f4fa87fa4941c29abf37c277f5ce895a51945bc
Add a human name in the invites sample configuration's from address
value, since this will cause messages to appear with a friendlier
from name than just a raw E-mail address.
Change-Id: Idf16904bcd56692f3a82e41cb52201ed2223fdfd
In the sample settings file, backslash-continue the string literal
opening to avoid introducing an extra leading newline in the
resulting message body.
Change-Id: Ief61f69acb5299ba324af8a897ea4f96fa47711d
Since the send.py script for invites uses print to emit progress
including the names of contacts to which messages are sent,
redirecting stdout of the script to a local file can result in
encoding errors if some of the names include non-ASCII codepoints
(but not when stdout is your interactive terminal). Setting
PYTHONIOENCODING=utf-8 in the calling environment works around this
nicely.
Change-Id: I52b70c64f8b3a20da5143b31c5090192b0c75c99
There only needs to be one sample ATCs file for the invites
mass-mailer, so remove the redundant one which isn't referenced in
the README file. This should help prevent people editing the wrong
sample and then performing a dry-run with the unmodified one.
Change-Id: I61e90ad085e89c466053858518db09a414a07792
The owners.py script is used to generate electoral rolls. It has
example usage comments which previously skipped reporting the
OpenStack Proposal Bot account used to push general changes into
code review, so add the OpenStack Release Bot account there as well
since it also pushes some release-oriented changes.
Change-Id: I98607b9adb8d2c6535beab2879e24097d32434e7
This change modifies the usage of the script so that it can be imported by
the election module. It also fixes maketrans support for python3.
Change-Id: Ie3b602237625e11651825abc8feb38caa73e9632
Kazoo client is very verbose for debug output, default to INFO.
Change-Id: Iff2682d98738e2df2acda11ac2dbcb2706262256
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This adds loggers and handlers for each provider in the nodepool
config file for separate image upload logs on the nodepool host.
This doesn't regenerate the file yet. It won't do anything until the
dependent change to nodepool starts generating upload logs with logger
names that match these.
Change-Id: Ic80e532891f039e0f835847ddfbae38f1ce3cd8a
In order to run the script directly in the test, the script needs to
have the executable bit set. Currently, the test is failing with a
"Permission denied" error when attempting to run the script.
We also need to run install_modules.sh in the logstash-filters test, so
move that invocation to the shared prep-apply.sh script.
The vcsrepo puppet define doesn't understand revisions of the form
"refs/zuul/foo", so instead parse the HEAD sha and pass that to vcsrepo.
Finally, we need to ensure that $elasticsearch_nodes is populated with
an array, otherwise the function @elasticsearch_nodes.map in the
output.conf template will fail.
Change-Id: Ic1ab6d04232abb3cf347f0d27afbf9172f62b0e4