Instead of keeping a local copy of spec_helper_acceptance.rb and
requiring updates to all modules for any change, we can move it into the
common helper gem and require it from there. This will make it easier to
create and review changes that affect all puppet modules. Also change
the Gemfile to look for the gem in the local workspace if running in a
zuul environment.
Change-Id: Ic0775473835f523d587b8e39170084fa5c37bcbe
It is good enough to assume that if puppet finished successfully then it
also successfully found and installed packages and applied configs. For
the sake of maintainability, remove unnecessary tests.
Change-Id: Iac783ddacfad7a58eca08635924e04da0016b625
Add a xenial nodeset and update the spec helper to install puppet 3 from
the Ubuntu repos instead of from puppetlabs.
Change-Id: I46395c93b83e3a9234ca3023830c74eefc68c925
The nodejs module does not install npm by default, and it is needed in
order to use it as a package provider. Also remove the npm package test
from beaker, since it makes no sense for package 'npm' to be installed
by provider 'npm'.
Change-Id: Idc3d51399f1263eded3f373a7c852a609b15a204
OpenStack Health api has a new functionality that allows users to
retrieve the grouping keys used on the dashboard page.
A few of them simply don't make sense for the users, since they
are too granular.
This commit includes a new default configuration that will ignore
these keys. In case you are interested on how I come up with these keys,
please check this patch: https://review.openstack.org/#/c/240453/
Change-Id: Ibe591d9af94c1cd8d5c1d4956c1c82b4a764b5b7
While applying this module downstream we noticed that its acceptance
tests were broken.
During the process of fixing them we noticed that the reason for this
were the changes made in the manifest 'openstack_health::frontend'.
Apparently a new manifest was created to take care of installing the
frontend, 'openstack_health::vhost'.
The first step in order to fix this was adapting the tests to use this
new manifest instead of the former. While doing so we noticed that the
apache vhost template file was not being generated correctly. That
happened because it was binding agains 'openstack_health::frontend',
which now did not have the parameters necessary.
So, in order to make the whole acceptance test suite work, it was
necessary updating the vhost template file as well.
Change-Id: I79edb3b05ca25b484a62d6a414592e662b42d85e
Co-Authored-By: Danilo Ramalho <dramalho@thoughtworks.com>
This is a initial version of how to deploy OpenStack-Health.
This script provisions openstack-health as it is today. This will be a
foundation for future deployments, once the application becomes more
mature.
Change-Id: Id4ef45bba0db28b95d7fb72799cb86ab4db6343b
Co-Authored-By: Bruno Tavares <btavare@thoughtworks.com>
Co-Authored-By: Caio Carrara <ccarrara@thoughtworks.com>
Colleen Murphy