CN119766876A

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

Info

Publication number: CN119766876A
Application number: CN202411727541.4A
Authority: CN
Inventors: 徐飞; 李琦; 山金孝; 龙喜洋; 程叶锋
Original assignee: China Merchants Finance Technology Co Ltd
Current assignee: China Merchants Finance Technology Co Ltd
Priority date: 2024-11-28
Filing date: 2024-11-28
Publication date: 2025-04-04

Abstract

The application discloses an IPv6 upgrading method, equipment and a storage medium of a private cloud data center, and relates to the technical field of communication, wherein the method comprises the steps of upgrading and converting an IPv4 and IPv6 dual protocol stack for a basic network environment of the private cloud data center; and determining a dual-stack node in the single service, and building an Nginx proxy on the dual-stack node according to a preset reconstruction sequence. The application can make the private cloud data center support two protocols of IPv4 and IPv6 at the same time, and realize compatibility and intercommunication with different network environments.

Description

IPv6 upgrading method, equipment and storage medium for private cloud data center

Technical Field

The present application relates to the field of communications technologies, and in particular, to a private cloud data center IPv6 upgrade method, apparatus, and storage medium.

Background

With the rapid development of the emerging technologies such as the internet of things and 5G, the IPv4 address resource is nearly exhausted. In order to support the connection requirements of all devices worldwide, sufficient address space is provided for future development of the internet, and IPv6 transformation is required. Currently, a dual-stack protocol technology is generally adopted, and two protocol stacks of IPv4 and IPv6 are simultaneously started on a node to realize smooth transition of a network to IPv6.

However, when IPv6 is modified by the dual stack protocol technology, since some services are gradually built with the development of services and technology iteration, these services, though undergoing multiple upgrades and modifications, still retain the early technology architecture and code base. There may be problems in that these early technology stacks and protocol developments may not be compatible with the dual stack mode. Upgrading services to support dual stack mode may require extensive code modification and testing effort and may even require overwriting portions of the functionality. Increasing the difficulty and risk of modification.

The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present application and is not intended to represent an admission that the foregoing is prior art.

Disclosure of Invention

The application mainly aims to provide an IPv6 upgrading method, equipment and a storage medium for a private cloud data center, and aims to solve the technical problem of how to carry out IPv6 transformation on the private cloud data center.

In order to achieve the above purpose, the present application provides a private cloud data center IPv6 upgrade method, which includes:

upgrading and converting IPv4 and IPv6 dual protocol stacks for the basic network environment of the private cloud data center;

determining a monomer service according to the composition and deployment mode of the service of the private cloud data center;

And determining a double-stack node in the single service, and building an Nginx proxy on the double-stack node according to a preset transformation sequence.

In an embodiment, the step of determining the monomer service according to the service deployment mode of the service of the private cloud data center includes:

Determining distributed deployment services in the private cloud data center;

And adding a server as a first dual-stack execution node to the distributed deployment service according to the preset reconstruction sequence.

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

Distributing IPv4 addresses and IPv6 addresses to the first dual stack execution nodes;

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;

Acquiring a configuration file of the distributed deployment service, and adding information of the first dual-stack execution node into the configuration file;

and adding the first dual-stack execution node into the distributed deployment service, and updating the state of the distributed deployment service.

In an embodiment, the step of building the Nginx agent on the dual stack node according to a preset modification sequence includes:

selecting a second dual-stack execution node from the single service, and installing an Nginx agent on the second dual-stack execution node;

And configuring the proxy rule of the Nginx proxy, converting the IPv6 request into the IPv4 request, and forwarding the IPv4 request to the monomer service.

In an embodiment, after the step of performing upgrade conversion of the IPv4 and IPv6 dual protocol stack in the infrastructure network environment of the private cloud data center, the method includes:

Determining the calling relation of each service of the private cloud data center according to the service framework diagram;

And sequencing the services according to the calling relation to obtain the transformation sequence.

In an embodiment, the step of performing upgrade conversion of the IPv4 and IPv6 dual protocol stack for the base network environment of the private cloud data center includes:

upgrading the hardware of the network equipment, and configuring an IPv6 address after the upgrading is completed;

And carrying out space allocation and division on the IPv6 address.

In an embodiment, the step of allocating and dividing the space of the IPv6 address includes:

Upgrading the NTP server and the DNS server to a version supporting IPv 6;

And configuring the updated NTP server and the updated DNS server, and starting IPv6 monitoring.

In an embodiment, after the step of determining a dual stack node in the single service and setting up an Nginx proxy on the dual stack node according to a preset modification sequence, the method includes:

setting a test source, a target IPv4 address and a target IPv6 address;

respectively sending data packets to the target IPv4 address and the target IPv6 address according to preset interval time;

Acquiring and calculating a response difference between response time of the target IPv4 address and response time of the target IPv6 address;

and if the response difference is greater than or equal to a preset difference range, verifying the configuration of the network environment and the service.

In addition, in order to achieve the aim, the application also provides private cloud data center IPv6 upgrading equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program is configured to realize the steps of the private cloud data center IPv6 upgrading method.

In addition, in order to achieve the above object, the present application further proposes a storage medium, which is a computer readable storage medium, on which a computer program is stored, the computer program implementing the steps of the private cloud data center IPv6 upgrading method as described above when being executed by a processor.

The application provides an IPv6 upgrading method of a private cloud data center, which comprises the steps of firstly, upgrading and converting an IPv4 and IPv6 dual protocol stack for a basic network environment of the private cloud data center. By modifying the basic network service, the network infrastructure of the private cloud data center can be ensured to simultaneously support two protocols of IPv4 and IPv 6. The compatibility of network infrastructure can be improved, and good support and guarantee are provided for subsequent service transformation. And secondly, determining the monomer service in the private cloud data center according to the composition and the deployment mode of the service of the private cloud data center. For single service, selecting a double-stack node, and constructing an Nginx proxy on the double-stack node according to a preset transformation sequence. By setting up the Nginx proxy on the dual stack node of the single service, the traffic of IPv4 and IPv6 can be processed simultaneously, and the request can be forwarded to the single 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 upgrades is reduced. In addition, through double-stack transformation, the service can simultaneously support two protocols of IPv4 and IPv6, and compatibility and intercommunication with different network environments are realized.

Drawings

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

In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.

Fig. 1 is a schematic flow chart provided in an embodiment of an IPv6 upgrade method for a private cloud data center according to the present application;

Fig. 2 is a schematic diagram of network communication for modifying a monomer service according to a first embodiment of an IPv6 upgrade method for a private cloud data center of the present application;

Fig. 3 is a schematic flow chart provided by a second embodiment of an IPv6 upgrade method for a private cloud data center according to the present application;

fig. 4 is a schematic detail flow chart provided by a second embodiment of an IPv6 upgrade method of a private cloud data center of the present application;

fig. 5 is a schematic diagram of network communication for modifying a distributed deployment service according to a second embodiment of an IPv6 upgrade method for a private cloud data center of the present application;

Fig. 6 is a schematic flow chart provided in a third embodiment of an IPv6 upgrade method for a private cloud data center according to the present application;

fig. 7 is a schematic diagram of a device structure of a hardware operating environment related to an IPv6 upgrade method of a private cloud data center according to an embodiment of the present application.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the technical solution of the present application and are not intended to limit the present application.

For a better understanding of the technical solution of the present application, the following detailed description will be given with reference to the drawings and the specific embodiments.

The main solution of the embodiment of the application is that the upgrade conversion of IPv4 and IPv6 dual protocol stacks is carried out on the basic network environment of the private cloud data center, the single service is determined according to the composition and the deployment mode of the service of the private cloud data center, the dual stack node is determined in the single service, and the Nginx agent is built on the dual stack node according to the preset reconstruction sequence.

It should be noted that, the execution body of the embodiment may be a computing service device having functions of network communication and program running, such as a tablet computer, a personal computer, a mobile phone, or an electronic device, an apparatus, or the like capable of implementing the above functions. The following describes this embodiment and the following embodiments by taking a private cloud data center IPv6 upgrade apparatus as an example.

Based on this, the embodiment of the application provides a private cloud data center IPv6 upgrading method, and referring to fig. 1, fig. 1 is a schematic flow chart of a first embodiment of the private cloud data center IPv6 upgrading method of the application.

In this embodiment, the private cloud data center IPv6 upgrading method includes steps S100 to S300:

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

It should be noted that, the private cloud data center is a deployment mode based on cloud computing technology, and is a cloud computing environment built and managed by an enterprise or an organization. IPv4 (Internet Protocol version, fourth edition of the internet communication protocol), one of the core protocols in the internet protocol suite (TCP/IP protocol), is used to assign a unique address (i.e., an IPv4 address) to a device on the internet. IPv4 addresses consist of 32-bit binary numbers, typically represented in the form of dot decimal, such as 192.168.1.1.IPv6 (Internet Protocol version, sixth edition of the internet communication protocol), which is a next generation version of IPv4, aims to solve the problem of insufficient IPv4 address space. IPv6 addresses consist of 128-bit binary numbers, providing a huge address space.

In the embodiment, the basic network environment comprises a DNS service, is responsible for domain name resolution and is the basis of network communication. It is necessary to ensure that it can handle both IPv4 and IPv6 domain name resolution requests. DHCP service, responsible for dynamic allocation of IP addresses. In a dual stack environment, DHCP services need to be able to allocate both IPv4 and IPv6 addresses. And the load balancing service can ensure that the traffic is reasonably distributed to a plurality of servers when the network traffic is high. It is necessary to ensure that the load balancing service supports IPv6 traffic. Firewall services, which are responsible for filtering and monitoring network traffic. It is necessary to ensure that it can handle both IPv4 and IPv6 traffic and provide corresponding security policies. Intrusion Detection Systems (IDS) are responsible for monitoring abnormal behavior in network traffic. There is a need to ensure that it can detect potential threats in IPv6 traffic. VPN services-VPN services are essential if remote access to a private cloud data centre is required. It is necessary to ensure that it supports the establishment and maintenance of IPv6 tunnels. Content Delivery Networks (CDNs) if a private cloud data center provides content delivery services, it is necessary to ensure that their CDN supports delivery of IPv6 traffic.

In this embodiment, the existing network architecture is evaluated, and compatibility and scalability of the existing network architecture are analyzed. It is determined which devices and services need to be upgraded or replaced to support IPv6. And (5) according to the evaluation result, making a detailed reconstruction plan. And upgrading or replacing the equipment which does not support IPv6, so as to ensure that the new equipment or the equipment after upgrading has correctly configured the dual stack technology. IPv 6-related protocols and configurations are enabled on a network device. Network services such as DNS, DHCP, load balancing, etc. are configured to support IPv6.

In one possible embodiment, step S100 may include the steps of:

and upgrading the hardware of the network equipment, and configuring the IPv6 address after the upgrading is completed.

And carrying out space allocation and division on the IPv6 address.

The NTP server and DNS server are upgraded to IPv 6-enabled versions.

In this embodiment, it is checked whether a network device (e.g., router, switch, firewall, etc.) supports the dual stack technique. For devices that do not support dual stacks, upgrade or replacement plans are formulated. And (3) formulating a detailed double-stack reconstruction scheme according to the requirement analysis and the equipment compatibility checking result. The solution should include a retrofit step, risk assessment, backup and restore planning, etc. According to the scheme, the equipment which does not support the dual stack is updated or replaced, so that the new equipment or the updated equipment is ensured to have correctly configured the dual stack technology. IPv6 routing protocols (e.g., OSPFv3, BGP4+, etc.) are enabled on the network device. And configuring an IPv6 address pool and subnet division. The IPv6 static routing or dynamic routing protocol is configured. And verifying the configuration in a test environment to ensure that the network equipment can correctly process the IPv4 and IPv6 traffic.

In this embodiment, the switch is upgraded, and a switch supporting dual protocol stacks (IPv 4 and IPv 6) is selected, so that it is ensured that the switch can process both IPv4 and IPv6 packets. The operating system and firmware of the switch are upgraded to ensure that it supports the latest dual stack functionality. The IPv6 address and related routing of the switch are configured to ensure that IPv6 traffic can be properly transported in the network.

In this embodiment, the IPv6 address is divided into different address segments according to the network topology and service requirements. The purpose and scene of each address segment, such as intranet address, extranet address, special purpose address, etc., are determined. And distributing IPv6 addresses to each network device and service according to the address segment division result. And establishing an IP address management system, and recording and managing the allocation and use condition of the IPv6 address. And formulating an IPv6 address management strategy, including the flows of address application, allocation, recovery, change and the like. And (3) auditing and cleaning the IPv6 address regularly to ensure effective utilization of address resources.

In this embodiment, an IPv6 address resolution function is enabled on a DNS (Domain name system) server. And configuring IPv6 related DNS records such as A6, AAAA records and the like. Ensuring that DNS servers can handle both IPv4 and IPv6 domain name resolution requests. And verifying the configuration of the DNS server in a test environment to ensure that the DNS server can correctly analyze the IPv4 and IPv6 addresses.

In this embodiment, a firewall supporting IPv6 is deployed at the network boundary, and firewall rules are configured to allow or reject specific ports and protocols for IPv6 traffic. An intrusion detection system is deployed, an intrusion detection system supporting IPv6 is deployed at a network boundary, and the intrusion detection system is configured to monitor abnormal behavior in IPv6 traffic. And verifying the configuration of the firewall and the intrusion detection system in a test environment to ensure that the security device can correctly process the IPv4 and IPv6 traffic and protect the network from security threats.

In this embodiment, a dual stack is configured on an NTP (Network Time Protocol ) server, so that it can monitor both IPv4 and IPv6 addresses. The IPv6 address and port are specified in the configuration file of the NTP server, and the NTP daemon is ensured to be capable of starting and monitoring the corresponding address and port correctly. The configuration of the NTP client is updated so that it can communicate with the NTP server using the IPv6 address. This typically involves modifying the client's profile, specifying the IPv6 address of the NTP server, and configuring a corresponding synchronization policy. The image station software is upgraded to support IPv6. Updating the software version of the mirror station and configuring corresponding IPv6 support options. Ensuring that the contents of the mirrored station can be properly accessed by the IPv6 client.

And step 200, determining a monomer service according to the composition and the deployment mode of the service of the private cloud data center.

And step S300, determining a dual-stack node in the single service, and building an Nginx agent on the dual-stack node according to a preset transformation sequence.

It should be noted that, the services may be classified into distributed deployment services and individual services according to service deployment and composition. The single service architecture mode is generally suitable for smaller systems or applications, and is characterized by all business logic being concentrated in a single service. The architecture mode has the advantages of simple deployment and easy management, but has the disadvantages that as the system expands, codes become complex and difficult to maintain, and the expansibility and fault tolerance of the system are limited. The distributed service architecture model splits business logic into multiple independent services, each of which can be deployed independently, extended independently, and managed independently. The advantage of this architecture mode 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.

In addition, nmginx is a high-performance HTTP and reverse proxy server that can distribute requests to multiple back-end servers for load balancing and failover.

In this embodiment, it is determined whether the deployment manner of each service is a single deployment or a distributed deployment. And further determining the transformation mode of each service according to the deployment mode of the service. And carrying out double-stack reconstruction on each single service according to a preset reconstruction sequence. The dual stack adaptation means that the service will support both IPv4 and IPv6 protocols in order to maintain compatibility with existing IPv4 networks during migration and to gradually transition to IPv6 networks. The modification mode of the monomer service is to build an Nginx proxy. And installing Nginx software on the server, and configuring agent rules, load balancing strategies and the like of the Nginx according to requirements. The nmginx service is started to begin listening and processing requests.

In one possible embodiment, step S300 may include:

And selecting a second dual-stack execution node from the single service, and installing an Nginx agent on the second dual-stack execution node.

It should be noted that, the nginx proxy service plays an important role in the internet request, and realizes the communication between the client and the server.

In this embodiment, in the private cloud data center, the monomer service includes a cloud management platform, a virtualization service such as KVM (Kernel-based Virtual Machine), xen, etc., an identity authentication and authorization service such as LDAP (Lightweight Directory Access Protocol), kerberos, etc., and a log and monitoring service such as ELK Stack (ELASTICSEARCH, LOGSTASH, KIBANA), promethaus, etc.

In this embodiment, as shown in fig. 2, for the single service, the manner of setting up the nginx proxy to realize 6-to-4 is adopted to modify. The nginx is installed and configured on the second dual stack node so that it can act as a reverse proxy server. And configuring the proxy rule of the nginx, converting the IPv6 request into the IPv4 request, and forwarding the IPv4 request to the original monomer service. Necessary configuration adjustments are made to the original monomer service to ensure that it can communicate normally with the nginx proxy server.

In this embodiment, one dual stack node is selected as the second dual stack node in the single service, and the nginnx agent is downloaded and installed on the second dual stack execution node. And configuring an instruction for monitoring the IPv4 address and the IPv6 address in the configuration file of the Nginx. A server block or a location block is created for the IPv6 request to be converted, and the proxy_pass instruction is used for forwarding the request to the IPv4 back-end server. Before the start of the ngginx, the command provided by the ngginx (such as Nginx-t) is used to check if the syntax of the configuration file is correct.

In this embodiment, the conversion tool of ng in x is used to realize the address conversion from IPv6 to IPv4, so as to allow the IPv6 client to access the IPv4 resource. Because the monomer service itself has a very complex calling condition, the problems that the data consistency is difficult to guarantee and the transformation period is long are avoided by the steps.

In the second embodiment of the present application, the same or similar content as in the first embodiment of the present application may be referred to the above description, and will not be repeated. On this basis, referring to fig. 3, step S200 may include steps a100 to a200:

Step A100, determining distributed deployment services in the private cloud data center;

and step A200, adding a server as a first dual-stack execution node to the distributed deployment service according to the preset reconstruction sequence.

In this embodiment, when the service adopts distributed deployment, IPv6 transformation is performed by adopting a node capacity expansion manner. According to the system requirements, preparing a new server or virtual machine as a new node, and carrying out necessary configuration on the new node, including installing an operating system, deploying an application program and the like. After configuration is completed, the new node is added to the distributed system so that the new node can work cooperatively with other nodes. And finally, verifying and testing to ensure that the system can work normally and meet the system requirements.

Referring to fig. 4, in one possible embodiment, step a200 may include steps a210 to a240:

step A210, distributing IPv4 addresses and IPv6 addresses to the first dual stack execution node;

Step A220, establishing 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;

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 types and requirements of the tasks. The executing node is responsible for actually executing the tasks received from the control node.

In this embodiment, in the private cloud data center, the distributed deployment service includes a cloud platform Cloud Automation Engine (CAE), a distributed storage service, such as a distributed file system (e.g., hadoop HDFS), a distributed object storage (e.g., ceph), and the like. Distributed database services, such as a distributed relational database (e.g., cockroachDB), a distributed NoSQL database (e.g., CASSANDRA, MONGODB), and the like. Distributed caching services such as Redis, memcached, etc. Distributed computing services such as APACHE SPARK, hadoop MapReduce, and the like.

In this embodiment, as shown in fig. 5, for some services adopting distributed deployment, a node capacity expansion manner is adopted, and a dual stack node is added, so as to implement management of the IPv6 service. First, the specification and deployment position of the first dual stack node are determined according to the network topology, the data center layout and the service requirements. When determining the specification, considering the calculation capacity (such as CPU, memory), storage capacity, network bandwidth and other factors of the node, selecting the node specification capable of meeting the current and future service demands in a period of time. In determining the deployment location, it is determined based on network topology, data center layout, and traffic requirements, and takes into account the impact of the physical location of the nodes on latency, bandwidth, and failure recovery. And secondly, adding the first dual-stack execution node into the distributed deployment service cluster, and modifying the configuration file of the cluster to contain the information of the new node.

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

Step A230, a configuration file of the distributed deployment service is obtained, and information of the first dual-stack execution node is added in the configuration file;

Step a240, adding the first dual stack execution node to the distributed deployment service, and updating the state of the distributed deployment service.

In this embodiment, the configuration file of the cluster is found according to the type of the cluster and the technology stack used. The configuration file may be one or more, depending on the architecture of the cluster and the management tool used. Information of the new node is added in the configuration file, including the IP address (IPv 4 and IPv 6), host name, role (such as master node, slave node, etc.), etc. of the node, and the modified configuration file is saved. Ensuring that the configuration of the new node remains consistent with the configuration of the existing node to avoid configuration conflicts. If the cluster uses a distributed configuration management tool (e.g., consul, etcd, etc.), the configuration information for the new node is distributed to all nodes. The state of the cluster is updated according to the cluster management tool used, enabling the cluster to identify newly added nodes.

In this embodiment, ping, telnet, or other network tools may be used to verify whether IPv4 and IPv6 network communications between the new node and the existing node are clear. The log file of the cluster is checked to ensure that there are no errors or warning messages associated with the new node. If the cluster is configured with a load balancer, it is ensured that the new node has been added correctly to the back-end node list of the load balancer. A failover test is performed to verify if the new node is able to take over and handle traffic in the event of a failure.

Optionally, after adding the new dual stack execution node, the load balancing policy is adjusted to balance the IPv4 and IPv6 traffic. IPv4 and IPv6 traffic data for existing services is collected using network traffic analysis tools (e.g., prometheus, grafana, etc.). And recording the flow changes of different time periods (such as workdays, weekends and holidays) and the flow distribution under different service scenes, and calculating the ratio of IPv4 to IPv6 flows. And determining weight distribution on different nodes according to the ratio of the IPv4 traffic to the IPv6 traffic. If the IPv6 traffic is less, the weight can be properly reduced so as to reduce the resource waste. And according to the service requirements and the traffic characteristics, using a polling strategy, a minimum connection strategy, a source address strategy and the like to ensure the balanced distribution of traffic.

In this embodiment, according to the scale and service requirement of the private cloud data center, a suitable load balancer (such as a hardware load balancer, a software load balancer, etc.) is selected to ensure that the load balancer supports IPv6, and has characteristics of high performance, high availability, etc. And modifying the corresponding configuration file according to the type of the load equalizer, and adding support for the IPv6 address. The virtual IP address (VIP) of the load balancer is configured to ensure that the VIP supports both IPv4 and IPv6. After configuration is completed, testing of the load balancer is performed to ensure that it can correctly identify and distribute IPv6 traffic. Test content includes, but is not limited to, distribution of IPv6 traffic, failover, health checking, and the like.

Alternatively, traffic changes may be monitored and load balancing policies dynamically adjusted based on real-time traffic data. And selecting a network flow monitoring tool such as Prometheus, grafana, zabbix and the like, and acquiring real-time flow data analysis and visual display. And monitoring key network traffic indexes such as total traffic, IPv4/IPv6 traffic proportion, traffic load of each node and the like. And (5) utilizing automation tools such as scripts, APIs and the like to realize automatic adjustment of the load balancing strategy. And automatically adjusting configuration parameters of the load equalizer, such as weights, distribution rules and the like, according to the monitoring data. Illustratively, when the traffic load of a certain node reaches a preset maximum threshold, the weight of the node is increased or a new node is added to share the traffic, and when the IPv6 traffic is increased, the strategy is adjusted to preferentially process the IPv6 traffic.

Optionally, the source address, destination address, access time, etc. of the user access may also be analyzed to identify the primary access pattern and traffic hot spot. According to the access mode, determining whether traffic optimization is required for a specific user group or service scene.

In the third embodiment of the present application, the same or similar content as the first embodiment of the present application can be referred to the above description, and the description thereof will not be repeated. Referring to fig. 6, before step S200, steps B100 to B200 are further included:

step B100, determining the calling relation of each service of the private cloud data center according to the service framework diagram;

And step B200, sequencing the services according to the calling relation to obtain the transformation sequence.

In this embodiment, the calling relationship between each service in the private cloud data center is carded, including identifying the dependency relationship, the data flow direction, the communication protocol, and the like between the services. Through this process, a clear service invocation graph is constructed that demonstrates interactions and connections between services. And further generating a transformation path diagram according to the service call relation diagram. The routing diagram specifies a specific order of service modification to determine which services require priority IPv6 modification to ensure minimal impact on traffic. For example, database purchases rely on cloud hosts, on internal mirror stations, and the like.

In this embodiment, first, all services in the private cloud data center are acquired, where the services may include a virtualization service, a distributed storage service, a distributed database service, an identity authentication and authorization service, a log and monitoring service, a containerization service, a backup and restore service, an API gateway service, a message queue service, and a Web service. Second, the dependencies between these services are analyzed. This includes both strong and weak dependencies. Strong dependencies refer to one service having to rely on the normal operation of another service to provide the service, while weak dependencies refer to one service may still provide the service when another service is not available (but may be functionally limited). Recording the dependency relationship obtained by analysis.

In this example, the direction of data flow between the various services may also be analyzed. This includes the data flow from which service to which service, as well as the specific path of the data flow. Recording the data flow direction obtained by analysis. The communication protocol used between the various services may also be identified. These protocols may include HTTP, HTTPS, TCP, UDP, RESTful APIs, etc. And recording the communication protocols obtained by analysis, and determining whether IPv6 reconstruction is needed for the protocols.

In this embodiment, a service call relationship diagram is drawn in a drawing tool according to a dependency relationship, a data flow direction, and a communication protocol. The graph should contain icons of the various services, arrows of the dependency, arrows of the data flow, and labels of the communication protocol. Different colors or shapes may be used to distinguish between different types of services, and arrows and labels are used to explicitly indicate dependencies and data flow directions.

In this embodiment, the dependency relationship may also be determined through a service interface document, and the service in the private cloud data center will generally have a detailed interface document, which describes the input and output of the service, the calling mode, and the interaction with other services. By referring to these documents, the call relationship and dependency between services can be known. The call chains between services can also be identified by analysis of the service codes. This typically involves parsing of the parts of the code for method calls, network communications, etc. Traffic analysis tools (e.g., WIRESHARK, TCPDUMP, etc.) may also be deployed to capture traffic between services at key nodes of the network. By analyzing these traffic data, call relationships and communication patterns between services can be identified. Call relationships between services can also be automatically discovered and a visual service graph generated according to tools (e.g., APPDYNAMICS, DYNATRACE, etc.) specific to the service mapping.

In this embodiment, a log collection system (e.g., ELK Stack, splunk, etc.) is configured to capture a log of services, parse the log using a log analysis tool (e.g., logstash, kibana, etc.), and extract call information between services. Service dependency analysis tools, such as APACHE SKYWALKING, prometheus, etc., are selected that are suitable for private cloud data centers and configured to monitor call relationships between services. The output of the tool is analyzed periodically to identify call chains and dependencies between services. And establishing a communication channel with a service development team to know calling relations and business logic between services. And verifying whether the call relations collected through the log and the tool are consistent with the description of the development team.

In this embodiment, the collected call relationship data is organized into a structured format, such as a table or database. Each service is assigned a unique identifier and its pre-dependencies and post-dependencies are recorded. The call between services is simulated using an automated test tool or script to verify the accuracy of the call relationship. And communicate with the development team to solve the problem of inconsistent or missing any possible calling relationship. The call relationship data is updated periodically as services are updated and changed. And ensuring that the call relationship data always reflects the latest call relationship among services in the private cloud data center.

In the fourth embodiment of the present application, the same or similar content as the first embodiment of the present application can be referred to the above description, and the description thereof will not be repeated. On this basis, step S300 may further include the following steps:

setting a test source, a target IPv4 address and a target IPv6 address;

In this embodiment, test source and target addresses are set, and the target addresses respectively select IPv4 and IPv6 addresses. Determining the test times and interval time, respectively sending data packets to the IPv4 target address and the IPv6 target address by using a ping command, recording response time, and taking an average value as final response time to reduce accidental errors. The difference between these two average response times is calculated. If the response difference exceeds the preset difference range, further verification steps, such as checking network configuration, routing rules, DNS analysis and the like, are triggered, so that the problems that the configuration of the IPv6 is incorrect or conflicts with the configuration of the IPv4 are avoided.

In this embodiment, IPv4 and IPv6 routing tables on the network device may be checked to ensure that the routing configuration is correct and there is no conflict to verify whether the network device (e.g., router, switch, etc.) has been properly configured to support dual stacks. It is also possible to verify whether each service has been properly configured to support dual stack and to handle both IPv4 and IPv6 traffic. Parameters such as bandwidth, queue management, etc. of the network device may also be adjusted to optimize network performance.

The application provides private cloud data center IPv6 upgrading equipment which comprises at least one processor and a memory in communication connection with 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 upgrading method in the first embodiment.

Referring now to fig. 7, a schematic diagram of a private cloud data center IPv6 upgrade apparatus suitable for use in implementing embodiments of the present application is shown. Private cloud data center IPv6 upgrade apparatuses in embodiments of the present application may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal DIGITAL ASSISTANT: personal digital assistants), PADs (Portable android device: tablet computers), PMPs (Portable MEDIA PLAYER: portable multimedia players), vehicle terminals (e.g., car navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The private cloud data center IPv6 upgrade apparatus shown in fig. 7 is only one example, and should not impose any limitation on the functionality and scope of use of the embodiment of the present application.

As shown in fig. 7, the private cloud data center IPv6 upgrade apparatus may include a processing device 1001 (e.g., a central processor, a graphics processor, etc.), which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access Memory (RAM: random Access Memory) 1004. In the RAM1004, various programs and data required for the operation of the private cloud data center IPv6 upgrade apparatus are also stored. The processing device 1001, the ROM1002, and the RAM1004 are connected to each other by a bus 1005. An input/output (I/O) interface 1006 is also connected to the bus. In general, a system including an input device 1007 such as a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc., an output device 1008 including a Liquid crystal display (LCD: liquid CRYSTAL DISPLAY), a speaker, a vibrator, etc., a storage device 1003 including a magnetic tape, a hard disk, etc., and a communication device 1009 may be connected to the I/O interface 1006. Communication means 1009 may allow the private cloud data center IPv6 upgrade device to communicate wirelessly or by wire with other devices to exchange data. While private cloud data center IPv6 upgrade equipment with various systems is shown in the figures, it should be understood that not all of the illustrated systems are required to be implemented or provided. More or fewer systems may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the ROM 1002. The above-described functions defined in the method of the disclosed embodiment of the application are performed when the computer program is executed by the processing device 1001.

The private cloud data center IPv6 upgrading device provided by the application can solve the problem of how to carry out IPv6 transformation on the private cloud data center by adopting the private cloud data center IPv6 upgrading method in the embodiment. Technical problems of (2). Compared with the prior art, the beneficial effects of the private cloud data center IPv6 upgrading device provided by the application are the same as those of the private cloud data center IPv6 upgrading method provided by the embodiment, and other technical features of the private cloud data center IPv6 upgrading device are the same as those disclosed by the method of the previous embodiment, so that the description is omitted.

It is to be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the description of the above embodiments, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

The present application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon for performing the private cloud data center IPv6 upgrade method in the above-described embodiments.

The computer readable storage medium provided by the present application may be, for example, a U disk, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or a combination of any of the foregoing. More specific examples of a computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (RAM: random Access Memory), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (EPROM: erasable Programmable Read Only Memory or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this embodiment, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to electrical wiring, fiber optic cable, RF (Radio Frequency) and the like, or any suitable combination of the foregoing.

The computer readable storage medium can be contained in the private cloud data center IPv6 upgrading device or can exist alone and not be assembled into the private cloud data center IPv6 upgrading device.

The computer readable storage medium is loaded with one or more programs, when the one or more programs are executed by the private cloud data center IPv6 upgrading device, the private cloud data center IPv6 upgrading device is enabled to conduct upgrading conversion of IPv4 and IPv6 dual protocol stacks on a basic network environment of the private cloud data center, single service is determined according to the composition and the deployment mode of the service of the private cloud data center, dual stack nodes are determined in the single service, and an Nginx agent is built on the dual stack nodes according to a preset transformation sequence.

Computer program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN: local Area Network) or a wide area network (WAN: wide Area Network), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments of the present application may be implemented in software or in hardware. Wherein the name of the module does not constitute a limitation of the unit itself in some cases.

The readable storage medium provided by the application is a computer readable storage medium, and the computer readable storage medium stores computer readable program instructions (namely computer programs) for executing the private cloud data center IPv6 upgrading method, so that the problem of how to carry out IPv6 transformation on the private cloud data center can be solved. Technical problems of (2). Compared with the prior art, the beneficial effects of the computer readable storage medium provided by the application are the same as those of the private cloud data center IPv6 upgrading method provided by the embodiment, and the description thereof is omitted herein.

The foregoing description is only a partial embodiment of the present application, and is not intended to limit the scope of the present application, and all the equivalent structural changes made by the description and the accompanying drawings under the technical concept of the present application, or the direct/indirect application in other related technical fields are included in the scope of the present application.

Claims

1. The IPv6 upgrading method of the private cloud data center is characterized by comprising the following steps of:

2. The method for upgrading the IPv6 of the private cloud data center according to claim 1, wherein the step of determining the single service according to the service deployment method of the service of the private cloud data center comprises:

Determining distributed deployment services in the private cloud data center;

3. The private cloud data center IPv6 upgrade method of claim 2, wherein for the distributed deployment service, adding a server as a first dual stack execution node comprises:

4. The private cloud data center IPv6 upgrade method of claim 1, wherein the step of building the nginnx proxy on the dual stack node according to a preset modification order comprises:

5. The private cloud data center IPv6 upgrade method according to claim 1, wherein after the step of performing upgrade conversion of the IPv4 and IPv6 dual protocol stack for the base network environment of the private cloud data center, it includes:

6. The method for upgrading the IPv6 of the private cloud data center according to claim 1, wherein the step of upgrading and converting the IPv4 and IPv6 dual protocol stack for the base network environment of the private cloud data center includes:

And carrying out space allocation and division on the IPv6 address.

7. The private cloud data center IPv6 upgrade method of claim 6, wherein the step of allocating and partitioning the space for the IPv6 address is followed by:

Upgrading the NTP server and the DNS server to a version supporting IPv 6;

8. The private cloud data center IPv6 upgrade method of claim 1, wherein after the step of determining a dual stack node in the single service and building an Nginx proxy on the dual stack node in a preset modification order, the method comprises:

setting a test source, a target IPv4 address and a target IPv6 address;

9. A private cloud data center IPv6 upgrade apparatus, characterized in that the apparatus comprises a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program being 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, which computer program, when being executed by a processor, implements the steps of the private cloud data center IPv6 upgrade method according to any one of claims 1 to 8.