Major Changes and New Features Summary. All changes are cloud only.

Future S3 failures will not cause an LPS system outage.

Two "hard dependencies" on S3 in the critical path of device/server communication have been removed. In the event of a future S3 outage only features that are critically dependent upon S3 such as Media Library should be impacted.

Mission Control is now launched from a separate URL.

Mission Control is now deployed as a standalone application, allowing for releases separate from the cloud platform releases in the future. Please contact your Liquid account manager for detailed instructions on launching the new MC.

Mission Control charts now support a range selector.

Charts in Mission Control that previously only showed 7-day data now support 1, 3, 7, and 30 day data via a range selector.

Setting user passwords for other users now uses a tiered authorization structure.

Previously any user with access to set passwords for other users could use this function to reset any passwords, including higher level administrators. This functionality is now restricted using a hierarchical set of permissions.

OpenAPI related enhancements

The OpenAPI Schema exposed by LPS now has added information for use by tools such as ReDoc.

Change Log. All changes are cloud only.

1. Fixed a bug that would cause MC to fail using the Function Testing panel if no functions were available to test.
2. The "highest load" and "pause percent" displays in MC are now more nicely formatted.
3. A bug has been resolved that would sometimes prevent MC from starting up when local configuration was corrupted.
4. Passthrough functions now support OAuth2 compliant authorization.
5. The CSV Import function now has enhanced error messages.
6. A predictive entitlements bug has been resolved that caused unnecessary increased database load.

Risks and Known Issues

No known risks or issues.

Maintenance Window

This server deployment does not require a maintenance window.

Special Deployment Notes

Release Schedule

Date	Environment
3/8/2017	ProdB
3/9/2017	Prod

#ProdB Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in ProdB:

1. In settings change the server URL to https://ldcloud-b.liquidanalytics.com
2. Perform exploratory testing
3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
   • Sync
   • Transactions
   • Registrations
   • Authentication
   • On-demand functions
   • Queries

#Prod Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in Prod:

1. In settings make sure the server URL is https://ldcloud.liquidanalytics.com
2. Perform exploratory testing
3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
   • Sync
   • Transactions
   • Registrations
   • Authentication
   • On-demand functions
   • Queries

A note on the AWS S3 outage on February 28.

AWS was offline for the majority of the afternoon on February 28. Liquid’s infrastructure is split across multiple zones for redundancy and DR. S3 is a software service that is the industry standard for storing files and is provided as a redundant service across all zones and regions. The last time that AWS experienced an S3 outage was 8 years ago.
As we are always seeking to improve our performance and stability, we are using this opportunity to evaluate our dependency on other AWS services. We will develop internal best practices to ensure that we do not have a system outage if an AWS service fails. You will notice improvements in future releases. We apologize for this inconvenience.