Preparing your system for AMP - what you need to know

AMP is due to release this week. Because of the changes that are being made to AMPs release system, there’s a few things you’ll need to know:

Take a backup!

This update has significant under-the-hood changes. As such, we advise taking a full system backup if possible (or at the absolute least, a copy of your AMP datastore(s)) so that you can roll back if anything goes wrong. Those of you running AMP in a VM we recommend taking a system snapshot.

AMP system tools must be updated

The system tools (ampinstmgr on Linux, the instance manager on Windows) must be updated to use the latest version of AMP. This is required so that both the system tools and the new ADS version both support the new release system.

ADS will now warn you if ampinstmgr is out-of-date and that failing to update it could cause problems, along with a link to instructions on how to update it.

The Nightly, Bleeding and FastTrack release streams no longer exist.

After upgrading to AMP, your instances will be automatically swapped over to the new release streams.

Any instances that are configured as either “Bleeding” or “Nightly” will be automatically switched over to the Development stream. FastTrack instances will be switched over to “Mainline”.

LTS will be immediately moved up to

Because the new release system can’t address AMP versions that were from before the new release system existed, this means that LTS installations will need to upgrade promptly.

Network Edition now supports version matching

Previously exclusive to Enterprise Edition, users with Network Edition will gain the ability to have ADS only create instances that match the same version number as the ADS installation itself. In the near future there will also be a “Newest compatible version” option which may install a newer version, but only if it’s API compatible with ADS so that ADS and other instances don’t need upgrading.

1 Like