Interface custom resource definition for stateful service management of clusters

Patent metadata

Field	Value
Publication number	US-11544289-B2
Application number	US-202016890912-A
Country	US
Kind code	B2
Filing date	Jun 2, 2020
Priority date	Jun 2, 2020
Publication date	Jan 3, 2023
Grant date	Jan 3, 2023

Abstract

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ç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.

First claim

What is claimed is:

1. A system comprising:
at least one hardware processor; and
a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
reading, by an in-memory database controller, a specification from an in-memory database service custom resource definition (CRD);
inserting, by the in-memory database controller, one or more attributes from the specification into an in-memory database CRD;
monitoring for status messages from an instance of an in-memory database; and
for each of one or more status messages generated from the instance of the in-memory database:
determining if a type for the status message is defined by the in-memory database controller as a type that is not to be mirrored back to the in-memory database service custom resource definition; and
in response to a determination that the type for the status message is not defined as a type that is not to be mirrored back to the in-memory database service CRD, causing a message to be generated and sent to an in-memory database service controller corresponding to the in-memory database service CRD, the message including a second status message.

2. The system of claim 1 , wherein the in-memory database service controller reads the specification from the in-memory database service CRD and runs one or more components based on the specification.

3. The system of claim 2 , wherein the one or more components read one or more mirrored status messages and generate status reports based upon the one or more mirrored status messages.

4. The system of claim 1 , wherein the in-memory database service CRD is created by a service that is dependent on the instance of the in-memory database.

5. The system of claim 1 , wherein the in-memory database controller manages the instance of the in-memory database based on the in-memory database CRD.

6. The system of claim 5 , wherein the operations further comprise, for each of the one or more status messages:
determining whether values for all conditions, defined in the in-memory database CRD, of the status message are true; and
wherein the causing a message to be generated and sent to the in-memory database service controller corresponding to the in-memory database service CRD is also performed in response to the determination that the values for all conditions, defined in the in-memory database CRD, are true.

7. The system of claim 6 , wherein the conditions include that all components are ready.

8. A method comprising:
reading, by an in-memory database controller, a specification from an in-memory database service custom resource definition (CRD);
inserting, by the in-memory database controller, one or more attributes from the specification into an in-memory database CRD;
monitoring for status messages from an instance of an in-memory database; and
for each of one or more status messages generated from the instance of the in-memory database:
determining if a type for the status message is defined by the in-memory database controller as a type that is not to be mirrored back to the in-memory database service custom resource definition; and
in response to a determination that the type for the status message is not defined as a type that is not to be mirrored back to the in-memory database service CRD, causing a message to be generated and sent to an in-memory database service controller corresponding to the in-memory database service CRD, the message including a second status message.

9. The method of claim 8 , wherein the in-memory database service controller reads the specification from the in-memory database service CRD and runs one or more components based on the specification.

10. The method of claim 9 , wherein the one or more components read one or more mirrored status messages and generate status reports based upon the one or more mirrored status messages.

11. The method of claim 8 , wherein the in-memory database service CRD is created by a service that is dependent on the instance of the in-memory database.

12. The method of claim 8 , wherein the in-memory database controller manages the instance of the in-memory database based on the in-memory database CRD.

13. The method of claim 12 , further comprising, for each of the one or more status messages:
determining whether values for all conditions, defined in the in-memory database CRD, of the status message are true; and
wherein the causing a message to be generated and sent to the in-memory database service controller corresponding to the in-memory database service CRD is also performed in response to the determination that the values for all conditions, defined in the in-memory database CRD, are true.

14. The method of claim 13 , wherein the conditions include that all components are ready.

15. A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
reading, by an in-memory database controller, a specification from an in-memory database service custom resource definition (CRD);
inserting, by the in-memory database controller, one or more attributes from the specification into an in-memory database CRD;
monitoring for status messages from an instance of an in-memory database; and
for each of one or more status messages generated from the instance of the in-memory database:
determining if a type for the status message is defined by the in-memory database controller as a type that is not to be mirrored back to the in-memory database service custom resource definition; and
in response to a determination that the type for the status message is not defined as a type that is not to be mirrored back to the in-memory database service CRD, causing a message to be generated and sent to an in-memory database service controller corresponding to the in-memory database service CRD, the message including a second status message.

16. The non-transitory machine-readable medium storing instructions of claim 15 , wherein the in-memory database service controller reads the specification from the in-memory database service CRD and runs one or more components based on the specification.

17. The non-transitory machine-readable medium storing instructions of claim 16 , wherein the one or more components read one or more mirrored status messages and generate status reports based upon the one or more mirrored status messages.

18. The non-transitory machine-readable medium storing instructions of claim 15 , wherein the in-memory database service CRD is created by a service that is dependent on the instance of the in-memory database.

19. The non-transitory machine-readable medium storing instructions of claim 15 , wherein the in-memory database controller manages the instance of the in-memory database based on the in-memory database CRD.

20. The non-transitory machine-readable medium storing instructions of claim 19 , wherein the operations further comprise, for each of the one or more status messages:
determining whether values for all conditions, defined in the in-memory database CRD, of the status message are true; and
wherein the causing a message to be generated and sent to the in-memory database service controller corresponding to the in-memory database service CRD is also performed in response to the determination that the values for all conditions, defined in the in-memory database CRD, are true.

Assignees

• Sap Se

Inventors

• Lenhard Joerg
• Kirmse Daniel

Classifications

• G06F16/2379 Primary

  Updates performed during online database operations; commit processing · CPC title

• G06F16/273 Primary

  Asynchronous replication or reconciliation · CPC title