WO2021137692A1

WO2021137692A1 - System and method for clustering a container orchestration

Info

Publication number: WO2021137692A1
Application number: PCT/MY2020/050153
Authority: WO
Inventors: Rajendar KANDAN; Sharipah Setapa; Mohammad Fairus Khalid; Hong Hoe ONG
Original assignee: Mimos Bhd
Current assignee: Mimos Bhd
Priority date: 2019-12-31
Filing date: 2020-11-16
Publication date: 2021-07-08
Anticipated expiration: 2022-06-30

Abstract

The present invention is a system (100) and a method (600) for clustering a container orchestration for propagation. The method includes the step of creating and collecting (602) a workflow of container applications through a creation and collection module (202). The workflow includes micro services to build container applications; encapsulating (604) the container application in a mini orchestration and embedded with a role through an encapsulation module (204); establishing (606) a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module (206); establishing (608) the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module (208). The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration. The most illustrative drawing.

Description

SYSTEM AND METHOD FOR CLUSTERING A CONTAINER ORCHESTRATION

TECHNICAL FIELD

[0001] The present invention relates to system and method for clustering a container orchestration, in particular to system and method for clustering a container orchestration for the propagation of the workflow service container application, mini orchestration, parent orchestration, and a role negotiation.

BACKGROUND

[0002] The advent of container orchestration enhances the ease of handling management and scaling of container solution. Typically, an orchestration system manages the container basic operation including launching, upgrading, and monitoring. However, the orchestration system lacks the method of identifying the nature of container/service being deployed, securing communication between the respective container across the same orchestration environment, and controlled sharing of resources across orchestration environment. Hence the current orchestration system causes inconsistency in managing the entire resources across orchestration framework.

[0003] US patent publication number US 2018/260204 A1 filed by Keagy et al. discloses an orchestration engine that interfaces with the various cloud systems to implement and configure the system solution. The orchestration engine disclosed in Keagy et al. reference includes configurations for a combination of different clouds, connections schema for connections and interactions between the cloud systems, and an order in which the clouds are to be implemented. The orchestration engine also instantiates the system solution by building infrastructure, installing and configuring software and services, and converging the various cloud systems to provide the system solution. However, the orchestration engine disclosed in Keagy et al. reference is not efficient because it builds the infrastructure by instantiating machines and services on the various clouds. Further, the orchestration engine installs and configures the software and services on the machines. The orchestration engine then converges the various clouds by establishing relationships and connections between the various services. [0004] US patent publication number US 2018/307514 A1 filed by Koutyrine et al. discloses a system to orchestrate transactions executed in part micro services. The system disclosed in Koutyrine et al. reference writes to a first tracking log a first log entry for a first action of a plurality of actions of the first transaction workflow. The first log entry describes an initial state of the first action. The writing to the first tracking log includes writing to the first tracking log at a persistent storage location. The system then writes to the first tracking log, a second log entry for a second action of the plurality of actions. The system then determines that a first microservice of the plurality of microservices successfully completed the first action. Further, this system determines that a second microservice of the plurality of microservices failed to complete the second action, and initiates a compensation action to reverse the first action. However, the information related to transactions disclosed in Koutyrine et al. reference is also not effective because the transactions are described by a transaction workflow including more than one action that makes up the transaction and different actions of the transaction are executed by different micro services.

[0005] This specification recognizes that a comprehensive orchestration with minimum interference of load balancing is required, and it is a challenge to cluster a container orchestration for the propagation of a workflow service container application, mini orchestration, parent orchestration, and role negotiation.

SUMMARY

[0006] The present invention provides a system and method for clustering a container orchestration for the propagation of the workflow service container application, mini orchestration, and parent orchestration, and a role negotiation. In one aspect of the present invention, it relates to a method for clustering a container orchestration for propagation. The method includes the step of creating and collecting a workflow of one or more container applications through a creation and collection module. The workflow includes one or more micro services to build container applications. The method then includes the step of encapsulating the container application in a mini orchestration and embedded with a role through an encapsulation module. The method includes the step of establishing a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module. The method includes the step of establishing the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module. The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

[0007] In an embodiment, the step of creating and collecting the workflow of the container applications includes the step of creating, and identifying the workflow of the micro service and collecting information pertaining to the role. The step then collects the workflow of each of the micro services and identifying to obtain a relationship with a plurality of scenarios of the container applications. The step of creating and collecting the workflow of the container applications further includes the step of storing a potential micro service in a different machine (VM). The step clusters the workflow of the container applications. The step of creating and collecting the workflow of the container applications includes the step of identifying if a potential mini orchestration present in the clustered workflow of the container applications. The step then creates the mini orchestration of the workflow of the container application on identifying the potential mini orchestration present in the clustered workflow of the container applications. The step of creating and collecting the workflow of the container applications includes the step of embedding the mini orchestration with the role. The role comprises a write role, a read or access role, and a restricted role. This step may re-initiate the step of creating, identifying the workflow of the micro service and collecting information pertaining to the role on identifying the potential mini orchestration is not present in the clustered workflow of the container applications.

[0008] In an embodiment, the step of encapsulating the container application in the mini orchestration and embedded with the role includes the step of establishing an interconnected orchestration role. The interconnected orchestration role is established by creating the container application by selecting the workflow of the micro service and creating the role of the mini orchestration based on the container application. The step then identifies the mini orchestration and matching with the role assigned before logging into the parent orchestration. The step then identifies if one or more sequence of the interconnected orchestration on roles are applied. The step of encapsulating the container application includes the step of establishing a relationship link between the interconnected orchestration on the roles on identifying the sequence of the interconnected orchestration on roles are applied. The step then verifies the relationship link the mini orchestration. The step of encapsulating the container application includes the step of checking whether the sequence is a failure on identifying the sequence of the interconnected orchestration on roles are not applied. The step then checks from a first initialization interconnected orchestration role and re-initiating the step of establishing an interconnected orchestration role.

[0009] In an embodiment, the step of establishing the relationship link between the mini orchestration, the role, and the workflow of the micro service and creating the permission to join the parent orchestration includes the step of creating the relationship link based on one or more rules. The step then combines the mini orchestrations based on the rules. The step applies the rules on the combining mini orchestrations. The step of establishing the relationship link between the mini orchestration, the role, and the workflow of the micro service and creating the permission to join the parent orchestration includes the step of identifying if the rules are applied. The step then executes policy on identifying that the rules are applied. The step of establishing the relationship link between the mini orchestration, the role, and the workflow of the micro service and creating the permission to join the parent orchestration includes the step of non-execution of the rule on identifying that the rules are not applied. The step then stops the execution of the policy. [0010] In an embodiment, the step of establishing the parent orchestration and the mini orchestration with secured access of the role includes the step of verifying that the mini orchestration is interconnected with the parent orchestration is eligible. The step then includes the step of clustering various mini orchestrations with the same role. The step of establishing the parent orchestration and the mini orchestration includes the step of assigning the mini orchestrations with the same role. The step then establishes communication between the mini orchestrations with the parent orchestration. Then the step identifies if the joining to the parent orchestration is successful. The step of establishing the parent orchestration and the mini orchestration includes the step of establishing the mini orchestrations with a single parent orchestration on identifying that the joining to the parent orchestration is successful. The step of establishing the parent orchestration and the mini orchestration includes the step of establishing the parent orchestrations. The workflow of the container applications is visualized by one or more users permitted in the parent orchestration. The step then includes the step of sharing the mini orchestrations with a respective workflow of the container application. The step of establishing the parent orchestration and the mini orchestration includes the step of replicating the workflow if the workflow of any mini orchestration is down. This step identifies if the workflow of any mini orchestration is down, then the other mini orchestration which consists replication workflow can support the failure workflow. The step of establishing the parent orchestration and the mini orchestration includes the step of checking if the mini orchestration is eligible on identifying that the joining to the parent orchestration is not successful. The step then verifies if the role exists in the mini orchestration.

[0011] Another aspect of the present invention relates to a system for clustering a container orchestration for propagation. The system includes a processor, and a memory communicatively coupled to the processor. The memory stores instructions, which, on execution by the processor, causes the processor to create and collect a workflow of one or more container applications through a creation and collection module. The workflow comprises one or more micro services to build container applications. The processor is then configured to encapsulate the container application in a mini orchestration and embedded with a role through an encapsulation module. The processor is then configured to establish a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module. The processor is then configured to establish the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module. The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

[0012] An embodiment of the present invention relates to a non-transitory computer- readable storage medium comprising a set of executable instructions stored thereon that, when executed by one or more processors, cause the processors to create and collect a workflow of one or more container applications through a creation and collection module. The workflow comprises one or more micro services to build container applications. The processor is then configured to encapsulate the container application in a mini orchestration and embedded with a role through an encapsulation module. The processor is then configured to establish a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module. The processor is then configured to establish the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module. The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration. [0013] Accordingly, one advantage of the present invention is that it provides n comprehensive orchestration with minimum interference of load balancing.

[0014] Accordingly, one advantage of the present invention is that it classify into mini orchestration and parent orchestration for empowerment.

[0015] Accordingly, one advantage of the present invention is that it provides mini orchestration for specific container application services.

[0016] Accordingly, one advantage of the present invention is that it creates a joint with the parent orchestration if the various mini orchestration container needs to coordinate with parent orchestration to a new entity.

[0017] Accordingly, one advantage of the present invention is that it initializes the joint between mini orchestration and parent orchestration to build a sophisticated application. [0018] Accordingly, one advantage of the present invention is that it builds and incorporates mini orchestration container application within parent orchestration.

[0019] Accordingly, one advantage of the present invention is that it logs into the parent orchestration with a specific role. [0020] Accordingly, one advantage of the present invention is that it allows the user who has a specific role be granted to visualize and access the multiple mini orchestrations in parent orchestration.

[0021] Other features of embodiments of the present invention will be apparent from accompanying drawings and from the detailed description that follows. [0022] Yet other objects and advantages of the present invention will become readily apparent to those skilled in the art following the detailed description, wherein the preferred embodiments of the invention are shown and described, simply by way of illustration of the best mode contemplated herein for carrying out the invention. As we realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the invention.

Accordingly, the drawings and description thereof are to be regarded as illustrative in nature, and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In the figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label irrespective of the second reference label.

[0024] FIG. 1 illustrates a block diagram of the present system for clustering a container orchestration for propagation, in accordance with one embodiment of the present invention. [0025] FIG. 2 illustrates a block diagram of the various modules within a memory of a container orchestration clustering device for clustering a container orchestration for the propagation of a workflow service container application, a mini orchestration, and parent orchestration, and a role negotiation, in accordance with another embodiment of the present invention. [0026] FIG. 3 illustrates an operational diagram of the present system for clustering a container orchestration for propagation, in accordance with another embodiment of the present invention.

[0027] FIG. 4 illustrates an operational diagram of the parent orchestration and role, in accordance with another embodiment of the present invention. [0028] FIG. 5 illustrates an operational diagram of the various mini orchestrations are logged to parent orchestration, in accordance with another embodiment of the present invention.

[0029] FIG. 6 illustrates a flowchart of the method for clustering a container orchestration for propagation, in accordance with an alternative embodiment of the present invention. [0030] FIG. 7 illustrates a flowchart for creating and collecting a workflow of one or more container applications through a creation and collection module in yet another embodiment of the present invention. [0031] FIG. 8 illustrates a flowchart for encapsulating the container application in a mini orchestration and embedded with a role through an encapsulation module a further embodiment of the present invention.

[0032] FIG. 9 illustrates a flowchart for establishing a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module in another embodiment of the present invention.

[0033] FIG. 10 illustrates a flowchart for establishing the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module in the further embodiment of the present invention.

[0034] FIG. 11 illustrates a tabular diagram of a workflow micro service is selected to create potential mini orchestration in the further embodiment of the present invention.

[0035] FIG. 12 illustrates a tabular diagram of a potential rule to be executed for permission to include in parent orchestration and mini orchestration in the further embodiment of the present invention.

[0036] FIG. 13 illustrates a tabular diagram of merging mini orchestration to be parent orchestration and retrieve micro service to continue workflow in the further embodiment of the present invention.

DETAILED DESCRIPTION

[0037] The present invention is best understood with reference to the detailed figures and description set forth herein. Various embodiments have been discussed with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions provided herein with respect to the figures are merely for explanatory purposes, as the methods and systems may extend beyond the described embodiments. For instance, the teachings presented and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond certain implementation choices in the following embodiments. [0038] Systems and methods are disclosed for clustering a container orchestration for the propagation of a workflow service container application, a mini orchestration, and parent orchestration, and a role negotiation to establish a cluster container application for orchestration by providing a controlled level of sharing and role to avoid duplication of various orchestration workflow services. Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, firmware, and/or by human operators.

[0039] Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine- readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).

[0040] Various methods described herein may be practiced by combining one or more machine-readable storage media containing the code according to the present invention with appropriate standard computer hardware to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, routines, subroutines, or subparts of a computer program product.

[0041] The present invention discloses a system and method, whereby the container orchestration is clustered for the propagation of the workflow service container application, mini orchestration, parent orchestration, and a role negotiation to establish cluster container application for orchestration by providing a controlled level of sharing and role to avoid duplication in various orchestration workflow services.

[0042] Although the present invention has been described with the purpose of clustering a container orchestration for propagation, it should be appreciated that the same has been done merely to illustrate the invention in an exemplary manner and to highlight any other purpose or function for which explained structures or configurations could be used and is covered within the scope of the present invention.

[0043] The term “machine-readable storage medium” or “computer-readable storage medium” includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing, or carrying instruction(s) and/or data. A machine-readable medium may include a non-transitory medium in which data can be stored, and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or versatile digital disk (DVD), flash memory, memory or memory devices.

[0044] FIG. 1 illustrates a block diagram of the present system 100 for clustering a container orchestration for propagation, in accordance with one embodiment of the present invention. The system 100 includes a container orchestration clustering device 102 that clusters a container orchestration for the propagation of a workflow service container application, a mini orchestration, parent orchestration, and a role negotiation to establish a cluster container application for orchestration by providing a controlled level of sharing and role to avoid duplication of various orchestration workflow services. In particular, the container orchestration clustering device 102 creates and collects a workflow of one or more container applications through a creation and collection module. The workflow comprises one or more micro services to build container applications. The container orchestration clustering device 102 then encapsulates the container application in a mini orchestration and embedded with a role through an encapsulation module.

[0045] Operationally, the container orchestration clustering device 102 establishes a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module. The container orchestration clustering device 102 establish the parent orchestration and the mini orchestration with a secured access of the role through a parent orchestration and a mini orchestration module, wherein the workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

[0046] The clustered container orchestration may be used by the user through a plurality of computing devices 104 (for example, a laptop 104a, a desktop 104b, and a smartphone 104c). The clustered container orchestration may be stored within a plurality of computing devices 104. Other examples of a plurality of computing devices 104, may include but are not limited to a phablet and a tablet. Alternatively, the data related to clustered container orchestration may be stored on a server 106 and may be accessed by a plurality of computing devices 104 via a network 108. The network 108 may be a wired or a wireless network, and the examples may include but are not limited to the Internet, Wireless Local Area Network (WLAN), Wi-Fi, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), and General Packet Radio Service (GPRS).

[0047] When a user of laptop 104a, for example, wants to visualize clustered container orchestration, laptop 104a communicates the same with container orchestration clustering device 102, via network 108. The container orchestration clustering device 102 then presents the predicted trends as per the user's request. To this end, container orchestration clustering device 102 includes a processor 110 that is communicatively coupled to a memory 112, which may be a non-volatile memory or a volatile memory. Examples of non volatile memory may include, but are not limited to flash memory, a Read Only Memory (ROM), a Programmable ROM (PROM), Erasable PROM (EPROM), and Electrically EPROM (EEPROM) memory. Examples of volatile memory may include but are not limited Dynamic Random Access Memory (DRAM), and Static Random-Access memory (SRAM).

[0048] Processor 110 may include at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as those included in this invention, or such a device itself. Processor 110 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

[0049] Processor 110 may include a microprocessor, such as AMD® ATHLON® microprocessor, DURON® microprocessor OR OPTERON® microprocessor, ARM's application, embedded or secure processors, IBM® POWERPC®, INTEL'S CORE® processor, ITANIUM® processor, XEON® processor, CELERON® processor or other line of processors, etc. Processor 110 may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.

[0050] Processor 110 may be disposed of in communication with one or more input/output (I/O) devices via an I/O interface. I/O interface may employ communication protocols/methods such as, without limitation, audio, analog, digital, RCA, stereo, IEEE- 1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n/b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.

[0051] Memory 112 further includes various modules that enable the container orchestration clustering device 102 for clustering a container orchestration for propagation of a workflow service container application, a mini orchestration, parent orchestration, and a role negotiation to establish a cluster container application for orchestration by providing a controlled level of sharing and role to avoid duplication of various orchestration workflow services. These modules are explained in detail in conjunction with FIG. 2. The container orchestration clustering device 102 may further include a display 114 having a User Interface (UI) 116 that may be used by a user or an administrator to initiate a request to view clustered container orchestration and provide various inputs to the container orchestration clustering device 102. Display 114 may further be used to display clustered container orchestration. The functionality of the container orchestration clustering device 102 may alternatively be configured within each of plurality of computing devices 104. [0052] FIG. 2 illustrates a block diagram of a memory 112 of a container orchestration clustering device 102 for clustering a container orchestration for the propagation of a workflow service container application, a mini orchestration, parent orchestration, and a role negotiation, in accordance with one embodiment of the present invention. The memory 112 includes a creation and collection module 202, an encapsulation module 204, a relationship and permission module 206, and a parent orchestration and a mini orchestration module 208.

[0053] The creation and collection module 202 create and collect a workflow of container applications. The workflow includes one or more micro services that build container applications. The creation and collection module 202 is configured to create, and identify the workflow of the micro service and collect information pertaining to the role. The creation and collection module 202 are further configured to collect the workflow of each of the micro services and identify a relationship with a plurality of scenarios of the container applications. The creation and collection module 202 is configured to store a potential micro service in a different virtual machine (VM). The creation and collection module 202 clusters the workflow of the container applications. The creation and collection module 202 further identifies if a potential mini orchestration present in the clustered workflow of the container applications and creates the mini orchestration of the workflow of the container application on identifying the potential mini orchestration present in the clustered workflow of the container applications. The creation and collection module 202 is also configured to embed the mini orchestration with the role. The role comprises a write role, a read or access role, and a restricted role. Then the creation and collection module 202 are configured to re-initiate the step of creating, identifying the workflow of the micro service and collecting information pertaining to the role on identifying the potential mini orchestration that is not present in the clustered workflow of the container applications.

[0054] The encapsulation module 204 encapsulates the container application in a mini orchestration and embedded with a role. The encapsulation module 204 is configured to establish an interconnected orchestration role. In an embodiment, the interconnected orchestration role is established by creating the container application by selecting the workflow of the micro service. The encapsulation module 204 is then configured to create the role of the mini orchestration based on the container application. The encapsulation module 204 is configured to identify the mini orchestration and matching with the role assigned before logging into the parent orchestration. The encapsulation module 204 is then configured to identify if one or more sequence of the interconnected orchestration on roles are applied. The encapsulation module 204 is then configured to establish a relationship link between the interconnected orchestration on the roles on identifying the sequence of the interconnected orchestration on roles are applied. The encapsulation module 204 is then configured to verify the relationship link the mini orchestration. The encapsulation module 204 is then configured to check whether the sequence is a failure on identifying the sequence of the interconnected orchestration on roles are not applied. The encapsulation module 204 is then configured to check from a first initialization interconnected orchestration role and re-initiating the step of establishing an interconnected orchestration role.

[0055] Relationship and permission module 206 establishes a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating a permission to join a parent orchestration. The relationship and permission module 206 is configured to create a relationship link based on one or more rules. The relationship and permission module 206 is configured to combine the mini orchestrations based on the rules. The relationship and permission module 206 is configured to apply the rules on combining mini orchestrations. The relationship and permission module 206 is configured to identify if the rules are applied. The relationship and permission module 206 is configured to execute a policy on identifying that the rules are applied. The relationship and permission module 206 is configured to suspend/halt/prevent of the rule that are not applicable be executed. The relationship and permission module 206 is configured to stop the execution of the policy.

[0056] Parent orchestration and a mini orchestration module 208 is configured to establish the parent orchestration and the mini orchestration with secured access of the role. The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration. The parent orchestration and the mini orchestration module 208 is configured to verify that the mini orchestration that is interconnected with the parent orchestration is eligible. The parent orchestration and the mini orchestration module 208 is configured to cluster various mini orchestrations with the same role. The parent orchestration and the mini orchestration module 208 is configured to assign the mini orchestrations with the same role. The parent orchestration and the mini orchestration module 208 is configured to establish communication between the mini orchestrations with the parent orchestration. The parent orchestration and the mini orchestration module 208 is configured to identify if the joining to the parent orchestration is successful. The parent orchestration and the mini orchestration module 208 is configured to establish the mini orchestrations with a single parent orchestration on identifying that the joining to the parent orchestration is successful. The parent orchestration and the mini orchestration module 208 is configured to establish the parent orchestrations. In an embodiment, the workflow of the container applications is visualized by one or more users permitted in the parent orchestration. The parent orchestration and the mini orchestration module 208 is configured to share the mini orchestrations with a respective workflow of the container application. The parent orchestration and the mini orchestration module 208 is configured to replicate the workflow if the workflow of any mini orchestration is down. In an embodiment, the step identifies if the workflow of any mini orchestration is down, then the other mini orchestration which consists replication workflow can support the failure workflow. The parent orchestration and the mini orchestration module 208 is configured to check if the mini orchestration is eligible on identifying that the joining to the parent orchestration is not successful. The parent orchestration and the mini orchestration module 208 is configured to verify if the role exists in the mini orchestration.

[0057] FIG. 3 illustrates an operational diagram 300 of the present system for clustering a container orchestration for propagation, in accordance with another embodiment of the present invention. A plurality of micro services 302 are analyzed before the deployment across the orchestration environment. The potential cluster container micro services are deployed in a different virtual machines (VM) 304. The potential cluster container micro services establish the cluster container application for orchestration by providing a controlled level of sharing 306 across containers 308 between the VMs. Various mini orchestrations 310a and 310b are added in a parent orchestration 312.

[0058] FIG. 4 illustrates an operational diagram 400 of the parent orchestration and role, in accordance with another embodiment of the present invention. In an embodiment, the workflow container application is visualized by all the users who are permitted in the parent orchestration 312. The mini orchestrations 310a, 310b, and 310c are added in the parent orchestration 312. [0059] FIG. 5 illustrates an operational diagram 500 of the various mini orchestrations that are log to parent orchestration, in accordance with another embodiment of the present invention. Various mini orchestrations 310a and 310b are logged to the parent orchestration 312. The mini orchestrations 310a and 310b are incorporated in the parent orchestration 312 with a role for a specific application. Various mini orchestrations 310a and 310b are logged to the parent orchestration 312 to build and incorporate mini orchestration container application which linked with each other in parent orchestration. Further, the mini orchestrations 310a and 310b are logged to the parent orchestration 312 for the user who has specific role be granted to see and access the multiple mini orchestrations 310a and 310b.

[0060] FIG. 6 illustrates a flowchart 600 of clustering a container orchestration for propagation, in accordance with an alternative embodiment of the present invention. The method includes a step 602 of creating and collecting a workflow of one or more container applications through a creation and collection module. The workflow includes one or more micro services to build container applications. The method then includes a step 604 of encapsulating the container application in a mini orchestration and embedded with a role through an encapsulation module. Various type of container applications can be encapsulated in the mini orchestra. At step 606 of establishing a link relationship between the mini orchestra, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module. At step 608 of establishing the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module. The workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

[0061] FIG. 7 illustrates a flowchart 700 for creating and collecting a workflow of one or more container applications through a creation and collection module in yet another embodiment of the present invention. The process of creating and collecting starts with a step 702 of identifying workflow service. In this step, each workflow service of the container application and information of role thereof are collected. At step 704, the creation and collection module creates potential micro service based on the relationship of the various container application scenarios. At step 706, putting the potential micro service in a different virtual machine (VM). [0062] At step 708, the creation and collection module clusters the workflow of the container applications in specific mini orchestra. At step 710, the creation and collection module determines whether any potential mini orchestration present in the clustered workflow of the container applications. If the potential mini orchestration is present in the clustered workflow of the container applications, at step 712, the creation and collection module creates the mini orchestration of the workflow of the container application. The new mini orchestra consists of various workflow services, capable to replicate. At the step 714, the mini orchestra are embedded with role. The role includes a write role, a read or access role, and a restricted role. [0063] Returining to the step 710, if no mini orchestra is present, the process returns to the step 702 and so on.

[0064] FIG. 8 illustrates a flowchart 800 for encapsulating the container application in a mini orchestration and embedded with a role through an encapsulation module in a further embodiment of the present invention. The step of encapsulating the container application in the mini orchestration and embedded with the role includes the step 802 of establishing an interconnected orchestration role. The interconnected orchestration role is established by creating the container application by selecting the workflow of the micro service and creating the role of the mini orchestration based on the container application. The step then identifies the mini orchestration and matching with the role assigned before logging into the parent orchestration. The step 804 determines if one or more sequence of the interconnected orchestration on roles are applied. The step of encapsulating the container application includes the step 806 of establishing a relationship link between the interconnected orchestration on the roles if the sequence of the interconnected orchestration on roles are applied. Specifically, the interconnected orchestration role pertains to the workflow micro service be selected to create container application; mini orchestra created based on container application; and mini orchestra be identified and matched with role be assigned before logging into the parent orchestration. At step 808 then verifies the relationship link the mini orchestration and the encapsulation process is concluded.

[0065] Returning to step 804, if the sequence of orchestration on role is not applied, at step 810, sequence relationship is checked whether any failure over the interconnection exists.

At step 812 then observes (for failure) from the befininf of initialization (of establishment) of interconnected orchestration role by looping back to step 802. [0066] FIG. 9 illustrates a flowchart 900 for establishing a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating permission to join a parent orchestration through a relationship and permission module in another embodiment of the present invention. The step of establishing the relationship link between the mini orchestration, the role, and the workflow of the micro service and creating the permission to join the parent orchestration includes a step 902 of creating a link relation based on one or more rules from a rule policy. Step 904 combines the mini orchestrations based on the rules (of the rule policy). Step 906 applies the rules on the combining mini orchestrations. [0067] At step 908, the process checks if the rules are applied successfully. If the rules are applied unsuccessfully, i.e. unable to execute the rule over the mini orchestration at step 912, the operation is halt at step 914, whereby the mini orchestration is not authorised to enter the parent orchesttation to build the application. It follows that the replication is not permitted to be included. Returning to the step 908, if the rules are applied successfully, at step 910, the policy is executed on the mini orchestrations.

[0068] FIG. 10 illustrates a flowchart 1000 for establishing the parent orchestration and the mini orchestration with secured access of the role through a parent orchestration and a mini orchestration module in the further embodiment of the present invention. The step of establishing the parent orchestration and the mini orchestration with secured access of the role includes the step 1002 of verifying that the interconnection between the mini orchestration and the parent orchestration is eligible. The step 1004 various mini orchestrations with the same role (i.e. write/read/access/restricted role) are grouped. At step 1006, the process assigns the mini orchestrations with the same role with at least IDs. At step 1008, the process then establishes communications between the mini orchestrations with the parent orchestration.

[0069] At step 1010, it is determined if the joining to the parent orchestration is successful. If it is successful, at step 1012, of the process establishes the mini orchestrations with a single parent orchestration. It follows with a step 1016 of establishing the parent orchestrations, whereby the workflow of the container applications is visualized by one or more users permitted in the parent orchestration. Further, at the step 1018, the mini orchestrations with a respective workflow of the container application are shared. At step 1020, the process replicates the corresponding workflow when mini orchestration is down. The corresponding workflow can be replicated from other mini orchestration that consists replicated workflow which can support the failed workflow.

[0070] Returning to the step 1010, if joining to the parent orchestration is unsuccessful, that mini orchestration is checked for its eligibility at step 1014 and verifies if the role associated thereto exists, at step 1022. The process then returns to the step 1002 to verify if interconnection between the mini and parent orchestration is eligible.

[0071] In operations, the initial clustering and profiling of workflow, container, and orchestration are performed by arranging potential workflow micro service to be a potential cluster. Each potential cluster resides in a specific virtual machine (VM). This potential cluster become container application. Each type of workflow services will be analyzed when creating workflow micro service, container application, and mini orchestration.

[0072] Each workflow service is collected and identified to get a relationship with various application scenarios. Then if the application gets grows, then move to another potential cluster with respective workflow services. At least the potential cluster has at least similar behavior and functionality with the previous potential cluster. Grouping the cluster container workflow micro service is easy for the management when the application gets to grow. For example, if one of the micro services which resides in application 1 is needed for application 2, then it will be put in the same mini orchestration for easy retrieval. Both the application 1 and 2 be classified as mini orchestration 1. Same with mini orchestration 2 which consists of application 3 and 4, then if anything happens to workflow then will retrieve micro service from a neighbor. Each child orchestration is merged to create orchestration with the role. Each join different micro service has to be recognized to access or retrieve if the application needs a combination of micro service.

[0073] Following Table 1 below exemplifies a combination of the parameter for different scheme and grouping individual micro service container:

[0074] The above table depicts that each application behaves as a container application consists of various micro service workflow. Each micro service can be analyzed (Mini Orchestration). The micro service can be shared across the application. Also, the micro service 2 is shared among Application 1 and 2. Similarly, the restriction of access to micro service 2 can also be applied (E.g.: micro service 2 in mini orchestra 1 not communicate with micro service 3). This enables the controlled level of sharing across the orchestration.

[0075] Table 2 examplifies a policy management across the mini orchestrations:

[0076] FIG. 11 illustrates a diagram 1100 of a workflow micro service be selected to create potential mini orchestration (orchestra) in the further embodiment of the present invention. If micro service ‘a’ and micro service ‘b’ then container application 1 is created.

[0077] FIG. 12 illustrates a diagram 1200 of a potential rule to be executed for permission to include in parent orchestration and mini orchestration in the further embodiment of the present invention. If mini orchestration is a success then merge with the role and select the roles to provide the output of role with the mini orchestration. [0078] FIG. 13 illustrates a diagram 1300 of merging mini orchestration to be parent orchestration and retrieve micro service to continue workflow in the further embodiment of the present invention. If mini orchestration 1 and mini orchestration 2 require services then merge with the parent orchestration. In case of parent orchestration and mini orchestration 1 workflow failure (example micro service 2), then retrieve micro service in mini orchestration 2. Also, the workflow if available or alive in the parent orchestration. If mini orchestration 2 workflow requires service then it will access the micro service 2 from mini orchestration 1. This will avoid any duplication and allows controlled sharing.

[0079] Thus the present system and method provide an efficient, simpler and more elegant framework that provides a comprehensive orchestration with minimum interference of load balancing. The present system and method break down into mini orchestration and parent orchestration for empowerment. Further, the present system and method provide mini orchestration for specific container application services. The present system and method create a joint with the parent orchestration if the various mini orchestration container needs to coordinate with parent orchestration to a new entity. Furthermore, the present system and method initialize the joint between mini orchestration and parent orchestration to build the sophisticated application.

[0080] While embodiments of the present invention have been illustrated and described, it will be clear that the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents will be apparent to those skilled in the art, without departing from the scope of the invention, as described in the claims.

Claims

1. A method for clustering a container orchestration for propagation, the method is characterized by the steps of: creating and collecting (602), by a container orchestration clustering device (102), a workflow of one or more container applications through a creation and collection module (202), wherein the workflow comprises one or more micro services to build the container applications; encapsulating (604), by the container orchestration clustering device (102), the container application in a mini orchestration and embedded with a role through an encapsulation module (204); establishing (606), by the container orchestration clustering device (102), a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating a permission to join a parent orchestration through a relationship and permission module (206); and establishing (608), by the container orchestration clustering device (102), the parent orchestration and the mini orchestration with a secured access of the role through a parent orchestration and a mini orchestration module (208), wherein the workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

2. The method according to claim 1, wherein the step of creating and collecting the workflow of the container applications (602) comprises the steps of: creating, and identifying the workflow of the micro service and collecting information pertaining to the role (702); collecting the workflow of each of the micro services and identifying to obtain a relationship with a plurality of scenarios of the container applications (704); storing a potential micro service in a different virtual machine, VM, (706); clustering the workflow of the container applications (708); identifying if a potential mini orchestration present in the clustered workflow of the container applications (710); creating the mini orchestration of the workflow of the container application on identifying the potential mini orchestration present in the clustered workflow of the container applications (712); and embedding the mini orchestration with the role, wherein the role comprises a write role, a read or access role, and a restricted role, and re-initiating the step of creating, identifying the workflow of the micro service and collecting information pertaining to the role on identifying the potential mini orchestration that is not present in the clustered workflow of the container applications (714).

3. The method according to claim 1, wherein the step of encapsulating the container application in the mini orchestration and embedded with the role (604) comprises the steps of: establishing an interconnected orchestration role, wherein the interconnected orchestration role is established by creating the container application by selecting the workflow of the micro service, creating the role of the mini orchestration based on the container application, and identifying the mini orchestration and matching with the role assigned before logging into the parent orchestration (802); identifying if one or more sequence of the interconnected orchestration on roles are applied (804); establishing a relationship link between the interconnected orchestration on the roles on identifying the sequence of the interconnected orchestration on roles are applied (806); verifying the relationship link the mini orchestration (808); checking whether the sequence is a failure on identifying the sequence of the interconnected orchestration on roles are not applied (810); and checking from a first initialization interconnected orchestration role and re-initiating the step of establishing an interconnected orchestration role (812).

4. The method according to claim 1, wherein the step of establishing the relationship link between the mini orchestration, the role, and the workflow of the micro service and creating the permission to join the parent orchestration (606) comprises the steps of: creating the relationship link based on one or more rules (902); combining the mini orchestrations based on the rules (904); applying the rules on the combining mini orchestrations (906); identifying if the rules are applied (908); executing a policy on identifying that the rules are applied (910); non-execution of the rule on identifying that the rules are not applied (912); and stopping the execution of the policy (914).

5. The method according to claim 1, wherein the step of establishing the parent orchestration and the mini orchestration with a secured access of the role (608) comprises the steps of: verifying that the mini orchestration is interconnected with the parent orchestration is eligible (1002); clustering various mini orchestrations with the same role (1004); assigning the mini orchestrations with the same role (1006); establishing communication between the mini orchestrations with the parent orchestration (1008); identifying if the joining to the parent orchestration is successful (1010); establishing the mini orchestrations with a single parent orchestration on identifying that the joining to the parent orchestration is successful(1012); establishing the parent orchestrations, wherein the workflow of the container applications is visualized by one or more users permitted in the parent orchestration (1016); sharing the mini orchestrations with a respective workflow of the container application (1018); replicating the workflow if the workflow of any mini orchestration is down (1020); checking if the mini orchestration is eligible on identifying that the joining to the parent orchestration is not successful (1014); and verifying if the role exists in the mini orchestration (1022).

6. A system for clustering a container orchestration for propagation, characterized in that the system comprising: a processor (110); and a memory (112) communicatively coupled to the processor, wherein the memory stores instructions executed by the processor (110), wherein the memory (112) comprising: a creation and collection module (202) to create and collect (602) a workflow of one or more container applications, wherein the workflow comprises one or more micro services to build the container applications; an encapsulation module (204) to encapsulate (604) the container applications in a mini orchestration and embedded with a role; a relationship and permission module (206) to establish (606) a relationship link between the mini orchestration, the role, and the workflow of the micro service and creating a permission to join a parent orchestration; and a parent orchestration and a mini orchestration module (208) to establish (608) the parent orchestration and the mini orchestration with a secured access of the role, wherein the workflow of the micro service, the mini orchestration and the permission to join the parent orchestration are interconnected and function together to be permitted in the parent orchestration.

7. The system according to claim 6, wherein the creation and collection module (202) is configured to operationally create, and identify (702) the workflow of the micro service and collect information pertaining to the role; collect (704) the workflow of each of the micro services and identify to obtain a relationship with a plurality of scenarios of the container applications; store (706) a potential micro service in a different virtual machine, VM; cluster the workflow of the container applications; identify (708) if a potential mini orchestration present in the clustered workflow of the container applications; create (712) the mini orchestration of the workflow of the container application on identifying the potential mini orchestration present in the clustered workflow of the container applications; and embed (714) the mini orchestration with the role, wherein the role comprises a write role, a read or access role, and a restricted role, and re-initiate the step of creating, identifying the workflow of the micro service and collecting information pertaining to the role on identifying the potential mini orchestration is not present in the clustered workflow of the container applications.

8. The system according to claim 6, wherein the encapsulation module (204) is adapted to operationally establish an interconnected orchestration role, wherein the interconnected orchestration role is established (604) by creating (802) the container application by selecting the workflow of the micro service, create the role of the mini orchestration based on the container application, and identify (804) the mini orchestration and matching with the role assigned before logging into the parent orchestration; identify if one or more sequence of the interconnected orchestration on roles are applied; establish (806) a relationship link between the interconnected orchestration on the roles on identifying the sequence of the interconnected orchestration on roles are applied; verify (808) the relationship link the mini orchestration; check (810) whether the sequence is a failure on identifying the sequence of the interconnected orchestration on roles are not applied; and check (812) from a first initialization interconnected orchestration role and re-initiating the step of establishing an interconnected orchestration role.

9. The system according to claim 6, wherein the relationship and permission module (206) is adapted to create (902) the relationship link based on one or more rules; combine (904) the mini orchestrations based on the rules; apply (906) the rules on the combining mini orchestrations; identify (908) if the rules are applied; execute (910) a policy on identifying that the rules are applied; non-execution (912) of the rule on identifying that the rules are not applied; and stop (914) the execution of the policy.

10. The system according to claim 6, wherein the parent orchestration and the mini orchestration module (208) is configured to operationally verify (1002) that the mini orchestration is interconnected with the parent orchestration is eligible; cluster (1004) various mini orchestrations with the same role; assign (1006) the mini orchestrations with the same role; establish communication between the mini orchestrations with the parent orchestration; identify if the joining to the parent orchestration is successful; establish (1008) the mini orchestrations with a single parent orchestration on identifying that the joining to the parent orchestration is successful; establish (1012) the parent orchestrations, wherein the workflow of the container applications is visualized by one or more users permitted in the parent orchestration; share (1018) the mini orchestrations with a respective workflow of the container application; replicate (1020) the workflow if the workflow of any mini orchestration is down; check (1022) if the mini orchestration is eligible on identifying that the joining to the parent orchestration is not successful; and verify if the role exists in the mini orchestration.