This repository was archived by the owner on Aug 16, 2019. It is now read-only.
Releases: raymondEhlers/OVERWATCH
Releases · raymondEhlers/OVERWATCH
Overwatch 1.3.1
[1.3.1] - 2 January 2019
Fixed
- Tagging issue in Travis with multiple python 3 versions. We only wanted to deploy to PyPI for one python version, which we arbitrarily select as the python 3.7 version. See: 460aab6.
Overwatch 1.3
[1.3] - 2 January 2019
Added
- Alarms subsystem to automatically detect unexpected trending values using user defined criteria. Thanks to Artur, Jacek, Pawel! See PR #50.
- Python 3.7 docker image. See: aa97cec.
Changed
- Updated python 3.6.6 -> 3.6.7. See: 358fed1.
- Reduced the cloned size of the ROOT repo when building the docker image. See: 5d9a63a.
- Bumped ROOT version in the docker images to 6.14/06. See: 627381b.
Fixed
- Fixed typos in the ROOT build script. See: d967dda.
- Blank pkgconfig directory created in the ROOT install. See: 627381b and the related ROOT JIRA ticket.
- Allow passing in of database information to the
processAllRuns()to avoid database locking issue when running repeated processing locally (ie without a ZEO/ZODB server). Thanks to Raquel for reporting! See: 7422451.
Overwatch 1.2.3
Overwatch 1.2.2
[1.2.2] - 24 November 2018
Added
- Updated ZMQ receiver to take advantage of improved error checking in
AliZMQhelpers. - Minor documentation updates.
Changed
- Modernized ZMQ receiver to use better coding practices (
Printf->std::cout, etc). - Increase certificate proxy validity time to a week. See: ee64bd2.
Fixed
Overwatch 1.2.1
[1.2.1] - 12 November 2018
- 1.2.1 fixes a tagging issue. Below is the 1.2 changelog.
Added
- Travis CI to run tests,
flake8, and coverage. Also addedcoverallsto expand of tests coverage information. Note that theflake8tests run in the Travis CI python 2.7 and 3.6, while the tests run inside the docker images. - Travis CI will build new docker images on each commit, which are known as
rehlers/overwatch:latest-py*. Tagged releases will be available asrehlers/overwatch:tag-py*. - Releases are automatically made on PyPI through Travis CI.
- Added
overwatch.base.dataTransfermodule, which is responsible for transferring data provided by the receiver to various Overwatch and EOS sites. This modules is fairly well covered by tests. - Added webApp, processing, and data transfer monitoring via
sentry. It hooks into everything (exceptions, logs, etc) to help identify and debug issues. - Added a module for replaying data in
overwatch.base.replay. Can be used to generically replay processed data, moving from one directory to another. For further information, see the README inoverwatch.base. - Units tests for timestamp extraction in
overwatch.base.utilities. See: 62737f1. - Added some integration tests for creating runs and subsystems in
overwatch.processing.processRuns. See: b09e738. - Added rudimentary ZMQ receiver monitoring via the
dataTransfermodule. If no files have been transferred in 12 hours, a warning will be emitted. See: 4ea80cf2. - Added dedicated direct ZMQ receiver monitor via the
overwatch.receiver.monitormodule. It monitors heartbeat information directly from the ZMQ receivers. It is a supplement to the monitoring via thedataTransfermodule. See: c081a8b. reprandstrmethods to most of the processing classes to aid in debugging. See: 3a544d6 and 43657bc.
Changed
- Updated
overwatchDeployto be class based, and generally far more stable and extensible. It is also broadly covered by unit tests. - Improved webApp status information (and removed obsolete code). See: c41e559.
- Changed all time related functionality to utilize the
pendulumpackage. It makes live so much easier! See: 8fe66ba.
Fixed
- Creation of run and subsystem containers as new data arrives. Issues were caused by received files arriving at different times, which split up the processing. See: b9230b9, with fixes in 1cfb18c, 5e3630a, f7863a6, and 364543f.
- Fixed data transfer to only select on files which end in ".root". ROOT appears to create temporary files when writing which are sometimes picked up during data transfer. See: 83412bb.
- Execution data is now stored in the
execdirectory. Information includes logs, configurations (except for the Overwatch config, which must be in the executing directory), and more sensitive files (SSL, etc). They will be used automatically in the docker images and bysupervisorThis was changed to better reflect what information was stored. See: ec64fbd. - Removed the
deploydirectory, along with much of its obsolete contents, which have been replaced by thedeploymodule. See: 9735748. - Timestamp handling was inconsistent, which caused problems when trying to improve the
isRunOngoing(...)logic. Switch to explicitly handling the time zones with thependulumpackage, which makes things much easier. See: 819fa6a for the start, and 8fe66ba for the last commit, which resolved all known issues. - The docker images now run in a less privileged user.
- Ensure that the data replay copies to the proper folder when there is already an existing folder. See: f71afab.
- A wide variety of typos.
Overwatch 1.2
[1.2] - 12 November 2018
Added
- Travis CI to run tests,
flake8, and coverage. Also addedcoverallsto expand of tests coverage information. Note that theflake8tests run in the Travis CI python 2.7 and 3.6, while the tests run inside the docker images. - Travis CI will build new docker images on each commit, which are known as
rehlers/overwatch:latest-py*. Tagged releases will be available asrehlers/overwatch:tag-py*. - Releases are automatically made on PyPI through Travis CI.
- Added
overwatch.base.dataTransfermodule, which is responsible for transferring data provided by the receiver to various Overwatch and EOS sites. This modules is fairly well covered by tests. - Added webApp, processing, and data transfer monitoring via
sentry. It hooks into everything (exceptions, logs, etc) to help identify and debug issues. - Added a module for replaying data in
overwatch.base.replay. Can be used to generically replay processed data, moving from one directory to another. For further information, see the README inoverwatch.base. - Units tests for timestamp extraction in
overwatch.base.utilities. See: 62737f1. - Added some integration tests for creating runs and subsystems in
overwatch.processing.processRuns. See: b09e738. - Added rudimentary ZMQ receiver monitoring via the
dataTransfermodule. If no files have been transferred in 12 hours, a warning will be emitted. See: 4ea80cf2. - Added dedicated direct ZMQ receiver monitor via the
overwatch.receiver.monitormodule. It monitors heartbeat information directly from the ZMQ receivers. It is a supplement to the monitoring via thedataTransfermodule. See: c081a8b. reprandstrmethods to most of the processing classes to aid in debugging. See: 3a544d6 and 43657bc.
Changed
- Updated
overwatchDeployto be class based, and generally far more stable and extensible. It is also broadly covered by unit tests. - Improved webApp status information (and removed obsolete code). See: c41e559.
- Changed all time related functionality to utilize the
pendulumpackage. It makes live so much easier! See: 8fe66ba.
Fixed
- Creation of run and subsystem containers as new data arrives. Issues were caused by received files arriving at different times, which split up the processing. See: b9230b9, with fixes in 1cfb18c, 5e3630a, f7863a6, and 364543f.
- Fixed data transfer to only select on files which end in ".root". ROOT appears to create temporary files when writing which are sometimes picked up during data transfer. See: 83412bb.
- Execution data is now stored in the
execdirectory. Information includes logs, configurations (except for the Overwatch config, which must be in the executing directory), and more sensitive files (SSL, etc). They will be used automatically in the docker images and bysupervisorThis was changed to better reflect what information was stored. See: ec64fbd. - Removed the
deploydirectory, along with much of its obsolete contents, which have been replaced by thedeploymodule. See: 9735748. - Timestamp handling was inconsistent, which caused problems when trying to improve the
isRunOngoing(...)logic. Switch to explicitly handling the time zones with thependulumpackage, which makes things much easier. See: 819fa6a for the start, and 8fe66ba for the last commit, which resolved all known issues. - The docker images now run in a less privileged user.
- Ensure that the data replay copies to the proper folder when there is already an existing folder. See: f71afab.
- A wide variety of typos.
Overwatch 1.1
[1.1] - 2 September 2018
Added
- Fully document all classes.
- Update documentation scheme and system (update sphinx, etc)
- Deploy documentation to Read The Docs.
CSRFprotection for the web app in preparation for deployment.- Tests for
overwatch.base.configandoverwatch.receiver.dqmReceiver.
Changed
- Moved
overwatch.processing.qa->overwatch.processing.pluginManagerto better represent how it's purpose
how evolved. - Moved update users script to the base package, allowing for it to be installed via
setup.py. It is
available viaoverwatchUpdateUsers. - Modified plugin future arguments to only use
**kwargs. Using*argsseems like a dangerous standard.
Anything that will be added should be added explicitly as a keyword argument. - Renamed
retrieveHist->retrieveHistogramin thetrendingObjectfor consistency with the histogram
container. Updated the corresponding classes and documentation. - Drop
vprefix in tags. The actual version we use in python doesn't include thev, so including it in the
tag makes versioning a bit more difficult for no benefit.
Fixed
- Add missing
__init__.pyin theoverwatch.processing.detectorsmodule. - Handling of newly received files had a number of small bugs and other mistakes in the relevant data
structures. All of these were corrected and tested.
Removed
- Removed
bcryptLogRoundsalias from the YAML config. The default is now drawn foroverwatch.base.config.
The value can still by set via YAML, but one should not depend on the alias. - Removed obsolete code in the webApp related to the former QA system. Mainly removed obsolete
jsandcss.
Initial full release
Initial full release of Overwatch, containing substantial upgrades from the previous version, including:
Full rework of the processing framework.
Full rework of the web app using Polymer and jsRoot.
Rework of configuration to use YAML.
Metadata database.
Basic trending framework.
Basic alarms functionality.