WO2021109686A1 - 集群资源的控制方法、装置和云计算系统 - Google Patents
集群资源的控制方法、装置和云计算系统 Download PDFInfo
- Publication number
- WO2021109686A1 WO2021109686A1 PCT/CN2020/117413 CN2020117413W WO2021109686A1 WO 2021109686 A1 WO2021109686 A1 WO 2021109686A1 CN 2020117413 W CN2020117413 W CN 2020117413W WO 2021109686 A1 WO2021109686 A1 WO 2021109686A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- expanded
- application
- executed
- processed
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 105
- 238000013515 script Methods 0.000 claims description 64
- 230000001419 dependent effect Effects 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 11
- 238000012546 transfer Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000011900 installation process Methods 0.000 claims description 6
- 230000000717 retained effect Effects 0.000 claims 1
- 238000007726 management method Methods 0.000 description 33
- 230000008602 contraction Effects 0.000 description 28
- 238000010586 diagram Methods 0.000 description 20
- 238000004064 recycling Methods 0.000 description 13
- 238000010276 construction Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 238000011084 recovery Methods 0.000 description 3
- 235000010425 Sorbus domestica Nutrition 0.000 description 2
- 240000005332 Sorbus domestica Species 0.000 description 2
- 238000004140 cleaning Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
Images
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/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5022—Mechanisms to release 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5055—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering software capabilities, i.e. software resources associated or available to the machine
-
- 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/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- 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
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5011—Pool
Definitions
- the present disclosure relates to the field of computer technology, and in particular to a method for controlling cluster resources, a device for controlling cluster resources, a cloud computing system, and a non-volatile computer-readable storage medium.
- resource control such as capacity expansion and contraction
- This kind of resource control has become an operation that operations and maintenance personnel need to perform on a regular basis.
- a method for controlling cluster resources including: determining a binding relationship between the resource to be expanded and an application when the resource to be controlled is a resource to be expanded; Add the resource to be expanded to the resource pool of the corresponding application that has the binding relationship with it; generate a data package to be executed of the application to be processed according to the deployment type of the application to be processed; and add the data package to be executed It is deployed and executed on the resource to be expanded in the resource pool of the application to be processed.
- the adding the initialized resource to be expanded to the resource pool of the corresponding application that has the binding relationship with it includes: transmitting the relevant information of the resource to be expanded to the front of the corresponding application. Script; execute the pre-script to complete the initialization of the resource to be expanded.
- generating the to-be-executed data package of the application to be processed includes: when the deployment type is package deployment, determining that the resource to be expanded is a physical machine, and generating the program package of the application to be processed as the The to-be-executed data package; in the case that the deployment type is an image deployment, the resource to be expanded is determined to be a container image, the program package of the to-be-processed application is generated, and based on the package and the to-be-processed application Run the mirror to generate the to-be-executed data package.
- the deploying the data packet to be executed on the resource to be expanded in the resource pool of the application to be processed for execution includes: when the resource to be expanded is a physical machine, the data packet to be executed Sent to the physical machine for execution; in the case that the resource to be expanded is a container image, the data packet to be executed is sent to an idle physical machine in the corresponding resource pool for execution.
- the deploying the data packet to be executed on the resource to be expanded in the resource pool of the application to be processed for execution includes: obtaining information about the resource to be expanded in the resource pool;
- the deployment interface configured for the application to be processed sends the relevant information about the resource to be expanded to the third-party program of the application to be processed, so that the third-party program deploys the data package to be executed according to its own deployment mode Execute on the resource to be expanded.
- the method further includes: executing a post script of the application to be processed, the post script being used for at least one of the following processing: returning the expansion result to the management node of the cluster; creating a volume for the expansion resource in the resource pool ; Clean up the garbage generated by the expansion process.
- the method further includes: establishing an SSH (Secure Shell, Secure Shell Protocol) connection with each resource to be expanded, used to execute each related script of the corresponding application, and can only communicate with each resource to be expanded at the same time.
- SSH Secure Shell, Secure Shell Protocol
- the method further includes: retaining the corresponding SSH connection for a preset period of time after the execution of the to-be-executed data packet of the corresponding application is completed.
- the method further includes: when the resource to be controlled is the resource to be scaled down, judging whether the resource to be scaled has important data, and whether there is a service that depends on the resource to be scaled down; when there is no important data If there are no services that depend on the resource to be scaled down, remove the resource to be scaled down from the cluster.
- the acquired information about the resource to be scaled is transferred through the configured shrink interface, so that the resource to be scaled can be removed from the cluster.
- the method further includes: obtaining the result of the reduction by polling the configured query interface.
- the method further includes: adding the resource to be scaled to the resource pool when the resource to be scaled is a physical machine; In the case of a container image, destroy the container image and add the resource to be reduced to the resource pool.
- the method further includes: when the resource to be scaled down is a physical machine, executing a post script of the scale-down processing, the post script is used to start the installation process to reinstall the operating system for the resource to be scaled down.
- a device for controlling cluster resources including: a determining unit, configured to determine the binding between the resource to be expanded and the application when the resource to be controlled is the resource to be expanded Relationship; adding unit for adding the initialized resource to be expanded to the resource pool of the application with the binding relationship; generating unit for generating the to-be-processed application according to the deployment type of the application to be processed Application data package to be executed; an execution unit, configured to deploy the data package to be executed on the resource to be expanded in the resource pool of the application to be processed for execution.
- the adding unit transmits the relevant information of the resource to be expanded to the pre-script of the corresponding application, and executes the pre-script to complete the initialization of the resource to be expanded.
- the deployment type when the deployment type is package deployment, it is determined that the resource to be expanded is a physical machine, and the generating unit generates the package of the application to be processed as the data package to be executed; when the deployment type is image deployment, it is determined The resource to be expanded is a container image, and the generating unit generates a program package of the application to be processed, and generates a data package to be executed according to the program package and the running image of the application to be processed.
- the execution unit when the resource to be expanded is a physical machine, the execution unit sends the data packet to be executed to the physical machine for execution; when the resource to be expanded is a container image, the execution unit sends the data packet to be executed to Execution on an idle physical machine in the corresponding resource pool.
- the execution unit obtains information about the resource to be expanded in the resource pool, and sends the information about the resource to be expanded to the third-party program of the application to be processed through a deployment interface configured for the application to be processed. So that the third-party program deploys the data package to be executed on the resource to be expanded for execution according to its own deployment method.
- the execution unit executes a post-script of the application to be processed, and the post-script is used for at least one of the following processing: returning the expansion result to the management node of the cluster; creating a volume for the expansion resource in the resource pool; cleaning up and expanding the capacity Dispose of the generated garbage.
- the device further includes an establishment unit for establishing an SSH connection with each resource to be expanded, and for executing each related script of the corresponding application. Only one SSH connection can be established with each resource to be expanded at the same time. connection.
- the establishment unit retains the corresponding SSH connection for a preset period of time after the execution of the to-be-executed data packet of the corresponding application is completed.
- the device further includes a scaling unit for determining whether the resource to be scaled has important data and whether there is a service that depends on the resource to be scaled when the resource to be controlled is the resource to be scaled down. ;
- the shrinking unit removes the resources to be scaled from the cluster when there is no important data and there are no services that depend on the resources to be scaled down.
- the shrinking unit transmits the acquired information about the resource to be shrinked through the configured shrinking interface, so as to remove the resource to be shrinked from the cluster.
- the shrinking unit obtains the shrinking result by polling the configured query interface.
- the adding unit adds the resource to be shrinked to the resource pool;
- the shrinking unit destroys the container image, and the adding unit adds the resource to be shrinked to the resource pool.
- the execution unit executes a post script of the scale-down processing, and the post script is used to start the installation process to reinstall the operating system for the resource to be scaled down.
- a device for controlling cluster resources including: a memory; and a processor coupled to the memory, and the processor is configured to execute any of the foregoing implementations based on instructions stored in the memory device The control method of cluster resources in the example.
- a non-volatile computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the method for controlling cluster resources in any of the above embodiments is implemented.
- a cloud computing system including: a cluster resource control device, configured to execute the cluster resource control method in any one of the above embodiments.
- Fig. 1 shows a flowchart of some embodiments of a method for controlling cluster resources of the present disclosure
- FIG. 2 shows a flowchart of other embodiments of the cluster resource control method of the present disclosure
- Figure 3 shows a schematic diagram of some embodiments of the cluster resource control device of the present disclosure
- FIG. 4 shows a flowchart of still other embodiments of the cluster resource control method of the present disclosure
- Figure 5 shows a schematic diagram of other embodiments of the cluster resource control device of the present disclosure.
- Fig. 6 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure
- FIG. 7 shows a schematic diagram of some embodiments of the method for controlling cluster resources of the present disclosure
- FIG. 8 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure.
- FIG. 9 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure.
- Figure 10 shows a block diagram of some embodiments of the cluster resource control device of the present disclosure
- FIG. 11 shows a block diagram of other embodiments of the cluster resource control device of the present disclosure.
- FIG. 12 shows a block diagram of still other embodiments of the cluster resource control device of the present disclosure.
- FIG. 13 shows a block diagram of some embodiments of the cluster resource control system of the present disclosure.
- the inventor of the present disclosure found that the above-mentioned related technology has the following problem: it cannot be applied to resource expansion of applications of different services, resulting in poor applicability.
- the present disclosure proposes a technical solution for controlling cluster resources, which can improve the applicability of resource expansion.
- FIG. 1 shows a flowchart of some embodiments of the method for controlling cluster resources of the present disclosure.
- the method includes: step S11, determining the binding relationship; step S12, adding resources to be expanded; step S13, generating data packets to be executed; and step S14, deploying data packets to be executed.
- step S11 when the resource to be controlled is the resource to be expanded, the binding relationship between the resource to be expanded and the corresponding application is determined.
- the resource to be expanded can be a physical machine or a container image.
- step S12 according to the binding relationship, the initialized resource to be expanded is added to the resource pool of the corresponding application.
- the relevant information of the resource to be expanded is transferred to the pre-script of the corresponding application; the pre-script is executed to complete the initialization of the resource to be expanded.
- step S13 the to-be-executed data package of the to-be-processed application is generated according to the deployment type of the to-be-processed application.
- the program package of the application to be processed is generated as the data package to be executed.
- the resources to be expanded are physical machines.
- the program package of the application to be processed is generated, and the data package to be executed is generated according to the program package and the running image of the application to be processed.
- the resource to be expanded is a container image.
- step S14 the data package to be executed is deployed on the corresponding resource to be expanded in the resource pool of the application to be processed for execution.
- the data packet to be executed is sent to the physical machine for execution; when the resource to be expanded is a container image, the data packet to be executed is sent to the corresponding resource pool (The idle physical machine in the standby machine pool is executed.
- the spare machine pool is a spare physical machine resource pool in the cloud computing system.
- the relevant information of the resource to be expanded is obtained; the relevant information of the resource to be expanded is sent to the third-party program of the application to be processed through the deployment interface configured for the application to be processed; the third-party program is deployed according to its own deployment In this way, the data package to be executed is deployed on the resource to be expanded for execution.
- the post script of the application to be processed is executed, and the post script is used for at least one of the following processing: return the expansion result to the management node of the cluster; create a corresponding volume for the corresponding expansion resource; clean up Expansion of the garbage generated.
- an SSH connection is established with each resource to be expanded to execute each related script of the corresponding application, and only one SSH connection can be established with each resource to be expanded at the same time.
- the corresponding SSH connection is reserved for a preset period of time, so that the next time the to-be-executed data packet of the corresponding application is executed, the SSH connection.
- FIG. 2 shows a flowchart of other embodiments of the method for controlling cluster resources of the present disclosure.
- the method further includes: step S21, judging important data and dependent services; and S22, removing the resource to be scaled down.
- step S21 when the resource to be controlled is a resource to be scaled down, it is determined whether the resource to be scaled down has important data and whether there is a service that depends on the resource to be scaled down.
- step S22 when there is no important data, and there is no service that depends on the resource to be scaled down, the resource to be scaled down is removed from the cluster.
- the acquired information about the resource to be scaled can be transferred in the system through the configured shrinking interface, so that the resource to be scaled can be removed from the cluster; and the configured query interface can be polled to obtain the shrinking. Content result.
- the resource to be scaled down when the resource to be scaled down is a physical machine, the resource to be scaled down is added to the resource pool (standby pool); when the resource to be scaled down is a container image, the container image is destroyed, And add the resources to be reduced to the resource pool.
- a post script of the scale-down process is executed.
- the post script is used to start the installation process to reinstall the operating system for the resources to be scaled down. For example, reinstallation can be achieved through PXE (Preboot eXecution Environment).
- Fig. 3 shows a schematic diagram of some embodiments of the cluster resource control apparatus of the present disclosure.
- the user can interact with the back-end expansion (or contraction) controller (ie, the control device) through the front-end Web (network) page.
- the front-end Web page can be implemented by an Nginx (engine x, x engine) server; the control device can be implemented by the Golang programming language.
- the internal structure of the control device can be a unified resource control system for complex proprietary cloud clusters that supports concurrent expansion and contraction of multiple components.
- Each line of business script can be connected to the control device.
- control device may include multiple modules such as a multi-component expansion and contraction controller, a heterogeneous component resource management module, a concurrent expansion and contraction executor, a unified component construction system, a multi-component deployment system, and a component reduction and recovery system.
- modules such as a multi-component expansion and contraction controller, a heterogeneous component resource management module, a concurrent expansion and contraction executor, a unified component construction system, a multi-component deployment system, and a component reduction and recovery system.
- a multi-component capacity expansion controller (for example, including a determining unit, an adding unit, etc.) is responsible for controlling the overall capacity expansion and contraction process.
- a multi-component expansion and contraction controller can coordinate the work of other modules; control and call each module used in expansion and contraction; and provide necessary data parameters.
- the heterogeneous component resource management module is responsible for managing all metadata required in the process of capacity expansion and contraction.
- metadata includes server (physical machine resource) management IP (Internet Protocol, Internet Protocol), server specification parameters, expansion and contraction application data, and so on.
- a heterogeneous component resource management module can use a relational database MySQL (My Structured Query Language, My Structured Sequence Language) to persistently store data.
- MySQL My Structured Query Language, My Structured Sequence Language
- the heterogeneous component resource management module can be deployed independently, and an OpenAPI (Open Application Programming Interface, open application programming interface) call interface is provided to the outside.
- OpenAPI Open Application Programming Interface, open application programming interface
- the concurrent expansion and contraction executor (for example, it may include an execution unit, an establishment unit, etc.) is responsible for executing the scripts that each resource server needs to run at different stages.
- the bottom layer of the concurrent expansion and contraction executor can be a connection pool based on the SSH protocol.
- the concurrent expansion and contraction executor can be implemented through the Golang programming language to ensure high concurrency.
- the concurrent expansion and contraction actuator can establish an SSH connection between the control device and the resource to be expanded.
- the concurrent expansion and contraction executor can execute a custom expansion and contraction process.
- IaaS infrastructure as a Service
- infrastructure as a service infrastructure as a service
- the concurrent expansion and contraction executor can perform standardized expansion and contraction procedures.
- the concurrent expansion and contraction executor can trigger a unified component construction system, a multi-component deployment system, and a component reduction and recycling system.
- the unified component construction system, the multi-component deployment system, and the component shrinking and recycling system perform related processing on the expansion and shrinkage of the cloud computing system cluster.
- the unified component construction system (for example, may include a generation unit) is responsible for compiling the source code of each resource server for online deployment; based on the Docker container, different compilation environments are prepared for different resource servers.
- the unified component construction system can realize the isolation of the compilation environment, so that the dependent services required by the compilation do not interfere with each other, thereby ensuring the smooth progress of the compilation work.
- a multi-component deployment system (for example, it may include an execution unit) is responsible for online deployment of the compiled program to a designated physical server or container.
- a multi-component deployment system can include two types: package deployment and image deployment.
- Package deployment will bring the compiled program online to the designated physical machine; image deployment will run the image packaged at compile time, and according to the required resources (including the number of CPU cores required for operation, memory size, hard disk size, etc. ) Deploy and start the container.
- the component shrinking and recycling system (for example, it may include a shrinking unit and an adding unit) is responsible for recovering the shrinking resources.
- the recycled container resources will be placed in the resource pool again, and the recycled physical machine will be placed in the spare machine pool.
- the component shrinking and recycling system destroys container resources, reinstalls the recovered physical machine, and formats the data disk.
- FIG. 4 shows a flowchart of still other embodiments of the method for controlling cluster resources of the present disclosure.
- the method may include a capacity expansion process (the process on the left in the figure) and a contraction process (the process on the right in the figure).
- the expansion process may include a standardized expansion process and a custom expansion process;
- the shrinking process may include a standardized scaling process and a custom scaling process.
- the expansion and shrinking of various resource nodes (such as MySQL resource nodes, mass storage resource nodes, etc.) related to IaaS and cloud database products belong to the custom expansion and shrinking process; it is related to cloud storage and data cloud
- the expansion and shrinking of various resource nodes (such as ds2-datanode resource node, big data datanode resource node, etc.) belong to the standardized expansion and shrinking process.
- the expansion and shrinking processes of the above-mentioned products all need to go through three common processes, namely, allocation of uses (that is, binding of resources to be expanded and scaled to the corresponding product application), execution of pre-scripts and execution of post-scripts. These public processes can be extracted to establish resource control methods with high applicability.
- the standardized expansion process mainly includes: mounting the standby machine (resource) to be expanded to the standby machine pool of the specified product application; compiling and building the application package or running the image; deploying the program package or image to the standby machine Servers in the machine pool; poll the deployment results.
- the expansion process of data cloud products is mainly for big data datanode resource nodes, and the standardized expansion process may include the following steps.
- step 1 allocate uses for the expanded host.
- the server (resource) to be expanded is allocated the tag mark of the big data datanode resource node, so as to realize the binding of the resource to be expanded and the application.
- a multi-component expansion controller can call the preset script (pre-script) of the data cloud in the FTP (File Transfer Protocol) directory of the control machine, and use the IP list of the server to be expanded as a command line
- the parameters are passed to the preset script.
- the control machine may be a computer running the control method of the present disclosure in a cluster.
- the preset script is mainly responsible for initializing and expanding the physical machine, such as installing some basic software packages.
- step 3 hang on the expansion host. For example, mount the physical machine to be expanded into the spare machine pool of the corresponding product line in the product service tree to facilitate uniform resource allocation.
- the resource to be expanded can be added to the resource pool of the product line to which the bound application belongs based on the relevant information of the product to be deployed in the cloud computing system.
- the related information of the product to be deployed in the cloud computing system may be stored in a tree structure.
- a tree structure For example, it can be stored in a five-level tree structure of departments, product lines, products, systems, and applications.
- step 4 compile and create a data package. For example, according to the deployment type of the application, compile and build the application package. If the big data datanode resource node uses package deployment, the corresponding program package is compiled as the processing data package; for image deployment, the program package and the running image are packaged together to generate the to-be-processed data package. Transfer the compiled and built program package to the bound machine to be expanded in the standby machine pool, and execute the startup script.
- step 5 poll the expansion results.
- the deployment situation can be polled regularly, and the deployment result can be recorded in the deployment unit of the information management module CMDB (Configuration Management Database).
- CMDB Configuration Management Database
- the web front-end can query the deployment result and present it to the user through the API interface.
- step 6 the post script is executed to process the post-expansion transaction.
- the post script can inform the management node in the cluster of the expanded resource node to complete the expansion of the cluster.
- the ds2-datanode resource node expansion is mainly completed, and the process steps are similar to the above data cloud.
- the post script of the cloud storage expansion process can perform the process of creating a volume.
- the standardized shrinking process may include business data checking, dependent service checking, moving out of the cluster, reclaiming resources, polling results, and executing post scripts.
- the standardized shrinking process may include the following steps.
- step 1 check the business data of the resource to be scaled down to determine whether there is important data in the resource to be scaled down. If there is important data, the resource to be scaled does not support the scale-down operation.
- step 2 a dependent service check is performed on the resource to be scaled down, and it is determined whether there is a service dependent on its operation. If there are dependent services, the resource to be scaled does not support scale-down operations.
- step 3 notify the management node of the cluster to move the resource to be reduced out of the cluster.
- step 4 the component shrinking and recycling system is called to recover the shrinking resources.
- step 5 poll the shrinking result.
- step 6 the post script is executed to process the post-scaled transaction. For example, you can trigger the PXE installation operation to reclaim resources.
- the custom expansion process may include: mounting the standby machine to be expanded into the designated product application standby machine pool; the third party provides its own expansion program (third-party program), and the expansion program must provide two Standard expansion interface, namely trigger expansion interface (deployment interface) and query expansion result interface (query interface); the multi-component expansion controller calls the trigger expansion interface, and passes the information of the standby machine to be expanded in the form of parameters; The interface for querying the expansion result polls the expansion result.
- custom expansion process for the application of IaaS products can be implemented through the following steps.
- step 1 allocate uses for the expanded host.
- the server to be expanded is assigned the tag mark of the resource node of the IaaS product application.
- step 2 execute the pre-script.
- the multi-component capacity expansion controller calls the data cloud preset script in the FTP directory of the management and control machine, and passes the IP list of the expanded machine as a command line parameter to the preset script; executes the expansion script to complete the initialization of the machine.
- the preset script is mainly responsible for initializing and expanding the physical machine, for example, installing some basic software packages.
- step 3 hang on the expansion host. For example, mount the physical machine to be expanded into the spare machine pool of the corresponding product line in the product's service tree for unified acquisition by third-party programs.
- step 4 transfer the expansion host.
- the multi-component expansion and contraction controller triggers the IaaS deployment interface, and obtains the relevant information of the server to be expanded from the information management CMDB; passes the preliminary information to the IaaS product in the form of parameters; the IaaS product deployment program goes to the standby pool to obtain The deployed server to be expanded; the IaaS deployment service is deployed online according to its own business.
- step 5 call the polling interface.
- the multi-component expansion controller periodically polls the IaaS expansion results; records the deployment results to the deployment unit of the information management module CMDB; the web front-end can query the deployment results through the API interface and present them to users.
- step 6 the post script is executed. If the product does not have a post script, this step can be empty.
- the custom scaling process may include business data checking, dependent service checking, calling a custom scaling interface, polling scaling results, reclaiming resources to the resource pool or standby pool, and executing post scripts. For example, you can implement a custom shrinking process through the following steps.
- step 1 check the business data of the resource to be scaled down to determine whether there is important data in the resource to be scaled down. If there is important data, the resource to be scaled does not support the scale-down operation.
- step 2 a dependent service check is performed on the resource to be scaled down, and it is determined whether there is a service dependent on its operation. If there are dependent services, the resource to be scaled does not support scale-down operations.
- step 3 call the self-defined shrinking interface to transfer the relevant information of the resource to be shrinked.
- step 4 poll the customized shrinking result interface (query interface) to obtain the shrinking result.
- step 5 put the recovered resources into the resource pool or the standby pool.
- Fig. 5 shows a schematic diagram of other embodiments of the cluster resource control device of the present disclosure.
- the heterogeneous component resource management module is mainly composed of the service layer and the data layer, and is used to provide other service modules and Web front-end UI (User Interface) through the Http (HyperText Transfer Protocol) API. Provide metadata. Supervisor can perform service monitoring on heterogeneous component resource management modules.
- the service layer includes an API server, a server information management unit, a container information management unit, a product information management unit, a compilation information management unit, and a deployment information management unit.
- the API server may be HTTP Server (server) developed based on Golang.
- the API server provides a Restful (Representational State Transfer) style interface externally, and is responsible for safely and legally providing internally managed data to users.
- the server information management unit is mainly responsible for managing all physical machine information in the cluster.
- the physical machine information may include the management node server, the resource node server that has been used, and the resource standby machine to be expanded and contracted.
- the server information management unit can manage the full amount of server information and can provide necessary information for subsequent server deployment, configuration, and recovery.
- the container information management unit serves to manage all container information in the cluster.
- the container information may include the number of CPU cores used by the container to run, the size of the memory, the size of the hard disk, the physical machine to which it belongs, and product applications.
- the product information management unit is responsible for managing product information deployed in the proprietary cloud.
- Product information can adopt a tree structure.
- the tree structure can be divided into five levels: department, product line, product, system, and application.
- the physical machines to be expanded and contracted need to be allocated to specific system applications to facilitate centralized management of the expansion and contraction process.
- the compiled information management unit is responsible for managing the compiled programs of each product application.
- the compilation information management unit can be developed based on Jenkins and supports automatically pulling code from the source code repository (gitlab).
- the compilation information management unit can compile and construct an application binary program or image (including running images and program packages) according to the configuration information.
- the deployment information management unit is responsible for deploying the compiled program package or packaged image to a designated physical machine or container, and recording all deployment records.
- the data layer can include a master storage node, a slave storage node, and a memory.
- the primary storage node stores various information sent from the service layer, and synchronously backs it up to the secondary storage node. For example, the data in the primary storage node can be backed up to the memory periodically to avoid obtaining backup data when both the primary storage node and the secondary storage node are contaminated.
- FIG. 6 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure.
- the multi-component expansion controller can be an SSH controller built by Golang.
- Each line of business script can be connected to the internal structure of the multi-component expansion controller.
- the multi-component capacity expansion controller executes the pre-script and the post-script, it needs to use a concurrent expansion and contraction executor to complete it.
- the bottom layer of the concurrent expansion and contraction executor is a high-performance SSH concurrent connection pool based on Golang.
- the connection pool includes SSH connections to the resources to be expanded.
- connection pool For example, a series of operation interfaces such as connecting to physical machines and executing script commands can be encapsulated on the basis of the connection pool. Due to the high concurrency characteristics of the Golang language, combined with the above connection pool, it can ensure large-scale concurrent operations on servers and containers, thereby improving the efficiency of scaling execution.
- connection pool only establishes one SSH connection for each resource (physical machine, container image) to be expanded or downsized, and periodically cleans up expired SSH connections.
- FIG. 7 shows a schematic diagram of some embodiments of the method for controlling cluster resources of the present disclosure.
- the method includes.
- the user submits relevant code to the git distributed version control system; git triggers the compilation, construction and online deployment process of the Jenkins automation server.
- the triggering of the compilation and build process can include manual triggering and automatic triggering after the user submits the code.
- Jenkins uses Docker to compile, build and compile images, and deploy them online.
- a program package or program image can be generated according to the type of application.
- the big data datanode resource node uses package deployment, that is, the compiled and constructed output is only the program package, excluding the running image; for the image deployment type, the program package and the running image will be packaged together as a program image.
- FIG. 8 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure.
- the multi-component expansion controller transmits the data packets compiled and constructed by the component unified construction system to the physical machine to be expanded through the concurrent expansion and contraction executor according to the type of expansion application. Free machines in the resource pool.
- the multi-component deployment system executes the startup script, deploys the package on the physical machine of the private cloud cluster, and checks the execution status; in the case of program image deployment, the multi-component deployment system Start the image and check the running status of the container in the Apsara Stack cluster.
- FIG. 9 shows a schematic diagram of still other embodiments of the cluster resource control device of the present disclosure.
- the component shrinking recycling system performs container resource recycling and physical machine resource recycling.
- the component shrinking recovery system adds the physical machine to the standby machine pool and calls the PXE reinstallation system; what is recovered is the program image (container) of the private cloud cluster.
- the component shrinking and recycling system will destroy the container and recycle the resources to the resource pool.
- the component shrinking and recycling system before shrinking, needs to check whether there is business data in the shrinking server or container; and, the component shrinking and recycling system needs to check whether the shrinking server or container has other applications deployed.
- Dependent services In the presence of business data or dependent services, the component shrinking and recycling system exits the shrinking process.
- the component recycling system in order to clear the deployed services on the physical machine, can start the PXE installation process, reinstall the operating system on the reduced physical machine and format the data disk, and then put the reduced resources into the standby machine Pool; or after the container is destroyed, the shrinking resources are put into the resource pool.
- FIG. 10 shows a block diagram of some embodiments of the device for controlling cluster resources of the present disclosure.
- the device 10 for controlling cluster resources includes a determining unit 101, an adding unit 102, a generating unit 103, and an executing unit 104.
- the determining unit 101 determines the binding relationship between the resource to be expanded and the corresponding application.
- the adding unit 102 adds the initialized resources to be expanded to the resource pool of the corresponding application according to the binding relationship.
- the adding unit 102 transmits the relevant information of the resource to be expanded to the pre-script of the corresponding application, and executes the pre-script to complete the initialization of the resource to be expanded.
- the generating unit 103 generates the to-be-executed data package of the to-be-processed application according to the deployment type of the to-be-processed application.
- the resource to be expanded is a physical machine
- the generating unit 103 generates the program package of the application to be processed as the data package to be executed
- the expansion resource is a container image
- the generating unit 103 generates a program package of the application to be processed, and generates a data package to be executed according to the program package and the running image of the application to be processed.
- the execution unit 104 deploys the data package to be executed on the corresponding resource to be expanded in the resource pool of the application to be processed for execution.
- the execution unit 104 when the resource to be expanded is a physical machine, the execution unit 104 sends the data packet to be executed to the physical machine for execution; when the resource to be expanded is a container image, the execution unit 104 sends the data packet to be executed Sent to the idle physical machine in the corresponding resource pool for execution.
- the execution unit 104 obtains the relevant information of the resource to be expanded, and sends the relevant information of the resource to be expanded to the third-party program of the application to be processed through the deployment interface configured for the application to be processed, so that the third-party program According to your own deployment method, deploy the data package to be executed on the resource to be expanded for execution.
- the execution unit 104 executes a post script of the application to be processed, and the post script is used for at least one of the following processing: returning the expansion result to the management node of the cluster; creating a corresponding volume for the corresponding expansion resource; cleaning up Expansion of the garbage generated.
- the device 10 for controlling cluster resources further includes an establishing unit 105 for establishing an SSH connection with each resource to be expanded.
- the SSH connection is used to execute the relevant scripts of the corresponding application.
- the establishing unit 105 can only establish one SSH connection with each resource to be expanded at the same time.
- the establishing unit 105 retains the corresponding SSH connection for a preset period of time after the execution of the to-be-executed data packet of the corresponding application is completed.
- the cluster resource control device 10 further includes a shrinking unit 106, which is used to determine whether the resource to be scaled has important data and whether the resource depends on the resource to be scaled.
- the service of shrinking the resource; the shrinking unit 106 removes the resource to be shrinked from the cluster when there is no important data and there is no service that depends on the resource to be reduced.
- the shrinking unit transmits the acquired information about the resource to be shrinked through the configured shrinking interface, so as to remove the resource to be shrinked from the cluster.
- the shrinking unit 106 obtains the shrinking result by polling the configured query interface.
- the adding unit 102 adds the resource to be shrinked to the resource pool;
- the shrinking unit 106 destroys the container image, and the adding unit adds the resource to be shrinked to the resource pool.
- the execution unit 104 executes a post script of the scale-down processing, and the post script is used to start the installation process to reinstall the operating system on the resource to be scaled down.
- FIG. 11 shows a block diagram of other embodiments of the device for controlling cluster resources of the present disclosure.
- the cluster resource control device 11 of this embodiment includes a memory 111 and a processor 112 coupled to the memory 111.
- the processor 112 is configured to execute the present disclosure based on instructions stored in the memory 111.
- the memory 111 may include, for example, a system memory, a fixed non-volatile storage medium, and the like.
- the system memory stores an operating system, application programs, boot loader, database, and other programs, for example.
- FIG. 12 shows a block diagram of still other embodiments of the cluster resource control device of the present disclosure.
- the cluster resource control device 12 of this embodiment includes a memory 1210 and a processor 1220 coupled to the memory 1210.
- the processor 1220 is configured to execute any of the foregoing based on instructions stored in the memory 1210.
- a method for controlling cluster resources in an embodiment is shown in FIG. 12, the cluster resource control device 12 of this embodiment.
- the memory 1210 may include, for example, a system memory, a fixed non-volatile storage medium, and the like.
- the system memory stores, for example, an operating system, an application program, a boot loader, and other programs.
- the cluster resource control device 12 may also include an input/output interface 1230, a network interface 1240, a storage interface 1250, and the like. These interfaces 1230, 1240, 1250, the memory 1210 and the processor 1220 may be connected via a bus 1260, for example.
- the input and output interface 1230 provides a connection interface for input and output devices such as a display, a mouse, a keyboard, and a touch screen.
- the network interface 1240 provides a connection interface for various networked devices.
- the storage interface 1250 provides connection interfaces for external storage devices such as SD cards and U disks.
- the embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media containing computer-usable program codes.
- FIG. 13 shows a block diagram of some embodiments of the cluster resource control system of the present disclosure.
- the cloud computing system 13 includes a cluster resource control device 131 for executing the cluster resource control method in any of the above embodiments.
- the embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. .
- the method and system of the present disclosure may be implemented in many ways.
- the method and system of the present disclosure can be implemented by software, hardware, firmware or any combination of software, hardware, and firmware.
- the above-mentioned order of the steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless specifically stated otherwise.
- the present disclosure can also be implemented as programs recorded in a recording medium, and these programs include machine-readable instructions for implementing the method according to the present disclosure.
- the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims (16)
- 一种集群资源的控制方法,包括:在待控制资源为待扩容资源的情况下,确定所述待扩容资源与应用之间的绑定关系;将初始化后的所述待扩容资源添加到与其具有所述绑定关系的相应应用的资源池中;根据待处理应用的部署类型,生成所述待处理应用的待执行数据包;将所述待执行数据包部署在所述待处理应用的资源池中的待扩容资源上执行。
- 根据权利要求1所述的控制方法,其中,所述将初始化后的所述待扩容资源添加到与其具有所述绑定关系的相应应用的资源池中包括:将所述待扩容资源的相关信息传递给相应应用的前置脚本;执行所述前置脚本,以完成所述待扩容资源的初始化。
- 根据权利要求1所述的控制方法,其中,所述生成所述待处理应用的待执行数据包包括:在所述部署类型为包部署的情况下,确定所述待扩容资源为物理机,生成所述待处理应用的程序包作为所述待执行数据包;在所述部署类型为镜像部署的情况下,确定所述待扩容资源为容器镜像,生成所述待处理应用的程序包,并根据该程序包和所述待处理应用的运行镜像,生成所述待执行数据包。
- 根据权利要求3述的控制方法,其中,所述将所述待执行数据包部署在所述待处理应用的资源池中的待扩容资源上执行包括:在待扩容资源为物理机的情况下,将所述待执行数据包发送给所述物理机执行;在待扩容资源为容器镜像的情况下,将所述待执行数据包发送给相应资源池中的空闲物理机执行。
- 根据权利要求1的控制方法,其中,所述将所述待执行数据包部署在所述待处理应用的资源池中的待扩容资源上执行包括:获取所述资源池中的待扩容资源的相关信息;通过为所述待处理应用配置的部署接口,将该待扩容资源的相关信息发送给所述待处理应用的第三方程序,以便所述第三方程序根据自己的部署方式,将所述待执行 数据包部署在该待扩容资源上执行。
- 根据权利要求1的控制方法,还包括:执行所述待处理应用的后置脚本,所述后置脚本用于以下处理的至少一项:向集群的管理节点返回扩容结果;为所述资源池中的扩容资源创建卷;清理扩容处理产生的垃圾。
- 根据权利要求1的控制方法,还包括:建立与各待扩容资源的安全壳协议SSH连接,用于执行所述相应应用的各相关脚本,在同一时间内只能与每个待扩容资源建立一条SSH连接。
- 根据权利要求7的控制方法,还包括:在所述相应应用的待执行数据包执行完毕后,在预设的时间段内保留相应的SSH连接。
- 根据权利要求1-8任一项的控制方法,还包括:在待控制资源为待缩容资源的情况下,判断所述待缩容资源是否存在重要数据,以及是否存在依赖于所述待缩容资源的服务;在不存在重要数据,且不存在依赖于所述待缩容资源的服务的情况下,将所述待缩容资源从集群中移除。
- 根据权利要求9的控制方法,其中,所述将所述待缩容资源从集群中移除包括:通过配置的缩容接口,传递获取的所述待缩容资源的相关信息,以便将所述待缩容资源从集群中移除;还包括:通过轮询配置的查询接口,获取缩容结果。
- 根据权利要求9的控制方法,将所述待缩容资源从集群中移除后,还包括:在所述待缩容资源为物理机的情况下,将所述待缩容资源添加到资源池;在所述待缩容资源为容器镜像的情况下,销毁该容器镜像,并将所述待缩容资源添加到资源池。
- 根据权利要求11的控制方法,还包括:在所述待缩容资源为物理机的情况下,执行缩容处理的后置脚本,所述后置脚本用于启动装机流程对所述待缩容资源进行操作系统重装。
- 一种集群资源的控制装置,包括:确定单元,用于在待控制资源为待扩容资源的情况下,确定所述待扩容资源与应用之间的绑定关系;添加单元,用于将初始化后的所述待扩容资源添加到与其具有所述绑定关系的相应应用的资源池中;生成单元,用于根据待处理应用的部署类型,生成所述待处理应用的待执行数据包;执行单元,用于将所述待执行数据包部署在所述待处理应用的资源池中的待扩容资源上执行。
- 一种集群资源的控制装置,包括:存储器;和耦接至所述存储器的处理器,所述处理器被配置为基于存储在所述存储器中的指令,执行权利要求1-12任一项所述的集群资源的控制方法。
- 一种云计算系统,包括:集群资源的控制装置,用于执行权利要求1-12任一项所述的集群资源的控制方法。
- 一种非易失性计算机可读存储介质,其上存储有计算机程序,该程序被处理器执行时实现权利要求1-12任一项所述的集群资源的控制方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2022534290A JP2023504870A (ja) | 2019-12-05 | 2020-09-24 | クラスタリソースの制御方法および装置、ならびにクラウドコンピューティングシステム |
EP20897260.4A EP4071611A4 (en) | 2019-12-05 | 2020-09-24 | METHOD FOR CONTROLLING CLUSTER RESOURCES AND APPARATUS AND CLOUD COMPUTING SYSTEM |
US17/782,110 US20230004439A1 (en) | 2019-12-05 | 2020-09-24 | Control method and apparatus of cluster resource, and cloud computing system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911232841.4 | 2019-12-05 | ||
CN201911232841.4A CN110968427A (zh) | 2019-12-05 | 2019-12-05 | 集群资源的控制方法、装置和云计算系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021109686A1 true WO2021109686A1 (zh) | 2021-06-10 |
Family
ID=70033132
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/117413 WO2021109686A1 (zh) | 2019-12-05 | 2020-09-24 | 集群资源的控制方法、装置和云计算系统 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230004439A1 (zh) |
EP (1) | EP4071611A4 (zh) |
JP (1) | JP2023504870A (zh) |
CN (1) | CN110968427A (zh) |
WO (1) | WO2021109686A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116010096A (zh) * | 2023-01-04 | 2023-04-25 | 上海弘积信息科技有限公司 | 一种负载均衡设备集中管理方法及系统 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110968427A (zh) * | 2019-12-05 | 2020-04-07 | 北京京东尚科信息技术有限公司 | 集群资源的控制方法、装置和云计算系统 |
CN112698916B (zh) * | 2020-12-31 | 2024-04-12 | 北京千方科技股份有限公司 | 一种多容器集群的管控系统、方法以及存储介质 |
CN113472565B (zh) * | 2021-06-03 | 2024-02-20 | 北京闲徕互娱网络科技有限公司 | 服务器功能的扩容方法、装置、设备和计算机可读介质 |
CN115292045B (zh) * | 2022-08-09 | 2023-06-23 | 安超云软件有限公司 | Jenkins多节点复用的方法、系统及电子设备 |
CN117648173B (zh) * | 2024-01-26 | 2024-05-14 | 杭州阿里云飞天信息技术有限公司 | 资源调度方法以及装置 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105867955A (zh) * | 2015-09-18 | 2016-08-17 | 乐视云计算有限公司 | 一种应用程序部署系统及部署方法 |
TW201812611A (zh) * | 2016-09-01 | 2018-04-01 | 中華電信股份有限公司 | 基於動態叢集規則範本之服務元件自動建構與水平延展的系統與方法 |
CN109062666A (zh) * | 2018-07-27 | 2018-12-21 | 浪潮电子信息产业股份有限公司 | 一种虚拟机集群管理方法及相关装置 |
CN110597623A (zh) * | 2019-08-13 | 2019-12-20 | 平安普惠企业管理有限公司 | 容器资源分配方法、装置、计算机设备和存储介质 |
CN110825494A (zh) * | 2019-11-01 | 2020-02-21 | 北京京东尚科信息技术有限公司 | 物理机调度方法及装置、计算机可存储介质 |
CN110968427A (zh) * | 2019-12-05 | 2020-04-07 | 北京京东尚科信息技术有限公司 | 集群资源的控制方法、装置和云计算系统 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8584131B2 (en) * | 2007-03-30 | 2013-11-12 | International Business Machines Corporation | Method and system for modeling and analyzing computing resource requirements of software applications in a shared and distributed computing environment |
CN109803018B (zh) * | 2019-01-24 | 2022-06-03 | 云南电网有限责任公司信息中心 | 一种基于Mesos和YARN结合的DCOS云管理平台 |
CN110333877A (zh) * | 2019-07-09 | 2019-10-15 | 西安点告网络科技有限公司 | 基于应用的可视化容器配置管理方法、装置及系统 |
-
2019
- 2019-12-05 CN CN201911232841.4A patent/CN110968427A/zh active Pending
-
2020
- 2020-09-24 US US17/782,110 patent/US20230004439A1/en active Pending
- 2020-09-24 WO PCT/CN2020/117413 patent/WO2021109686A1/zh active Application Filing
- 2020-09-24 JP JP2022534290A patent/JP2023504870A/ja active Pending
- 2020-09-24 EP EP20897260.4A patent/EP4071611A4/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105867955A (zh) * | 2015-09-18 | 2016-08-17 | 乐视云计算有限公司 | 一种应用程序部署系统及部署方法 |
TW201812611A (zh) * | 2016-09-01 | 2018-04-01 | 中華電信股份有限公司 | 基於動態叢集規則範本之服務元件自動建構與水平延展的系統與方法 |
CN109062666A (zh) * | 2018-07-27 | 2018-12-21 | 浪潮电子信息产业股份有限公司 | 一种虚拟机集群管理方法及相关装置 |
CN110597623A (zh) * | 2019-08-13 | 2019-12-20 | 平安普惠企业管理有限公司 | 容器资源分配方法、装置、计算机设备和存储介质 |
CN110825494A (zh) * | 2019-11-01 | 2020-02-21 | 北京京东尚科信息技术有限公司 | 物理机调度方法及装置、计算机可存储介质 |
CN110968427A (zh) * | 2019-12-05 | 2020-04-07 | 北京京东尚科信息技术有限公司 | 集群资源的控制方法、装置和云计算系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4071611A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116010096A (zh) * | 2023-01-04 | 2023-04-25 | 上海弘积信息科技有限公司 | 一种负载均衡设备集中管理方法及系统 |
Also Published As
Publication number | Publication date |
---|---|
US20230004439A1 (en) | 2023-01-05 |
CN110968427A (zh) | 2020-04-07 |
JP2023504870A (ja) | 2023-02-07 |
EP4071611A1 (en) | 2022-10-12 |
EP4071611A4 (en) | 2023-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021109686A1 (zh) | 集群资源的控制方法、装置和云计算系统 | |
CN109104467B (zh) | 开发环境构建方法、装置以及平台系统和存储介质 | |
CN108376100B (zh) | 基于安全的容器调度 | |
US9307019B2 (en) | Apparatus, systems and methods for deployment and management of distributed computing systems and applications | |
CN102576354B (zh) | 支持不同部署架构的可扩展框架 | |
JP5598762B2 (ja) | 仮想マシンパッケージ生成システム、仮想マシンパッケージ生成方法および仮想マシンパッケージ生成プログラム | |
CN111641515B (zh) | Vnf的生命周期管理方法及装置 | |
WO2017049828A1 (zh) | 基于Linux的数据处理方法、装置和系统 | |
CN110741350A (zh) | 用于分布式计算系统的备份和还原架构 | |
US11086662B2 (en) | Method and system of migrating applications to a cloud-computing environment | |
US10983908B1 (en) | Method and system for garbage collection of data protection virtual machines in cloud computing networks | |
CN103064742A (zh) | 一种hadoop集群的自动部署系统及方法 | |
CN103248696B (zh) | 一种云计算环境下的虚拟资源动态配置方法 | |
WO2022151776A1 (zh) | 一种云平台虚拟机回收方法及计算机设备 | |
JP2008293358A (ja) | 分散処理プログラム、分散処理方法、分散処理装置、および分散処理システム | |
CN111262908A (zh) | 基于jenkins的任务构建方法及系统 | |
CN103414712A (zh) | 一种分布式虚拟桌面管理系统和方法 | |
CN107707687A (zh) | 一种虚拟机ip地址配置的方法和装置 | |
WO2021013248A1 (zh) | 容器分层部署方法及系统 | |
JP2010250749A (ja) | パッチ適用システム | |
CN107465709B (zh) | 分布式镜像构建任务方法及装置、系统 | |
CN112463290A (zh) | 动态调整计算容器的数量的方法、系统、装置和存储介质 | |
WO2020015751A1 (zh) | 容器服务快照的管理方法和装置 | |
JP2012208752A (ja) | ライセンス管理装置、ライセンス管理方法、及びプログラム | |
US11797206B2 (en) | Hash migration using a gold image library management 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: 20897260 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022534290 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202237038494 Country of ref document: IN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2020897260 Country of ref document: EP Effective date: 20220705 |