Mechanism for deploying legacy applications on new generation hyperscalers

Patent metadata

Field	Value
Publication number	US-11977870-B2
Application number	US-202217820194-A
Country	US
Kind code	B2
Filing date	Aug 16, 2022
Priority date	Apr 3, 2020
Publication date	May 7, 2024
Grant date	May 7, 2024

Abstract

In some implementations, there is provided a method including determining whether a topology description includes a static physical host name and a static port address; in response to determining the topology description includes the static physical host name and the static port address, converting at least the topology description into a deployment file; including, in a container, the deployment file, code, and a control script that limits pre-start database operations to a single node of a plurality of nodes of a cloud platform; and deploying, the container including the deployment file, the code, and the control script, to the cloud platform to form, at the cloud platform, the plurality of nodes including the single node. Related systems and articles of manufacture are also disclosed.

First claim

What is claimed:

1. A system comprising:
at least one processor; and
at least one memory including code which when executed by the at least one processor causes operations comprising:
in response to determining a topology description includes a static physical host name and/or a static port address, converting the topology description into a deployment file for use at a cloud platform associated with a hyperscaler and/or a deployment orchestrator that do not allow use of the static physical host name and/or the static port address; and
deploying, a container including the deployment file to form, at the cloud platform associated with the hyperscaler and/or the deployment orchestrator, a plurality of nodes of a database system.

2. The system of claim 1 , wherein the container further includes a control script that limits at least one database operation to a single node of the plurality of nodes.

3. The system of claim 2 , wherein the at least one database operation comprises a pre-start database operation to be executed only once at database initialization of the database system.

4. The system of claim 2 , wherein the control script includes a lock and key process to limit the at least one database operation to the single node of the plurality of nodes.

5. The system of claim 1 , further comprising:
determining whether the hyperscaler and/or the deployment orchestrator do not allow the use of the static physical host name and/or the static port address.

6. The system of claim 5 , wherein in response to determining the cloud platform does allow the use of the static physical host name and/or the static port address, deploying the topology description and code to the cloud platform.

7. The system of claim 6 , in response to determining the cloud platform does allow the use of the static physical host name and/or the static port address, by-passing at least the converting and the deploying of the container including the deployment file.

8. The system of claim 1 , wherein the deployment file is configured to be deployed by the deployment orchestrator associated with the cloud platform.

9. The system of claim 1 , wherein the deployment file describes a deployment architecture of a service at the cloud platform.

10. The system of claim 1 , wherein the deployment file includes one or more roles for the plurality of nodes, and wherein at least one of the one or more roles provides a user interface for accessing the database system.

11. The system of claim 1 , wherein the deployment file includes node names for the plurality of nodes to enable communications among the plurality of nodes.

12. A computer-implemented method comprising:
in response to determining a topology description includes a static physical host name and/or a static port address, converting the topology description into a deployment file for use at a cloud platform associated with a hyperscaler and/or a deployment orchestrator that do not allow use of the static physical host name and/or the static port address; and
deploying, a container including the deployment file to form, at the cloud platform associated with the hyperscaler and/or the deployment orchestrator, a plurality of nodes of a database system.

13. The computer-implemented method of claim 12 , wherein the container further includes a control script that limits at least one database operation to a single node of the plurality of nodes.

14. The computer-implemented method of claim 13 , wherein the at least one database operation comprises a pre-start database operation to be executed only once at database initialization of the database system.

15. The computer-implemented method of claim 13 , wherein the control script includes a lock and key process to limit the at least one database operation to the single node of the plurality of nodes.

16. The computer-implemented method of claim 12 , further comprising:
determining whether the hyperscaler and/or the deployment orchestrator do not allow the use of the static physical host name and/or the static port address.

17. The computer-implemented method of claim 16 , wherein in response to determining the cloud platform does allow the use of the static physical host name and/or the static port address, deploying the topology description and code to the cloud platform.

18. The computer-implemented method of claim 16 , in response to determining the cloud platform does allow the use of the static physical host name and/or the static port address, by-passing at least the converting and the deploying of the container including the deployment file.

19. The computer-implemented method of claim 12 , wherein the deployment file is configured to be deployed by the deployment orchestrator associated with the cloud platform.

20. A non-transitory computer readable storage medium including code which when executed by at least one processor causes operations comprising:
in response to determining a topology description includes a static physical host name and/or a static port address, converting the topology description into a deployment file for use at a cloud platform associated with a hyperscaler and/or a deployment orchestrator that do not allow use of the static physical host name and/or the static port address; and
deploying, a container including the deployment file to form, at the cloud platform associated with the hyperscaler and/or the deployment orchestrator, a plurality of nodes of a database system.

Assignees

• Sap Se

Inventors

• Banerjee Rick
• Joshi Himanshu
• Dinakar Sujith Henamagalur

Classifications

• H04L41/40

  using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title

• G06F8/60 Primary

  Software deployment · CPC title

• H04L41/12 Primary

  Discovery or management of network topologies · CPC title

• G06F8/41

  Compilation · CPC title

• G06F16/252

  between a Database Management System and a front-end application · CPC title