MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

Cloud Foundry

What's new?

Within this release we the following buildpacks and updates are available:


































Known issues

  • Upgrading single Logme, MongoDB 3.2 and PostgreSQL 9.4 Backing Services instances to clustered instances is not possible.

Additional Information

  • CF Stack

    • CFlinuxFS2 Stack is deprecated and planned to be removed from cloud Foundry at end of May 2020. Apps running on cflinuxfs2 stack will not run anymore.

    • DotNet BuildpackNext DotNet buildpack update will not support DotNet 3.0 anymore.

Container Registry

What's new?

Container Registry is now available.

Container Registry enables you to accelerate development, simplify storing and managing images, and reduce operations efforts. It offers an effective way to deploy, manage, and scale containerized solutions.
Applications running on Kubernetes or any container orchestration engine are compatible and can be easily migrated to MindSphere to participate in the MindSphere ecosystem.
Container Registry application is a part of the MindSphere platform, and you can access it from the MindSphere launchpad.
A third-party software called Harbor is integrated in Container Registry. It allows the customers to  deploy their applications quickly and scale them as required. You can decide between a high and non-high available version.

Using the Container Registry application, you can:

● Create new projects and (view/see) existing projects and their content
● Create Robot Accounts
● Tag and push images into Container Registry
● View log information of operations performed in Container Registry
     – Global log: Logs which include all projects and repositories
     – Project log: Project specific logs
● Create, edit and delete registry endpoints and replication rules
● Configure global settings
● Enable content trust
● Check common Vulnerabilities and Exposures (CVE)

Data Flow Engine

Known issues

  • Sporadically streams cannot be deleted. Please try again if it was unsuccessful.

  • If an entity is derived from type core.basicdevice only one stream can be deployed.

Identity and Access Management

Known issues

  • If you have problems logging off in Internet Explorer 11, please refer to Overcoming Logout Problems in IE11. 

  • After a user's permissions have been changed using the Identity Management Service, the change is not immediately visible. The user must close the browser and log in again.

IoT and Storage Services: File Service

Known issues

  • For security reasons a strict timeout is enforced. Currently, this leads to the situation that the size of a file which can be uploaded/ downloaded depends on the network bandwidth at client side.

  • When uploading files to the File Service, a file name cannot contain blank spaces. Blank spaces in the file name will prevent the file form being stored.

  • After deleting an asset, associated files might still be accessible for up to 30 minutes as this data is deleted asynchronously.

  • After deleting a file, it will take some time (up to 60 seconds) to create the file with the same name again.

  • After creating or deleting the file, it will take some time (up to 3 seconds) to get the file in "search file" API. 

IoT and Storage Services: Time Series Service

Known issues

  • The maximum payload size of a message sent to Time Series Service as part of a PUT request cannot exceed 1 MB.

  • The service will never return more than 2000 records in a response.

  • After deleting an asset, respective time series data might still be accessible for up to 30 minutes as this data is deleted asynchronously.

  • When getting the job status of a bulk import job, the response might not always contain detailed information on errors that occurred.

  • When creating or updating an aspect it might take up to 30 minutes until aggregated data can be read for this aspect. Writing data or reading raw data is possible immediately.

  • When ingesting time series data for multiple asset and aspects in single request, the combination of records should be unique.

  • Get Latest Value with query parameter "latestValue = true" will work with a delay up to 2 hours from the time of ingestion. Refer to developer documentation 'sample' section for more information.

  • While using Get Latest Value with query parameter  "latestValue = true", historic/late arriving data may take more than 1 day to reflect in the response.