Skip to content

Release Notes

Announcements

Long Term Support Release

The Long Term Support (LTS) release of Open AMT Cloud Toolkit is official and is planned for September 2021. With the release of LTS, the version of Open AMT Cloud Toolkit and all of the components will be moving to 2.0.0. Why the major version change? During the 1.X development period, we made many breaking changes as we were improving our external interfaces, database schemas, and communication protocols. Starting with 2.0, we will no longer be introducing breaking changes in minor version releases. This means that any 2.X component will be compatible with other 2.X components. With this adherence to semantic versioning our goal is to allow our customers the flexibility to upgrade versions with confidence and clarity of compatibility.

RPC 1.3 release delayed

We are working on updating the version of CPPRestSDK used in RPC which will update the version of OpenSSL as a sub-dependency of CPPRestSDK. The next version of RPC will be released with our 2.0 LTS release.

Key Feature Changes for 1.5

This section outlines key features changes between versions 1.4 and 1.5 for Open AMT Cloud Toolkit.

Breaking Changes

  • Removed configuration_script column from profiles DB

Additions

Open AMT Cloud Toolkit

  • MQTT address configuration: To support the service events feature, we have add an option to the .env.template to configure the mqtt address.
  • Vault route added to Kong: We added a Vault route in the API Gateway. This facilitates direct calls to the secure key storage to retrieve data stored in Vault. RPS and MPS will not return any of the information that is stored in Vault in our REST API responses (security measure). However, there are certain times in which an ISV may want to retrieve this information. Vault has its own APIs and authentication model and calls using this route will need to implement per Vault's APIs.

RPS

  • Wireless Configuration: Added the capability to configure Intel® AMT with wireless profiles. This enables Intel® AMT to connect to a known wireless access point and establish a CIRA connection back to MPS. RPS has added a new Wireless Profile interface that allows adding and prioritizing multiple wireless profiles in the AMT Profile. These profiles are set during configuration of the Intel® AMT device. The new APIs are documented here
  • RPS Events: Continuing to improve our server event messages, we have instrumented RPS to send events to the MQTT broker in this release. Some of the events you can expect to see are devices successfully being configured, failures in configuration, and new profiles being added. As this feature is still early release, we continue to appreciate feedback on how we can improve this feature.

MPS & RPS

  • API Paging support: We have added the ability to limit the response size to a specific number. This allows UIs making queries to MPS and RPS to scope responses to page size.

UI Toolkit

  • Split up Core, React, and Angular code into different repositories: We have had quite a few requests to have an option to just deliver the core functionality of the UI-Toolkit without being wrapped in the React framework. To support this, we have split out the UI-Toolkit into three repositories: Core, React, and Angular. Both the React and Angular repositories pull from the Core to build the components in the specific ui framework.

Sample Web UI

  • UI updated to handle Wireless configurations: The Sample Web UI has been updated to support the new Wireless profile feature.

Modifications and Removals

Open AMT Cloud Toolkit

  • Removed postgresdb from helm charts: When deploying the Toolkit to Kubernetes, it is recommend to use a managed database service from the cloud service provider. With this in mind, we have removed the option to deploy the postgresdb container from our helm charts.

RPS

  • Profile API update: the ciraconfigname now accepts a null value now. This allows the removal of the CIRA config from a Profile.

Sample Web UI

  • Improvements: We have made some minor changes and improvements in the Sample Web UI to streamline profile creation and provide additional information on the devices page.
    • The UI now sets the password length for new random passwords, removing the need for the password length field in the CIRA Config and Profiles. The REST APIs still support user defined values from 8 to 32 for password length.
    • On the devices page, we have added the device hostname, GUID, and tags to help with easily finding this information for each device.
    • An Add New Device button has been added that will provide the exact RPC command needed to activate a device. You can copy this command and input it onto the command line of the device you are activating.

Resolved Issues in this release

MPS

Sample-Web-UI

Known Issues in 1.5

Intel® AMT

  • Intel® AMT device fails to re-connect to MPS after MPS is not available for an extended period of time: UPDATE: There is a firmware fix available for this issue, however, we are still testing to ensure that it completely resolves this issue. We'll let you know once this issue is resolved. If the MPS goes down for more than 2 days, Intel® AMT devices will no longer attempt to connect to MPS. If this happens, there are two ways to prompt Intel® AMT to attempt to re-connect to MPS:
    1. Unplug and re-plug the network cable
    2. Reboot the Intel® AMT device

Open AMT Cloud Toolkit

RPS

MPS

UI-Toolkit

  • KVM freeze intermittently: We have added a small delay in handling mouse interactions that prevents us from flooding the AMT channel. There are still a few occasions where KVM could still freeze. We are still root causing this new issue

Sample-Web-UI

Back to top