CN111988367B - Method and system for managing single server in server cluster - Google Patents
Method and system for managing single server in server cluster Download PDFInfo
- Publication number
- CN111988367B CN111988367B CN202010748830.8A CN202010748830A CN111988367B CN 111988367 B CN111988367 B CN 111988367B CN 202010748830 A CN202010748830 A CN 202010748830A CN 111988367 B CN111988367 B CN 111988367B
- Authority
- CN
- China
- Prior art keywords
- server
- restapi
- cluster
- cluster management
- request
- 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 39
- 238000004891 communication Methods 0.000 claims description 22
- 230000002159 abnormal effect Effects 0.000 claims description 11
- 238000012544 monitoring process Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 8
- 238000012217 deletion Methods 0.000 abstract 1
- 230000037430 deletion Effects 0.000 abstract 1
- 238000007726 management method Methods 0.000 description 154
- 230000004044 response Effects 0.000 description 4
- 230000002457 bidirectional effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
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
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mathematical Physics (AREA)
- Hardware Redundancy (AREA)
Abstract
The application discloses a method and a system for managing a single server in a server cluster, wherein the method comprises the following steps: according to the acquired command, a RestAPI interface is used for starting management services of a plurality of servers, and any server adopts a form of saving RestAPI to perform operation recording; and the server side and the cluster management side perform data synchronization by using a mode of sending a restapi request. The system comprises: the system comprises a management service starting module, a recording module and a data synchronization module. By the method and the device, single-server virtualization management can be realized, normal operation of starting up and shutting down the virtual machine, virtual machine creation and virtual machine deletion can be realized, and therefore high availability of a cluster management end is greatly improved, and virtualization management efficiency is improved.
Description
Technical Field
The present application relates to the technical field of server cluster management, and in particular, to a method and a system for managing a single server in a server cluster.
Background
In the virtualization service, a plurality of servers are generally grouped into a server cluster for unified management, and the server cluster can share the CPU and the memory resources thereof, so as to be provided for the virtual machine. Therefore, how to manage each server in the server cluster is an important technical problem.
Currently, in a server cluster, all servers in the current cluster are generally managed in a unified manner, a virtualization management end sends an instruction to each server, and each server performs related operations according to the obtained instruction. When the virtualization management end fails or the communication connection between the virtualization management end and a certain server is disconnected, the management process of the whole cluster is suspended, the failure processing is carried out, and the communication is continued until the troubleshooting is finished.
However, in the existing method for managing servers in a server cluster, when a virtualization management end fails or a communication failure occurs, cluster management is suspended in a processing manner for a single server, which may cause high availability of the virtualization management end to be greatly reduced and management efficiency to be reduced.
Disclosure of Invention
The application provides a method and a system for managing a single server in a server cluster, which are used for solving the problems that the management efficiency of the single server is low and the high availability of the server cluster is low in the prior art.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method of managing individual servers in a server cluster, the server cluster comprising: the method comprises the following steps that a server side and a cluster management side are provided with the same restapi protocol, the server side comprises a plurality of servers, and a single server is any one of the servers which are free from a server cluster when the cluster management side fails, and the method comprises the following steps:
according to the acquired command, a RestAPI interface is used for starting management services of a plurality of servers, the management services are used for single machine management, and the RestAPI interface comprises: a post interface, a put interface and a delete interface;
any server performs operation recording in a form of saving restapi;
the server and the cluster management end perform data synchronization by sending a restapi request, wherein each server of the server comprises a server database, the server database is used for storing host information and an api record storage table of the current server, and the host information comprises: virtual machine information on a host, host network information, and host storage information.
Optionally, the operation record is performed by any server in a form of saving restapi, specifically:
when any RestAPI interface is called, any server inserts a record into an api record storage table, and the record is used for recording the content of operation RestAPI.
Optionally, the data synchronization between the server and the cluster management end by sending a restapi request includes:
after any server carries out operation record in a mode of saving restapi, the server side sends a restapi request to the cluster management side and synchronizes the operation record to the cluster management side;
and the cluster management end synchronizes the operation records of the cluster management end to the server end according to the acquired restapi request.
Optionally, the step of the server side synchronizing the operation record to the cluster management side by sending a restapi request to the cluster management side includes:
judging whether the communication states of the server side and the cluster management side are normal or not;
if the communication states of the server side and the cluster management side are normal, judging that the cluster management service is normal;
the server side sends a restapi request to the cluster management side;
the cluster management terminal synchronizes the data of the current server in cluster management with the data of the current server after operation recording according to the restapi request;
if the communication states of the server side and the cluster management side are abnormal, judging that the cluster management service is abnormal;
the server monitors the management service until the cluster management service is normal, and then the server sends a restapi request to the cluster management terminal;
and after the Restapi processing is finished, emptying the records in the api record saving table of the server side.
Optionally, the synchronizing, by the cluster management end, the cluster management end synchronizes an operation record of the cluster management end to the server end according to the obtained restapi request, including:
the cluster management terminal judges whether the request is any one of a post interface, a put interface and a delete interface according to the acquired restapi request;
if so, judging whether the server sending the restapi request is online;
if the server sending the restapi request is online, sending the same restapi request to the server sending the restapi request;
and if the server sending the restapi request is offline, not responding to the server sending the restapi request.
Optionally, the method further comprises:
when the same resource is operated by the post interface and the delete interface, the operation records are deleted on both the post interface and the delete interface, and the resource comprises: information, storage, and networks.
Optionally, the method further comprises:
when the resources are merged, the bottom layer resource uuid is utilized to judge whether the resources to be merged are the same resource at the server side and the cluster management side;
if yes, merging the resources into one resource;
if not, no combination is performed.
A management system for a single server in a server cluster, the server cluster comprising: the system comprises a server side and a cluster management side, wherein the server side and the cluster management side have the same restapi protocol, and a single server is any one server dissociated from a server cluster when the cluster management side fails, and the system comprises:
a management service starting module, configured to start management services of multiple servers according to the obtained command by using a RestAPI interface, where the management services are used for stand-alone management, and the RestAPI interface includes: a post interface, a put interface and a delete interface;
the recording module is used for carrying out operation recording on any server in a form of saving restapi;
the data synchronization module is used for performing data synchronization at the server side and the cluster management side by sending a restapi request, wherein each server of the server side comprises a server side database, the server side database is used for storing host information and an api record storage table of the current server, and the host information comprises: virtual machine information on the host, host network information, and host storage information.
Optionally, the data synchronization module includes:
the first synchronization unit is used for synchronizing the operation records to the cluster management end by sending a restapi request to the cluster management end at the server end after any server performs the operation records in a restapi storage mode;
and the second synchronization unit is used for synchronizing the cluster management end operation records to the current server end according to the acquired restapi request.
Optionally, the first synchronization unit includes:
the first judging subunit is used for judging whether the communication states of the server side and the cluster management side are normal or not, if the communication states of the server side and the cluster management side are normal, judging that the cluster management service is normal, and if not, judging that the cluster management service is abnormal;
the restapi request sending subunit is used for controlling the current server side to send a restapi request to the cluster management side when the cluster management service is normal;
the synchronization subunit is used for synchronizing the data of the current server in cluster management with the data of the current server after operation recording according to the restapi request;
the monitoring subunit is used for monitoring the management service when the communication states of the server side and the cluster management side are abnormal;
the restapi request sending subunit is further configured to send a restapi request to the cluster management end by the current server end after the monitoring subunit monitors that the cluster management service is normal;
and the emptying subunit is used for emptying the records in the server-side api record saving table after the restapi processing is finished.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the method comprises the steps of firstly starting management services of a plurality of servers by using a RestAPI interface according to an acquired command, then carrying out operation recording on any server in the server cluster in a mode of saving RestAPI, and finally carrying out data synchronization by using a mode of sending a RestAPI request by a server side and a cluster management side. In the embodiment, operation recording is performed by saving a RestAPI form, and when three RestAPI interfaces, namely a post interface, a put interface and a delete interface, are called, operation of the server is recorded by updating the RestAPI _ info table, so that a basis is provided for subsequent data synchronization. The server side and the cluster management side perform data synchronization by sending a restapi request, so that the synchronization of operation contents from the server side to the cluster management side and the synchronization of operation contents from the cluster management side to the server side can be realized, the data synchronization of a single server free from a server cluster is ensured when the cluster management side fails, the downtime operation is avoided, the normal operation of starting, shutting down, creating a virtual machine and deleting the virtual machine of the virtual machine are realized through the virtualization management of the single server, the high availability of the cluster management side is greatly improved, and the virtualization management efficiency is improved.
The application also provides a management system of the single server in the server cluster. The system mainly comprises: the system comprises a management service starting module, a recording module and a data synchronization module. The management service starting module is used for starting the management services of a plurality of servers in the server cluster, so that the follow-up single machine management is facilitated. Through the recording module, the operation record is carried out on the interface call in a mode of saving restapi, and the improvement of the management efficiency is facilitated. And finally, the bidirectional synchronization of the server side and the cluster management side can be realized through the data synchronization module, so that the single server can be normally subjected to virtualization management when the cluster management side fails, the high availability of the cluster management side is greatly improved, and the virtualization management efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a management method for a single server in a server cluster according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a management system of a single server in a server cluster according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort shall fall within the protection scope of the present application.
For a better understanding of the present application, embodiments of the present application are explained in detail below with reference to the accompanying drawings.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart of a management method for a single server in a server cluster according to an embodiment of the present application. As shown in fig. 1, the method for managing a single server in a server cluster in this embodiment mainly includes the following steps:
s1: and starting the management services of the plurality of servers by utilizing the RestAPI interface according to the acquired command, wherein the management services are used for single machine management.
The server cluster in this embodiment includes: the system comprises a server side and a cluster management side, wherein the server side and the cluster management side have the same restapi protocol, and a management interface of the server side is consistent with an interface of the cluster management side. The server side comprises a plurality of servers, and a single server in the embodiment is any server which is free from the server cluster when the cluster management side fails. Any server of the server side is provided with a management system and a server side database, wherein the management system is used for managing the host service of the current server, the server side database is used for storing the host information and the api record storage table of the current server, and the host information comprises: virtual machine information on the host, host network information, and host storage information. And the table structure of the server-side database is consistent with that of the cluster-side server, but only an api record storage table is added in the server-side database. The api record holding table in this embodiment is a table restapi _ info, and is used to record whether the host performs stand-alone management. The setting of the api record storage table can timely record the content of the operation restapi and provide a basis for subsequent data synchronization, so that the accuracy of data synchronization is improved.
In step S1, the management service is opened for each of the plurality of servers, and the subsequent stand-alone management can be realized. The management provides the RestAPI interface to the outside. Wherein, the RestAPI interface includes: post interface, put interface, and delete interface. The post interface is used for creating the virtual machine, the put interface is used for updating the virtual machine, and the delete interface is used for deleting the virtual machine.
With continued reference to fig. 1, after the management service is started, step S2 is executed: any server performs operation recording in a mode of saving restapi.
Specifically, step S2 includes: when any RestAPI interface is called, any server inserts a record into the api record saving table, and the record is used for recording the content of the operation RestAPI. That is, in this embodiment, through RestAPI, when three types of interfaces, namely, a post interface, a put interface, and a delete interface, are called, the table RestAPI _ info is updated, that is: when these three types of interfaces are called, a record must be inserted into the table restapin _ info for recording the operation restapin content. Of course, the record here does not include the record sent from the cluster management side.
S3: and the server side and the cluster management side perform data synchronization by using a mode of sending a restapi request.
Specifically, step S3 includes:
s31: after any server performs operation recording in a form of saving restapi, the server side synchronizes the operation recording to the cluster management side by sending a restapi request to the cluster management side.
The restapi request matches the content of the current recording operation restapi in step S2.
Specifically, step S31 includes the following process:
s311: and judging whether the communication states of the server side and the cluster management side are normal or not.
The communication state in this embodiment includes: RestAPI interface status and network status.
If the communication status of the server and the cluster manager is normal, step S312 is executed: and judging that the cluster management service is normal.
When the cluster management service is normal, step S313 is executed: and the server side sends a restapi request to the cluster management side.
S314: and the cluster management terminal synchronizes the data of the current server in the cluster management with the data of the current server after the operation record according to the restapi request.
As shown in steps S313-S314, when the cluster management service is normal, the restapi request can be processed normally, and at this time, the cluster management end processes the restapi request, but does not issue a real command to the bottom layer, and only performs data operation, so as to synchronize the data of the server in the cluster management with the data in the single service.
If the communication status of the server side and the cluster management side is not normal, execute step S315: it is determined that the cluster management service is not normal.
When the cluster management service is abnormal, step S316 is executed: and the server monitors the management service until the cluster management service is normal, and the server sends a restapi request to the cluster management terminal.
And performs step S341 for data synchronization.
After the Restapi process is completed, step S317 is executed: and clearing the records in the server-side api record storage table.
Namely, the records in the database table of the server side are deleted, and the accuracy of subsequent data synchronization can be improved and the utilization rate of the resource space of the server can be improved by emptying the records.
The bidirectional data synchronization between the server and the cluster manager, in addition to the data synchronization from the server to the cluster manager in step S31, further includes step S32: and the cluster management end synchronizes the operation records of the cluster management end to the server end according to the acquired restapi request.
Specifically, step S32 includes the following processes:
s321: and the cluster management terminal judges whether the request is any one of a post interface, a put interface and a delete interface according to the acquired restapi request.
If the interface is any one of the post interface, the put interface and the delete interface, step S322 is executed: and judging whether the server sending the restapi request is online or not.
If the server that sent the restapi request is online, step S323 is performed: sending a restapi request responding to the same to a server sending the restapi request;
if the server sending the restapi request is offline, step S324 is executed: no response is made to the server that sent the restapi request.
As can be seen from the above steps S321-S324, when the cluster management end receives the restapip process, and the type is a post interface, a put interface, or a delete interface, the same restapip is sent to the corresponding host at the same time; when the host is off-line, the request is abandoned, and the processing of the cluster side to the off-line host is failed, so that the condition that the data is inconsistent is ensured to be only generated at a single server side.
Further, the method of this embodiment further includes, when the post interface and the delete interface operate the same resource, deleting the operation record at both the post interface and the delete interface, where the resource includes: information, storage, and networks. By deleting the operation records, the times of data synchronization can be reduced, the data synchronization efficiency is improved, the single-server management efficiency is further improved, and the high availability of cluster management is improved.
The method of the embodiment further comprises the following steps: when the resources are merged, the bottom layer resource uuid is utilized to judge whether the resources to be merged are the same resource at the server side and the cluster management side; if yes, merging the resources into one resource; if not, no merging is performed. That is to say, in the data synchronization process, when resources are merged, only one resource exists in the cluster management, but each host may exist on the server side, and it needs to be ensured that the system can recognize that the resources are the same. In the embodiment, the bottom-layer resource uuid can be used as the unique identifier, so that whether the resource uuid is the same resource or not can be judged quickly and accurately, and the accuracy and the efficiency of data synchronization are improved.
Example two
Referring to fig. 2 based on the embodiment shown in fig. 1, fig. 2 is a schematic structural diagram of a management system of a single server in a server cluster according to an embodiment of the present application. As can be seen from fig. 2, the management system for a single server in a server cluster in this embodiment mainly includes: the system comprises a management service starting module, a recording module and a data synchronization module.
The management service starting module is used for starting the management services of a plurality of servers by using a RestAPI interface according to the acquired command, the management services are used for single machine management, and the RestAPI interface comprises: post interface, put interface, and delete interface. And the recording module is used for operating and recording any server in a form of saving restapi. The data synchronization module is used for performing data synchronization at the server end and the cluster management end in a mode of sending a restapi request, wherein each server of the server end comprises a server end database, the server database is used for storing host information and an api record storage table of the current server, and the host information comprises: virtual machine information on the host, host network information, and host storage information.
The server cluster in this embodiment includes: the single server is any server which is free from the server cluster when the cluster management end fails.
Wherein, the data synchronization module includes: a first synchronization unit and a second synchronization unit. The first synchronization unit is arranged at the server side, and the second synchronization unit is arranged at the cluster management side. The first synchronization unit is used for synchronizing the operation records to the cluster management end by sending a restapi request to the cluster management end at the server end after any server performs the operation records in a restapi storage mode; and the second synchronization unit is used for synchronizing the cluster management end operation records to the current server end according to the acquired restapi request.
Further, the first synchronization unit includes: the system comprises a first judgment subunit, a restapi request sending subunit, a synchronization subunit, a monitoring subunit and an emptying subunit. The first judging subunit is used for judging whether the communication states of the server side and the cluster management side are normal or not, if the communication states of the server side and the cluster management side are normal, judging that the cluster management service is normal, and if not, judging that the cluster management service is abnormal. And the restapi request sending subunit is used for controlling the current server side to send a restapi request to the cluster management side when the cluster management service is normal. And the synchronization subunit is used for synchronizing the data of the current server in the cluster management with the data of the current server after the operation record according to the restapi request. And the monitoring subunit is used for monitoring the management service when the communication states of the server side and the cluster management side are abnormal. The restapi request sending subunit is further configured to send a restapi request to the cluster management end by the current server end after the monitoring subunit monitors that the cluster management service is normal. And the emptying subunit is used for emptying the records in the server-side api record saving table after the restapi processing is finished.
The second synchronization unit includes: the second judging subunit, the third judging subunit and the response subunit. And the second judging subunit is configured to judge, by the cluster management end according to the obtained restapi request, whether the request is any one of a post interface, a put interface, and a delete interface. And the third judging subunit is used for judging whether the server sending the restapi request is online or not when the server is any one of the post interface, the put interface and the delete interface. The response subunit is used for sending the same restapi request to the server sending the restapi request if the server sending the restapi request is online; if the server that sent the restapi request is offline, no response is made to the server that sent the restapi request.
The working principle and the working method of the management system of a single server in the server cluster in this embodiment have been explained in detail in the embodiment shown in fig. 1, and are not described herein again.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for managing a single server in a server cluster, the server cluster comprising: the method comprises the following steps that a server side and a cluster management side are provided with the same restapi protocol, the server side comprises a plurality of servers, and a single server is any one of the servers which are free from a server cluster when the cluster management side fails, and the method comprises the following steps:
according to the acquired command, a RestAPI interface is used for starting management services of a plurality of servers, the management services are used for single machine management, and the RestAPI interface comprises: a post interface, a put interface and a delete interface;
any server performs operation recording in a form of saving restapi;
the server and the cluster management end perform data synchronization by sending a restapi request, wherein each server of the server comprises a server database, the server database is used for storing host information and an api record storage table of the current server, and the host information comprises: virtual machine information on the host, host network information, and host storage information.
2. The method for managing the single server in the server cluster according to claim 1, wherein any one of the servers performs operation recording in a form of storing restapi, specifically:
when any RestAPI interface is called, any server inserts a record into an api record storage table, and the record is used for recording the content of operation RestAPI.
3. The method for managing the single server in the server cluster according to claim 1, wherein the server side and the cluster management side perform data synchronization by sending a restapi request, and the method comprises:
after any server performs operation recording in a form of saving restapi, the server side synchronizes the operation recording to the cluster management side by sending a restapi request to the cluster management side;
and the cluster management end synchronizes the operation records of the cluster management end to the server end according to the acquired restapi request.
4. The method for managing the single server in the server cluster according to claim 3, wherein the server side synchronizes the operation record to the cluster management side by sending a restapi request to the cluster management side, and the method comprises:
judging whether the communication states of the server side and the cluster management side are normal or not;
if the communication states of the server side and the cluster management side are normal, judging that the cluster management service is normal;
the server side sends a restapi request to the cluster management side;
the cluster management terminal synchronizes the data of the current server in cluster management with the data of the current server after operation recording according to the restapi request;
if the communication states of the server side and the cluster management side are abnormal, judging that the cluster management service is abnormal;
the server monitors the management service until the cluster management service is normal, and then the server sends a restapi request to the cluster management terminal;
and after the Restapi processing is finished, clearing the records in the api record saving table of the server side.
5. The method for managing the single server in the server cluster according to claim 3, wherein the cluster management terminal synchronizes the cluster management terminal operation record to the server terminal according to the obtained restapi request, and the method comprises the following steps:
the cluster management terminal judges whether the request is any one of a post interface, a put interface and a delete interface according to the acquired restapi request;
if yes, judging whether a server sending the restapi request is online or not;
if the server sending the restapi request is online, sending the same restapi request to the server sending the restapi request;
and if the server sending the restapi request is offline, not responding to the server sending the restapi request.
6. The method for managing the single server in the server cluster according to claim 1, wherein the method further comprises:
when the same resource is operated by the post interface and the delete interface, the operation records are deleted on both the post interface and the delete interface, and the resource comprises: information, storage, and networks.
7. The method for managing the single server in the server cluster according to claim 1, wherein the method further comprises:
when the resources are merged, the bottom layer resource uuid is utilized to judge whether the resources to be merged are the same resource at the server side and the cluster management side;
if yes, merging the resources into one resource;
if not, no merging is performed.
8. A management system for a single server in a server cluster is characterized in that the server cluster comprises: the system comprises a server side and a cluster management side, wherein the server side and the cluster management side have the same restapi protocol, and a single server is any one server dissociated from a server cluster when the cluster management side fails, and the system comprises:
a management service starting module, configured to start management services of multiple servers according to the obtained command by using a RestAPI interface, where the management services are used for stand-alone management, and the RestAPI interface includes: a post interface, a put interface and a delete interface;
the recording module is used for carrying out operation recording on any server in a form of saving restapi;
the data synchronization module is used for performing data synchronization at the server side and the cluster management side by sending a restapi request, wherein each server of the server side comprises a server side database, the server side database is used for storing host information and an api record storage table of the current server, and the host information comprises: virtual machine information on the host, host network information, and host storage information.
9. The system for managing single servers in a server cluster according to claim 8, wherein the data synchronization module comprises:
the first synchronization unit is used for synchronizing the operation records to the cluster management end by sending a restapi request to the cluster management end at the server end after any server performs the operation records in a restapi storage mode;
and the second synchronization unit is used for synchronizing the cluster management end operation records to the current server end according to the acquired restapi request.
10. The system for managing single servers in a server cluster according to claim 9, wherein the first synchronization unit comprises:
the first judging subunit is used for judging whether the communication states of the server side and the cluster management side are normal or not, if the communication states of the server side and the cluster management side are normal, judging that the cluster management service is normal, and if not, judging that the cluster management service is abnormal;
the restapi request sending subunit is used for controlling the current server side to send a restapi request to the cluster management side when the cluster management service is normal;
the synchronization subunit is used for synchronizing the data of the current server in cluster management with the data of the current server after operation recording according to the restapi request;
the monitoring subunit is used for monitoring the management service when the communication states of the server side and the cluster management side are abnormal;
the restapi request sending subunit is further configured to send a restapi request to the cluster management end by the current server end after the monitoring subunit monitors that the cluster management service is normal;
and the emptying subunit is used for emptying the records in the server-side api record saving table after the restapi processing is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010748830.8A CN111988367B (en) | 2020-07-30 | 2020-07-30 | Method and system for managing single server in server cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010748830.8A CN111988367B (en) | 2020-07-30 | 2020-07-30 | Method and system for managing single server in server cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111988367A CN111988367A (en) | 2020-11-24 |
| CN111988367B true CN111988367B (en) | 2022-05-10 |
Family
ID=73444730
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010748830.8A Active CN111988367B (en) | 2020-07-30 | 2020-07-30 | Method and system for managing single server in server cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111988367B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107329799A (en) * | 2017-05-22 | 2017-11-07 | 国网安徽省电力公司信息通信分公司 | A kind of fusion Docker containers and the system of KVM virtualization technology |
| CN107959588A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | Cloud resource management method, cloud resource management platform and the management system of data center |
| CN108170510A (en) * | 2017-12-22 | 2018-06-15 | 天津津航计算技术研究所 | A kind of managing computing resources system based on virtualization technology |
| CN109284170A (en) * | 2018-09-11 | 2019-01-29 | 山东观海数据技术有限公司 | USB shared system and sharing method in a kind of local area network |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8856337B2 (en) * | 2011-08-16 | 2014-10-07 | Hitachi, Ltd. | Method and apparatus of cluster system provisioning for virtual maching environment |
| CN105357038B (en) * | 2015-10-26 | 2019-05-07 | 北京百度网讯科技有限公司 | Monitor the method and system of cluster virtual machine |
-
2020
- 2020-07-30 CN CN202010748830.8A patent/CN111988367B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107329799A (en) * | 2017-05-22 | 2017-11-07 | 国网安徽省电力公司信息通信分公司 | A kind of fusion Docker containers and the system of KVM virtualization technology |
| CN107959588A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | Cloud resource management method, cloud resource management platform and the management system of data center |
| CN108170510A (en) * | 2017-12-22 | 2018-06-15 | 天津津航计算技术研究所 | A kind of managing computing resources system based on virtualization technology |
| CN109284170A (en) * | 2018-09-11 | 2019-01-29 | 山东观海数据技术有限公司 | USB shared system and sharing method in a kind of local area network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111988367A (en) | 2020-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102981931B (en) | Backup method and device for virtual machine | |
| WO2020248507A1 (en) | Container cloud-based system resource monitoring method and related device | |
| WO2022063322A1 (en) | Hard drive migration method, distributed storage cluster system and storage medium | |
| CN106936623A (en) | The management method of distributed cache system and cache cluster | |
| CN107368369B (en) | Distributed container management method and system | |
| CN103024065A (en) | System configuration management method for cloud storage system | |
| CN105471622A (en) | High-availability method and system for main/standby control node switching based on Galera | |
| CN110113406B (en) | Distributed computing service cluster system | |
| CN107404509A (en) | Distributed Services configure system and approaches to IM | |
| CN110401651A (en) | A kind of distributed type assemblies node monitoring method, apparatus and system | |
| CN106331081B (en) | Information synchronization method and device | |
| CN111752488B (en) | Management method and device of storage cluster, management node and storage medium | |
| CN104793981B (en) | A kind of online snapshot management method and device of cluster virtual machine | |
| CN107357800A (en) | A kind of database High Availabitity zero loses solution method | |
| CN117130730A (en) | Metadata management method for federal Kubernetes cluster | |
| CN115001990A (en) | Cross-region openstack cluster management method and system based on declarative API | |
| CN108733808B (en) | Big data software system switching method, system, terminal equipment and storage medium | |
| CN111988367B (en) | Method and system for managing single server in server cluster | |
| CN113835834A (en) | K8S container cluster-based computing node capacity expansion method and system | |
| CN113438111A (en) | Method for restoring RabbitMQ network partition based on Raft distribution and application | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN111917588A (en) | Edge device management method, device, edge gateway device and storage medium | |
| CN113765690A (en) | Cluster switching method, system, device, terminal, server and storage medium | |
| CN108984602B (en) | Database control method and database system | |
| CN116132517A (en) | Offline working and local area network data intercommunication method based on airport client |
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 |