Skip to content

Boreas
Compare
Choose a tag to compare
@vkotronis vkotronis released this 26 Jan 10:46
· 122 commits to master since this release
2.0.0
9425921

To upgrade, please follow the guide here and pay attention to the important 2.0.0 upgrade instructions.

Added

  • Action and necessary logic to un-mitigate a hijack
  • Ability to reload targeted services based on what conf section changed
  • GET config endpoints to backend and monitor services
  • Makefile for local commands (dev/ci)
  • Added healthchecks to docker-compose (docker-compose version bumped to 3.4)
  • Service reconfiguring flag and status
  • Redis no-data-received key expiry logic (default: 60 seconds)
  • Hijack detail JSON export

Changed

  • Decoupled microservice architecture for backend and frontend
  • Possible states constraint on DB hijacks table to allow orthogonal mitigation tagging
  • Orthogonal mitigation/unmitigation tagging
  • Heavily refactored docs
  • Replaced bulk timer thread with separate process
  • Replaced autoignore checker thread with separate process
  • Replaced exabgp autoconf thread with separate process
  • Display info on new microservices, grouping backend/monitor
  • Upgraded requests to 2.25.1
  • Upgraded to new bgpstream containers (using also ris and routeviews live sources)
  • Full refactoring and upgrade of artemis-utils, refactored all imports (1.0.7)
  • Upgraded Flask-JWT-Extended to 3.25.0 to address JWT issue with new browsers
  • Upgraded artemis-utils to 1.0.8

Fixed

  • Discard messages with timestamps in future datetime (updated to artemis-utils==1.0.5)
  • Check for very old timestamps in DB update handling
  • Replaced sets that are not supported by shared manager with lists
  • Removed unneeded read locks
  • Non-gracefull SIGKILL for taps in case graceful stop delays a lot
  • Redis configuration file input

Deprecated

  • 'caida' project in bgpstreamlive
  • supervisor support and configuration

Notes:

  1. if you encounter issues with detection essentially getting "stuck" (see #564) please comment under this issue and give us a heads-up in Slack. This was a bug we encountered only in a certain local deployment and we would like to double-check with the users whether it is an actual problem. If it is, please consult the issue workaround comment and we will patch on demand.
  2. If you see any redis-related errors probably you have not set the configuration file of redis (new 2.0.0 addition correctly). Just run:
cp backend-services/configs/redis.conf local_configs/backend/redis.conf

and restart artemis.

Assets 2
Loading