SHIELD v5 Release

New Features

• Added a new Web UI for SHIELD to manipulate configs, schedule and run tasks, as well as see
  what's going on in SHIELD.
• Added a new validation mode for plugins, so they can validate their endpoint configuration
  prior to running the job, and during configuration updates.
• Added a new /v1/status/internal API to shield-daemon to provide better visibility into the
  internals of the shieldd daemon
• Added a recovery mode to shield-agent, for emergency restoration. This is mostly focused
  at allowing one to restore BOSH or SHIELD from a backup, prior to having shield-daemon up and
  running, after a disaster. For details, see
  our Disaster Recovery wiki page.
• Upon restart of shield-daemon, any pending tasks are re-scheduled, for cases where shield-daemon
  is restarted in the middle of scheduling a task to run.

Improvements

• shield restore archive prompts you for targets, rather than jobs, and properly filters
  the archive list to the target you specified. This makes it easier to restore an archive
  for a specific service, even if you have multiple jobs (hourly, daily, weekly, etc) for it.
• The fs plugin now implements store functionality, and can be used as both target and store,
  to save local backups on the shield-agent machine.
• Added a lot of default settings for JSON endpoint configurations to make configuration all the
  easier.
• Refactored a lot of logic that used to live in-memory of the shield-daemon into the database,
  paving the way for many planned improvements to the daily operation of SHIELD.
• Made shield.agent.autoprovision an optional property, and set it to ignore failures on
  auto-provisioning, so that one can deploy a shield-agent before the IP of the shield-daemon is
  known. This will be followed up on with #15 for a long-term solution:

Bug Fixes

• Fixed an issue where shield-daemon was keeping connections to shield-agents open after
  completing tasks, exhausting available file descriptors for the daemon
• Fixed an issue where tasks were incorrectly being marked as canceled after their timeout
  window expired, even if they had completed (successfully or failed)
• Fixes an issue where weekly backups could send SHIELD into a loop of job re-execution.

SHIELD v4.1

Enhancements:

• Added the ability to focus mysql backups/restores on a specific database
• Added extremely experimental support for auto-creating SHIELD targets/stores/policies/schedules/jobs via the BOSH manifest
• Updated the s3 store plugin to support a wider variety of non-AWS S3 products, like OpenStack Swift, Google Cloud Storage, and Scality Object API

Fixes:

• Fixed issue preventing shield show task from finding data on purge/restore tasks.

SHIELD v4

Enhancements

• mysql plugin now supports an optional mysql_read_replica property, so that you can back up from the read replica, and restore to the master.

Fixes:

• #81 limit the number of archives shown by default in shield show archives
• #101 limit number of tasks shown by default in shield show tasks
• #99 ensure that no tasks with bad stopped_at times prevent status updates
• #94 fix to the display of certain un-startable jobs stuck as 'running'
• #36 improved tabular output
• #76 fixed shield output to show time in days rather than microseconds

v3 Release

New Features

• Added mysql target plugin, with corresponding agent-mysql job template, to install the mysql client
• Moved to golang 1.5.3
• Added support for hourly backups

Bugfixes and Improvements

• CLI underwent a lot of work, improving user experience all over
• Redis target plugin has been updated to improve backup reliability during high usage of the redis server
• Fixed a major bug where failed tasks were being reported as successful
• Fixed a major bug where archives from failed tasks were not being marked as invalid

With Tarball

Same as v2, just has a tarball release artifact.

v2 Release

Changes

• Use golang 1.5.2 for compilation
• Retention Policies are now enforced, and expired archives are purged from long-term storage
• Archives created as a result of a failed backup task are marked as invalid and purged from long-term storage
• Improved API error messaging and parameter validation

Initial Release

v1 release of the shield backup system