Dynamic scoping for variables in ERB templates was removed in puppet
4[1] which means that the variables defined in the
openstack_health::vhost class cannot be found when it is referenced in
the httpd::vhost defined type and will be evaluated as nil when
puppet runs. Use scope.lookupvar instead to be explicit about the
variable's source.
[1] https://puppet.com/docs/puppet/4.10/lang_updating_manifests.html#dynamic-scoping-in-erb
Depends-On: https://review.openstack.org/527302
Change-Id: I19a55d079b236728f1311e130ec6ea851539b446
This commit removes the venv handling from the api puppet module. The
venv added unecessary complexity to the puppet module and made things a
bit fragile. Since this is typically deployed on a standalone server
there wasn't really a reason to do this.
Change-Id: Ifa3a0c8ece479534115d8905f5faf831d8bb88ae
This commit switches the backend used on the api server to be the dbm
file backend with using memcached for distributed locking. This enables
having an async worker, but avoids the size limitations with storing
the cached data in memcached directly.
Change-Id: If506bbca1eb867135430c7f435c5e4a1db1a0232
Depends-On: Ied241ca1762c62a047bd366d7bd105028a884f30
This commit adds installing and configuring memcached to the api
server. It then configures the api server to use memcached for it's
local response cache. This is needed to enable the async worker from
openstack-health change I0fd29839c72ca2fdfb4c4724bb3da7e283e3d27d.
Change-Id: I3057e7f9f920550a12c12c1bfeb643a713c5f696
This commit adds a cache_expiration parameter to make the cache
expiration for the api configurable. By default it sets it 15min
(which is half of the far more conservative openstack-health default)
to match the longest e-r query times seen in testing.
Change-Id: Iaea17e16f6995121ad54bae2c46a96112b702caf
This commits adds the installation of elastic-recheck and the
configuration to the openstack-health api server for using the
additional data source. This depends on openstack-health change:
Icf203668690419c38f6d6be6b6fe4af8462845f3 to work, however it's not a
hard dependency because we can land this first without any issues.
If we do it'll mean the api server will be configured and start using
the data as soon as the openstack-health change lands.
Change-Id: Ia17effc714d176f0b0ceb517bd93d6533e16fdbc
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
Alteration of the Apache configuration for apply in the Ubuntu Precise.
It was changed for mod_disk_cache because mod_cache_disk not exist for the
Precise and check Apache Version due the parameter "Require all Granted".
Change-Id: Icc1d13fc39058f147bdbb1e6b9a810143051ece4
Co-Authored-By: Maitê Balhester <mbalhest@thoughtworks.com>
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 commit adds enabling mod_cache to the api server to enable some
server side caching. We don't need to update the data in real time on
the dashboard and performing some server side caching will improve
the dashboard performance. It'll also decrease the load we'll put on
that poor trove node in rax cloud we're running subunit2sql on.
Change-Id: I61d862603306a36c3ec6cd74d000126155bb29d5
This commit adds a missing pair of quotes around the config.json
template. The url isn't being treated as a string without the quotes,
and we're getting json parsing errors.
Change-Id: Ic6a435b3872de89801792296d19d98107e673e48
This commit adds a site.pp file which is used to deploy the frontend
to a directory instead of setting up a vhost. When deploying this on
status.o.o we need to put the dashboard in a dir on an existing vhost
instead of deploying a seperate one. This commit adds the class to do
this.
Change-Id: Ic47fbd817a293a257f7a9b164682fc96cce5321e
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>