Distributed resource area deployment method and system based on data center
By combining computing, network and control data centers, a target data center is formed, and the resources of the sub-service system are deployed to different small data centers respectively, the overall business unavailability problem caused by sub-service system exceptions in traditional data center architecture is solved, and a highly reliable and highly secure distributed resource area deployment is achieved.
Patent Information
- Application Number
- CN202411893734.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-20
- Publication Date
- 2025-04-15
- Estimated Expiration
- 2044-12-20
AI Technical Summary
The existing data center architecture mainly adopts a single computer room deployment method, which causes abnormalities in the data processing process of a single sub-business system, which may cause the entire business system to be unavailable.
The three small data center combinations focusing on implementing different functions are adopted, forming a target data center that can replace the traditional data center architecture, and deploying the infrastructure resources of different sub-business systems to different small data centers respectively.
It realizes secure isolation between different sub-service systems and small data centers, ensuring the high reliability and high security of the target business system.
Smart Images

Figure CN119830339A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information technology, and in particular to a distributed resource area deployment method and system based on a data center. Background Art
[0002] In the existing technology, in daily operations, enterprises usually deploy the infrastructure resources corresponding to the business system on a data center, support the normal operation of the business system through the data center, provide the business system with infrastructure resources such as computing resources, network resources and storage resources, and provide the business system with various Internet services.
[0003] At present, the existing traditional data center architecture mainly adopts a single computer room deployment method. In the single computer room deployment method, the infrastructure resources corresponding to all sub-business systems in the business system will be centrally deployed on the same server in the data center, so that the computing tasks and data storage corresponding to all sub-business systems are completed on this server. As a result, if the data processing process corresponding to a single sub-business system is abnormal, the entire business system may be unavailable due to a data center failure. Summary of the invention
[0004] In view of this, the present application provides a distributed resource area deployment method and system based on a data center, with distributed high availability as the goal, using three small data centers that focus on realizing different functions, namely, a computing data center, a network data center, and a control data center, to combine into a target data center that can replace the traditional data center architecture, and deploy the infrastructure resources corresponding to different sub-business systems in different of the above-mentioned small data centers, which is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.
[0005] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings.
[0006] In a first aspect, an embodiment of the present application provides a distributed resource area deployment method based on a data center, which is applied to a target data center, wherein the target data center includes: a computing data center, a network data center, and a control data center; wherein the computing data center and the control data center implement network communication within the target data center through the network data center, and the distributed resource area deployment method includes:
[0007] According to the business requirements corresponding to different sub-business systems, multiple sub-business systems constituting the target business system are grouped to obtain multiple sub-business system combinations; wherein each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements;
[0008] For each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the computing data center;
[0009] If the business requirements corresponding to the sub-business system combination match the control-type data center, the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the control-type data center.
[0010] In a second aspect, an embodiment of the present application provides a distributed resource area deployment system based on a data center, which is applied to a target data center, wherein the target data center includes: a computing data center, a network data center, and a control data center; wherein the computing data center and the control data center implement network communication within the target data center through the network data center, and the distributed resource area deployment system includes:
[0011] A grouping module, used to group multiple sub-business systems constituting a target business system according to the business requirements corresponding to different sub-business systems, to obtain multiple sub-business system combinations; wherein each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements;
[0012] A first deployment module is used for deploying the infrastructure resources corresponding to the sub-business systems in each of the sub-business system combinations on the computing data center if the business requirements corresponding to the sub-business system combination match the computing data center;
[0013] The second deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control-type data center if the business requirements corresponding to the sub-business system combination match the control-type data center.
[0014] The technical solution provided by the embodiments of the present application may have the following beneficial effects:
[0015] The embodiments of the present application provide a distributed resource area deployment method and system based on a data center, with distributed high availability as the goal, using three small data centers that focus on achieving different functions, namely, a computing data center, a network data center, and a control data center, to combine into a target data center that can replace the traditional data center architecture, and deploy the infrastructure resources corresponding to different sub-business systems in different of the above-mentioned small data centers, which is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 A schematic diagram of the structure of a target data center provided in an embodiment of the present application is shown;
[0018] Figure 2 A schematic diagram of a process flow of a distributed resource area deployment method based on a data center provided in an embodiment of the present application is shown;
[0019] Figure 3 A flow chart of an Internet line wiring method applicable to each type of data center standardized distributed resource area provided in an embodiment of the present application is shown;
[0020] Figure 4 A structural diagram of a distributed resource zone deployment system based on a data center provided in an embodiment of the present application is shown. DETAILED DESCRIPTION
[0021] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.
[0022] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.
[0023] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.
[0024] Here, the distributed resource area deployment method provided in the embodiment of the present application can be applied to the target data center. Figure 1 A schematic diagram of the structure of a target data center provided in an embodiment of the present application is shown. Figure 1 As shown, the target data center includes: a computing data center 101, a network data center 102 and a control data center 103; wherein, with distributed high availability as the goal, the minimized infrastructure resource deployment unit in the data center is explored to form a standardized distributed resource area of the data center, and the above-mentioned standardized distributed resource area of the data center can be divided into three categories according to function: computing (i.e., computing data center 101), network (i.e., network data center 102), and control (i.e., control data center 103); that is, in the embodiment of the present application, with distributed high availability as the goal, the three small data centers focusing on realizing different functions, namely, the computing data center 101, the network data center 102 and the control data center 103, are combined into a target data center that can replace the traditional data center architecture.
[0025] like Figure 1 As shown, inside the target data center, the computing data center 101 and the control data center 103 realize network communication inside the target data center through the network data center 102; among them, for the three types of data center standardized distributed resource areas focusing on different functions, namely the computing data center 101, the network data center 102 and the control data center 103, common hardware devices in data centers such as servers, network equipment, and security equipment can be deployed in a standard manner in the standardized distributed resource areas of each type of data center. However, based on the different functional emphases, the specific number of the same type of functional equipment deployed in different types of data center standardized distributed resource areas may be different.
[0026] Specifically, since the computing data center 101 mainly carries the business system operation functions and needs to perform more computing tasks (i.e., focuses on computing functions), as an optional embodiment, in the target data center, the number of computing function devices (such as servers) configured in the computing data center 101 is greater than the number of computing function devices configured in the network data center 102 and the control data center 103 respectively (equivalent to the computing data center 101 having the largest number of computing function devices configured in the target data center).
[0027] Specifically, since the network data center 102 mainly carries the network core and security management functions (i.e., focuses on network functions), as an optional embodiment, in the target data center, the number of network devices (such as firewalls, switches, routers, etc.) configured in the network data center 102 is greater than the number of network devices configured in the computing data center 101 and the control data center 103 respectively (equivalent to the network data center 102 having the largest number of network devices configured in the target data center).
[0028] Specifically, since the control data center 103 mainly carries the centralized control function and strengthens security control (i.e., focuses on control functions), as an optional embodiment, in the target data center, the number of centralized control function devices (such as network monitoring devices, access control devices, etc.) configured in the control data center 103 is greater than the number of centralized control function devices configured in the computing data center 101 and the network data center 102 respectively.
[0029] Specifically, in terms of software resource deployment, host security, monitoring, and operating system standard software can be deployed in the standardized distributed resource area of each type of data center (i.e., computing data center 101, network data center 102, and control data center 103). Middleware, containers, cloud platforms, and storage and computing software can also be deployed on demand to achieve integrated cloud management of network, computing, storage and other resources within the standardized distributed resource area of each type of data center, and support distributed application deployment.
[0030] It should be noted that in terms of computer room deployment, if standardized deployment is mainly adopted, the same number of cabinet positions can be allocated to each type of data center standardized distributed resource area in the target data center (i.e., computing data center 101, network data center 102, and control data center 103) based on the distribution of cabinet positions in the computer room (for example, 4 columns of cabinet positions can be allocated to each type of data center standardized distributed resource area to form a standard data center standardized distributed resource area, and every 3 cabinet positions can be used as a network access unit). In addition, if standardized deployment is difficult to achieve in the actual computer room deployment, different numbers of cabinet positions can also be allocated to different types of data center standardized distributed resource areas as needed.
[0031] It should be noted that, taking three cabinet positions as a network access unit as an example, the three cabinet positions can share one or more access switches, and aggregation layer switches can also be deployed on the access layer. Under normal circumstances, a group of access switches can be deployed corresponding to each type of data center standardized distributed resource area (i.e., computing data center 101, network data center 102, and control data center 103), and the intranet and extranet can also be distinguished based on the specific functions of the network access unit.
[0032] To facilitate understanding of the embodiments of the present application, Figure 1 Taking the target data center shown as an example, a distributed resource area deployment method based on a data center provided in an embodiment of the present application is introduced in detail.
[0033] Reference Figure 2 As shown, Figure 2 The present invention provides a schematic diagram of a distributed resource area deployment method based on a data center, wherein the distributed resource area deployment method can be applied to Figure 1 In the target data center shown, the distributed resource area deployment method includes steps S201-S203; specifically:
[0034] S201 , grouping a plurality of sub-business systems constituting a target business system according to business requirements corresponding to different sub-business systems to obtain a plurality of sub-business system combinations.
[0035] Here, the target business system represents a complete business system composed of multiple sub-business systems that can cover the entire business processing flow. The types and numbers of sub-business systems corresponding to target business systems in different fields may be different, and the embodiments of this application do not impose any limitations on this.
[0036] For example, taking the target business system in the financial field as an example, the sub-business systems that make up the target business system may include but are not limited to: asset management system, insurance management system, financial settlement system, customer relationship management system, risk monitoring system, automated operation and maintenance system, security management system, etc.
[0037] Specifically, when executing step S201, the similarities between the business requirements corresponding to different sub-business systems can be calculated separately, and one or more sub-business systems whose similarity calculation results are less than or equal to the preset similarity threshold can be divided into a group of sub-business system combinations, so that each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements (that is, the similarity calculation results are less than or equal to the preset similarity threshold).
[0038] S202: For each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the computing data center.
[0039] Here, since each sub-business system combination is composed of one or more sub-business systems with similar business requirements, the business requirements corresponding to each sub-business system combination can be determined based on the business requirements corresponding to the sub-business systems that constitute each sub-business system combination (equivalent to the business requirements corresponding to a sub-business system combination being able to cover the business requirements of each sub-business system that constitutes the sub-business system combination).
[0040] Specifically, for each sub-business system combination, when the business demand corresponding to the sub-business system combination involves massive data storage or data computing tasks, it can be determined that the business demand corresponding to the sub-business system combination matches the computing data center, and the infrastructure resources corresponding to the sub-business system in the sub-business system combination (including but not limited to: computing resources, network resources, storage resources and other infrastructure resources) are deployed on the computing data center (such as Figure 1 As shown, a communication connection is established between the sub-business system and the computing data center 101 to ensure that data transmission and communication can be carried out between the sub-business system and the computing data center 101).
[0041] S203: If the business requirements corresponding to the sub-business system combination match the control-type data center, the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the control-type data center.
[0042] Specifically, for each sub-business system combination, when the business requirements corresponding to the sub-business system combination involve centralized control tasks of various management permissions (such as access permissions, monitoring management permissions, identity authentication permissions, etc.), it can be determined that the business requirements corresponding to the sub-business system combination match the control-type data center, and the infrastructure resources corresponding to the sub-business systems in the sub-business system combination (including but not limited to: computing resources, network resources, storage resources and other infrastructure resources) are deployed on the control-type data center (such as Figure 1 As shown, a communication connection is established between the sub-business system and the control-type data center 103 to ensure that data transmission and communication can be carried out between the sub-business system and the control-type data center 103).
[0043] It should be noted that since the network data center 102 is mainly used to carry functions such as network core switching, wide area network access, Internet access, external access, and border security management and control, in the embodiment of the present application, the network data center 102 is used as an isolation zone between the external network and the internal network of the target data center. The computing data center 101 and the control data center 103 realize network communication within the target data center through the network data center 102, so as to improve the data security performance of the target data center. In addition, according to the different functions focused on by the computing data center 101 and the control data center 103, the infrastructure resources corresponding to the sub-business systems with different business needs are deployed separately to different small data centers (i.e., the computing data center 101 or the control data center 103) that focus on functions and business needs. This is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.
[0044] The following is a detailed description of the network security architecture design for the above target data center:
[0045] 1. Establish a full network interconnection architecture for the target data center, specifically:
[0046] In an embodiment of the present application, in order to achieve full Internetization of the target data center and retain only necessary external connections, a communication connection between the network-based data center and external third-party devices can be established through a hybrid cloud dedicated line; wherein, the hybrid cloud dedicated line is a dedicated network connection method used to connect the enterprise's local data center (i.e., the target data center) with the above-mentioned external third-party devices, providing a high-speed, low-latency, and secure exclusive channel.
[0047] Here, the above-mentioned external third-party devices include at least: the client of the target business system (equivalent to the terminal device of any sub-business system that may be used in the business scenario of each sub-business system in the target business system) and the terminal device corresponding to the third-party cloud service provider of the target data center.
[0048] Specifically, if the client of the above-mentioned target business system belongs to the terminal equipment in special intranet business scenarios such as provincial and municipal external connections and intranet interconnection business scenarios between provinces and cities, it can access the hybrid cloud dedicated line between the network-based data center and external third-party equipment based on the Internet VPN or SD-WAN.
[0049] Specifically, if the above-mentioned external third-party equipment belongs to the terminal equipment corresponding to the third-party cloud service provider of the target data center or the headquarters cooperation agency, a hybrid cloud dedicated line between the external dedicated line access network data center and the external third-party equipment can be used.
[0050] 2. Establish a multi-data center ring network architecture for the target data center, specifically:
[0051] In the embodiment of the present application, based on the design concept of dual-network dual-plane, multiple operators can be introduced to build a dual-plane backbone network to avoid the unavailability of cross-center services due to the failure of a single operator.
[0052] Specifically, when the target data center belongs to a data center in the same city, within the target data center, the computing data center, the network data center and the control data center can be interconnected by bare fiber wavelength division multiplexing; wherein, one target data center can be deployed in the same city, or multiple target data centers can be deployed. The specific number of target data centers deployed in the same city is not limited in any way by the embodiments of the present application.
[0053] Specifically, in addition to deployment in the same city, in order to improve the regional disaster recovery capability of the target data center, multiple target data centers can also be deployed across regions (for example, one target data center is deployed in city A and one target data center is deployed in city B) so as to use geographical separation to ensure the target data center's ability to resist catastrophic events; among them, as an optional embodiment, for any two target data centers deployed across regions, the network data centers contained in each of the two target data centers can be interconnected by a point-to-point dedicated line (equivalent to establishing a point-to-point dedicated line between two network data centers deployed across regions).
[0054] Here, in addition to the architectural design at the hardware deployment level mentioned above, when establishing a multi-data center ring network architecture for the target data center, cross-center traffic orchestration can also be achieved through a software-defined backbone network to ensure business priority and cross-center traffic load balancing.
[0055] It should be noted that the backbone network is dual-plane and has multiple operator redundancy. In the prior art, traffic balance is usually achieved by manually configuring complex commands. However, this manual configuration method, on the one hand, makes maintenance difficult, and on the other hand, it cannot be dynamically adjusted, resulting in lack of flexibility.
[0056] Based on this, in an embodiment of the present application, by introducing the technology of software-defined backbone network, service channels, routing strategies, and automatic delivery strategies can be configured on the controller. The service direction can also be automatically adjusted according to the load conditions of the line to achieve load balancing (which can be understood as dedicated lines between different operators, which achieve load adjustment through automated means).
[0057] 3. For each type of data center standardized distributed resource area in the target data center (i.e., computing data center, network data center, and control data center), independent Internet exits are deployed on demand in each type of data center standardized distributed resource area, and high cohesion of the entire link of business scenarios is achieved within each type of data center standardized distributed resource area (i.e., ensuring that each part of the business process completes only one clearly defined task, thereby improving the readability, reusability, maintainability, and changability of the entire system or application), and low coupling between scenarios. Specifically:
[0058] In the embodiment of the present application, independent Internet exits can be deployed on the computing data center, the network data center, and the control data center, respectively, and each of the deployed Internet exits can be connected to the Internet lines of multiple different operators, so that each Internet exit is connected to the Internet lines of no less than two operators. In this way, even if an abnormality occurs in the Internet line of an operator, the respective Internet exits of the computing data center, the network data center, and the control data center (i.e., each Internet exit) can still maintain normal network communication and data transmission through the Internet lines of other operators connected, so that the independent fault domain can isolate the entire business processing flow, and realize the safe isolation between different sub-business systems, different business scenarios, and different Internet exits, which is conducive to the realization of distributed deployment, the setting of independent fault domains, and high availability of the system.
[0059] Here, as an optional embodiment, Figure 3 A flow chart of an Internet line wiring method applicable to each type of data center standardized distributed resource area provided in an embodiment of the present application is shown, such as Figure 3 As shown, the Internet line wiring method includes steps S301-S302, specifically:
[0060] S301, for each of the Internet outlets, interconnect multiple optical transmission devices with a router corresponding to the Internet outlet through an optical fiber distribution frame.
[0061] Here, for each Internet exit (i.e., the Internet exit of the computing data center, the network data center, and the control data center), the above-mentioned multiple optical transmission devices respectively correspond to multiple different operators connected to the Internet exit, that is, each operator corresponds to an optical transmission device, and the optical transmission device is interconnected with the router corresponding to the Internet exit through a fiber optic distribution frame.
[0062] S302: For each of the optical transmission devices, dual uplink the optical transmission device to a plurality of different local end nodes of the target operator.
[0063] Here, the above-mentioned target operator represents the operator corresponding to the optical transmission equipment; wherein, each operator's multiple different local end nodes respectively deploy optical cables to the operator access room of the target data center, and each operator's corresponding optical transmission equipment is also deployed in the above-mentioned operator access room. Based on this, each optical transmission equipment can be dual-connected to multiple different local end nodes of the corresponding operator.
[0064] It should be noted that the above-mentioned multiple different terminal nodes include but are not limited to: terminal offices, switching offices, gateway offices and long-distance offices; among them, when operators deploy optical transmission equipment, they dual-connect the optical transmission equipment to different terminal nodes to ensure the reliability and redundancy of the network. This deployment method provides double protection for the business, ensuring that when one of the nodes fails, the business can be transmitted normally through another path, thereby maintaining the continuity of network services.
[0065] Specifically, within the target data center, the computing data center and the control data center are interconnected with the network data center through pre-connected optical cables, respectively, to achieve wired interconnection between standardized distributed resource areas of different types of data centers.
[0066] In an embodiment of the present application, the standardized distributed resource area of each type of data center mentioned above is used as the minimized infrastructure resource deployment unit in the target data center. At this time, in response to an abnormality in the infrastructure resources corresponding to any sub-business system in the target business system, the target data center can determine the data center where the abnormal infrastructure resources are deployed as an independent fault domain from the computing data center and the control data center, and isolate the determined fault domain in the target data center, so that the standardized distributed resource area of each type of data center mentioned above can be used as a starting point to build a standardized and modular fault isolation domain, strengthen the isolation of risk areas, implement integrated distributed deployment, build on demand at the module level, and deliver in phases to provide basic capabilities for on-demand expansion.
[0067] Based on the above-mentioned distributed resource area deployment method based on the data center provided in the embodiment of the present application, with distributed high availability as the goal, three small data centers focusing on realizing different functions, namely, a computing data center, a network data center and a control data center, are combined into a target data center that can replace the traditional data center architecture. The infrastructure resources corresponding to different sub-business systems are deployed in different of the above-mentioned small data centers, which is conducive to achieving secure isolation between different sub-business systems and different small data centers, and ensuring high reliability and high security of the overall application of the target business system.
[0068] Based on the same inventive concept, the present application also provides a distributed resource area deployment system corresponding to the above-mentioned distributed resource area deployment method based on the data center. Since the principle of solving the problem by the distributed resource area deployment system in the embodiment of the present application is similar to the above-mentioned distributed resource area deployment method in the embodiment of the present application, the implementation of the distributed resource area deployment system can refer to the implementation of the above-mentioned distributed resource area deployment method, and the repeated parts will not be repeated.
[0069] Reference Figure 4 As shown, Figure 4 A structural schematic diagram of a distributed resource area deployment system based on a data center provided in an embodiment of the present application is shown, wherein the distributed resource area deployment system is applied to a target data center, wherein the target data center includes: a computing data center, a network data center, and a control data center; wherein the computing data center and the control data center implement network communication within the target data center through the network data center, and the distributed resource area deployment system includes:
[0070] The grouping module 401 is used to group the multiple sub-business systems constituting the target business system according to the business requirements corresponding to the different sub-business systems, so as to obtain multiple sub-business system combinations; wherein each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements;
[0071] The first deployment module 402 is used for deploying the infrastructure resources corresponding to the sub-business system in the sub-business system combination on the computing data center for each of the sub-business system combinations if the business requirements corresponding to the sub-business system combination match the computing data center;
[0072] The second deployment module 403 is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control-type data center if the business requirements corresponding to the sub-business system combination match the control-type data center.
[0073] In an optional implementation, the distributed resource area deployment system further includes a communication module, wherein the communication module is used to:
[0074] A communication connection is established between the network-based data center and external third-party devices through a hybrid cloud dedicated line; wherein the external third-party devices include at least: a client of the target business system and a terminal device corresponding to the third-party cloud service provider of the target data center.
[0075] In an optional implementation, the distributed resource area deployment system further includes an Internet egress deployment module, wherein the Internet egress deployment module is used to:
[0076] Independent Internet exits are respectively deployed on the computing data center, the network data center and the control data center, and each of the deployed Internet exits is connected to Internet lines of multiple different operators.
[0077] In an optional implementation, the distributed resource area deployment system further includes a wiring module, wherein the wiring module is used to:
[0078] For each of the Internet exits, multiple optical transmission devices are interconnected with a router corresponding to the Internet exit through an optical fiber distribution frame; wherein the multiple optical transmission devices correspond to the multiple different operators connected to the Internet exit respectively;
[0079] For each of the optical transmission devices, the optical transmission device is dual-uplinked to a plurality of different local end nodes of a target operator; wherein the target operator represents the operator corresponding to the optical transmission device.
[0080] In an optional implementation, when the target data center belongs to a data center in the same city, within the target data center, the computing data center, the network data center and the control data center are interconnected by bare fiber wavelength division multiplexing.
[0081] In an optional implementation, for any two target data centers deployed across regions, the network data centers included in each of the two target data centers are interconnected by a point-to-point dedicated line.
[0082] In an optional implementation, inside the target data center, the computing data center and the control data center are interconnected with the network data center via pre-connected optical cables, respectively.
[0083] In an optional implementation, the distributed resource zone deployment system further includes a fault domain determination module, wherein the fault domain determination module is used to:
[0084] In response to an abnormality in the infrastructure resources corresponding to any sub-business system in the target business system, the data center where the abnormal infrastructure resources are deployed is determined as an independent fault domain from the computing data center and the control data center, and the determined fault domain is isolated in the target data center.
[0085] In an optional implementation, the number of computing functional devices configured in the computing data center is greater than the number of computing functional devices configured in the network data center and the control data center respectively;
[0086] The number of network devices configured in the network data center is greater than the number of network devices configured in the computing data center and the control data center respectively;
[0087] The number of centralized control function devices configured in the control data center is greater than the number of centralized control function devices configured in the computing data center and the network data center respectively.
[0088] In the embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. The system embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of systems or units, which can be electrical, mechanical or other forms.
[0089] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.
[0090] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A distributed resource area deployment method based on a data center, characterized in that: Applied in a target data center, the target data center includes: a computing data center, a network data center and a control data center; wherein the computing data center and the control data center realize network communication within the target data center through the network data center, and the distributed resource area deployment method includes: According to the business requirements corresponding to different sub-business systems, multiple sub-business systems constituting the target business system are grouped to obtain multiple sub-business system combinations; wherein each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements; For each of the sub-business system combinations, if the business requirements corresponding to the sub-business system combination match the computing data center, the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the computing data center; If the business requirements corresponding to the sub-business system combination match the control-type data center, the infrastructure resources corresponding to the sub-business systems in the sub-business system combination are deployed on the control-type data center.
2. The distributed resource area deployment method according to claim 1, characterized in that: A communication connection is established between the network-based data center and external third-party devices through a hybrid cloud dedicated line; wherein the external third-party devices include at least: a client of the target business system and a terminal device corresponding to the third-party cloud service provider of the target data center.
3. The distributed resource area deployment method according to claim 1, characterized in that: Independent Internet exits are respectively deployed on the computing data center, the network data center and the control data center, and each of the deployed Internet exits is connected to Internet lines of multiple different operators.
4. The distributed resource area deployment method according to claim 3, characterized in that: The distributed resource area deployment method further includes: For each of the Internet exits, multiple optical transmission devices are interconnected with a router corresponding to the Internet exit through an optical fiber distribution frame; wherein the multiple optical transmission devices correspond to the multiple different operators connected to the Internet exit respectively; For each of the optical transmission devices, the optical transmission device is dual-uplinked to a plurality of different local end nodes of a target operator; wherein the target operator represents the operator corresponding to the optical transmission device.
5. The distributed resource area deployment method according to claim 1, characterized in that: When the target data center belongs to a data center in the same city, the computing data center, the network data center and the control data center are interconnected within the target data center by using bare fiber wavelength division multiplexing.
6. The distributed resource area deployment method according to claim 1, characterized in that: For any two target data centers deployed across regions, the network data centers contained in each of the two target data centers are interconnected by a point-to-point dedicated line.
7. The distributed resource area deployment method according to claim 1, characterized in that: Inside the target data center, the computing data center and the control data center are interconnected with the network data center via pre-connected optical cables.
8. The distributed resource area deployment method according to claim 1, characterized in that: The distributed resource area deployment method further includes: In response to an abnormality in the infrastructure resources corresponding to any sub-business system in the target business system, the data center where the abnormal infrastructure resources are deployed is determined as an independent fault domain from the computing data center and the control data center, and the determined fault domain is isolated in the target data center.
9. The distributed resource area deployment method according to claim 1, characterized in that: The distributed resource area deployment method further includes: The number of computing functional devices configured in the computing data center is greater than the number of computing functional devices configured in the network data center and the control data center respectively; The number of network devices configured in the network data center is greater than the number of network devices configured in the computing data center and the control data center respectively; The number of centralized control function devices configured in the control-type data center is greater than the number of centralized control function devices configured in the computing-type data center and the network-type data center respectively.
10. A distributed resource zone deployment system based on a data center, characterized in that: Applied in a target data center, the target data center includes: a computing data center, a network data center and a control data center; wherein the computing data center and the control data center realize network communication within the target data center through the network data center, and the distributed resource area deployment system includes: A grouping module, used to group multiple sub-business systems constituting a target business system according to the business requirements corresponding to different sub-business systems, to obtain multiple sub-business system combinations; wherein each of the sub-business system combinations is composed of one or more sub-business systems with similar business requirements; A first deployment module is used for deploying the infrastructure resources corresponding to the sub-business systems in each of the sub-business system combinations on the computing data center if the business requirements corresponding to the sub-business system combination match the computing data center; The second deployment module is used to deploy the infrastructure resources corresponding to the sub-business systems in the sub-business system combination on the control-type data center if the business requirements corresponding to the sub-business system combination match the control-type data center.
Citation Information
Patent Citations
Remote-place cloud data center management system based on three-layer network architecture
CN109547239A
Dual-active data center system and disaster recovery method and device
CN116016132A
Mixed deployment architecture for distributed services
US20170005883A1
Globally distributed utility computing cloud
WO2009111799A2