This moves git01.openstack.org to a new server, but should not be
merged until the old one is gracefully offlined in haproxy and the
new one is in sync with Gerrit replication and has been thoroughly
tested.
Change-Id: I84a3b2710edd96087a29735ca26863c75eb5023d
This moves git02.openstack.org to a new server, but should not be
merged until the old one is gracefully offlined in haproxy and the
new one is in sync with Gerrit replication and has been thoroughly
tested.
Change-Id: I8d0cc04ac6429a7780020242c9cc1ff2f0126b6e
This moves git03.openstack.org to a new server, but should not be
merged until the old one is gracefully offlined in haproxy and the
new one is in sync with Gerrit replication and has been thoroughly
tested.
Change-Id: Id4ab17d959fb6b7ab959fffca061b2c246a73b79
This moves git04.openstack.org to a new server, but should not be
merged until the old one is gracefully offlined in haproxy and the
new one is in sync with Gerrit replication and has been thoroughly
tested.
Change-Id: Ib15fe65bfd7e8099ae7ec1f4c9b08a15c4a7956e
Now that the new elasticsearch cluster members are joined, we need
to move the primary discover node from elasticsearch.openstack.org
to one of the new servers before we can remove it from service.
Change-Id: I79fe4e2154def6b0404b6620601f4a02b63fee8a
Kibana seems to be the only module using this list, and by default
it will try to query any nodes in this list even if they've been
pulled from service. Preemptively remove them from its configuration
so that it will continue to perform queries correctly.
Change-Id: Iecdc3414dec7ed2816b5a68a3398b0643fccaf31
Once the git repositories on git05 are replicated from
review.openstack.org and confirmed in sync, merge this to add it to
the farm.
Change-Id: I6bc87957ff9ba7983c48ce156ab7658a9ab8a5ad
Add the actual elasticsearch module and associated parameters to the
new worker nodes, and put them in the node and discovery lists.
Change-Id: I0b55e4c5c8a3f0864dab2b2bf7f498b65bc20fd2
Temporarily leave the old node names in place with an override to
16g heap size, but pass the openstack_project default of 30g into
the elasticsearch module as a new variable. Also don't actually
configure the new servers to install and run elasticsearch yet,
since there are manual steps needed to prep the additional block
devices on them.
Change-Id: I9fca2115c8996ae2f1a6c605bcdf16a8b6342a24
Implements: blueprint openid-oauth2-infra-implementation-puppet-script
Prepares a raw server with all software stack needed to run
openstackid project:
* installs PHP
* installs Apache
* installs Redis Server
* creates a initial environment configuration for laravel application
(using *.erb templates)
Change-Id: If6216da0d70a45609076e8111a67055dbc87c9e4
The following items were missing from an automated zuul install:
* A pre-populated known hosts file
* The git user/email for creating commits (.gitconfig existed
on zuul.o.o, but switch to using zuul's config file instead).
Also, make sure that the mergers specify the zuul server as the
gearman server address rather than localhost.
Change-Id: I47a473f60c4b5b2daaa910aa61cdf6e0c6fe1528
Remove obsolete config options from zuul module.
The server and merger classes are constructed so that they
may coexist on a single server. Also, the init section is
constructed so that it will install everything needed for
both services but without activating them (leaving maximum
flexibility for the operator).
Change-Id: I7b86fbbe4611c5edfb463a0a6944e0717f664188
This brings in the puppetdb module via install_modules.sh and
creates a new class, openstack_project::puppetdb. It was modeled
on openstack_project::puppetmaster. Note that this will not enable
puppetdb to participate in the Puppet ecosystem yet. An additional
class will have to be added to the master:
class { 'puppetdb::master::config':
puppetdb_server => 'puppetdb',
}
I will leave this out of this change so we can bring up puppetdb in
stages.
This paves the way for puppetboard to be brought online.
Change-Id: I8194372bd31e08f12a815fd04dcdf338565ed911
The ssh key in ~gerrit2/.ssh/id_rsa which is what is used for outbound
ssh-based replication is currently just kinda there by hand. Add management
of the files there.
Change-Id: I5bfea4543d6eb46ba2e9f3c791f4e6b6c5534522
Closes-Bug: 1209464
The differences between openstack_project::slave,
openstack_project::slave_template, and openstack_project::bare_slave
were not always clear. Keep openstack_project::slave as the default long
running slave manifest, but replace slave_template with a
single_use_slave.pp to make it clear where single use slave config
begins. Add the ability to toggle automatic upgrades and jenkins sudo
rights to this new manifest. Finally, add a more verbose comment to
bare_slave explaining what it is useful for (having a jenkins like slave
host that doesn't need a firewall or ntp or automatic upgrades).
Change-Id: I3989c9e6ad9469f441ca5d3627f7b3b704d8a8da
There are two major parts being installed with this module:
1. storyboard-api - REST API service served with
apache mod_wsgi module
2. storyboard-webclient - static html/css/js files.
This project is built and published to tarballs.o.o,
from where it'll be installed with this puppet module
This module requires three configs from Hiera:
* storyboard_db_host
* storyboard_db_password
* storyboard_db_user
Installed projects:
* http://git.openstack.org/cgit/openstack-infra/storyboard/
* http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/
Things to be added in later commits:
* Documentation for ci.openstack.org
* Configure logging (once supported by storyboard)
* SSL
Change-Id: If3da06f8d20a6282036f1f9f063c25a6d0db60c6
* manifests/site.pp
* modules/openstack_project/manifests/git_backend.pp: Add the zuul
server's public SSH key to a dedicated zuul account on the git
server farm. This will allow zuul to push arbitrary references into
its scratch repositories. Also set ownership on its scratch
repository hierarchy and pack them, properly skipping it in the
existing cgit repo repack since ownership differs.
Change-Id: I4b5b583847c828aadc903270433882531e5b1ea7
Add them to all the places it's safe to do so for now. Don't actually
spin up any nodes for them yet.
Change-Id: I59e97be7e5b094af3153bc7d5dce0cff57996f55
Also, normalize some parameters to the status manifest to make it
more readable (since they follow the same pattern). And make the
ssh config for elastic-recheck bot match reviewday.
Change-Id: I2417f121e7b3685aab9540504cdd4c6db1754e67
Refactor the openstack_project::openstackid_dev module out into a
top-level openstackid module in preparation for multiple servers,
set up Apache to serve content out of /srv/openstackid, add an
/etc/openstackid/database.php file with connection details injected
from hiera and keep an updated clone of openstack-infra/openstackid
in /opt/openstackid.
Change-Id: Icdde594384e3af27c8dd185a51b9e5a71619fb7b
