WO2022127420A1 - 业务编排部署方法、系统、网络设备和存储介质 - Google Patents

业务编排部署方法、系统、网络设备和存储介质 Download PDF

Info

Publication number
WO2022127420A1
WO2022127420A1 PCT/CN2021/128504 CN2021128504W WO2022127420A1 WO 2022127420 A1 WO2022127420 A1 WO 2022127420A1 CN 2021128504 W CN2021128504 W CN 2021128504W WO 2022127420 A1 WO2022127420 A1 WO 2022127420A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
deployment
services
container
deployed
Prior art date
Application number
PCT/CN2021/128504
Other languages
English (en)
French (fr)
Inventor
丁杰
张耀光
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022127420A1 publication Critical patent/WO2022127420A1/zh

Links

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/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
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • 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/445—Program loading or initiating
    • 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/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • 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
    • 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
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • 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
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the embodiments of the present application relate to the field of container technologies, and in particular, to a service orchestration and deployment method, system, network device, and storage medium.
  • Docker is an open source application container engine. At present, many users use the Docker system for manual deployment of services.
  • An embodiment of the present application provides a method for orchestrating and deploying services, including: acquiring basic environment information of a server to be deployed; when the basic environment information of the server to be deployed meets user requirements, acquiring and parsing a service configuration file, and performing user services Hierarchical processing, wherein the user business includes at least two services, the service includes at least one microservice, and a dependency relationship exists between the microservices; according to the dependency relationship, an image dependency tree and a container dependency tree are generated; According to the dependency relationship, image construction and container deployment are performed on all nodes of each layer of the image dependency tree and the container dependency tree; all containers are started to complete the orchestration and deployment of the user service.
  • the embodiment of the present application further provides a service orchestration and deployment system, including: a configuration file processing module, configured to obtain basic environment information of a server to be deployed; determine whether the server to be deployed meets user requirements; obtain and parse a service configuration file, Perform hierarchical processing on user services, wherein the user services include at least two services, the services include at least one microservice, and a dependency relationship exists between the microservices; a dependency tree generation module is used to generate a module according to the dependency relationship, generate an image dependency tree and a container dependency tree; an image building module is used to build images of all nodes in each layer of the image dependency tree according to the dependency relationship; a container deployment module is used to build an image according to the dependency relationship , perform container deployment on all nodes of each layer of the container dependency tree, start all containers, and complete the orchestration and deployment of the user service.
  • a configuration file processing module configured to obtain basic environment information of a server to be deployed; determine whether the server to be deployed meets user requirements; obtain and parse a service configuration file
  • An embodiment of the present application further provides a network device, the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores data that can be processed by the at least one processor The instructions are executed by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the service orchestration deployment method described above.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the above-mentioned service orchestration and deployment method is used.
  • FIG. 1 is a flowchart of a service orchestration and deployment method provided by the first embodiment of the present application
  • FIG. 2 is a flowchart of a service orchestration and deployment method provided by a second embodiment of the present application
  • FIG. 3 is a flowchart of a service orchestration and deployment method provided by a third embodiment of the present application.
  • FIG. 4 is a flowchart of a service orchestration and deployment method provided by a fourth embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a service orchestration and deployment system provided by a fifth embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a service orchestration and deployment system provided by a sixth embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device provided by a seventh embodiment of the present application.
  • the main purpose of the embodiments of this application is to propose a service orchestration and deployment method, system, network device, and storage medium, which greatly reduces the difficulty and complexity of service deployment, so that users can focus on service container transformation and deployment strategies.
  • the first embodiment of the present application relates to a service orchestration and deployment method, as shown in FIG. 1 , which specifically includes:
  • Step 101 Obtain basic environment information of the server to be deployed.
  • the service orchestration method of the embodiment of the present application is based on the Docker system, and Docker is an open source application container engine.
  • the basic environment information in this step may include: relevant parameters of the Docker system, firewall module information, network interface configuration information, disk space information, various startup items, and the like.
  • relevant parameters of the Docker system may include: relevant parameters of the Docker system, firewall module information, network interface configuration information, disk space information, various startup items, and the like.
  • the basic environment information can be obtained according to user requirements or actual service deployment requirements, and details are not repeated here.
  • the application does not limit the number of servers to be deployed, and one server may be deployed, or multiple servers may be deployed.
  • Step 102 when the basic environment information of the to-be-deployed server meets user requirements, obtain a service configuration file and parse it, and perform hierarchical processing on the user service, wherein the user service includes at least two services, and the service includes at least one microservice, There are dependencies between microservices.
  • the business configuration file can be customized according to the user's business deployment requirements.
  • the business configuration file can include: the dependencies between services, the size of each container, the target path of each container, and the log storage path of each service. , the IP address of each container, etc.
  • the service configuration file may also contain other service configuration information in actual application.
  • by flexibly configuring the container network through the service configuration file it is possible to form an advanced usage form in which a single container uses multiple network cards to form multiple service planes and uses different types of network infrastructure. It effectively meets the deployment needs of many different types of businesses.
  • the user can customize the volume (a logical storage unit) size and target path required by the service container, so as to realize automatic allocation, management and mapping of source paths on the virtual disk , while ensuring high availability of data.
  • volume a logical storage unit
  • the layered processing of user services may be to divide user services into four layers: network basic services, middleware services, framework services, and business services.
  • network basic services middleware services
  • framework services framework services
  • business services For each layer of services, the actual Business development needs to be divided into many finer microservices.
  • the specific business division method or rule is not limited here, and can be divided according to business functions and business types, or a user-defined division method.
  • Step 103 Generate an image dependency tree and a container dependency tree according to the dependency.
  • high-level services basically depend on low-level services, and multiple high-level services may depend on multiple low-level service components at the same time.
  • This dependency can be understood as the completion of one service must be completed on the basis of the completion of one or more other services.
  • Step 104 Perform image construction and container deployment on all nodes in each layer of the image dependency tree and the container dependency tree according to the dependency.
  • each layer of the dependency tree is deployed and checked in a concurrent manner, such as image construction, container construction, business initialization and startup, and waiting for the business status to be normal.
  • the work at this level is completed, and the deployment, installation and configuration of the next layer begins.
  • the process for each layer is the same until all the containers of all layers are deployed.
  • the network interworking and IP address allocation of all containers in this application are completely completed by a combination of service configuration file specification and automatic allocation by the orchestration system.
  • Step 105 Start all containers to complete the orchestration and deployment of user services.
  • the network communication between all the containers or the network communication between the container and the server host can be combined by setting up a dedicated bridge (a software bridge built in linux) and using the docker host network.
  • ipv4ip_forward (ip layer three forwarding) function, netfilter and iptables (linux built-in firewall module and control system) perform NAT (network address translation) to meet the needs of pure container layer network communication and container and server host network communication, so that users do not need to pay attention
  • NAT network address translation
  • the user's business is processed in layers and divided into various micro-services, and a dependency tree is generated according to the dependencies between the micro-services, and image construction and service container deployment are performed, so that the user does not It is necessary to care about complex basic service deployment, network parameter configuration and other processes, which greatly reduces the difficulty and complexity of business deployment.
  • the second embodiment of the present application relates to a service orchestration and deployment method.
  • This embodiment is substantially the same as the first embodiment, except that, as shown in FIG. 3 , before step 102 , the method further includes:
  • Step 201 judging whether the basic environment information of the server to be deployed meets user requirements.
  • Step 202 if the basic environment information of the server to be deployed does not meet user requirements, check the basic environment of the server to be deployed, and perform system installation and configuration according to the system configuration file.
  • the system configuration file in step 201 is the system configuration file pre-edited by the user. If there is one server to be deployed, the user pre-edits the single-machine system configuration file. If there are two servers to be deployed, the user Prepare the dual system configuration file in advance.
  • the system needs to be installed and configured according to the system configuration file, such as: docker system parameters, firewall module in Linux system, network interface configuration, startup Items, etc., are modified and reconfigured according to user needs.
  • system configuration file such as: docker system parameters, firewall module in Linux system, network interface configuration, startup Items, etc.
  • the system installation and related parameter configuration of the server can be performed according to the user-defined system configuration file. , which provides a business deployment method with customizable policies, which greatly satisfies the user's personalized deployment needs.
  • step 103 includes:
  • Step 301 traverse the contents of dependencies in the business configuration file, where the contents of dependencies are dependencies between microservices.
  • the content of the dependency in the business configuration file is the service name of the service that this service depends on.
  • the content is B, that is, the service name of the dependent service.
  • Step 302 generating an image dependency tree and a container dependency tree through a recursive backtracking algorithm.
  • the generated image dependency tree needs to be satisfied, and the component that is not depended on by any other image is used as the root node; while the container dependency tree needs to be satisfied, and the component that is not depended on by any other container is used as the root node.
  • the number of deployment threads is determined by these root nodes, and each tree is deployed in reverse from the leaf node to the parent node by subsequent traversal.
  • each service layer performs dependency calculations with less correlation, which greatly reduces the complexity of the generation and calculation of the dependency tree, and improves the Business deployment efficiency.
  • the fourth embodiment of the present application uses the service orchestration and deployment method to be applied in the case of dual servers, as follows: example to illustrate.
  • the service orchestration and deployment method provided by the fourth embodiment of the present application includes:
  • Step 401 Obtain basic environment information of two servers to be deployed.
  • Step 402 according to the basic environment information of the main server, determine whether the main server to be deployed meets the user requirements.
  • step 403 is performed, and if the main server meets the user requirements, step 404 is performed.
  • Step 403 check the basic environment of the primary server, and perform system installation and configuration according to the primary server system configuration file.
  • step 411 is performed.
  • Step 404 according to the basic environment information of the standby server, determine whether the standby server to be deployed meets user requirements.
  • step 405 is performed, and if the standby server meets the user's requirements, step 406 is performed.
  • Step 405 check the basic environment of the standby server, and perform system installation and configuration according to the system configuration file of the standby server.
  • step 411 is performed.
  • Step 406 perform dual-system component installation and configuration on the primary server and the secondary server.
  • dual-machine components may include: disk configuration, heartbeat network, synchronization network, etc., which are only described here as specific examples.
  • other components and configurations can also be installed according to user needs.
  • Step 407 Obtain and parse the service configuration file, and perform hierarchical processing on the user service, wherein the user service includes at least two services, the service includes at least one microservice, and there is a dependency relationship between the microservices.
  • Step 408 generate an image dependency tree and a container dependency tree according to the dependency.
  • step 412 is performed.
  • Step 409 Perform image construction and container deployment on all nodes in each layer of the image dependency tree and the container dependency tree according to the dependencies.
  • step 412 is performed.
  • Step 410 Start all containers to complete the orchestration and deployment of user services.
  • Step 411 clearing the system and configuration information, and generating a failure log.
  • step 412 the configuration information, images and containers in the two servers are cleaned up, and a failure log is generated.
  • the dual-server system can use the disk real-time replication technology to replicate the disk block devices on the Linux system in real time, ensuring that any data changes on the synchronized disks on the current host are replicated to The corresponding disk of the standby machine. Set up virtual disks on actual block devices. When upper-layer services use disks, they do not need to care about the actual disk devices used by the bottom layer. Decoupling services and disk devices to achieve greater hardware compatibility and reduce the intrusiveness of upper-layer coding .
  • the user's business is processed in layers and divided into various micro-services, and a dependency tree is generated according to the dependencies between the micro-services, and image construction and service container deployment are performed, so that the user does not It is necessary to care about complex basic service deployment, network parameter configuration and other processes, which greatly reduces the difficulty and complexity of business deployment.
  • the fifth embodiment of the present application relates to a service orchestration and deployment system, as shown in FIG. 5 , including:
  • the configuration file processing module 501 is used to obtain basic environmental information of the server to be deployed; determine whether the server to be deployed meets user requirements; obtain and parse a service configuration file, and perform hierarchical processing on user services, wherein the user services are at least Includes two services;
  • a dependency tree generation module 502 configured to generate an image dependency tree and a container dependency tree according to the dependencies between the services
  • an image construction module 503, configured to perform image construction on each layer of the image dependency tree according to the dependency;
  • the container deployment module 504 is configured to deploy service containers for each layer of the container dependency tree according to the dependencies, and start all service containers.
  • the service orchestration and deployment system further includes:
  • the monitoring module 505 is configured to monitor the running status of all services in the to-be-deployed server.
  • the monitoring module 505 sets a series of monitoring indicators, including: failure of key services, number of common multiple service failures, network unreachability, network quality, etc.
  • failure of key services including: failure of key services, number of common multiple service failures, network unreachability, network quality, etc.
  • number of common multiple service failures including: failure of key services, number of common multiple service failures, network unreachability, network quality, etc.
  • this embodiment is a device embodiment corresponding to the first embodiment, and this embodiment can be implemented in cooperation with the first embodiment.
  • the related technical details mentioned in the first embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition.
  • the relevant technical details mentioned in this embodiment can also be applied in the first embodiment.
  • the business orchestration and deployment system is mainly for the orchestration and deployment of microservices in small and micro scenarios. Different from the traditional manual deployment of a large number of containers on the docker system, this system greatly reduces the difficulty of business orchestration and deployment and complexity. In addition, compared with the kubernetes system (k8s system), this system saves a lot of cluster physical resources, so that small and micro scenarios can avoid huge cluster infrastructure costs to reuse the basic capabilities of large-scale distributed microservice frameworks.
  • k8s system k8s system
  • each module involved in this embodiment is a logical module.
  • a logical unit may be a physical unit, a part of a physical unit, or multiple physical units.
  • a composite implementation of the unit in order to highlight the innovative part of the present invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other units in this embodiment.
  • the sixth embodiment of the present application relates to a network device, as shown in FIG. 7 , comprising: at least one processor 701 ; and a memory 702 communicatively connected to the at least one processor 701 ; wherein the memory 702 stores data that can be accessed by at least one Instructions executed by one processor 701, the instructions are executed by at least one processor 701, so that at least one processor 701 can execute the service orchestration and deployment method described in any of the above method embodiments.
  • the memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory.
  • the bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein.
  • the bus interface provides the interface between the bus and the transceiver.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium.
  • the data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor.
  • the processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data used by the processor in performing operations.
  • the seventh embodiment of the present invention relates to a computer-readable storage medium storing a computer program.
  • the above method embodiments are implemented when the computer program is executed by the processor.
  • a storage medium includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, Read-Only Memory (ROM for short), Random Access Memory (RAM for short), magnetic disk or optical disk, etc. medium of program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例涉及容器技术领域，提出了一种业务编排部署方法、系统、网络设备和存储介质。该方法包括：获取待部署服务器的基本环境信息；当所述待部署服务器的基本环境信息符合用户需求时，获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务，所述服务至少包括一个微服务，所述微服务之间存在依赖关系；根据所述依赖关系，生成镜像依赖树和容器依赖树；根据所述依赖关系，对所述镜像依赖树和所述容器依赖树的每一层的所有节点进行镜像构建和容器部署；启动所有容器，完成所述用户业务的编排部署。

Description

业务编排部署方法、系统、网络设备和存储介质
相关申请的交叉引用
本申请基于申请号为“202011507151.8”、申请日为2020年12月18日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请的实施例涉及容器技术领域，特别涉及一种业务编排部署方法、系统、网络设备和存储介质。
背景技术
Docker是一个开源的应用容器引擎，目前，许多用户采用Docker系统进行业务的手工部署。
然而，采用Docker系统手工部署业务，用户需要关心基础服务部署，网络打通，网络配置参数，服务注册与发现的流程等等，难度大复杂度高，使得用户无法专注于业务容器的改造和部署策略。
发明内容
本申请实施例提供了一种业务编排部署方法，包括：获取待部署服务器的基本环境信息；当所述待部署服务器的基本环境信息符合用户需求时，获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务，所述服务至少包括一个微服务，所述微服务之间存在依赖关系；根据所述依赖关系，生成镜像依赖树和容器依赖树；根据所述依赖关系，对所述镜像依赖树和所述容器依赖树的每一层的所有节点进行镜像构建和容器部署；启动所有容器，完成所述用户业务的编排部署。
本申请实施例还提供了一种业务编排部署系统，包括：配置文件处理模块，用于获取待部署服务器的基本环境信息；判断所述待部署服务器是否符合用户需求；获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务，所述服务至少包括一个微服务，所述微服务之间存在依赖关系；依赖树生成模块，用于根据所述依赖关系，生成镜像依赖树和容器依赖树；镜像构建模块，用于根据所述依赖关系，对所述镜像依赖树每一层的所有节点进行镜像构建；容器部署模块，用于根据所述依赖关系，对所述容器依赖树的每一层的所有节点进行容器部署，启动所有容器，完成所述用户业务的编排部署。
本申请实施例还提供了一种网络设备，所述设备包括：至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行以上所述的业务编排部署方法。
本申请实施例还提供了一种计算机可读存储介质，存储有计算机程序，所述计算机程序 被处理器执行时上述的业务编排部署方法。
附图说明
图1是本申请第一实施例提供的业务编排部署方法的流程图；
图2是本申请第二实施例提供的业务编排部署方法的流程图；
图3是本申请第三实施例提供的业务编排部署方法的流程图；
图4是本申请第四实施例提供的业务编排部署方法的流程图；
图5是本申请第五实施例提供的业务编排部署系统的结构示意图；
图6是本申请第六实施例提供的业务编排部署系统的结构示意图；
图7是本申请第七实施例提供的网络设备的结构示意图。
具体实施方式
本申请实施例的主要目的在于提出一种业务编排部署方法、系统、网络设备和存储介质，大大降低了业务部署的难度与复杂度，使得用户可以专注于业务容器的改造和部署策略。
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请的第一实施例涉及一种业务编排部署方法，如图1所示，具体包括：
步骤101，获取待部署服务器的基本环境信息。
具体地说，本申请实施例的业务编排方法基于Docker系统，Docker是一个开源的应用容器引擎。另外，本步骤中的基本环境信息可以包括：Docker系统的相关参数、防火墙模块信息、网络接口配置信息、磁盘空间信息和各种启动项等。当然，此处仅为具体的举例说明，实际使用时，基本环境信息可以根据用户需求或实际业务部署需求进行获取，此处不做一一赘述。另外，本申请对待部署的服务器数量不做限定，可以部署一个服务器，也可以部署多个服务器。
步骤102，当所述待部署服务器的基本环境信息符合用户需求时，获取业务配置文件并解析，将用户业务进行分层处理，其中，用户业务至少包括两个服务，服务至少包括一个微服务，微服务之间存在依赖关系。
具体地说，业务配置文件可以根据用户业务部署需求进行自定义配置，业务配置文件中可以包括：各服务之间的依赖关系、各容器的大小、各容器的目标路径和各服务的日志存放路径、各容器的IP地址等等，当然，此处仅为具体的举例说明，实际应用时业务配置文件还可以包含其他业务配置信息。另外，通过业务配置文件灵活配置容器网络，可以形成单容器使用多网卡组成多业务平面使用不同类型的网络基础设施的高级使用形式。有效满足了多种不同类型业务的部署需求。
在一个实施例中，通过业务配置文件，用户可以自定义业务容器所需的volume(一种逻辑存储单元)大小和目标路径，以此实现自动在虚拟磁盘上进行源路径的分配、管理和映射， 同时保证数据的高可用。
在一个实施例中，将用户业务进行分层处理，可以是将用户业务划分成网络基础服务、中间件服务、框架类服务和业务服务四个层，当然，对于每一层服务还可以根据实际业务开展需要划分为许多更细的微服务。关于具体的业务划分方法或规则，此处不做限定，可以根据业务功能、业务类型进行划分，也可以用户自定义划分方法。
步骤103，根据依赖关系，生成镜像依赖树和容器依赖树。
具体地说，服务之间的依赖关系，高层的服务基本都会对低层服务发生依赖，且多个高层服务可能同时依赖多个低层服务组件。这种依赖关系可以理解为，一种服务的完成必须在其他一个或多个服务完成的基础上才能进行。
步骤104，根据依赖关系，对镜像依赖树和容器依赖树的每一层的所有节点进行镜像构建和容器部署。
具体地说，对依赖树的每一层使用并发的方式进行镜像构建、容器构建、业务初始化启动、等待业务状态正常等部署和检查工作，本层次工作完成，开始下一层的部署安装配置，每个层次的流程相同，直到所有层的容器全部部署完成。
在一个实施例中，本申请所有容器的网络互通和IP地址的分配完全由业务配置文件指定和编排系统自动分配相结合的方式来完成。
步骤105，启动所有容器，完成用户业务的编排部署。
在本实施例中，所有容器之间进行网络通信或者容器与服务器主机进行网络通信可以通过设立专属bridge(一种linux内置的软件桥接方式)和使用docker主机网络2种方式结合，利用linux系统的ipv4ip_forward(ip三层转发)功能、netfilter和iptables(linux内置的防火墙模块和控制系统)进行NAT(网络地址转换)满足单纯的容器层网络通信和容器与服务器主机网络通信的需求，使得用户无需关注底层复杂的基础服务部署、网络打通、服务注册与发现的流程等，专注于业务容器本身的改造和部署策略。
本实施例，通过获取用户的业务配置文件，将用户业务进行分层处理，划分为各个微服务，根据微服务之间的依赖关系，生成依赖树，进行镜像构建和服务容器部署，使得用户不需要关心复杂的基础服务部署，网络参数配置等过程，大大降低了业务部署的难度和复杂度。
本申请的第二实施例涉及一种业务编排部署方法，本实施例与第一实施例大致相同，区别在于，如图3所示，步骤102之前，还包括：
步骤201，判断待部署服务器的基本环境信息是否符合用户需求。
步骤202，若待部署服务器的基本环境信息不符合用户需求，则对待部署服务器进行基本环境的检查，并根据系统配置文件进行系统安装和配置。
具体地说，步骤201中的系统配置文件为用户预先编辑好的系统配置文件，若待部署的服务器为一个，则用户预先编辑好单机系统配置文件，若待部署的服务器为两个，则用户预先好双机系统配置文件。
在一个实施例中，若待部署服务器的基本环境不满足用户需求，则需要根据系统配置文件对系统进行安装和配置，比如：对docker系统参数、Linux系统中的防火墙模块、网络接口配置、启动项等根据用户需求进行修改重新配置。
本实施例，在实现第一实施例有益效果的基础上，还可以在待部署服务器的基本环境信息不符合用户需求时，根据用户自定义的系统配置文件，对服务器进行系统安装和相关参数 配置，提供了一种可自定义策略的业务部署方法，大大满足了用户个性化部署需求。
本申请的第三实施例涉及一种业务编排部署方法，本实施例与第一实施例大致相同，区别在于，如图3所示，步骤103包括：
步骤301，遍历业务配置文件中依赖项的内容，其中，依赖项内容为微服务之间的依赖关系。
具体地说，业务配置文件中依赖项的内容为本服务所依赖服务的服务名称。比如：A服务依赖于B服务，那么对于业务配置文件中A服务的依赖项，其内容为B，即所依赖服务的服务名称。当然，此处仅为具体的举例说明，实际使用过程中，业务配置文件中依赖项的表示方法还可以使用其他表示。此处不做赘述。
步骤302，通过递归回溯算法生成镜像依赖树和容器依赖树。
具体地说，生成的镜像依赖树需要满足，不被任何其他镜像依赖的组件作为根节点；而容器依赖树需要满足，不被任何其他容器依赖的组件作为根节点。另外，在进行容器部署时，由这些根节点决定部署线程的数量，以后续遍历的方式将每颗树从叶子节点开始往父节点反向部署。
在本实施例中，若生成镜像依赖树和容器依赖树失败，则表示业务编排部署失败，需要清理系统和配置信息，生成失败日志。
本实施例，在实现第一实施例有益效果的基础上，基于业务分层处理后，每个服务层内部进行相关性较小的依赖计算，大大降低了依赖树生成计算的复杂性，提高了业务部署效率。
为了使本领域技术人员能够更清楚地理解以上本申请第一至第三实施例公开的业务编排部署方法整体流程，本申请的第四实施例以业务编排部署方法应用在双服务器情况下，为例进行说明。
如图4所示，本申请的第四实施例提供的业务编排部署方法，包括：
步骤401，获取待部署的两个服务器的基本环境信息。
步骤402，根据主服务器基本环境信息，判断待部署的主服务器是否符合用户需求。
具体地，若主服务器不符合用户需求，则执行步骤403，若主服务器符合用户需求，执行步骤404。
步骤403，对主服务器进行基本环境的检查，并根据主服务器系统配置文件进行系统安装和配置。
其中，若系统安装和配置失败，则执行步骤411。
步骤404，根据备服务器基本环境信息，判断待部署的备服务器是否符合用户需求。
具体地，若备服务器不符合用户需求，则执行步骤405，若备服务器符合用户需求，则执行步骤406。
步骤405，对备服务器进行基本环境的检查，并根据备服务器系统配置文件进行系统安装和配置。
其中，若系统安装和配置失败，则执行步骤411。
步骤406，对主服务器和备服务器进行双机组件安装和配置。
具体地，双机组件安装和配置可以包括：磁盘配置、心跳网络、同步网络等等，此处仅为具体的举例说明，当然还可以根据用户需要安装其他组件和配置。
步骤407，获取业务配置文件并解析，将用户业务进行分层处理，其中，用户业务至少 包括两个服务，服务至少包括一个微服务，微服务之间存在依赖关系。
步骤408，根据依赖关系，生成镜像依赖树和容器依赖树。
其中，若生成镜像依赖树和容器依赖树失败，则执行步骤412。
步骤409，根据依赖关系，对镜像依赖树和容器依赖树的每一层的所有节点进行镜像构建和容器部署。
其中，若镜像构建和容器部署失败，则执行步骤412。
步骤410，启动所有容器，完成用户业务的编排部署。
步骤411，清理系统和配置信息，生成失败日志。
步骤412，清理两个服务器中的配置信息、镜像和容器，生成失败日志。
在本实施例中，对于双服务器进行业务部署，双机系统可以使用磁盘实时复制技术，对linux系统上的磁盘块设备进行实时复制，确保当前主机上被同步的磁盘任意数据改动均被复制到备机的对应磁盘。在实际的块设备上设置虚拟磁盘，上层业务使用磁盘时无需关心底层实际使用的磁盘设备，对业务和磁盘设备进行解耦，以起到更大的硬件兼容性，同时降低上层编码的侵入性。
本实施例，通过获取用户的业务配置文件，将用户业务进行分层处理，划分为各个微服务，根据微服务之间的依赖关系，生成依赖树，进行镜像构建和服务容器部署，使得用户不需要关心复杂的基础服务部署，网络参数配置等过程，大大降低了业务部署的难度和复杂度。
此外，应当理解的是，上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请的第五实施例涉及一种业务编排部署系统，如图5所示，包括：
配置文件处理模块501，用于获取待部署服务器的基本环境信息；判断所述待部署服务器是否符合用户需求；获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务；
依赖树生成模块502，用于根据所述服务之间的依赖关系，生成镜像依赖树和容器依赖树；
镜像构建模块503，用于根据所述依赖关系，对所述镜像依赖树每一层进行镜像构建；
容器部署模块504，用于根据所述依赖关系，对所述容器依赖树的每一层进行服务容器部署，启动所有服务容器。
在一个实施例中，如图6所示，业务编排部署系统还包括：
监控模块505，用于监控所述待部署服务器中所有服务的运行状态。
需要说明的是，监控模块505在监控所有服务的运行状态时，设置了一系列监控指标，包括：关键服务发生故障、普通多个服务故障数量、网络不可达、网络质量等等，当然，以上仅为具体的监控指标举例，实际应用时用户可以自定义监控指标与监控方法。
不难发现，本实施例为与第一实施例相对应的装置实施例，本实施例可与第实施例互相配合实施。第一实施例中提到的相关技术细节在本实施例中依然有效，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在第一实施例中。
需要说明的是，本实施例提供的业务编排部署系统主要针对于小微场景的微服务进行编 排部署，区别于传统的在docker系统上手工部署大量容器，本系统大大降低了业务编排部署的难度与复杂度。另外，相较于kubernetes系统(k8s系统)而言，本系统节省了大量的集群物理资源，使得小微场景可以避开庞大的集群基础设施成本来复用大型分布式微服务框架的基础能力。
值得一提的是，本实施例中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本发明的创新部分，本实施例中并没有将与解决本发明所提出的技术问题关系不太密切的单元引入，但这并不表明本实施例中不存在其它的单元。
本申请的第六实施例涉及一种网络设备，如图7所示，包括：至少一个处理器701；以及，与至少一个处理器701通信连接的存储器702；其中，存储器702存储有可被至少一个处理器701执行的指令，指令被至少一个处理器701执行，以使至少一个处理器701能够执行上述任一方法实施例所描述的业务编排部署方法。
其中，存储器和处理器采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器和存储器的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传输给处理器。
处理器负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器可以被用于存储处理器在执行操作时所使用的数据。
本发明第七实施例涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称：ROM)、随机存取存储器(Random Access Memory，简称：RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施例是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (10)

  1. 一种业务编排部署方法，包括：
    获取待部署服务器的基本环境信息；
    当所述待部署服务器的基本环境信息符合用户需求时，获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务，所述服务至少包括一个微服务，所述微服务之间存在依赖关系；
    根据所述依赖关系，生成镜像依赖树和容器依赖树；
    根据所述依赖关系，对所述镜像依赖树和所述容器依赖树的每一层的所有节点进行镜像构建和容器部署；
    启动所有容器，完成所述用户业务的编排部署。
  2. 根据权利要求1所述的业务编排部署方法，其中，在所述当所述待部署服务器的基本环境信息符合用户需求时，获取业务配置文件并解析之前，还包括：
    判断所述待部署服务器的基本环境信息是否符合用户需求；
    若所述待部署服务器的基本环境信息不符合用户需求，则对所述待部署服务器进行基本环境的检查，并根据系统配置文件进行系统安装和配置。
  3. 根据权利要求1至2中任一项所述的业务编排部署方法，其中，所述将用户业务进行分层处理，包括：将所述用户业务分成网络基础服务、中间件服务、框架类服务和业务服务中的一种或多种。
  4. 根据权利要求1至3中任一项所述的业务编排部署方法，其中，所述根据所述依赖关系，生成镜像依赖树和容器依赖树，包括：
    遍历业务配置文件中依赖项的内容，其中，所述依赖项内容为微服务之间的依赖关系；
    通过递归回溯算法分别生成镜像依赖树和容器依赖树。
  5. 根据权利要求2所述的业务编排部署方法，其中，在所述根据系统配置文件进行系统安装和配置之后，还包括：当所述待部署服务器的数量为两个时，对两个待部署服务器进行双机组件安装和配置。
  6. 根据权利要求1至5中任一项所述的业务编排部署方法，其中，在所述对所述镜像依赖树和所述容器依赖树的每一层的所有节点进行镜像构建和容器部署之后，还包括：若所述镜像构建和所述容器部署任一操作失败，则清理所述待部署服务器中的配置信息、镜像和容器，生成失败日志。
  7. 一种业务编排部署系统，包括：
    配置文件处理模块，用于获取待部署服务器的基本环境信息；判断所述待部署服务器是否符合用户需求；获取业务配置文件并解析，将用户业务进行分层处理，其中，所述用户业务至少包括两个服务，所述服务至少包括一个微服务，所述微服务之间存在依赖关系；
    依赖树生成模块，用于根据所述依赖关系，生成镜像依赖树和容器依赖树；
    镜像构建模块，用于根据所述依赖关系，对所述镜像依赖树每一层的所有节点进行镜像 构建；
    容器部署模块，用于根据所述依赖关系，对所述容器依赖树的每一层的所有节点进行容器部署，启动所有容器，完成所述用户业务的编排部署。
  8. 根据权利要求7所述的业务编排部署系统，其中，所述系统还包括：
    监控模块，用于监控所述待部署服务器中所有服务的运行状态。
  9. 一种网络设备，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至6中任意一项所述业务编排部署方法。
  10. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至6中任一项所述的业务编排部署方法。
PCT/CN2021/128504 2020-12-18 2021-11-03 业务编排部署方法、系统、网络设备和存储介质 WO2022127420A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011507151.8 2020-12-18
CN202011507151.8A CN114721764A (zh) 2020-12-18 2020-12-18 业务编排部署方法、系统、网络设备和存储介质

Publications (1)

Publication Number Publication Date
WO2022127420A1 true WO2022127420A1 (zh) 2022-06-23

Family

ID=82058907

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/128504 WO2022127420A1 (zh) 2020-12-18 2021-11-03 业务编排部署方法、系统、网络设备和存储介质

Country Status (2)

Country Link
CN (1) CN114721764A (zh)
WO (1) WO2022127420A1 (zh)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114860350A (zh) * 2022-07-07 2022-08-05 杭州子默网络科技有限公司 基于云无盘树状镜像的数据处理的方法及装置
CN114880000A (zh) * 2022-07-05 2022-08-09 深圳市信润富联数字科技有限公司 工控机远程运维方法、装置、电子设备及存储介质
CN115016832A (zh) * 2022-08-08 2022-09-06 北京安普诺信息技术有限公司 一种深度分析软件组件依赖关系的方法及相关装置、平台
CN115514666A (zh) * 2022-09-26 2022-12-23 郑州小鸟信息科技有限公司 一种可视化部署的方法及系统
CN115543353A (zh) * 2022-09-19 2022-12-30 北京三维天地科技股份有限公司 一种基于分布式部署架构的系统管理解决方法及系统
CN115562690A (zh) * 2022-12-05 2023-01-03 杭州未名信科科技有限公司 基于Docker容器的算法服务处理方法、装置及介质
CN116016227A (zh) * 2022-12-29 2023-04-25 浪潮通用软件有限公司 基于Docker Compose的微服务系统编排可视化方法、设备及介质
CN116208497A (zh) * 2023-05-05 2023-06-02 广东省新一代通信与网络创新研究院 一种可编程网络系统、方法、交换机及装置
CN116225464A (zh) * 2023-05-09 2023-06-06 霖济智云科技(苏州)有限公司 一种平台的快速部署方法
CN116431277A (zh) * 2023-03-13 2023-07-14 浙江海规技术有限公司 多地运维容器化方法、装置、计算机设备及存储介质
CN116700902A (zh) * 2023-06-25 2023-09-05 天津大学 一种镜像层异步并行提取的容器加速部署方法及装置
CN117055880A (zh) * 2023-08-22 2023-11-14 广东保伦电子股份有限公司 一种基于容器化部署的文档转码方法、装置及存储介质
CN117289951A (zh) * 2023-11-22 2023-12-26 华信咨询设计研究院有限公司 一种基于递归原则的软件系统多应用自动部署方法
CN117834205A (zh) * 2023-12-13 2024-04-05 长江信达软件技术（武汉）有限责任公司 一种docker容器防火墙配置方法及系统
CN118227293A (zh) * 2024-04-02 2024-06-21 三峡高科信息技术有限责任公司 一种基于业务领域组件快速构建文件类应用的方法及系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115220874B (zh) * 2022-09-05 2023-01-06 税友信息技术有限公司 一种Kubernetes集群部署方法、装置、设备及存储介质
CN116136756A (zh) * 2023-04-18 2023-05-19 浪潮通用软件有限公司 一种基于分层结构的微服务组装方法、装置、设备及介质
CN117234489B (zh) * 2023-11-14 2024-03-15 云筑信息科技(成都)有限公司 一种基于业务流程实现动态模块编排的方法
CN117785224A (zh) * 2023-12-12 2024-03-29 暗物质(北京)智能科技有限公司 模型部署方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131193A1 (en) * 2010-11-23 2012-05-24 Red Hat Inc. Systems and methods for identifying service dependencies in a cloud deployment
US20140372533A1 (en) * 2011-02-09 2014-12-18 Cliqr Technologies, Inc. Apparatus, systems, and methods for cloud agnostic multi-tier application modeling and deployment
CN105867955A (zh) * 2015-09-18 2016-08-17 乐视云计算有限公司 一种应用程序部署系统及部署方法
CN108595180A (zh) * 2018-03-14 2018-09-28 广东能龙教育股份有限公司 一种基于依赖链的微服务自动部署方法
CN108762769A (zh) * 2018-06-04 2018-11-06 万惠投资管理有限公司 微服务应用编排和部署方法、装置及计算机终端
CN111367534A (zh) * 2020-03-19 2020-07-03 远光软件股份有限公司 一种基于应用环境的服务编排方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205616A1 (en) * 2017-01-18 2018-07-19 International Business Machines Corporation Intelligent orchestration and flexible scale using containers for application deployment and elastic service

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131193A1 (en) * 2010-11-23 2012-05-24 Red Hat Inc. Systems and methods for identifying service dependencies in a cloud deployment
US20140372533A1 (en) * 2011-02-09 2014-12-18 Cliqr Technologies, Inc. Apparatus, systems, and methods for cloud agnostic multi-tier application modeling and deployment
CN105867955A (zh) * 2015-09-18 2016-08-17 乐视云计算有限公司 一种应用程序部署系统及部署方法
CN108595180A (zh) * 2018-03-14 2018-09-28 广东能龙教育股份有限公司 一种基于依赖链的微服务自动部署方法
CN108762769A (zh) * 2018-06-04 2018-11-06 万惠投资管理有限公司 微服务应用编排和部署方法、装置及计算机终端
CN111367534A (zh) * 2020-03-19 2020-07-03 远光软件股份有限公司 一种基于应用环境的服务编排方法及系统

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114880000A (zh) * 2022-07-05 2022-08-09 深圳市信润富联数字科技有限公司 工控机远程运维方法、装置、电子设备及存储介质
CN114860350A (zh) * 2022-07-07 2022-08-05 杭州子默网络科技有限公司 基于云无盘树状镜像的数据处理的方法及装置
CN115016832A (zh) * 2022-08-08 2022-09-06 北京安普诺信息技术有限公司 一种深度分析软件组件依赖关系的方法及相关装置、平台
CN115016832B (zh) * 2022-08-08 2022-11-29 北京安普诺信息技术有限公司 一种深度分析软件组件依赖关系的方法及相关装置、平台
CN115543353A (zh) * 2022-09-19 2022-12-30 北京三维天地科技股份有限公司 一种基于分布式部署架构的系统管理解决方法及系统
CN115514666A (zh) * 2022-09-26 2022-12-23 郑州小鸟信息科技有限公司 一种可视化部署的方法及系统
CN115562690A (zh) * 2022-12-05 2023-01-03 杭州未名信科科技有限公司 基于Docker容器的算法服务处理方法、装置及介质
CN116016227A (zh) * 2022-12-29 2023-04-25 浪潮通用软件有限公司 基于Docker Compose的微服务系统编排可视化方法、设备及介质
CN116431277A (zh) * 2023-03-13 2023-07-14 浙江海规技术有限公司 多地运维容器化方法、装置、计算机设备及存储介质
CN116208497A (zh) * 2023-05-05 2023-06-02 广东省新一代通信与网络创新研究院 一种可编程网络系统、方法、交换机及装置
CN116225464B (zh) * 2023-05-09 2023-07-11 霖济智云科技(苏州)有限公司 一种平台的快速部署方法
CN116225464A (zh) * 2023-05-09 2023-06-06 霖济智云科技(苏州)有限公司 一种平台的快速部署方法
CN116700902A (zh) * 2023-06-25 2023-09-05 天津大学 一种镜像层异步并行提取的容器加速部署方法及装置
CN116700902B (zh) * 2023-06-25 2024-03-12 天津大学 一种镜像层异步并行提取的容器加速部署方法及装置
CN117055880A (zh) * 2023-08-22 2023-11-14 广东保伦电子股份有限公司 一种基于容器化部署的文档转码方法、装置及存储介质
CN117055880B (zh) * 2023-08-22 2024-05-03 广东保伦电子股份有限公司 一种基于容器化部署的文档转码方法、装置及存储介质
CN117289951A (zh) * 2023-11-22 2023-12-26 华信咨询设计研究院有限公司 一种基于递归原则的软件系统多应用自动部署方法
CN117289951B (zh) * 2023-11-22 2024-04-02 华信咨询设计研究院有限公司 一种基于递归原则的软件系统多应用自动部署方法
CN117834205A (zh) * 2023-12-13 2024-04-05 长江信达软件技术（武汉）有限责任公司 一种docker容器防火墙配置方法及系统
CN118227293A (zh) * 2024-04-02 2024-06-21 三峡高科信息技术有限责任公司 一种基于业务领域组件快速构建文件类应用的方法及系统

Also Published As

Publication number Publication date
CN114721764A (zh) 2022-07-08

Similar Documents

Publication Publication Date Title
WO2022127420A1 (zh) 业务编排部署方法、系统、网络设备和存储介质
CN110474792B (zh) 网络配置方法、设备及系统
US7478361B2 (en) Method and system for managing application deployment
JP2021508997A (ja) ネットワーク・スライスの展開方法および装置
US10142180B2 (en) Method and system for providing unified configuration information to disparate system software components
CN111683074A (zh) 一种基于nfv的安全网络架构和网络安全管理方法
CN110719209B (zh) 一种集群网络配置方法、系统、设备及可读存储介质
CN102447585B (zh) 将网络配置协议响应报文转换为命令行的方法及装置
US9847903B2 (en) Method and apparatus for configuring a communication system
US10230567B2 (en) Management of a plurality of system control networks
CN102158498B (zh) 一种支持服务定制与扩展的网络节点结构实现方法
CN104956332A (zh) 主自动化服务
CN109462511B (zh) 网络的建立方法及装置
EP2815346A1 (en) Coordination of processes in cloud computing environments
CN107666493B (zh) 一种数据库配置方法及其设备
CN111970337B (zh) 跨云环境下的p2p网络通信构建方法、系统、介质及终端
CN112394947A (zh) 一种基于微服务架构的信息系统
WO2024130997A1 (zh) 一种节点配置方法、装置、设备、非易失性可读存储介质及服务器
WO2024088217A1 (zh) 私有网络的访问方法和系统
EP4109251A1 (en) Vnf instantiation method and device
Khalel et al. Enhanced load balancing in kubernetes cluster by minikube
US7885292B2 (en) Method, system, and computer program product for data exchange
CN113407306B (zh) 一种资源管理系统、方法、装置、设备及介质
CN109101367A (zh) 云计算系统中组件的管理方法和装置
CN112351114B (zh) 一种信息处理方法、装置以及存储介质

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: 21905349

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: 21905349

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 021123)

122 Ep: pct application non-entry in european phase

Ref document number: 21905349

Country of ref document: EP

Kind code of ref document: A1