Cloud Foundry¶
Overview¶
Industrial IoT offers a managed runtime environment powered by Cloud Foundry to easily run own applications across all regions. The following features and Buildpacks are currently supported. This is subject to change and might be enriched over the time.
Note
- For the subscribers of Capability Packages: If you want to host your applications on Insights Hub, you must purchase the Cloud Foundry service as an add-on. For more information, refer to Product Sheet.
- Cloud Foundry is not applicable for Private Cloud.
| Feature | Description | Support/Status |
|---|---|---|
| Runtime | Cloud Foundry Runtime | Industrial IoT uses 2.9.x runtime with hardened stemcells |
| Buildpacks | The following Buildpacks are supported by Industrial IoT | Java, Node.js, .NET Core, Python, PHP, Go, Ruby, staticfile, binary and mendix |
| Custom Buildpacks | This Cloud Foundry feature allows to use custom buildpacks and different versions of a buildpack. See Using Custom Buildpack. | enabled |
| Backing Services | Backing Services can be data stores or other services that are provided by Industrial IoT. Every Backing Service is available as a single instance (for development) and as a clustered high-available version for productive usage. | redis, postgresql, rabbitmq, elasticsearch, logme, |
| User Provided Services | This Cloud Foundry feature allows to integrate services from outside CF e.g. Kinesis. | enabled |
| Stack | Cloud Foundry supports multiple prebuilt root file systems | cflinuxfs4 (Since CF1.49 release, we have introduced cflinuxfs4, which is the default stack instead of cflinuxfs3. However, cflinuxfs3 will be removed in future releases.) |
| SSH | SSH enables connections to containers running your application and connecting database management tools | activated |
| SSO | Single-Sign-On - use your Insights Hub user account to access Cloud Foundry | activated |
Access Cloud Foundry¶
Use the official Cloud Foundry CLI for accessing your development environment. The API-endpoint is: https://api.cf.{region}.{mindsphere-domain}.
Initially only the original administrator of the MindAccess Developer or Operator Plan has administrator (called OrgManager) permissions for Cloud Foundry. If you want to give other users Cloud Foundry access permissions, you must use the Cloud Foundry command-line tool. Note that the Settings cannot be used to grant or remove these permissions.
Login
Industrial IoT comes with an Single-Sign-On mechanism which allows users logging in to Cloud Foundry an in to the environment with the same credentials. Read the Getting Started or Cloud Foundry documentation on how to log in to Cloud Foundry. There are no separate credentials required.
The following steps describe the procedure to check the supported version of Cloud Foundry buildpacks:
- Login to Cloud Foundry.
- Execute the command "cf marketplace" to check the supported buildpacks. To search for the specific buildpack version, refer https://github.com/cloudfoundry. The details about the supported programming language versions, refer the chapter "Packaged binaries".
- Use
^ ~inside thepackage.jsonfile to install a compatible or similar version.
Cloud Foundry Updates¶
In this section we describe the process of an Cloud Foundry update. Cloud Foundry implements a rolling update concept to avoid downtimes. During the update each component will be updated sequentially and restarted afterwards. Therefore, each Cloud Foundry component uses multiple instances (horizontal scaling) to ensure availability. Yet, this has implications of the duration of updates as those depend on the number of services and virtual machines to update.
The same principles as for the Cloud Foundry components also apply to applications running on top of Cloud Foundry. Therefore you must run at least two of an application to ensure high availability and reduce downtimes during update phases. During the Cloud Foundry update the virtual machine on which the application container is executed will be shutdown, updated and restarted. There will be a short downtime if you have only one instance running. Cloud Foundry will notice a problem with the application and will start another instance.
Benefits of Cloud Foundry¶
Why should I use Cloud Foundry? The following subsections and bullet points give a brief overview about the advantages of Cloud Foundry.
Structured platform¶
- Incorporates best practices for developing cloud software
- Proven to work in a practical way
- Reducing complexity due to standard procedures (e.g. service binding)
- Predefined procedures for deployment and app management that reduce operational effort
Easy and fast app development with focus on the business logic¶
- No need to care about underlying infrastructure, OS and runtime
- Out-of-the-box scaling, load-balancing, health management and configuration management
- Apps run in isolated containerized environments
Security by Industrial IoT¶
- Industrially hardened Stemcells
- Managed Buildpacks with a high level of security standard (e.g. CVE scanning)
- Managed Backing Services with automated backup capabilities (plan medium or higher)
- Separation of Concerns - clear separation of development and production environments
- Positive Security Concept for Applications and APIs
Operations efforts reduced¶
- Out of the box security, patch, backup, release management for the underlying layers
- Ensuring app compatibility during updates of OS and buildpacks
- Managed Cloud Foundry platform with zero downtime on a stable IaaS layer
Except where otherwise noted, content on this site is licensed under the Development License Agreement.