CN109495298B - Method and device for managing nodes in OpenStack system - Google Patents
Method and device for managing nodes in OpenStack system Download PDFInfo
- Publication number
- CN109495298B CN109495298B CN201811313509.6A CN201811313509A CN109495298B CN 109495298 B CN109495298 B CN 109495298B CN 201811313509 A CN201811313509 A CN 201811313509A CN 109495298 B CN109495298 B CN 109495298B
- Authority
- CN
- China
- Prior art keywords
- node
- data
- file
- openstack
- configuration
- 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
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000009434 installation Methods 0.000 claims abstract description 63
- 238000013515 script Methods 0.000 claims description 20
- 239000002184 metal Substances 0.000 claims description 6
- 230000008569 process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 241000883510 Kolla Species 0.000 description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000002347 injection Methods 0.000 description 2
- 239000007924 injection Substances 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- RZVAJINKPMORJF-UHFFFAOYSA-N Acetaminophen Chemical compound CC(=O)NC1=CC=C(O)C=C1 RZVAJINKPMORJF-UHFFFAOYSA-N 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000011176 pooling Methods 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- 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
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The invention discloses a method and a device for managing nodes in an OpenStack system. The method comprises the following steps: acquiring nodes required to be deployed in the OpenStack system; configuring operation data for the node, wherein the operation data comprises network configuration data and/or mirror image data of an application program; storing the operation data into a preset storage path of the node; and sending an automatic operation installation package, wherein the automatic operation installation package is used for calling the data on the storage path and executing installation operation on the data.
Description
Technical Field
The present invention relates to the field of information processing, and in particular, to a method and an apparatus for managing nodes in an OpenStack system.
Background
Cloud Computing (Cloud Computing) is an increasing, usage and delivery model of internet-based related services, typically involving the provision of dynamically scalable and often virtualized resources over the internet. Cloud is a metaphor of network and internet. In the past, telecommunications networks were often represented by clouds and later also by the abstraction of the internet and the underlying infrastructure. Therefore, cloud computing can enable you to experience even 10 trillion times per second computing power, and the powerful computing power can simulate nuclear explosion, forecast climate change and market development trend. A user accesses the data center through a computer, a notebook, a mobile phone and the like and operates according to the own requirements. The cloud computing realizes the pooling of hardware resources, provides the computing resources, the storage resources and the network resources to the user in a resource pool mode, and provides the user with the resource integration in a virtual machine mode. OpenStack has found wide application as a de facto standard for cloud computing.
OpenStack has been a difficult problem to deploy as a distributed system with numerous components. The Kolla project utilizes Docker, Docker-Complex, Ansible to accomplish the deployment of OpenStack. Currently Kolla has completed the deployment of an all-in-one and multinode development environment. Kolla mainly utilizes the isolation of Docker containers to achieve atomic upgrade and rollback on upgrade of OpenStack. The whole upgrading and returning process is easier to control the influence range, and the operation and maintenance complexity of the whole OpenStack is reduced. However, the deployment mode has no graphical deployment system and still has great optimization and promotion space.
Ironic is bare computer service of OpenStack and can implement installation operation for bare computers; the method can be independently deployed and can also be used in an integrated manner with other projects of OpenStack, and a client can install the selected system image template to a specified bare computer like creating a virtual machine.
The Config Drive is used as a metadata injection mode, and data specified by a user can be injected into a virtual machine or a bare machine; the Cloud-init uses the Config Drive as the Data Source to perform initialization configuration on the virtual machine or the bare machine or execute a series of scripts.
At present, node deployment work of an OpenStack system is complex, and how to simplify a deployment process is an urgent problem to be solved.
Disclosure of Invention
In order to solve the technical problem, the invention provides a method and a device for managing nodes in an OpenStack system, which can simplify the node deployment process of the OpenStack system.
In order to achieve the object of the present invention, the present invention provides a method for managing nodes in an OpenStack system, including:
acquiring nodes required to be deployed in the OpenStack system;
configuring operation data for the node, wherein the operation data comprises network configuration data and/or mirror image data of an application program;
storing the operation data into a preset storage path of the node;
and sending an automatic operation installation package, wherein the automatic operation installation package is used for calling the data on the storage path and executing installation operation on the data.
In an exemplary embodiment of the present invention, the configuring operation data for the node includes:
acquiring information of a network and a subnet in the OpenStack system;
and determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
In an exemplary embodiment of the present invention, after the sending the auto-run installation package, the method further includes:
after informing the node to execute the network configuration operation, inquiring whether the node is in a normal network connection state;
and if the information which is fed back by the node and is in a normal network connection state is received, the node is informed to clear the running program and/or the automatic running installation package stored by the node.
In an exemplary embodiment provided by the present invention, after querying whether the node is in a normal network connection state, the method further includes:
if the information which is fed back by the node and is in the normal network connection state is not received, whether the node is in the normal network connection state or not is inquired again according to a preset time interval;
and if the information which is fed back by the node and is in the normal network connection state is not received and the record which is not inquired reaches a preset time threshold value, the node is informed of clearing the running program and/or the automatic running installation package stored by the node.
In an exemplary embodiment provided by the present invention, after the method that the information in the normal network connection state fed back by the node is not received and the unexplored record reaches the preset threshold number of times, the method further includes:
and re-issuing the running program and/or the automatic running installation package corresponding to the node, and controlling the node to execute installation operation.
In order to achieve the object of the present invention, the present invention provides an apparatus for managing nodes in an OpenStack system, including:
the obtaining module is used for obtaining nodes needing to be deployed in the OpenStack system;
the configuration module is used for configuring operation data for the node, wherein the operation data comprises network configuration data and/or mirror image data of an application program;
the storage module is used for storing the operation data into a preset storage path of the node;
and the first sending module is used for sending an automatic operation installation package, wherein the automatic operation installation package is used for calling the data on the storage path and executing installation operation on the data.
In an exemplary embodiment provided by the present invention, the configuration module includes:
the obtaining unit is used for obtaining the information of the network and the subnet in the OpenStack system;
and the determining unit is used for determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
In an exemplary embodiment provided by the present invention, the apparatus further comprises:
the query module is used for querying whether the node is in a normal network connection state or not after informing the node to execute the network configuration operation;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is received.
In an exemplary embodiment provided by the present invention, the apparatus further comprises:
the query module is further configured to, after querying whether the node is in a normal network connection state, if the information that is fed back by the node and is in the normal network connection state is not received, query again whether the node is in the normal network connection state according to a preset time interval;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is not received and the unexplored record reaches a preset time threshold value.
In an exemplary embodiment provided by the present invention, the apparatus further comprises:
and the management module is used for retransmitting the running program and/or the automatic running installation package corresponding to the node and controlling the node to execute installation operation after the information which is fed back by the node and is in a normal network connection state and the unexplored record reaches a preset time threshold device.
According to the embodiment provided by the invention, the nodes required to be deployed in the OpenStack system are obtained, the running data is configured for the nodes, wherein the running data comprises network configuration data and/or mirror image data of an application program, the running data is stored into the preset storage path of the nodes, and the automatic running installation package is sent, wherein the automatic running installation package is used for calling the data on the storage path and executing installation operation on the data, so that the difficulty of OpenStack deployment under a physical machine is simplified, the deployment time is shortened, the deployment threshold is reduced, the implementation pressure is reduced, and the expansion of OpenStack is accelerated.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
Fig. 1 is a flowchart of a method for managing nodes in an OpenStack system according to the present invention;
fig. 2 is a schematic structural diagram of a deployment system of an OpenStack system provided in the present invention;
fig. 3 is a flowchart of a deployment method of an OpenStack system provided in the present invention;
fig. 4 is a structural diagram of an apparatus for managing nodes in an OpenStack system according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
Fig. 1 is a flowchart of a method for managing nodes in an OpenStack system according to the present invention. The method shown in fig. 1 comprises:
and 104, sending an automatic operation installation package, wherein the automatic operation installation package is used for calling the data on the storage path and executing installation operation on the data.
According to the method embodiment provided by the invention, the nodes required to be deployed in the OpenStack system are obtained, the running data is configured for the nodes, wherein the running data comprises network configuration data and/or mirror image data of an application program, the running data is stored into the preset storage path of the nodes, and the automatic running installation package is sent, wherein the automatic running installation package is used for calling the data on the storage path and executing installation operation on the data, so that the difficulty of OpenStack deployment under a physical machine is simplified, the deployment time is shortened, the deployment threshold is reduced, the implementation pressure is reduced, and the expansion of OpenStack is accelerated.
The method provided by the present invention is further illustrated below:
in an exemplary embodiment, the configuring the operation data for the node includes:
acquiring information of a network and a subnet in the OpenStack system;
and determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
In this exemplary embodiment, information of a network and a subnet in the OpenStack system is collected, a network environment corresponding to the deployment location of the node is determined, and corresponding network configuration data is configured for the node according to the network environment.
In an exemplary embodiment, after the sending the autorun installation package, the method further comprises:
after informing the node to execute the network configuration operation, inquiring whether the node is in a normal network connection state;
and if the information which is fed back by the node and is in the normal network connection state is received, the node is informed to clear the running program and/or the automatic running installation package stored by the node.
In the exemplary embodiment, whether the deployed node has completed deployment work is determined by detecting whether the deployed node can feed back connection information through the network, and after the deployment work is determined to be completed, data in the deployment process is deleted, so that reasonable utilization of storage space in the node is ensured.
In an exemplary embodiment, after said querying whether the node is in a normal network connection state, the method further comprises:
if the information which is fed back by the node and is in the normal network connection state is not received, whether the node is in the normal network connection state or not is inquired again according to a preset time interval;
and if the information which is fed back by the node and is in the normal network connection state is not received and the record which is not inquired reaches a preset time threshold value, the node is informed of clearing the running program and/or the automatic running installation package stored by the node.
In the exemplary embodiment, if the node attempts to deploy the work several times continuously without success, the node may perform a data clearing operation to stop the deployment work, thereby reducing waste of system resources caused by several attempts.
In an exemplary embodiment, after the information in the normal network connection state fed back by the node is not received and the record that is not queried reaches the preset number threshold method, the method further includes:
and re-issuing the running program and/or the automatic running installation package corresponding to the node, and controlling the node to execute installation operation.
In this exemplary embodiment, if the node attempts to perform the deployment operation continuously and repeatedly without success, the data required for the deployment may be reissued for the node, and the node is controlled to perform the deployment operation by using the new data, so as to improve the success rate of the deployment operation.
The following examples of applications provided by the present invention are further illustrated:
the application example of the invention provides an OpenStack graphical one-key deployment method based on an Ironic installation, and the method realizes physical installation based on the Ironic, kolla, closed-init and deployment foot; wherein:
the OpenStack is deployed in a Kolla-allowed command line mode and is required to be installed for each node; configuring each node for mutual trust; yml files and multinode files of deployment nodes are configured to achieve the purposes of configuring VIPs, selecting components to be deployed, configuring roles of each node and the like.
Fig. 2 is a schematic structural diagram of a deployment system of the OpenStack system provided by the present invention. In the system shown in fig. 2:
graphically selecting OpenStack nodes and roles, and graphically setting a vip interface; a method and a process for correctly deploying OpenStack according to graphical configuration are designed: generating a configuration file for the deployment according to the interface configuration, the template file global.yml and the multimode; generating a deployment startup script (default. py) and hosts files of startup self-running; when the nova creates the virtual machine, a config-drive is started, the configuration file and the script are injected into each bare machine and placed into a corresponding position, the deployment node deployment script detects whether each node is ready, and a koll-dependent deployment-i/root/multinode command is executed to execute deployment operation after the node deployment script is ready. Graphical one-key deployment of Ironic-based OpenStack is implemented.
The interaction steps of the deployment service and the OpenStack component are as follows:
1) and calling an Ironic API to acquire an Ironic bare engine node for selecting a node to be deployed with an OpenStack environment.
2) And calling a Neutron API to acquire a network and a subnet for creating the network parameters of the bare metal instance.
3) And calling a Glance API to acquire a mirror list used as a mirror parameter for creating the bare metal instance.
4) Invoking the Nova API creates a bare metal instance to deploy OpenStack. And appointing to start a Config Drive, and generating files of OpenStack nodes, role configuration, global configuration, component service configuration and deployment scripts acquired by the page as parameters when the nova create server is called.
5) Nova calls the Ironic api to perform bare computer system deployment through Nova Ironic virtual driver, performs installation operation on Openstack nodes, and injects a config drive file system as a single partition.
Through page configuration, the deployment service generates a configuration file through configuration, injects the configuration file into a bare engine through a config drive, and performs an architecture of OpenStack deployment through a deployment script.
And running a deployment script after the deployment nodes are completed, reading/etc/hosts files by the deployment script and ping each node to judge whether the installation of each node is finished. Three deployment procedures were attempted after completion.
The name and the vip of the Openstack environment can be configured, and Openstack nodes are selected from available nodes in an Ironic bare engine list and designated in roles; whether each component is started or not is configured through a switch.
The specific deployment process and mode are as follows:
1) uploading an OpenStack bare machine image containing the close-init to the blance;
2) registering the bare computer node with the BMC into Ironic;
3) nova profile allows file injection;
4) and selecting a page to deploy OpenStack, and entering an OpenStack environment configuration interface: filling in an environment name;
5) entering a node configuration page: selecting a bare computer with an available Ironic, designating roles, selecting a node as a deployment node, filling in a host name of each node, selecting a provider network and designating an IP address;
6) enter component configuration page: whether each component service is started or not is selected; whether haproxy is opened or not is selected, vip is appointed, and clicking is carried out.
The front end calls a Rest Api exposed by the deployment Service to Deploy OpenStack, and the deployment Service generates a temporary configuration file from parameters transmitted from the front end: yml, multimode, hosts, deploy.sh; wherein:
yml contains global configuration, vip information and component opening configuration data of the OpenStack environment;
the multimode is an arbitrary configuration file inventory file;
the hosts file designates ip and the hosts file of the user name for each node of the OpenStack environment;
sh is a script which is injected into a bare metal selected as a deployment node by a user and is self-started for the first time, and is used for deployment.
And after the temporary configuration file is generated by the deployment service, sequentially calling nova api to designate a bare engine selected by a user to create a bare engine instance, designating ip set by the user, and injecting all four files to a corresponding directory by a deployment node and injecting other three files except the deployment service.
After each bare computer node is installed, acquiring an ip address specified by a user, and injecting a user name and three configuration files into a corresponding directory through a config drive and a closed init; starting Openstack deployment by deployment node deployment start, wherein the deployment process is as follows:
fig. 3 is a flowchart of a deployment method of an OpenStack system provided in the present invention. The script flow for deployment shown in FIG. 3 is as follows:
1. reading/etc/hosts files of the deployed nodes, and analyzing and obtaining a list of ip information of each node of the OpenStack environment deployed at this time.
2. Sequentially ping all the hosts, and entering the next step if all the hosts are communicated flatly; if not, sleep again for 60 seconds.
3. Run kolla-allowed deployment-i/root/multimode for deployment.
4. Judging whether the deployment is successful or not, and if so, finishing; if the failure is detected, judging whether the failure frequency exceeds 3 times, if so, ending; if not, the next step is carried out.
5. Run kolla-allowed chemistry-i/root/multimode to clear the environment, go to step 3 again.
The method provided by the application example of the invention designs one-key deployment of graphical configuration from page configuration to Ironic installation to script deployment environment by kolla-ansable based on the bare computer service of the Ironic, simplifies the difficulty of OpenStack deployment under a physical computer, shortens the deployment time, reduces the deployment threshold, reduces the implementation pressure and accelerates the expansion of the OpenStack.
Fig. 4 is a structural diagram of an apparatus for managing nodes in an OpenStack system according to the present invention. The apparatus shown in fig. 4 comprises:
an obtaining module 401, configured to obtain a node to be deployed in an OpenStack system;
a configuration module 402, configured to configure operation data for the node, where the operation data includes network configuration data and/or mirror data of an application;
a storage module 403, configured to store the operation data in a preset storage path of the node;
a first sending module 404, configured to send an automatic execution installation package, where the automatic execution installation package is used to call data on the storage path and perform an installation operation on the data.
In an exemplary embodiment, the configuration module 402 includes:
the obtaining unit is used for obtaining the information of the network and the subnet in the OpenStack system;
and the determining unit is used for determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
In one exemplary embodiment, the apparatus further comprises:
the query module is used for querying whether the node is in a normal network connection state or not after informing the node to execute the network configuration operation;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is received.
In one exemplary embodiment, the apparatus further comprises:
the query module is further configured to, after querying whether the node is in a normal network connection state, if the information that is fed back by the node and is in the normal network connection state is not received, query again whether the node is in the normal network connection state according to a preset time interval;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is not received and the unexplored record reaches a preset time threshold value.
In one exemplary embodiment, the apparatus further comprises:
and the management module is used for retransmitting the running program and/or the automatic running installation package corresponding to the node and controlling the node to execute installation operation after the information which is fed back by the node and is in a normal network connection state and the unexplored record reaches a preset time threshold device.
The device embodiment provided by the invention is used for acquiring the nodes needing to be deployed in the OpenStack system, configuring the running data for the nodes, wherein the running data comprises network configuration data and/or mirror image data of an application program, storing the running data into the preset storage path of the nodes, and sending the automatic running installation package, wherein the automatic running installation package is used for calling the data on the storage path and executing installation operation on the data, so that the difficulty of OpenStack deployment under a physical machine is simplified, the deployment time is shortened, the deployment threshold is reduced, the implementation pressure is reduced, and the expansion of OpenStack is accelerated.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Claims (10)
1. A method for managing nodes in an OpenStack system is characterized by comprising the following steps:
acquiring nodes required to be deployed in the OpenStack system;
configuring operation data for the node, wherein the operation data comprises network configuration data and/or mirror image data of an application program, and the method comprises the following steps: recording a method and a flow for correctly deploying OpenStack by using a graphical interface, and generating a configuration file of the deployment according to the graphical interface and a template file, wherein the configuration file comprises a global.yml file, a multimode file, a startup self-running deployment. py script and a hosts file;
storing the operation data into a preset storage path of the node;
sending an automatic operation installation package, wherein the automatic operation installation package is used for calling data on the storage path and executing installation operation on the data;
after the script is started and operated, taking data in the global.yml file as a configuration parameter, and when the script detects that a bare engine node is ready, operating a multimode file; wherein:
yml files comprise global configuration, vip information and component opening configuration data of the OpenStack environment;
the deployment script is used for detecting whether each bare metal node is ready;
the hosts file records the designated ip and user name of each node in the OpenStack environment;
the multimode file includes an allowed configuration file and an inventory file.
2. The method of claim 1, wherein configuring operational data for the node comprises:
acquiring information of a network and a subnet in the OpenStack system;
and determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
3. The method of claim 1 or 2, wherein after sending the autorun installation package, the method further comprises:
after informing the node to execute the network configuration operation, inquiring whether the node is in a normal network connection state;
and if the information which is fed back by the node and is in a normal network connection state is received, the node is informed to clear the running program and/or the automatic running installation package stored by the node.
4. The method of claim 3, wherein after querying whether the node is in a normal network connection state, the method further comprises:
if the information which is fed back by the node and is in the normal network connection state is not received, whether the node is in the normal network connection state or not is inquired again according to a preset time interval;
and if the information which is fed back by the node and is in the normal network connection state is not received and the record which is not inquired reaches a preset time threshold value, the node is informed of clearing the running program and/or the automatic running installation package stored by the node.
5. The method according to claim 4, wherein after the information in the normal network connection state fed back by the node is not received and the record of non-inquiry reaches a preset number threshold method, the method further comprises:
and re-issuing the running program and/or the automatic running installation package corresponding to the node, and controlling the node to execute installation operation.
6. An apparatus for managing nodes in an OpenStack system, comprising:
the obtaining module is used for obtaining nodes needing to be deployed in the OpenStack system;
a configuration module, configured to configure operation data for the node, where the operation data includes network configuration data and/or mirror image data of an application program, and the configuration module includes: recording a method and a flow for correctly deploying OpenStack by using a graphical interface, and generating a configuration file of the deployment according to the graphical interface and a template file, wherein the configuration file comprises a global.yml file, a multimode file, a startup self-running deployment. py script and a hosts file;
the storage module is used for storing the operation data into a preset storage path of the node;
the first sending module is used for sending an automatic operation installation package, wherein the automatic operation installation package is used for calling data on the storage path and executing installation operation on the data;
after the script is started and operated, taking data in the global.yml file as a configuration parameter, and when the script detects that a bare engine node is ready, operating a multimode file; wherein:
yml files comprise global configuration, vip information and component opening configuration data of the OpenStack environment;
the deployment script is used for detecting whether each bare metal node is ready;
the hosts file records the designated ip and user name of each node in the OpenStack environment;
the multimode file includes an allowed configuration file and an inventory file.
7. The apparatus of claim 6, wherein the configuration module comprises:
the obtaining unit is used for obtaining the information of the network and the subnet in the OpenStack system;
and the determining unit is used for determining the network configuration data of the node according to the information of the network and the subnet in the OpenStack system.
8. The apparatus of claim 6 or 7, further comprising:
the query module is used for querying whether the node is in a normal network connection state or not after informing the node to execute the network configuration operation;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is received.
9. The apparatus of claim 8, further comprising:
the query module is further configured to, after querying whether the node is in a normal network connection state, if the information that is fed back by the node and is in the normal network connection state is not received, query again whether the node is in the normal network connection state according to a preset time interval;
and the notification module is used for notifying the node to clear the stored running program and/or the automatic running installation package of the node if the information which is fed back by the node and is in the normal network connection state is not received and the unexplored record reaches a preset time threshold value.
10. The apparatus of claim 9, further comprising:
and the management module is used for retransmitting the running program and/or the automatic running installation package corresponding to the node and controlling the node to execute installation operation after the information which is fed back by the node and is in a normal network connection state and the unexplored record reaches a preset time threshold device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811313509.6A CN109495298B (en) | 2018-11-06 | 2018-11-06 | Method and device for managing nodes in OpenStack system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811313509.6A CN109495298B (en) | 2018-11-06 | 2018-11-06 | Method and device for managing nodes in OpenStack system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109495298A CN109495298A (en) | 2019-03-19 |
| CN109495298B true CN109495298B (en) | 2022-06-07 |
Family
ID=65693999
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811313509.6A Active CN109495298B (en) | 2018-11-06 | 2018-11-06 | Method and device for managing nodes in OpenStack system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109495298B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111427749B (en) * | 2020-04-01 | 2023-07-11 | 山东汇贸电子口岸有限公司 | Monitoring tool and method for ironic service in opentack environment |
| CN112702308A (en) * | 2020-08-20 | 2021-04-23 | 纬领(青岛)网络安全研究院有限公司 | Big data private cloud storage security analysis and practical research |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231681A (en) * | 2011-06-27 | 2011-11-02 | 中国建设银行股份有限公司 | High availability cluster computer system and fault treatment method thereof |
| CN105426208A (en) * | 2015-11-16 | 2016-03-23 | 山东超越数控电子有限公司 | OpenStack offline automatic installation method of cloud computing system |
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| CN106998338A (en) * | 2016-01-22 | 2017-08-01 | 中兴通讯股份有限公司 | A kind of method and device for realizing VNF deployment |
| CN107329769A (en) * | 2017-07-07 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of method and apparatus for configuring bare machine server |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106155719A (en) * | 2015-04-02 | 2016-11-23 | 上海仪电(集团)有限公司 | A kind of method and system utilizing USB device to realize openstack rapid deployment |
| CN106878385B (en) * | 2016-12-30 | 2020-05-12 | 新华三技术有限公司 | Private cloud deployment method and device |
| CN108196764A (en) * | 2017-11-30 | 2018-06-22 | 银联商务股份有限公司 | Application architecture dispositions method, device, system and cloud platform |
-
2018
- 2018-11-06 CN CN201811313509.6A patent/CN109495298B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231681A (en) * | 2011-06-27 | 2011-11-02 | 中国建设银行股份有限公司 | High availability cluster computer system and fault treatment method thereof |
| CN105426208A (en) * | 2015-11-16 | 2016-03-23 | 山东超越数控电子有限公司 | OpenStack offline automatic installation method of cloud computing system |
| CN106998338A (en) * | 2016-01-22 | 2017-08-01 | 中兴通讯股份有限公司 | A kind of method and device for realizing VNF deployment |
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| CN107329769A (en) * | 2017-07-07 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of method and apparatus for configuring bare machine server |
Non-Patent Citations (2)
| Title |
|---|
| "ironic介绍与原理";张忠琳;《CSDN：https://blog.csdn.net/zhonglinzhang/article/details/73527973》;20170621;全文 * |
| "OpenStack Ironic实现裸机部署";无问_;《Linux公社 ：https://www.linuxidc.com/Linux/2018-09/154530.htm》;20180930;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109495298A (en) | 2019-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11146620B2 (en) | Systems and methods for instantiating services on top of services | |
| US9529613B2 (en) | Methods and apparatus to reclaim resources in virtual computing environments | |
| US9858105B1 (en) | Service for managing custom virtual machine images | |
| US20140189677A1 (en) | Effective Migration and Upgrade of Virtual Machines in Cloud Environments | |
| KR102524126B1 (en) | Apparatus for providing design and deployment of distributed cloud system for establishing 5G infra and method thereof | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN110138577B (en) | Cluster creation method, first server and readable storage medium | |
| CN111427594B (en) | Application program running method and device | |
| US20240111549A1 (en) | Method and apparatus for constructing android running environment | |
| CN110928554A (en) | Deployment method, device, equipment and storage medium | |
| CN109495298B (en) | Method and device for managing nodes in OpenStack system | |
| CN110968331A (en) | Method and device for running application program | |
| US11681585B2 (en) | Data migration for a shared database | |
| WO2016197688A1 (en) | Data collection method and device | |
| CN112948008A (en) | Ironic based physical bare computer management method | |
| CN111488163B (en) | Firmware updating method and device, electronic equipment and storage medium | |
| CN104104701A (en) | Online service configuration updating method and system | |
| CN109491762B (en) | Container state control method and device, storage medium and electronic equipment | |
| CN116724543A (en) | Container cluster management method and device | |
| CN112214227A (en) | Edge server mirror image customization and deployment system and method | |
| CN115357198B (en) | Mounting method and device of storage volume, storage medium and electronic equipment | |
| CN111131131B (en) | Vulnerability scanning method and device, server and readable storage medium | |
| CN104111862A (en) | Method and system for obtaining IP (Internet Protocol) address of virtual machine in cloud computing platform | |
| CN106803786B (en) | Network element updating method and system based on network function virtualization | |
| CN109101253B (en) | Management method and device for host in cloud computing system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |