It doesn't seem like this is used anymore. Let's remove it before
we update the rest of this, so that we don't have to, you know,
update abandoned things.
Change-Id: I1c3708021046a428da82eaa843961091915ba4af
There's a bunch in here. This is mostly big-ticket things and test
fixes. Also, change the README to rst - because why is it markdown?
Depends-On: https://review.opendev.org/654005
Change-Id: I21e5017011e1111b4d7a9e4bf0ea6b10f5dd8c1b
Grafana has moved to a new package repo [1] and the apt-get update
step is failing on the current host.
The first version of puppet-grafana that has this update is 6.0.0;
this is two years later than the current version we're using so
... yeah. It does not work with puppet3, so only run apply test with
puppet4.
It looks like upstream has moved from camptocamp/archive to
voxpupuli/archive so the comment is no longer required.
[1] https://grafana.com/blog/2019/01/05/moving-to-packages.grafana.com/
Change-Id: Ibab0ed6799563ba0f9674ef1ea575c6ac5d60341
The puppet-python module had some broken facter custom facts that they
removed in 1.9.5. After upgrading to puppet-4 we notice this now. Update
to 1.9.5 from 1.9.4 to fix the error.
Error from puppet log:
Apr 11 00:15:30 afs01 puppet-user[5184]: (Facter) error while resolving custom fact "virtualenv_version": undefined method `[]' for nil:NilClass
Change-Id: I853ed9e212885b01944dd5dc9157f2abdd9dedc3
Puppet4 is a lot pickier about puppet module dependency resolution. On
some hosts with puppet4 we are getting:
ModuleLoader: module 'project_config' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules
Running the suggested command we see that vcsrepo is not resolved
because the version of vcsrepo we install doesn't ahve a metadata.json.
Thankfully the HEAD of vcsrepo does have metadata.json which should
allow this to be resolved.
Depends-On: https://review.openstack.org/641161
Change-Id: I022afd8bab58588e31f3f8e806183933a1de4e6b
Puppet 4 is a lot more particular about module deps and has notices that
our mysql module version depends on puppet/staging >=1.0.1 but we only
have 1.0.0 installed. Fix this dep issue by bumping to 1.0.1.
Change-Id: I36629821d8f8187dbffd614d3b263a9bc44ced6e
Remove the puppetry for managing nameservers as we now use ansible
configured name servers without puppet.
We will need to follow this up with deletion of the existing
ns*.openstack.org and adns1.openstack.org servers.
Change-Id: Id7ec8fa58c9e37ce94ec71e4562607914e5c3ea4
This appears to be the first version that supports Xenial (16.04).
Choose this to be as close to what we have but no further than we
need.
Change-Id: Ibf383ec80f1b1a773874663b7db1f58e932c9eba
Bandersnatch mirroring has been disabled since
I88a838cb28fee3bd16b2b0a26e614ac5c2f23241 which is currently almost 6
months ago. Since then we have been running a reverse caching proxy.
Although bandersnatch served us well, it seems pypi has become
impractical to mirror locally. This is partially due to 2TB volume
limitations of OpenAFS and partially due to us not having a sane way
to filter large, frequently updating packages. With the reverse proxy
working there are no plans to restore our local mirror.
Retire the references to it before we clean up the AFS volumes.
Change-Id: Ia23828328dd859bbf26f95735c1c2e99c573d10e
Contains a handler to restart crond when tz is changed. Cron service
name differs across distros.
Removes the puppet-timezone usage.
Change-Id: I4e45d0e0ed37214ac491f373ff2d37750e720718
stackalytics.openstack.org does not resolve and seems very dead. Remove
its node from site.pp and remove it from the docs to avoid confusion
about what servers we're really managing. We can always add it back when
the time comes to try again.
Change-Id: I733130ebe97ae7e06ca57b3c8e3a8708fcfa069c
The odsreg.openstack.org server was removed from service 2018-01-11,
and should also be cleared from our global site manifest. It was the
only thing utilizing the puppet-odsreg module, so we can take that
out of the modules list as well (that will be retired separately).
Change-Id: Iadfddb3bf57428b928cacaaa672e24c4a1e92058
This module has been deprecated for the voxpupuli version. 2.6.1 is
the last release with Puppet 3 support. It seems to mostly be a fork,
so I think it is compatible. The repo is hard-coded which is why I
think it's worth updating.
Change-Id: I3ca7c04a4e6122625e716682f8e0d4f9b62dbfc0
Infracloud is sadly deceased. The upside is we can delete a lot of code
we don't need anymore. This patch removes infracloud nodes from
site.pp so that the puppet-apply test no longer bothers to validate
them, removes the infracloud modules from modules.env so that we don't
bother to install those modules in puppet-apply and puppet functional
tests, and removes the infracloud-specific data from the public hiera.
Additionally stop the puppetmaster from trying to run the infracloud
ansible playbook and finally remove the chocolate region from nodepool's
clouds.yaml (vanilla was already done).
This patch leaves the run_infracloud.sh script and the
infracloud-specific ansible playbooks as well as the infracloud
manifests in the openstack_project puppet module. It's possible those
tools could come in handy in the future if we ever have another
infracloud, and leaving those tools in place doesn't add confusion about
which hosts are actually active nor does it leave cruft that gets
unnecessarily tested.
Change-Id: Ic760cc55f8e17fa7f39f2dd0433f5560aa8e2d65
This runs bind as a hidden master nameserver so we can do all the
keysigning there, and then use nsd (or bind) as public authoritative
slaves.
Change-Id: Ifb2ad109103051fa13c4af1c7be1ca0ae98bb1a1
This is currently the last 1.x release that still support puppet 3, we
could make the jobs to puppet 4, but for now we just need a new enough
module for xenial support.
Also, seems puppetlabs-apache is only uesd by cacti.o.o.
Change-Id: I128a0d8d851311b77592d98ded5891d71dce2031
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This is the lastest version of puppet-nodejs that both supports Xenial
and puppet 3 ... after this it starts using puppet 4 syntax. Update
because we need it for Xenial. (note they also changed to using a "v"
prefix)
Change-Id: Ia7966fb9578d0d79f3a7f9480e3a956555737dc8
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>
This installs the ptgbot Puppet module so it will run from the
eavesdrop.openstack.org server and generate its Web content there.
Include some rudimentary operational documentation.
Change-Id: I92ddbbb683dede2c325f70267bd5e26884a35c01
Depends-On: Idb1fc5273b67ab88e1c78578275969b04c781c7a
infra-cloud still uses mitaka, but the stable/mitaka branch is not
around, so we can't use that as a git ref.
Change-Id: Ib7456376111a630c2e99e6d5a45bd39e486e60ae
The mysql module was hardcoding 'upstart' as the mysql service provider,
which is wrong on xenial. This was fixed in 3.7.0[1] but let's go ahead
and bump it up to the latest version, which is still not a major version
bump.
[1] https://github.com/puppetlabs/puppetlabs-mysql/blob/master/CHANGELOG.md#supported-release-370
Change-Id: If25da754ec107b8dba2d9343f16b54b99cc88e01
To get metrics on MQTT usage into graphite/grafana this commit adds
running mqtt_statsd on firehose
Change-Id: I90bb2c4fc7e409e9af24ca7cec7ad9d7926739e9
Depends-On: I28058bf6eac2354e3ceba0011464509ed6bdd869
This is a simple first deployment of an ethercalc service. It does not
come with authenticated redis or redis backups. It will however have
working ssl.
Change-Id: I8c434a6bff42bce75e67fb37665d213f3cc018c8
Depends-On: Id10247211d9643e81bb1b6e8fb67377ba6de873a
We were using version 0.4.0 which supported Wildfly 9 just fine (with
the systemd sysv support hack), but now we need wildfly 10 on the
translate-dev server. Unfortunately 0.4.0 does not support wildfly 10
properly because wildfly 10 removed its built in init scripts. This
newer puppet module will install systemd unit files that should work
fine.
Note that even though the new version of the puppet module supports
wildfly 8, 9, and 10 it does not appear to do so on all ubuntu releases.
Wildfly 10 requires a current enough release to have proper systemd.
Older wildfly versions shoudl work on older ubuntu releases via the
built in init scripts.
Depends-On: I39453506821ff7073290a4e5696eda8575b6cb06
Change-Id: Iac6abcc4644276b1fc3117737e1dd4aa1be87785
This reverts commit c6c192a49df6a473e0bbc9535293f305dd551b1f.
We are seeing failures on puppet runs in lists.openstack.org related
to pacemaker provider, reverting till we figure out the problem.
Change-Id: If7e095190b98a9888d52dc89f9c8840c97e3a631
Please note that we are skipping this module install
on precise because it does not work and due to puppet-apply
on precise we are not able to pass tests.
Change-Id: I9420fb582d85debf91509b6b251c5a84de128b1b
This commit adds deploying a running lpmqtt to firehose nodes.
Change-Id: Ia9d659e282a2a992b8c1a7a48577f3e59793effa
Depends-On: I613330e2bff2e6fe1cacd7e53f3c189584978ea2
This commit adds the policy to configure firehose nodes which will run
mosquitto and a germqtt daemon.
Depends-On: Ibec91fd0abc637ea7087872cab1ec8487c73acae
Depends-On: I24a0cdb6a41f6e440db8e68216b19ca61b4cba31
Change-Id: Ie3be71e16c42c32a9f479da468db6c53ebae52ac
The needed commit is included in the 1.4.0 tag, and a subsequent 1.5.0
tag has also been released. Bump module version to 1.5.0.
Change-Id: I1554775a0bcade53a0302c2bd5f13fa964c0d611
This is our initial commit for adding zookeeper to Nodepool. Right now
this is the most basic configuration needed to start zookeeper. As we
move forward, I expect us to change out for default settings.
Change-Id: I22640a91dc51d4318e6cc055177c879fa380cc4f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>