We can use textwrap to break up the ridiculously long lines in the
logging configuration (with less images, it's less ridiculous than it
used to be, but it's still easier to parse). Only trick is to put
spaces between the arguments to give it somewhere to split (and better
for readability) and stop it splitting on words/hyphens.
Change-Id: I04840e98b0564dc531b74b96e8595f9d18b284af
Now that the nodepool builder is running as a separate daemon it needs
its own log config file. Move the auto generated nodepool logging config
stuff over to the new builder logging config as we can manage the main
daemon's logging config by hand trivially now.
Depends-On: I013835621dfbc311a0f7bd7c957b7d4656dfa628
Change-Id: Ic1da30eab949876e5bd6c88e83979bdedc6dd50a
Manage nodepool configurations using the common-ci solution
in puppet-openstackci
Remove nodepool.yaml.erb from this repo as openstackci::nodepool
will pull it in from project-config/nodepool/nodepool.yaml
Remove the tox nodepool environment and test dependency as it
has been migrated to project-config
The nodepool logging template file and associated tool that generates the file
will remain in this repo. In the short term, updates to nodepool.yaml in
project-config repo may require a related change in this repo to update the logging
configuration. In the longer term, nodepool will be updated to automatically
log image creations without needing a customized logging configuration.
Depends-on: I89207d100eb4b6bbb502a6ed38831f49e4b29096
Depends-on: I473a1b78acdb035eb379394a7ed5f771434dc942
Depends-on: I6b01ab7260a41927fff34b9b81b631ea2c933f22
Change-Id: I2b45a7145805368b1598d3a3e8a94f0e4eb8cf2d
In I54db78b028017500b58693ec717c23eaf6a220b6 I added some handy values
that are intendend to go into public log files to help you establish
when an image-build has started or stopped (for example, [1] is
currently ~300MiB of looping build log data and it's really hard to
pick out where things are going wrong).
The problem is, I put them in at DEBUG level and the image loggers are
only set to INFO level. So the messages aren't making it into the
public logfiles as hoped, and thus not available to help people
diagnose issues with their builds.
I think the best idea is to turn these up to DEBUG level to capture
these, and any other low-level messages from this logger, in the
public output.
[1] http://nodepool.openstack.org/image.log
Change-Id: Ib9ac5fc81ccef73f1b1e20b8381bdd1afac4bcae
This tool assumes that diskimages option is always present on
nodepool configuration. For downstream consumption, it may not
be the case, so checking if setting is present.
Change-Id: I901e044ae9ec37eb64bc662e4182d317cf4a7647
There's no need to create per-provider image update logs for
providers which only use diskimages of the same.
Change-Id: I06e5413ac9357587cd4aa7afa34414b0cc01c124
This is the second part of splitting out log files for image builds;
putting diskimage-builder logs into separate files. They are added
with a special "dib" provider to keep them grouped.
Change-Id: I6406f63df2f625beee57d7ff9707bd3b4f3fc060
Generate a logging configuration template for nodepool that splits
image-build logs out into separate files.
A tool to generate and maintain this file based on the nodepool
configuration is added.
The logging configuration template this tool creates is added
alongside the main configuration. This is passed to the deployment
puppet module via a parameter.
Change-Id: I4723c68e5c83b536560e0a8bd7b73e312b46fc02
Depends-on: Iec77fb62c353d09186140b23912caf02225a643b