Database instance management and control system, method, device, medium and program product

Abstract

The embodiment of the invention provides a database instance management and control system, method and device, a medium and a program product, the management and control system comprises a management and control platform, and a first cloud platform and a second cloud platform provided by different cloud service providers, and each cloud platform also runs a database instance and a management and control component. And if yes, the management and control component in the first cloud platform can respond to the management and control instruction generated by the management and control platform so as to realize management and control of the database instance running in the first cloud platform. Similarly, the second cloud platform can also respond to the management and control instruction generated by the management and control platform so as to realize management and control of the database instance running in the second cloud platform. Visibly, in the system, the arrangement of the management and control platform can realize the management and control of the database instances contained in different cloud platforms provided by different cloud service providers, namely, the unified management and control of the database instances across the cloud platforms can be conveniently realized.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and in particular to a database instance management system, method, device, medium, and program product. Background Technology

[0002] A cloud database is a database service deployed on a cloud platform. It provides users with database storage and management functions, freeing them from the burden of understanding the underlying database configuration and maintenance. Specifically, data can be stored in at least one database instance that constitutes the cloud database. Users can then manage the entire database by controlling these database instances.

[0003] In practice, considering issues such as cost and data disaster recovery, users often deploy database instances across cloud platforms provided by different cloud service providers. This dispersed deployment can increase the difficulty of managing and controlling database instances.

[0004] Therefore, improving the ease of database instance management has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a database instance management system, method, device, medium, and program product to achieve unified management and control of database instances across cloud platforms, thereby improving the convenience of database instance management and control.

[0006] In a first aspect, embodiments of the present invention provide a database instance management and control system, comprising: a management and control platform and a first cloud platform and a second cloud platform provided by different cloud service providers, wherein the cloud platforms provided by the different cloud service providers are communicatively connected to the management and control platform, and the first cloud platform and the second cloud platform run their respective database instances and management and control components;

[0007] The management and control platform is used to generate management and control instructions, which are used to operate on the database instance;

[0008] The management and control component in the first cloud platform is used to receive a first management and control instruction generated by the management and control platform; and to control the database instance in the first cloud platform according to the first management and control instruction.

[0009] The management and control component in the second cloud platform is used to receive the second management and control instructions generated by the management and control platform; and to control the database instance in the second cloud platform according to the second management and control instructions.

[0010] Secondly, embodiments of the present invention provide a database instance management system, including: a management platform and a cloud platform connected by communication, wherein the cloud platform includes a database instance and an agent management component, and the database instance runs in a server environment provided by the cloud platform;

[0011] The control platform is used to generate control instructions;

[0012] The agent management component is used to control the database instance running in the server environment according to the management instructions. Thirdly, embodiments of the present invention provide a database instance management method applied to a management platform, comprising:

[0013] Thirdly, embodiments of the present invention provide a database instance management method, including:

[0014] Send a first control instruction to the control component in the first cloud platform, so that the control component in the first cloud platform controls the database instance in the first cloud platform according to the first control instruction;

[0015] Send a second control instruction to the control component in the second cloud platform, so that the control component in the second cloud platform controls the database instance in the second cloud platform according to the second control instruction;

[0016] The first cloud platform and the second cloud platform are provided by different cloud service providers.

[0017] Fourthly, embodiments of the present invention provide an electronic device, including a processor and a memory, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the database instance management method described in the third aspect above. The electronic device may also include a communication interface for communicating with other devices or communication networks.

[0018] Fifthly, embodiments of the present invention provide a non-transitory machine-readable storage medium storing executable code, wherein when the executable code is executed by a processor of an electronic device, the processor is able to at least implement the database instance management method as described in the third aspect.

[0019] In a sixth aspect, embodiments of the present invention provide a computer program product, the computer program product including a computer program or instructions, which, when executed by a processor, causes the processor to implement the database instance management method as described in the third aspect above.

[0020] The database instance management system provided in this embodiment of the invention includes a management platform and a first cloud platform and a second cloud platform provided by different cloud service providers. Each cloud platform also runs its own database instance and management component. The management component in the first cloud platform can respond to management commands generated by the management platform to manage its internally running database instance. Similarly, the second cloud platform can also respond to management commands generated by the management platform to manage its internally running database instance.

[0021] As can be seen, in the above system, the management and control platform can be configured to manage the database instances contained in different cloud platforms provided by different cloud service providers, which means that unified management and control of database instances across cloud platforms can be easily achieved. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram of the structure of a database instance management system provided in an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of another database instance management system provided in an embodiment of the present invention;

[0025] Figure 3 This is a schematic diagram of the structure of another database instance management system provided in an embodiment of the present invention;

[0026] Figure 4 A signaling diagram of a database instance creation process provided in an embodiment of the present invention;

[0027] Figure 5 This is a schematic diagram of the structure of another database instance management system provided in an embodiment of the present invention;

[0028] Figure 6 This is a schematic diagram of the structure of another database instance management system provided in an embodiment of the present invention;

[0029] Figure 7 A schematic diagram illustrating the working process of a database instance management system provided in an embodiment of the present invention;

[0030] Figure 8 A flowchart illustrating a database instance management method provided in an embodiment of the present invention;

[0031] Figure 9 A flowchart illustrating a database instance creation method provided in an embodiment of the present invention;

[0032] Figure 10 This is a schematic diagram of the structure of a database instance management and control device provided in an embodiment of the present invention;

[0033] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0035] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0036] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0037] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to identification.” Similarly, depending on the context, the phrases “if determination” or “if identification (of the condition or event of the statement)” can be interpreted as “when determination” or “in response to determination” or “when identification (of the condition or event of the statement)” or “in response to identification (of the condition or event of the statement).”

[0038] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this invention are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0039] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes said element.

[0040] The following detailed description of some embodiments of the present invention, in conjunction with the accompanying drawings, is provided. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0041] Figure 1 This is a schematic diagram illustrating the structure of a database instance management system provided in an embodiment of the present invention. The system may include a management platform and different cloud platforms provided by different cloud service providers, each cloud platform running its own database instance and management components. The management platform and the different cloud platforms provided by different cloud service providers are communicatively connected. The management platform can generate management commands, which are used to operate on the database instances running in the cloud platforms, i.e., to control the database.

[0042] like Figure 1 As shown in the figure, two cloud platforms are schematically illustrated: a first cloud platform provided by cloud service provider 1 and a second cloud platform provided by cloud service provider 2. However, the embodiments of the present invention do not limit the number of cloud platforms in the system. That is, the management and control system provided by the embodiments of the present invention can be used to manage and control database instances in the first cloud platform, the second cloud platform, ..., the Nth cloud platform provided by different cloud service providers, where N is greater than 2.

[0043] The following section uses the first and second cloud platforms as examples to describe in detail the process of managing database instances within the cloud platforms:

[0044] The management platform can generate a first management command for a first cloud platform. This first management command can be received by the management component in the first cloud platform, and the management component can execute the first management command to control the database instance in the first cloud platform. At this point, the management platform has achieved management and control over the database instance in the first cloud platform. Similarly, the management platform can also generate a second management command for a second cloud platform, and the management component in the second cloud platform can also respond to the second management command to control the database instance in the second cloud platform. At this point, the management platform has achieved management and control over the database instance in the second cloud platform.

[0045] Optionally, the management commands generated by the management platform can be used to manage any stage of the database instance's lifecycle, such as adding, deleting, or backing up data. Furthermore, since the first and second cloud platforms can be provided by different cloud service providers, the aforementioned management process is actually the management platform's management process for database instances across cloud platforms. In other words, the management platform settings in the system can easily achieve unified management of database instances across cloud platforms.

[0046] Alternatively, the management platform can also be provided by a cloud service provider, and the management platform can correspond to the same cloud service provider as any cloud platform in the system.

[0047] In this embodiment, the database instance management system may include a management platform and a first cloud platform and a second cloud platform provided by different cloud service providers. Each cloud platform also runs its own database instance and management components. The management component in the first cloud platform can respond to a first management command generated by the management platform to manage the database instance running within it. Similarly, the second cloud platform can also respond to a second management command generated by the management platform to manage the database instance running within it.

[0048] In other words, in the above system, the management platform can manage and control the database instances contained in different cloud platforms provided by different cloud service providers, thus conveniently achieving unified management and control of database instances across cloud platforms. Furthermore, since the actual running medium of a database can be called a runtime environment, the management and control system provided in this embodiment and the following embodiments is actually also a management and control system for the runtime environment.

[0049] In practice, database instances can run in different environments provided by cloud platforms. Optionally, database instances that can be included in different cloud platforms within the system can run in container environments. Figure 2 This is a schematic diagram of another database instance management system provided in an embodiment of the present invention. Figure 1Based on the illustrated embodiment, the first cloud platform and the second cloud platform may each further include container orchestration tools. In this case, Figure 1 The management components running on the first cloud platform and the second cloud platform in the illustrated embodiment may specifically include controllers in the container orchestration tool.

[0050] The collaborative work of the system's management platform and container orchestration tools can create containers and deploy database instances into them. For details, please refer to the following... Figure 4 The relevant descriptions in the illustrated embodiments.

[0051] Accept Figure 1 For clarity in subsequent descriptions, the database instance running in the container environment provided by the first cloud platform can be referred to as the first database instance, and the controller included in the first cloud platform can be referred to as the first controller. Similarly, the database instance running in the container environment provided by the second cloud platform can be referred to as the second database instance, and the controller included in the second cloud platform can be referred to as the second controller.

[0052] Based on this Figure 2 The system's operation can be described as follows: A first controller in the first cloud platform receives and executes a first management command sent by the management platform to control a first database instance running in the container environment. Similarly, a second controller in the second cloud platform receives and executes a second management command sent by the management platform to control a second database instance running in the container environment. In other words, with the help of the controllers, the management platform can directly manage the first and second database instances running in container environments on different cloud platforms.

[0053] Optionally, the container orchestration tool in the cloud platform can include any of Docker Swarm, Kubernetes (K8s), Apache Mesos, etc. When the container orchestration tool is specifically K8s, the first controller and the second controller are specifically operators in K8s. The first controller can receive the first management commands through the interface service (i.e., API service) provided by K8s in the first cloud platform. Similarly, the second controller can also receive the second management commands through the interface service provided by K8s in the second cloud platform.

[0054] Optionally, the first database instance can include at least one type, such as a non-relational database like Redis and a relational database like MySQL or PoolarDB. Similarly, the second database instance can also include at least one of the types mentioned above. Furthermore, different types of database instances running in the container environment can be controlled by different types of controllers. For example, MySQL and Redis can use the same type of controller, while PoolarDB can use a different type of controller.

[0055] Optionally, any controller within any cloud platform in the system can not only receive management commands from the management platform, but also generate its own management commands. The management commands generated by any controller can autonomously manage database instances running in a container environment on the same cloud platform as that controller. Specifically, the first controller can generate a third management command to autonomously control the first database instance. The second controller can generate a fourth management command to autonomously control the second database instance.

[0056] In this embodiment, the configuration of controllers in the management platform and cloud platform can provide a multi-layered management architecture for database instances. Specifically, for the first and second cloud platforms provided by different cloud service providers, the management platform can conveniently achieve unified management of database instances across cloud platforms using its own generated management commands. At the same time, the controller in any cloud platform can also use its own generated management commands to achieve autonomous management of database instances running in a container environment within that cloud platform.

[0057] When different cloud platforms' database instances are running in a server environment Figure 3 This is a schematic diagram of the structure of another database instance management system provided in an embodiment of the present invention. Figure 2 Based on the illustrated embodiment, each of the different cloud platforms in this system can also include a database instance running in a server environment. Figure 2 The management and control components in the cloud platform shown in the embodiment may further include a proxy management and control component.

[0058] The collaborative work of the system's management platform and agent management components can create database instances and deploy them to the cloud platform's servers. For details, please refer to the following... Figure 4 The relevant descriptions in the illustrated embodiments are provided. Optionally, the server in the cloud platform can be a physical server or a bare-metal server.

[0059] And continue to undertake Figure 1 , 2In the examples shown, for clarity in subsequent descriptions, the database instance running in the server environment provided by the first cloud platform can be referred to as the third database instance, and the proxy management component in the first cloud platform can be referred to as the first proxy management component. The database instance running in the server environment provided by the second cloud platform can be referred to as the fourth database instance, and the proxy management component in the second cloud platform can be referred to as the second proxy management component.

[0060] Optionally, a database instance in any cloud platform can run in at least one Virtual Private Cloud (VPC) under that cloud platform. Therefore, as... Figure 3 As shown, in one optional scenario, the first and third database instances in the first cloud platform can be deployed in different VPCs under the first cloud platform. Similarly, the second and fourth database instances in the second cloud platform can also be deployed in different VPCs under the second cloud platform. Optionally, when the container orchestration tool in the cloud platform is K8, the proxy component may specifically include virtual-kubelet.

[0061] but Figure 3 The system's operation can be described as follows: The first controller receives and forwards a first control instruction generated by the control platform to the first proxy control component. The first proxy control component executes this first control instruction to control the third database instance. Similarly, the second controller can receive and forward a second control instruction sent by the control platform to the second proxy control component. The second proxy control component can control the fourth database instance according to this second control instruction. In other words, with the help of the proxy control component, the control platform can indirectly control the third and fourth database instances running in the server environment.

[0062] Optionally, the agent management components included in different cloud platforms within the system can receive management commands generated by the management platform and forwarded by the controller, as well as management commands generated by the controller itself. This allows the controller to autonomously manage database instances running in a server environment on the same cloud platform as the controller. Specifically, the first controller can forward its own generated third management command to the first agent management component to control the third database instance. The second controller can forward its own generated fourth management command to the second agent management component to control the fourth database instance.

[0063] Optionally, the third database instance may also include at least one type, similar to the first database instance type, such as a non-relational database like Red Is, or a relational database like MySQL or Pol arDB. Similarly, the fourth database instance may also include at least one of the types mentioned above.

[0064] In this embodiment, on the one hand, database instances in the cloud platform can be deployed in either a container environment or a server environment, enriching the deployment methods of database instances and thus meeting the deployment needs of different users. On the other hand, by setting up agent management components and controllers, the management platform can indirectly control database instances running in the server environment, and the controller can also autonomously control database instances running in the server environment.

[0065] Furthermore, for the systems provided in the above embodiments, optionally, the management component in any cloud platform can control the corresponding database instance via Remote Procedure Call (RPC) during the execution of management instructions. The management component in any cloud platform may include a controller and / or an agent management component. The management instructions executed by the management component may be generated by the management platform and / or by the controller in that cloud platform.

[0066] In summary, the technical effects achieved by the control system and method provided in the various embodiments of the present invention can also be understood as follows:

[0067] Any cloud platform in the management and control system provided in the various embodiments of the present invention can simultaneously support database instances running in different environments (container environment and server environment). Furthermore, the configuration of the management and control platform and controller in the system enables two-layer management of database instances within the cloud platform. That is, the management and control platform can achieve unified management and control of database instances across cloud platforms by leveraging the controller and agent management components within the cloud platform; the controller can autonomously manage database instances located on the same cloud platform as itself.

[0068] Based on the management and control system provided in the above embodiments, the creation process of database instances in the cloud platform can be further described in detail below.

[0069] For the creation process of database instances running in a container environment: different cloud platforms’ respective container orchestration tools can first register their provided interface services with the management platform, and then the management platform installs the controller in the container orchestration tool.

[0070] Continuing with the specific examples of the creation process of the first and second cloud platforms described in the above embodiments: In response to the registration of the interface service provided by the container orchestration tool in the first cloud platform, the management platform can establish a first access connection between the management platform and the first cloud platform. Similarly, in response to the registration of the interface service provided by the container orchestration tool in the second cloud platform, the management platform can also establish a second access connection between the management platform and the second cloud platform. When the container orchestration tool is Kubernetes (K8S), the management platform can create the access connection by obtaining an endpoint. Further, in response to the establishment of the first access connection, the management platform can install the first controller into the container orchestration tool included in the first cloud platform. Similarly, in response to the establishment of the second access connection, the management platform can install the second controller into the container orchestration tool included in the second cloud platform.

[0071] At this point, the preparations for creating the database instance are complete.

[0072] When there is a need to create instances, the management platform can respond to user actions and determine the instance creation method selected by the user. Optionally, the instance creation method can include single-platform creation and multi-platform creation. As is easily understood, single-platform creation means creating a database instance in one cloud platform, while multi-platform creation means creating database instances of the same type in multiple cloud platforms.

[0073] If the instance is created using a single-platform creation method, the management platform, in response to the user's operation, can also determine the instance type selected by the user and the platform identifier of the cloud platform where the database instance resides, and generate an instance creation instruction containing the instance type and platform identifier. This instance creation instruction can also be further sent to the cloud platform with the platform identifier, so that the controller in that cloud platform can create the corresponding type of database instance.

[0074] If the instance is created via a multi-platform creation method, the management platform, in response to user actions, can generate an instance creation command containing the instance type and platform identifier. Database instances created on multiple cloud platforms can have the same type. However, unlike single-platform creation, the platform identifier in the instance creation command can include the individual platform identifiers of the multiple cloud platforms from which the database instance needs to be created. The management platform can then further send this instance creation command to the corresponding multiple cloud platforms, so that each cloud platform's controller can create the database of the appropriate type.

[0075] Optionally, the database instance in the cloud platform can store general data. Considering that general data has lower availability requirements, it can be stored in a single database instance within the cloud platform, that is, in a database instance created using a single-platform creation method.

[0076] Optionally, database instances in the cloud platform can also store important data. Furthermore, to improve the availability of important data, it can optionally be stored across multiple database instances on different cloud platforms through data synchronization, thereby achieving disaster recovery for important data. In other words, important data can be stored in database instances created using a multi-platform approach. The process and significance of data synchronization can be found below. Figure 5 The relevant descriptions in the illustrated embodiments.

[0077] Optionally, as described in the above embodiments, database instances in the cloud platform can not only have different types, but can also be deployed in different VPCs under the cloud platform. In this case, the management platform can also control the controller to create database instances of the corresponding type that run in the container environment in the corresponding VPC.

[0078] Specifically, if the instance is created using a single-platform creation method, the management platform responds to the user's operation by determining the type of database instance selected by the user, the platform identifier of the cloud platform, and the network identifier of the VPC. It then generates an instance creation instruction containing the type, platform identifier, and network identifier. This instance creation instruction can be further sent to the corresponding cloud platform, where the controller creates the appropriate type of database instance in the VPC containing the network identifier from the instruction.

[0079] If the instance is created using a single-platform creation method, the management platform responds to the user's operation by generating an instance creation command that includes the type and platform identifier. The management platform can also further send this instance creation command to multiple corresponding cloud platforms, so that the controllers of each cloud platform can create the database of the corresponding type.

[0080] For the creation process of database instances running in a server environment: After completing the preparation work for database instance creation, the management platform can also create the instance using controllers and agent management components deployed in different VPCs under the same cloud platform.

[0081] Specifically, continuing with the first and second cloud platforms in the above embodiments, the instance creation process is described as follows: The first controller in the first cloud platform can forward the instance creation instruction sent by the management platform to the first proxy management component in the first cloud platform, so that the first proxy management component executes the instance creation instruction to create a third database instance running in the server environment. Similarly, the second controller in the second cloud platform can also forward the instance creation instruction sent by the management platform to the second proxy management component, so that the second proxy management component creates a fourth database instance running in the server environment.

[0082] The creation process of the database instances mentioned above, running in container or server environments, can also be combined with... Figure 4 The signaling diagram shown.

[0083] And it should be noted that, in Figure 4 In the diagram, the process of sending instance creation commands is represented by dashed lines. This is because when an instance is created using a single platform, there may be a process where the management platform sends an instance creation command to the first controller in the first cloud platform or to the second controller in the second cloud platform. When an instance is created using a multi-platform approach, there may be a process where the management platform sends instance creation commands to both the first and second controllers simultaneously.

[0084] In this embodiment, the management platform can establish a communication connection, or access connection, between itself and the cloud platform via commands. This communication connection can then be used to enhance the instance creation functionality of the container orchestration tool within the cloud platform; that is, the container orchestration tool can respond to instance creation commands sent by the management platform and create database instances.

[0085] Furthermore, after the database instance creation is completed, the first control command generated by the management platform can be sent to the first cloud platform via the first access connection. Using the interface service, this first control command can also be obtained by the first controller in the first cloud platform. Similarly, using the second access connection and the interface service, the management platform can also send the second control command to the second controller in the second cloud platform.

[0086] In this embodiment, after the database instance is created, the management platform can use access connections and interface services to send its generated management commands to the controller, so that the controller can control the database instance running in the container environment. Furthermore, any content not described in detail in this embodiment and the technical effects achieved can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0087] As mentioned in the database instance creation process above, "Important data can be stored in database instances across multiple cloud platforms through data synchronization, thereby achieving disaster recovery for important data." Continuing with the first and second cloud platforms in the above embodiments, to achieve data synchronization, the first and second cloud platforms provided by different cloud service providers can be configured with the same architecture. An identical architecture means that the VPC network structure of the two cloud platforms is the same, and the corresponding VPCs deploy the same number and type of database instances. Therefore, data in the database instances of the first cloud platform with the same architecture can be completely synchronized to the database instances contained in the second cloud platform.

[0088] Based on this Figure 5This is a schematic diagram of the structure of another database instance management system provided in an embodiment of the present invention. Figure 3 Based on the illustrated embodiments, as Figure 5 As shown, the first database instance running in the container environment of the first cloud platform can specifically be located in VPC1 under the first cloud platform, and the first database instance can belong to at least one type. The third database instance running in the server environment can specifically be located in VPC2 under the first cloud platform, and the third database instance can also belong to at least one type. Similar to the first cloud platform, the third database instance running in the second cloud platform can specifically be located in VPC3 under the second cloud platform, and the third database instance corresponds one-to-one with the first database instance. The fourth database instance running in the server environment can specifically be located in VPC4 under the second cloud platform, and the fourth database instance corresponds one-to-one with the second database instance.

[0089] The first and second cloud platforms are interconnected. Optionally, the two cloud platforms can be interconnected using Virtual Private Network (VPN) technology based on Internet Security Protocol (IPSec). Based on this interconnection, data synchronization between the first and second database instances can be described as follows:

[0090] Optionally, the management platform can send a link creation command to the first controller in the first cloud platform. The first controller can respond to the link creation command and create a first synchronization link between the first database instance and the second database instance.

[0091] Optionally, the first cloud platform may also include a data synchronization component, which can reside in the same VPC as the first controller and the first database instance. The data synchronization component in the first cloud platform can utilize the first synchronization link to achieve data synchronization between the first database instance and the second database instance.

[0092] Optionally, when the database instance is Pol arDB, the data synchronization component in the First Cloud Platform can utilize its own Change Data Capture (CDC) capability to achieve data synchronization between instances. When the database instance is Redis or MySQL, the data synchronization component in the First Cloud Platform can utilize its own Data Transmission Service (DTS) to achieve data synchronization between instances.

[0093] Alternatively, the management platform can send a link creation command to the second controller in the second cloud platform, so that the second controller can create the aforementioned first synchronization link. The second cloud platform can also have a data synchronization component, which can reside in the same VPC as the second controller and the second database instance. In this case, the data synchronization component in the second cloud platform can also achieve data synchronization between the first and second database instances in the manner described above; further details will not be elaborated here.

[0094] When the management platform sends a link creation command to the first controller, the first controller may optionally forward the command to the first agent management component. The first agent management component then responds to the command by establishing a second synchronization link between the third and fourth database instances. Optionally, the data synchronization component in the first cloud platform can utilize this second synchronization link to achieve data synchronization between the third and fourth database instances. Furthermore, depending on the type of database instance, the data synchronization component can employ appropriate methods to achieve data synchronization; details are described above and will not be repeated here.

[0095] In this embodiment, the collaborative work of the management platform, controller, and data synchronization component can realize the synchronization of data in database instances on different cloud platforms, thereby improving data availability.

[0096] Additionally, during data synchronization, optionally, the first controller in the first cloud platform can also detect in real time whether any abnormalities have occurred during data synchronization. If an abnormality occurs, it indicates that the interconnection between the two cloud platforms has been disconnected. However, since the access connection between the management platform and the cloud platform remains, the management platform can still achieve unified management of database instances across cloud platforms. Furthermore, the technical effects achieved in this embodiment can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0097] Figure 6 This is a schematic diagram illustrating the structure of another database instance management system provided in an embodiment of the present invention. The system includes a management platform and a cloud platform, wherein the cloud platform may include an agent management component and database instances running in a server environment.

[0098] The management platform is used to generate management commands, and the proxy management component is used to execute the management commands generated by the management platform, thereby controlling the database instances running in the server environment.

[0099] As can be seen, for database instances running in the server environment provided by the cloud platform, the management and control platform set up in the system provided in this embodiment can be used to manage them, thereby expanding the scope of database instance management. Furthermore, for any content not described in detail in this embodiment and the technical effects that can be achieved, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0100] Optionally, such as Figure 6 As shown, a cloud platform can include database instances running in both server and container environments. In this case, the controller within the container orchestration tool of the cloud platform can receive and execute management commands from the management platform to control the database instances running in the container environment. Figure 6 In the illustrated embodiment, the control instructions executed by the agent control component can also be forwarded by the controller in the container orchestration tool.

[0101] In this embodiment, with the help of the controller and agent management components in the cloud platform, the management platform can achieve unified management and control of database instances in different operating environments in a cloud platform.

[0102] Optionally, Figure 6 The cloud platform shown in this embodiment can be any of the cloud platforms mentioned in the above embodiments. Optionally, the server in this embodiment may include a bare metal server or a physical server.

[0103] Furthermore, the contents not described in detail in this embodiment and the technical effects that can be achieved can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0104] To facilitate understanding, the following specific scenario illustrates the working process of the database instance management system described above. The following content can also be combined with... Figure 7 understand.

[0105] As Figure 7As shown, assume there is a cloud platform 1 provided by cloud service provider 1 and a cloud platform 2 provided by cloud service provider 2. Cloud platform 1 deploys VPC1 and VPC2. VPC1 includes Redis1, MySQL1, and PoolDB1 (i.e., the first database instances in the above embodiments) running in a container environment; VPC2 includes Redis2 and MySQL2 (i.e., the third database instances in the above embodiments) running in an ECS environment. VPC1 also runs Kubernetes (K8S1), which specifically includes API service1 (i.e., the interface service in the above embodiments) and operator1 and operator2 (i.e., the first controller in the above embodiments). VPC2 also runs Virtual-Kubernetes (i.e., the first agent management component in the above embodiments).

[0106] Cloud platform 2 deploys VPC3 and VPC4. VPC3 includes Redis3, MySQL3, and PoolDB3 (i.e., the second database instances mentioned in the above embodiments) running in a container environment; VPC4 includes Redis4 and MySQL4 (i.e., the fourth database instances mentioned in the above embodiments) running in an ECS environment. VPC3 also runs Kubernetes 2, which specifically includes API service2 (i.e., the interface service in the above embodiments) and operator3 and operator4 (i.e., the second controllers in the above embodiments). VPC2 also runs Virtual-Kublet2 (i.e., the second agent management component in the above embodiments).

[0107] for Figure 7The database instance management process in the system shown can be described as follows: The first management command generated by the management platform can be sent to operator1 and operator2 via API service1, so that operator1 can manage Redis1 and MySQL1 running in the container environment, and operator2 can manage PollDB1 running in the container environment. This first management command can also be forwarded by operator1 to Virtual-kubelet1, so that Virtual-kubelet1 can manage Redis2 and MySQL2 running in the ECS environment. Additionally, operator1 can generate a third management command to manage Redis1 and MySQL1 autonomously. Operator2 can also generate a third management command to manage PollDB1 autonomously. This third management command can also be forwarded to Virtual-kubelet1 to manage Redis2 and MySQL2 running in the ECS environment.

[0108] Similar to Cloud Platform 1, the management platform and operators 3 and 4 can manage Redis3, MySQL3, and PoolDB3 running in container environments, as well as Redis4 and MySQL4 running in ECS environments.

[0109] In summary, the management platform and Virtual-kube let1 configuration enable multi-level management of database instances on any cloud platform. Simultaneously, the management platform can also achieve unified management of database instances across multiple cloud platforms.

[0110] Additionally, the process for creating a database instance can be found above. Figure 4 The relevant descriptions in the illustrated embodiments.

[0111] In addition, to ensure the availability of important data, data within database instances can also be synchronized. Specifically, this can be achieved by synchronizing data between database instances of the same type running in the same environment on different cloud platforms. Figure 7 The system shown synchronizes data between Redis1 and Redis3, between Redis2 and Redis4, between PolarDB1 and PolarDB3, and so on.

[0112] Based on the management and control system provided in the above embodiments, the management and control process of the database instance can be further described from a methodological perspective below.

[0113] Figure 8 This is a flowchart illustrating a database instance management method provided in an embodiment of the present invention. The method provided in this embodiment can be executed by the management platform shown in the above embodiments. Figure 8 As shown, the method may include the following steps:

[0114] S101, send a first control instruction to the control component in the first cloud platform so that the control component in the first cloud platform can control the database instance in the first cloud platform according to the first control instruction.

[0115] The management platform in the management system can send a first management instruction to the management component in the first cloud platform, so that the management component in the first cloud platform can execute the first management instruction, thereby realizing the control of the database instance in the first cloud platform.

[0116] Optionally, the first cloud platform may include a first database instance running in a container environment. In this case, a management component, specifically a first controller, can be used to control the first database instance. Since the first database instance runs in a container environment, the first cloud platform may also include a container orchestration tool, and the first controller may be included within this container orchestration tool.

[0117] Optionally, the first cloud platform may also include a third database instance running in a server environment. In this case, a management component, specifically manifested as a first agent management component within the first cloud platform, can be used to control the third database instance. Specifically, the controller can forward the first management commands generated by the management platform to the first agent management component to achieve management of the third database instance.

[0118] S102, send a second control instruction to the control component in the second cloud platform so that the control component in the second cloud platform controls the database instance in the second cloud platform according to the second control instruction, wherein the first cloud platform and the second cloud platform are provided by different cloud service providers.

[0119] The management platform sends a second management instruction to the management component in the second cloud platform, so that the management component in the second cloud platform executes the second management instruction to control the database instance in the second cloud platform.

[0120] Similar to step S101, the second database instance running in a container environment within the second cloud platform can also be controlled using the second controller within the second cloud platform. Similarly, the fourth database instance running in a server environment can be controlled using the second agent management component within the second cloud platform.

[0121] The first cloud platform and the second cloud platform can be provided by different cloud service providers.

[0122] In this embodiment, the management platform can generate a first management instruction for the first cloud platform and a second management instruction for the second cloud platform. Different cloud platforms can then utilize their own running management components to execute the corresponding management instructions, thereby controlling their own running database instances. In other words, the management platform can manage the database instances contained in each of the different cloud platforms, thus conveniently achieving unified management of database instances across cloud platforms. Furthermore, any steps not described in detail in this embodiment, as well as the technical effects they achieve, can be found in the relevant descriptions in the aforementioned embodiments, and will not be repeated here.

[0123] Figure 9 This is a flowchart illustrating a database instance creation method provided in an embodiment of the invention. The method provided in this embodiment can be executed by the management platform shown in the above embodiments. Furthermore, it is readily understood that the method provided in this embodiment can be... Figure 8 The method provided in the illustrated embodiment is executed prior to this. For example... Figure 9 As shown, the method may include the following steps:

[0124] S201, in response to the registration of different interface services, establishes a first access connection and a second access connection respectively. The interface services are provided by the container orchestration tools included in each cloud platform.

[0125] The container orchestration tool in the first cloud platform can register its provided interface services with the management platform. In response to the registration of the interface services, the management platform establishes the first access connection between the management platform and the first cloud platform. Similarly, the container orchestration tool in the second cloud platform can also register its provided interface services with the management platform. In response to the registration of the interface services, the management platform establishes the second access connection between the management platform and the second cloud platform.

[0126] S202, install the first controller into the container orchestration tool in the first cloud platform.

[0127] S203, install the second controller into the container orchestration tool in the second cloud platform.

[0128] Furthermore, in response to the creation of the first access connection, the management platform can install the first controller into the container orchestration tool in the first cloud platform. Similarly, in response to the creation of the second access connection, the management platform can install the second controller into the container orchestration tool in the second cloud platform. This completes the preparatory work before creating the database instance.

[0129] S204, Determine how the instance is created.

[0130] S205, If the instance is created using a multi-platform creation method, then instance creation instructions are sent to the first controller and the second controller respectively, so that the first controller creates a database instance in the first cloud platform according to the instance creation instructions, and the second controller creates a database instance in the second cloud platform according to the instance creation instructions. The database instance runs in the container environment or server environment provided by the cloud platform.

[0131] Based on the above preparations, when there is a need to create a database instance, the management platform can respond to the user's operation and determine whether the instance is created on a single platform or multiple platforms.

[0132] The management platform can respond to user actions. When it is determined that the instance creation method is single-platform creation, the management puzzle can further generate an instance creation instruction containing the type and platform identifier. This instance creation instruction can be sent to a cloud platform with a platform identifier, so that the controller in that cloud platform can create a database instance of the corresponding type. The cloud platform can be either a first cloud platform or a second cloud platform.

[0133] When the instance creation method is determined to be multi-platform creation, the management platform can also generate instance creation instructions that include the type and platform identifiers. However, unlike single-platform creation, the platform identifiers in the instance creation instructions include the platform identifiers of the multiple cloud platforms from which the database instance needs to be created. Furthermore, database instances created on multiple cloud platforms can have the same type.

[0134] The management platform can then send the instance creation command to multiple corresponding cloud platforms, so that each cloud platform's controller can create the corresponding type of database.

[0135] Additionally, for any details not described in this embodiment, please refer to the above. Figure 4 The signaling diagram shown.

[0136] Optionally, the management platform can also control the synchronization of data contained in database instances across different cloud platforms. The specific data synchronization process can be found above. Figure 5 The relevant content in the illustrated embodiments will not be repeated here.

[0137] The database instance management apparatus of one or more embodiments of the present invention will be described in detail below. Those skilled in the art will understand that the management apparatus can be configured using commercially available hardware components through the steps taught in this solution.

[0138] Figure 10 This is a schematic diagram of the structure of a database instance management device provided in an embodiment of the present invention, as shown below. Figure 10As shown, the device includes:

[0139] The first sending module 11 is used to send a first control instruction to the control component in the first cloud platform, so that the control component in the first cloud platform controls the database instance in the first cloud platform according to the first control instruction.

[0140] The second sending module 12 is used to send a second control instruction to the control component in the second cloud platform, so that the control component in the second cloud platform controls the database instance in the second cloud platform according to the second control instruction;

[0141] The first cloud platform and the second cloud platform are provided by different cloud service providers.

[0142] Optionally, the database instance in the cloud platform runs in a container environment provided by the cloud platform, and the management components in the cloud platform include a controller in a container orchestration tool.

[0143] The first sending module 11 is used to send the first control instruction to the first controller in the first cloud platform using the first access connection between the control platform and the first cloud platform.

[0144] The second sending module 12 is used to send the second control command to the second controller in the second cloud platform using the second access connection between the control platform and the second cloud platform.

[0145] Optionally, the device further includes an establishment module 13, an installation module 14, and a determination module 15.

[0146] The establishment module 13 is used to establish the first access connection and the second access connection respectively in response to the registration of different interface services, wherein the interface services are provided by the container orchestration tools included in the cloud platform.

[0147] The installation module 14 is used to install the first controller into the container orchestration tool in the first cloud platform; and to install the second controller into the container orchestration tool in the second cloud platform.

[0148] Module 15 is used to determine how the instance is created.

[0149] The first sending module 11 is used to send an instance creation instruction to the first controller if the instance is created using a multi-platform creation method, so that the first controller can create a database instance in the first cloud platform according to the instance creation instruction.

[0150] The second sending module 12 is used to send an instance creation instruction to the second controller if the instance is created using a multi-platform creation method, so that the second controller can create a database instance in the second cloud platform according to the instance creation instruction.

[0151] The database instance runs in a container environment or server environment provided by the cloud platform.

[0152] Figure 10 The device shown can perform Figure 8 or Figure 9 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 8 or Figure 9 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 8 or Figure 9 The descriptions in the illustrated embodiments will not be repeated here.

[0153] In one possible design, the database instance management method and database instance creation method provided in the above embodiments can be applied to an electronic device, such as... Figure 11 As shown, the electronic device may include a processor 21 and a memory 22. The memory 22 is used to store data that supports the electronic device in performing the above-described actions. Figure 8 or Figure 9 The program of the method provided in the illustrated embodiment, wherein the processor 21 is configured to execute the program stored in the memory 22.

[0154] The program includes one or more computer instructions, wherein the one or more computer instructions, when executed by the processor 21, can achieve the following: Figure 8 or Figure 9 All or part of the steps in the illustrated embodiments.

[0155] The structure of the electronic device may also include a communication interface 23 for the electronic device to communicate with other devices or communication networks.

[0156] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by the aforementioned electronic device, which includes instructions for executing the above-mentioned... Figure 8 or Figure 9 The procedure involved in the method shown.

[0157] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by the aforementioned electronic device, which includes instructions for executing the above-mentioned... Figure 8 or Figure 9 The procedure involved in the method shown.

[0158] In addition, embodiments of the present invention provide a computer program product. This computer program product includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is able to perform the above-described functions. Figure 8 or Figure 9 The steps or functions of the method shown.

[0159] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A database instance management system, characterized in that, Includes: a management and control platform and a first cloud platform and a second cloud platform provided by different cloud service providers, wherein the cloud platforms provided by the different cloud service providers are communicatively connected to the management and control platform, and the first cloud platform and the second cloud platform run their own database instances and management and control components; The management and control platform is used to generate management and control instructions, which are used to operate on the database instance; The management and control component in the first cloud platform is used to receive a first management and control instruction generated by the management and control platform; and to control the database instance in the first cloud platform according to the first management and control instruction. The management and control component in the second cloud platform is used to receive the second management and control instructions generated by the management and control platform; and to control the database instance in the second cloud platform according to the second management and control instructions.

2. The system according to claim 1, characterized in that, The different cloud platforms in the system each include container orchestration tools and database instances running in a container environment, and the management component includes a controller in the container orchestration tool; The first controller in the first cloud platform is used to receive the first management and control instructions by means of the interface service provided by the container orchestration tool in the first cloud platform; and to control the first database instance running in the container environment in the first cloud platform according to the first management and control instructions. The second controller in the second cloud platform is used to receive the second management and control instructions by means of the interface service provided by the container orchestration tool in the second cloud platform; and to control the second database instance running in the container environment in the second cloud platform according to the second management and control instructions.

3. The system according to claim 2, characterized in that, The first controller is used to generate a third control instruction and control the first database instance according to the third control instruction. The second controller is used to generate a fourth control instruction; and to control the second database instance according to the fourth control instruction.

4. The system according to claim 2, characterized in that, The different cloud platforms in the system also include database instances running in the server environment, and the management and control components also include agent management and control components deployed on the different cloud platforms. The first agent management component in the first cloud platform is used to receive the first management instruction forwarded by the first controller; and to control the third database instance running in the server environment in the first cloud platform according to the first management instruction. The second agent management component in the second cloud platform is used to receive the second management instruction forwarded by the second controller; and to control the fourth database instance running in the server environment in the second cloud platform according to the second management instruction.

5. The system according to claim 4, characterized in that, The first agent control component is used to receive a third control instruction generated by the first controller; and control the third database instance according to the third control instruction; The second agent management component is used to receive the fourth management instruction generated by the second controller; and to control the fourth database instance according to the fourth management instruction.

6. The system according to any one of claims 2 to 5, characterized in that, A management component in any cloud platform is used to execute management instructions to control the database instance in the cloud platform via remote procedure calls. The management instructions include management instructions generated by the management platform and / or management instructions generated by the controller in the cloud platform.

7. The system according to claim 4, characterized in that, The cloud platform and the management platform correspond to the same cloud service provider; the database instance contained in the cloud platform runs in at least one virtual private cloud provided by the cloud platform, the database instance running in the container environment and the database instance running in the server environment in the cloud platform each contain at least one type, and the controller in the cloud platform corresponds to the type of the database instance running in the container environment in the cloud platform.

8. The system according to claim 4, characterized in that, A container orchestration tool in any cloud platform is used to register the interface services provided by the container orchestration tool to the management and control platform; The management platform is configured to respond to the registration of the interface service by establishing a first access connection with the first cloud platform and a second access connection with the second cloud platform; sending the first management instruction to the first controller using the first access connection; and sending the second management instruction to the second controller using the second access connection.

9. The system according to claim 8, characterized in that, The management platform is configured to, in response to the establishment of the first access connection, install the first controller into the container orchestration tool in the first cloud platform; and in response to the establishment of the second access connection, install the second controller into the container orchestration tool in the second cloud platform.

10. The system according to claim 9, characterized in that, The management and control platform is used to determine how instances are created; If the instance is created using a multi-platform creation method, then instance creation instructions are sent to the first controller and the second controller respectively; The first controller is configured to execute the instance creation instruction to create the first database instance; The second controller is used to execute the instance creation instruction to create the second database instance.

11. The system according to claim 10, characterized in that, The first controller is used to forward the instance creation instruction to the first agent management component; The first agent management component is used to execute the instance creation instruction to create the third database instance.

12. The system according to claim 4, characterized in that, The first cloud platform and the second cloud platform are interconnected; The first controller is configured to establish a first synchronization link between the first database instance and the second database instance in response to a link creation command sent by the management and control platform. The data synchronization tool in the first cloud platform is used to synchronize data from the first database instance to the second database instance via the first synchronization link.

13. The system according to claim 12, characterized in that, The first controller is used to forward the link creation instruction to the first agent management component; The first proxy management component is used to establish a second synchronization link between the third database instance and the fourth database instance in response to the link creation instruction; The data synchronization component in the first cloud platform is used to synchronize data from the third database instance to the fourth database instance via the second synchronization link.

14. A database instance management system, characterized in that, include: A communication connection management platform and a cloud platform, wherein the cloud platform includes a database instance and an agent management component, and the database instance runs in a server environment provided by the cloud platform; The control platform is used to generate control instructions; The agent management component is used to control the database instance running in the server environment according to the management instructions.

15. The system according to claim 14, characterized in that, The cloud platform also includes container orchestration tools and database instances running in a container environment provided by the cloud platform. The controller in the container orchestration tool is used to receive the management instructions; control the database instance running in the container environment according to the management instructions; and forward the management instructions generated by the management platform to the agent management component.

16. The system according to claim 14, characterized in that, The server may be a bare metal server or a physical server.

17. A database instance management method, characterized in that, Applications in management and control platforms include: Send a first control instruction to the control component in the first cloud platform, so that the control component in the first cloud platform controls the database instance in the first cloud platform according to the first control instruction; Send a second control instruction to the control component in the second cloud platform, so that the control component in the second cloud platform controls the database instance in the second cloud platform according to the second control instruction; The first cloud platform and the second cloud platform are provided by different cloud service providers.

18. The method according to claim 17, characterized in that, The database instances in the cloud platform run in the container environment provided by the cloud platform, and the management components of the cloud platform include the controller in the container orchestration tool; The step of sending the first control command to the control component in the first cloud platform includes: Using the first access connection between the control platform and the first cloud platform, the first control instruction is sent to the first controller in the first cloud platform; The sending of the second control command to the control component in the second cloud platform includes: Using the second access connection between the control platform and the second cloud platform, the second control command is sent to the second controller in the second cloud platform.

19. The method according to claim 18, characterized in that, The method further includes: In response to the registration of different interface services, the first access connection and the second access connection are established respectively, wherein the interface services are provided by the container orchestration tools included in the cloud platform; Install the first controller into the container orchestration tool in the first cloud platform; Install the second controller into the container orchestration tool in the second cloud platform; Determine how the instance is created; If the instance is created using a multi-platform creation method, an instance creation instruction is sent to both the first controller and the second controller. The first controller creates a database instance in the first cloud platform according to the instance creation instruction, and the second controller creates a database instance in the second cloud platform according to the instance creation instruction. The database instance runs in a container environment or server environment provided by the cloud platform.

20. An electronic device, characterized in that, include: A memory and a processor; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor performs the database instance management method as described in any one of claims 17 to 19.

21. A non-transitory machine-readable storage medium, characterized in that, The non-transitory machine-readable storage medium stores executable code that, when executed by a processor of an electronic device, causes the processor to perform the database instance management method as described in any one of claims 17 to 19.

22. A computer program product, characterized in that, The computer program product includes a computer program or instructions that enable the computer program or instructions to perform the steps in the database instance management method of any one of claims 17 to 19.

Images