Sap Se

Daniel Kirmse

Henning Zahn

Michael Kutik

Joerg Lenhard

Cora Glass

Henrik Hempelmann

Martin Brunzema

Ivan T Bowman

Anne Roessiger

Stefan Voss

Nathan Auch

Benedikt Klus

Various examples are directed to systems and methods for upgrading a cloud-implemented application. A cloud service may receive a request from a user group to access the application. The cloud service may access consumer context data comprising a plurality of context properties of the user group and may access a rollout strategy map comprising a first rollout record. The cloud service may compare the plurality of context properties of the first user group to first selector data indicated by a first rollout record. Based on the comparing, the cloud service may add the first version of the application to a list of permissible versions for the first user group.

Cloud version management for legacy on-premise application

Various examples described herein are directed to systems and methods for managing a cloud-implemented database management application, the method comprising. At least one cloud service may receive a request from a first user group to launch a first instance of the database management application. The at least one cloud service may access a version metadata record for the database management application and use the version metadata record to launch the first instance of the database management application. The at least one cloud service may store first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application. The first instance metadata may comprise an indication of the first container image.

Cloud application management using instance metadata

A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker® container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Multiple versions of on-premises legacy application in a microservices environment

Various examples are directed to systems and methods for installing a plugin to a cloud-implemented database management application. A shared container file system may be initiated at a cloud environment. A plugin container image may be accessed, where the plugin container image comprises plugin payload data describing a first plugin to the database management application and a copy executable. A plugin container may be started at the cloud environment, where the plugin container is based at least in part on the plugin container image. The plugin container may be mounted to the shared container file system. The copy executable may be executed to copy the plugin payload data to the shared container file system. The first plugin may be installed to a database management application instance executing at the cloud environment.

Container plugin for legacy on-premise application

In an example embodiment, a specialized software object, called a behavior toggle, is utilized for stateful applications in cloud environments. The behavior toggle, once enabled and used by an entity, is not able to be disabled anymore for that entity, other than by explicit migration. Unlike feature toggles, whose values are expressed using 'true' or “false” flags or the like, behavior toggles are enabled by specific version. Specifically, the value indicates which version of the behavior is enabled. The behavior toggle software objects may then be referenced by, or included in, other software objects, to utilize the behavior toggle software objects with the other software objects and have the behavior toggle be applied to the other software objects.

Behavior toggle for stateful applications

In an example embodiment, a solution is provided for a container-orchestration service that allows a custom resource to reflect an entire software application while still splitting the actual work out into independent microservices. Specifically, the concepts of an extendable controller and controller extensions are introduced. An extendable controller defines an extendable custom resource. This custom resource is still the main resource describing the entire application, but does so in a way that extensions are referenced that can be defined in their own resources (called extension resources). The extendable controller itself is surrounded by extension controllers, which are responsible for certain aspects of the system that need to be considered in atomic transactions, such as high-availability configuration or scale-out.

Extendable container-orchestration system controllers

Various examples are directed to systems and methods for upgrading a cloud-implemented database management application. A cloud service may receive a request from a first user group to upgrade the database management application for the first user group. The cloud service may determine a first version of the database management application used by the first user group and access an upgrade strategy map. Using the upgrade strategy map, the cloud service may determine a set of target versions of the database management application suitable for upgrading from the first version. The cloud service may access an indication of a selected target version from the set of target versions and initiate execution of a first instance of the selected target version for the first user group at the cloud environment. The first instance may access a first data persistence associated with the first user group.

Cloud upgrade for legacy on-premise application

Various examples are directed to systems and methods for managing a plugin at a cloud-implemented database management application. A service at the cloud environment may receive from a first user a request to install a first plugin to a database management application executing at the cloud environment in at least one container. The service may determine a build version of the database management application and access a plugin catalog record for the first plugin. The plugin catalog record may comprise an indication of a first plugin version associated with the build version of the database management application. The service may access first plugin version installation data and install the first plugin version.

Plugin version management for legacy on-premise application

In an example embodiment, a workflow engine is introduced within a cloud landscape. Runbooks re then implemented as workflow templates within the workflow engine. The workflow engine allows for creation of workflows from the workflow templates as well as composing workflows from individual steps. The workflow engine provides a mechanism to describe workflow templates and workflow sets as code.

Secure operations of cloud landscapes through workflow templates

Various examples described herein are directed to systems and methods for managing a cloud-implemented database management application. A frontend service executing at a cloud environment may receive a plugin request from a first user associated with a first user group and determine a version of a database management application executing at the cloud environment for the first user group. The frontend service may access a plugin catalog to determine at least one plugin compatible with the database management application and provide an indication of the at least one plugin to the first user. The frontend service may receive from the first user a selection of a first plugin from the at least one plugin and call a plugin installer service executing at the cloud environment to install the first plugin to the database management application.

Cloud plugin for legacy on-premise application

In an example embodiment, an additional interface customer resource definition (CRD), which operates in conjunction with the normal CRD, is utilized. The interface CRD may be called a service CRD. The service CRD provides an abstraction of the original CRD by abstracting away all technical details that no other services should depend upon. The service CRD provides a fa&#xe7;ade to the original CRD. Both are kept in sync by a component called an operator, which infers the specification of the original CRD on the basis of the specification of a given service CRD. Furthermore, status updates sent to the original CRD that are relevant to the dependent services are mirrored back to the corresponding service CRD. Correspondingly, status updates with technical details that are too specific for the dependent services are not mirrored back.

Interface custom resource definition for stateful service management of clusters

In an example embodiment, a solution is provided that causes a binary used by an in-memory database application to be deployed in a separate container. The container with the binary may be called a 'sidecar' to the container with the in-memory database application. Both containers mount the same path in the hosts shared filesystem to expose the binary to the application. There is no permanent connection between the two containers, and thus the binary can be updated individually without inducing a downtime of the in-memory database application.

External binary sidecar for cloud containers

Disclosed herein are system, method, and computer program product embodiments for disaster resilience of applications managed by Kubernetes operators. An embodiment operates by creating an orchestration and worker cluster, where the worker cluster is coupled to the orchestration cluster by a proxy server. Custom resources are deployed to the orchestration cluster and custom resource controllers are deployed to the worker cluster. The proxy server federates these custom resources between the orchestration cluster and the worker cluster. During disasters, the worker cluster is recreated and reconciled to prevent loss of the federated cluster.

Disaster resilient federated kubernetes operator

A data structure called a product version map is introduced. The product version map contains a catalog of available application versions to be used by the application orchestration services. It can describe the available versions. For each version, there is an image, such as a Docker&#xae; container image, that can be used to instantiate the application instance. Furthermore, in some example embodiments, an expiration date can be given, which could be used to enforce upgrades of application instances when their used version expires.

Growing community of inventors

Berlin, Germany

Daniel Kirmse