0% found this document useful (0 votes)
19 views3 pages

MDE - Release Notes

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views3 pages

MDE - Release Notes

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

RELEASE 1.2.

Manufacturing Data Engine


Release Notes
Public

Table of Contents Applicable versions


Release History See each release below
Release 1.2.0
Applicable Versions
Document information
Status: Final
What is New? Last updated: Nov 9, 2022
Deployment Changes and Restrictions
Release 1.1.2 Intended audience
Applicable Versions Googlers, Partners, Customers
What is New?
Things to Notice During Deployment
Contact for questions
[email protected]
Release 1.1.0
What is New? Other documents
documentation/pdf/Deployment Guide.pdf
documentation/pdf/MDE - Configuration Guide.pdf
documentation/pdf/Release Notes.pdf
documentation/pdf/User Guide.pdf
documentation/pdf/Default Kit - Postman Getting Started.pd
documentation/pdf/Whistle V2 Documentation.pdf
documentation/pdf/Troubleshooting Guide.pdf

Manufacturing Connect - Supported Protocols


LEM-UserGuide-v2.3.2-PDF.pdf
LE-UserGuide-v3.2.5-PDF.pdf

Glossary of terms
documentation/pdf/MDE - Glossary of Terms.pdf

Copyright 2022 Google LLC Page 1 of 3


Release History

Release 1.2.0

Applicable Versions
● MDE 1.2.0-120
● MC 2.6

What is New?

● Introduced versioning control tables and labels to the solution storage elements such as BigQuery and
CloudSQL. This enables MDE to check the compatibility of the deployment and avoid unexpected problems.
● Upgradeability scripts, simplifying the transformations of required schema, configuration and data series
changes changes as well as re-deployment of upgraded compute artifacts like dataflow jobs, or GKE workloads
● Introduced the ability to export and import configurations from MDE config-manager components. The exported
configuration is stored into a GCS bucket which can be used to import configuration to another environment, if
both environments are on the same level of 1.2.0.
● This release uses BigQuery JSON columns natively, and it provides an upgrade script that enables this feature by
default on existing deployments. For new deployments, the BigQuery JSON feature is enabled by default. You
will need to run the upgrade script before deploying 1.2.0 release
● Multiple stability improvements and better troubleshooting logs/tools
● Introduced an operational dashboard for error reporting and performance monitoring
● Introduced the ability to dynamically subscribe to tag streams via Pub/Sub. You can enable/disable the
subscription by adding a new transformer on the type level, and it will automatically send the tags belonging to
that type to a pub/sub. This enable further extensibility to MDE by subscribing to a particular list of tags to do
further processing
● This release also includes alpha features for enabling anomaly detection, and it is enabled in a closed preview
mode through the solution team. Please contact the manufacturing solutions team if you have a business case
and would like to enable this feature.

Deployment Changes and Restrictions


● For the import/export feature of MDE configuration, the solution needs a new GCS bucket that is included in the
deployment Terraform script, and the bucket must exist in the same multi-region as BigQuery. For example, for
US deployment, both BigQuery and this GCS bucket must exist in the US multi-region, and the same for Europe.
● The upgrade procedure requires service account key exported as json
● The upgrade procedure doesn’t support rollback to previous the version

Release 1.1.2

Applicable Versions
● MDE 1.1.2-110
● MC 2.5

What is New?

● Introduced the ability for the config-manager and federation-api to connect to a BigQuery instance outside the
project where they are deployed. You will need to specify the extra attribute sfp_bigquery_project_id to the project
ID of BigQuery.
● Simplified the load-balancer provisioning by using TCP/UDP internal load-balancer instead of proxy-based for all of the
exposed services. This simplifies the network subnet requirements and firewall rules to enable the proxy-based
load-balancers to work.

Copyright 2022 Google LLC Page 2 of 3


● Removed dependencies on the IoT Core APIs after the service planned deprecation.
● Several documentation updates including the configuration guide, deployment guide, troubleshooting guide, and user
guide.
● Introduced a proxy compute instance to connect to the config-manager and the federation-api from the developer
workstation using only the private IPs, and there is no need to enable public IPs for the services. You can check the
deployment guide for more details about how to use the proxy.

Things to Notice During Deployment


● When you run the terraform for deployments, you will need to add an additional required variable in this release 1.1.2
which was not required in the previous release. The required variable is sfp_bigquery_project_id and you can set it
to the same project ID you’re using to deploy the solution, or another project where the BigQuery dataset is created.
The deployment guide is updated with this variable.

Release 1.1.0

What is New?
● New Features
○ Metadata management UI: Fully supported integration with Manufacturing Connect (cloud app)
○ Metadata Learning Mode: Automatically infers metadata buckets and schemas based on data from the edge
○ Metadata Domain Files: More control over the metadata validation
○ Observability & Error Reporting using both Stackdriver and BigQuery operational table for improved
observability and error reporting
○ Enabled delete operation via API for Payloads, Parsers, and Domain Files
○ Introducing two deployment size options:
■ Small deployment: Supports up to 1k msg/s with single Dataflow workers jobs. Suitable for proof of
concept environments and small deployment sizes.
■ Medium deployment: Supports up to 50k msg/s based on multiple Dataflow workers
■ Large deployment option is available as preview on request (with up to 100k msg/s validated)
● General Improvements
○ Optimized deployment size with a 66% reduction vs. previous version
○ Improved performance and efficiency utilizing the same resource footprint (tested with up to 100k msg/s)
○ Various stability improvements and bug fixes
○ Various additional security measures implemented
○ Various cost optimization measures (e.g., reduced logging volume outside debug mode, filters on PubSub to
optimize DataFlow processing)

Copyright 2022 Google LLC Page 3 of 3

You might also like