Self-service orchestration platform

Patent metadata

Field	Value
Publication number	US-2020293337-A1
Application number	US-202016815601-A
Country	US
Kind code	A1
Filing date	Mar 11, 2020
Priority date	Mar 13, 2019
Publication date	Sep 17, 2020
Grant date	—

Abstract

Techniques for self-service orchestration are disclosed. A system deploys instances of a self-service orchestration agent to tenant-specific software-as-a-service (SaaS) environments operating in a multi-tenant SaaS environment, without reconfiguring existing software in the tenant-specific SaaS environments. Each self-service orchestration agent includes functionality to configure one or more components. Each tenant-specific SaaS environment includes a dedicated set of software operating on a dedicated logical partition of hardware infrastructure. The system receives, via a self-service orchestration interface, a request to configure a component across the tenant-specific SaaS environments. The system: transmits the request to a self-service orchestration module that is operating in the multi-tenant SaaS environment and configured to communicate with each instance of the self-service orchestration agent; dispatches, by the self-service orchestration module, the request to each instance of the self-service orchestration agent; configures, by each of the self-service orchestration agents in a corresponding tenant-specific SaaS environment, the component.

First claim

What is claimed is:

1 . One or more non-transitory computer-readable media storing instructions, which when executed by one or more hardware processors, cause performance of operations comprising:
responsive to detecting an executable file in a storage location, identifying a manifest corresponding to the executable file; based on the manifest, identifying parameter types corresponding to a function associated with the executable file; configuring an interface for a platform based on the parameter types corresponding to the function associated with the executable file; receiving, by the platform via the interface, a command to execute the function associated with the executable file, the command comprising parameter values; and causing execution of the function by passing the parameter values to a process corresponding to the executable file.

2 . The one or more media of claim 1 , further comprising applying a policy to the process corresponding to the executable file, the policy separate from the executable file and including at least one or more of a security policy, an auditing policy, a communication routing policy, or a life cycle management agent.

3 . The one or more media of claim 2 , wherein the policy is associated with an environment within which the process operates.

4 . The one or more media of claim 3 , wherein the policy further enables at least one of an auto-configuration function for the process or specifies environment dependencies corresponding to the process.

5 . The one or more media of claim 1 , further comprising applying measurement functionality to the process, the measurement functionality identifying at least one of API call sources, API call requests, and measuring request completion times.

6 . The one or more media of claim 1 , wherein the executable file includes binary code associated with one or more independently deployable modules.

7 . The one or more media of claim 1 , wherein the manifest further identifies a script in the executable file.

8 . The one or more media of claim 1 , wherein the manifest further defines a map identifying at least one script in the executable file and a corresponding function.

9 . The one or more media of claim 1 , further comprising periodically checking a storage location for the executable file.

10 . The one or more media of claim 1 , further comprising inferring an identity of the function associated with the executable file based on one or more of the parameter types and parameters and return values identified in the manifest.

11 . A method comprising:
identifying a manifest corresponding to an executable file responsive to detecting the executable file in a storage location; based on the manifest, identifying parameter types corresponding to a function associated with the executable file; configuring an interface for a platform based on the parameter types corresponding to the function associated with the executable file; receiving, by the platform via the interface, a command to execute the function associated with the executable file, the command comprising parameter values; and causing execution of the function by passing the parameter values to a process corresponding to the executable file.

12 . The method of claim 11 , further comprising applying a policy to the process corresponding to the executable file, the policy separate from the executable file and including at least one or more of a security policy, an auditing policy, a communication routing policy, or a life cycle management agent.

13 . The method of claim 12 , wherein the policy is associated with an environment within which the process operates.

14 . The method of claim 13 , wherein the policy further enables at least one of an auto-configuration function for the process or specifies environment dependencies corresponding to the process.

15 . The method of claim 11 , further comprising applying measurement functionality to the process, the measurement functionality identifying at least one of API call sources, API call requests, and measuring request completion times.

16 . The method of claim 11 , wherein the executable file includes binary code associated with one or more independently deployable modules.

17 . The method of claim 11 , wherein the manifest further identifies a script in the executable file.

18 . The method of claim 11 , wherein the manifest further defines a map identifying at least one script in the executable file and a corresponding function.

19 . The method of claim 11 , further comprising periodically checking a storage location for the executable file.

20 . The method of claim 11 , further comprising inferring an identity of the function associated with the executable file based on one or more of the parameter types and parameters and return values identified in the manifest.

Assignees

• Oracle Int Corp

Inventors

• Rangasamy Venkatachalam
• Jeyapaul Jaganathan
• Sundaram Krithika Bharathi
• Unnikrishnan Parvathy
• Pratik Kumar
• Selvam Narayanan
• Hiremath Jayadev

Classifications

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L67/566

  Grouping or aggregating service requests, e.g. for unified processing · CPC title

• G06F8/60

  Software deployment · CPC title

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• H04L63/20

  for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title