WO2019184116A1 - Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur - Google Patents

Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur Download PDF

Info

Publication number
WO2019184116A1
WO2019184116A1 PCT/CN2018/093710 CN2018093710W WO2019184116A1 WO 2019184116 A1 WO2019184116 A1 WO 2019184116A1 CN 2018093710 W CN2018093710 W CN 2018093710W WO 2019184116 A1 WO2019184116 A1 WO 2019184116A1
Authority
WO
WIPO (PCT)
Prior art keywords
master node
component
kubernetes
management
configuration file
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/093710
Other languages
English (en)
Chinese (zh)
Inventor
邓志弘
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019184116A1 publication Critical patent/WO2019184116A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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 present application belongs to the field of data processing technologies, and in particular, to a method, an apparatus, a terminal device, and a computer readable storage medium for automatically setting up a Kubernetes master node.
  • a container can be understood as a sandbox.
  • One application runs inside each container, and different containers are isolated from each other, but a communication mechanism can be established between the containers.
  • Docker container technology allows several containers to run on the same host or virtual machine, each of which is a separate virtual environment or application.
  • Kubernetes is an open source container operation platform that can realize the functions of combining containers into one service and dynamically allocating the host running the container, which provides great convenience for users to use the container.
  • the Kubernetes cluster includes two types of nodes: the master node and the slave node.
  • the master node is responsible for the management and scheduling of all resources in the Kubernetes cluster. Therefore, to use Kubernetes, the master node needs to be built first.
  • the Kubernetes master node is manually built by the user, and the construction process relies on the Internet service, and the construction efficiency and applicability are low.
  • the embodiment of the present application provides a method, a device, a terminal device, and a computer readable storage medium for automatically setting up a Kubernetes master node, so as to solve the problem that the prior art needs to manually build a Kubernetes master node, and build efficiency and applicability. Low problem.
  • a first aspect of the embodiments of the present application provides a method for automatically setting up a Kubernetes master node, including:
  • a second aspect of the embodiments of the present application provides an apparatus for automatically setting up a Kubernetes master node, which may include a unit for implementing the steps of the above method of automatically setting up a Kubernetes master node.
  • a third aspect of the embodiments of the present application provides a terminal device, including a memory and a processor, where the computer stores computer readable instructions executable on the processor, the processor executing the computer
  • the steps of the above method of automatically setting up the Kubernetes master node are implemented when the instruction is read.
  • a fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being implemented by a processor to implement the above-mentioned automatic establishment of a Kubernetes master node The steps of the method.
  • the embodiment of the present application obtains a preset script file for setting up a Kubernetes master node, and executes a preset script file to generate a configuration file according to a creation parameter related to the Kubernetes master node input by the user, and finally starts the SaltStack.
  • the tool under the control of the SaltStack tool, automatically constructs the Kubernetes master node according to the configuration file, realizes the automatic establishment of the Kubernetes master node, and does not need to rely on the Internet service, thereby improving the building efficiency and the applicability to the construction environment.
  • FIG. 1 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node in the first embodiment of the present application
  • FIG. 2 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node in Embodiment 2 of the present application;
  • FIG. 3 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node in Embodiment 3 of the present application;
  • FIG. 4 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node in Embodiment 4 of the present application;
  • FIG. 5 is a flowchart of an implementation of a method for automatically setting a Kubernetes master node in Embodiment 5 of the present application;
  • FIG. 6 is a structural block diagram of an apparatus for automatically setting up a Kubernetes master node in Embodiment 6 of the present application;
  • FIG. 7 is a schematic diagram of a Kubernetes cluster in Embodiment 7 of the present application.
  • Embodiment 8 is a regional structure diagram based on a Kubernetes cluster in Embodiment 8 of the present application;
  • FIG. 9 is a schematic diagram of a terminal device in Embodiment 9 of the present application.
  • FIG. 1 is a flowchart of an implementation of a method for automatically setting a Kubernetes master node according to an embodiment of the present application. As shown in Figure 1, the method includes the following steps:
  • S101 Obtain a preset script file for setting up a Kubernetes master node.
  • the Kubernetes master node is mainly built by the SaltStack tool.
  • the preset script file for setting up the Kubernetes master node is obtained.
  • Kubernetes and Kubernetes master nodes are introduced.
  • Kubernetes is an open source platform for automated container operations. It enables the deployment, scheduling, and inter-cluster expansion of containers.
  • the physical server or virtual machine on which the Kubernetes platform is installed is called the Kubernetes node.
  • multiple Kubernetes nodes are required to be formed as Kubernetes clusters (Kubernetes) Cluster) to achieve the deployment and management of the container.
  • the Kubernetes master node (Kubernetes) Master
  • the Kubernetes master node (Kubernetes) Master
  • the components of the Kubernetes master node are described in detail later.
  • the Kubernetes cluster also includes multiple subordinate objects of the Kubernetes master node, namely the Kubernetes Node, which is used to actually run the container allocated by the Kubernetes master node.
  • the Kubernetes master node is mainly built by the script file, and the script file is a determined series of control computer operations. Combination, in which logical branches can be implemented, and script files can be written in Shell language or the like.
  • the user may be provided with a setup option for setting up a Kubernetes master node, and the setup option may be presented to the user in the form of a graphical interface or a command line, and the obtained confirmation result of the user is obtained.
  • the operation of acquiring the script file is performed.
  • the script file can be placed in the file server PackageServer after the pre-setting is completed.
  • the PackageServer is a high-speed download server, which can be used to place various binary files and script files, and the contents thereof are usually fixed, so it can be applied in this application.
  • the real-time and reliability of the script file acquisition is improved.
  • the Kubernetes platform is suitable for different operating systems, such as Windows, Linux, etc., and under different environments, the underlying build code has a certain degree of difference, so it can be written for multiple operating systems.
  • S102 execute the script file to generate a configuration file according to a creation parameter input by the user related to the Kubernetes master node.
  • the script file After obtaining the preset script file, the script file is executed, and the creation parameters related to the Kubernetes master node are obtained during the execution of the script file, and some of the creation parameters such as the version number of the Kubernetes master node are automatically acquired, and another part is automatically acquired.
  • Creating parameters such as log file paths, etc. requires detecting user input and looking up the contents of the log file path from the user's input.
  • the creation parameters related to the Kubernetes master node include the attribute parameters of the Kubernetes master node, such as the installation version, the Internet Protocol address of the Kubernetes master node, the host identifier (name) of the Kubernetes master node, and the area identifier, etc., and also constitute the Kubernetes master. Attribute parameters of each component of the node, etc.
  • the script file After the creation parameters entered by the user are obtained, the script file generates a configuration file according to the creation parameters.
  • the configuration file is written in script language. It is similar to the script file. For the convenience of description, the configuration file can be named as the deployment script. In the subsequent steps, the configuration file is executed to build the Kubernetes master node through the SaltStack tool.
  • an input template is generated according to each type of the creation parameter related to the Kubernetes master node, and a creation parameter input by the user through the input template is obtained. Since each type of the created parameter is determined, an input template can be generated according to the type of the created parameter, and the input template includes the names of the various types of the created parameters, so that the user can input the content corresponding to each type of name, and the error of creating the parameter input is reduced. may.
  • the input template can also be configured in the script file. When the creation parameters need to be obtained, the script file is executed, and the input template is automatically provided to the user.
  • S103 Start a SaltStack tool to build the Kubernetes master node according to the configuration file.
  • the Kubernetes master node is built by using the SaltStack tool.
  • the SaltStack tool is an open source infrastructure management tool, which is divided into two parts: the management master node (SaltMaster) and the management slave node (SaltMinion).
  • the management master node of the SaltStack tool mainly manages the management slave nodes, and the management slave nodes run on the physical servers or virtual machines that need to be managed, and execute the management master node transmission. Instructions, and build the main Kubernetes node according to the configuration file, the specific process will be explained later.
  • the script file can be stored in the file server PackageServer and obtain the creation related to the Kubernetes master node by acquiring a preset script file for setting up the Kubernetes master node. After executing the script file, generate the configuration file corresponding to the created parameter, and finally start the SaltStack tool. Specifically, through the management master node and the management slave node in the SaltStack tool, the Kubernetes master node is built according to the configuration file, and the Kubernetes master node is implemented. Automated construction reduces user operations and improves construction efficiency.
  • FIG. 2 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node according to Embodiment 2 of the present application.
  • the embodiment refines S103 to obtain S201 ⁇ S202, which are as follows:
  • S201 Configure a management master node and a plurality of management slave nodes under the SaltStack tool, wherein the management master node is connected to the plurality of management slave nodes.
  • the SaltStack tool applies a client/server architecture that enables remote command execution and configuration management.
  • the SaltStack tool includes a management master node and multiple management slave nodes.
  • the management master node is equivalent to the SaltStack tool server. It is responsible for resource management.
  • the multiple management slave nodes are equivalent to the SaltStack tool client, and are responsible for executing the instructions issued by the management master node. .
  • an area that provides a specific service for a user is referred to as an available area, and the inside of the available area is specifically divided into a resource management area and a public service area, wherein the resource management area is used to deploy a resource management related program and A component that can access a physical server or virtual machine in a public service area, which is equivalent to a server in a client/server architecture.
  • the management master node runs in the resource management area; the public service area is used to deploy a program or service that provides a specific service to the user. , equivalent to the client in the client/server architecture, so the management slave node is installed in the public service area.
  • the management master node and the plurality of management slave nodes are automatically configured.
  • the management slave node starts, the private key and the public key are generated according to the encryption algorithm, and after the generation is completed, the public key is sent to the management master node.
  • the management master node verifies and accepts the public key to establish a connection with the management slave node.
  • the management master node and the management slave node pass the message through the message queue ZeroMQ, that is, the management master node posts the message to the message queue ZeroMQ, and the management slave node obtains the message by subscribing to the message queue ZeroMQ.
  • S202 Call the management master node, so that one of the plurality of management slave nodes constructs the Kubernetes master node according to the configuration file.
  • the SaltStack tool calls the management master node, and the management master node selects one of the plurality of management slave nodes, and the selected management slave node receives the setup instructions, according to the configuration.
  • the file is built on the Kubernetes master node, which essentially builds the Kubernetes master node on the physical server or virtual machine where the management slave node is located.
  • the management master node and the plurality of management slave nodes are connected, and the communication is realized through the message queue ZeroMQ. And call the management master node, so that the management master node selects one of the plurality of management slave nodes, and builds the Kubernetes master node according to the configuration file under the selected management slave node, which embodies the specific process of setting up the Kubernetes master node through the SaltStack tool, and improves The stability of building the main Kubernetes node.
  • FIG. 3 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node according to Embodiment 3 of the present application.
  • S202 is refined to obtain S301 ⁇ S303, which are as follows:
  • the management master node searches for multiple management slave nodes connected thereto to find out whether there is a corresponding parameter corresponding to the creation parameter.
  • the main node of Kubernetes Since the creation parameters are related to the Kubernetes master node, after the SaltStack tool is started and the management master node and the plurality of management slave nodes are configured, the management master node searches for multiple management slave nodes connected thereto to find out whether there is a corresponding parameter corresponding to the creation parameter. The main node of Kubernetes.
  • S302 If the Kubernetes master node does not exist under the multiple management slave nodes, select a management slave node corresponding to the creation parameter from the multiple management slave nodes as a slave node.
  • the Kubernetes master node is built under the management slave node, so in step S102, the acquired creation parameters related to the Kubernetes master node also include the user-configured management slave node correlation. The parameters, then in this step, the corresponding management slave node can be selected from the plurality of management slave nodes according to the creation parameters, as a slave node.
  • one of the plurality of management slave nodes may be randomly selected as a slave node, or may be performed in multiple management slave nodes according to a preset selection mechanism. select.
  • the Kubernetes master node is built according to the configuration file under the setup slave node.
  • a flag can be set for the setup slave node
  • a flag stamp can be set for the setup slave node to prove that the setup slave node has been used to create a Kubernetes master node.
  • the flag stamp setting is completed, if the new Kubernetes master node is set again, then when the operation of step S301 is performed, that is, whether there is a Kubernetes master node under the plurality of management slave nodes, whether there is a mark stamp according to the management slave node To determine whether the management slave node has been used to create a Kubernetes master node, improving detection efficiency.
  • FIG. 4 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node according to Embodiment 4 of the present application.
  • the S103 is refined to obtain S401 ⁇ S402, which are as follows:
  • S401 Deploy the database component by using the SaltStack tool, and obtain network configuration data related to the creation parameter, and load the network configuration data to the database component.
  • the Kubernetes master node includes a database (Etcd) component, an interface service (Kube ApiServer) component, and a control (Kube).
  • the Controller Manager component and the Kube Scheduler component provide a schematic diagram of a Kubernetes cluster as shown in FIG. 7 for facilitating the explanation of the content of the embodiment of the present application.
  • the Master represents the Kubernetes master node
  • the Controller The Manager represents the control component
  • the Scheduler represents the scheduling component
  • the ApiServer represents the interface service component
  • the Etcd represents the database component
  • the lowest node represents the Kubernetes slave node.
  • the database component is a distributed key-value storage service that guarantees data consistency through a distributed Raft algorithm and provides Hypertext Transfer Protocol (HTTP) and JavaScript Object Notation (JSON). Application Programming Interface (API).
  • the database component is used for configuration management, data storage, and as a distributed lock, which can be deployed through the SaltStack tool, specifically, the management slave node is configured according to
  • the file configuration database component obtains the database component configuration file from the file server through the configuration file.
  • the database component configuration file is a binary file, which is used to configure the database component service, and the configuration content also includes the database name and the data path. After the database component is configured, obtain the network configuration data related to the creation parameters and load the network configuration data into the database component.
  • the network configuration data may be obtained by presetting a network configuration template in the script file, and extracting the content related to the network configuration data in the creation parameter when the parameter is created, and adding the content to the network configuration template, thereby Obtained directly from the network configuration template when network configuration data is required.
  • the database component can identify the node to be joined as a Kubernetes slave node according to the network configuration data.
  • S402 Deploy the interface service component, the control component, and the scheduling component in sequence, and modify a service address of the interface service component.
  • the interface service component is responsible for data interaction with the database component. It is worth mentioning that, in addition to the interface service component, other components of the Kubernetes master node do not directly manipulate the database component.
  • the interface service component is the data center of the Kubernetes master node, which manages the application programming interface of the Kubernetes cluster. It is mentioned in step S102 that the configuration file is essentially a script file written by the scripting language. Therefore, in this step, the interface service configuration file in the file server is automatically extracted according to the configuration file, and the interface service component is performed according to the interface service configuration file. Configuration.
  • the creation parameter input by the user includes the database component address and the interface service address
  • the configuration file is generated by the creation parameter, so in the step, the database component address and the interface service component address are also configured in the interface service component through the configuration file, wherein the database The component address is the address of the database service in the database component, and the database component address is configured in the interface service component to enable the interface service component to access the database component through the database component address; the interface service component address is the local address of the interface service component.
  • the interface service component includes two types of communication interfaces, one is used to provide an interface for Kubernetes slave nodes to access database components, and needs to be authenticated by a security certificate. The specific content is introduced later; It is an interface for data interaction with the scheduling component and the control component. This interface is the internal interface of the component and does not require permission authentication.
  • the control component is the management and control center of the Kubernetes cluster, ensuring that the status of various resources in the Kubernetes cluster is in a normal state.
  • the control component triggers the scheduling operation, and the control component includes the node controller. (Node Controller) and copy controller (Replication Controller).
  • the scheduling component is responsible for orchestrating the containers in the Kubernetes cluster, and is responsible for dispatching the containers to specific Kubernetes slave nodes.
  • the scheduling component listens to the container through the application programming interface provided by the interface service component, obtains the container to be scheduled, and sorts each Kubernetes slave node according to a preset sorting mechanism, and dispatches the container to the Kubernetes slave node of the first sort.
  • the control component configuration file and the scheduling component configuration file are obtained from the file server through the configuration file, and the control component configuration file and the scheduling component configuration file are all binary files, wherein the control component configuration file is used to configure the control component related services, and the component configuration is scheduled. Files are used to configure the scheduling component.
  • the configuration process also includes setting environment variables, including control component and version environment variables of the scheduling component.
  • the environment variables are determined by the creation parameters input by the user, and the environment variables are automatically configured in the control component and the scheduling component through the configuration file.
  • the service address of the interface service component is automatically modified according to the configuration file, so that the control component and the scheduling component can respectively perform data interaction with the interface service component, wherein the service address refers to an address that the interface service component provides the service to.
  • DNS Domain Name System
  • you can create the Domain Name System (DNS) service which is kube-dns, which is responsible for creating DNS services inside the Kubernetes cluster, so that the containers can be searched through the domain name. It is convenient to build services between containers.
  • a dashboard is created, and the dashboard is a user interface of the Kubernetes cluster, which is convenient for the user to view and operate the resources of the Kubernetes cluster through the dashboard.
  • the Kubernetes master node includes a database component, an interface service component, a control component, and a scheduling component, deploys a database component through the SaltStack tool, and acquires and creates parameters from the network configuration template.
  • Related network configuration data loading network configuration data into the database component, after the database component configuration is completed, sequentially deploying the interface service component, the control component, and the scheduling component, and modifying the service address of the interface service component, so as to facilitate the control component and the scheduling component
  • Data interaction with the interface service component alone reflects the deployment process of each component under the Kubernetes master node, which improves the automation of component configuration.
  • FIG. 5 is a flowchart of an implementation of a method for automatically setting up a Kubernetes master node according to Embodiment 5 of the present application.
  • S401 is refined to obtain S501 ⁇ S502, which are as follows:
  • S501 Generate a first security certificate and a second security certificate according to the configuration file, where the first security certificate is used to control access rights to the database component, and the second security certificate is used to control the interface service component. access permission.
  • the first security certificate and the second security certificate are automatically generated according to the configuration file, and the first security certificate and the first security certificate are
  • the second security certificate is the Secure Sockets Layer (Secure Socket Layer, SSL) certificate.
  • the first security certificate is used to control access rights to the database component
  • the second security certificate is used to control access rights to the interface service component.
  • S502 Configure the first security certificate to the database component and the interface service component, and configure the second security certificate to the interface service component.
  • the Kubernetes slave node and the interface service component need to be verified by the first security certificate before performing data interaction with the database component.
  • the second security certificate is configured into the interface service component. After the interface service component service is started, the Kubernetes slave node needs to be verified by the second security certificate before performing data interaction with the interface service component.
  • FIG. 5 shows that, in the embodiment of the present application, when the database component is deployed, the first security certificate and the second security certificate are generated, and the first security certificate is configured to the database component and the interface service component, and is used for Controls the access rights of Kubernetes from the node and interface service components to the database components, configures the second security certificate to the interface service component, controls the access rights of the Kubernetes slave node to the interface service component, and improves the access of the database component and the interface service component. safety.
  • the Kubernetes primary node and the Kubernetes cluster may be constructed based on a proprietary network.
  • a regional structure diagram based on the Kubernetes cluster is provided.
  • the user-specific network Virtual Private Cloud (VPC) is a user-created custom private network. Different private networks are logically isolated. Users can create and manage cloud hosts in their own private networks to implement load balancing and secure access control.
  • VPC1 And VPC2 is a proprietary network created by different users.
  • the available area includes the resource management area and the public service area, and the specific user VPC area, which provides specific services for the cloud platform service.
  • the ECA and SCA in Figure 8 are two instances of the available area, representing East China and South China respectively. District A.
  • the resource management area is used to deploy resource management related programs and components, and can access physical servers or virtual machines in the public service area, and the public service area is used to deploy programs or services that provide specific services to users.
  • the user VPC communicates with each other.
  • the public service area contains the resource pool.
  • the resource pool is a collection of physical servers or virtual machines that can be run.
  • the Package Server represents the file server.
  • the master1 and master2 in the resource pool represent the Kubernetes master node, and the VPC1 and VPC2.
  • Node represents the Kubernetes slave node, and the default user isolation between user VPCs of different users.
  • the management area is a general level with respect to the higher level of the available area. It can open and manage the resource management area and the public service area of all available areas.
  • the Manager in the management area in Figure 8 represents Kubernetes. Manager is a hypervisor that can manage Kubernetes clusters.
  • the DB connected to the Manager in the management area of FIG. 8 represents a database
  • the etcd cluster connected to the Manager represents a cluster of database components.
  • the database is used to store data
  • the database component cluster as a distributed lock guarantees consistency.
  • Kubernetes The Manager manages the physical server or virtual machine of the public service area by calling the management master node of the resource management area. There are multiple management slave nodes in the resource pool of the public service area, when Kubernetes When the Manager deploys the Kubernetes master node, the available management slave nodes are selected from the plurality of management slave nodes of the resource pool, and the Kubernetes master node is deployed on the management slave node.
  • the node under the user VPC acts as a Kubernetes slave node and forms a Kubernetes cluster with the Kubernetes master node.
  • the embodiment of the present application ensures the isolation between different Kubernetes clusters by establishing a Kubernetes master node and a Kubernetes cluster under the user's proprietary network.
  • FIG. 6 is a structural block diagram of an apparatus for automatically setting up a Kubernetes master node according to an embodiment of the present application.
  • the device is provided. include:
  • the first obtaining unit 61 is configured to acquire a preset script file for setting up a Kubernetes master node
  • a second obtaining unit 62 configured to execute the script file to generate a configuration file according to a creation parameter input by the user related to the Kubernetes master node;
  • the building unit 63 is configured to start the SaltStack tool to construct the Kubernetes master node according to the configuration file.
  • the building unit 63 includes:
  • a node configuration unit configured to configure a management master node and a plurality of management slave nodes under the SaltStack tool, wherein the management master node is connected to the plurality of management slave nodes;
  • a calling unit configured to invoke the management master node, so that one of the plurality of management slave nodes constructs the Kubernetes master node according to the configuration file.
  • the calling unit includes:
  • a detecting unit configured to detect whether the Kubernetes master node exists under the plurality of management slave nodes
  • a selecting unit configured to: if the Kubernetes master node does not exist under the plurality of management slave nodes, select a management slave node corresponding to the creation parameter from the plurality of management slave nodes as a slave node;
  • the Kubernetes master node includes a database component, an interface service component, a control component, and a scheduling component
  • the building unit 63 includes:
  • a deployment unit configured to deploy the database component by using the SaltStack tool, and obtain network configuration data related to the creation parameter, and load the network configuration data into the database component;
  • sequentially deploying units for sequentially deploying the interface service component, the control component, and the scheduling component, and modifying a service address of the interface service component.
  • the deployment unit further includes:
  • a generating unit configured to generate a first security certificate and a second security certificate according to the configuration file, where the first security certificate is used to control access rights to the database component, and the second security certificate is used to control the interface Access to the service component;
  • a configuration unit configured to configure the first security certificate to the database component and the interface service component, and configure the second security certificate to the interface service component.
  • FIG. 9 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 9 of this embodiment includes a processor 90 and a memory 91 in which computer readable instructions 92 executable on the processor 90 are stored, for example, a Kubernetes master node is built. program of.
  • the processor 90 executes the computer readable instructions 92, the steps in the method embodiments of the foregoing automatic establishment of the Kubernetes master node are implemented, for example, steps S101 to S103 shown in FIG.
  • the processor 90 when executing the computer readable instructions 92, implements the functions of the various units of the apparatus embodiments described above, such as the functions of the units 61-63 shown in FIG.
  • the computer readable instructions 92 may be partitioned into one or more modules/units that are stored in the memory 91 and executed by the processor 90, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 92 in the terminal device 9.
  • the computer readable instructions 92 can be segmented into a first acquisition unit, a second acquisition unit, and a construction unit, each unit having a specific function as described above.
  • the terminal device may include, but is not limited to, a processor 90 and a memory 91. It will be understood by those skilled in the art that FIG. 9 is only an example of the terminal device 9, does not constitute a limitation of the terminal device 9, may include more or less components than those illustrated, or combine some components, or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 90 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 91 may be an internal storage unit of the terminal device 9, such as a hard disk or a memory of the terminal device 9.
  • the memory 91 may also be an external storage device of the terminal device 9, for example, a plug-in hard disk equipped on the terminal device 9, a smart memory card (SMC), and a secure digital (SD). Card, flash card, etc. Further, the memory 91 may also include both an internal storage unit of the terminal device 9 and an external storage device.
  • the memory 91 is configured to store the computer readable instructions and other programs and data required by the terminal device.
  • the memory 91 can also be used to temporarily store data that has been output or is about to be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

La présente solution est applicable au domaine technique du traitement de données, et concerne un procédé de construction automatique d'un nœud principal de Kubernetes, un dispositif terminal et un support de stockage lisible par ordinateur, le procédé consistant à : acquérir un fichier de script prédéfini utilisé pour construire le nœud principal de Kubernetes ; exécuter le fichier de script, de façon à produire un fichier de configuration selon des paramètres de création qui sont entrés par un utilisateur et qui sont associés au nœud principal de Kubernetes ; et démarrer un outil SaltStack, afin de construire le nœud principal de Kubernetes selon le fichier de configuration. La présente solution réalise la construction automatique d'un nœud principal de Kubernetes et améliore l'efficacité de construction du nœud principal de Kubernetes.
PCT/CN2018/093710 2018-03-30 2018-06-29 Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur Ceased WO2019184116A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810276602.8 2018-03-30
CN201810276602.8A CN108536519B (zh) 2018-03-30 2018-03-30 自动搭建Kubernetes主节点的方法及终端设备

Publications (1)

Publication Number Publication Date
WO2019184116A1 true WO2019184116A1 (fr) 2019-10-03

Family

ID=63482051

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093710 Ceased WO2019184116A1 (fr) 2018-03-30 2018-06-29 Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN108536519B (fr)
WO (1) WO2019184116A1 (fr)

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111444062A (zh) * 2020-04-01 2020-07-24 山东汇贸电子口岸有限公司 管理云数据库的主节点和从节点的方法及装置
CN111880815A (zh) * 2020-07-14 2020-11-03 北京中电广通技术服务有限公司 在封闭网络环境下快速部署Kubernetes的方法
CN111984623A (zh) * 2020-08-14 2020-11-24 北京人大金仓信息技术股份有限公司 数据库集群自动化部署方法、装置、介质和电子设备
CN112632527A (zh) * 2020-12-18 2021-04-09 航天信息股份有限公司 一种用于服务开放平台的api测试方法及系统
CN113301069A (zh) * 2020-04-07 2021-08-24 阿里巴巴集团控股有限公司 无服务器化管理系统、其调用方法及云原生应用平台
CN113965546A (zh) * 2021-09-10 2022-01-21 济南浪潮数据技术有限公司 一种容器云平台为应用设置租户专用dns服务器的方法
CN113986881A (zh) * 2021-10-29 2022-01-28 济南浪潮数据技术有限公司 一种双活及主从同步环境的搭建方法、系统、设备及介质
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114185646A (zh) * 2021-12-13 2022-03-15 深圳壹账通智能科技有限公司 一种部署产品的方法、装置、设备及可读存储介质
CN114443059A (zh) * 2020-10-30 2022-05-06 中国联合网络通信集团有限公司 Kubernetes集群的部署方法、装置及设备
CN114493548A (zh) * 2022-02-22 2022-05-13 光大科技有限公司 持续交付实现方法及装置
CN114679380A (zh) * 2021-04-09 2022-06-28 腾讯云计算（北京）有限责任公司 边缘集群的创建方法和相关装置
CN115022335A (zh) * 2022-05-27 2022-09-06 桂林电子科技大学 基于多目标均衡优化的Kubernetes Pod调度方法
CN115357336A (zh) * 2022-08-04 2022-11-18 招商银行股份有限公司 容器组的在线扩容方法、装置、终端设备与介质
EP4095678A1 (fr) * 2021-08-20 2022-11-30 Beijing Baidu Netcom Science And Technology Co., Ltd. Procédé et appareil de déploiement d'un groupe, dispositif et support d'informations
CN116132267A (zh) * 2022-12-30 2023-05-16 天翼物联科技有限公司 基于公有云的物联网设备平台及其部署方法
CN116634001A (zh) * 2023-06-12 2023-08-22 中国光大银行股份有限公司 一种区块链联盟建立方法及装置
CN117112144A (zh) * 2023-09-22 2023-11-24 上海卓悠网络科技有限公司 一种在android系统上部署k3s的方法及系统、存储介质
US11861405B2 (en) 2020-04-29 2024-01-02 Kyndryl, Inc. Multi-cluster container orchestration
CN119225752A (zh) * 2024-12-03 2024-12-31 之江实验室 基于RISC-V架构集成PENGLAI可信执行环境的Linux系统及其搭建方法
CN119292743A (zh) * 2024-09-26 2025-01-10 浪潮云信息技术股份公司 一种基于Kubernetes使用XXL-JOB实现多租户任务调度的方法

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392020A (zh) * 2018-10-26 2019-02-26 中山大学 一种面向5g移动网络的资源管理平台
CN109189569A (zh) * 2018-11-02 2019-01-11 郑州云海信息技术有限公司 一种Docker调度优化方法、装置、终端及存储介质
CN111352664B (zh) * 2018-12-05 2023-11-03 北京京东尚科信息技术有限公司 分布式机器学习任务启动方法、系统、设备及存储介质
CN109753301A (zh) * 2018-12-06 2019-05-14 东软集团股份有限公司 应用系统部署方法、装置、存储介质及电子设备
CN109857644A (zh) * 2018-12-30 2019-06-07 贝壳技术有限公司 一种快速搭建软件测试环境的方法及装置
CN110166278A (zh) * 2019-04-09 2019-08-23 平安科技（深圳）有限公司 Kubernetes集群搭建方法、装置、计算机设备及存储介质
CN111144839B (zh) * 2019-12-17 2024-02-02 深圳市优必选科技股份有限公司 一种项目构建方法、持续集成系统及终端设备
CN115834168B (zh) * 2022-11-14 2024-08-13 浪潮云信息技术股份公司 一种基于私网连接的公共服务网络的实现方法及系统
CN115878166A (zh) * 2022-12-29 2023-03-31 济南浪潮数据技术有限公司 flowable云平台的运维方法、装置、设备及介质
CN118331764B (zh) * 2024-06-07 2024-08-09 北京凌云雀科技有限公司 一种基于Kubernetes平台的远程数据处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105553737A (zh) * 2015-12-25 2016-05-04 浪潮(北京)电子信息产业有限公司 一种节点管理方法与系统
US20170111241A1 (en) * 2015-10-19 2017-04-20 Draios Inc. Automated service-oriented performance management
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102591679B (zh) * 2011-11-30 2014-09-17 中国科学院计算机网络信息中心 一种集群系统应用软件快速部署方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170111241A1 (en) * 2015-10-19 2017-04-20 Draios Inc. Automated service-oriented performance management
CN105553737A (zh) * 2015-12-25 2016-05-04 浪潮(北京)电子信息产业有限公司 一种节点管理方法与系统
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111444062A (zh) * 2020-04-01 2020-07-24 山东汇贸电子口岸有限公司 管理云数据库的主节点和从节点的方法及装置
CN111444062B (zh) * 2020-04-01 2023-09-19 山东汇贸电子口岸有限公司 管理云数据库的主节点和从节点的方法及装置
CN113301069A (zh) * 2020-04-07 2021-08-24 阿里巴巴集团控股有限公司 无服务器化管理系统、其调用方法及云原生应用平台
US11861405B2 (en) 2020-04-29 2024-01-02 Kyndryl, Inc. Multi-cluster container orchestration
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114006815B (zh) * 2020-07-13 2024-01-26 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN111880815B (zh) * 2020-07-14 2024-01-23 北京朗玛峰科技有限公司 在封闭网络环境下快速部署Kubernetes的方法
CN111880815A (zh) * 2020-07-14 2020-11-03 北京中电广通技术服务有限公司 在封闭网络环境下快速部署Kubernetes的方法
CN111984623A (zh) * 2020-08-14 2020-11-24 北京人大金仓信息技术股份有限公司 数据库集群自动化部署方法、装置、介质和电子设备
CN111984623B (zh) * 2020-08-14 2024-02-09 北京人大金仓信息技术股份有限公司 数据库集群自动化部署方法、装置、介质和电子设备
CN114443059A (zh) * 2020-10-30 2022-05-06 中国联合网络通信集团有限公司 Kubernetes集群的部署方法、装置及设备
CN112632527A (zh) * 2020-12-18 2021-04-09 航天信息股份有限公司 一种用于服务开放平台的api测试方法及系统
CN112632527B (zh) * 2020-12-18 2024-03-08 航天信息股份有限公司 一种用于服务开放平台的api测试方法及系统
CN114679380B (zh) * 2021-04-09 2024-04-26 腾讯云计算（北京）有限责任公司 边缘集群的创建方法和相关装置
CN114679380A (zh) * 2021-04-09 2022-06-28 腾讯云计算（北京）有限责任公司 边缘集群的创建方法和相关装置
EP4095678A1 (fr) * 2021-08-20 2022-11-30 Beijing Baidu Netcom Science And Technology Co., Ltd. Procédé et appareil de déploiement d'un groupe, dispositif et support d'informations
US20230060053A1 (en) * 2021-08-20 2023-02-23 Beijing Baidu Netcom Science Technology Co., Ltd. Method and apparatus of deploying a cluster, and storage medium
CN113965546A (zh) * 2021-09-10 2022-01-21 济南浪潮数据技术有限公司 一种容器云平台为应用设置租户专用dns服务器的方法
CN113986881A (zh) * 2021-10-29 2022-01-28 济南浪潮数据技术有限公司 一种双活及主从同步环境的搭建方法、系统、设备及介质
CN114185646A (zh) * 2021-12-13 2022-03-15 深圳壹账通智能科技有限公司 一种部署产品的方法、装置、设备及可读存储介质
CN114493548A (zh) * 2022-02-22 2022-05-13 光大科技有限公司 持续交付实现方法及装置
CN115022335A (zh) * 2022-05-27 2022-09-06 桂林电子科技大学 基于多目标均衡优化的Kubernetes Pod调度方法
CN115022335B (zh) * 2022-05-27 2024-11-12 桂林电子科技大学 基于多目标均衡优化的Kubernetes Pod调度方法
CN115357336A (zh) * 2022-08-04 2022-11-18 招商银行股份有限公司 容器组的在线扩容方法、装置、终端设备与介质
CN116132267A (zh) * 2022-12-30 2023-05-16 天翼物联科技有限公司 基于公有云的物联网设备平台及其部署方法
CN116634001A (zh) * 2023-06-12 2023-08-22 中国光大银行股份有限公司 一种区块链联盟建立方法及装置
CN117112144A (zh) * 2023-09-22 2023-11-24 上海卓悠网络科技有限公司 一种在android系统上部署k3s的方法及系统、存储介质
CN117112144B (zh) * 2023-09-22 2024-03-12 上海卓悠网络科技有限公司 一种在android系统上部署k3s的方法及系统、存储介质
CN119292743A (zh) * 2024-09-26 2025-01-10 浪潮云信息技术股份公司 一种基于Kubernetes使用XXL-JOB实现多租户任务调度的方法
CN119225752A (zh) * 2024-12-03 2024-12-31 之江实验室 基于RISC-V架构集成PENGLAI可信执行环境的Linux系统及其搭建方法

Also Published As

Publication number Publication date
CN108536519A (zh) 2018-09-14
CN108536519B (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
WO2019184116A1 (fr) Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur
WO2019218463A1 (fr) Procédé et appareil de construction automatique d'un nœud maître kubernetes en fonction d'un outil ansible, dispositif terminal et support d'informations lisible
CN108549580B (zh) 自动部署Kubernetes从节点的方法及终端设备
CN107145380B (zh) 虚拟资源编排方法及装置
US10700947B2 (en) Life cycle management method and device for network service
CN111371579B (zh) 云平台部署方法、装置、服务器及存储介质
WO2021147288A1 (fr) Procédé, dispositif et système de gestion de groupe de conteneurs
EP3913859B1 (fr) Procédé et appareil de gestion de cycle de vie de fonction réseau virtualisée (vnf)
EP3442201B1 (fr) Procédé de construction de plateforme en nuage et plateforme en nuage
WO2017162173A1 (fr) Procédé et dispositif pour établir une connexion d'un groupe de serveurs en nuage
CN106375101A (zh) 一种生命周期管理方法及装置
CN104468791B (zh) 私有云IaaS平台的构建方法
CN108170508A (zh) 批量创建虚拟机的方法、装置、设备及其存储介质
CN113127150A (zh) 云原生系统的快速部署方法、装置、电子设备和存储介质
CN106325953A (zh) 一种Weblogic集群一键自动部署方法
CN104717233A (zh) 数据库部署方法和装置
US20170300696A1 (en) Software verification method and apparatus
CN115604120B (zh) 一种多云集群资源共享方法、装置、设备及存储介质
US11573819B2 (en) Computer-implemented method for reducing service disruption times for a universal customer premise equipment, uCPE, device with resource constraint in a network functions virtualization, NFV, network infrastructure
EP3193253B1 (fr) Procédé, appareil, et système, d'affichage de noms de machine virtuelle
CN114564530A (zh) 一种数据库访问方法、装置、设备及存储介质
CN110019145A (zh) 一种大数据平台的多环境级联的方法和装置
KR101493828B1 (ko) 가상머신 초기 설정 자동화 방법 및 가상머신 초기 설정 자동화 서비스 제공 방법
US10979439B1 (en) Identity management for coordinated devices in a networked environment
CN111427589B (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: 18911924

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 21.01.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18911924

Country of ref document: EP

Kind code of ref document: A1