shield Release v0.7.0

NOTE: Prior to 0.7.0 of SHIELD, the fs plugin had a nasty bug that would manifest if you had more than one fs-based backup (target or store) configured on the same agent. Users are advised to upgrade to 0.7.0 if they wish to make use of filesystem-based backups!

Improvements

• The CLI now displays the store / target / schedule / retention
  policy names, alongside UUIDs in the Job creation TUI forms.
  Fixes #195.

• shield show tasks now honors the --limit parameter, so you
  don't have to look at all the tasks. Fixes #164.

• shield backend now prints the currently selected backend.
  Fixes #194

• Both the Web UI and the CLI now lowercase plugin names before
  submitting them to the Rest API. Fixes #156

• The postgres plugin once again allows users to customize the path
  to postgres binaries via the pg_bindir target configuration parameter.

  NOTE This re-introduces a feature that was previously removed, using
  the same configuration. Take care to insure that any targets you have
  configured are no longer specifying this key, as it was ignored until now.
  If it is specified, ensure that it is the correct value, or remove it, if
  it is unneeded. If it is specified and is an invalid value, your postgres
  backups will start to fail after upgrading.

• Releases should now include both the SHIELD CLI (built for
  various platforms) and also the server components, available as a
  tarball for different platforms / architectures. This tarball
  contains: shield-schema, shield-agent and shieldd, all
  supported plugins, and the static assets for the SHIELD Web UI
  (in webui/). Fixes #217

• Backup and Restore operations now bail out if no data is
  detected on the input side of the stream. That is, if a backup
  plugin misbehaves and doesn't send any data to be backed up, the
  job will fail. Likewise, if a restore doesn't pull any data
  back from the remote store, the operation fails. This is
  considered a good thing.

Bug Fixes

• Dropdowns on the Job Edit Form now remember the values the Job
  had before you opened the form. Fixes #173
• The mysql plugin can now be used to backup and restore all
  databases. Fixes #211
• The fs plugin just plain didn't work; it would happily write
  to the (regular) file /dev/st0, but not to standard output.
  Similarly, on restore, it would read from /dev/st0, not standard
  input. This caused our testing (one fs-based backup) to pass,
  but didn't work out so well in the real world. Mitigations have
  been put in place to ensure that plugins send backup data to the
  store plugin.
• The fs plugin now creates the base directory if it does not
  already exist, allowing for complete restore from a backup.

shield Release v0.6.6

Improvements

• Shield will now only let a single task be run for a given
  target at a time. You can no longer run a backup and restore
  of the same data simultaneously.

Bug Fixes

• Fixed an issue with the s3 plugin having issues when paths
  contained/started with double /s.
• Fixed an issue where purge tasks weren't properly created with the MySQL
  backend.

shield Release v0.6.5

New Features

• MySQL support has been added to SHIELD.
• The API and CLI now support exact-name-matching when doing searches,
  to aid in automation when multiple targets/stores/jobs/etc match the
  name of another.

shield Release v0.6.4

Improvements

• When the WebUI prints target/store configuration, it will now pretty-print the JSON.
• When running an adhoc backup job, or restore, the CLI and APIs
  now return the UUID of the created task, to allow users and scripts to
  more easily identify what task was created to watch its logs.
• make dev and the testdev script received a number of enhancements for
  making life easier with developing shield.

Bug Fixes

• Fixed an issue where authorized headers weren't being properly passed
  if a user had not been authenticated prior to sending a PUT/POST request
  to the API.
• Fixed issue where the exclude option to the fs plugin's backups was
  including instead of excluding.

v0.6.3.0 Release

• Fixes a bug with the Postgres restore plugin where the restore would fail if any given line in the dump file was too long.
• Fixes a bug where an initial run of create backend would fail if the user's home directory was on a different filesystem than /tmp.
• The backend name is now displayed in the CLI when executing a command, in addition to its IP.
• The help dialogues for the backend commands now give the flags required.
• The shield plugins will no longer display the endpoint argument (potentially along with credentials contained within) in the process name.

v0.6.2.0 Release

Added the scality plugin. It's like the S3 plugin, only it actually works with Scality.
Eliminated configuration leakage through process args during plugin execution.

v0.5 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 `shield daemon
• Upon restart of shield-daemon, any pending tasks are re-started, 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.

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.

v0.4.1

Enhancements:

• Added the ability to focus mysql backups/restores on a specific database
• 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 v0.4

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

v0.3 SHIELD Release!

Lots of bug fixes (too many to name)

Adds a mysql target plugin
Adds support for running backups hourly
Improved CLI experience