WO2021137692A1 - Système et procédé de regroupement d'une orchestration de conteneurs - Google Patents

Système et procédé de regroupement d'une orchestration de conteneurs Download PDF

Info

Publication number
WO2021137692A1
WO2021137692A1 PCT/MY2020/050153 MY2020050153W WO2021137692A1 WO 2021137692 A1 WO2021137692 A1 WO 2021137692A1 MY 2020050153 W MY2020050153 W MY 2020050153W WO 2021137692 A1 WO2021137692 A1 WO 2021137692A1
Authority
WO
WIPO (PCT)
Prior art keywords
orchestration
mini
role
workflow
parent
Prior art date
Application number
PCT/MY2020/050153
Other languages
English (en)
Inventor
Rajendar KANDAN
Sharipah Setapa
Mohammad Fairus Khalid
Hong Hoe ONG
Original Assignee
Mimos Berhad
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mimos Berhad filed Critical Mimos Berhad
Publication of WO2021137692A1 publication Critical patent/WO2021137692A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors

Definitions

  • 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.
  • the system 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • one advantage of the present invention is that it classify into mini orchestration and parent orchestration for empowerment.
  • one advantage of the present invention is that it provides mini orchestration for specific container application services.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 illustrates an operational diagram of the parent orchestration and role, in accordance with another embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • machine-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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • WLAN Wireless Local Area Network
  • Wi-Fi Wireless Fidelity
  • LTE Long Term Evolution
  • WiMAX Worldwide Interoperability for Microwave Access
  • GPRS General Packet Radio Service
  • container orchestration clustering device 102 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.
  • 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).
  • DRAM Dynamic Random Access Memory
  • SRAM Static Random-Access memory
  • 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.
  • 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.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • FPGAs Field Programmable Gate Arrays
  • 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.
  • CDMA code-division multiple access
  • HSPA+ high-speed packet access
  • GSM global system for mobile communications
  • LTE long-term evolution
  • WiMax wireless wide area network
  • 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.
  • UI User Interface
  • 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.
  • 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).
  • VM virtual machine
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 illustrates an operational diagram 400 of the parent orchestration and role, in accordance with another embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the creation and collection module creates potential micro service based on the relationship of the various container application scenarios.
  • VM virtual machine
  • the creation and collection module clusters the workflow of the container applications in specific mini orchestra.
  • the creation and collection module determines whether any potential mini orchestration present in the clustered workflow of the container applications.
  • 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.
  • the mini orchestra are embedded with role.
  • the role includes a write role, a read or access role, and a restricted role.
  • 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.
  • 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.
  • step 808 verifies the relationship link the mini orchestration and the encapsulation process is concluded.
  • step 810 sequence relationship is checked whether any failure over the interconnection exists.
  • 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.
  • 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.
  • the rules are applied successfully, at step 910, the policy is executed on the mini orchestrations.
  • 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.
  • the process assigns the mini orchestrations with the same role with at least IDs.
  • the process then establishes communications between the mini orchestrations with the parent orchestration.
  • 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.
  • 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.
  • 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.
  • VM virtual machine
  • Each type of workflow services will be analyzed when creating workflow micro service, container application, and mini orchestration.
  • 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.
  • 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.
  • the micro service 2 is shared among Application 1 and 2.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système (100) et un procédé (600) destinés à regrouper une orchestration de conteneurs pour une propagation. Le procédé comprend l'étape de création et de collecte (602) d'un flux de travail d'applications de conteneurs par l'intermédiaire d'un module de création et de collecte (202). Le flux de travail comprend des micro-services pour construire des applications de conteneurs ; l'encapsulation (604) de l'application de conteneurs dans une mini-orchestration et incorporée avec un rôle par l'intermédiaire d'un module d'encapsulation (204) ; l'établissement (606) d'une liaison de relation entre la mini-orchestration, le rôle et le flux de travail du micro-service et la création d'une autorisation de joindre une orchestration mère par l'intermédiaire d'un module de relation et d'autorisation (206) ; l'établissement (608) de l'orchestration mère et de la mini-orchestration avec un accès sécurisé du rôle par l'intermédiaire d'une orchestration mère et d'un module de mini-orchestration (208). Le flux de travail du micro-service, la mini-orchestration et l'autorisation de joindre l'orchestration mère sont interconnectés et fonctionnent ensemble pour être autorisés dans l'orchestration mère. Dessin le plus représentatif.
PCT/MY2020/050153 2019-12-31 2020-11-16 Système et procédé de regroupement d'une orchestration de conteneurs WO2021137692A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
MYPI2019007940 2019-12-31
MYPI2019007940 2019-12-31

Publications (1)

Publication Number Publication Date
WO2021137692A1 true WO2021137692A1 (fr) 2021-07-08

Family

ID=76686719

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/MY2020/050153 WO2021137692A1 (fr) 2019-12-31 2020-11-16 Système et procédé de regroupement d'une orchestration de conteneurs

Country Status (1)

Country Link
WO (1) WO2021137692A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210326192A1 (en) * 2020-04-14 2021-10-21 Oracle International Corporation System and method for reactive messaging client for use with a microservices environment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140304398A1 (en) * 2013-04-01 2014-10-09 Nebula, Inc. Orchestration Service for a Distributed Computing System
US20160378450A1 (en) * 2015-06-24 2016-12-29 Cliqr Technologies, Inc. Apparatus, systems, and methods for distributed application orchestration and deployment
US20180365006A1 (en) * 2017-06-16 2018-12-20 Red Hat, Inc. Coordinating Software Builds for Different Computer Architectures
WO2019129987A1 (fr) * 2017-12-27 2019-07-04 Bull Sas Reseau informatique d'infrastructures de ressources de calcul et procede d'affectation de ces ressources a des applications client
US20190220361A1 (en) * 2018-01-12 2019-07-18 Robin Systems, Inc. Monitoring Containers In A Distributed Computing System

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140304398A1 (en) * 2013-04-01 2014-10-09 Nebula, Inc. Orchestration Service for a Distributed Computing System
US20160378450A1 (en) * 2015-06-24 2016-12-29 Cliqr Technologies, Inc. Apparatus, systems, and methods for distributed application orchestration and deployment
US20180365006A1 (en) * 2017-06-16 2018-12-20 Red Hat, Inc. Coordinating Software Builds for Different Computer Architectures
WO2019129987A1 (fr) * 2017-12-27 2019-07-04 Bull Sas Reseau informatique d'infrastructures de ressources de calcul et procede d'affectation de ces ressources a des applications client
US20190220361A1 (en) * 2018-01-12 2019-07-18 Robin Systems, Inc. Monitoring Containers In A Distributed Computing System

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210326192A1 (en) * 2020-04-14 2021-10-21 Oracle International Corporation System and method for reactive messaging client for use with a microservices environment

Similar Documents

Publication Publication Date Title
US9407664B1 (en) Systems and methods for enforcing enterprise data access control policies in cloud computing environments
US10298514B2 (en) System and method for cloud connection pool
US9077579B1 (en) Systems and methods for facilitating access to shared resources within computer clusters
US20170091075A1 (en) Distributed system test automation framework
US11212175B2 (en) Configuration management for cloud storage system and method
US10678630B2 (en) Method and system for resolving error in open stack operating system
EP3217312B1 (fr) Procédés et systèmes pour la gestion dynamique de l'accès à des dispositifs pour la résolution d'un ticket d'incident
US20210397730A1 (en) Controlling Access to Secure Information Resources Using Rotational Datasets and Dynamically Configurable Data Containers
US11768672B1 (en) Systems and methods for user-controlled deployment of software updates
US12069057B2 (en) Controlling access to secure information resources using rotational datasets and dynamically configurable data containers
US9098392B1 (en) Systems and methods for changing fencing modes in clusters
US10298681B1 (en) Systems and methods for rerouting data sent between application containers and storage containers
US9411974B2 (en) Managing document revisions
CN116166390A (zh) 一种业务处理方法、装置、电子设备和存储介质
WO2021137692A1 (fr) Système et procédé de regroupement d'une orchestration de conteneurs
US11630742B2 (en) System and method of performing recovery using a backup image
US10129328B2 (en) Centralized management of webservice resources in an enterprise
JP2023517564A (ja) リモート・ファイルの予測プロビジョニング方法、システム、プログラム
US20230205634A1 (en) Method and system for performing replication recovery operation in a disaggregated distributed storage systems
US10909136B1 (en) Systems and methods for automatically linking data analytics to storage
CN115098469A (zh) 数据库迁移方法及装置、电子设备和可读存储介质
US20220334717A1 (en) System and Method for User Space NVMe-over-RDMA Host Library
US20240232387A1 (en) Intercepting and securing backup traffic
US11360797B2 (en) System and method for enabling dynamic configuration of virtual hardware
US10275296B2 (en) Method and system for resolving one or more errors in an enterprise storage system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20908518

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20908518

Country of ref document: EP

Kind code of ref document: A1