Version 2.0.0 beta - Release Candidate 4

The major changes in this release is a bug-fix that prevented connecting to Anvil! systems that were behind the same external IP using different ports for port forwarding. Also added a check that errors out is a striker.conf points to the same ScanCore database twice.

Version 2.0.0 beta - Release Candidate 3

The main change in this release is a change to how Media Library downloads files directly onto an Anvil! system. Previously, it called wget directly, but no progress was shown and that caused very large downloads (and/or very slow downloads) to complete in the background without telling the user. To handle this, Media Library uses a new tool to download the URL in the background and the user is shows a reloading progress.

In addition, registering with Red Hat will use the requested host name, instead of the initial default one. A new '--withdraw-only' has been added to anvil-safe-start, making it more useful for admins who want to quickly withdraw a node for maintenance.

So much for no more changes. >_>

Version 2.0.0 beta - Release Candidate 2

RC1 had a compile error. This release candidate fixes it. Other changes clean up the ISO and USB installers.

Version 2.0.0 beta - Test Candidate 9

This release will, with luck, be the final test release. Barring major issues, the next release will start the beta release candidate phase.

• Fixed OS updating in striker-installer and Install Manifest.
• Cleaned up footer printing in AN->nice_exit().

Version 2.0.0 beta - Release Candidate 1

This marks the start of the beta Release Candidate phase.

No major issues found from TC9 and all open 'pre-v2.0' bugs are now closed.

Version 2.0.0 beta - Test Candidate 8

The major changes in this release is much improved support when running Install Manifest against a good node and a rebuilt/replaced node. Now, InstallManifest will effectively mark a node that is hosting one of more servers as 'read-only'. The only change that will be make to that node will be the update of the peer's SSH details. Also updated to better reconfigure Striker's virt-manager (and backing SSH stuff) to handle a replacement node without user interaction.

NOTE: Supersedes the now-deleted tc7 which had a compile-time error in it.

Version 2.0.0 beta - Test Candidate 6

** This update includes very important bug fixes. Anyone who installed earlier versions is advised to reinstall.

• Very large SQL transactions are now split into chunks of 'sys::db::maximum_batch_size' transaction per commit to avoid eating too much memory during very large database resyncs.
• Fixed a bug in calculating how much RAM is being used by ScanCore (including shared memory, still).
• Added a new '--host-uuid X' switch to 'striker-installer' to allow for pre-defined (or restored) host UUIDs, useful for rebuilding or replacing a Striker dashboard machine to keep the old instance's ScanCore data linked to the rebuilt system.
• Created a dumb 'striker-drop-scancore-data' debug/test tool to wipe a dashboard's ScanCore DB of data generated by agents. This allows "resetting" agents on a dashboard, forcing a resync (if the other dashboard(s) aren't wiped).
• Fixed bugs in scan-storcli related to "Unconfigured Good" drives that aren't in a drive group or virtual drive.

Version 2.0.0 beta - Test Candidate 5

This test candidate rolls up several bug fixes related to display issues, foreign PID detection, memory management during resynchronisation tasks and cold-stop optimisations.

A fresh install is recommended for users running prior versions.

Version 2.0.0 beta - Test Candidate 4

This fixes a bug in anvil-safe-stop where load shedding would fail to migrate the server because both nodes were in a warning state. This also fixes several display bugs.

Version 2.0.0 beta - Test Candidate 3

This update fixes a flaw in the striker-installer script when the source is in 'striker-master' instead of just 'striker'. Otherwise it is tc2.