Service fabrication tool

Patent metadata

Field	Value
Publication number	US-2022012045-A1
Application number	US-202017002616-A
Country	US
Kind code	A1
Filing date	Aug 25, 2020
Priority date	Jul 13, 2020
Publication date	Jan 13, 2022
Grant date	—

Abstract

Disclosed embodiments include a Custom Resource Abstraction and Fabrication Tool (CRAFT) that declares operators in a robust, idempotent, and generic manner for any resource. In embodiments, a developer can run create, read, update, and delete (CRUD) operations on resources in any language. The developer can create configuration files that is used by CRAFT to generate and deploy application container with the operator according to the configuration files. Other embodiments may be described and/or claimed.

First claim

1 . One or more non-transitory computer-readable storage media (NTCRSM) comprising instructions, wherein execution of the instructions is operable to cause a computing system to:
receive a request to generate an application for providing a service, the request including or indicating one or more configurations, the one or more configurations indicating application requirements for the application that is to be generated; generate, using the one or more configurations, each of an operator file, an operator container image, and a controller container image; create a container on a computing cluster using the operator container image and the controller container image; and deploy an operator into the container using information contained in the operator file, the operator including code to perform one or more operations according to the application requirements.

2 . The one or more NTCRSM of claim 1 , wherein the request is received via an application programming interface (API), a command file, or a declarative manifest.

3 . The one or more NTCRSM of claim 2 , wherein the API includes a Kubernetes API, the command file includes a kubectl imperative command, or the declarative manifest includes a YAML file.

4 . The one or more NTCRSM of claim 1 , wherein the one or more configurations include a controller file and a resource file.

5 . The one or more NTCRSM of claim 4 , wherein the controller file includes custom resource definition (CRD), the CRD indicating one or more of a group, domain, operator image, and reconciliation frequency.

6 . The one or more NTCRSM of claim 5 , wherein the resource file includes schema information for validating inputs while creating the CRD.

7 . The one or more NTCRSM of claim 4 , wherein execution of the instructions is further to operable to cause the computing system to:
generate the controller container image using the controller file, the controller container image including service dependency files.

8 . The one or more NTCRSM of claim 1 , wherein execution of the instructions is further to operable to cause the computing system to:
generate the operator using the one or more configurations and the controller container image.

9 . The one or more NTCRSM of claim 1 , wherein the one or more configurations are stored in a version control system or a source code repository.

10 . The one or more NTCRSM of claim 1 , wherein the application requirements include one or more of a compile time, a build time, and a run time of the service.

11 . The one or more NTCRSM of claim 1 , wherein execution of the instructions is further to operable to cause the computing system to:
identify one or more operational status codes in response to performance of the one or more operations of the operator; and determine one or more actions to improve the performance of the one or more operations based on the identified operational status codes.

12 . The one or more NTCRSM of claim 11 , wherein the one or more actions are based on a time when respective status codes of the one or more operational status codes are generated.

13 . The one or more NTCRSM of claim 11 , wherein execution of the instructions is further to operable to cause the computing system to:
map the one or more operational status codes to respective messages, the respective messages including a notification or an instruction of a corresponding action of the one or more actions; and provide the respective messages to a user associated with the service.

14 . The one or more NTCRSM of claim 11 , wherein the operational status codes include one or more of run time status codes, build time status codes, and compile time status codes,
the run time status codes include one or more of errors generated by components, logs generated by components, or state changes of components, the build time status codes include one or more of semantic errors, dependency errors, packaging errors, or pipeline errors, and the compile time status codes include one or more of schema errors or input errors.

15 . A computing system comprising:
a network interface configurable to receive a request to generate an application for providing a service, the request including or indicating one or more configurations, the one or more configurations indicating application requirements for the application that is to be generated; and a processor system communicatively coupled with the network interface, the processor system configurable to:
generate, using the one or more configurations, each of an operator file, an operator container image, and a controller container image;
create a container on a computing cluster using the operator container image and the controller container image; and
deploy an operator into the container using information contained in the operator file, the operator including program code to perform one or more operations according to the application requirements.

16 . The application server of claim 15 , wherein the one or more configurations include a controller file and a resource file, the controller file including a custom resource definition (CRD), and the resource file including schema information for validating inputs while creating the CRD.

17 . The application server of claim 16 , wherein the processor system is configurable to:
generate the controller container image using the controller file, the controller container image including service dependency files; and generate the operator using the controller file, the resource file, and the controller container image.

18 . The application server of claim 15 , wherein the application requirements include one or more of a compile time, a build time, and a run time of the service.

19 . The application server of claim 15 , wherein the processor system is configurable to:
identify one or more operational status codes in response to performance of the one or more operations of the operator; determine one or more actions to improve the performance of the one or more operations based on the identified operational status codes; map the one or more operational status codes to respective messages, the respective messages including a notification or an instruction of a corresponding action of the one or more actions; and provide the respective messages to a user associated with the service.

20 . The application server of claim 19 , wherein the operational status codes include one or more of:
run time status codes, the run time status codes including one or more of errors generated by components, logs generated by components, or state changes of components; build time status codes, the build time status codes including one or more of semantic errors, dependency errors, packaging errors, or pipeline errors, and compile time status codes, the compile time status codes including one or more of schema errors or input errors.

Assignees

• Salesforce Com Inc

Inventors

• Rudraraju Prakash
• Sayyaparaju Maheswara Sunil Varma
• Satya Damini
• Satasiya Babu

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/60

  Software deployment · CPC title

• G06Q30/02 Primary

  Marketing; Price estimation or determination; Fundraising · CPC title

• G06F16/951

  Indexing; Web crawling techniques · CPC title

• G06F8/36

  Software reuse · CPC title