OpenStack cloud resource cross-domain fusion method and system

Abstract

The embodiment of the invention discloses an OpenStack cloud resource cross-domain fusion method, which comprises the following steps of: establishing a remote network between a data center and remote sites in different regions; the original OpenStack of each remote site is accessed to the data center through each remote network; a new OpenStack is deployed, and the new OpenStack is connected to the data center; the tenants are created for different regions in the new OpenStack; and the tenants of each region and the original OpenStacks of each region perform cooperative use of cloud resources through the data center. According to the embodiment, cross-region fusion of cloud resources is realized.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of cloud resource virtualization, and in particular to a method and system for cross-domain integration of OpenStack cloud resources. Background Art

[0002] With the rapid development of cloud computing technology, OpenStack, as an open source cloud computing management platform, is widely used in private cloud and hybrid cloud scenarios. However, when sharing and managing OpenStack resources between multiple remote sites, there are challenges such as network isolation, resource scheduling, and permission control.

[0003] In the prior art, when cloud resources in different regions are cross-regionally scheduled, different versions of OpenStack need to be adapted because the versions of OpenStack deployed in different regions are different. The difficulty and workload of the adaptation are very high. Summary of the invention

[0004] The embodiments of the present invention provide a method and system for cross-domain integration of OpenStack cloud resources to solve the above technical problems.

[0005] In a first aspect, an embodiment of the present invention provides a method for cross-domain integration of OpenStack cloud resources, including:

[0006] Establishing remote networks between data centers and remote sites in different regions;

[0007] Connecting the original OpenStack of each remote site to the data center through each remote network;

[0008] Deploy a new OpenStack and connect the new OpenStack to the data center;

[0009] Creating tenants for different regions in the new OpenStack;

[0010] Tenants in various regions and existing OpenStack in various regions collaboratively use cloud resources through the data center.

[0011] In a second aspect, an embodiment of the present invention provides an OpenStack cloud resource cross-domain fusion system, characterized by comprising: a data center and remote sites in different regions;

[0012] Wherein, a remote network is established between the data center and each remote site;

[0013] The existing OpenStack at each remote site is connected to the data center through each remote network;

[0014] Tenants in different regions are created in the new OpenStack, and the new OpenStack is also connected to the data center;

[0015] Tenants in various regions and existing OpenStack in various regions collaboratively use cloud resources through the data center.

[0016] In summary, the embodiment of the present invention provides a method and system for cross-domain integration of OpenStack cloud resources. First, a stable and efficient cloud platform infrastructure is constructed, on which the OpenStack open source cloud computing management platform is deployed to integrate cross-domain resources, thereby improving the utilization rate of cross-domain networks and resources and the efficiency of operation and maintenance from the overall structure; and by establishing a data center, cross-domain resources are uniformly managed through openstack, thereby improving the co-management and sharing capabilities of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 This is a flow chart of a method for cross-domain integration of OpenStack cloud resources provided by an embodiment of the present invention;

[0019] Figure 2 is a schematic diagram of an OpenStack cloud resource cross-domain fusion system provided by an embodiment of the present invention;

[0020] Figure 3 An architecture diagram of an OpenStack cloud resource cross-domain fusion system provided in this embodiment;

[0021] Figure 4 This embodiment provides another architecture diagram of the OpenStack cloud resource cross-domain fusion system. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work belong to the scope of protection of the present invention.

[0023] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0024] In the description of the present invention, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0025] The embodiment of the present invention provides a method for cross-domain integration of OpenStack cloud resources. In order to illustrate the method, the main technical difficulties faced in realizing cross-domain integration of OpenStack cloud resources are first introduced. In general, in the process of collaborative sharing of openstack resources, this embodiment mainly focuses on the establishment of data centers, the opening of cross-domain networks, dynamic deployment, efficient operation and maintenance, and real-time monitoring to build a "logically integrated, physically distributed" resource co-management and sharing technical architecture.

[0026] At present, with the rapid development of cloud computing technology, data centers are gradually developing in the direction of large-scale, high availability, and easy management. As an open source cloud computing management platform, OpenStack is widely used in private cloud and hybrid cloud scenarios. However, when sharing and managing OpenStack resources between multiple data centers or remote sites, there are challenges such as network isolation, resource scheduling, and permission control.

[0027] At present, in terms of data resources, cross-domain management of OpenStack cloud resources requires the establishment of a unified data center, and scalability and compatibility also face challenges. When managing across domains, the connection of cross-domain networks may encounter network complexity and performance bottlenecks, as well as security issues. The dynamic deployment process is relatively complex, and the degree of automation needs to be improved. At the same time, it is necessary to ensure that new resources can be quickly and stably integrated into the existing system. In terms of efficient operation and maintenance, the operation and maintenance costs and technical thresholds are high, and the difficulty of monitoring and troubleshooting cannot be ignored. These defects need to be continuously improved and optimized in actual applications to ensure the stable operation and efficient operation and maintenance of the OpenStack system.

[0028] Due to the above technical difficulties, Figure 1 1 is a flow chart of a method for cross-domain integration of OpenStack cloud resources provided by an embodiment of the present invention. The method is applicable to the situation where cross-domain management and scheduling of OpenStack cloud resources in different regions are performed, such as Figure 1 As shown, the method specifically includes:

[0029] S110. Establish a remote network between the data center and remote sites in different regions.

[0030] Different regions can refer to different areas, different cities, etc., and remote sites refer to cloud resource sites located in different regions. This step uses virtual private networks, including but not limited to VPN (virtual private network) or EVPN (Ethernet virtual private network) + VXLAN (virtual extensible local area network), etc., to achieve cross-regional, secure and reliable network interconnection, ensuring unimpeded data flow and secure isolation.

[0031] Optionally, taking VPN as an example, the construction of a virtual network may include the following steps: first, deploy VPN equipment between the data center and each remote site to establish an encrypted tunnel connection; then, configure the VPN tunnel parameters to ensure that network bandwidth, latency, and security meet business requirements; finally, implement QoS (Quality of Service) policies on the VPN tunnel to optimize data transmission performance.

[0032] In addition, this embodiment can also establish a blockchain-enhanced SDN intelligent routing and security audit system for virtual private networks. Optionally, the consensus mechanism of the blockchain (such as DPoS, for the efficiency of large-scale networks) can be deeply integrated with the intelligent routing algorithm of SDN. Blockchain nodes not only participate in the data verification and consensus process, but also receive network status information through smart contracts as part of routing decisions, jointly calculate and verify the optimal routing path, and significantly improve the reliability and security of routing. At the same time, a comprehensive security audit system is built, and all network traffic data, routing decision records and key network events are encrypted and stored on the blockchain. The tamper-proof nature of the blockchain is used to ensure the authenticity and integrity of the audit data, providing a solid data foundation for network troubleshooting, performance optimization and compliance inspection.

[0033] In a specific implementation, the establishment of a blockchain-enhanced SDN intelligent routing and security audit system may include the following steps:

[0034] Step 1: Develop a dedicated SDN controller plug-in to achieve seamless integration with blockchain nodes. The plug-in is responsible for forwarding the routing decision requests of the SDN control plane to the blockchain network and receiving the decision results returned by the blockchain.

[0035] Step 2: Write a smart contract to define the logic and rules for routing decisions. The smart contract receives network status data from the SDN controller, combines the voting or weight information of the blockchain nodes, calculates and returns the optimal routing path. Optionally, you can log in to the SDN controller through a VPN tunnel between the data center and remote sites in different regions, and configure the smart contract on the SDN controller.

[0036] Step 3: Design an efficient blockchain storage architecture to support rapid processing and query of large-scale network traffic data. Use distributed storage technology and indexing mechanisms to ensure fast access and efficient management of data.

[0037] S120. Connect the original OpenStack of each remote site to the data center through each remote network.

[0038] Remote sites in different regions may have deployed OpenStack cloud resource management platforms and are running. These OpenStack versions may be different. This embodiment retains the original OpenStack unchanged and only enables it to interact with the data center through the remote network.

[0039] S130: Deploy a new OpenStack, and connect the new OpenStack to the data center.

[0040] This embodiment maintains the original OpenStack of each remote site unchanged, establishes a new OpenStack platform, and manages and schedules the cloud resources in different regions through the new OpenStack platform. Similarly, the new OpenStack platform should also be connected to the data center, and the data center will uniformly manage and schedule the original OpenStack and the new OpenStack.

[0041] In a specific implementation, Kubernetes can be used to deploy the new OpenStack. Specifically, the process may include the following steps:

[0042] Step 1: Deploy Kubernetes clusters in the data center and remote sites, and deploy new OpenStack components. Optionally, you can install OpenStack Helm Chart or a custom Operator to deploy OpenStack components in a containerized manner.

[0043] Step 2: Use Kubernetes persistent volumes to provide storage support for the new OpenStack to ensure data and configuration persistence.

[0044] Step 3. Configure a Kubernetes network plug-in (such as Calico) to ensure network communication between Kubernetes and the new OpenStack.

[0045] In addition, this embodiment can also establish a blockchain-assisted resource scheduling and cross-platform trust mechanism in the integration of Kubernetes and OpenStack. Optionally, blockchain is introduced between Kubernetes and OpenStack as the core recording system for resource allocation and scheduling. All resource request, allocation, and release operations are recorded and verified through blockchain to ensure the transparency and fairness of resource management. At the same time, the blockchain's smart contract is used to establish a trust chain between Kubernetes and OpenStack. Smart contracts are used to achieve automated verification and confirmation of cross-platform resource requests and responses, reduce manual intervention, reduce error rates, and improve the efficiency and accuracy of resource scheduling.

[0046] In a specific implementation, the establishment of a blockchain-assisted resource scheduling and cross-platform trust mechanism may include the following steps:

[0047] Step 1: Through a cross-platform blockchain client, the interaction between Kubernetes and the new OpenStack and the blockchain is realized, and the blockchain is used to record and verify the resource scheduling of the new OpenStack. Optionally, a cross-platform blockchain client or agent is developed to support the interaction between Kubernetes and OpenStack and the blockchain network. The client is responsible for encrypting the resource request and response information and sending it to the blockchain network, and receiving the verification result returned by the blockchain.

[0048] Step 2: Establish a signature and verification mechanism between Kubernetes and the new OpenStack through smart contracts. Optionally, design a resource scheduling algorithm based on blockchain to make intelligent resource scheduling decisions based on resource allocation records and resource demand forecasts on the blockchain. The algorithm considers multiple factors, such as resource utilization, load balancing, cost-effectiveness, etc., to ensure the optimal configuration of resources.

[0049] Step 3: Establish a blockchain signature and verification mechanism for cross-platform resource requests. Resource requests are signed with a private key before being sent, and the recipient verifies with a public key to ensure the authenticity and non-repudiation of the request.

[0050] S140: Create tenants for different regions in the new OpenStack.

[0051] This step implements the co-management and sharing of resources. When Kubernetes is used to deploy the new OpenStack, the co-management and sharing of resources can be achieved in the following ways:

[0052] Step 1: Create multiple namespaces in Kubernetes. Each namespace corresponds to an OpenStack tenant in a different region.

[0053] Step 2: Implement role-based access control policies to ensure that each tenant can only access authorized resources.

[0054] Step 3: Use Kubernetes' scheduler and load balancer to optimize the allocation and use of OpenStack resources.

[0055] In addition, this embodiment can also establish a blockchain-driven resource sharing and incentive mechanism. Optionally, a decentralized resource sharing platform based on blockchain is constructed to allow different projects, teams or business units to freely publish and request resources on the platform. The platform realizes automatic matching and allocation of resources through smart contracts, improving the flexibility and utilization of resources. At the same time, the incentive mechanism for resource use is designed using the smart contracts of the blockchain. Rewards are automatically calculated and allocated based on factors such as resource usage, duration, and quality. The incentive mechanism encourages users to actively share resources and promotes efficient and recycled use of resources.

[0056] In a specific implementation, the establishment of a blockchain-driven resource sharing and incentive mechanism may include the following steps:

[0057] Step 1: Deploy a blockchain-based resource sharing API for each tenant. The resource sharing API is used to publish, request, match and confirm resources to the blockchain. Optionally, develop a blockchain-based resource sharing API that supports operations such as resource publishing, requesting, matching and confirming. The API provides a unified interface specification to facilitate integration and interoperability between different systems and platforms.

[0058] Step 2: Deploy smart contract templates and parameterized configuration tools on each tenant for users to customize incentive mechanisms and rules. Optionally, you can design smart contract templates and parameterized configuration tools to allow users to customize incentive mechanisms and rules according to actual needs. Users can implement complex incentive mechanism designs through simple configurations, improving the flexibility and scalability of the system.

[0059] Step 3: Blockchain storage and real-time analysis of resource usage data. Blockchain storage ensures the authenticity and integrity of data, and real-time analysis provides data support for incentive mechanisms. The analysis results can be used to optimize resource allocation strategies and improve resource utilization efficiency.

[0060] S150: Tenants in various regions and existing OpenStacks in various regions collaboratively use cloud resources through the data center.

[0061] After the operations of S110-S140 are completed, the new OpenStack tenants in each region and the original OpenStack cloud resources in each region can be uniformly managed and scheduled in the data center.

[0062] Specifically, tenants in each region and the original OpenStack in each region send their own cloud resource ownership and usage to the data center. If a user makes a resource usage request to a tenant of the new OpenStack or the original OpenStack in a region, the tenant or the original OpenStack will initiate a resource call request to the data center. After receiving the resource call request, the data center allocates cloud resources to the user who initiated the request based on the overall cloud resource ownership and usage, thereby achieving collaborative management and use of cloud resources with express delivery without changing the original OpenStack.

[0063] Furthermore, to ensure the stable operation and efficient management of the cloud environment, on the basis of the above-mentioned cross-domain integration of OpenStack cloud resources, the entire cloud environment needs to be monitored and maintained. In order to achieve automated monitoring and operation and maintenance, tools such as Helm or Ansible can be used to achieve automated deployment and configuration of OpenStack and Kubernetes; deploy monitoring tools such as Prometheus and Grafana to monitor the operating status in real time; and configure log collection and analysis systems such as ELK Stack (Elasticsearch, Logstash, Kibana) for log management and auditing.

[0064] In addition, this embodiment can also establish a blockchain-enabled operation and maintenance monitoring and fault recovery system. Optionally, the immutability, transparency, and traceability characteristics of the blockchain can be used to encrypt and store all key operation and maintenance logs, performance indicators (KPIs), system events, etc. on the blockchain to ensure the authenticity and integrity of the data. This not only provides a reliable data basis for troubleshooting and performance optimization, but also enhances the security and compliance of the system. At the same time, an automatic fault recovery mechanism based on blockchain smart contracts can be designed. Smart contracts can monitor monitoring data on the blockchain, and once a preset fault condition or abnormal event is detected, the corresponding fault recovery process is immediately triggered. These processes may include automatically restarting services, switching backup resources, notifying operation and maintenance personnel, etc., thereby greatly reducing human intervention and recovery time, and improving the stability and availability of the system.

[0065] In a specific implementation, the establishment of a blockchain-enabled operation and maintenance monitoring and fault recovery system may include the following steps:

[0066] Step 1: Deploy a blockchain-based operation and maintenance monitoring plug-in to write monitoring data to the blockchain in real time. Optionally, you can develop a blockchain-based operation and maintenance monitoring plug-in or middleware to write monitoring data to the blockchain in real time.

[0067] Step 2: Define fault detection, diagnosis, and response rules through smart contracts, which are used to automatically execute the corresponding recovery strategy and record the response results back to the blockchain when a fault occurs. Optionally, you can write a smart contract to define the logic and rules for fault detection, diagnosis, and recovery. The smart contract needs to be able to parse the monitoring data on the blockchain and determine the system status based on preset thresholds or conditions. Once a fault is detected, the smart contract will automatically execute the corresponding recovery strategy and record the recovery results back to the blockchain.

[0068] Step 3: Integrate and link the blockchain monitoring plug-in with existing operation and maintenance tools. The blockchain monitoring plug-in can be integrated into existing operation and maintenance monitoring systems, such as Prometheus, Grafana, etc., to achieve seamless data connection and transmission. Through API interfaces or message queues, the monitoring data and fault recovery information on the blockchain are synchronized to the operation and maintenance tools in real time to ensure that the operation and maintenance personnel can understand the system status in a timely manner and take corresponding measures.

[0069] Step 4: Perform permission management and access control. Implement strict permission management and access control mechanisms in the blockchain network to ensure that only authorized operation and maintenance personnel or systems can access and modify monitoring data and smart contracts on the blockchain. This helps protect sensitive information of the system and prevent unauthorized access and tampering.

[0070] Figure 2 FIG. 1 is a schematic diagram of an OpenStack cloud resource cross-domain fusion system provided by an embodiment of the present invention. Figure 2 As shown, the system includes a data center and remote sites in different regions.

[0071] A remote network is established between the data center and each remote site; the original OpenStack of each remote site is connected to the data center through each remote network; tenants in different regions are created in the new OpenStack, and the new OpenStack is also connected to the data center; tenants in different regions and the original OpenStack in different regions use cloud resources in a collaborative way through the data center. Figure 2Remote site 1 and remote site 2 in the example have already been deployed with OpenStack. This embodiment keeps the original OpenStack unchanged and continues to manage the original cloud resources in the site. At the same time, tenants are created for these two sites in the new OpenStack to manage the newly added cloud resources in the site. Remote site N-1 and remote site N have not originally deployed OpenStack. A combination is directly created for them in the new OpenStack to manage all cloud resources in the site.

[0072] Figure 3 and Figure 4 The following are the architecture diagrams of the OpenStack cloud resource cross-domain fusion system provided in this embodiment, respectively showing the architecture flow of the system from different angles. Figure 3 The system includes infrastructure layer, virtualization and containerization layer, security policy and planning layer, monitoring and log management layer, and user interface and API access layer.

[0073] Among them, the infrastructure layer and the virtualized container layer together constitute the basic platform architecture of the system, and its main parts include the basic network environment and the k8s basic base. The basic platform architecture is firmly built on an efficient network environment and a Kubernetes (k8s) base. The architecture uses a virtual private network to achieve cross-regional, secure and reliable network interconnection, ensuring unimpeded data flow and secure isolation. As the core base, k8s provides elastic scaling, automated deployment and management capabilities, supports the efficient operation of microservice architecture, and accelerates application iteration and delivery. The overall design aims to create a flexible, scalable, and easy-to-maintain cloud platform foundation to lay a solid foundation for upper-level application services.

[0074] At the cloud infrastructure layer, the system deploys the open source cloud computing management platform OpenStack based on the above basic platform architecture to further enhance the flexibility and scalability of cloud services. OpenStack supports the comprehensive management of computing resources, storage resources and network resources by providing rich API interfaces and modular design, and realizes dynamic allocation and efficient utilization of resources.

[0075] At the security policy and compliance layer, the system formulates and implements security policies for the cloud environment, including network isolation, data encryption, identity authentication and authorization, to ensure the security and compliance of cloud resources and services. By formulating and implementing a series of security policies, covering multiple dimensions such as network isolation, data encryption, identity authentication and authorization. Through strict network isolation measures, the data between different tenants is ensured to be securely isolated; advanced data encryption technology is used to protect the confidentiality of data during transmission and storage; a strong identity authentication and authorization mechanism is implemented to ensure that only legitimate users can access authorized resources.

[0076] At the monitoring and log management level, to ensure stable operation and efficient management of the cloud environment, the system makes full use of Kubernetes' monitoring and log management tools, such as Prometheus for performance monitoring, Grafana for visualization, and Elasticsearch for centralized storage and analysis of log data. These tools work together to monitor key indicators of the cloud environment in real time, such as CPU usage, memory usage, network traffic, etc., while collecting and analyzing system and application logs to help the operation and maintenance team quickly locate and solve problems.

[0077] At the user interface and API layer, the system provides an easy-to-use user interface (such as Dashboard) and rich API interfaces to facilitate users and administrators to access and manage cloud resources and services. By integrating the visual display, one-click operation and management functions of cloud resources, users and administrators can easily access, monitor and manage cloud resources and services. At the same time, it provides a rich API interface, supports multiple protocols such as RESTful and GraphQL, and meets the flexible calling needs of developers and automation tools for cloud resources. These API interfaces not only cover basic services such as computing, storage, and networking, but also go deep into advanced functions such as monitoring, logging, and security, providing users with powerful and flexible cloud environment management capabilities.

[0078] Figure 4 yes Figure 3 A specific implementation method of the present invention is to divide the above-mentioned OpenStack cloud resource cross-domain fusion system into multiple subsystems from the perspective of technical implementation: a network architecture design system, a Kubernetes and OpenStack integration system, a resource co-management and sharing system, and an operation and maintenance and automation system. Among them, the network architecture design system can be deployed and implemented in the manner recorded in S110 and S120 in the above-mentioned method embodiment, the Kubernetes and OpenStack integration system can be deployed and implemented in the manner recorded in S130, the resource co-management and sharing system can be deployed and implemented in the manner recorded in S140, and the operation and maintenance and automation system can be deployed and implemented in the manner of operation and maintenance and automation in the above-mentioned method embodiment. All subsystems jointly ensure the normal operation of the OpenStack cloud resource cross-domain fusion system.

[0079] In summary, the embodiment of the present invention provides a method and system for cross-domain integration of OpenStack cloud resources. First, a stable and efficient cloud platform infrastructure is constructed, with Kubernetes as the core base, combined with advanced network technologies such as VPN, EVPN+VXLAN, to achieve cross-regional secure network interconnection and flexible resource scheduling. On top of this, the OpenStack open source cloud computing management platform is deployed, and through its rich API interface and modular design, it comprehensively manages computing, storage and network resources to ensure dynamic allocation and efficient utilization of resources. At the same time, strict security policies are implemented, including network isolation, data encryption, identity authentication and authorization, to ensure the security and compliance of the cloud environment. Using tools such as Prometheus, Grafana and Elasticsearch, the intelligentization of cloud environment performance monitoring and log management is realized to ensure stable operation of the system. In addition, an intuitive and easy-to-use user interface and a comprehensive API interface are provided, supporting multiple protocols such as RESTful and GraphQL, which not only simplifies the operation process of users and administrators, but also meets the flexible call requirements of developers and automation tools for cloud resources, laying a solid, flexible and easy-to-maintain foundation for upper-level application services. The method and system adopt the OpenStack cloud resource collaborative management and cross-domain integration mode to integrate cross-domain resources, thereby improving the cross-domain network, resource utilization and operation and maintenance efficiency from the overall structure; and by establishing a data center, cross-domain resources are uniformly managed through Openstack, thereby improving the co-management and sharing capabilities of resources.

[0080] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present invention.

Claims

1. A method for cross-domain integration of OpenStack cloud resources, characterized in that: include: Establishing remote networks between data centers and remote sites in different regions; Connecting the original OpenStack of each remote site to the data center through each remote network; Deploy a new OpenStack and connect the new OpenStack to the data center; Creating tenants for different regions in the new OpenStack; Tenants in various regions and existing OpenStack in various regions collaboratively use cloud resources through the data center.

2. The method according to claim 1, characterized in that The remote network is established between the data center and remote sites in different regions, including: Establish VPN tunnels between data centers and remote sites in different regions; The SDN controller is logged in through the VPN tunnel, and a smart contract is configured in the SDN controller. The smart contract is used to calculate the optimal routing path according to the network status data from the SDN controller and the voting or weight information of the blockchain node.

3. The method according to claim 1, characterized in that Deploying a new OpenStack includes: Deploy Kubernetes clusters in the data center and at each remote site, and deploy new OpenStack components; Use Kubernetes persistent volumes to provide storage support for the new OpenStack; Configure the Kubernetes network plug-in to ensure network communication between Kubernetes and the new OpenStack.

4. The method according to claim 3, characterized in that The deployment of the new OpenStack also includes: Through a cross-platform blockchain client, the interaction between Kubernetes and the new OpenStack and the blockchain is realized, and the blockchain is used to record and verify the resource scheduling of the new OpenStack; Through smart contracts, a signature and verification mechanism is established between Kubernetes and the new OpenStack.

5. The method according to claim 3, characterized in that: The step of creating tenants for different regions in the new OpenStack includes: Create multiple namespaces in Kubernetes, each corresponding to an OpenStack tenant in a different region; Implement role-based access control policies to ensure that each tenant can only access authorized resources; Use Kubernetes' scheduler and load balancer to optimize the allocation and use of OpenStack resources.

6. The method according to claim 3, characterized in that Kubernetes and the new OpenStack record and verify the resource scheduling of the new OpenStack through blockchain; Accordingly, after creating tenants for different regions in the new OpenStack, the following steps are also included: Deploy a blockchain-based resource sharing API for each tenant, which is used to publish, request, match and confirm resources on the blockchain; Smart contract templates and parameterized configuration tools are deployed on each tenant to allow users to customize incentive mechanisms and rules.

7. The method according to claim 3, characterized in that Kubernetes and the new OpenStack record and verify the resource scheduling of the new OpenStack through blockchain; The method further comprises: Deploy a blockchain-based operation and maintenance monitoring plug-in to write monitoring data into the blockchain in real time; Fault detection, diagnosis and response rules are defined through smart contracts to automatically execute corresponding recovery strategies and record the response results back to the blockchain when a fault occurs.

8. The method according to claim 7, characterized in that Also includes: Deploy Prometheus and Grafana monitoring tools to monitor the operating status of OpenStack and Kubernetes in real time; Through API interfaces or message queues, the monitoring data on the blockchain is synchronized in real time to the Prometheus and Grafana monitoring tools.

9. The method according to claim 1, characterized in that: The tenants in each region and the existing OpenStack in each region use cloud resources in a collaborative manner through the data center, including: Tenants in each region and the original OpenStack in each region send their respective cloud resource usage information to the data center; In response to resource usage requirements, tenants in various regions or existing OpenStacks in various regions initiate resource call requests to the data center; In response to the resource call request, the data center performs unified cloud resource scheduling according to the overall cloud resource usage.

10. An OpenStack cloud resource cross-domain fusion system, characterized in that: include: Data centers and remote sites in different regions; Wherein, a remote network is established between the data center and each remote site; The existing OpenStack at each remote site is connected to the data center through each remote network; Tenants in different regions are created in the new OpenStack, and the new OpenStack is also connected to the data center; Tenants in various regions and existing OpenStack in various regions collaboratively use cloud resources through the data center.

Images