The opendev project has been moving away from puppet and this is one of
the puppet modules that is no longer used. To simplify things for us we
are taking the extra step of retiring this repo.
Change-Id: I46ccab87f063c51dd3236757dbb0567738803fae
Our CI jobs' logserver wasn't setting cache headers so browsers were
always downloading the log files on each request. Reduce load on the
logserver and improve performance by users via the setting of a 2 week
ttl on log data.
This should be safe because each job writes to a uuid identified dir and
that data doesn't get overwritten. Once written the data is static.
Change-Id: Ic99df4e4e64a6bf64e68e6f1bc297c91134ab716
Fix the scope for the template variables for the httpd vhost, and fix
the ServerAlias value when serveraliases is undefined.
Depends-On: https://review.openstack.org/578559
Change-Id: Ia0f9b704d95facd4668d972a66f94f741a99bca2
Dynamic scoping for variables in ERB templates was removed in puppet
4[1] which means that the variables defined in the
openstackci::logserver 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
Change-Id: Iea37fb14bc332cbf2d598b908bce997786814924
After being tested in the parent patch, this will improve the
performance of the logs and ara report browsing.
Change-Id: Ib0dd51e24e7e4cc0d4308639d27a2aba18a9e96c
We've successfully tested the ARA sqlite middleware on logs-dev.o.o.
We're ready to use this on logs.openstack.org.
Change-Id: I88c06366b8d5837ad6fc50163e5d58fe1b5eaa8f
I'm not sure why, but previously we have not passed .log.gz files
through to the htmlify web-app. This means clicking on it in the
browser prompts to download the file. This is unlikley to be what
devlopers investigating logs interactively want.
Traditionally in devstack-gate there's been a bunch of renaming
log->log.txt that happens to make the files presentable [1]. With
zuulv3 native jobs this happens less and everyone has to be aware of
this behaviour (e.g. Ia7415d2fbbb320f8eddc4e46c3a055414df5f997 is a
good example of raw .log files being added). I think it is fine to
assume a .log file is text that is safe to pass through os-loganalyze.
From my reading of os-loganalyze [2], a .log.gz file would get mached
by util.use_passthrough_view and by default be filtered via a HTMLView
-- thus the file_conditions.yaml update is perhaps unnecessary, but
provided just to keep things in sync with .txt which has always been
there (I9cda9c05f42c5658d1c1dde8aa2efbc0abcc48a2)
[1] https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n869
[2] https://git.openstack.org/cgit/openstack-infra/os-loganalyze/tree/os_loganalyze/view.py#n237
Change-Id: I72e4f752713e7947bd66dfe8164976f0a4e3af24
- In vhosts templates, iterates each key/value from the hash
by using the proper Ruby syntax: https://ruby-doc.org/core-2.2.0/Hash.html
- In logserver.pp, default readmes to an empty hash instead of an empty
array.
Change-Id: Ib1c70cfd9254bb4da9b6f7477baa48918de16cc2
Add legacy parameter for logserver class, to install logserver resources
specific to OpenStack Infra only when needed (true by default for
backward compatibility).
Change-Id: I65e8ecf39130377c088c053e5623212f7db60f7a
This sets the json.gz files' mimetype to application/json so that we can
compress stackviz report data and still have it render properly in your
browser. This will allow us to save space on the log server.
Change-Id: I42d7d607e5864a81d52e72ff695331eb2d67d2c0
We tested an addition to the logs-dev.o.o vhost in
https://review.openstack.org/#/c/435566/ in order to properly
detect and serve .svg.gz files and it works well.
Let's do it on logs.o.o.
Change-Id: I1305f7e1c4fe02269eccd60fe8d49419d8372b59
In I5e5d2da0ef3c385f836507e69a686821aba925a1 we applied new
rewrite rules and mimetypes on logs-dev.o.o to try and make
sure that rich html content (css/js/fonts) would work either
when gzipped prior to initial log upload or when automatically
gzipped after some time.
This brings the change from logs-dev.o.o to logs.o.o.
Change-Id: I20db0aa12eda8157d68a7b27dbbfe3ca729347c7
We have a vars.yaml file that is output as part of jobs. It's useful to
be able to browse its content in the web.
Change-Id: I618b25cde4118ae3eadfdf88ad4e7f2f004d6b71
When someone looks at the logs for a periodic job, they are almost
certainly looking for the results of the latest run. Order the
listing by date descending so that is right up the top, and you don't
have to search through all the entries to find the latest one.
Change-Id: Ie37343728a90a805b20b2b125e17cd3b11dc6b40
This reverts commit fededacaf0.
Reverting because os-loganalyze doesn't list file sizes from disk. This
is an important piece of info for people debugging failures.
Change-Id: Ibecc3372c3040432db03056bd681dec182dd2d03
os-loganalyze now has the ability to provide indexes for both on
disk and in swift files. Handle all requests through osloganalyze
so that paths containing both disk and swift files can have all
of their assets listed.
Change-Id: I495ce20d56b04fdc5c2051f2bbcb834049ac6bda
Remove some old path patterns which are a year past their expiration
date, and also sync up the logs-dev template comments to match the
production version (for ease of diffing).
Change-Id: Ibfd4fc1b16c3eac2c6093f1b031bf7ae237eaf04
Clark Boylan