CN117118814A - Cloud resource switching method, device, equipment and medium based on multi-cloud management platform - Google Patents
Cloud resource switching method, device, equipment and medium based on multi-cloud management platform Download PDFInfo
- Publication number
- CN117118814A CN117118814A CN202311003319.5A CN202311003319A CN117118814A CN 117118814 A CN117118814 A CN 117118814A CN 202311003319 A CN202311003319 A CN 202311003319A CN 117118814 A CN117118814 A CN 117118814A
- Authority
- CN
- China
- Prior art keywords
- cloud
- domain name
- service
- access domain
- target
- 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
- 238000000034 method Methods 0.000 title claims abstract description 78
- 238000003032 molecular docking Methods 0.000 claims abstract description 9
- 230000008569 process Effects 0.000 claims description 16
- 230000004044 response Effects 0.000 claims description 13
- 230000007246 mechanism Effects 0.000 claims description 8
- 210000001503 joint Anatomy 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000035800 maturation Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
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
- 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/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a cloud resource switching method, device, equipment and medium based on a multi-cloud management platform, and belongs to the technical field of computers. The method comprises the following steps: acquiring an access domain name of a service interface docking of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching triggering condition; under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name; starting analysis of the target cloud server, and closing analysis of the current cloud server; and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal. According to the technical scheme, the fast switching from the fault cloud to the target cloud can be realized through the multi-cloud management platform under the condition of multi-cloud service, so that the service safety and the service robustness of the enterprise user are ensured.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a cloud resource switching method, device, equipment and medium based on a multi-cloud management platform.
Background
With the rapid development of technology level, cloud computing has become one of the main choices for individual enterprise management and hosting services. With the continuous development and maturation of cloud computing technology, more and more enterprise users host their business on cloud servers.
However, if a cloud provider's machine room fails, it can be an important challenge for enterprise users. These faults may cause interruption of the service of the user, causing serious losses. For enterprise users relying on a single cloud provider, once the provider fails, the business is severely impacted. Therefore, how to provide a stable cloud service manner for enterprise users is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application aims to provide a cloud resource switching method, device, equipment and medium based on a multi-cloud management platform, which solve the problem that service is affected due to machine room faults existing in a cloud provider in the prior art, ensure that enterprise users can realize rapid switching from fault cloud to target cloud through the multi-cloud management platform under the condition of multi-cloud service, and further ensure the safety and robustness of the service of the enterprise users.
In a first aspect, an embodiment of the present application provides a cloud resource switching method based on a multi-cloud management platform, where the multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; the method comprises the following steps:
acquiring an access domain name of a service interface docking of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching triggering condition;
under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name;
starting analysis of the target cloud server, and closing analysis of the current cloud server;
and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal.
Further, the process of identifying that the access domain name meets the preset condition includes:
identifying a number of clouds pre-deployed for the access domain name;
under the condition that the number of the clouds is one, determining that the access domain name does not meet a preset condition;
and under the condition that the number of the clouds is at least two, determining that the access domain name meets the preset condition.
Further, before determining the target cloud service end according to the access domain name, the method further includes:
under the condition that the number of the clouds deployed in advance for the access domain name is at least two, constructing a multi-cloud deployment association relationship for the access domain name; the association relation is obtained by writing address information of at least two cloud servers;
correspondingly, determining the target cloud server according to the access domain name comprises:
and determining a target cloud server from address information of the incidence relation according to the incidence relation of the multi-cloud deployment of the access domain name.
Further, after the parsing of the target cloud server is started and the parsing of the current cloud server is closed, the method further includes:
and synchronizing a response mechanism for responding to the access domain name of the request terminal through the service interface of the target cloud service terminal into the HTTPDNS so as to analyze the access domain name of the request terminal through the HTTPDNS.
Further, the multi-cloud management platform establishes a synchronization mechanism between databases of at least two cloud servers;
correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps:
acquiring a database read-write request to be processed by a service interface of the current cloud service end;
and sending the database read-write request to be processed to a service interface of the target cloud server so as to respond to the database read-write request to be processed based on the database of the target cloud server.
Further, before the database read-write request to be processed is sent to the service interface of the target cloud service end, the method further includes:
and searching and killing the database read-write request to be processed of the current cloud server.
Further, the at least two cloud service ends are connected to the same database;
correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps:
acquiring a database read-write request to be processed by a service interface of the current cloud service end;
and sending the database read-write request to be processed to a service interface of the target cloud server to perform read-write operation on the database based on the target cloud server so as to complete response to the database read-write request to be processed.
In a second aspect, an embodiment of the present application provides a cloud resource switching device based on a multi-cloud management platform, where the multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; the device comprises:
the access domain name acquisition module is used for acquiring an access domain name of the service interface butt joint of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching trigger condition;
the switching target determining module is used for determining a target cloud server according to the access domain name under the condition that the access domain name is identified to meet the preset condition;
the analysis management module is used for starting the analysis of the target cloud server and closing the analysis of the current cloud server;
and the flow switching module is used for receiving the access domain name of the request end, analyzing to obtain a service interface of the target cloud service end, and responding through the target cloud service end.
In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the steps of the method according to the first aspect when executed by the processor.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor perform the steps of the method according to the first aspect.
In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and where the processor is configured to execute a program or instructions to implement a method according to the first aspect.
In the embodiment of the application, the multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; the method comprises the following steps: acquiring an access domain name of a service interface docking of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching triggering condition; under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name; starting analysis of the target cloud server, and closing analysis of the current cloud server; and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal. By the cloud resource switching method based on the multi-cloud management platform, whether the current cloud has faults or not can be identified through the multi-cloud management platform under the condition of multi-cloud service, the target cloud is determined under the condition that switching is needed, and the rapid switching from the fault cloud to the target cloud is realized, so that the safety and the robustness of the business of the enterprise user are ensured.
Drawings
Fig. 1 is a schematic flow chart of a cloud resource switching method based on a multi-cloud management platform according to an embodiment of the present application;
fig. 2 is a flow chart of a cloud resource switching method based on a multi-cloud management platform according to a second embodiment of the present application;
fig. 3 is a schematic structural diagram of a cloud resource switching device based on a multi-cloud management platform according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the following detailed description of specific embodiments of the present application is given with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the matters related to the present application are shown in the accompanying drawings. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are obtained by a person skilled in the art based on the embodiments of the present application, fall within the scope of protection of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type, and are not limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
The cloud resource switching method, device, equipment and medium based on the multi-cloud management platform provided by the embodiment of the application are described in detail through specific embodiments and application scenes thereof with reference to the accompanying drawings.
Example 1
Fig. 1 is a flow chart of a cloud resource switching method based on a multi-cloud management platform according to an embodiment of the present application. The multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; as shown in fig. 1, the method specifically comprises the following steps:
s101, under the condition that a current cloud service end connected with the request end meets a switching trigger condition, acquiring an access domain name of service interface butt joint of the current cloud service end.
Firstly, the scheme can be a use scene of providing services for enterprise users through at least two cloud service ends. The multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends.
Based on the above usage scenario, it can be understood that the execution subject of the present application may be the intelligent terminal, or may be a processor running software or editing pages in the intelligent terminal, which is not limited herein too.
In the scheme, the multi-cloud management platform can be compatible with APIs (Application Programming Interface, application programming interfaces) and services of a plurality of mainstream cloud providers, such as Tencent cloud, ali cloud, overseas cloud services and the like, so as to ensure that users can switch among different cloud platforms. The multi-cloud management platform supports virtual machines, storage, networking, and other SAAS (Software As A Service, software operating services) services of different cloud providers, and the like.
The request end can be a client end, or can be some intelligent terminal equipment which can be connected with the cloud service end, such as a computer, a tablet personal computer, a smart phone and the like.
The request end can send out a request to the cloud service end through connection, and the request can comprise login, registration, recharging and the like. Taking a game development enterprise user as an example, the game development enterprise user can deploy micro services on one or more cloud service ends, so that in the process of logging in by a game player, a login condition can be sent to the cloud service ends through connection, if the user name and the password are verified successfully, the login operation is completed, and further, the next service request is sent, for example, a game service request is sent, or a recharging service request is sent.
In this scheme, the current cloud server may be the cloud server to which the requesting peer is being connected. The current cloud service end can be used for responding to the request sent by the request end, such as login, recharging and other requests.
The condition that the switching trigger condition is met may be that the current cloud server is identified to fail, or that the current cloud server needs gray level deployment, for example, upgrading the current cloud server.
And under the condition that the switching triggering condition is met, acquiring the access domain name of the service interface docking of the current cloud service end. Wherein the service interface may be an interface of a request-side connection. The access domain name that the server receives can be a domain name used when the server makes a request, for example www.***.com. It can be appreciated that if the current cloud server fails, the interface is also unable to respond if it is also docked with other domain names. Thus, the access domain name interfaced by the service interface herein may be a plurality of domain names. Since the processing modes of other domain names are consistent with the processing mode of the access domain name sent by the request end, the scheme only uses the access domain name sent by the request end for explanation, and the other domain names can be processed by referring to the processing mode.
S102, determining a target cloud server according to the access domain name under the condition that the access domain name is identified to meet the preset condition.
And identifying whether the domain name meets the preset condition. The preset condition here may be a condition that the domain name is deployed at a plurality of cloud servers. For example, the interface a of the cloud service a may respond to accessing the domain name www.***.com, and then it needs to determine whether to perform cloudy deployment on the domain name in advance. If the access domain name www.***.com is also deployed on the interface B of the cloud server B, it may be determined that the preset condition is satisfied.
In this scheme, specifically, the process of identifying that the access domain name meets the preset condition includes:
identifying a number of clouds pre-deployed for the access domain name;
under the condition that the number of the clouds is one, determining that the access domain name does not meet a preset condition;
and under the condition that the number of the clouds is at least two, determining that the access domain name meets the preset condition.
The number of the clouds which are deployed in advance and access to the domain name can be stored in a fixed position, and can be identified when a fault is identified, and a specific identification mode, a reading mode of the fixed position and the like can be determined based on the design of the multi-cloud management platform, and are not repeated here.
According to the method and the device, whether the preset conditions are met or not is determined through the number of the cloud deployed in advance for the access domain name, and through the arrangement, whether the conditions are met or not can be pre-checked before switching, so that accurate switching operation can be ensured.
It can be understood that, when the preset condition is satisfied, the target cloud server is determined according to the access domain name. Specifically, among the plurality of cloud servers that are pre-deployed with the access domain name, other cloud servers than the current cloud server may be selected. The basis selected may be numerous, such as according to load conditions, according to deployment sequence, and so forth.
S103, starting analysis of the target cloud server, and closing analysis of the current cloud server.
It can be understood that after the request end sends out the access domain name, the DNS address of the service interface of the cloud service end needs to be obtained through resolving, so that the service interface connection with the cloud service end is completed. After the target cloud server is determined, the resolution of the target cloud server can be started, the resolution of the current cloud server is closed, namely the access domain name www.***.com is received, the original DNS address which is resolved to be 1.1.1.1 is closed, and the resolution of the target cloud server is started, namely the resolution of the target cloud server is 2.2.2.2. And switching the current cloud service end with the fault to the normal target cloud service end.
S104, receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal.
Here, after the request end sends out the access domain name, the multi-cloud management platform may parse the service interface to the target cloud service end according to the previously opened parsing to perform the response to the request end.
According to the technical scheme provided by the embodiment, under the condition that the current cloud service end connected with the request end meets the switching trigger condition, the access domain name of the service interface docking of the current cloud service end is obtained; under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name; starting analysis of the target cloud server, and closing analysis of the current cloud server; and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal. By executing the scheme, the enterprise user can identify whether the current cloud has faults or not through the multi-cloud management platform under the condition of multi-cloud service, and under the condition that switching is needed, the target cloud is determined, and the rapid switching from the fault cloud to the target cloud is realized, so that the safety and the robustness of the business of the enterprise user are ensured.
It will be appreciated that the enterprise users herein may be large, medium or small enterprises, and may be other users that need to provide services through a cloud service, such as personal users, other organizational users, and so on. Based on the above, any service that needs to be provided through the cloud service end can be used as a user of the scheme.
Based on the above technical solutions, optionally, before determining the target cloud server according to the access domain name, the method further includes:
under the condition that the number of the clouds deployed in advance for the access domain name is at least two, constructing a multi-cloud deployment association relationship for the access domain name; the association relation is obtained by writing address information of at least two cloud servers;
correspondingly, determining the target cloud server according to the access domain name comprises:
and determining a target cloud server from address information of the incidence relation according to the incidence relation of the multi-cloud deployment of the access domain name.
In this solution, in the case that the number of clouds that are deployed in advance for an access domain name is at least two, a multi-cloud deployment association relationship may be constructed for the access domain name, for example, there is one access domain name www.***.com, which is at three cloud service ends, and then the addresses of service interfaces of the three cloud service ends that are deployed in the access domain name may be associated, for example, 1.1.1.1-/-2.2.2.2-/-3.3.3.3.
In the case of an association, after 1.1.1.1 fails, 2.2.2 or 3.3.3.3 may be determined to serve the access domain name based on the association.
The method and the device can be used for rapidly determining the target cloud service end, improving the switching speed, completing the operation of switching from the fault cloud to the target cloud in the shortest time, providing service guarantee for users, and enabling the loss of the users caused by the fault of the cloud service end to be the lowest.
Based on the above technical solutions, optionally, after the parsing of the target cloud server is turned on and the parsing of the current cloud server is turned off, the method further includes:
and synchronizing a response mechanism for responding to the access domain name of the request terminal through the service interface of the target cloud service terminal into the HTTPDNS so as to analyze the access domain name of the request terminal through the HTTPDNS.
The HTTPDNS uses the HTTP protocol to request the DNS server instead of the traditional DNS protocol to request the DNS server by using the UDP protocol, thereby bypassing the Local DNS of the operator, simplifying the complexity of the request and avoiding the hijacking and cross-network problems caused by using the Local DNS of the operator. The http dns workflow may be that the client directly accesses the http dns interface to obtain the IP with the optimal access delay configured by the service on the domain name configuration management platform. After the IP is obtained, a service protocol request is directly sent to the IP. Taking HTTP requests as an example, by specifying a host field in the header, a standard HTTP request may be sent to the IP returned by the HTTP dns.
In the scheme, when the client sends out the access domain name, the domain name resolution is to resolve the IP address, and the self-developed HTTPDNS is used for switching and synchronizing to the HTTPDNS service, so that the current service can be recovered more quickly.
Example two
Fig. 2 is a schematic flow chart of a cloud resource switching device based on a multi-cloud management platform according to a second embodiment of the present application. The scheme makes better improvement on the embodiment, and the specific improvement is as follows: the multi-cloud management platform establishes a synchronization mechanism between databases of at least two cloud servers; correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps: acquiring a database read-write request to be processed by a service interface of the current cloud service end; and sending the database read-write request to be processed to a service interface of the target cloud server so as to respond to the database read-write request to be processed based on the database of the target cloud server.
As shown in fig. 2, the method specifically comprises the following steps:
s201, under the condition that the current cloud service end connected with the request end meets the switching trigger condition, an access domain name of the service interface docking of the current cloud service end is obtained.
S202, determining a target cloud server according to the access domain name under the condition that the access domain name is identified to meet a preset condition; and performs S203 or S205.
S203, acquiring a database read-write request to be processed by a service interface of the current cloud server.
The multi-cloud management platform establishes a synchronization mechanism between databases of at least two cloud servers. That is, the cloud server a is connected to the database A1, and the cloud server B is connected to the database B1. The multi-cloud management platform may synchronize the database A1 and the database B1 according to a preset rule.
Under the condition that the current cloud server is identified to have faults, the database read-write request which is not processed yet, namely the database read-write request to be processed, can be identified.
S204, the database read-write request to be processed is sent to a service interface of the target cloud server, so that the database read-write request to be processed is responded based on the database of the target cloud server.
In this scheme, since the data of the database A1 and the database B1 are synchronous, if there is an unprocessed database read-write request for the cloud server a, the processing can be implemented by the cloud server B.
In this scheme, the request end may resend the database read-write request that the cloud server a does not respond to the cloud server B. Therefore, the method and the device can send the database read-write request to be processed to the service interface of the target cloud server, and respond to the database read-write request to be processed based on the database of the target cloud server.
S205, starting analysis of the target cloud server, and closing analysis of the current cloud server.
S206, receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal.
The embodiment provides a data service scheduling based on the above embodiment, that is, switching from the fault cloud service end response data service to the target cloud service end response data service, so that the accuracy and timeliness of the response to the data access request of the request end can be ensured.
On the basis of the foregoing embodiment, optionally, before sending the pending database read-write request to a service interface of the target cloud service end, the method further includes:
and searching and killing the database read-write request to be processed of the current cloud server.
According to the technical scheme, the read-write operation of the current cloud server on the database read-write requests to be processed in stock can be avoided through the checking and killing operation, and the execution of the read-write operation can be avoided under the condition that the current cloud server has faults, so that errors are introduced into the database, and the accurate response of the database to the data requests is affected.
The embodiment can improve the data accuracy of the database and avoid unnecessary influence caused by the fact that the database error is introduced by the fault cloud service end.
On the basis of the technical scheme, optionally, the at least two cloud service ends are connected to the same database;
correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps:
acquiring a database read-write request to be processed by a service interface of the current cloud service end;
and sending the database read-write request to be processed to a service interface of the target cloud server to perform read-write operation on the database based on the target cloud server so as to complete response to the database read-write request to be processed.
The database can be connected with a plurality of cloud service ends, so that when one cloud service end has a fault, the database can be subjected to data reading and writing operation through the other cloud service end to complete the response of the database reading and writing request.
By the arrangement, the response to the database read-write request can still be correct through the target cloud server under the condition that the cloud server fails, and the normal operation of business of enterprise users is ensured.
For clarity of illustration, the present embodiment also provides a preferred implementation. The method comprises the following steps:
(1) the current cloud server machine room level fault occurs;
(2) the multi-cloud management platform automatically senses faults and analyzes and locates the cloud provider with the faults;
here, specifically, the fault may be located first according to the service scenario. For example, in the case where two clouds serve enterprise users simultaneously, one of which provides 90% of the service and the other of which provides 10% of the service. At this time, the failure can be determined by identifying that the packet loss reaches 20%, or by analyzing the service, if the state is abnormal, such as a state code, the connection database is overtime, has errors, the login success rate is reduced, the recharging success rate is reduced, and the like, the failure can be determined.
(3) The multi-cloud management platform analyzes the service damage proportion, and when a preset threshold value is reached, switching is executed according to a preset strategy;
(4) when a cloud provider is found to have a great number of service overtime and influence user service, executing one-key switching through a platform;
(1) Acquiring a domain name related record;
(2) Switching pre-inspection;
(3) Starting target cloud analysis and stopping fault cloud analysis;
(4) Synchronizing the HTTPDNS;
(5) in the aspect of an application data layer, the platform also executes automatic switching to schedule the data read-write request of the application to the data service of the target cloud; the method comprises the following specific steps:
(1) The platform blocks the read-write request of the fault cloud data service through a network strategy;
(2) The platform searches and kills stock application connection of the fault cloud data service;
(3) The platform puts through a network strategy of the target cloud data service, and allows the application to initiate a read-write request;
(4) The platform schedules application requests to the target cloud data service.
(6) Completing switching and outputting a switching result;
(7) the service is restored to normal.
The multi-cloud management platform provided by the scheme aims at rapidly responding to faults of a cloud provider level and achieving service recovery in a short time. Through a systematic switching and scheduling mechanism, the scheme can complete service switching within 15 minutes and schedule the user request to the standby cloud provider.
Example III
Fig. 3 is a schematic structural diagram of a cloud resource switching device based on a multi-cloud management platform according to a third embodiment of the present application. As shown in fig. 3, the method specifically includes the following steps:
an access domain name obtaining module 301, configured to obtain an access domain name of a service interface docking of the current cloud service end, where the current cloud service end connected with the request end meets a handover triggering condition;
the switching target determining module 302 is configured to determine a target cloud server according to the access domain name if the access domain name is identified to meet a preset condition;
the resolution management module 303 is configured to turn on resolution of the target cloud server, and turn off resolution of the current cloud server;
the flow switching module 304 is configured to receive the access domain name of the request end, and parse the access domain name to obtain a service interface of the target cloud service end, so as to respond through the target cloud service end.
In the embodiment of the application, under the condition that the current cloud service end connected with the request end meets the switching trigger condition, the access domain name of the service interface docking of the current cloud service end is obtained; under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name; starting analysis of the target cloud server, and closing analysis of the current cloud server; and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal. According to the method and the system, whether the current cloud has faults or not can be identified through the multi-cloud management platform under the condition of multi-cloud service, the target cloud is determined under the condition that switching is needed, and the rapid switching from the fault cloud to the target cloud is realized, so that the safety and the robustness of the business of the enterprise user are ensured.
The cloud resource switching device based on the multi-cloud management platform in the embodiment of the application can be a device, and can also be a component, an integrated circuit or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a cell phone, tablet computer, notebook computer, palm computer, vehicle mounted electronic device, wearable device, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook or personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device may be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and embodiments of the present application are not limited in particular.
The cloud resource switching device based on the multi-cloud management platform in the embodiment of the application can be a device with an operation platform. The operation platform may be an Android operation platform, an iOS operation platform, or other possible operation platforms, and the embodiment of the present application is not limited specifically.
The cloud resource switching device based on the multi-cloud management platform provided by the embodiment of the application can realize each process realized by each method embodiment, and in order to avoid repetition, the description is omitted here.
Example IV
Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application. As shown in fig. 4, the embodiment of the present application further provides an electronic device 400, which includes a processor 401, a memory 402, and a program or an instruction stored in the memory 402 and capable of running on the processor 401, where the program or the instruction implements each process of the cloud resource switching device embodiment based on the multiple cloud management platform when executed by the processor 401, and the process can achieve the same technical effect, so that repetition is avoided, and no redundant description is given here.
The electronic device in the embodiment of the application includes the mobile electronic device and the non-mobile electronic device.
Example five
The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the cloud resource switching device embodiment based on the multi-cloud management platform, and can achieve the same technical effect, so that repetition is avoided, and no redundant description is provided herein.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
Example six
The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running programs or instructions, the processes of the cloud resource switching device embodiment based on the multi-cloud management platform can be realized, the same technical effects can be achieved, and the repetition is avoided, so that the description is omitted.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as platform-level chips, platform chips, chip platforms, or platform-on-chip chips, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.
The foregoing description is only of the preferred embodiments of the application and the technical principles employed. The present application is not limited to the specific embodiments described herein, but is capable of numerous modifications, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, while the application has been described in connection with the above embodiments, the application is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit of the application, the scope of which is set forth in the following claims.
Claims (10)
1. The cloud resource switching method based on the multi-cloud management platform is characterized in that the multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; the method comprises the following steps:
acquiring an access domain name of a service interface docking of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching triggering condition;
under the condition that the access domain name meets the preset condition, determining a target cloud server according to the access domain name;
starting analysis of the target cloud server, and closing analysis of the current cloud server;
and receiving the access domain name of the request terminal, and analyzing to obtain a service interface of the target cloud service terminal so as to respond through the target cloud service terminal.
2. The cloud resource switching method based on the multiple cloud management platform according to claim 1, wherein the process of identifying that the access domain name meets a preset condition comprises:
identifying a number of clouds pre-deployed for the access domain name;
under the condition that the number of the clouds is one, determining that the access domain name does not meet a preset condition;
and under the condition that the number of the clouds is at least two, determining that the access domain name meets the preset condition.
3. The cloud resource switching method based on a multiple cloud management platform according to claim 2, wherein before determining a target cloud service according to the access domain name, the method further comprises:
under the condition that the number of the clouds deployed in advance for the access domain name is at least two, constructing a multi-cloud deployment association relationship for the access domain name; the association relation is obtained by writing address information of at least two cloud servers;
correspondingly, determining the target cloud server according to the access domain name comprises:
and determining a target cloud server from address information of the incidence relation according to the incidence relation of the multi-cloud deployment of the access domain name.
4. The cloud resource switching method based on the multiple cloud management platforms according to claim 1, wherein after starting the resolution of the target cloud service and closing the resolution of the current cloud service, the method further comprises:
and synchronizing a response mechanism for responding to the access domain name of the request terminal through the service interface of the target cloud service terminal into the HTTPDNS so as to analyze the access domain name of the request terminal through the HTTPDNS.
5. The cloud resource switching method based on the multiple cloud management platform according to claim 1, wherein the multiple cloud management platform establishes a synchronization mechanism between databases of at least two cloud servers;
correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps:
acquiring a database read-write request to be processed by a service interface of the current cloud service end;
and sending the database read-write request to be processed to a service interface of the target cloud server so as to respond to the database read-write request to be processed based on the database of the target cloud server.
6. The cloud resource switching method based on the multiple cloud management platform according to claim 5, wherein before sending the pending database read-write request to the service interface of the target cloud service, the method further comprises:
and searching and killing the database read-write request to be processed of the current cloud server.
7. The cloud resource switching method based on the multi-cloud management platform according to claim 1, wherein the at least two cloud service ends are connected to the same database;
correspondingly, after determining the target cloud service end according to the access domain name, the method further comprises the following steps:
acquiring a database read-write request to be processed by a service interface of the current cloud service end;
and sending the database read-write request to be processed to a service interface of the target cloud server to perform read-write operation on the database based on the target cloud server so as to complete response to the database read-write request to be processed.
8. The cloud resource switching device based on the multi-cloud management platform is characterized in that the multi-cloud management platform is connected with a request end and at least two cloud service ends, and the request end is connected with service interfaces of the at least two cloud service ends; the device comprises:
the access domain name acquisition module is used for acquiring an access domain name of the service interface butt joint of the current cloud service end under the condition that the current cloud service end connected with the request end meets a switching trigger condition;
the switching target determining module is used for determining a target cloud server according to the access domain name under the condition that the access domain name is identified to meet the preset condition;
the analysis management module is used for starting the analysis of the target cloud server and closing the analysis of the current cloud server;
and the flow switching module is used for receiving the access domain name of the request end, analyzing to obtain a service interface of the target cloud service end, and responding through the target cloud service end.
9. An electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the cloud resource switching method based on a multi-cloud management platform as claimed in any of claims 1 to 7.
10. A readable storage medium, wherein a program or instructions are stored on the readable storage medium, which when executed by a processor, implement the steps of the cloud resource switching method based on a multi-cloud management platform as claimed in any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311003319.5A CN117118814A (en) | 2023-08-09 | 2023-08-09 | Cloud resource switching method, device, equipment and medium based on multi-cloud management platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311003319.5A CN117118814A (en) | 2023-08-09 | 2023-08-09 | Cloud resource switching method, device, equipment and medium based on multi-cloud management platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117118814A true CN117118814A (en) | 2023-11-24 |
Family
ID=88794065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311003319.5A Pending CN117118814A (en) | 2023-08-09 | 2023-08-09 | Cloud resource switching method, device, equipment and medium based on multi-cloud management platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117118814A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117478488A (en) * | 2023-12-26 | 2024-01-30 | 苏州元脑智能科技有限公司 | Cloud management platform switching system, method, equipment and medium |
-
2023
- 2023-08-09 CN CN202311003319.5A patent/CN117118814A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117478488A (en) * | 2023-12-26 | 2024-01-30 | 苏州元脑智能科技有限公司 | Cloud management platform switching system, method, equipment and medium |
| CN117478488B (en) * | 2023-12-26 | 2024-03-19 | 苏州元脑智能科技有限公司 | Cloud management platform switching system, method, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11960388B2 (en) | System and method for data collection and analysis of information relating to mobile applications | |
| KR102024694B1 (en) | Decentralized service platform using multiple service nodes based on block chain | |
| US7979734B2 (en) | Method and system for preventing service disruption of internet protocol (IP) based services due to domain name resolution failures | |
| CN104767775A (en) | Webpage application information push method and webpage application information push system | |
| CN107666493B (en) | Database configuration method and equipment thereof | |
| CN104253686A (en) | Account number login method, equipment and system | |
| CN117118814A (en) | Cloud resource switching method, device, equipment and medium based on multi-cloud management platform | |
| CN105430016A (en) | Network access authentication method and system | |
| CN110727501A (en) | Practicing method and system based on virtual machine backup data | |
| CN107580032B (en) | Data processing method, device and equipment | |
| CN106034138A (en) | Remote service calling method and remote service calling device | |
| CN116366652A (en) | Distributed application operation and maintenance method, system, device, server and gateway equipment | |
| CN112699034B (en) | Virtual login user construction method, device, equipment and storage medium | |
| CN110502238A (en) | A kind of method and device of front and back end joint debugging | |
| US11784996B2 (en) | Runtime credential requirement identification for incident response | |
| EP3297254B1 (en) | Domain name system (dns) resolution processing method and device | |
| CN111200512A (en) | Network connection disaster tolerance method, terminal device, storage medium and electronic device | |
| JP2006285453A (en) | Information processor, information processing method, and information processing program | |
| CN108769246B (en) | NFS sharing maximization test method and system | |
| US11399067B2 (en) | Network access method and apparatus for speech recognition service based on artificial intelligence | |
| CN112995648A (en) | Internet television full-flow fault diagnosis method and device and computing equipment | |
| CN116192539B (en) | Method, device, equipment and storage medium for merging data after user login | |
| CN116302711B (en) | Disaster recovery method and device based on cloud platform mirror image, electronic equipment and storage medium | |
| CN109684158A (en) | Method for monitoring state, device, equipment and the storage medium of distributed coordination system | |
| CN110213783B (en) | Base station monitoring method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |