CN109039784B - Node deployment method and device of OpenStack - Google Patents
Node deployment method and device of OpenStack Download PDFInfo
- Publication number
- CN109039784B CN109039784B CN201811133228.2A CN201811133228A CN109039784B CN 109039784 B CN109039784 B CN 109039784B CN 201811133228 A CN201811133228 A CN 201811133228A CN 109039784 B CN109039784 B CN 109039784B
- Authority
- CN
- China
- Prior art keywords
- node
- network
- information
- type
- openstack
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a node deployment method of OpenStack, which comprises the following steps: obtaining type information of a node currently installed by OpenStack; acquiring network information of the node according to the type information; generating a first type configuration file corresponding to the node according to the type information and the network information; and installing the network service installation package corresponding to the node according to the first type configuration file and the installation function of the node, and generating and starting a corresponding network plug-in. After the type information of the currently installed node is obtained, the network information of the node is correspondingly obtained. Therefore, the generation of the configuration file and the installation of the network service where the node is located are automatically completed, and finally, the corresponding network plug-in is generated and started, so that the automatic configuration installation of the node is realized. The user intervention degree in the node deployment process is low, the operation is simple and convenient, and the effect of greatly improving the deployment efficiency of each node is effectively realized.
Description
Technical Field
The application relates to the technical field of cloud computing, in particular to a node deployment method and device of OpenStack.
Background
With the development of information technology, cloud service technology is developing and rapidly developing in order to meet the increasingly expanding mass data processing requirements. OpenStack is an open source IaaS (Infrastructure as a Service) cloud computing platform. The main services of the OpenStack include computing services, network services, mirroring services, storage services and the like, and different types of services can be deployed on different types of nodes, so that various functions of the cloud computing platform and unified management of the functions are realized.
In the OpenStack process, a network system needs to be established, for example, the establishment of a network environment, for example, the configuration of network information such as a network mode and a network mechanism is completed, and service nodes, for example, a control node and a computing node, are installed to complete the installation of a network service where each node is located. The OpenStack comprises a plurality of control nodes and computing nodes, and network information needs to be repeatedly configured to corresponding nodes when each node is deployed. However, in the process of implementing the present invention, the inventors find that at least the problem of low node deployment efficiency exists in the establishment process of the conventional OpenStack.
Disclosure of Invention
Therefore, it is necessary to provide a node deployment method of OpenStack, a node deployment apparatus of OpenStack, a computer device and a storage medium, which can greatly improve node deployment efficiency, in order to solve the above technical problems.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in one aspect, an embodiment of the present invention provides a node deployment method for OpenStack, including:
obtaining type information of a node currently installed by OpenStack;
acquiring network information of the node according to the type information;
generating a first type configuration file corresponding to the node according to the type information and the network information;
and installing the network service installation package corresponding to the node according to the first type configuration file and the installation function of the node, and generating and starting a corresponding network plug-in.
In one embodiment, the network information includes at least network mechanism information, network mode information, IP domain and portal information.
In one embodiment, the step of installing the network service installation package corresponding to the node according to the first type of configuration file and the installation function of the node, and generating and enabling a corresponding network plugin includes:
starting the installation function of the node according to the type information and the network mechanism information, installing the network service installation package corresponding to the node, and generating a corresponding second type configuration file and the network plug-in;
configuring the second type configuration file according to the network mechanism information;
and starting the network plug-in.
In one embodiment, after the step of starting the network plug-in, the method further includes:
and if the node is a control node, establishing a network with a corresponding mode according to the network mode information.
In one embodiment, the second type of configuration file includes a network mechanism configuration file corresponding to the network mechanism information;
the method further comprises the following steps:
setting an IP address of a corresponding type for the node according to the IP domain;
and binding the network interface information of the network mechanism configuration file according to the network mechanism information.
In one embodiment, the method further comprises:
and starting a verification function of the OpenStack, and installing and verifying the network plug-in corresponding to the network service of the OpenStack.
In one embodiment, the method further comprises:
installing a database of the node, and reading the network information in the first type configuration file;
and respectively storing the network information and the type information into corresponding storage tables in the database.
In one embodiment, the method further comprises:
and sending the file name of the first type configuration file and the network information to a display for displaying.
In one embodiment, the step of obtaining the network information of the node according to the type information includes:
and if the node is determined to be a control node according to the type information, receiving the input network information of the node.
In one embodiment, the step of obtaining the network information of the node according to the type information includes:
and if the node is determined to be a control node according to the type information, reading the network information of the node from a preset information table.
In one embodiment, the nodes comprise control nodes or computing nodes;
the step of obtaining the network information of the node according to the type information includes:
if the node is determined to be a computing node according to the type information, network information of the installed control node is obtained;
and matching the corresponding network information for the computing node according to the network information of the control node.
In another aspect, a node deployment apparatus of OpenStack is further provided, including:
the type acquisition module is used for acquiring the type information of the node currently installed by the OpenStack;
the network acquisition module is used for acquiring the network information of the node according to the type information;
the configuration module is used for generating a first type of configuration file corresponding to the node according to the type information and the network information;
and the network installation module is used for installing the network service installation package corresponding to the node according to the first type of configuration file and the installation function of the node, and generating and starting a corresponding network plug-in.
In another aspect, a computer device is further provided, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the node deployment method of OpenStack when executing the computer program.
In still another aspect, a computer readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the node deployment method of OpenStack.
One of the above technical solutions has the following advantages and beneficial effects:
according to the node deployment method, the node deployment device, the computer equipment and the storage medium of the OpenStack, after the type information of the currently installed node is obtained, the network information of the node is correspondingly obtained. Therefore, the generation of the configuration file and the installation of the network service where the node is located are automatically completed, and finally, the corresponding network plug-in is generated and started, so that the automatic configuration installation of the node is realized. The user intervention degree in the node deployment process is low, the operation is simple and convenient, and the effect of greatly improving the deployment efficiency of each node is effectively realized.
Drawings
Fig. 1 is an application environment diagram of a node deployment method of OpenStack in an embodiment;
fig. 2 is a first flowchart of a node deployment method of OpenStack in an embodiment;
fig. 3 is a second flowchart of the node deployment method of OpenStack in an embodiment;
FIG. 4 is a flow diagram illustrating the sub-steps for step S18 in one embodiment;
fig. 5 is a third flow diagram of a node deployment method of OpenStack in an embodiment;
fig. 6 is a fourth flowchart illustrating a node deployment method of OpenStack in an embodiment;
fig. 7 is a fifth flowchart illustrating a node deployment method of OpenStack in an embodiment;
fig. 8 is a block diagram of a module structure of a node deployment apparatus of OpenStack in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The node deployment method of the OpenStack can be applied to an application environment shown in FIG. 1. The management device 102 may be a computer or a server. When OpenStack installation is performed, the management device 102 may obtain type information of a currently installed node by, but not limited to, inputting a setting manner, so as to determine a type of the currently installed node, for example, the type of the currently installed node is a control node or a compute node. After obtaining the type information of the currently installed node, the management device 102 may further obtain network information of the currently installed node, such as a network mode, a network mechanism, and other relevant network configuration information required when the node is installed, by, but not limited to, inputting a setting. The management device 102 may write the type information and the network information into a configuration file, that is, generate a first type configuration file corresponding to the currently installed node, so that the function calls the type information and the network information therein during the installation process. After the management device 102 generates the first type configuration file corresponding to the currently installed node, according to the first type configuration file, the installation function corresponding to the currently installed node is entered, the network service installation package corresponding to the currently installed node is installed, and the corresponding network plug-in is generated and started to complete installation of the current node.
In an embodiment, as shown in fig. 2, a node deployment method of OpenStack is provided, which is described by taking the method as an example when the method is applied to the management device 102 in fig. 1, and includes the following steps S12 to S18:
and S12, acquiring the type information of the node currently installed by the OpenStack.
The type information is type identification information of each service node on the OpenStack, such as a type parameter or a type variable, and is used for indicating whether a currently installed node is a control node or a compute node.
Specifically, when an OpenStack is installed, each node needs to provide corresponding type information for the node to distinguish the specific type of the node. The type information may be selected and obtained by, but not limited to, an instruction input by a user, or may be read from a preset type table, for example, each type information is sequentially pre-stored on the preset type table according to a sequence, and in the installation process, the type information is sequentially read from the preset type table for each installation node according to the sequence of node installation.
And S14, acquiring the network information of the node according to the type information.
The network information is basic configuration information required by node installation, and is used for ensuring that the node installation does not conflict with the configuration of other nodes and ensuring that corresponding services can be provided normally.
Specifically, in the process of installing the current node, after the type information is acquired, the specific type of the currently installed node is determined. Further, the network information of the node can be obtained according to the type of the node to determine the basic configuration information required when the node is installed. The network information may also be selected by, but not limited to, instructions input by a user, read from a preset type table, or downloaded from a third-party database server according to a preset data link.
And S16, generating a first type configuration file corresponding to the node according to the type information and the network information.
The first type of configuration file is a configuration file corresponding to the node, such as a cfg configuration file, and is used for writing the type information and the network information, so that the node can call required information from the first type of configuration file by a corresponding installation function or module in an installation process.
Specifically, after type information and network information required by the currently installed node are acquired, a first type of configuration file corresponding to the node may be generated according to the type information and the network information, so as to be used in the node installation process.
And S18, according to the first type configuration file and the installation function of the node, installing the network service installation package corresponding to the node, and generating and starting the corresponding network plug-in.
The installation function is an installation function corresponding to each node on the OpenStack and used for calling corresponding configuration information to execute specific installation work of each node. The network service installation package is an installation file package of each network plug-in corresponding to each service required to be provided by the node, and is used for installing each network plug-in of the node when the installation function is called, so that the node can realize support of each service function.
Specifically, after the generation of the first type configuration file of the currently installed node is completed, the installation function of the node is started, and the corresponding information, such as type information and/or network information, in the first type configuration file is called to complete the installation of the network service installation package corresponding to the node. And generating corresponding network plug-ins when the installation is completed, and finally enabling the network plug-ins to realize the support of corresponding services so as to basically complete the installation work of the node.
In the node deployment method of the OpenStack, after the type information of the currently installed node is acquired, the network information of the node is correspondingly acquired. Therefore, the generation of the configuration file and the installation of the network service where the node is located are automatically completed, and finally, the corresponding network plug-in is generated and started, so that the automatic configuration installation of the node is realized. The user intervention degree in the node deployment process is low, the operation is simple and convenient, the effect of greatly improving the deployment efficiency of each node is effectively realized, and the problem of high installation error rate caused by high manual configuration error rate can be solved.
In one embodiment, the network information includes at least network mechanism information, network mode information, IP domain and portal information.
It can be understood that the network information in the foregoing embodiment may include at least the foregoing several kinds of main information, and may further include other configuration information corresponding to other service items that the node needs to provide in the installation process, for example, configuration information corresponding to requirements when some of the extended services are selected according to each service provided by OpenStack, which is not limited in this specification. The network mechanism information is network mechanism identification information of the network service of the OpenStack, for example, setting parameters of the network mechanism and the like. The network mechanism information is used to indicate a network mechanism of a network service corresponding to the currently installed node, for example, to indicate that the current network mechanism is a linux bridge network mechanism or an openvswitch network mechanism.
The network mode information is network mode type information of a network segment where the currently installed node is located, such as network mode parameters, and is used for indicating a network mode to which the network segment where the currently installed node is located belongs. The network mode is, for example, a Flat network mode, a Flat DHCP network mode, a VLAN network mode, or the like. The IP domain can comprise network segment IP addresses which are set by corresponding servers of all nodes and correspond to all network ports so as to ensure network intercommunication in the cloud environment, and network segment IP addresses of all network mode networks established at the control nodes. The network port information is network port parameters between different network segments and is used for distributing corresponding network ports for each network segment. Through the acquisition and the use of the various network information, the correct configuration of each node during installation can be effectively ensured.
In one embodiment, the step S14 may specifically include: and if the node is determined to be the control node according to the type information, receiving the input network information of the node.
It can be understood that, before the network information of the currently installed node is acquired, when it is determined that the node belongs to the control node according to the type information of the node, the network information of the node may be acquired by receiving a manual input from a user. For example, when the node is determined to be a control node, the network information of the node is obtained by receiving each network information input by a user on the installation display interface. By the method, the network information of the currently installed node can be directly set by the user, visual operation is realized, and the operation is convenient.
In one embodiment, the step S14 may specifically include: and if the node is determined to be the control node according to the type information, reading the network information of the node from the preset information table.
The preset information table is a storage table of network information of the nodes, and network information of one or more nodes can be stored according to a set sequence. The preset information table may be stored in a local terminal or a server, or may be stored in a third-party server, such as a proxy server or a cloud, and is used for responding to a network information acquisition request when the node is installed and providing network information corresponding to the node.
It can be understood that, before the network information of the currently installed node is acquired, when the node is determined to belong to the control node according to the type information of the node, the acquisition may be implemented by reading the corresponding network information from the preset information table. For example, when the node is determined to be a control node, the management device 102 accesses the preset information table to read corresponding network information on the preset information table according to the identifier of the node, such as an IP address or a serial number of the node, and allocate the corresponding network information to the node. By the method, the network information of the currently installed node can be directly read, manual setting by a user is not needed, the node deployment efficiency is further improved, and the problem of high installation error rate caused by high manual configuration error rate can be effectively solved.
In one embodiment, the node comprises a control node or a compute node. The step S14 may specifically include: if the node is determined to be a computing node according to the type information, network information of the installed control node is obtained; and matching corresponding network information for the computing node according to the network information of the control node.
It can be understood that, before the network information of the currently installed node is obtained, when it is determined that the node belongs to the computing node according to the type information of the node, for example, if the user selects the type of the node as the computing node on the installation display interface, the selection interface of the network information will not be shown on the installation display interface, but the network information of the first installed control node, such as the network mechanism information, the network mode information, the IP domain and the portal information, etc., is automatically read. And matching corresponding network information for the computing node according to the read network information, for example, configuring the same network mechanism information as the control node for the computing node, reading a management IP address of the control node, and configuring the IP address of the computing node and the network segment as a self management IP address. And configuring network mode information and network port information which are respectively matched with the network mode information and the network port information of the control node for the computing node.
By the matching configuration mode, the network information required by the computing node can be automatically acquired, manual setting by a user is not needed, the consistency between the network information of the computing node and the network information of the control node installed in the previous time is effectively ensured, the node deployment efficiency is further improved, and the problem of high installation error rate caused by high manual configuration error rate is effectively solved.
Referring to fig. 3, in one embodiment, the method further includes step S17:
and S17, sending the file name and the network information of the first type of configuration file to a display for showing.
The display may be a display of the management device 102, or may be an external independent display, and is used to display a configuration interface, so that a user can conveniently obtain or confirm configuration information of the node installation process.
Specifically, after the first type configuration file is generated, the management device 102 may output the file name of the first type configuration file and the selected network information to a display, so that the display is displayed to the user, and the user can conveniently confirm whether the configuration is correct. Thus, through the above step S17, it can be timely found whether there is a problem in the configuration, so as to timely correct the configuration, thereby further reducing the error rate of the node deployment process.
Referring to fig. 4, in one embodiment, the step S18 includes steps S182 to S186:
and S182, starting an installation function of the node according to the type information and the network mechanism information, installing a network service installation package corresponding to the node, and generating a corresponding second-class configuration file and a corresponding network plug-in.
When the second type of configuration file is a network plug-in generated by the node, the configuration files generated correspondingly, such as but not limited to conf configuration file and ini configuration file. The second type of configuration file is generated with normally empty or unusable mismatched configuration content within the file. The second type of configuration file is used for writing configuration information, such as network information, of the network plug-in under the network mechanism to which the node belongs, so that the network plug-in can effectively provide corresponding services after being started.
Specifically, after the generation of the first type configuration file of the currently installed node is completed, a configuration quantization module of the OpenStack may be called, for example, a key module defines the configuration information, that is, the type information and the network information, in the first type configuration file of the node as variables respectively. When the read variable is type information, starting an installation function of the node, for example, when the node is determined to be a control node according to the type information, correspondingly entering the installation function of the control node; and for example, when the node is determined to be a computing node according to the type information, the node correspondingly enters the installation function of the computing node. And determining a network mechanism corresponding to the node according to the network mechanism information, and then installing a network service installation package corresponding to the node by calling an execution module, such as a shell module, of the OpenStack according to the network mechanism. When the installation is completed, a second type configuration file corresponding to the network service of the node and a network plug-in corresponding to the network mechanism, such as but not limited to a network bridge plug-in, a metadata plug-in, a network layer plug-in and a dynamic host configuration protocol related plug-in, are generated.
S184, configuring a second type configuration file according to the network mechanism information;
and S186, starting the network plug-in.
It can be understood that, when the second type configuration file is generated, the second type configuration file is usually empty or invalid, and configuration is required to be performed so that the corresponding network plug-in can take effect. Specifically, the second type of configuration file may be configured by calling a file editing module of the OpenStack, for example, an exit module, to read the network mechanism information. After the configuration of the second type of configuration file is completed, the corresponding network plug-in can be started to enable the corresponding service.
Through the above steps S182 to S186, the network service installation package corresponding to the installation function installation node corresponding to the node may be started according to the acquired first type configuration file. And after the installation is finished, configuring the generated second type configuration file according to the network mechanism information, and finally starting a corresponding network plug-in to start the corresponding service to finish the installation of the node. The installation process is automatically executed, so that the deployment efficiency of the nodes is effectively improved, and the error rate is reduced.
In one embodiment, after step S186, the method further includes the steps of:
and if the node is a control node, establishing a network with a corresponding mode according to the network mode information.
It can be understood that, when the node is installed, if it is determined that the currently installed node is the control node according to the type information, after the installation steps S182 to S186 are completed, the network mode of the node is also determined according to the network mode information in the network information in the first type configuration file, and then a corresponding network is created according to the network mode of the network node, so as to complete network creation of the control node, thereby completing perfect deployment of the control node. Through the steps of network creation, the installation, the perfection and the deployment of the control nodes can be automatically realized, and the installation efficiency is improved.
Referring to fig. 5, in one embodiment, the second type of configuration file includes a network mechanism configuration file corresponding to the network mechanism information. The node deployment method of OpenStack further includes the following steps S20 and S22:
and S20, setting the IP address of the corresponding type for the node according to the IP domain.
It is understood that the corresponding type of IP address is, for example, but not limited to, a management IP address. Each server corresponding to each node needs to manage an IP address and the like. Therefore, in the installation process, the first control node can set its own management IP address when installed, and can read the corresponding configuration information of the first control node when installing other control nodes and computing nodes, so as to analyze and obtain the network segment where the management IP address is located, and configure its own IP address of the same network segment as the management IP address corresponding to the node, so as to ensure the accurate communication and data interaction of the node in the operation process.
And S22, binding the network mechanism configuration file according to the network mechanism information.
It can be understood that when data interaction is performed between different network segments, matching network port information needs to be provided. Therefore, in the installation process, the network port information can be bound to the network mechanism configuration file corresponding to the network mechanism information, so that when the node installation is completed, the corresponding network port information can be correspondingly obtained, and the effective realization of network bridge linkage and the like in the node operation process is ensured.
In the above embodiment, the binding between the IP address and the portal information may be implemented through manual configuration by the user. In this embodiment, through the steps S20 and S22, in the node installation process, the allocation of the IP address and the binding of the portal information are automatically completed, so as to further improve the node deployment efficiency and reduce the configuration error rate.
Referring to fig. 6, in an embodiment, the node deployment method of OpenStack further includes steps S19 and S21:
s19, installing a database of the node, and reading the network information in the first type of configuration file;
and S191, respectively storing the network information and the type information into corresponding storage tables in a database.
It can be understood that, in the installation process, before starting the installation function of the node, the environment basic configuration needs to be completed, for example, the database installation corresponding to the node. Therefore, the database of the current node is installed through the above step S19, and the network information in the first type configuration file, such as the network mechanism information, the network mode information, the IP domain and the portal information, is read. Further, in step S21, the read network information and the type information are stored in the database. Specifically, after the database is installed, corresponding storage tables, such as, but not limited to, a network mechanism table, a portal information table, and an IP address table, may be respectively created in the database, so as to respectively store each network information into the corresponding storage table.
Through the steps S19 and S191, the preparation step before starting the installation function can be reliably completed, so that when the network service installation package corresponding to the node is installed, the shell module of the OpenStack can quickly execute the operation of the database command, complete the installation of the network service installation package, and improve the installation and deployment efficiency.
Referring to fig. 7, in an embodiment, the above node deployment method of OpenStack further includes step S24:
and S24, starting a verification function of the OpenStack, and installing and verifying the network plug-in corresponding to the network service of the OpenStack.
It can be understood that after the installation of each node is completed, the authentication function of the OpenStack is automatically entered, and the network service of the OpenStack is started to be authenticated, that is, the corresponding network plug-in is authenticated, and whether the installation is successfully authenticated or not is verified. For example, the verification work of the network service is completed by calling the command function and the assertion function (assert) of the authentication module (keystone) and the command result parsing module (OpenStack _ output) of OpenStack. Specifically, for two different network mechanisms, namely Linux bridge agent and openvswitch agent plugins are generated and other network plugins such as Metadata agent, L3agent and DHCP agent are generated after installation and deployment of each node are completed, so that whether installation is successful or not can be determined by verifying whether the corresponding plugins can be found.
Through the step S24, after the node installation and deployment are completed, installation verification may be performed to obtain a corresponding installation result, which is convenient for a user to perform corresponding perfection processing according to the installation result, and improves the reliability of the network service of the OpenStack.
It should be understood that although the various steps in the flow charts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-7 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 8, there is provided an OpenStack node deployment apparatus 100, including: a type acquisition module 12, a network acquisition module 14, a configuration module 16, and a network installation module 18, wherein: a type obtaining module 12, configured to obtain type information of a node currently installed in OpenStack. And a network obtaining module 14, configured to obtain the network information of the node according to the type information. And the configuration module 16 is configured to generate a first type configuration file corresponding to the node according to the type information and the network information. And the network installation module 18 is configured to install the network service installation package corresponding to the node according to the first class configuration file and the installation function of the node, and generate and enable a corresponding network plugin.
The node deployment device 100 of OpenStack acquires the type information of the currently installed node, and then correspondingly acquires the network information of the node. Therefore, the generation of the configuration file and the installation of the network service where the node is located are automatically completed, and finally, the corresponding network plug-in is generated and started, so that the automatic configuration installation of the node is realized. The user intervention degree in the node deployment process is low, the operation is simple and convenient, the effect of greatly improving the deployment efficiency of each node is effectively realized, and the problem of high installation error rate caused by high manual configuration error rate can be solved.
In one embodiment, the network installation module 18 may specifically include an installation execution sub-module, a configuration sub-module, and a plug-in start sub-module. The installation execution submodule is used for starting an installation function of the node according to the type information and the network mechanism information, installing a network service installation package corresponding to the node, and generating a corresponding second type configuration file and a corresponding network plug-in. And the configuration submodule is used for configuring the second type of configuration files according to the network mechanism information. And the plug-in starting submodule is used for starting the network plug-in.
In one embodiment, the node deployment apparatus 100 of OpenStack further includes a network creation module, configured to create a network of a corresponding mode according to the network mode information when the node is a control node.
In one embodiment, the node deployment apparatus 100 of OpenStack further includes an IP setting module and a portal binding module. The IP setting module is used for setting IP addresses of corresponding types according to the IP domain. And the network port binding module is used for binding the network port information of the network mechanism configuration file according to the network mechanism information.
In one embodiment, the node deployment apparatus 100 of OpenStack further includes an installation verification module, configured to start a verification function of OpenStack, and perform installation verification on a network plug corresponding to a network service of OpenStack.
In one embodiment, the node deployment apparatus 100 of OpenStack further includes a database installation module and a data storage module. The database installation module is used for installing a database of the node and reading the network information in the first type of configuration file. The data storage module is used for respectively storing the network information and the type information into corresponding storage tables in the database.
In one embodiment, the node deployment apparatus 100 of OpenStack further includes a display processing module, configured to send the file name and the network information of the first type of configuration file to a display for displaying.
In one implementation, the network obtaining module 14 may specifically include a first information submodule, configured to receive the input network information of the node when the node is determined to be the control node according to the type information.
In one implementation, the network obtaining module 14 may further include a second information submodule, configured to read the network information of the node from the preset information table if the node is determined to be the control node according to the type information.
In one implementation, the network obtaining module 14 may further include a third information sub-module and an information matching module. And the third information submodule is used for acquiring the network information of the installed control node if the node is determined to be a computing node according to the type information. And the information matching module is used for matching corresponding network information for the computing node according to the network information of the control node.
For specific limitations of the OpenStack node deployment apparatus 100, reference may be made to the above limitations of the OpenStack node deployment method in each corresponding embodiment, and details are not described here again. The modules in the node deployment apparatus 100 of OpenStack described above may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a node deployment method of OpenStack. The display screen of the computer device may be, but is not limited to, a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covered on the display screen, a key, a trackball or a touch pad arranged on a casing of the computer device, or an external keyboard, a touch pad or a mouse, etc.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: obtaining type information of a node currently installed by OpenStack; acquiring network information of the node according to the type information; generating a first type configuration file corresponding to the node according to the type information and the network information; and according to the first type of configuration files and the installation function of the nodes, installing the network service installation package corresponding to the nodes, and generating and starting the corresponding network plug-in.
In one embodiment, the steps of the node deployment method of OpenStack in the above embodiments may also be implemented when the processor executes the computer program.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: obtaining type information of a node currently installed by OpenStack; acquiring network information of the node according to the type information; generating a first type configuration file corresponding to the node according to the type information and the network information; and according to the first type of configuration files and the installation function of the nodes, installing the network service installation package corresponding to the nodes, and generating and starting the corresponding network plug-in.
In one embodiment, the computer program, when executed by the processor, may further implement the steps of the node deployment method of OpenStack in the above embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (22)
1. A node deployment method of OpenStack is characterized by comprising the following steps:
obtaining type information of a node currently installed by OpenStack;
acquiring network information of the node according to the type information;
generating a first type configuration file corresponding to the node according to the type information and the network information;
according to the first type configuration file and the installation function of the node, installing a network service installation package corresponding to the node, and generating and starting a corresponding network plug-in;
the method further comprises the following steps:
installing a database of the node, and reading the network information in the first type configuration file;
and respectively storing the network information and the type information into corresponding storage tables in the database.
2. The OpenStack node deployment method according to claim 1, wherein the network information at least comprises network mechanism information, network mode information, IP domain and portal information.
3. The OpenStack node deployment method according to claim 2, wherein the step of installing the network service installation package corresponding to the node according to the first class configuration file and the installation function of the node, and generating and enabling a corresponding network plug-in includes:
starting the installation function of the node according to the type information and the network mechanism information, installing the network service installation package corresponding to the node, and generating a corresponding second type configuration file and the network plug-in;
configuring the second type configuration file according to the network mechanism information;
and starting the network plug-in.
4. The OpenStack node deployment method according to claim 3, wherein the step of starting the network plug-in further comprises:
and if the node is a control node, establishing a network with a corresponding mode according to the network mode information.
5. The OpenStack node deployment method according to claim 3 or 4, wherein the second type of configuration file comprises a network mechanism configuration file corresponding to the network mechanism information;
the method further comprises the following steps:
setting an IP address of a corresponding type for the node according to the IP domain;
and binding the network interface information of the network mechanism configuration file according to the network mechanism information.
6. The OpenStack node deployment method of claim 5, wherein the method further comprises:
and starting a verification function of the OpenStack, and installing and verifying the network plug-in corresponding to the network service of the OpenStack.
7. The OpenStack node deployment method of claim 1, further comprising:
and sending the file name of the first type configuration file and the network information to a display for displaying.
8. The OpenStack node deployment method according to claim 1, wherein the step of obtaining the network information of the node according to the type information includes:
and if the node is determined to be a control node according to the type information, receiving the input network information of the node.
9. The OpenStack node deployment method according to claim 1, wherein the step of obtaining the network information of the node according to the type information includes:
and if the node is determined to be a control node according to the type information, reading the network information of the node from a preset information table.
10. The OpenStack node deployment method of claim 1, wherein the node comprises a control node or a compute node;
the step of obtaining the network information of the node according to the type information includes:
if the node is determined to be a computing node according to the type information, network information of the installed control node is obtained;
and matching the corresponding network information for the computing node according to the network information of the control node.
11. An OpenStack node deployment device, comprising:
the type acquisition module is used for acquiring the type information of the node currently installed by the OpenStack;
the network acquisition module is used for acquiring the network information of the node according to the type information;
the configuration module is used for generating a first type of configuration file corresponding to the node according to the type information and the network information;
the network installation module is used for installing a network service installation package corresponding to the node according to the first type configuration file and the installation function of the node, and generating and starting a corresponding network plug-in;
the device further comprises:
the database installation module is used for installing a database of the node and reading the network information in the first type of configuration file;
and the data storage module is used for respectively storing the network information and the type information into corresponding storage tables in the database.
12. The OpenStack node deployment device of claim 11, wherein the network information at least comprises network mechanism information, network mode information, IP domain, and portal information.
13. The OpenStack node deployment apparatus of claim 12, further comprising:
the installation execution submodule is used for starting the installation function of the node according to the type information and the network mechanism information, installing the network service installation package corresponding to the node and generating a corresponding second type configuration file and the network plug-in;
the configuration module is used for configuring the second type of configuration files according to the network mechanism information;
and the plug-in starting sub-module is used for starting the network plug-in.
14. The OpenStack node deployment device of claim 13, further comprising:
and the network creating module is used for creating a network with a corresponding mode according to the network mode information if the node is a control node.
15. The OpenStack node deployment device according to claim 13 or 14, wherein the second type of configuration file includes a network mechanism configuration file corresponding to the network mechanism information;
the device further comprises:
the IP setting module is used for setting IP addresses of corresponding types for the nodes according to the IP domain;
and the network port binding module is used for binding the network port information of the network mechanism configuration file according to the network mechanism information.
16. The OpenStack node deployment apparatus of claim 15, wherein the apparatus further comprises:
and the installation verification module is used for starting a verification function of the OpenStack and performing installation verification on the network plug-in corresponding to the network service of the OpenStack.
17. The OpenStack node deployment apparatus of claim 11, wherein the apparatus further comprises:
and the display processing module is used for sending the file name of the first type of configuration file and the network information to a display for displaying.
18. The OpenStack node deployment device of claim 11, wherein the network acquisition module comprises:
and the first information submodule is used for receiving the input network information of the node if the node is determined to be a control node according to the type information.
19. The OpenStack node deployment device of claim 11, wherein the network acquisition module comprises:
and the second information submodule is used for reading the network information of the node from a preset information table if the node is determined to be a control node according to the type information.
20. The OpenStack node deployment apparatus of claim 11, wherein the node comprises a control node or a compute node;
the network acquisition module comprises:
the third information submodule is used for acquiring the network information of the installed control node if the node is determined to be a computing node according to the type information;
and the information matching module is used for matching the corresponding network information for the computing node according to the network information of the control node.
21. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program implements the steps of the node deployment method of OpenStack of any of claims 1 to 10.
22. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the OpenStack node deployment method of any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811133228.2A CN109039784B (en) | 2018-09-27 | 2018-09-27 | Node deployment method and device of OpenStack |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811133228.2A CN109039784B (en) | 2018-09-27 | 2018-09-27 | Node deployment method and device of OpenStack |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109039784A CN109039784A (en) | 2018-12-18 |
| CN109039784B true CN109039784B (en) | 2021-05-28 |
Family
ID=64614758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811133228.2A Active CN109039784B (en) | 2018-09-27 | 2018-09-27 | Node deployment method and device of OpenStack |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109039784B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109889377B (en) * | 2019-01-29 | 2022-03-25 | 京信网络系统股份有限公司 | Method and device for deploying VNF in NFV system based on Openstack |
| CN111400107B (en) * | 2020-04-21 | 2023-03-03 | 贵州新致普惠信息技术有限公司 | Self-starting recovery system and method for database multi-master cluster |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580519A (en) * | 2015-01-29 | 2015-04-29 | 福建师范大学福清分校 | Method for rapid deployment of openstack cloud computing platform |
| CN104754032A (en) * | 2015-02-27 | 2015-07-01 | 浪潮集团有限公司 | Method and device for deploying OpenStack |
| CN106506636A (en) * | 2016-11-04 | 2017-03-15 | 武汉噢易云计算股份有限公司 | A kind of cloud platform cluster method and system based on OpenStack |
| CN106533753A (en) * | 2016-11-07 | 2017-03-22 | 广州视源电子科技股份有限公司 | Role configuration method and device of distributed system |
| CN107483243A (en) * | 2017-08-09 | 2017-12-15 | 鹤云来科技有限公司 | A kind of automatic deployment method and equipment of OpenStack platforms |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9906401B1 (en) * | 2016-11-22 | 2018-02-27 | Gigamon Inc. | Network visibility appliances for cloud computing architectures |
-
2018
- 2018-09-27 CN CN201811133228.2A patent/CN109039784B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580519A (en) * | 2015-01-29 | 2015-04-29 | 福建师范大学福清分校 | Method for rapid deployment of openstack cloud computing platform |
| CN104754032A (en) * | 2015-02-27 | 2015-07-01 | 浪潮集团有限公司 | Method and device for deploying OpenStack |
| CN106506636A (en) * | 2016-11-04 | 2017-03-15 | 武汉噢易云计算股份有限公司 | A kind of cloud platform cluster method and system based on OpenStack |
| CN106533753A (en) * | 2016-11-07 | 2017-03-22 | 广州视源电子科技股份有限公司 | Role configuration method and device of distributed system |
| CN107483243A (en) * | 2017-08-09 | 2017-12-15 | 鹤云来科技有限公司 | A kind of automatic deployment method and equipment of OpenStack platforms |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109039784A (en) | 2018-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11296957B2 (en) | Network slice management method, unit, and system | |
| US12035416B2 (en) | ESIM card change method and related device | |
| CN107896162B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| WO2016015558A1 (en) | Method and apparatus for applying for license | |
| CN109460527A (en) | Product data configuration method, device, computer equipment and storage medium | |
| CN109889377B (en) | Method and device for deploying VNF in NFV system based on Openstack | |
| CN110933189A (en) | Fabric-based block chain network deployment method, device, equipment and medium | |
| CN110008665B (en) | Authority control method and device for blockchain | |
| WO2021164462A1 (en) | Data encryption method, data decryption method, computer device, and medium | |
| CN110764788B (en) | Cloud storage deployment method and device, computer equipment and readable storage medium | |
| CN110266761B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| CN109299010A (en) | Mock test method, device, computer equipment and storage medium | |
| CN111414391A (en) | Method and system for accessing multiple data sources | |
| CN108959384B (en) | Webpage data acquisition method and device, computer equipment and storage medium | |
| CN109039784B (en) | Node deployment method and device of OpenStack | |
| EP3687112A1 (en) | Communication method and communication device | |
| CN110969354A (en) | Linear flow configuration method and device, computer equipment and storage medium | |
| CN117453240A (en) | RAID configuration method, device, equipment and medium of bare metal server | |
| CN116541085B (en) | Android/Linux fusion method, device, equipment and storage medium | |
| CN112559352A (en) | Interface test method, device, equipment and storage medium | |
| CN112099902A (en) | Network adapter configuration method and device of virtual machine, electronic device and storage medium | |
| CN116225617A (en) | Management migration method and device for container instance, electronic equipment and storage medium | |
| CN109587013A (en) | APP network compatibility test method, device, computer equipment and storage medium | |
| CN114615285A (en) | Physical machine deployment method and device, electronic equipment and storage medium | |
| CN113918423A (en) | Cloud platform monitoring method and device and application thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200110 Address after: 510663 Shenzhou Road, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangdong, 10 Applicant after: Jingxin Communication System (China) Co., Ltd. Address before: 510663 Shenzhou Road 10, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangzhou, Guangdong Applicant before: Jingxin Communication System (China) Co., Ltd. Applicant before: Jingxin Communication System (Guangzhou) Co., Ltd. Applicant before: Jingxin Communication Technology (Guangzhou) Co., Ltd. Applicant before: TIANJIN COMBA TELECOM SYSTEMS CO., LTD. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 510663 Shenzhou Road, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangdong, 10 Patentee after: Jingxin Network System Co.,Ltd. Address before: 510663 Shenzhou Road, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangdong, 10 Patentee before: Comba Telecom System (China) Ltd. |