Private cloud data center IPv6 upgrade method, equipment and storage medium

Abstract

The present application discloses a method, device and storage medium for upgrading IPv6 in a private cloud data center, and relates to the field of communication technology. The method comprises: upgrading and converting the basic network environment of the private cloud data center to the dual protocol stack of IPv4 and IPv6; determining a single service according to the composition and deployment mode of the service of the private cloud data center; determining a dual stack node in the single service, and building an Nginx proxy on the dual stack node according to a preset transformation sequence. The present application enables the private cloud data center to support both IPv4 and IPv6 protocols at the same time, and realize compatibility and intercommunication with different network environments.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for upgrading IPv6 in a private cloud data center. Background Art

[0002] With the rapid development of emerging technologies such as the Internet of Things and 5G, IPv4 address resources are close to exhaustion. In order to support the connection needs of all devices in the world and provide sufficient address space for the future development of the Internet, IPv6 transformation is needed. At present, dual-stack protocol technology is usually adopted to enable both IPv4 and IPv6 protocol stacks on nodes at the same time to achieve a smooth transition of the network to IPv6.

[0003] However, when IPv6 transformation is carried out through dual-stack protocol technology, since some services are gradually established with business development and technology iteration, these services, although upgraded and modified many times, still retain the early technical architecture and code base. There may be problems that these early technology stacks and protocol developments may be incompatible with the dual-stack mode. Upgrading services to support the dual-stack mode may require a lot of code modification and testing work, and may even require rewriting some functions. This increases the difficulty and risk of transformation.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a private cloud data center IPv6 upgrade method, device and storage medium, aiming to solve the technical problem of how to perform IPv6 transformation on a private cloud data center.

[0006] To achieve the above objectives, the present application proposes a private cloud data center IPv6 upgrade method, the method comprising:

[0007] Upgrade and convert the IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center;

[0008] Determine a single service based on the composition and deployment of services in the private cloud data center;

[0009] A dual-stack node is determined in the single service, and an Nginx proxy is built on the dual-stack node according to a preset transformation sequence.

[0010] In one embodiment, after the step of determining a single service according to the service deployment mode of the service of the private cloud data center, the step includes:

[0011] In the private cloud data center, determining a distributed deployment service;

[0012] According to the preset transformation order, for the distributed deployment service, a server is added as a first dual-stack execution node.

[0013] In one embodiment, for the distributed deployment service, the step of adding a server as a first dual-stack execution node includes:

[0014] Allocating an IPv4 address and an IPv6 address to the first dual-stack execution node;

[0015] Establishing a connection between the first dual-stack execution node and a control node in the distributed deployment service, and between the first dual-stack execution node and an execution node in the distributed deployment service;

[0016] Obtain a configuration file of the distributed deployment service, and add information of the first dual-stack execution node to the configuration file;

[0017] Add the first dual-stack execution node to the distributed deployment service, and update the status of the distributed deployment service.

[0018] In one embodiment, the step of building an Nginx proxy on the dual-stack node according to a preset transformation order includes:

[0019] Selecting a second dual-stack execution node in the single service, and installing an Nginx proxy on the second dual-stack execution node;

[0020] Configure the proxy rules of the Nginx proxy to convert IPv6 requests into IPv4 requests and forward them to the single service.

[0021] In one embodiment, after the step of upgrading and converting the basic network environment of the private cloud data center to the dual protocol stack of IPv4 and IPv6, the following steps are included:

[0022] Determine the calling relationship of each service of the private cloud data center according to the business architecture diagram;

[0023] The services are sorted according to the calling relationship to obtain the transformation order.

[0024] In one embodiment, the step of upgrading and converting the basic network environment of the private cloud data center to the dual protocol stack of IPv4 and IPv6 includes:

[0025] Upgrade the network equipment hardware and configure the IPv6 address after the upgrade is completed;

[0026] The IPv6 address is spatially allocated and divided.

[0027] In one embodiment, the step of allocating and dividing the IPv6 address space includes:

[0028] Upgrade the NTP server and DNS server to versions that support IPv6;

[0029] The upgraded NTP server and the DNS server are configured to enable IPv6 monitoring.

[0030] In one embodiment, after the step of determining the dual-stack node in the single service and building the Nginx proxy on the dual-stack node according to a preset transformation order, the following steps are included:

[0031] Set the test source, target IPv4 address and target IPv6 address;

[0032] Sending data packets to the target IPv4 address and the target IPv6 address respectively at a preset interval;

[0033] Obtaining and calculating a response difference between the response times of the target IPv4 address and the target IPv6 address;

[0034] If the response difference is greater than or equal to a preset difference range, the network environment and the configuration of the service are verified.

[0035] In addition, to achieve the above-mentioned objectives, the present application also proposes a private cloud data center IPv6 upgrade device, wherein the private cloud data center IPv6 upgrade device comprises: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the private cloud data center IPv6 upgrade method as described above.

[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the private cloud data center IPv6 upgrade method described above are implemented.

[0037] The present application provides a method for upgrading IPv6 in a private cloud data center. First, the basic network environment of the private cloud data center is upgraded and converted to the dual protocol stack of IPv4 and IPv6. By first transforming the basic network service, it can be ensured that the network infrastructure of the private cloud data center can support both IPv4 and IPv6 protocols. It can improve the compatibility of the network infrastructure and provide good support and guarantee for subsequent service transformation. Secondly, according to the composition and deployment mode of the service of the private cloud data center, the monomer service in the private cloud data center is determined. For the monomer service, a dual stack node is selected, and an Nginx proxy is built on the dual stack node according to the preset transformation order. By building an Nginx proxy on the dual stack node of the monomer service, it is possible to process IPv4 and IPv6 traffic at the same time and forward the request to the monomer service at the back end. By building an Nginx proxy, dual stack support can be achieved without directly modifying the monomer service code. The risk of upgrading is reduced. In addition, through dual stack transformation, the service can support both IPv4 and IPv6 protocols at the same time, and achieve compatibility and intercommunication with different network environments. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0040] Figure 1 A flowchart of the first embodiment of the method for upgrading IPv6 in a private cloud data center of this application is provided;

[0041] Figure 2 A network communication diagram for transforming a single service provided in Example 1 of the private cloud data center IPv6 upgrade method of the present application;

[0042] Figure 3 A flow chart of the second embodiment of the method for upgrading IPv6 in a private cloud data center of this application;

[0043] Figure 4 A detailed flow chart of the second embodiment of the method for upgrading IPv6 in a private cloud data center of this application;

[0044] Figure 5A network communication diagram for transforming a distributed deployment service provided in Example 2 of the private cloud data center IPv6 upgrade method of this application;

[0045] Figure 6 A flowchart of the third embodiment of the method for upgrading IPv6 in a private cloud data center of this application is provided;

[0046] Figure 7 This is a schematic diagram of the device structure of the hardware operating environment involved in the private cloud data center IPv6 upgrade method in the embodiment of the present application. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0049] The main solution of the embodiment of the present application is: to upgrade and convert the IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center; to determine a single service based on the composition and deployment method of the services of the private cloud data center; to determine the dual stack nodes in the single service, and to build an Nginx proxy on the dual stack nodes according to a preset transformation order.

[0050] With the rapid development of emerging technologies such as the Internet of Things and 5G, IPv4 address resources are close to exhaustion. In order to support the connection needs of all devices in the world and provide sufficient address space for the future development of the Internet, IPv6 transformation is needed. At present, dual-stack protocol technology is usually adopted to enable both IPv4 and IPv6 protocol stacks on nodes at the same time to achieve a smooth transition of the network to IPv6.

[0051] However, when IPv6 transformation is carried out through dual-stack protocol technology, since some services are gradually established with business development and technology iteration, these services, although upgraded and modified many times, still retain the early technical architecture and code base. There may be problems that these early technology stacks and protocol developments may be incompatible with the dual-stack mode. Upgrading services to support the dual-stack mode may require a lot of code modification and testing work, and may even require rewriting some functions. This increases the difficulty and risk of transformation.

[0052] The present application provides a method for upgrading IPv6 in a private cloud data center. The present application provides a method for upgrading IPv6 in a private cloud data center. First, the basic network environment of the private cloud data center is upgraded and converted to the dual protocol stack of IPv4 and IPv6. By first transforming the basic network service, it can be ensured that the network infrastructure of the private cloud data center can support both IPv4 and IPv6 protocols. It can improve the compatibility of the network infrastructure and provide good support and guarantee for subsequent service transformation. Secondly, according to the composition and deployment mode of the service of the private cloud data center, the monomer service in the private cloud data center is determined. For the monomer service, a dual stack node is selected, and an Nginx proxy is built on the dual stack node according to the preset transformation order. By building an Nginx proxy on the dual stack node of the monomer service, it is possible to process IPv4 and IPv6 traffic at the same time and forward the request to the monomer service at the back end. By building an Nginx proxy, dual stack support can be achieved without directly modifying the monomer service code. The risk of upgrading is reduced. In addition, through dual stack transformation, the service can support both IPv4 and IPv6 protocols at the same time, and achieve compatibility and intercommunication with different network environments.

[0053] It should be noted that the execution subject of this embodiment can be a computing service device with network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a device, etc. that can realize the above functions. The following takes the private cloud data center IPv6 upgrade device as an example to illustrate this embodiment and the following embodiments.

[0054] Based on this, the embodiment of the present application provides a private cloud data center IPv6 upgrade method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the private cloud data center IPv6 upgrade method of the present application.

[0055] In this embodiment, the private cloud data center IPv6 upgrade method includes steps S100 to S300:

[0056] Step S100, upgrading and converting the IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center.

[0057] It should be noted that a private cloud data center is a deployment model based on cloud computing technology. It is a cloud computing environment built and managed by an enterprise or organization itself. IPv4 (Internet Protocol version 4) is one of the core protocols in the Internet Protocol Suite (TCP / IP protocol) and is used to assign unique addresses (i.e. IPv4 addresses) to devices on the Internet. IPv4 addresses consist of 32-bit binary numbers and are usually expressed in dotted decimal form, such as 192.168.1.1. IPv6 (Internet Protocol version 6) is the next generation version of IPv4, designed to solve the problem of insufficient IPv4 address space. IPv6 addresses consist of 128-bit binary numbers, providing a huge address space.

[0058] In this embodiment, the basic network environment includes: DNS service, which is responsible for domain name resolution and is the basis of network communication. It is necessary to ensure that it can handle domain name resolution requests for IPv4 and IPv6 at the same time. DHCP service: responsible for the dynamic allocation of IP addresses. In a dual-stack environment, the DHCP service needs to be able to allocate IPv4 and IPv6 addresses at the same time. Load balancing service: During peak network traffic, the load balancing service can ensure that traffic is reasonably distributed to multiple servers. It is necessary to ensure that the load balancing service supports IPv6 traffic. Firewall service: responsible for filtering and monitoring network traffic. It is necessary to ensure that it can handle IPv4 and IPv6 traffic at the same time and provide corresponding security policies. Intrusion Detection System (IDS): responsible for monitoring abnormal behavior in network traffic. It is necessary to ensure that it can detect potential threats in IPv6 traffic. VPN service: If remote access to a private cloud data center is required, VPN service is essential. It is necessary to ensure that it supports the establishment and maintenance of IPv6 tunnels. Content Distribution Network (CDN): If a private cloud data center provides content distribution services, it is necessary to ensure that its CDN supports the distribution of IPv6 traffic.

[0059] In this embodiment, the existing network architecture is evaluated and its compatibility and scalability are analyzed. Determine which devices and services need to be upgraded or replaced to support IPv6. Based on the evaluation results, a detailed transformation plan is developed. Upgrade or replace devices that do not support IPv6, and ensure that the new or upgraded devices have been correctly configured with dual stack technology. Enable IPv6-related protocols and configurations on network devices. Configure network services such as DNS, DHCP, and load balancing to support IPv6.

[0060] In a feasible implementation, step S100 may include the following steps:

[0061] Upgrade the network device hardware and configure the IPv6 address after the upgrade is complete.

[0062] The IPv6 address is spatially allocated and divided.

[0063] Upgrade the NTP server and DNS server to versions that support IPv6.

[0064] The upgraded NTP server and the DNS server are configured to enable IPv6 monitoring.

[0065] In this implementation, check whether network devices (such as routers, switches, firewalls, etc.) support dual stack technology. For devices that do not support dual stack, develop an upgrade or replacement plan. Develop a detailed dual stack transformation plan based on the demand analysis and device compatibility check results. The plan should include transformation steps, risk assessment, backup and recovery plans, etc. According to the plan, upgrade or replace devices that do not support dual stack, and ensure that the new or upgraded devices have been correctly configured with dual stack technology. Enable IPv6 routing protocols (such as OSPFv3, BGP4+, etc.) on network devices. Configure IPv6 address pools and subnet divisions. Configure IPv6 static routing or dynamic routing protocols. Verify the configuration in a test environment to ensure that the network equipment can correctly handle IPv4 and IPv6 traffic.

[0066] In this implementation, the switch is upgraded and a switch that supports dual protocol stacks (IPv4 and IPv6) is selected to ensure that the switch can process both IPv4 and IPv6 packets. The operating system and firmware of the switch are upgraded to ensure that they support the latest dual stack functions. The IPv6 address and related routes of the switch are configured to ensure that IPv6 traffic can be correctly transmitted in the network.

[0067] In this implementation, IPv6 addresses are divided into different address segments according to the network topology and business requirements. Determine the purpose and scenario of each address segment, such as intranet address, extranet address, special-purpose address, etc. According to the address segment division results, IPv6 addresses are allocated to various network devices and services. Establish an IP address management system to record and manage the allocation and use of IPv6 addresses. Formulate IPv6 address management strategies, including processes such as address application, allocation, recovery, and change. Regularly audit and clean up IPv6 addresses to ensure the effective use of address resources.

[0068] In this implementation, the IPv6 address resolution function is enabled on the DNS (Domain Name System) server. IPv6-related DNS records such as A6 and AAAA records are configured. Ensure that the DNS server can handle both IPv4 and IPv6 domain name resolution requests. Verify the configuration of the DNS server in a test environment to ensure that the DNS server can correctly resolve IPv4 and IPv6 addresses.

[0069] In this implementation, deploy an IPv6-enabled firewall at the network edge and configure firewall rules to allow or deny specific ports and protocols for IPv6 traffic. Deploy an intrusion detection system. Deploy an IPv6-enabled intrusion detection system at the network edge and configure the intrusion detection system to monitor abnormal behavior in IPv6 traffic. Verify the configuration of the firewall and intrusion detection system in a test environment to ensure that the security device can correctly handle IPv4 and IPv6 traffic and protect the network from security threats.

[0070] In this embodiment, a dual stack is configured on the NTP (Network Time Protocol) server so that it can listen to both IPv4 and IPv6 addresses. The IPv6 address and port are specified in the configuration file of the NTP server, and it is ensured that the NTP daemon can be correctly started and listen to the corresponding address and port. The configuration of the NTP client is updated so that it can communicate with the NTP server using the IPv6 address. This usually involves modifying the client's configuration file, specifying the IPv6 address of the NTP server, and configuring the corresponding synchronization policy. Upgrade the mirror station software to support IPv6. Update the mirror station software version and configure the corresponding IPv6 support options. Ensure that the content of the mirror station can be correctly accessed by the IPv6 client.

[0071] Step S200: determining a single service according to the composition and deployment mode of the services of the private cloud data center.

[0072] Step S300, determining a dual-stack node in the single service, and building an Nginx proxy on the dual-stack node according to a preset transformation sequence.

[0073] It should be noted that services can be divided into distributed deployment services and monolithic services according to the service deployment and composition methods. The monolithic service architecture pattern is usually suitable for smaller systems or applications, and its characteristic is that all business logic is concentrated in a single service. The advantage of this architecture pattern is that it is simple to deploy and easy to manage, but the disadvantage is that as the system expands, the code will become complex and difficult to maintain, and the scalability and fault tolerance of the system will also be limited. The distributed service architecture pattern splits the business logic into multiple independent services, each of which can be independently deployed, independently expanded, and independently managed. The advantage of this architecture pattern is that it improves the scalability, fault tolerance, and maintainability of the system, but the disadvantage is that it increases the complexity of system deployment and management.

[0074] In addition, it should be noted that Nginx is a high-performance HTTP and reverse proxy server that can distribute requests to multiple backend servers to achieve load balancing and failover.

[0075] In this embodiment, it is determined whether the deployment mode of each service is a single deployment or a distributed deployment. According to the deployment mode of the service, the transformation mode of each service is further determined. According to the preset transformation order, each single service is dual-stack transformed. Dual-stack transformation means that the service will support both IPv4 and IPv6 protocols in order to maintain compatibility with the existing IPv4 network during the migration process and gradually transition to the IPv6 network. The transformation mode of the single service is to build an Nginx proxy. Install the Nginx software on the server, and configure Nginx's proxy rules, load balancing strategy, etc. according to requirements. Start the Nginx service so that it starts listening and processing requests.

[0076] In a feasible implementation, step S300 may include:

[0077] A second dual-stack execution node is selected in the single service, and an Nginx proxy is installed on the second dual-stack execution node.

[0078] Configure the proxy rules of the Nginx proxy to convert IPv6 requests into IPv4 requests and forward them to the single service.

[0079] It should be noted that the nginx proxy service plays an important role in Internet requests and realizes the communication between the client and the server.

[0080] In this embodiment, in the private cloud data center, the single service includes a cloud management platform; virtualization services, such as KVM (Kernel-based Virtual Machine), Xen, etc.; identity authentication and authorization services, such as LDAP (Lightweight Directory Access Protocol), Kerberos, etc.; log and monitoring services, such as ELK Stack (Elasticsearch, Logstash, Kibana), Prometheus, etc.

[0081] In this embodiment, if Figure 2 As shown in the figure, for the single service, a dual-stack node is used to build an nginx proxy to achieve 6 to 4 transformation. Install and configure nginx on the second dual-stack node so that it can act as a reverse proxy server. Configure nginx's proxy rules to convert IPv6 requests to IPv4 requests and forward them to the original single service. Make necessary configuration adjustments to the original single service to ensure that it can communicate normally with the nginx proxy server.

[0082] In this implementation, a dual-stack node is selected as the second dual-stack node in the single service, and the Nginx proxy is downloaded and installed on the second dual-stack execution node. Instructions for listening to IPv4 and IPv6 addresses are configured in the Nginx configuration file. A server block or location block is created for IPv6 requests that need to be converted, and the proxy_pass instruction is used to forward the request to the IPv4 backend server. Before starting Nginx, use the command provided by Nginx (such as nginx -t) to check whether the syntax of the configuration file is correct.

[0083] In this implementation, Nginx is used as a conversion tool to achieve IPv6 to IPv4 address conversion, thereby allowing IPv6 clients to access IPv4 resources. Since the single service itself already has very complex calling situations, the above steps avoid the need to transform the single service itself, which would lead to problems such as difficulty in ensuring data consistency and long transformation cycles.

[0084] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 3 , after step S200, steps A100 to A200 may be included:

[0085] Step A100, determining a distributed deployment service in the private cloud data center;

[0086] Step A200: adding a server as a first dual-stack execution node to the distributed deployment service according to the preset transformation sequence.

[0087] In this embodiment, when the service is deployed in a distributed manner, IPv6 transformation is performed by expanding the node capacity. According to system requirements, a new server or virtual machine is prepared as a new node, and necessary configuration is performed on the new node, including installing an operating system, deploying applications, etc. After the configuration is completed, the new node is added to the distributed system so that it can work in conjunction with other nodes. Finally, verification and testing are performed to ensure that it can work normally and meet system requirements.

[0088] Please refer to Figure 4 In a feasible implementation manner, step A200 may include steps A210 to A240:

[0089] Step A210, allocating an IPv4 address and an IPv6 address to the first dual-stack execution node;

[0090] Step A220: establishing a connection between the first dual-stack execution node and the control node in the distributed deployment service, and between the first dual-stack execution node and the execution node in the distributed deployment service;

[0091] It should be noted that the control node is responsible for receiving and managing task requests from users, and distributing tasks to appropriate execution nodes according to the type and requirements of the tasks. The execution nodes are responsible for actually executing the tasks received from the control node.

[0092] In this embodiment, in the private cloud data center, the distributed deployment services include the cloud platform cloud automation engine (CAE), distributed storage services, such as distributed file systems (such as Hadoop HDFS), distributed object storage (such as Ceph), etc. Distributed database services, such as distributed relational databases (such as CockroachDB), distributed NoSQL databases (such as Cassandra, MongoDB), etc. Distributed cache services, such as Redis, Memcached, etc. Distributed computing services, such as Apache Spark, Hadoop MapReduce, etc.

[0093] In this embodiment, if Figure 5As shown, for some services that adopt distributed deployment, a dual-stack node is added by node expansion to realize the management of IPv6 services. First, the specifications and deployment location of the first dual-stack node are determined according to the network topology, data center layout and business needs. When determining the specifications, the computing power (such as CPU, memory), storage capacity, network bandwidth and other factors of the node are considered, and the node specifications that can meet the current and future business needs are selected. When determining the deployment location, it is determined according to the network topology, data center layout and business needs, and the impact of the physical location of the node on latency, bandwidth and fault recovery is considered. Secondly, the first dual-stack execution node is added to the service cluster that adopts distributed deployment, and the cluster configuration file is modified to include the information of the new node.

[0094] In this embodiment, an IPv4 address and an IPv6 address are assigned to the first dual stack execution node, and these addresses are set in the network configuration of the operating system to ensure that they can be correctly resolved and routed. The network interfaces of the first dual stack execution node are configured to ensure that they can handle both IPv4 and IPv6 traffic. Ping or other network tools are executed on the first dual stack execution node to test IPv4 and IPv6 connectivity respectively. If a response is received from the target node, it indicates that the connectivity is normal; if no response is received, there may be a network problem or a firewall / security group policy blocking the connection.

[0095] Step A230, obtaining a configuration file of the distributed deployment service, and adding information of the first dual-stack execution node to the configuration file;

[0096] Step A240: Add the first dual-stack execution node to the distributed deployment service, and update the status of the distributed deployment service.

[0097] In this implementation, the configuration file of the cluster is found according to the type of cluster and the technology stack used. There may be one or more configuration files, depending on the architecture of the cluster and the management tools used. Add the information of the new node to the configuration file, including the node's IP address (IPv4 and IPv6), host name, role (such as master node, slave node, etc.), etc., and save the modified configuration file. Make sure that the configuration of the new node is consistent with the configuration of the existing nodes to avoid configuration conflicts. If the cluster uses a distributed configuration management tool (such as Consul, Etcd, etc.), distribute the configuration information of the new node to all nodes. Update the status of the cluster according to the cluster management tool used so that the cluster can recognize the newly added node.

[0098] In this implementation, you can use ping, telnet, or other network tools to verify that the new node has smooth IPv4 and IPv6 network communication with existing nodes. Check the cluster's log files to ensure that there are no errors or warnings related to the new node. If the cluster is configured with a load balancer, ensure that the new node has been correctly added to the load balancer's backend node list. Perform failover tests to verify that the new node can take over and handle traffic in the event of a failure.

[0099] Optionally, after adding a new dual-stack execution node, adjust the load balancing strategy to balance IPv4 and IPv6 traffic. Use network traffic analysis tools (such as Prometheus, Grafana, etc.) to collect IPv4 and IPv6 traffic data for existing services. Record traffic changes in different time periods (such as weekdays, weekends, holidays), as well as traffic distribution in different business scenarios, and calculate the ratio of IPv4 and IPv6 traffic. Determine the weight distribution on different nodes based on the ratio of IPv4 and IPv6 traffic. If IPv6 traffic is less, the weight can be appropriately reduced to reduce resource waste. According to business needs and traffic characteristics, use distribution strategies such as polling, least connections, and source addresses to ensure balanced distribution of traffic.

[0100] In this implementation, according to the scale and business needs of the private cloud data center, select a suitable load balancer (such as a hardware load balancer, a software load balancer, etc.) to ensure that the load balancer supports IPv6 and has high performance, high availability and other characteristics. According to the type of load balancer, modify the corresponding configuration file to add support for IPv6 addresses. Configure the virtual IP address (VIP) of the load balancer to ensure that the VIP supports both IPv4 and IPv6. After the configuration is complete, test the load balancer to ensure that it can correctly identify and distribute IPv6 traffic. The test content includes but is not limited to: distribution of IPv6 traffic, failover, health check, etc.

[0101] Optionally, you can monitor traffic changes and dynamically adjust the load balancing strategy based on real-time traffic data. Select network traffic monitoring tools such as Prometheus, Grafana, Zabbix, etc. to obtain real-time traffic data analysis and visualization. Monitor key network traffic indicators, such as total traffic, IPv4 / IPv6 traffic ratio, traffic load of each node, etc. Use automation tools such as scripts and APIs to automatically adjust the load balancing strategy. Automatically adjust the configuration parameters of the load balancer, such as weights, distribution rules, etc., based on monitoring data. For example, when the traffic load of a node reaches the preset maximum threshold, increase the weight of the node or add a new node to share the traffic; when IPv6 traffic increases, adjust the strategy to give priority to IPv6 traffic.

[0102] Optionally, you can also analyze the source address, destination address, access time, etc. of user access to identify the main access patterns and traffic hotspots. Based on the access pattern, determine whether traffic optimization is needed for specific user groups or business scenarios.

[0103] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. Figure 6 , before step S200, it also includes steps B100 to B200:

[0104] Step B100, determining the calling relationship of each service of the private cloud data center according to the business architecture diagram;

[0105] Step B200, sorting the services according to the calling relationship to obtain the transformation order.

[0106] In this embodiment, the call relationship between each service in the private cloud data center is sorted out, including identifying the dependency between services, data flow direction, and communication protocol. Through this process, a clear service call relationship diagram is constructed, which shows the interaction and connection between services. According to the service call relationship diagram, a transformation path diagram is further generated. The path diagram specifies a specific order for transforming services to determine which services need to be transformed to IPv6 first to ensure that the impact on the business is minimized. For example, the purchase of a database depends on cloud hosts, internal mirror stations, and other related transformations.

[0107] In this embodiment, first, all services in the private cloud data center are obtained. These services may include virtualization services, distributed storage services, distributed database services, identity authentication and authorization services, log and monitoring services, container services, backup and recovery services, API gateway services, message queue services, and Web services. Secondly, the dependencies between these services are analyzed. This includes strong dependencies and weak dependencies. Strong dependency means that a service must rely on the normal operation of another service to provide services, while weak dependency means that a service can still provide services when another service is unavailable (but the functions may be limited). The analyzed dependencies are recorded.

[0108] In this example, you can also analyze the direction of data flow between services. This includes which service the data flows from and to which service, as well as the specific path of the data flow. Record the analyzed data flow direction. You can also identify the communication protocols used between services. These protocols may include HTTP, HTTPS, TCP, UDP, RESTful API, etc. Record the analyzed communication protocols and determine whether IPv6 transformation is required for these protocols.

[0109] In this embodiment, a service call relationship diagram is drawn in a drawing tool according to dependency relationships, data flow directions, and communication protocols. The diagram should include icons of each service, dependency arrows, data flow arrows, and communication protocol labels. Different colors or shapes can be used to distinguish different types of services, and arrows and labels can be used to clearly indicate dependency relationships and data flow directions.

[0110] In this embodiment, the dependency relationship can also be determined through the service interface document. The services in the private cloud data center usually have detailed interface documents that describe the input and output of the service, the calling method, and the interaction with other services. By consulting these documents, the calling relationship and dependency between services can be understood. The call chain between services can also be identified by analyzing the service code. This usually involves parsing the method calls, network communications, and other parts in the code. Traffic analysis tools (such as Wireshark, tcpdump, etc.) can also be deployed on key nodes of the network to capture the communication traffic between services. By analyzing these traffic data, the calling relationship and communication mode between services can be identified. It is also possible to automatically discover the calling relationship between services and generate a visual service graph based on tools specifically used for service mapping (such as AppDynamics, Dynatrace, etc.).

[0111] In this implementation, a log collection system (such as ELK Stack, Splunk, etc.) is configured to capture service logs, and log analysis tools (such as Logstash, Kibana, etc.) are used to parse the logs and extract call information between services. Select service dependency analysis tools suitable for private cloud data centers, such as Apache SkyWalking, Prometheus, etc., and configure these tools to monitor the call relationships between services. Analyze the output of the tools regularly to identify the call chains and dependencies between services. Establish a communication channel with the service development team to understand the call relationships and business logic between services. Verify whether the call relationships collected through logs and tools are consistent with the descriptions of the development team.

[0112] In this implementation, the collected call relationship data is organized into a structured format, such as a table or database. A unique identifier is assigned to each service, and its pre-dependencies and post-dependencies are recorded. An automated testing tool or script is used to simulate calls between services to verify the accuracy of the call relationship. Communicate with the development team to resolve any possible call relationship inconsistencies or omissions. As services are updated and changed, the call relationship data is updated regularly. Ensure that the call relationship data always reflects the latest call relationships between services in the private cloud data center.

[0113] Based on the first embodiment of the present application, in the fourth embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. On this basis, after step S300, the following steps may be further included:

[0114] Set the test source, target IPv4 address and target IPv6 address;

[0115] Sending data packets to the target IPv4 address and the target IPv6 address respectively at a preset interval;

[0116] Obtaining and calculating a response difference between the response times of the target IPv4 address and the target IPv6 address;

[0117] If the response difference is greater than or equal to a preset difference range, the network environment and the configuration of the service are verified.

[0118] In this embodiment, the test source and target address are set, and the target address selects IPv4 and IPv6 addresses respectively. Determine the number of tests and the interval time, use the ping command to send data packets to the IPv4 and IPv6 target addresses respectively, and record the response time, and take the average value as the final response time to reduce accidental errors. Calculate the difference between the two average response times. If the response difference exceeds the preset difference range, further verification steps are triggered, such as checking the network configuration, routing rules, DNS resolution, etc., to avoid the problem that the IPv6 configuration is incorrect or conflicts with the IPv4 configuration.

[0119] In this embodiment, the IPv4 and IPv6 routing tables on the network device can be checked to ensure that the routing configuration is correct and there is no conflict, so as to verify whether the network device (such as a router, switch, etc.) has been correctly configured to support dual stacks. It can also be verified whether each service has been correctly configured to support dual stacks and can handle IPv4 and IPv6 traffic at the same time. Parameters such as bandwidth and queue management of the network device can also be adjusted to optimize network performance.

[0120] The present application provides a private cloud data center IPv6 upgrade device, which private cloud data center IPv6 upgrade device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the private cloud data center IPv6 upgrade method in the above-mentioned embodiment one.

[0121] Reference below Figure 7 , which shows a schematic diagram of the structure of a private cloud data center IPv6 upgrade device suitable for implementing the embodiment of the present application. The private cloud data center IPv6 upgrade device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (portable android devices), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The private cloud data center IPv6 upgrade device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0122] like Figure 7As shown, the private cloud data center IPv6 upgrade device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the private cloud data center IPv6 upgrade device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the private cloud data center IPv6 upgrade device to communicate wirelessly or wired with other devices to exchange data. Although the private cloud data center IPv6 upgrade device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have alternatively.

[0123] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0124] The private cloud data center IPv6 upgrade device provided by the present application adopts the private cloud data center IPv6 upgrade method in the above embodiment, which can solve the technical problem of how to perform IPv6 transformation on the private cloud data center. Compared with the prior art, the beneficial effects of the private cloud data center IPv6 upgrade device provided by the present application are the same as the beneficial effects of the private cloud data center IPv6 upgrade method provided in the above embodiment, and other technical features in the private cloud data center IPv6 upgrade device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0125] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0126] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0127] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the private cloud data center IPv6 upgrade method in the above-mentioned embodiment.

[0128] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0129] The above-mentioned computer-readable storage medium may be included in the private cloud data center IPv6 upgrade device; or it may exist independently without being assembled into the private cloud data center IPv6 upgrade device.

[0130] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the private cloud data center IPv6 upgrade device, the private cloud data center IPv6 upgrade device: performs an upgrade and conversion of the IPv4 and IPv6 dual protocol stacks on the basic network environment of the private cloud data center; determines a single service based on the composition and deployment method of the services of the private cloud data center; determines a dual-stack node in the single service, and builds an Nginx proxy on the dual-stack node according to a preset transformation order.

[0131] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0132] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0133] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0134] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned private cloud data center IPv6 upgrade method, and can solve the technical problem of how to perform IPv6 transformation on the private cloud data center. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the private cloud data center IPv6 upgrade method provided in the above-mentioned embodiment, and will not be repeated here.

[0135] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A private cloud data center IPv6 upgrade method, characterized in that: The method includes: Upgrade and convert the IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center; Determine a single service based on the composition and deployment of services in the private cloud data center; A dual-stack node is determined in the single service, and an Nginx proxy is built on the dual-stack node according to a preset transformation sequence.

2. The private cloud data center IPv6 upgrade method according to claim 1, characterized in that: After the step of determining a single service according to the service deployment mode of the service of the private cloud data center, the following steps are included: In the private cloud data center, determining a distributed deployment service; According to the preset transformation order, for the distributed deployment service, a server is added as a first dual-stack execution node.

3. The private cloud data center IPv6 upgrade method according to claim 2, characterized in that: For the distributed deployment service, the step of adding a server as a first dual-stack execution node includes: Allocating an IPv4 address and an IPv6 address to the first dual-stack execution node; Establishing a connection between the first dual-stack execution node and a control node in the distributed deployment service, and between the first dual-stack execution node and an execution node in the distributed deployment service; Obtain a configuration file of the distributed deployment service, and add information of the first dual-stack execution node to the configuration file; Add the first dual-stack execution node to the distributed deployment service, and update the status of the distributed deployment service.

4. The private cloud data center IPv6 upgrade method according to claim 1, characterized in that: The steps of building the Nginx proxy on the dual-stack node according to the preset transformation order include: Selecting a second dual-stack execution node in the single service, and installing an Nginx proxy on the second dual-stack execution node; Configure the proxy rules of the Nginx proxy to convert IPv6 requests into IPv4 requests and forward them to the single service.

5. The private cloud data center IPv6 upgrade method according to claim 1, characterized in that: After the step of upgrading and converting the IPv4 and IPv6 dual protocol stacks in the basic network environment of the private cloud data center, the following steps are included: Determine the calling relationship of each service of the private cloud data center according to the business architecture diagram; The services are sorted according to the calling relationship to obtain the transformation order.

6. The private cloud data center IPv6 upgrade method according to claim 1, characterized in that: The steps of upgrading and converting the IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center include: Upgrade the network equipment hardware and configure the IPv6 address after the upgrade is completed; The IPv6 address is spatially allocated and divided.

7. The private cloud data center IPv6 upgrade method according to claim 6, characterized in that: The step of allocating and dividing the IPv6 address space comprises: Upgrade the NTP server and DNS server to versions that support IPv6; The upgraded NTP server and the DNS server are configured to enable IPv6 monitoring.

8. The private cloud data center IPv6 upgrade method according to claim 1, characterized in that: After the step of determining the dual-stack node in the single service and building the Nginx proxy on the dual-stack node according to the preset transformation sequence, the following steps are included: Set the test source, target IPv4 address and target IPv6 address; Sending data packets to the target IPv4 address and the target IPv6 address respectively at a preset interval; Obtaining and calculating a response difference between the response times of the target IPv4 address and the target IPv6 address; If the response difference is greater than or equal to a preset difference range, the network environment and the configuration of the service are verified.

9. A private cloud data center IPv6 upgrade device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the private cloud data center IPv6 upgrade method according to any one of claims 1 to 8.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the private cloud data center IPv6 upgrade method according to any one of claims 1 to 8 are implemented.

Images