CN106878385B - Private cloud deployment method and device - Google Patents
Private cloud deployment method and device Download PDFInfo
- Publication number
- CN106878385B CN106878385B CN201611255511.3A CN201611255511A CN106878385B CN 106878385 B CN106878385 B CN 106878385B CN 201611255511 A CN201611255511 A CN 201611255511A CN 106878385 B CN106878385 B CN 106878385B
- Authority
- CN
- China
- Prior art keywords
- container
- cluster
- node
- deployment
- operating system
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- 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
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a private cloud deployment method, which comprises the following steps: deploying a container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to the OpenStack component service set by a user for the node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment; receiving cluster nodes set by a user, and informing the cluster nodes to deploy a specified operating system according to deployment information of the specified operating system issued by the node; after the cluster node deploys the specified operating system, the cluster node is informed to deploy the container cluster environment according to the container cluster environment deployment information issued by the node, so that the cluster node starts the corresponding container after deploying the container cluster environment. Therefore, the private cloud deployment can be carried out by adopting a cluster mode and a container technology, the stability and the expansibility of the private cloud deployment are improved, and the efficiency of the private cloud deployment is also improved.
Description
Technical Field
The present application relates to the field of cloud technologies, and in particular, to a private cloud deployment method and apparatus.
Background
With the rapid development of cloud computing technology, more and more enterprises start to build their own private clouds (PrivateClouds).
At present, OpenStack is an open-source cloud computing management platform project, and several main components are combined to complete specific work. And when the private cloud is deployed based on the OpenStack, different components of the OpenStack can be downloaded through a network, and different configurations are performed on each component in a manual mode.
However, the deployment efficiency of the private cloud is very low due to the numerous OpenStack components and the complex configuration.
Disclosure of Invention
The application provides a private cloud deployment method and device, and aims to solve the problem that in the prior art, due to numerous OpenStack components and complex configuration, the deployment efficiency of a private cloud is extremely low.
According to a first aspect of embodiments of the present application, there is provided a private cloud deployment method,
the method is applied to the nodes which are deployed with specified operating systems and serve as cluster management nodes, and comprises the following steps:
deploying a container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to the OpenStack component service set by a user for the node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment;
receiving a cluster node set by a user, and informing the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the node;
and after the cluster node deploys the specified operating system, informing the cluster node to deploy the container cluster environment according to the container cluster environment deployment information issued by the node, so that after the cluster node deploys the container cluster environment, starting a corresponding container according to a container mirror image corresponding to the OpenStack component service set by the cluster node by a user issued by the node under the container cluster environment.
According to a second aspect of the embodiments of the present application, there is provided a private cloud deployment apparatus, where the apparatus is applied to a node deployed with a specified operating system and serving as a cluster management node, and the apparatus includes:
the deployment unit is used for deploying the container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to the OpenStack component service set by a user for the node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment;
the first notification unit is used for receiving a cluster node set by a user and notifying the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the node;
and the second notification unit is used for notifying the cluster nodes to deploy the container cluster environment according to the container cluster environment deployment information issued by the cluster nodes after the cluster nodes have deployed the specified operating system, so that the cluster nodes can start corresponding containers according to container images corresponding to the OpenStack component services set by the cluster nodes by users issued by the cluster nodes under the container cluster environment after the cluster nodes have deployed the container cluster environment.
By applying the embodiment of the application, the container cluster environment is deployed on each cluster node, the cluster management node can acquire the container mirror image corresponding to the OpenStack component service set by the user for the cluster node from the container service mirror image warehouse, and start the corresponding container according to the acquired container mirror image in the container cluster environment, and other cluster nodes can start the corresponding container according to the container mirror image corresponding to the OpenStack component service set by the user for other cluster nodes issued by the cluster management node, so that private cloud deployment is realized by adopting a cluster mode and a container technology, the stability and expansibility of the private cloud deployment are improved, and the efficiency of the private cloud deployment is also improved.
Drawings
FIG. 1 is a flow diagram of one embodiment of a private cloud deployment method of the present application;
FIG. 2 is a schematic diagram of an application scenario of the private cloud deployment method of the present application;
FIG. 3 is a flow diagram of another embodiment of a private cloud deployment method of the present application;
fig. 4 is a schematic diagram of a hardware structure of a device in which the private cloud deployment apparatus of the present application is located;
fig. 5 is a block diagram of an embodiment of a private cloud deployment apparatus of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Fig. 1 is a flowchart of an embodiment of a private cloud deployment method of the present application, and fig. 2 is an application scenario diagram of the private cloud deployment method of the present application, where the private cloud deployment method may be applied to a node that is deployed with a specified operating system and serves as a cluster management node, where the specified operating system may be specifically a Windows system or a Linux system, and the node that serves as the cluster management node may be specifically a server or a virtual machine. As shown in fig. 1, the private cloud deployment method includes the following steps 110 and 130:
and step 110, deploying the container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to the OpenStack component service set by the user for the node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment.
In this embodiment of the application, the node may obtain the container cluster environment deployment information from the preset installation package. Wherein the preset installation package is a container technology-based installation package that includes information for deploying a container cluster environment.
Such as: the preset installation package comprises operating system deployment information (which can comprise an operating installation source and an operating system installation script), an automation deployment management program, a centralized configuration management system script, a container installation source, a container cluster management tool installation source and a container service mirror repository. Wherein the container installation source and the container cluster management tool installation source are information for deploying a container cluster environment.
The node can also run an automatic deployment management program, and an automatic deployment page is provided after the automatic deployment management program runs, so that a user can conveniently set information for private cloud deployment on the automatic deployment page.
In an embodiment, when deploying the container cluster environment according to the acquired container cluster environment deployment information, the method may include:
and deploying the container cluster environment according to the acquired container installation source and the container cluster management tool installation source.
In an embodiment, when a container image corresponding to an OpenStack component service set by a user for the node is acquired from a container service image repository, the method may include:
and acquiring a container mirror image corresponding to the OpenStack component service set by the user on the automatic deployment page aiming at the node from a container service mirror image warehouse.
And step 120, receiving the cluster nodes set by the user, and informing the cluster nodes to deploy the specified operating system according to the deployment information of the specified operating system issued by the node.
In the embodiment of the application, cluster nodes are set, and private cloud deployment is performed in a cluster mode, so that when one node in a cluster is down, other nodes can completely assume the role of the node. Wherein the cluster nodes are peer-to-peer, without a master-slave partition, and each have relevant parameters for network communication, e.g. each cluster node has an IP address for intra-cluster communication.
When a user sets cluster nodes, the automatic deployment page provided by the node can be used for setting, and after the user sets the cluster nodes, the node can acquire operating system deployment information from the preset installation package, issue the operating system deployment information to each cluster node set by the user, and inform each cluster node to install a specified operating system according to the issued operating system deployment information.
In addition, the node is defaulted as one node in the cluster and has a cluster management function. Before a user sets a cluster node, the node acquires operating system deployment information from a preset installation package and installs a specified operating system.
In an embodiment, the cluster node receiving the user setting may include:
and receiving cluster nodes set on an automatic deployment page displayed after the automatic deployment management program is run by a user on the node.
The step 110 and the step 120 are not executed in sequence, and the step 110 may be executed first, and then the step 120 may be executed; step 120 may be performed first, and then step 110 may be performed; step 110 and step 120 may also be performed simultaneously.
In this embodiment of the present application, the OpenStack component may include: a compute component, a storage component, a web component, an authentication component, and the like.
In an embodiment, before notifying the cluster node to deploy the container cluster environment according to the container cluster environment deployment information issued by the node, the method may include:
and running a centralized configuration management system script to realize the management of the cluster nodes.
Referring to fig. 2, the server 1 is a node that is deployed with a specified operating system and serves as a cluster management node. The server 1 may first obtain the operating system deployment information from the preset installation package and install the specified operating system, and then obtain the container installation source and the container cluster management tool installation source from the preset installation package and deploy the container cluster environment.
After the server 1 runs the automated deployment management program, an automated deployment page is displayed, so that a user can conveniently set cluster nodes on the automated deployment page and set OpenStack component services for the cluster nodes.
When receiving that a user sets that the server 2 and the server 3 are cluster nodes on an automatic deployment page, the server 1 issues deployment information of the operating system to the server 2 and the server 3 and informs the server 2 and the server 3 of installing a specified operating system; and after the server 2 and the server 3 are installed with the specified operating systems, sending the container installation source and the container cluster management tool installation source to the server 2 and the server 3, and informing the server 2 and the server 3 to deploy the container cluster environment.
For the OpenStack component service set by the user for the node on the automated deployment page, the server 1 may acquire a container mirror image corresponding to the OpenStack component service set by the user for the node from the container service mirror image warehouse, and start a corresponding container according to the acquired container mirror image in the container cluster environment.
For the OpenStack component service set by the user for the server 2 on the automated deployment page, the server 1 obtains a container mirror image corresponding to the OpenStack component service set by the user for the server 2 from the container service mirror image warehouse, and sends the container mirror image to the server 2, so that the server 2 starts a corresponding container.
For the OpenStack component service set by the user for the server 3 on the automated deployment page, the server 1 obtains a container mirror image corresponding to the OpenStack component service set by the user for the server 3 from the container service mirror image warehouse, and issues the container mirror image to the server 3, so that the server 3 starts a corresponding container.
As can be seen from the above embodiments, by deploying a container cluster environment for each cluster node, a cluster management node may obtain, from a container service mirror warehouse, a container mirror corresponding to an OpenStack component service set by a user for the node, and start a corresponding container according to the obtained container mirror in the container cluster environment, and other cluster nodes may start corresponding containers according to container mirrors corresponding to OpenStack component services set by the user for other cluster nodes, which are issued by the cluster management node, thereby implementing private cloud deployment by using a cluster manner and a container technology, improving stability and expansibility of private cloud deployment, and further improving efficiency of private cloud deployment.
Fig. 3 is a flowchart of another embodiment of the private cloud deployment method according to the present application, where the private cloud deployment method may be applied to a node that is deployed with a specified operating system and serves as a cluster management node, where the specified operating system may specifically be a Windows system or a Linux system, and the node that serves as the cluster management node may specifically be a server or a virtual machine. As shown in fig. 3, the private cloud deployment method includes the following steps 300-390:
In this embodiment of the application, the node may obtain the automated deployment management program from the preset installation package, and start the automated deployment management program.
The preset installation package may include operating system deployment information, an automation deployment management program, a centralized configuration management system script, a container installation source, a container cluster management tool installation source, and a container service mirror repository. Wherein the container installation source and the container cluster management tool installation source are information for deploying a container cluster environment.
In the embodiment of the application, the automatic deployment page is a graphical interface, the graphical interface and a flexible configuration mode are adopted, and the automatic deployment page is the graphical interface. The user can set cluster nodes and network planning parameters (parameters for network communication) and OpenStack component service parameters for each cluster node on an automated deployment page.
And the automatic deployment page also comprises a page guide, and a user can add one or more network devices as cluster nodes of the private cloud according to the page guide in an automatic discovery mode or a manual mode, and configure network planning parameters and OpenStack component service parameters for each cluster node.
And step 320, receiving the cluster nodes set on the automatic deployment page by the user.
In the embodiment of the application, the preset installation package includes the centralized configuration management system script, and after the node runs the centralized configuration management system script, other nodes in the cluster can be managed.
And 350, acquiring the container cluster environment deployment information, and deploying the container cluster environment according to the container cluster environment deployment information.
In this embodiment of the present application, the container cluster environment deployment information may be a container installation source and a container cluster management tool installation source in a preset installation package. Wherein the container mounting source may be specifically a Docker container mounting source.
And 360, issuing the container cluster environment deployment information to the cluster nodes, and informing the cluster nodes to deploy the container cluster environment.
And 380, acquiring a container mirror image corresponding to the OpenStack component service set by the user for the node from the container service mirror image warehouse, starting a corresponding container according to the acquired container mirror image in the container cluster environment, and ending the process.
As can be seen from the above embodiments, the OpenStack component service is more lightweight and starts more quickly by adopting a container technology for deployment; the cluster mode is adopted for deployment, so that each cluster node is equal and has no master-slave division, and the reliability of the deployment operation environment and the continuity of the service are improved; and a graphical interface and a flexible setting mode are adopted, so that the private cloud deployment efficiency is improved.
Corresponding to the private cloud deployment method embodiment, the application also provides an embodiment of a private cloud deployment apparatus.
The embodiment of private cloud deployment can be applied to specified equipment in an intranet and used for executing the functions of the management nodes of the private cloud deployment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. From a hardware aspect, as shown in fig. 4, the private cloud deployment apparatus according to the present application is a schematic hardware structure diagram of a device in which the private cloud deployment apparatus is located, where the device in the embodiment may generally include other hardware, such as a forwarding chip responsible for processing a packet, in addition to the processor, the network interface, the memory, and the nonvolatile memory shown in fig. 4; the device may also be a distributed device in terms of hardware architecture, possibly including multiple interface cards to allow for expansion of network address translation at the hardware level.
Referring to fig. 5, a block diagram of an embodiment of a private cloud deployment apparatus according to the present application is applied to a node deployed with a designated operating system and serving as a cluster management node, where the designated operating system may specifically be a Windows system or a Linux system, and the node serving as the cluster management node may specifically be a server or a virtual machine, and is used to execute the private cloud deployment method shown in fig. 1, where the apparatus may include: a deployment unit 51, a first notification unit 52 and a second notification unit 53.
A deployment unit 51, configured to deploy a container cluster environment according to the acquired container cluster environment deployment information, acquire a container mirror image corresponding to the OpenStack component service set by the user for the node from a container service mirror image warehouse, and start a corresponding container according to the acquired container mirror image in the container cluster environment;
a first notifying unit 52, configured to receive a cluster node set by a user, and notify the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the node;
and a second notification unit 53, configured to notify the cluster node to deploy the container cluster environment according to the container cluster environment deployment information issued by the cluster node after the cluster node has deployed the specified operating system, so that after the cluster node has deployed the container cluster environment, the cluster node starts a corresponding container according to a container mirror image corresponding to an OpenStack component service set by the cluster node by a user issued by the cluster node in the container cluster environment.
As can be seen from the above embodiments, by deploying a container cluster environment for each cluster node, a cluster management node may obtain, from a container service mirror warehouse, a container mirror corresponding to an OpenStack component service set by a user for the node, and start a corresponding container according to the obtained container mirror in the container cluster environment, and other cluster nodes may start corresponding containers according to container mirrors corresponding to OpenStack component services set by the user for other cluster nodes, which are issued by the cluster management node, thereby implementing private cloud deployment by using a cluster manner and a container technology, improving stability and expansibility of private cloud deployment, and further improving efficiency of private cloud deployment.
In an optional implementation manner, the deployment unit 51 may include: a first deployment subunit, a first acquisition subunit, and a first promoter unit (not shown in fig. 5).
The first deployment subunit is used for deploying the container cluster environment according to the acquired container installation source and the container cluster management tool installation source;
the first obtaining subunit is configured to obtain, from a container service mirror image warehouse, a container mirror image corresponding to the OpenStack component service set by the user for the node;
and the first starting subunit is used for starting the corresponding container according to the container mirror image acquired by the first acquiring subunit in the container cluster environment deployed by the first deploying subunit.
In another alternative implementation manner, the first notification unit 52 may include: a receiving subunit and a notification subunit (not shown in fig. 5).
The receiving subunit is used for receiving the cluster nodes arranged on an automatic deployment page displayed after the automatic deployment management program is operated by the node by a user;
and the notification subunit is configured to notify the cluster node received by the receiving subunit to deploy the specified operating system according to the deployment information of the specified operating system issued by the node.
In another alternative implementation, the deployment unit 51 may include: a second deployment subunit, a second acquisition subunit, and a second promoter unit (not shown in fig. 5).
The second deployment subunit is used for deploying the container cluster environment according to the acquired container cluster environment deployment information;
and the second acquiring subunit is configured to acquire, from the container service mirror repository, a container mirror corresponding to the OpenStack component service set by the user for the node on the automation deployment page.
And the second starting subunit is used for starting the corresponding container according to the container mirror image acquired by the second acquiring subunit in the container cluster environment deployed by the second deploying subunit.
In another optional implementation manner, the apparatus may further include: an operating unit (not shown in fig. 5).
And the running unit is configured to run the centralized configuration management system script before the second notification unit 53 notifies the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the node.
As can be seen from the above embodiments, the OpenStack component service is more lightweight and starts more quickly by adopting a container technology for deployment; the cluster mode is adopted for deployment, so that each cluster node is equal and has no master-slave division, and the reliability of the deployment operation environment and the continuity of the service are improved; and a graphical interface and a flexible setting mode are adopted, so that the private cloud deployment efficiency is improved.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A private cloud deployment method is applied to a node which is deployed with a specified operating system and serves as a cluster management node, and comprises the following steps:
deploying a container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to an OpenStack component service set by a user for the cluster management node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment;
receiving a cluster node set by a user, and informing the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the cluster management node;
and after the cluster node deploys the specified operating system, informing the cluster node to deploy the container cluster environment according to the container cluster environment deployment information issued by the cluster management node, so that after the cluster node deploys the container cluster environment, starting a corresponding container according to a container mirror image corresponding to an OpenStack component service set by the cluster node by a user issued by the cluster management node under the container cluster environment.
2. The method according to claim 1, wherein the deploying the container cluster environment according to the acquired container cluster environment deployment information specifically comprises:
and deploying the container cluster environment according to the acquired container installation source and the container cluster management tool installation source.
3. The method according to claim 1, wherein the receiving the cluster node set by the user specifically includes:
and receiving cluster nodes set on an automatic deployment page displayed after the automatic deployment management program is operated by the cluster management nodes by a user.
4. The method according to claim 3, wherein the obtaining of the container image corresponding to the OpenStack component service set by the user for the cluster management node from the container service image repository specifically includes:
and acquiring a container mirror image corresponding to the OpenStack component service set by the user on the automatic deployment page aiming at the cluster management node from a container service mirror image warehouse.
5. The method according to claim 1, wherein before notifying the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the cluster management node, the method further comprises:
and running a centralized configuration management system script.
6. A private cloud deployment apparatus applied to a node deployed with a specified operating system and serving as a cluster management node, the apparatus comprising:
the deployment unit is used for deploying the container cluster environment according to the acquired container cluster environment deployment information, acquiring a container mirror image corresponding to the OpenStack component service set by a user aiming at the cluster management node from a container service mirror image warehouse, and starting a corresponding container according to the acquired container mirror image in the container cluster environment;
the first notification unit is used for receiving a cluster node set by a user and notifying the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the cluster management node;
and the second notification unit is used for notifying the cluster nodes to deploy the container cluster environment according to the container cluster environment deployment information issued by the cluster management node after the cluster nodes have deployed the specified operating system, so that the cluster nodes start corresponding containers according to container images corresponding to the OpenStack component services set by the cluster nodes under the container cluster environment after the cluster nodes have deployed the container cluster environment according to users issued by the cluster management node.
7. The apparatus of claim 6, wherein the deployment unit comprises:
the first deployment subunit is used for deploying the container cluster environment according to the acquired container installation source and the container cluster management tool installation source;
the first obtaining subunit is configured to obtain, from a container service mirror repository, a container mirror corresponding to the OpenStack component service set by the user for the cluster management node;
and the first starting subunit is used for starting the corresponding container according to the container mirror image acquired by the first acquiring subunit in the container cluster environment deployed by the first deploying subunit.
8. The apparatus of claim 6, wherein the first notification unit comprises:
the receiving subunit is used for receiving the cluster nodes arranged on an automatic deployment page displayed by a user after the automatic deployment management program is run by the cluster management nodes;
and the notification subunit is configured to notify the cluster node received by the receiving subunit to deploy the specified operating system according to the deployment information of the specified operating system issued by the cluster management node.
9. The apparatus of claim 8, wherein the deployment unit comprises:
the second deployment subunit is used for deploying the container cluster environment according to the acquired container cluster environment deployment information;
a second obtaining subunit, configured to obtain, from a container service mirror repository, a container mirror corresponding to an OpenStack component service set by a user on the automation deployment page for the cluster management node;
and the second starting subunit is used for starting the corresponding container according to the container mirror image acquired by the second acquiring subunit in the container cluster environment deployed by the second deploying subunit.
10. The apparatus of claim 6, further comprising:
and the running unit is used for running a centralized configuration management system script before the second notification unit notifies the cluster node to deploy the specified operating system according to the deployment information of the specified operating system issued by the cluster management node.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611255511.3A CN106878385B (en) | 2016-12-30 | 2016-12-30 | Private cloud deployment method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611255511.3A CN106878385B (en) | 2016-12-30 | 2016-12-30 | Private cloud deployment method and device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106878385A CN106878385A (en) | 2017-06-20 |
CN106878385B true CN106878385B (en) | 2020-05-12 |
Family
ID=59165366
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201611255511.3A Active CN106878385B (en) | 2016-12-30 | 2016-12-30 | Private cloud deployment method and device |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106878385B (en) |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107547519B (en) * | 2017-07-31 | 2020-03-06 | 新华三大数据技术有限公司 | Wireless big data deployment method and device |
CN107659643A (en) * | 2017-09-25 | 2018-02-02 | 浪潮软件集团有限公司 | Cloud platform construction method and device |
CN108462746B (en) * | 2018-03-14 | 2021-11-16 | 广州西麦科技股份有限公司 | Container deployment method and framework based on openstack |
CN108628664A (en) * | 2018-05-11 | 2018-10-09 | 北京辰森世纪科技股份有限公司 | A kind of method and device of container processing |
CN108924217B (en) * | 2018-06-29 | 2020-12-22 | 中山大学 | Automatic deployment method of distributed cloud system |
CN109495298B (en) * | 2018-11-06 | 2022-06-07 | 郑州云海信息技术有限公司 | Method and device for managing nodes in OpenStack system |
CN109799998B (en) * | 2018-12-18 | 2023-02-10 | 深圳先进技术研究院 | OpenStack cluster configuration and batch deployment method and system |
CN109995878A (en) * | 2019-04-12 | 2019-07-09 | 成都四方伟业软件股份有限公司 | Resource share method and distributed cluster system |
CN112379934B (en) * | 2019-07-29 | 2022-12-13 | 中移(苏州)软件技术有限公司 | Deployment method and device of cloud computing platform and storage medium |
CN110688126A (en) * | 2019-08-29 | 2020-01-14 | 北京浪潮数据技术有限公司 | Big data platform deployment method and device |
CN111198696B (en) * | 2019-12-30 | 2021-06-29 | 湖南大学 | OpenStack large-scale deployment method and system based on bare computer server |
CN112187567A (en) * | 2020-09-11 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Containerized agent-free private cloud management method and system |
CN112269694B (en) * | 2020-10-23 | 2023-12-22 | 北京浪潮数据技术有限公司 | Management node determining method and device, electronic equipment and readable storage medium |
CN112311886B (en) * | 2020-10-30 | 2022-03-01 | 新华三大数据技术有限公司 | Multi-cluster deployment method, device and management node |
CN113434245A (en) * | 2021-05-31 | 2021-09-24 | 济南浪潮数据技术有限公司 | Edge cluster deployment method, system, equipment and storage medium |
CN113645300B (en) * | 2021-08-10 | 2023-11-28 | 上海道客网络科技有限公司 | Intelligent node scheduling method and system based on Kubernetes cluster |
CN114827177B (en) * | 2022-04-22 | 2024-03-08 | 杭州萤石软件有限公司 | Deployment method and device of distributed file system and electronic equipment |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7861243B2 (en) * | 2003-07-11 | 2010-12-28 | Computer Associates Think, Inc. | Automatically deploying program units to a cluster of networked servers |
CN103167041B (en) * | 2013-03-28 | 2016-04-20 | 广州中国科学院软件应用技术研究所 | A kind ofly support the system and method that the automation of cloud environment application cluster is disposed |
CN104219099A (en) * | 2014-09-25 | 2014-12-17 | 浪潮(北京)电子信息产业有限公司 | Automatic server cluster deploying method and device |
CN104580519B (en) * | 2015-01-29 | 2017-11-28 | 福建师范大学福清分校 | A kind of method of rapid deployment openstack cloud computing platforms |
CN104754032A (en) * | 2015-02-27 | 2015-07-01 | 浪潮集团有限公司 | Method and device for deploying OpenStack |
CN105100267B (en) * | 2015-08-24 | 2018-12-14 | 用友网络科技股份有限公司 | The deployment device and method of large enterprises' private clound |
CN105245373B (en) * | 2015-10-12 | 2017-08-04 | 天津市普迅电力信息技术有限公司 | A kind of container cloud platform system is built and operation method |
CN105468362B (en) * | 2015-11-17 | 2019-03-08 | 广州杰赛科技股份有限公司 | Using dispositions method and cloud computing system |
CN105743995B (en) * | 2016-04-05 | 2019-10-18 | 北京轻元科技有限公司 | A kind of system and method for the deployment of portable High Availabitity and management container cluster |
-
2016
- 2016-12-30 CN CN201611255511.3A patent/CN106878385B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN106878385A (en) | 2017-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106878385B (en) | Private cloud deployment method and device | |
US11611487B2 (en) | Model driven process for automated deployment of domain 2.0 virtualized services and applications on cloud infrastructure | |
CN108809722B (en) | Method, device and storage medium for deploying Kubernetes cluster | |
US11296923B2 (en) | Network fault originator identification for virtual network infrastructure | |
CN110752947B (en) | K8s cluster deployment method and device, and deployment platform | |
CN106533753B (en) | Role configuration method and device of distributed system | |
WO2017161984A1 (en) | Method, device and system for deploying data clusters, and computer storage medium | |
EP2904739B1 (en) | Discovering, validating, and configuring hardware-inventory components | |
CN104967664A (en) | Automatic cloud deploying system and method | |
EP3300298B1 (en) | Method and apparatus for switching vnf | |
JP2020500462A (en) | Virtualizable satellite platform | |
CN103336688A (en) | Software integrating method and system oriented to cloud computing software research and development process | |
US20140317229A1 (en) | Automatic versioning and updating M2M network applications | |
CN112506617B (en) | Mirror image updating method and device for side car containers in Kubernetes cluster | |
CN106549789B (en) | Method and system for realizing server installation | |
CN111324412A (en) | Service deployment method, device and storage medium | |
CN107005435B (en) | Network service descriptor shelving method and device | |
CN109474443B (en) | Configuration method, device and system of newly added server and communication equipment | |
CN113656147B (en) | Cluster deployment method, device, equipment and storage medium | |
CN113645314B (en) | Private cloud deployment method and server | |
CN111198696B (en) | OpenStack large-scale deployment method and system based on bare computer server | |
CN109120444B (en) | Cloud resource management method, processor and storage medium | |
CN110489305B (en) | Server management method and device | |
CN112333229A (en) | Method, device, equipment and storage medium for expanding kubernets nodes | |
US10608867B2 (en) | Method and an electronic arrangement for providing demand-supply service of physical communication network resources |
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 |