CN113794581A - Distributed CP unified deployment method, network equipment and storage medium - Google Patents
Distributed CP unified deployment method, network equipment and storage medium Download PDFInfo
- Publication number
- CN113794581A CN113794581A CN202110896461.1A CN202110896461A CN113794581A CN 113794581 A CN113794581 A CN 113794581A CN 202110896461 A CN202110896461 A CN 202110896461A CN 113794581 A CN113794581 A CN 113794581A
- Authority
- CN
- China
- Prior art keywords
- network element
- deployed
- cloud host
- network
- distributed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 239000013256 coordination polymer Substances 0.000 title claims abstract description 37
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000003860 storage Methods 0.000 title claims description 18
- 230000006855 networking Effects 0.000 claims abstract description 4
- 238000004590 computer program Methods 0.000 claims description 15
- 238000007635 classification algorithm Methods 0.000 claims description 9
- 239000002071 nanotube Substances 0.000 claims description 5
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000009826 distribution Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000008602 contraction Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011982 device technology Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/287—Remote access server, e.g. BRAS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a distributed CP unified deployment method which is applied to a VNF management server and used for acquiring all cloud host topologies in a networking; acquiring basic configuration template files which are uploaded and suitable for various network element types; analyzing the basic configuration template file, and after confirming the anti-affinity groups of the network elements to be deployed according to the analyzed information, correspondingly creating a network element model for each anti-affinity group, wherein the network element model comprises attribute information, and the network elements to be deployed in the same anti-affinity group have the same attribute information; acquiring cloud host nodes of a cloud host topology, and calculating the load condition of each cloud host node; confirming the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node; and starting network element configuration. The embodiment of the application realizes the uniform deployment of the distributed CP, reduces the artificial workload, is convenient to deploy, and has faster deployment speed.
Description
Technical Field
The present application relates to the field of communications device technologies, and in particular, to a distributed CP unified deployment method, a network device, and a storage medium.
Background
A vbrs-CP (virtual Broadband Access Server Control Plane) distributed architecture divides the function of the Control node CP which is originally found in a centralized manner into different functional network elements, so as to implement a Control Plane of the BRAS service. Each network element has definite functions and is matched with each other to complete a series of functions of user online, authentication, charging and the like.
The vBRAS-CP under the distributed architecture mainly comprises three network elements of CTRL-VM, BRAS-VM and FWD-VM. The CTRL-VM is responsible for network element management, unified configuration management, unified address management, unified license management, CP disaster tolerance, elastic expansion and contraction capacity, DP network element management and the like belonging to the same vBRAS-CP. The BRAS-VM is responsible for remote interface management, user management, access control, authentication authorization accounting, DP data backup and the like. The FWD-VM is responsible for communication and message distribution with the DP network element, such as Radius, WEB information distribution, and the like. Generally, two CTRL-VM, BRAS-VM, and FWD-VM are stacked to form a primary device and a secondary device, and the primary device and the secondary device must be distributed and deployed on different servers, so as to prevent the functions of the primary device and the secondary device from being affected simultaneously when one server fails.
The VNF management server is NFV deployment, configuration and life cycle management software which conforms to ETSI NFV specifications, can manage a plurality of physical servers, flexibly configures required resources according to user service requirements, and completes the creation and deployment of virtual network elements. Meanwhile, the VNF management server can establish connection with the network element through a NETCONF protocol, the required initial configuration is issued to the network element, and the management platform is enabled to manage the life cycle of the network element after the network element is started, and manual intervention and operation are not needed.
The VNF network element model is responsible for defining the VNF resource model.
According to the existing deployment scheme known by the inventor, a user operates a VNF management server, and determines an operating system used by a network element to be deployed by selecting different types of image files. And determining the hardware configuration of the network element to be deployed by selecting the interface name, the interface type, the CPU core number, the memory size, the storage space size and the like. And determining a cloud host server where the network element to be deployed is located by selecting the cloud host according to the control node, the available domain or the computing node. The VNF management server first creates a VNF network element model with custom attribute values according to the above selection.
Then, according to the designated VNF network element model, the VNF management server analyzes the parameters, and can rapidly deploy a type of network elements with custom attributes. If the user selects the cloud host according to the control node, the network element is deployed on the computing node which is managed by the control node and meets the requirements of the network element; if the designated available domain is selected, the network element is deployed on the computing node which meets the requirements of the network element in the designated available domain; if a designated compute node is selected, the network element will be deployed on the designated compute node.
In the existing deployment scheme, in order to implement the distribution of each type of stacked network elements, each network element needs to select different computing nodes to be deployed independently. When the required number of network elements in the network is large, there may be a lot of duplicated work. Therefore, the existing deployment scheme cannot realize rapid deployment, cannot realize distributed deployment of stacked network elements, and cannot realize a vbars-CP distributed architecture.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides a distributed CP unified deployment method, a network device, and a storage medium.
According to a first aspect of the embodiments of the present application, a distributed CP unified deployment method is provided, which is applied to a VNF management server,
acquiring all cloud host topologies included in networking;
acquiring basic configuration template files which are uploaded and suitable for various network element types;
analyzing the basic configuration template file, and after confirming the anti-affinity groups of the network elements to be deployed according to the analyzed information, correspondingly creating a network element model for each anti-affinity group, wherein the network element model comprises attribute information, and the network elements to be deployed in the same anti-affinity group have the same attribute information;
acquiring cloud host nodes of a cloud host topology, and calculating the load condition of each cloud host node;
confirming the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node;
and starting network element configuration.
Preferably, the analyzing the basic configuration template file and confirming the anti-affinity group of the network element to be deployed according to the analyzed information includes:
analyzing the basic configuration template file to obtain parameter information, wherein the parameter information at least comprises network element marks which are in one-to-one correspondence with each network element;
the VNF management server obtains the anti-affinity group number through a classification algorithm by using the network element mark, and if the anti-affinity group numbers of the network elements to be deployed are the same, the VNF management server belongs to an anti-affinity group.
Further, according to different types of the network elements to be deployed, the network element marks of the network elements to be deployed are set in different sections.
Further, there are three types of network elements to be deployed, and the VNF management server obtains a group number of the anti-affinity group through a classification algorithm by using the network element identifier, including:
when the network element to be deployed is of the first type, the anti-affinity group number is (network element mark number-1)/2 + 1;
when the network element to be deployed is of the second type, the anti-affinity group number is (network element mark number-5)/2 + 2;
when the network element to be deployed is of the third type, the anti-affinity group number is (network element number-97)/2 + 66.
Preferably, the determining the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node includes:
acquiring attribute information of a current network element to be deployed;
judging whether deployed network elements in the cloud host topology have the same attribute information or not; if not, selecting a cloud host node from the cloud host topology to deploy the current network element to be deployed; and if so, deleting the cloud host nodes of the deployed network elements with the same attribute information from all the nodes of the cloud host topology, and selecting the cloud host nodes from the rest cloud hosts to deploy the current network elements to be deployed.
Further, cloud host nodes are selected from the cloud host topology, the cloud host nodes comprise the load of each cloud host node in the cloud host topology, and the cloud host nodes with small load are selected to be used for deploying the current network elements to be deployed.
Preferably, the basic configuration template file further comprises an internal channel Vlan and a network segment which are customized and modified according to the network element type.
Further, the starting of the network element configuration includes:
acquiring uploaded mirror image files containing various network elements, and analyzing the mirror image files to acquire operating systems corresponding to the network elements;
obtaining an initial configuration file through network element model conversion corresponding to a network element, starting an operating system by the network element, and reading the initial configuration file;
different types of network elements establish network connection by configuring the same Vlan and network segment;
taking one network element as a nanotube network element, detecting other network elements and recording;
the network element is started.
A second aspect of the present application provides a network device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the distributed CP unified deployment method is performed.
A third aspect of the present application provides a storage medium having stored thereon computer program instructions for implementing the distributed CP unified deployment method described above when executed by a processor.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the embodiment of the application realizes the uniform deployment of the distributed CP, reduces the artificial workload, is convenient to deploy, and has faster deployment speed.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments consistent with the present application and together with the application, serve to explain the principles of the application.
FIG. 1 is a block diagram of a distributed CP architecture according to an embodiment of the present application;
FIG. 2 is a flow chart of an interaction according to an embodiment of the present application;
fig. 3 is a flowchart of a method for initiating network element configuration according to an embodiment of the present application;
FIG. 4 is a flow chart of an embodiment of the present application;
fig. 5 is a hardware block diagram of a network device according to the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
In order to solve the problems in the background art, the application provides a distributed CP unified deployment method, which is applied to a VNF management server and a cloud host topology composed of cloud hosts. Various network elements are deployed on cloud host nodes of a cloud host topology. There are many types of network elements to be deployed here, taking network element deployment under a vbars-CP distributed architecture as an example, the network elements are mainly divided into three types according to functions, and an architecture diagram formed by the three types of network elements is shown in fig. 1. The CTRL-VM is responsible for network element management, unified configuration management, unified address management, unified license management, CP disaster tolerance, elastic expansion and contraction capacity, DP network element management and the like belonging to the same vBRAS-CP. The BRAS-VM is responsible for remote interface management, user management, access control, authentication authorization accounting, DP data backup and the like. The FWD-VM is responsible for communication and message distribution with the DP network element, such as Radius, WEB information distribution, and the like. CP refers to the Control Plane. DP refers to the Data Plane forwarding Plane.
In the first embodiment of the present application, as shown in fig. 2:
0001: the VNF management server acquires all cloud host topologies in the networking.
0003: and the VNF management server acquires the uploaded basic configuration template files suitable for various network element types.
The basic configuration template file can self-define internal channels Vlan and network segments of various network elements, and can also set parameter information such as the number of the network elements, the ranges of marks of different types of network elements, the number of CPU cores, the size of a memory and a storage space, the name of an interface, the type of the interface and the like. Wherein each network element has a unique label, and each network element has a network element label number. When the number of the network elements is customized, the number of the network element marks must correspond to the number of the network element marks.
Example 1: CTRL-VM number 2;
the number of BRAS-VM is 4;
the FWD-VM number is 2;
CTRL-VM network element tag number range: 1-2;
BRAS-VM network element mark number scope: 97 to 100;
FWD-VM network element marking number range: 5-6.
The internal channel Vlan and the network segment realize internal communication between different types of network elements.
The uploaded files are not only basic configuration template files, but also image file compression packages containing different types of network element image files. The image file determines the operating system of the network element to be deployed, so that the image files required by different types of network elements are different. The image file is used during the network element configuration, so the image file does not need to be uploaded at the step, and the image file only needs to be uploaded before the network element configuration is started.
0005: and the VNF management server analyzes the basic configuration template file and confirms the anti-affinity group of the network element to be deployed according to the analyzed information.
The method comprises the following steps:
00051: the VNF management server analyzes the basic configuration template file to obtain parameter information;
00052: and the VNF management server obtains the anti-affinity group numbers by using the network element marks through a classification algorithm, and if the anti-affinity group numbers of the network elements to be deployed are the same, the VNF management server belongs to one anti-affinity group.
The VNF management server obtains the group number of the anti-affinity group by using the network element mark through a classification algorithm, and the method comprises the following steps:
when the network element to be deployed is of the first type, the anti-affinity group number is (network element mark number-1)/2 + 1;
when the network element to be deployed is of the second type, the anti-affinity group number is (network element mark number-5)/2 + 2;
when the network element to be deployed is of the third type, the anti-affinity group number is (network element number-97)/2 + 66.
Taking the foregoing vbars-CP distributed architecture example 1 as an example, a classification algorithm is exemplified.
When CTRL-VM network element marking number range: 1-2, taking a network element mark number 2, and then setting the anti-affinity group number as 1;
when the BRAS-VM network element mark number range is as follows: 97-98, if the network element mark number 97 is taken, the anti-affinity group number is 66;
when the FWD-VM network element mark number ranges: and 5-6, taking the network element mark number 6, and then the anti-affinity group number is 2.
If the same anti-affinity group number is obtained by calculation, the network elements are located in the same anti-affinity group, as shown in fig. 1, and the network elements in one frame belong to one anti-affinity group.
0007: and correspondingly establishing a network element model for each anti-affinity group, wherein the network element model comprises attribute information, and the network elements to be deployed in the same anti-affinity group have the same attribute information.
The VNF management server creates a network element model of the anti-affinity strategy, the network element model comprises customized specification attributes such as mirror images, hardware configuration, interface binding and the like, and a network element with the customized specification attributes is created through the network element model. Compared with the conventional network element model, the network element model in the embodiment of the application is added with a new attribute information, and the network elements to be deployed have the same attribute information in the same anti-affinity group. The attribute information may be a string of characters or a string of numbers, etc. In the embodiment of the present application, the network element model is a VNF network element model.
0009: the VNF management server acquires cloud host nodes of the cloud host topology and calculates the load condition of each cloud host node.
The load comprises the number of network elements started on the physical server, the utilization rate of the memory, the utilization rate of the CPU and the like.
The cloud host node may be a computing node, a control node, or a network element node within an available domain that may select a cloud host deployment.
0011: and confirming the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node.
Acquiring attribute information of a current network element to be deployed;
judging whether deployed network elements in the cloud host topology have the same attribute information or not;
if not, selecting a cloud host node from the cloud host topology to deploy the current network element to be deployed;
and if so, deleting the cloud host nodes of the deployed network elements with the same attribute information from all the nodes of the cloud host topology, and selecting the cloud host nodes from the rest cloud hosts to deploy the current network elements to be deployed.
Two network elements with the same attribute in one anti-affinity group can be used as a master stack and cannot be arranged on one cloud host node in the manner.
In the embodiment of the application, the cloud host nodes are selected from the cloud host topology, the cloud host node load in the cloud host topology is calculated, and the cloud host nodes with small load are selected to be used for deploying the current network element to be deployed. The cloud host node load can obtain which cloud host node has a small load through a load balancing algorithm. Since the load balancing algorithm is a common algorithm in the art, it will not be described herein.
0013: the network element configuration is initiated as shown in figure 3.
00131: and acquiring the operating system corresponding to each network element by analyzing the network element mirror image file.
00132: and obtaining an initial configuration file by converting part of configuration information in the network element model corresponding to each network element.
The initial configuration file is placed at a well defined place, for example, as an optical drive to be hung on a virtual device. The network element starts the mirror image operation system, reads the initial configuration file and executes one by one.
00133: and different types of network elements establish network connection by configuring the same Vlan and network segment.
00134: and taking one network element as a nanotube network element, detecting other network elements and recording.
In the embodiment of the application, the CTRL-VM is used as the nanotube, and the CTRL-VM can detect the link bi-pass situation with other network elements through a link detection mechanism. The network elements successfully probed can be uniformly recorded in the registry of the CTRL-VM.
00135: the network element is started.
According to the foregoing, network elements having the same attribute information in an anti-affinity group form a primary/secondary stack. The network element with limited starting is mainly in role, and the other network element is standby and mutually guarantees.
And (4) repeatedly executing the steps 00131 and 00135 according to the information of the number of the network elements of each type in the basic configuration template file until all the network elements are created, thereby realizing the uniform deployment of the distributed CP.
The embodiment of the application realizes the uniform deployment of the distributed CP, reduces the artificial workload, is convenient to deploy, and has faster deployment speed.
Example two:
the distributed CP unified deployment method is applied to a VNF management server and used for acquiring all cloud host topologies in a network; acquiring basic configuration template files which are uploaded and suitable for various network element types; analyzing the basic configuration template file, and after confirming the anti-affinity groups of the network elements to be deployed according to the analyzed information, correspondingly creating a network element model for each anti-affinity group, wherein the network element model comprises attribute information, and the network elements to be deployed in the same anti-affinity group have the same attribute information; acquiring computing nodes of a cloud host topology, and computing the load condition of each cloud host node; confirming the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node; the network element configuration is initiated as shown in figure 4.
Preferably, the analyzing the basic configuration template file and confirming the anti-affinity group of the network element to be deployed according to the analyzed information includes: analyzing the basic configuration template file to obtain parameter information, wherein the parameter information at least comprises network element marks which are in one-to-one correspondence with each network element; the VNF management server obtains the anti-affinity group number through a classification algorithm by using the network element mark, and if the anti-affinity group numbers of the network elements to be deployed are the same, the VNF management server belongs to an anti-affinity group.
And setting the network element mark number of the network element to be deployed in different sections according to different types of the network elements to be deployed.
In this embodiment, there are three types of network elements to be deployed, and the VNF management server obtains a group number of the anti-affinity group through a classification algorithm by using the network element identifier, including:
when the network element to be deployed is of the first type, the anti-affinity group number is (network element mark number-1)/2 + 1;
when the network element to be deployed is of the second type, the anti-affinity group number is (network element mark number-5)/2 + 2;
when the network element to be deployed is of the third type, the anti-affinity group number is (network element number-97)/2 + 66.
As a preferred embodiment of the present invention, determining the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node includes: acquiring attribute information of a current network element to be deployed; judging whether deployed network elements in the cloud host topology have the same attribute information or not; if not, selecting a cloud host node from the cloud host topology to deploy the current network element to be deployed; and if so, deleting the cloud host nodes of the deployed network elements with the same attribute information from all the nodes of the cloud host topology, and selecting the cloud host nodes from the rest cloud hosts to deploy the current network elements to be deployed.
Preferably, the cloud host nodes are selected from the cloud host topology, including calculating the load of each cloud host node in the cloud host topology, and selecting the load small cloud host nodes for deploying the current network element to be deployed.
Preferably, the basic configuration template file further includes an internal channel Vlan and a network segment customized according to the network element type.
As a preferred preference of this embodiment, the starting of the network element configuration includes:
acquiring uploaded mirror image files containing various network elements, and analyzing the mirror image files to acquire operating systems corresponding to the network elements;
obtaining an initial configuration file through network element model conversion corresponding to a network element, starting an operating system by the network element, and reading the initial configuration file;
different types of network elements establish network connection by configuring the same Vlan and network segment;
and taking one network element as a nanotube network element, detecting and recording other network elements, and starting the network elements.
The application also provides a network device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the distributed CP unified deployment method is performed, as shown in fig. 5.
The present application finally provides a storage medium having stored thereon computer program instructions for implementing the above-described distributed CP unified deployment method when executed by a processor.
The machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The present invention is not intended to be limited to the particular embodiments shown and described, but is to be accorded the widest scope consistent with the principles and novel features herein disclosed.
Claims (10)
1. A distributed CP unified deployment method is applied to a VNF management server and is characterized in that all cloud host topologies are included in the networking;
acquiring basic configuration template files which are uploaded and suitable for various network element types;
analyzing the basic configuration template file, and after confirming the anti-affinity groups of the network elements to be deployed according to the analyzed information, correspondingly creating a network element model for each anti-affinity group, wherein the network element model comprises attribute information, and the network elements to be deployed in the same anti-affinity group have the same attribute information;
acquiring cloud host nodes of the cloud host topology, and calculating the load condition of each cloud host node;
confirming the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node;
and starting network element configuration.
2. The distributed CP unified deployment method of claim 1, wherein parsing the basic configuration template file, and determining the anti-affinity group of the to-be-deployed network element according to the parsed information comprises:
analyzing the basic configuration template file to obtain parameter information, wherein the parameter information at least comprises network element marks which are in one-to-one correspondence with each network element;
and the VNF management server obtains an anti-affinity group number by using the network element mark through a classification algorithm, and if the anti-affinity group numbers of the network elements to be deployed are the same, the VNF management server belongs to one anti-affinity group.
3. The distributed CP unified deployment method of claim 2, wherein the network element identifier of the network element to be deployed is set in different sections according to different types of the network element to be deployed.
4. The distributed CP unified deployment method of claim 3, wherein the network elements to be deployed have three types, and the VNF management server obtains a group number of an anti-affinity group through a classification algorithm by using the network element identifier, including:
when the network element to be deployed is of the first type, the anti-affinity group number is (network element mark number-1)/2 + 1;
when the network element to be deployed is of the second type, the anti-affinity group number is (network element mark number-5)/2 + 2;
when the network element to be deployed is of the third type, the anti-affinity group number is (network element number-97)/2 + 66.
5. The distributed CP unified deployment method of claim 1, wherein determining the node position of the current network element to be deployed according to the attribute information of the current network element to be deployed and the load condition of each cloud host node comprises:
acquiring attribute information of a current network element to be deployed;
judging whether deployed network elements in the cloud host topology have the same attribute information or not; if not, selecting a cloud host node from the cloud host topology to deploy a current network element to be deployed; and if so, deleting the cloud host nodes of the deployed network elements with the same attribute information from all the nodes of the cloud host topology, and selecting the cloud host nodes from the rest cloud hosts to deploy the current network elements to be deployed.
6. The distributed CP unified deployment method of claim 5, wherein selecting a cloud host node from the cloud host topology comprises calculating a load of each cloud host node in the cloud host topology, and selecting a cloud host node with a small load for deploying the current network element to be deployed.
7. The distributed CP unified deployment method of claim 1, wherein said basic configuration template file further comprises an internal channel Vlan and a network segment customized according to a network element type.
8. The distributed CP unified deployment method of claim 7, wherein the starting of the network element configuration comprises:
acquiring uploaded mirror image files containing various network elements, and analyzing the mirror image files to acquire operating systems corresponding to the network elements;
obtaining an initial configuration file through network element model conversion corresponding to the network element, starting the operating system by the network element, and reading the initial configuration file;
different types of network elements establish network connection by configuring the same Vlan and network segment;
taking one network element as a nanotube network element, detecting other network elements and recording;
the network element is started.
9. Network device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor executes the program to perform the distributed CP unified deployment method according to any of claims 1 to 8.
10. A storage medium having stored thereon computer program instructions, wherein the program instructions, when executed by a processor, are for implementing the distributed CP unified deployment method as claimed in any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110896461.1A CN113794581B (en) | 2021-08-05 | 2021-08-05 | Distributed CP unified deployment method, network equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110896461.1A CN113794581B (en) | 2021-08-05 | 2021-08-05 | Distributed CP unified deployment method, network equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113794581A true CN113794581A (en) | 2021-12-14 |
| CN113794581B CN113794581B (en) | 2023-11-07 |
Family
ID=78877154
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110896461.1A Active CN113794581B (en) | 2021-08-05 | 2021-08-05 | Distributed CP unified deployment method, network equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113794581B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115269126A (en) * | 2022-09-28 | 2022-11-01 | 中国人寿保险股份有限公司上海数据中心 | Cloud platform inverse affinity scheduling system based on cosine similarity |
| CN115412440A (en) * | 2022-08-19 | 2022-11-29 | 浪潮思科网络科技有限公司 | VNF device distributed deployment method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017080391A1 (en) * | 2015-11-09 | 2017-05-18 | 中兴通讯股份有限公司 | Network service deployment method and device |
| CN109889377A (en) * | 2019-01-29 | 2019-06-14 | 京信通信***（中国）有限公司 | The method and apparatus of VNF are disposed in NFV system based on Openstack |
| CN110098946A (en) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | Virtualize the dispositions method and device of network element device |
| CN110661641A (en) * | 2018-06-29 | 2020-01-07 | 华为技术有限公司 | Virtual network function VNF deployment method and device |
| CN111193782A (en) * | 2019-12-18 | 2020-05-22 | 北京航天智造科技发展有限公司 | PAAS cloud cluster construction method and device, electronic equipment and storage medium |
| CN112367182A (en) * | 2020-09-29 | 2021-02-12 | 新华三大数据技术有限公司 | Configuration method and device of disaster recovery main and standby equipment |
-
2021
- 2021-08-05 CN CN202110896461.1A patent/CN113794581B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017080391A1 (en) * | 2015-11-09 | 2017-05-18 | 中兴通讯股份有限公司 | Network service deployment method and device |
| CN110098946A (en) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | Virtualize the dispositions method and device of network element device |
| CN110661641A (en) * | 2018-06-29 | 2020-01-07 | 华为技术有限公司 | Virtual network function VNF deployment method and device |
| CN109889377A (en) * | 2019-01-29 | 2019-06-14 | 京信通信***（中国）有限公司 | The method and apparatus of VNF are disposed in NFV system based on Openstack |
| CN111193782A (en) * | 2019-12-18 | 2020-05-22 | 北京航天智造科技发展有限公司 | PAAS cloud cluster construction method and device, electronic equipment and storage medium |
| CN112367182A (en) * | 2020-09-29 | 2021-02-12 | 新华三大数据技术有限公司 | Configuration method and device of disaster recovery main and standby equipment |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115412440A (en) * | 2022-08-19 | 2022-11-29 | 浪潮思科网络科技有限公司 | VNF device distributed deployment method and device |
| CN115412440B (en) * | 2022-08-19 | 2024-07-09 | 浪潮思科网络科技有限公司 | Distributed deployment method and device for VNF (virtual network function) device |
| CN115269126A (en) * | 2022-09-28 | 2022-11-01 | 中国人寿保险股份有限公司上海数据中心 | Cloud platform inverse affinity scheduling system based on cosine similarity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113794581B (en) | 2023-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103460203B (en) | cluster unique identifier | |
| US20200081731A1 (en) | Method, system and apparatus for creating virtual machine | |
| CN113794581B (en) | Distributed CP unified deployment method, network equipment and storage medium | |
| CN105955824A (en) | Method and device for configuring virtual resource | |
| CN106339177A (en) | Method and device for creating virtual machines | |
| CN107783816A (en) | The method and device that creation method and device, the big data cluster of virtual machine create | |
| EP3442201B1 (en) | Cloud platform construction method and cloud platform | |
| EP3432132B1 (en) | Data storage method and device | |
| CN110855458B (en) | Configuration command generation method and equipment | |
| CN111641515A (en) | VNF life cycle management method and device | |
| CN105704188A (en) | Deployment method and apparatus of applications and services | |
| CN108259200A (en) | A kind of physical network function PNF moving methods and relevant device | |
| CN105635311A (en) | Method for synchronizing resource pool information in cloud management platform | |
| CN108600282A (en) | Micro services dissemination method, device, storage medium and computer equipment | |
| CN104793981B (en) | A kind of online snapshot management method and device of cluster virtual machine | |
| CN109672752A (en) | The synchronous method of data and node | |
| CN108418752B (en) | A kind of creation method and device of aggregation group | |
| CN109861869B (en) | Configuration file generation method and device | |
| CN108228310B (en) | Balanced deployment method and device of virtual network function | |
| CN112953739B (en) | K8S platform-based method, system and storage medium for nanotube SDN | |
| CN110768811B (en) | Method, device and system for updating YANG model file library | |
| CN111324368B (en) | Data sharing method and server | |
| CN107493181A (en) | The indicating means and device of virtual extended port | |
| CN113133030A (en) | Management method and device for RAN (radio access network) scene of 5G (third generation) wireless access network | |
| CN115412440B (en) | Distributed deployment method and device for VNF (virtual network function) device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |