CN110519112A - A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system - Google Patents
A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system Download PDFInfo
- Publication number
- CN110519112A CN110519112A CN201810491763.9A CN201810491763A CN110519112A CN 110519112 A CN110519112 A CN 110519112A CN 201810491763 A CN201810491763 A CN 201810491763A CN 110519112 A CN110519112 A CN 110519112A
- Authority
- CN
- China
- Prior art keywords
- high availabitity
- server
- cluster
- availabitity
- dynamic
- 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.)
- Pending
Links
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/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- 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/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
- H04L67/1048—Departure or maintenance mechanisms
Abstract
The invention discloses a kind of methods for realizing the continuous High Availabitity of dynamic in cluster storage system, by periodically sending heartbeat packet cluster server state, when server breaks down switching destruction High Availabitity, triggering High Availabitity reconfiguration system reconstructs a new high-availability system from cluster residue available server node automatically, data shape between synchronous High Availabitity server simultaneously, state synchronized between holding High Availabitity server, makes cluster reach the new state of stable High Availabitity.The present invention reconstructs the new state of High Availabitity automatically, is sustained High Availabitity when cluster failure High Availabitity destroys.
Description
Technical field
The present invention relates to a kind of storage system, specifically a kind of side for realizing the continuous High Availabitity of dynamic in cluster storage system
Method.
Background technique
With the rapid growth and cloud of data, the extensive use of big data, server data to be treated are got over
Carry out more, the server rectilinear growth needed for storing and calculate for data.Clustering, which ensure that, can unify to provide
High performance service, but in cluster server node it is more and more, and data rapid growth to be treated, cluster and clothes
The probability that device breaks down of being engaged in is also higher and higher, how to guarantee the continuous high availability of cluster and constantly stable external
Service is provided, urgent problem is become.It is provided in particular in the group system of important information data storage, can be provided persistently
Continuously high availability becomes an important factor for influencing cluster stability and safety.It may be said that High Availabitity affects one
The success or failure of cluster.
Current main High Availabitity includes active-standby mode, and more main one is standby.No matter which kind of mode, which all exists, needs artificial deployment,
Once destruction High Availabitity environment is just irreversible or can not repeatedly provide the defect of High Availabitity.
For currently on the market have cluster High Availabitity it is single, can not inverse problem, cluster can only be implemented deployed good
High Availabitity may only construct a High Availabitity automatically.Cluster High Availabitity break down switching after can not continuous several times weigh automatically
Structure goes out the safety that new high-availability system guarantees cluster, once cluster is destroyed more than two times, group system is also faced with nothing
Method operates normally or the great risk of loss of data.Through this method when cluster failure High Availabitity destroys, automatic weight
Structure goes out the new state of High Availabitity, is sustained High Availabitity.
Summary of the invention
The purpose of the present invention is to provide a kind of methods for realizing the continuous High Availabitity of dynamic in cluster storage system, to solve
The problems mentioned above in the background art.
To achieve the above object, the invention provides the following technical scheme:
A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system, by periodically sending heartbeat packet cluster
Server state, when server breaks down switching destruction High Availabitity, triggering High Availabitity reconfiguration system is available from cluster residue
Automatically a new high-availability system, while the data shape between synchronous High Availabitity server are reconstructed in server node, are kept
State synchronized between High Availabitity server makes cluster reach the new state of stable High Availabitity.
As a further solution of the present invention: being responsible for whether locating using heartbeat detection High Availabitity server using monitoring module
In normal condition, if heartbeat is unable to normal communication and shows that current High Availabitity breaks down, service can be switched to active service
Device continues offer service.
As a further solution of the present invention: can give trigger module one signal after server switching, trigger module is being received
To after signal, environment required for reconstruct High Availabitity is begun preparing, including regulative strategy module selection reconstruct High Availabitity is included
Server calls the data between the synchronous primary server of synchronization module and standby server, keeps the consistency of data.
As a further solution of the present invention: being responsible for from server trouble-free in cluster using policy module according to pre-
Fixed strategy is selected need to set up new High Availabitity needed for server, and close the High Availabitity service of all failure servers,
It is no longer selected after determining as High Availabitity server.
As further scheme of the invention: being responsible for after selecting new server using synchronization module, synchronous service
Database data between device, configuration file.
Compared with prior art, the beneficial effects of the present invention are: the present invention is when cluster failure High Availabitity destroys, from
It is dynamic to reconstruct the new state of High Availabitity, it is sustained High Availabitity.
Specific embodiment
The following is a clear and complete description of the technical scheme in the embodiments of the invention, it is clear that described embodiment
Only a part of the embodiment of the present invention, instead of all the embodiments.Based on the embodiments of the present invention, the common skill in this field
Art personnel every other embodiment obtained without making creative work belongs to the model that the present invention protects
It encloses.
In the embodiment of the present invention, a method of the continuous High Availabitity of dynamic in cluster storage system is realized, by periodically sending out
Heartbeat packet cluster server state is sent, when server breaks down switching destruction High Availabitity, High Availabitity reconstruct can be triggered
System reconstructs a new high-availability system, while synchronous High Availabitity service automatically from cluster residue available server node
Data shape between device keeps state synchronized between High Availabitity server, cluster is made to reach the new state of stable High Availabitity.Ensure to collect
Group's moment is in the state of High Availabitity.
The present invention every time when High Availabitity is by destroying, can trigger under the premise of not influencing to provide outward service
Select server and standby server to reconstruct new High Availabitity state automatically from remaining server, and sync server it
Between data, keep the data mode timing synchronization between High Availabitity server, overall process do not need manually to be intervened.Even if high
It can be with also can guarantee continuous High Availabitity state by destroying for times, until there is no available server in cluster.
The present invention realizes that cluster provides reliable and stable High Availabitity, tries one's best and provides stable service for user, protects
Secure user data.
One, comprising modules:
Present invention composition: monitoring module, trigger module, synchronization module, reconstructed module
1. monitoring module
Monitoring module is responsible for whether being in normal condition using heartbeat detection High Availabitity server.If heartbeat cannot be normal
Communication shows that current High Availabitity breaks down, and service can be switched to standby server and continue offer service.
2. trigger module
It can give trigger module one signal after server switching.It is high to begin preparing reconstruct after receiving signal for trigger module
Required environment can be used.Reconstruct the included server of High Availabitity is selected including regulative strategy module, calls synchronization module synchronous
Data between primary server and standby server keep the consistency of data.
3. policy module
Policy module be responsible for selecting from server trouble-free in cluster according to scheduled strategy need to set up new peak can
With required server.And close the High Availabitity service of all failure servers.It is no longer selected after determining as High Availabitity.
4. synchronization module
Synchronization module is responsible for after selecting new server, the database data between sync server, configuration file etc.,
Ensure being consistent property between server.The server for constructing High Availabitity is set to be in same state.Prevent the difference between server from leading
Cause High Availabitity abnormal.
5. reconstructed module
After all environment before are ready to, reconstructed module is responsible for can using the new height of selected server construction
Use state.It is constant that all services are externally provided after reconstruct High Availabitity.User is had no effect.
Two, realization principle:
The continuous High Availabitity building of dynamic is the improvement and optimization done on the basis of general High Availabitity.And it fully achieves automatic
Change, does not need manual intervention configuration.Had between High Availabitity server heartbeat carry out communication check, heartbeat can not normal communication, be
System thinks that server failure, High Availabitity are destroyed at this time, and all services will be switched on standby server, system hair
Server construction similar in an IP address and standby server can be selected from existing normal server after existing server switching
New High Availabitity.Building process needs to control modification new demand servicing device High Availabitity configuration by telecommunication, provides service for existing
Device is as primary server, and the server newly selected is as standby server.And in synchrodata to new standby server.To occur
Failed server High Availabitity server closing, and identify as not can be used as High Availabitity use.Again reconstruct High Availabitity when this
Server is not in selecting.Repeatedly reconstruct High Availabitity use identical mechanism, until Servers-all be identified as can not make height can
Until use.
It is obvious to a person skilled in the art that invention is not limited to the details of the above exemplary embodiments, Er Qie
In the case where without departing substantially from spirit or essential attributes of the invention, the present invention can be realized in other specific forms.Therefore, no matter
From the point of view of which point, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the present invention is by appended power
Benefit requires rather than above description limits, it is intended that all by what is fallen within the meaning and scope of the equivalent elements of the claims
Variation is included within the present invention.In addition, it should be understood that although this specification is described in terms of embodiments, but it is not each
Embodiment only contains an independent technical solution, and this description of the specification is merely for the sake of clarity, this field
Technical staff should consider the specification as a whole, and the technical solutions in the various embodiments may also be suitably combined, form this
The other embodiments that field technical staff is understood that.
Claims (5)
1. a kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system, which is characterized in that by periodically sending heartbeat
Detection cluster server state is wrapped, when server breaks down switching destruction High Availabitity, triggers High Availabitity reconfiguration system from collection
Automatically a new high-availability system, while the number between synchronous High Availabitity server are reconstructed in the remaining available server node of group
According to shape, state synchronized between High Availabitity server is kept, cluster is made to reach the new state of stable High Availabitity.
2. the method according to claim 1 for realizing the continuous High Availabitity of dynamic in cluster storage system, which is characterized in that adopt
It is responsible for whether being in normal condition using heartbeat detection High Availabitity server with monitoring module, if heartbeat is unable to normal communication table
Bright current High Availabitity breaks down, and service can be switched to standby server and continue offer service.
3. the method according to claim 1 or 2 for realizing the continuous High Availabitity of dynamic in cluster storage system, feature exist
In meeting give trigger module one signal after server switching, and trigger module begins preparing reconstruct High Availabitity institute after receiving signal
The environment needed, including regulative strategy module selection reconstruct the included server of High Availabitity, call synchronization module to synchronize main service
Data between device and standby server keep the consistency of data.
4. the method according to claim 1 or 2 for realizing the continuous High Availabitity of dynamic in cluster storage system, feature exist
In being responsible for selecting from server trouble-free in cluster according to scheduled strategy and needing to set up new High Availabitity using policy module
Required server, and the High Availabitity service of all failure servers is closed, it is no longer selected after determining as High Availabitity clothes
Business device.
5. the method according to claim 4 for realizing the continuous High Availabitity of dynamic in cluster storage system, which is characterized in that adopt
It is responsible for after selecting new server with synchronization module, the database data between sync server, configuration file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810491763.9A CN110519112A (en) | 2018-05-22 | 2018-05-22 | A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810491763.9A CN110519112A (en) | 2018-05-22 | 2018-05-22 | A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110519112A true CN110519112A (en) | 2019-11-29 |
Family
ID=68621865
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810491763.9A Pending CN110519112A (en) | 2018-05-22 | 2018-05-22 | A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110519112A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112134933A (en) * | 2020-09-04 | 2020-12-25 | 苏州浪潮智能科技有限公司 | Method and device for realizing OpenStack high-availability cache cluster and storage medium |
| US10949192B2 (en) | 2016-02-12 | 2021-03-16 | Nutanix, Inc. | Virtualized file server data sharing |
| US11086826B2 (en) | 2018-04-30 | 2021-08-10 | Nutanix, Inc. | Virtualized server systems and methods including domain joining techniques |
| US20210349858A1 (en) * | 2020-05-08 | 2021-11-11 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
| US11194680B2 (en) | 2018-07-20 | 2021-12-07 | Nutanix, Inc. | Two node clusters recovery on a failure |
| US11218418B2 (en) | 2016-05-20 | 2022-01-04 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
| US11281484B2 (en) | 2016-12-06 | 2022-03-22 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
| US11288239B2 (en) | 2016-12-06 | 2022-03-29 | Nutanix, Inc. | Cloning virtualized file servers |
| US11294777B2 (en) | 2016-12-05 | 2022-04-05 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
| US11310286B2 (en) | 2014-05-09 | 2022-04-19 | Nutanix, Inc. | Mechanism for providing external access to a secured networked virtualization environment |
| US11562034B2 (en) | 2016-12-02 | 2023-01-24 | Nutanix, Inc. | Transparent referrals for distributed file servers |
| US11568073B2 (en) | 2016-12-02 | 2023-01-31 | Nutanix, Inc. | Handling permissions for virtualized file servers |
| US11770447B2 (en) * | 2018-10-31 | 2023-09-26 | Nutanix, Inc. | Managing high-availability file servers |
Citations (3)
| 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 |
| CN103647668A (en) * | 2013-12-16 | 2014-03-19 | 上海证券交易所 | Host group decision system in high availability cluster and switching method for host group decision system |
| US9450852B1 (en) * | 2014-01-03 | 2016-09-20 | Juniper Networks, Inc. | Systems and methods for preventing split-brain scenarios in high-availability clusters |
-
2018
- 2018-05-22 CN CN201810491763.9A patent/CN110519112A/en active Pending
Patent Citations (3)
| 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 |
| CN103647668A (en) * | 2013-12-16 | 2014-03-19 | 上海证券交易所 | Host group decision system in high availability cluster and switching method for host group decision system |
| US9450852B1 (en) * | 2014-01-03 | 2016-09-20 | Juniper Networks, Inc. | Systems and methods for preventing split-brain scenarios in high-availability clusters |
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11310286B2 (en) | 2014-05-09 | 2022-04-19 | Nutanix, Inc. | Mechanism for providing external access to a secured networked virtualization environment |
| US11544049B2 (en) | 2016-02-12 | 2023-01-03 | Nutanix, Inc. | Virtualized file server disaster recovery |
| US11550557B2 (en) | 2016-02-12 | 2023-01-10 | Nutanix, Inc. | Virtualized file server |
| US10949192B2 (en) | 2016-02-12 | 2021-03-16 | Nutanix, Inc. | Virtualized file server data sharing |
| US11537384B2 (en) | 2016-02-12 | 2022-12-27 | Nutanix, Inc. | Virtualized file server distribution across clusters |
| US11947952B2 (en) | 2016-02-12 | 2024-04-02 | Nutanix, Inc. | Virtualized file server disaster recovery |
| US11669320B2 (en) | 2016-02-12 | 2023-06-06 | Nutanix, Inc. | Self-healing virtualized file server |
| US11922157B2 (en) | 2016-02-12 | 2024-03-05 | Nutanix, Inc. | Virtualized file server |
| US11550559B2 (en) | 2016-02-12 | 2023-01-10 | Nutanix, Inc. | Virtualized file server rolling upgrade |
| US11579861B2 (en) | 2016-02-12 | 2023-02-14 | Nutanix, Inc. | Virtualized file server smart data ingestion |
| US11106447B2 (en) | 2016-02-12 | 2021-08-31 | Nutanix, Inc. | Virtualized file server user views |
| US11966730B2 (en) | 2016-02-12 | 2024-04-23 | Nutanix, Inc. | Virtualized file server smart data ingestion |
| US11645065B2 (en) | 2016-02-12 | 2023-05-09 | Nutanix, Inc. | Virtualized file server user views |
| US11550558B2 (en) | 2016-02-12 | 2023-01-10 | Nutanix, Inc. | Virtualized file server deployment |
| US11966729B2 (en) | 2016-02-12 | 2024-04-23 | Nutanix, Inc. | Virtualized file server |
| US11888599B2 (en) | 2016-05-20 | 2024-01-30 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
| US11218418B2 (en) | 2016-05-20 | 2022-01-04 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
| US11562034B2 (en) | 2016-12-02 | 2023-01-24 | Nutanix, Inc. | Transparent referrals for distributed file servers |
| US11568073B2 (en) | 2016-12-02 | 2023-01-31 | Nutanix, Inc. | Handling permissions for virtualized file servers |
| US11775397B2 (en) | 2016-12-05 | 2023-10-03 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
| US11294777B2 (en) | 2016-12-05 | 2022-04-05 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
| US11288239B2 (en) | 2016-12-06 | 2022-03-29 | Nutanix, Inc. | Cloning virtualized file servers |
| US11281484B2 (en) | 2016-12-06 | 2022-03-22 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
| US11922203B2 (en) | 2016-12-06 | 2024-03-05 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
| US11954078B2 (en) | 2016-12-06 | 2024-04-09 | Nutanix, Inc. | Cloning virtualized file servers |
| US11675746B2 (en) | 2018-04-30 | 2023-06-13 | Nutanix, Inc. | Virtualized server systems and methods including domain joining techniques |
| US11086826B2 (en) | 2018-04-30 | 2021-08-10 | Nutanix, Inc. | Virtualized server systems and methods including domain joining techniques |
| US11194680B2 (en) | 2018-07-20 | 2021-12-07 | Nutanix, Inc. | Two node clusters recovery on a failure |
| US11770447B2 (en) * | 2018-10-31 | 2023-09-26 | Nutanix, Inc. | Managing high-availability file servers |
| US11768809B2 (en) | 2020-05-08 | 2023-09-26 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
| US20210349858A1 (en) * | 2020-05-08 | 2021-11-11 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
| CN112134933A (en) * | 2020-09-04 | 2020-12-25 | 苏州浪潮智能科技有限公司 | Method and device for realizing OpenStack high-availability cache cluster and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110519112A (en) | A kind of method for realizing the continuous High Availabitity of dynamic in cluster storage system | |
| CN102739775B (en) | The monitoring of internet of things data acquisition server cluster and management method | |
| US11360854B2 (en) | Storage cluster configuration change method, storage cluster, and computer system | |
| CN111371696B (en) | Method for realizing Pod network flow control in Kubernetes | |
| US11075795B2 (en) | Arbitration method, apparatus, and system used in active-active data centers | |
| CN102739799B (en) | Distributed communication method in distributed application | |
| CN106375342A (en) | Zookeeper-technology-based system cluster method and system | |
| CN105471960A (en) | Information interaction system and method between private clouds and public cloud | |
| CN103744809A (en) | Method for dual-computer hot-standby of vehicle information management system on basis of VRRP | |
| CN110365750A (en) | Service registration system and method | |
| CN103780497B (en) | Extendible distributed coordination service management under a kind of cloud platform | |
| CN103152434A (en) | Leader node replacing method of distributed cloud system | |
| CN107911238A (en) | One kind is based on IPSAN servers two unit standby method and system | |
| CN102122306A (en) | Data processing method and distributed file system applying same | |
| CN105095008B (en) | A kind of distributed task scheduling fault redundance method suitable for group system | |
| CN108173959A (en) | A kind of cluster storage system | |
| CN103488546A (en) | Backup and recovery method capable of supporting online concurrency of multi-level data and database | |
| CN102231677A (en) | Double-center disaster recovery-based switching method and device in IPTV system | |
| CN110765203B (en) | Method and system for realizing MySQL master-slave synchronization and performance acquisition of container | |
| CN108228393A (en) | A kind of implementation method of expansible big data High Availabitity | |
| CN102480489A (en) | Logging method and device used in distributed environment | |
| CN108710550B (en) | Double-data-center disaster tolerance system for public security traffic management inspection and control system | |
| CN112631764A (en) | Task scheduling method and device, computer equipment and computer readable medium | |
| CN106385330B (en) | A kind of implementation method and device of network function virtualization composer | |
| CN106302569A (en) | Process method and the computer system of cluster virtual machine |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191129 |
|
| RJ01 | Rejection of invention patent application after publication |