A method, system, storage medium and device for application component scheduling

Abstract

The application provides a method for application component scheduling when openstack is deployed on kubernetes, comprising the following steps: creating a node role planning file, dividing the node role planning file into an abstract layer, an application layer and an application component layer; configuring the node role planning file, planning roles of each node bearing an openstack cloud computing platform application in the abstract layer; and transmitting the configured node role planning file into a deployment tool for deployment, wherein the planning roles of each node bearing the openstack cloud computing platform application in the abstract layer comprises dividing each node into any one of a control node role, a network node role, a computing node role, a storage node role and a monitoring node role.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a method and system for scheduling application components when openstack is deployed on kubernetes, a storage medium and equipment. BACKGROUND

[0002] OpenStack is an open-source cloud computing management platform, and its main purpose is to hide the details of underlying physical hardware through virtualization technology, to provide users with resource isolation and resource usage limitation in the aspects of computing, storage and network, so that users can see that it is like occupying a machine. At present, a large number of developers worldwide participate in it, which provides a strong guarantee for the rapid development of OpenStack. After years of development, the technology of OpenStask has become mature and stable, and it has flexible scalability while providing high availability, so OpenStack has been widely used in various industries.

[0003] Kubernetes is a new container cluster management system based on container technology, which provides deployment and running, resource scheduling, service discovery and dynamic scaling for containerized applications on the basis of docker technology, and provides convenience for large-scale container cluster management.

[0004] Therefore, it has become a trend to deploy openstack cloud computing platform on kubernetes, so as to improve the deployment flexibility, scalability, fault self-recovery and other capabilities of openstack cloud computing platform. SUMMARY

[0005] Before deploying openstack cloud computing platform on kubernetes, the roles of each node that needs to carry openstack cloud computing platform application need to be planned, that is, to plan which applications in openstack cloud computing platform need to be deployed on which nodes. In addition to planning the roles of each node, it is also necessary to create a label on the corresponding node that can be recognized by kubernetes, so as to facilitate kubernetes to schedule the related applications of openstack cloud computing platform to the nodes with the corresponding label.

[0006] The current node role planning method when deploying the openstack cloud computing platform on the kubernetes is a non-record planning method, that is, the deployment personnel simply plans the node role by using a temporary method (such as thinking on paper or in the mind) before deployment. This non-record planning method does not transfer the node role planning result to the deployment tool in a certain way, and does not participate in the actual deployment process, that is, the node role planning result is not linked to the deployment tool and the deployment process, and is easy to lose. Moreover, the current node role planning granularity is very coarse, that is, many applications in the openstack cloud computing platform correspond to the same node role, which leads to low flexibility in deploying the openstack.

[0007] In addition, the current node label creation method when deploying the openstack cloud computing platform on the kubernetes is to create multiple labels for multiple nodes by using a manual method on the basis of node planning. When the number of nodes and the number of labels is large, this manual node label creation method is very complex and time-consuming, and is prone to errors.

[0008] Therefore, it is necessary to improve the application component scheduling method when deploying the openstack cloud computing platform on the kubernetes, so as to improve the flexibility of deploying the openstack cloud computing platform on the kubernetes, reduce the probability of errors caused by human operation, reduce the operation complexity, and improve the efficiency of node label creation.

[0009] Therefore, it is necessary to improve the application component scheduling method when deploying the openstack cloud computing platform on the kubernetes, so as to improve the flexibility of deploying the openstack cloud computing platform on the kubernetes, reduce the probability of errors caused by human operation, reduce the operation complexity, and improve the efficiency of node label creation.

[0010] Based on the above purpose, the application provides an application component scheduling method when deploying the openstack on the kubernetes, which comprises the following steps:

[0011] A node role planning file is created, and the node role planning file is divided into an abstract layer, an application layer and an application component layer;

[0012] The node role planning file is configured, and the roles of the nodes carrying the openstack cloud computing platform applications are planned in the abstract layer; and

[0013] The configured node role planning file is transmitted into a deployment tool for deployment,

[0014] The role planning of the nodes carrying the openstack cloud computing platform application in the abstraction layer includes dividing the nodes into any one of a control node role, a network node role, a computing node role, a storage node role and a monitoring node role.

[0015] In some embodiments, the deployment tool is ansible.

[0016] In some embodiments, the method further includes, when configuring the node role planning file, planning roles of the nodes carrying the openstack cloud computing platform application in the application layer to determine the nodes corresponding to the specific application modules.

[0017] In some embodiments, the method further includes, when configuring the node role planning file, planning roles of the nodes carrying the openstack cloud computing platform application in the application component layer to determine the nodes corresponding to each component in the specific application module.

[0018] In some embodiments, the method further includes automatically generating node labels for each component of the application component layer.

[0019] In some embodiments, the automatic creation of the node labels includes reading the node role planning file passed in during the deployment process, and obtaining a node list in which the components should be carried from the node role planning file for each component of the application component layer in the node role planning file, and generating a node label corresponding to the component for each node in the node list using a kubernetes related command.

[0020] In some embodiments, the format of the node label is a fixed string prefix + component name.

[0021] Another aspect of the present application also provides a system for application component scheduling when openstack is deployed on kubernetes, comprising:

[0022] A creating module for creating a node role planning file, dividing the node role planning file into an abstraction layer, an application layer and an application component layer;

[0023] A configuring module for configuring the node role planning file, planning roles of the nodes carrying the openstack cloud computing platform application in the abstraction layer; and

[0024] A passing-in module for passing the configured node role planning file into a deployment tool for deployment,

[0025] The configuration module divides each node carrying the openstack cloud computing platform application into any one of a control node role, a network node role, a computing node role, a storage node role and a monitoring node role at the abstraction layer.

[0026] In some embodiments, the deployment tool is ansible.

[0027] In some embodiments, when configuring the node role planning file, the configuration module further plans roles for each node carrying the openstack cloud computing platform application at the application component layer to determine nodes corresponding to each component in a specific application module.

[0028] In some embodiments, when configuring the node role planning file, the configuration module further plans roles for each node carrying the openstack cloud computing platform application at the application component layer to determine nodes corresponding to each component in a specific application module.

[0029] In some embodiments, the system further comprises a label generation module configured to automatically generate node labels for each component in the application component layer. The label generation module reads the node role planning file input in the deployment process, and for each component in the application component layer in the node role planning file, obtains a node list that should carry the component from the node role planning file, and generates a node label corresponding to the component for each node in the node list using a kubernetes related command. The format of the node label is: a fixed string prefix + component name

[0030] In another aspect of the present application, a computer readable storage medium storing computer program instructions is provided, and the computer program instructions are executed to implement any of the above methods.

[0031] In another aspect of the present application, a computer device is provided, which comprises a memory and a processor, and the memory stores a computer program, and the computer program is executed by the processor to implement any of the above methods.

[0032] This invention proposes an application component scheduling method and system for OpenStack deployment on Kubernetes. Based on the Ansible deployment tool, it introduces a node role planning file, making node role planning, deployment tools, and the deployment process a coherent whole, improving the integrity and synergy of node role planning and deployment. The node configuration in the node configuration file is hierarchically divided, increasing the flexibility of the deployment process. Node labels are automatically generated and created for each component in the application component layer without human intervention, effectively reducing the possibility of human error, lowering operational complexity, and improving the efficiency of node label creation. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a schematic diagram of an application component scheduling method for deploying OpenStack on Kubernetes according to an embodiment of the present invention;

[0035] Figure 2 This is a schematic diagram of an application component scheduling system when OpenStack is deployed on Kubernetes according to an embodiment of the present invention.

[0036] Figure 3 A schematic diagram of a computer-readable storage medium for implementing a method for scheduling application components when deploying OpenStack on Kubernetes according to an embodiment of the present invention;

[0037] Figure 4 This is a schematic diagram of the hardware structure of a computer device for implementing a method for scheduling application components when deploying OpenStack on Kubernetes, according to an embodiment of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0039] It should be noted that all the expressions of "first" and "second" in the embodiments of the present application are used to distinguish two non-identical entities or non-identical parameters with the same name, and it can be seen that "first" and "second" are only used for the convenience of description, and should not be understood as a limitation on the embodiments of the present application. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, the process, method, system, product or device inherently includes other steps or units in addition to a series of steps or units.

[0040] Based on the above purpose, in a first aspect of the embodiments of the present application, an embodiment of a method for scheduling application components when openstack is deployed on kubernetes is provided. Figure 1 An embodiment of a method for scheduling application components when openstack is deployed on kubernetes provided by the present application is shown. As shown in Figure 1 The embodiment of the present application includes the following steps:

[0041] Step S10, creating a node role planning file, dividing the node role planning file into an abstract layer, an application layer and an application component layer;

[0042] Step S20, configuring the node role planning file, and planning the roles of each node carrying the openstack cloud computing platform application in the abstract layer;

[0043] Step S30, inputting the configured node role planning file into a deployment tool for deployment,

[0044] Planning the roles of each node carrying the openstack cloud computing platform application in the abstract layer includes dividing each node into any one of a control node role, a network node role, a computing node role, a storage node role and a monitoring node role.

[0045] In some preferred embodiments, the method further includes, when configuring the node role planning file, planning the roles of each node carrying the openstack cloud computing platform application in the application layer to determine the nodes corresponding to the specific application modules.

[0046] In some preferred embodiments, the method further includes, when configuring the node role planning file, planning the roles of each node carrying the openstack cloud computing platform application in the application component layer to determine the nodes corresponding to each component in the specific application module.

[0047] In some preferred embodiments, the method further includes automatically generating node labels for each component of the application component layer.

[0048] In some preferred embodiments, the automatically creating the node tags comprises: reading a node role planning file inputted in the deployment process; and for each component of an application component layer in the node role planning file, obtaining a node list on which the component should run from the node role planning file, and generating a node tag corresponding to the component for each node in the node list using a kubernetes related command. The format of the node tag is: a fixed string prefix + component name.

[0049] In an embodiment of the present application, the node role planning file is divided into three layers: an abstract layer, an application layer and an application component layer, wherein the openstack five abstract function role nodes (control / network / compute / storage / monitor) are defined in the abstract layer, the nodes corresponding to the specific application modules are defined in the application layer, and the nodes corresponding to each component in the specific application modules are defined in the application component layer; if a node needs to carry a function, a module or a component of a module, the node only needs to be configured into the corresponding section in the node role planning file.

[0050] The abstract layer includes five roles: control node role, network node role, compute node role, storage node role and monitor node role. By default, when configuring the node role planning file, only the five node roles in the abstract layer need to be planned, for example, the nodes carrying the control function need to be configured into the control node section of the node role planning file, and the nodes carrying the network function need to be configured into the network node section of the node role planning file.

[0051] If the node role planning in the abstract layer does not meet the deployment scenario, the application layer in the node role planning file can be configured for node role planning when configuring the node role planning file.

[0052] If the node role planning in the application layer still does not meet the deployment scenario, the application component layer in the node role planning file can be configured for node role planning when configuring the node role planning file.

[0053] For example, Figure 1As shown, the application provides a method for scheduling application components when deploying an openstack cloud computing platform on a kubernetes. The method introduces a node role planning file on the basis of deployment tool ansible, and passes the node role planning file to the deployment process for use in the deployment process, so that the node role planning in the deployment process and the deployment tool and the deployment process become a coherent whole, improving the integrity and linkage of node role planning and deployment. At the same time, the node configuration in the node configuration file is divided into three levels: abstract layer, application layer and application component layer. By default, only node role configuration in the abstract layer is required. If the default condition does not meet the needs of the deployment scene, the node role can be configured in the application layer or the application component layer, improving the flexibility of the deployment process.

[0054] In addition, the method also automatically generates node tags for each component in the application component layer according to the node configuration in the node role planning file, and automatically creates corresponding node tags for each component in the application component layer, so that the kubernetes can schedule these application components to these nodes. The method is fully automated when creating node tags, without human intervention, effectively reducing the possibility of human error, reducing the complexity of operation, and improving the efficiency of node tag creation.

[0055] The second aspect of the embodiment of the application also provides a system for scheduling application components when deploying openstack on kubernetes. Figure 2 As shown, the embodiment of the system for scheduling application components when deploying openstack on kubernetes provided by the application is shown. As Figure 2 As shown, a system for scheduling application components when deploying openstack on kubernetes includes a creation module 10 for creating a node role planning file, dividing the node role planning file into an abstract layer, an application layer and an application component layer; a configuration module 20 for configuring the node role planning file, and planning the roles of each node carrying the openstack cloud computing platform application in the abstract layer; and a transmission module 30 for transmitting the configured node role planning file to the deployment tool for deployment. The configuration module 20 divides each node carrying the openstack cloud computing platform application into any one of a control node role, a network node role, a computing node role, a storage node role and a monitoring node role in the abstract layer.

[0056] In some preferred embodiments, the configuration module 20, when configuring the node role planning file, further plans roles of each node carrying the openstack cloud computing platform application at the application layer to determine the node corresponding to the specific application module.

[0057] In some preferred embodiments, the configuration module 20, when configuring the node role planning file, further plans roles of each node carrying the openstack cloud computing platform application at the application component layer to determine the node corresponding to each component in the specific application module.

[0058] In some preferred embodiments, the system further comprises a label generation module for automatically generating node labels for each component at the application component layer. The label generation module reads the node role planning file passed in during the deployment process, and for each component at the application component layer in the node role planning file, obtains a list of nodes that should carry the component from the node role planning file, and generates a node label corresponding to the component for each node in the list of nodes using kubernetes-related commands. The format of the node label is: a fixed string prefix + component name.

[0059] As shown in Figure 2 The present application provides an application component scheduling system when deploying an openstack cloud computing platform on kubernetes. The system introduces a node role planning file on the basis of the deployment tool ansible, and passes the node role planning file to the deployment process during the deployment process for use by the deployment process, so that the node role planning during the deployment process and the deployment tool and the deployment process become a coherent whole, improving the integrity and linkage of node role planning and deployment. At the same time, the node configuration in the node configuration file is divided into three levels: the abstract layer, the application layer and the application component layer. By default, only node role configuration at the abstract layer is required. If the default does not meet the needs of the deployment scenario, the node role can be configured at the application layer or the application component layer, improving the flexibility of the deployment process.

[0060] In addition, the system also automatically generates node labels for each component at the application component layer according to the node configuration in the node role planning file, and automatically creates corresponding node labels for the nodes corresponding to each component at the application component layer, so that kubernetes can schedule these application components to these nodes. The system is fully automated when creating node labels, without human intervention, effectively reducing the possibility of human error, reducing the complexity of operation, and improving the efficiency of node label creation.

[0061] The third aspect of the embodiment of the present application also provides a computer readable storage medium, Figure 3A schematic diagram of a computer readable storage medium implementing the method of scheduling application components when openstack is deployed on kubernetes according to an embodiment of the present application is shown. As shown in Figure 3 The computer readable storage medium 3 stores computer program instructions 31 which can be executed by a processor. The computer program instructions 31, when executed, implement the method of any of the above embodiments.

[0062] It should be understood that all the embodiments, features and advantages described above in relation to the method of scheduling application components when openstack is deployed on kubernetes according to the present application are equally applicable to the system of scheduling application components when openstack is deployed on kubernetes according to the present application and the storage medium according to the present application, mutatis mutandis.

[0063] A fourth aspect of the embodiments of the present application also provides a computer device comprising a memory 402 and a processor 401, the memory storing a computer program which, when executed by the processor, implements the method of any of the above embodiments.

[0064] As shown in Figure 4 A hardware structure schematic diagram of one embodiment of the computer device implementing the method of scheduling application components when openstack is deployed on kubernetes according to the present application is shown. As shown in Figure 4 The computer device shown in the figure comprises a processor 401 and a memory 402, and can further comprise an input device 403 and an output device 404. The processor 401, the memory 402, the input device 403 and the output device 404 can be connected by a bus or other means, Figure 4 for example, by a bus. The input device 403 can receive input digital or character information, and generate key signal input related to user settings and function control of the system of scheduling application components when openstack is deployed on kubernetes. The output device 404 can comprise a display device such as a display screen.

[0065] The memory 402, as a non-volatile computer readable storage medium, can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as the program instructions / modules corresponding to the application component scheduling method when openstack is deployed on kubernetes in the embodiments of the present application. The memory 402 can include a program storage area and a data storage area, wherein the program storage area can store an operating system and application programs required by at least one function; the data storage area can store data created by use of the application component scheduling method when openstack is deployed on kubernetes and the like. In addition, the memory 402 can include a high-speed random access memory, and can also include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 402 can optionally include a memory disposed remotely with respect to the processor 401, and these remote memories can be connected to the local module through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0066] The processor 401 performs various functional applications and data processing of the server by running the non-volatile software programs, instructions and modules stored in the memory 402, that is, implements the application component scheduling method when openstack is deployed on kubernetes in the above-mentioned method embodiments.

[0067] Finally, it should be noted that the computer readable storage medium (for example, the memory) herein can be a volatile memory or a non-volatile memory, or can include both volatile memory and non-volatile memory. As an example but not limitation, the non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. The volatile memory can include random access memory (RAM) which can serve as an external cache memory. As an example but not limitation, the RAM can be obtained in various forms, such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The storage device of the disclosed aspect is intended to include but not limited to these and other suitable types of memory.

[0068] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments disclosure.

[0069] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein can be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0070] The above are example embodiments of the present disclosure, but it should be noted that various changes and modifications can be made without departing from the scope of the present embodiments disclosure defined by the claims. The functions, steps and / or actions of the method claims in accordance with the embodiments described herein need not be performed in any particular order. Furthermore, although the elements of the present embodiments disclosure can be described or claimed in individual forms, other embodiments can include a plurality of these elements in order to carry out the objectives of the present embodiments disclosure. The terms "comprises", "comprising", "includes", "including" and the like specified herein are used in the sense of "including but not limited to".

[0071] It should be understood that, as used herein, "and / or" is used to include any and all combinations of one or more of the associated listed items. The above reference to an embodiment of the present embodiments disclosure is not a limitation, but merely an example of an embodiment of the present embodiments disclosure.

[0072] Those skilled in the art should understand that the above discussion of any embodiment is only exemplary, and is not intended to mean that the scope of the embodiments disclosed by the present application (including claims) is limited to these examples; under the idea of the embodiments of the present application, the above embodiments or technical features in different embodiments can also be combined, and there are many other changes of different aspects of the embodiments of the present application as above. In order to be brief, they are not provided in details. Therefore, any omission, modification, equivalent replacement, improvement, etc. made in the spirit and principle of the embodiments of the present application shall be included in the protection scope of the embodiments of the present application.

Claims

1. A method for application component scheduling, the method comprising: The method comprises the following steps: creating a node role planning file, and dividing the node role planning file into an abstract layer, an application layer, and an application component layer; configuring the node role planning file to plan roles of nodes carrying an openstack cloud computing platform application in the abstract layer, to plan roles of the nodes carrying the openstack cloud computing platform application in the application layer to determine nodes corresponding to specific application modules, and to plan roles of the nodes carrying the openstack cloud computing platform application in the application component layer to determine nodes corresponding to components in the specific application modules; wherein planning roles of the nodes carrying the openstack cloud computing platform application in the abstract layer comprises dividing the nodes into any one of a control node role, a network node role, a computing node role, a storage node role, and a monitoring node role; transmitting the configured node role planning file into a deployment tool for deployment; reading the node role planning file transmitted in the deployment process, and for each component in the application component layer in the node role planning file, obtaining a node list that should carry the component from the node role planning file, and generating a node tag corresponding to the component for each node in the node list by using a kubernetes related command.

2. A system for application component scheduling, the system comprising: The method comprises: a creating module for creating a node role planning file, and dividing the node role planning file into an abstract layer, an application layer, and an application component layer; a configuring module for configuring the node role planning file to plan roles of nodes carrying an openstack cloud computing platform application in the abstract layer, to plan roles of the nodes carrying the openstack cloud computing platform application in the application layer to determine nodes corresponding to specific application modules, and to plan roles of the nodes carrying the openstack cloud computing platform application in the application component layer to determine nodes corresponding to components in the specific application modules; wherein dividing the nodes carrying the openstack cloud computing platform application in the abstract layer comprises dividing the nodes into any one of a control node role, a network node role, a computing node role, a storage node role, and a monitoring node role; a transmitting module for transmitting the configured node role planning file into a deployment tool for deployment; a tag generating module for reading the node role planning file transmitted in the deployment process, and for each component in the application component layer in the node role planning file, obtaining a node list that should carry the component from the node role planning file, and generating a node tag corresponding to the component for each node in the node list by using a kubernetes related command.

3. A computer-readable storage medium, characterized in that, A computer program instruction is stored, and the computer program instruction is executed to implement the method of claim 1. A computer program instruction is stored, and the computer program instruction is executed to implement the method of claim 1.

Images