WO2020010887A1 - 网络部署方法及装置 - Google Patents
网络部署方法及装置 Download PDFInfo
- Publication number
- WO2020010887A1 WO2020010887A1 PCT/CN2019/082109 CN2019082109W WO2020010887A1 WO 2020010887 A1 WO2020010887 A1 WO 2020010887A1 CN 2019082109 W CN2019082109 W CN 2019082109W WO 2020010887 A1 WO2020010887 A1 WO 2020010887A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- orchestration
- protocol
- parameters
- relationship
- Prior art date
Links
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
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- 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
-
- 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
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
-
- 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/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- 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/12—Discovery or management of network topologies
-
- 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/14—Network analysis or design
-
- 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/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
Definitions
- the present disclosure relates to the field of the Internet, and in particular, to a network deployment method and device.
- Method 1 Configure the device based on the template. That is, a startup configuration template is created in advance for a zero configuration device. After the zero-configuration device completes the initial configuration, it searches for a corresponding startup configuration template to deploy to the zero-configuration device according to the device type information, and then runs the startup configuration template to complete the automatic configuration of the zero-configuration device.
- Method 2 Configure the device based on the topology. That is, according to the saved configuration information of the device, a Link Layer Discovery Protocol (LLDP) message is delivered and the network topology is collected. Second, stack devices based on the network topology to get a simplified network topology. Then, continue to configure other protocols for the devices in the simplified network topology to complete the network configuration.
- LLDP Link Layer Discovery Protocol
- Method 3 Device configuration based on identity. That is, the device information and neighbor relationship of the current device are acquired, so as to identify the current device according to the device information and neighbor relationship of the current device, and then configure the current device according to the identified device identity.
- Method four Configure devices based on neighbors. That is, the device to be deployed obtains a preset description of the neighbor by accessing the neighbor to generate configuration information. Then, the corresponding preset configuration file is downloaded from the preset server according to the configuration information, and the preset configuration file is automatically started to run, thereby completing the configuration of the device to be deployed.
- At least part of the embodiments of the present disclosure provide a network deployment method and device to solve at least the problems of high operation complexity and low fault tolerance of the network deployment methods provided in the related art.
- a network deployment method including: obtaining network orchestration parameters, a dependency relationship chain, and a network topology, wherein each protocol node in the dependency relationship chain is pre-configured with a corresponding orchestration template and orchestration.
- the template is used to describe the parameter information that each protocol node depends on; the network protocol orchestration is performed according to the network orchestration parameters, the dependency relationship chain and the network topology to generate network configuration information; and the network configuration information is delivered to the device.
- a network deployment apparatus including: a network orchestration module configured to obtain network orchestration parameters, a dependency relationship chain, and a network topology, wherein each protocol node in the dependency relationship chain is pre-configured There are corresponding orchestration templates.
- the orchestration templates are used to describe the parameter information that each protocol node depends on; and the network protocol orchestration is generated according to the network orchestration parameters, the dependency relationship chain and the network topology to generate network configuration information.
- the network configuration information is delivered to the device.
- a network deployment device includes a network orchestration module configured to obtain network orchestration parameters, a dependency relationship chain, and a network topology, wherein each of the dependency relationship chains
- a network orchestration module configured to obtain network orchestration parameters, a dependency relationship chain, and a network topology, wherein each of the dependency relationship chains
- Each protocol node is pre-configured with a corresponding orchestration template, and the orchestration template is used to describe the parameter information that each protocol node depends on; and the network protocol orchestration is generated according to the network orchestration parameters, the dependency relationship chain and the network topology to generate network configuration information; Module, set to deliver network configuration information to the device.
- a storage medium stores a computer program, and the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
- an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute any one of the above. Steps in a method embodiment.
- the obtained network orchestration parameters, dependency chains, and network topology are used to perform overall network planning before network deployment, simplifying the network deployment process and automatically generating network configuration information, reducing manual participation, and further network
- the configuration information is then sent to the equipment of the manufacturer. Therefore, it can solve the problems of high operation complexity and low fault tolerance of the network deployment methods provided in related technologies, and achieve the established dependency chain to reduce the operation complexity of the network deployment configuration process, which is more helpful for large data. Automatic deployment and rapid delivery of central infrastructure networks.
- FIG. 1 is a block diagram of a hardware structure of a computer terminal in a network deployment method according to an embodiment of the present disclosure
- FIG. 2 is a flowchart of a network deployment method according to an embodiment of the present disclosure
- FIG. 3 is a logic diagram of networking according to an optional embodiment of the present disclosure
- FIG. 4 is a schematic diagram of a dependency relationship chain according to an optional embodiment of the present disclosure.
- FIG. 5 is a schematic diagram of another dependency relationship chain according to an optional embodiment of the present disclosure.
- FIG. 6 is a flowchart of a network orchestration process according to an optional embodiment of the present disclosure.
- FIG. 7 is a structural block diagram of a network deployment apparatus according to an embodiment of the present disclosure.
- FIG. 1 is a block diagram of a hardware structure of a computer terminal in a network deployment method according to an embodiment of the present disclosure.
- the computer terminal may include one or more (only one is shown in FIG. 1) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) And a memory 104 configured to store data, optionally, the computer terminal may further include a transmission device 106 and an input-output device 108 configured as a communication function.
- FIG. 1 is only an illustration, and does not limit the structure of the computer terminal described above.
- the computer terminal may further include more or fewer components than those shown in FIG. 1, or have a configuration different from that shown in FIG. 1.
- the memory 104 may be configured to store a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the network deployment method in the embodiment of the present disclosure.
- the processor 102 executes the computer program stored in the memory 104 to execute Various functional applications and data processing, that is, the aforementioned network deployment method is implemented.
- the memory 104 may include a high-speed random access memory, and may further include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memory.
- the memory 104 may further include memory remotely disposed with respect to the processor 102, and these remote memories may be connected to a computer terminal through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
- the transmission device 106 is configured to receive or transmit data via a network.
- Specific examples of the above network may include a wireless network provided by a communication provider of a computer terminal.
- the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network equipment through a base station so as to communicate with the Internet.
- the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet in a wireless manner.
- RF radio frequency
- FIG. 2 is a flowchart of a network deployment method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps:
- Step S22 Obtain network orchestration parameters, dependency relationship chains, and network topology, wherein each protocol node in the dependency relationship chain is pre-configured with a corresponding orchestration template, and the orchestration template is used to describe parameter information that each protocol node depends on;
- Step S24 Perform network protocol orchestration according to the network orchestration parameters, the dependency relationship chain, and the network topology to generate network configuration information
- step S26 the network configuration information is delivered to the device.
- the execution subject of the above steps may be a terminal or the like, but is not limited thereto.
- the protocol nodes in the above dependency chain refer to a plurality of protocols to be configured on the network. Among them, one protocol needs to rely on another protocol to complete a specific network function, and a dependency chain is established through the inter-protocol dependency relationship. Part of the agreement relationship chain.
- the parameter information that each of the protocol nodes depends on may include, but is not limited to, the pool parameters and global parameters that each protocol node depends on.
- step S22 acquiring network orchestration parameters may include the following execution steps:
- Step S221 obtaining protocol parameters, where the protocol parameters include at least: a protocol to be configured on the network, and configuration parameters and global parameters associated with the protocol to be configured;
- Step S222 obtaining orchestration parameters, where obtaining the orchestration parameters includes at least the following execution steps:
- step S2221 a primary parameter is obtained, and the primary parameter is a representative parameter that faces the overall structure of the network and is simplified.
- Protocol parameters refer to the protocols to be configured on the network, as well as the configuration parameters and global parameters of the protocols.
- the orchestration parameters include at least: primary parameters, which refer to the simplified, representative parameters of the overall structure of the network.
- the network structure of a virtual data center can be divided into a traditional single-layer network (underlay) and an overlay logical network (overlay) built on the underlay network. )Wait.
- the underlay network is the basic network, an IP network used to carry user services.
- the overlay network is a logical network constructed on the underlay network through virtual machine technology. The following uses VDC's underlay network as an example to implement deployment.
- FIG. 3 is a schematic diagram of a networking logic according to an optional embodiment of the present disclosure.
- the underlay network adopts a Spine-Leaf topology structure to carry the service business plane.
- Deployment requirements include stacking of access switches to implement active and standby, and access switches are connected to aggregation switches.
- Configuration protocols include but are not limited to: Link Aggregation Control Protocol (LACP), Virtual Local Area Network (VLAN), and Intermediate System to Intermediate System. to Intermediate System (hereinafter referred to as the I protocol), and implement Layer 3 interworking.
- LACP Link Aggregation Control Protocol
- VLAN Virtual Local Area Network
- I protocol Intermediate System to Intermediate System
- the specific implementation process of this optional embodiment is as follows:
- Initializing network orchestration may include: setting protocol parameters and orchestration parameters.
- the protocol parameters may include: configuration parameters of the protocol and global parameters of the protocol.
- the programming parameters may include at least: primary parameters.
- Primary parameters refer to the simplified, representative parameters of the overall structure of the network. Under normal circumstances, if the user sets the primary orchestration parameters, the orchestration of the network can be achieved.
- loopback1 10.30.0.1 / 32
- loopback2 10.30.1.1 / 32
- vlanid 101
- vlanip 10.30.3.2 / 30, thereby defining a vlan allocation.
- the initial value of the identifier is 101
- the vlan IP uses a step allocation method, which is assigned in order: 10.30.3.2/30, 10.30.3.6/30, 10.30.3.10/30, ...
- the routing protocol I is defined, and two loopbacks are defined (the IP address is allocated in steps), and the routing advertisement interface is added.
- the Spine-Leaf network of a data center is configured with an underlay network and bears both a service business plane and a store storage plane, that is, the data center services and storage share a single underlay basic network.
- Store storage surface needs VRF isolation, and the link aggregation group joins different VLANs.
- the general parameters of the orchestrator are designed.
- the underlay network carries the service business plane and the store storage plane.
- the storage plane is isolated by VRF.
- loopback1 10.30.0.1 / 32
- loopback2 10.30.1.1 / 32
- loopback3 10.325.1 / 32
- obtaining the orchestration parameters may further include the following execution steps:
- Step S2222 obtaining advanced parameters, where the advanced parameters are parameters obtained by orchestrating the primary parameters.
- the orchestration parameters may also include: advanced parameters, which refer to parameters obtained by orchestrating the primary parameters (that is, the parameter arranger).
- the advanced parameters are more comprehensive, and the configuration-oriented protocol supports the parameters set by the user.
- Parameter arranger refers to the process of refining the primary parameters to generate more comprehensive advanced parameters. This process will be further described in combination with the configuration process of the dependency chain mentioned below.
- step S2222 obtaining the advanced parameters includes at least the following execution steps:
- Step S22221 Acquire a pool parameter, where the pool parameter is used to limit an allocation range of the parameter value.
- the pool parameter refers to an allocation range that provides parameters defined by a list and by an initial value plus a step size.
- step S22 obtaining the dependency relationship chain may include the following execution steps:
- Step S223 Obtain a protocol relationship chain, where the protocol relationship chain is used to describe a dependency relationship between each protocol among the protocols to be configured on the network;
- Step S224 Obtain a pool parameter relationship chain, where the pool parameter relationship chain is used to describe the mutual relationship between each pool parameter among the pool parameters to be used on the network;
- Step S225 Obtain a dependency relationship between the protocol relationship chain and the pool parameter relationship chain, so that the pool parameter relationship chain is used to assign values to parameters in the protocol relationship chain.
- Dependency means that a configuration item needs to depend on another configuration item to complete a specific function.
- a dependency relationship chain is a relationship chain established by multiple configuration items through a dependency relationship.
- the dependency relationship chain may include: a protocol relationship chain and a pool parameter relationship chain.
- Protocol relationship chain refers to that a protocol needs to rely on another protocol to complete a specific network function, and a protocol relationship chain is established through the inter-protocol dependency relationship.
- the pool parameter relationship chain means that the allocation of one pool parameter depends on another pool parameter.
- the protocol relationship chain needs to rely on the pool parameter relationship chain at the same time to complete the value assignment of protocol parameters in the protocol relationship chain.
- FIG. 4 is a schematic diagram of a dependency relationship chain according to an optional embodiment of the present disclosure.
- the protocol relationship chain defines a local loopback interface (LOOPBACK), LACP, VLAN, and I protocols.
- LOOPBACK local loopback interface
- LACP LACP
- VLAN virtual local area network
- I protocols I protocols.
- the protocol relationship can be explained as follows: If a link joins LACP in an aggregation group to achieve connection reliability, load balancing, or dynamic link backup, the link is a dependency of LACP in the aggregation group. If LACP is added to a VLAN to implement network isolation, LACP is dependent on VLAN division. If a VLAN or LOOPBACK is added to the I route advertisement interface, then the VLAN or LOOPBACK is a dependency of I.
- LOOPBACK local loopback interface
- the pool parameter relationship chain defines the Sg pool, IP pool, VLAN pool, and I pool.
- user parameters can be arranged to obtain advanced parameters.
- the advanced parameters can include:
- the IP pool generated by user parameter orchestration where name is an import item that depends on the pool parameter or protocol relationship.
- the orchestration output is as follows:
- the vlan pool generated by user parameter orchestration the dependency chain includes ippool, and is imported through ippool, and the vlan dependency chain also outputs the name item.
- the orchestration output is as follows:
- the Sg pool of the pool parameter relationship chain is responsible for the ID allocation of LACP, SMARTGROUP, and the I pool is responsible for the systemid allocation, etc., which will not be described in detail here.
- step S22 acquiring the dependency relationship chain may further include the following execution steps:
- Step S226 Establish a corresponding relationship according to the obtained dependency relationship chain, where the corresponding relationship includes a plurality of orchestration items and a type corresponding to each orchestration item, an orchestration template, and a dependency relationship.
- the orchestration template defines the orchestration fields of the protocol, including: dependent pool parameters and global parameters.
- Table 1 is an explanation of each orchestration item in the dependency chain of FIG. 4, as shown in Table 1:
- Choreography Types of template rely IP pool Pool IP list or IP start and step size no VLAN pool Pool VLAN ID initial and step size IP pool SG Pool Pool SMARTGROUP ID initial and step size no LACP protocol LACP template SG pool, topology VLAN protocol VLAN template VLAN pool, LACP LOOPBACK protocol LOOPBACK template IP pool I protocol I template VLAN, LOOPBACK
- the orchestration template defines the orchestration fields of the protocol, including at least the dependent pool parameters and global parameters.
- the orchestration template is orchestrated based on the user's primary parameters, and the details are as follows:
- the parameter orchestrator generates a LOOPBACK template, and imports the ippool based on the chain:
- the parameter orchestrator generates a LACP template, and the dependency chain is imported into the VLAN (that is, the VLAN depends on LACP).
- the parameter sgmode, ifmode, and so on depend on the pool sgpool as follows:
- the parameter orchestrator generates a VLAN template, the dependency chain includes at least vlanpool, the parameterized mode, mtu, and description, and the dependency chain outputs name. It can be seen that the VLAN template depends on the pool vlanpool:
- the parameter orchestrator generates an I template, which depends on the VLAN (imported through intf.vlan), depends on LOOPBACK (through intf.loopback), and parameterizes max_lsp_lifetime, metric_style, is_type.
- the pool parameters depend on Ipool, and the allocation includes at least area and systemid. Examples are as follows:
- FIG. 5 is a schematic diagram of another dependency relationship chain according to an optional embodiment of the present disclosure.
- the VRF orchestration dependency The chain is: VRF ⁇ LOOPBACK ⁇ LACP ⁇ VLAN ⁇ I.
- Table 2 is the specific explanation of each orchestration item in the dependency relationship shown in Figure 5, as shown in Table 2:
- Choreography Types of template rely IP pool Pool IP list or IP start and step size no VLAN pool Pool VLAN ID initial and step size IP pool SG Pool Pool SMARTGROUP ID initial and step size no LACP protocol LACP template SG pool, topology VLAN protocol VLAN template VLAN pool, LACP, VRF LOOPBACK protocol LOOPBACK template IP pool, VRF I protocol I template VLAN, LOOPBACK, VRF VRF protocol VRF template Topology
- step S22 obtaining the network topology includes at least the following execution steps:
- Step S227 Obtain a neighbor relationship between various devices in the network, where the neighbor relationship includes at least: device information and port information of each port connected to each device.
- the neighbor relationship further includes: a network role of each device in the network and a neighbor model between neighboring devices.
- Network topology is used to describe the neighbor relationship between nodes in the network.
- the neighbor relationship includes: device information of the corresponding device connected to each port of the device in the network and information of the connected port.
- the neighbor relationship may also include a neighbor model, that is, a network role of the device and a neighbor model between the devices.
- Network topology is a neutral description of the network topology. It has nothing to do with the specific device type or device manufacturer, and it has nothing to do with the specific description format and storage.
- the method for generating a network topology may adopt a neighbor discovery protocol based on LLDP. That is, first log in to the device according to the Internet Protocol (IP) and other information, and view the LLDP information of the device, including but not limited to: the device itself, the peer device, and the connection port; then analyze the topology of the entire network by aggregating LLDP information And the relationships and roles between nodes.
- IP Internet Protocol
- the method for generating a network topology may use a graphic-based method to draw devices and make port connections to identify specific port numbers, device IPs, user names, and passwords, and identify them graphically. The relationship and role of the nodes, so as to get the topology of the entire network.
- an LLDP-based topology generation method and a graphical-based topology generation method are used in combination to ensure the correctness of the network topology structure.
- the topology generation method may be used as an example to dynamically discover the network topology based on LLDP for further explanation.
- the topology generation method may include:
- the device information to be deployed including at least: device IP address, login user name and password, device type, and role.
- the manner of using the IP address list is as follows:
- Neighbor topology discovery read the list of devices to be deployed, and generate device neighbor relationships.
- the neighbor relationship includes the device information of the corresponding device connected to each port of the device and the information of the connected port.
- aggregation switch 1 Take aggregation switch 1 as an example. , Specific examples are as follows:
- Neighbor relationship the neighbor relationship of the above-mentioned Spine-leaf network topology, including but not limited to up-link (in a point-to-multipoint system, a transmission link from a distributed point to a centralized point) model, peer-to-peer link (peer-link) model.
- up-link in a point-to-multipoint system, a transmission link from a distributed point to a centralized point
- peer-link peer-to-peer link
- the up-link model represents the spine-leaf node relationships in the spine-leaf topology, such as the relationship between spine-1 and leaf-1.
- the peer-link model represents leaf-leaf node relationships in the spine-leaf topology, such as the relationship between leaf-1 and leaf-2.
- the network orchestration is initialized, the dependency chain is configured, and the network topology is generated.
- the preparation of the network orchestration is completed, and the orchestration can be started below.
- step S24 network protocol orchestration is performed according to the network orchestration parameters, the dependency relationship chain, and the network topology.
- Generating network configuration information may include the following execution steps:
- Step S241 selecting a device to be scheduled from the network topology
- Step S242 Read the neighbor relationship of the device to be scheduled
- Step S243 traverse all the neighbor devices according to the neighbor relationship, and perform port connection orchestration for the orchestration device and the neighbor device for each traversal respectively;
- step S244 it is determined whether there are devices that have not been scheduled in the network topology. If so, the process returns to step S241, and if not, network configuration information is generated.
- FIG. 6 is a flowchart of a network orchestration process according to an optional embodiment of the present disclosure. As shown in FIG. 6, the process may include the following execution steps:
- Step S602 selecting a device to be scheduled from the network topology
- a spine-1 aggregation switch in the network topology is selected as a fulcrum, and the neighbor relationship is read to obtain all the neighbor relationships of the fulcrum, including leaf-1 and leaf-2, and then the neighbor relationship is used for orchestration. .
- Step S604 Read a neighbor device of the device to be scheduled according to the neighbor relationship of the device to be scheduled;
- step S606 it is determined whether the neighbor device has been scheduled, and if so, the process returns to step S604; if not, the process continues to step S608;
- Step S608 orchestrating a port connection between the device to be orchestrated and the neighbor device
- the port connection between the spine-1 device to be scheduled and the neighbor device leaf-1 needs to be scheduled.
- Step S6081 reading the neighbor relationship of the device to be scheduled
- Step S6082 read the protocol dependency relationship chain and orchestration parameters
- the arrangement is performed according to the up-link model, and the protocol dependency chain is read, that is, the arrangement is performed according to LOOPBACK ⁇ LACP ⁇ VLAN ⁇ I.
- Step S6083 Read the start protocol of the protocol dependency chain
- orchestrate LOOPBACK refer to the orchestration template of LOOPBACK, and its dependency is ippool.
- Step S6084 network orchestration is performed according to the orchestrator of the protocol
- IP address from the ip pool, that is, ip.service.loopback1, and replace the LOOPBACK template.
- Step S6085 it is judged whether there is an unscheduled agreement in the protocol dependency chain, and if so, step S6086 is continued; if not, step S608 is performed;
- Step S6086 Read the next protocol to be scheduled in the protocol dependency chain, and go to step S6084.
- LACP its dependencies are the neighbor topology and the sg pool.
- a smartgroupID from the sg pool, and obtain the egress ports xgei-0 / 1/1/22 and xgei- from spine-1 to leaf-1. 0/1/1/24, orchestrating the lacp group of spine-1, and obtaining the egress ports of leaf-1 to spine-1 xgei-0 / 1/1/2, xgei-0 / 1/1/4, orchestrating leaf Lacp group of -1. And so on, until all protocol orchestration in the protocol dependency chain is closed.
- step S610 it is determined whether there are neighbor nodes, if yes, go to step S604, and if no, continue to step S612;
- step S612 it is determined whether there are devices that have not been scheduled. If yes, go to step S602. If no, the network protocol scheduling is completed.
- step S243 all the neighbor devices are traversed according to the neighbor relationship, and the port connection orchestration of the orchestration device and the neighbor device for each traversal may include the following execution steps:
- Step S2431 traverse all the protocols of the protocol relationship chain starting from the initial protocol on the protocol relationship chain;
- Step S2432 For each protocol, perform port connection orchestration for the orchestration device and the neighbor device for each traversal according to the orchestration template corresponding to the current protocol until all protocol orchestration is completed.
- the port connection orchestration includes reading the protocol relationship chain and orchestration parameters, and then traversing all the protocols on the relationship chain starting from the starting protocol. For each protocol, selecting the template of the protocol to orchestrate on the selected node and neighboring nodes, and output the orchestration. content.
- orchestration process For a specific orchestration process, reference may be made to the orchestration example provided in the process shown in FIG. 6 above, which will not be repeated here.
- step S2432 performing port connection orchestration to the orchestration device and the neighbor device for each traversal according to the orchestration template corresponding to the current protocol may include the following execution steps:
- Step S24321 analyzing the current protocol according to the orchestration template corresponding to the current protocol to obtain a parse field
- Step S24322 Determine the value of the pool parameter corresponding to the parse field from the allocation range defined by the pool parameter, and replace the value of the global parameter corresponding to the parse field with a predefined value of the global parameter.
- Orchestration refers to the analysis of the protocol orchestration template. For pool parameters, you need to apply for relevant values from the pool parameter pool; for global parameters, you need to replace the values defined by the global parameters; and finally assemble or synthesize the orchestration content (equivalent to the above network) Configuration information). Orchestration content is independent of the device type and specific manufacturer's product, and is a neutral organization structure for protocol description.
- a spine-1 aggregation switch in the network topology is selected as a fulcrum, and the neighbor relationship is read to obtain all the neighbor relationships of the fulcrum, including leaf-1 and leaf-2, and then the neighbor relationship is used for orchestration. .
- leaf-1 and leaf-2 Because the neighbor relationship between spine-1, leaf-1, and leaf-2 is an up-link model, it can be arranged according to the up-link structure. Because leaf-1 and leaf-2 have a direct connection and are peer-link models, they can be arranged according to the peer-link structure.
- orchestration is performed according to up-link, and the protocol dependency chain is read, that is, the orchestration is performed according to LOOPBACK ⁇ LACP ⁇ VLAN ⁇ I.
- the specific orchestration process is as follows:
- Orchestration LOOPBACK refer to the orchestration template of LOOPBACK, and its dependency is ippool. Assign an IP address from the ip pool, namely ip.service.loopback1, and replace the LOOPBACK template to get the following arrangement:
- the orchestrator outputs the lacp group of leaf-1 as follows:
- VLAN dependencies are the VLAN pool and LACP.
- VLAN orchestration template assign an ID 101 from the VLAN pool, and spinner-1 LACP (smartgroup33) joins the VLAN.
- spinner-1 LACP (smartgroup33) joins the VLAN.
- the output is as follows:
- LACP (smartgroup3) of leaf-1 is added to the VLAN.
- An example of the output of the orchestrator is as follows:
- the orchestrator generates leaf-1 configuration as follows:
- an orchestration of a storage plane is newly added, which includes the storage plane using VRF isolation.
- VLANs that is, vlan101 and lan1101, as listed above:
- sending the network configuration information to the device in step S26 may include the following execution steps:
- step S261 the network configuration information is parsed into a message recognizable by the device according to the requirements of the delivery channel;
- step S262 the identifiable message obtained after analysis is sent to the device.
- the orchestration content is a neutral organization structure. When it is delivered to a manufacturer's device, it needs to be analyzed once to adapt to the specific device. Parsing can be based on the requirements of the delivery channel, such as: Remote Terminal Protocol (TELNET), Secure Shell Protocol (SSH), or Extensible Markup Language-based Network Configuration Protocol (NETCONF). After parsing, relevant device-identifiable packets are constructed. Packets are delivered to the device through the channel to complete network deployment. At this point, the basic layout of the dependency chain is installed and the underlay foundation (business side) network of the data center is constructed.
- TELNET Remote Terminal Protocol
- SSH Secure Shell Protocol
- NETCONF Extensible Markup Language-based Network Configuration Protocol
- sending the network configuration information to the device may further include the following execution steps:
- step S263 the processes of network protocol orchestration, network configuration information analysis, and network configuration information distribution are detected, and a detection log is generated.
- the orchestration content is delivered to the device, self-tests can be used to verify the correctness of the entire process from orchestration to parsing, and then to the release of the device, and a log is provided.
- the orchestrator output and delivery provide a parallel mechanism to speed up deployment efficiency.
- FIG. 4 and FIG. 5 are developed from an implementation level, and generally include the five steps of initializing orchestration parameters, configuring a dependency chain, generating a network topology, orchestrating, and issuing. The following will introduce how to quickly deploy the network from the application level.
- an example of a user-defined primary orchestration parameter is as follows:
- loopback1 10.30.0.1 / 32
- loopback2 10.30.1.1 / 32
- loopback3 10.325.1 / 32
- the generation of the pool parameter relationship chain and protocol relationship dependency chain is completed, the network topology is generated using the LLDP method, and the network orchestration is performed based on the topology discovered by LLDP, and then issued Orchestrate content to automate the entire deployment process.
- the implementation process of the above-mentioned optional embodiment is combined with a specific commercial data center switch and is arranged based on a specific network protocol (for example, a LACP + VLAN + I protocol chain).
- a specific network protocol for example, a LACP + VLAN + I protocol chain.
- the technical solutions provided caused improper restrictions.
- protocol orchestration is added during the implementation process, for example, the routing protocol enables Open Shortest Path First (OSPF), it does not exceed the protection scope of the technical solution provided by the present disclosure.
- OSPF Open Shortest Path First
- the method according to the above embodiments can be implemented by means of software plus a necessary universal hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
- the technical solution of the present disclosure that is essentially or contributes to the existing technology can be embodied in the form of a software product that is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in the embodiments of the present disclosure.
- a network deployment device is also provided in this embodiment, and the device is used to implement the foregoing embodiments and preferred implementation manners, and the descriptions will not be repeated.
- the term "module” may implement a combination of software and / or hardware for a predetermined function.
- the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and conceived.
- FIG. 7 is a structural block diagram of a network deployment device according to an embodiment of the present disclosure.
- the device includes a network orchestration module 10 configured to obtain network orchestration parameters, a dependency relationship chain, and a network topology, wherein the dependency relationship chain
- a network orchestration module 10 configured to obtain network orchestration parameters, a dependency relationship chain, and a network topology, wherein the dependency relationship chain
- Each protocol node in the pre-configured corresponding orchestration template, the orchestration template is used to describe the parameter information that each protocol node depends on; and the network protocol orchestration is generated according to the network orchestration parameters, dependency chain and network topology to generate network configuration information ;
- a delivery module 20 configured to deliver network configuration information to the device.
- the network orchestration module 10 includes a first obtaining unit (not shown in the figure) configured to obtain protocol parameters, where the protocol parameters include at least: a protocol to be configured on the network and a protocol to be configured with Associated configuration parameters and global parameters; the second acquisition unit (not shown in the figure) is configured to obtain the orchestration parameters, where the acquisition orchestration parameters include at least: the acquisition of primary parameters, which are simplified for the overall network structure Representative parameters.
- the second obtaining unit (not shown in the figure) is further configured to obtain advanced parameters, where the advanced parameters are parameters obtained by orchestrating the primary parameters.
- the second obtaining unit (not shown in the figure) is further configured to obtain a pool parameter, where the pool parameter is used to limit an allocation range of the parameter value.
- the network orchestration module 10 includes a third obtaining unit (not shown in the figure) configured to obtain a protocol relationship chain, where the protocol relationship chain is used to describe each of the protocols to be configured on the network.
- the dependency relationship between the protocols; the fourth obtaining unit (not shown in the figure) is configured to obtain a pool parameter relationship chain, wherein the pool parameter relationship chain is used to describe each pool parameter among the pool parameters to be used on the network.
- the fifth obtaining unit (not shown in the figure) is configured to obtain the dependency relationship between the protocol relationship chain and the pool parameter relationship chain, so that the pool parameter relationship chain is used to assign values to the parameters in the protocol relationship chain.
- the network orchestration module 10 further includes: a establishing unit (not shown in the figure), configured to establish a corresponding relationship according to the obtained dependency relationship chain, wherein the corresponding relationship includes a plurality of orchestration items and The type, orchestration template, and dependencies for each orchestration item.
- a establishing unit (not shown in the figure), configured to establish a corresponding relationship according to the obtained dependency relationship chain, wherein the corresponding relationship includes a plurality of orchestration items and The type, orchestration template, and dependencies for each orchestration item.
- the network orchestration module 10 includes: a sixth obtaining unit (not shown in the figure), configured to obtain a neighbor relationship between various devices in the network, wherein the neighbor relationship includes at least: Device information and port information connected to each port.
- the neighbor relationship further includes: a network role of each device in the network and a neighbor model between neighboring devices.
- the network orchestration module 10 includes: a selection unit (not shown in the figure) configured to select a device to be orchestrated from a network topology; and a reading unit (not shown in the figure) configured to read the Orchestration relationship of orchestration devices; orchestration unit (not shown in the figure) is set to traverse all neighbor devices according to the neighbor relationship, and arrange the port connection orchestration of the orchestration device and the neighbor device for each traversal respectively; judgment unit (not shown in the figure) ), It is set to determine whether there is a device that has not been scheduled in the network topology. If it is, the selection unit is returned, and if not, network configuration information is generated.
- the orchestration unit (not shown in the figure) includes: a traversal subunit (not shown in the figure), which is set to traverse all the protocols of the protocol relationship chain starting from the initial agreement on the protocol relationship chain ; Orchestration subunit (not shown in the figure), which is set for each protocol and performs port connection orchestration for the orchestration device and the neighbor device for each traversal according to the orchestration template corresponding to the current protocol until all the protocol orchestration is completed.
- the orchestration subunit (not shown in the figure) is configured to parse the current protocol according to the orchestration template corresponding to the current protocol to obtain a parsing field; and determine the parsing from the allocation range defined by the pool parameters The value of the pool parameter corresponding to the field, and the value of the global parameter corresponding to the parse field is replaced with a predefined value of the global parameter.
- the delivery module 20 includes: a parsing unit (not shown in the figure), configured to parse the network configuration information into a message recognizable by the device according to the requirements of the delivery channel; (Not shown in the figure), it is set to send the identifiable message obtained after analysis to the device.
- a parsing unit (not shown in the figure), configured to parse the network configuration information into a message recognizable by the device according to the requirements of the delivery channel; (Not shown in the figure), it is set to send the identifiable message obtained after analysis to the device.
- the delivery module 20 further includes: a detection unit (not shown in the figure), configured to detect a process of orchestrating network protocols, analyzing network configuration information, and issuing network configuration information, and generate a detection Log.
- a detection unit (not shown in the figure), configured to detect a process of orchestrating network protocols, analyzing network configuration information, and issuing network configuration information, and generate a detection Log.
- each of the above modules can be implemented by software or hardware.
- it can be implemented by the following methods, but is not limited to this: the above modules are all located in the same processor; or the above modules are arbitrarily combined The forms are located in different processors.
- An embodiment of the present disclosure further provides a storage medium that stores a computer program therein, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
- the foregoing storage medium may be configured to store a computer program for performing the following steps:
- Each protocol node in the dependency relationship chain is pre-configured with a corresponding orchestration template, and the orchestration template is used to describe parameter information that each protocol node depends on.
- the network configuration information is delivered to the device.
- the storage medium is further configured to store a computer program for performing the following steps:
- protocol parameters include at least: a protocol to be configured on the network, and configuration parameters and global parameters associated with the protocol to be configured;
- Obtaining orchestration parameters where obtaining the orchestration parameters includes at least: obtaining primary parameters, and the primary parameters are representative parameters that are simplified for the overall structure of the network.
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- pool parameter relationship chain where the pool parameter relationship chain is used to describe the mutual relationship between each pool parameter among the pool parameters to be used on the network;
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- S4 Determine whether there are devices that have not been scheduled in the network topology. If yes, return to S1; if not, generate network configuration information.
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- the storage medium is further configured to store a computer program for performing the following steps:
- S1 Detect the process of network protocol orchestration, network configuration information analysis, and network configuration information distribution, and generate a detection log.
- the foregoing storage medium may include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (Random Access Memory, RAM), A variety of media that can store computer programs, such as removable hard disks, magnetic disks, or optical disks.
- ROM read-only memory
- RAM Random Access Memory
- An embodiment of the present disclosure further provides an electronic device including a memory and a processor.
- the memory stores a computer program
- the processor is configured to run the computer program to perform the steps in any one of the foregoing method embodiments.
- the electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the processor, and the input-output device is connected to the processor.
- the foregoing processor may be configured to execute the following steps by a computer program:
- Each protocol node in the dependency relationship chain is pre-configured with a corresponding orchestration template, and the orchestration template is used to describe parameter information that each protocol node depends on.
- the network configuration information is delivered to the device.
- the foregoing processor may be further configured to execute the following steps through a computer program:
- protocol parameters include at least: a protocol to be configured on the network, and configuration parameters and global parameters associated with the protocol to be configured;
- Obtaining orchestration parameters where obtaining the orchestration parameters includes at least: obtaining primary parameters, and the primary parameters are representative parameters that are simplified for the overall structure of the network.
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- pool parameter relationship chain where the pool parameter relationship chain is used to describe the mutual relationship between each pool parameter among the pool parameters to be used on the network;
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- S4 Determine whether there is a device that has not been scheduled in the network topology. If yes, return to S1; if not, generate network configuration information.
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- the foregoing processor may be further configured to execute the following steps through a computer program:
- S1 Detect the processes of network protocol orchestration, network configuration information analysis, and network configuration information distribution, and generate a detection log.
- modules or steps of the present disclosure may be implemented by a general-purpose computing device, and they may be centralized on a single computing device or distributed on a network composed of multiple computing devices Above, optionally, they may be implemented with program code executable by a computing device, so that they may be stored in a storage device and executed by the computing device, and in some cases, may be in a different order than here
- the steps shown or described are performed, or they are separately made into individual integrated circuit modules, or multiple modules or steps in them are made into a single integrated circuit module for implementation.
- the present disclosure is not limited to any particular combination of hardware and software.
- the network deployment method and device provided by the embodiments of the present invention have the following beneficial effects: the problems of high operation complexity and low fault tolerance rate of the network deployment methods provided in related technologies are solved,
- the dependency relationship chain reduces the operational complexity of the network deployment and configuration process, and is more conducive to the automatic deployment and rapid delivery of the basic network of a large data center.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本公开提供了一种网络部署方法及装置。该方法包括:获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;将网络配置信息下发至设备。通过本公开,解决了相关技术中所提供的网络部署方式操作复杂度较高、容错率较低的问题,达到通过建立的依赖关系链,降低网络部署配置过程的操作复杂度,更有助于大型数据中心基础网络的自动部署和快速交付。
Description
本公开涉及互联网领域,具体而言,涉及一种网络部署方法及装置。
目前,数据中心的建设日趋集中,网络规模越来越大,上万台甚至超十万台的数据中心愈发普及。网络部署已经逐步成为数据中心快速交付的瓶颈问题。该问题主要表现在网络规模大、手工部署效率低且容易出错、出现故障排查难、交付周期长、运行维护成本高。为此,相关技术中提出多种自动化的网络部署方式。
方式一、基于模板进行设备配置。即,预先为零配置设备创建启动配置模板。在零配置设备完成初始配置之后,根据设备类型信息查找对应的启动配置模板部署到零配置设备,进而通过运行该启动配置模板,以使零配置设备完成自动配置。
方式二、基于拓扑进行设备配置。即,根据保存的设备的配置信息下发链路层发现协议(LLDP)报文并收集网络拓扑。其次,基于网络拓扑对设备进行堆叠配置,以得到简化的网络拓扑。然后,继续对简化的网络拓扑中的设备进行其他协议配置,以完成网络的配置。
方式三、基于身份进行设备配置。即,获取当前设备的设备信息和邻居关系,以便根据当前设备的设备信息和邻居关系对当前设备进行身份识别,进而根据识别出的设备身份对当前设备进行配置。
方式四、基于邻居进行设备配置。即,待部署设备通过访问邻居,获取邻居的预设描述,以生成配置信息。然后,根据配置信息从预设服务器中下载对应的预设配置文件,并自动启动运行该预设配置文件,由此完成待部署设备的配置。
综合上述介绍,虽然上述方式均可实现设备的自动部署但是仍处于理 论研究阶段。因此,在自动部署准备阶段还存在诸多问题(包括但不限于:模板如何自动生成、配置文件如何自动生成,根据邻居或身份识别如何具体生成配置信息,缺乏具体的实现方案。
不仅如此,虽然上述自动部署从触发开始可以完成快速的、大量的部署,但是,自动化触发前的准备阶段却是非常消耗人力并且容易出错的。而且,鉴于上述配置方案缺少在部署前的整体网络规划,一旦发现某个设备由于前期的配置生成有误,可能需要推倒重新部署。
发明内容
本公开至少部分实施例提供了一种网络部署方法及装置,以至少解决相关技术中所提供的网络部署方式操作复杂度较高、容错率较低的问题。
根据本公开的一个实施例,提供了一种网络部署方法,包括:获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;将网络配置信息下发至设备。
根据本公开的另一个实施例,提供了一种网络部署装置,包括:网络编排模块,设置为获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;以及根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;下发模块,设置为将网络配置信息下发至设备。
根据本公开的又一个实施例,还提供了一种网络部署设备,该网络部署设备包括:网络编排模块,设置为获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;以及根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;下发模块,设置为将网络配置信息下发至设备。
根据本公开的又一个实施例,还提供了一种存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例,还提供了一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开至少部分实施例,采用获取到的网络编排参数,依赖关系链以及网络拓扑,在网络部署前进行整体网络规划,简化网络部署过程并自动化生成网络配置信息、减少人工参与,进而将网络配置信息再下发至生产厂商的设备当中。因此,可以解决相关技术中所提供的网络部署方式操作复杂度较高、容错率较低的问题,达到通过建立的依赖关系链,降低网络部署配置过程的操作复杂度,更有助于大型数据中心基础网络的自动部署和快速交付。
此处所说明的附图用来提供对本公开的进一步理解,构成本申请的一部分,本公开的示意性实施例及其说明用于解释本公开,并不构成对本公开的不当限定。在附图中:
图1是本公开实施例的一种网络部署方法的计算机终端的硬件结构框图;
图2是根据本公开其中一实施例的网络部署方法的流程图;
图3是根据本公开其中一可选实施例的组网逻辑示意图;
图4是根据本公开其中一可选实施例的一种依赖关系链的示意图;
图5是根据本公开其中一可选实施例的另一种依赖关系链的示意图;
图6是根据本公开其中一可选实施例的网络编排过程的流程图;
图7是根据本公开实施例的网络部署装置的结构框图。
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是,本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例,图1是本公开实施例的一种网络部署方法的计算机终端的硬件结构框图。如图1所示,计算机终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和设置为存储数据的存储器104,可选地,上述计算机终端还可以包括设置为通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解,图1所示的结构仅为示意,其并不对上述计算机终端的结构造成限定。例如,计算机终端还可包括比图1中所示更多或者更少的组件,或者具有与图1所示不同的配置。
存储器104可设置为存储计算机程序,例如,应用软件的软件程序以及模块,如本公开实施例中的网络部署方法对应的计算机程序,处理器102通过运行存储在存储器104内的计算机程序,从而执行各种功能应用以及数据处理,即实现上述的网络部署方法。存储器104可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器104可进一步包括相对于处理器102远程设置的存储器,这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具 体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中,传输装置106包括一个网络适配器(Network Interface Controller,简称为NIC),其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中,传输装置106可以为射频(Radio Frequency,简称为RF)模块,其设置为通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述计算机终端的网络部署方法,图2是根据本公开其中一实施例的网络部署方法的流程图,如图2所示,该流程包括如下步骤:
步骤S22,获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;
步骤S24,根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;
步骤S26,将网络配置信息下发至设备。
通过上述步骤,解决了相关技术中所提供的网络部署方式操作复杂度较高、容错率较低的问题,达到通过建立的依赖关系链,降低网络部署配置过程的操作复杂度,更有助于大型数据中心基础网络的自动部署和快速交付。
可选地,上述步骤的执行主体可以为终端等,但不限于此。
上述依赖关系链中的协议节点是指网络上多个待配置的协议,其中,一种协议需要依赖于另外一种协议来完成特定的网络功能,并通过协议间依赖关系建立起构成依赖关系链一部分的协议关系链。上述每个协议节点所依赖的参数信息可以包括但不限于:每个协议节点所依赖的池参数和全局参数。
在一个可选实施例中,在步骤S22中,获取网络编排参数可以包括以下执行步骤:
步骤S221,获取协议参数,其中,协议参数至少包括:网络上待配 置的协议以及与待配置协议关联的配置参数和全局参数;
步骤S222,获取编排参数,其中,获取编排参数至少包括以下执行步骤:
步骤S2221,获取初级参数,初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
协议参数是指网络上待配置的协议以及协议的配置参数,全局参数等。编排参数至少包括:初级参数,其是指面向网络整体结构的、简化的、具有代表性的参数。
在一个可选实施例中,虚机化数据中心(Virtual Data Center,简称为VDC)的网络结构,可以分为传统单层网络(underlay)以及构建在underlay网络之上的叠加的逻辑网络(overlay)等。underlay网络是基础网络,用于承载用户业务的IP网络。而overlay网络则是在underlay网络上通过虚机化技术构建的逻辑网络。下面以VDC的underlay网络为例实施部署。
图3是根据本公开其中一可选实施例的组网逻辑示意图,如图3所示,underlay网络采用Spine-Leaf拓扑结构,承载service业务面。部署要求包括接入交换机堆叠实现主备,接入交换机上联到汇聚交换机,配置协议包括但不限于:链路聚合控制协议(LACP),虚拟局域网(VLAN),中间***到中间***(Intermediate System to Intermediate System,以下简称为I协议),并实现三层互通。该可选实施例的具体实施过程如下:
初始化网络编排可以包括:设定协议参数和编排参数。协议参数可以包括:协议的配置参数和协议的全局参数。编排参数至少可以包括:初级参数。
初级参数是指面向网络整体结构的、简化的、具有代表性的参数。在通常情况下,如果用户设置初级编排参数,便可以实现网络的编排。以下为编排网络的初级参数的示例:
[service]
loopback1=10.30.0.1/32
loopback2=10.30.1.1/32
vlanid=101:200
vlanip=10.30.3.2/30
router=I
其中,vlanid=101、vlanip=10.30.3.2/30,由此定义了一个vlan分配。标识初始值为101,vlan ip采用步长分配方式,依次分配为:10.30.3.2/30,10.30.3.6/30,10.30.3.10/30,...。此外,还定义了路由协议I,以及定义了两个loopback(ip地址采用步长分配方式),加入路由通告接口。
在另一个可选实施例中,一个数据中心的Spine-Leaf网络配置underlay网络,同时承载service业务面和store存储面,即数据中心的业务和存储共用一张underlay基础网络。store存储面需要有VRF隔离,链路聚合组加入不同VLAN。与前一个可选实施例不同,在该可选实施例中,设计编排器的概要参数,underlay网络承载service业务面和store存储面,其中,存储面使用VRF隔离,具体示例如下:
[service]
loopback1=10.30.0.1/32
loopback2=10.30.1.1/32
vlanid=101:200
vlanip=10.30.3.2/30
router=I
[store]
vrf=store
loopback3=10.30.25.1/32
vlanid=1101:200
vlanip=10.30.26.2/30
router=I
在一个可选实施例中,在步骤S222中,获取编排参数还可以包括以下执行步骤:
步骤S2222,获取高级参数,其中,高级参数是通过对初级参数进行编排得到的参数。
可选的,编排参数还可以包括:高级参数,其是指通过对初级参数进行编排(即参数编排器)得到的参数。高级参数更加全面,并且面向配置的协议,支持用户设置的参数。参数编排器是指对初级参数进行细化处理,以生成更加全面的高级参数的过程。该过程将结合下文中提到的依赖关系链的配置过程作进一步展开描述。
在一个可选实施例中,在步骤S2222中,获取高级参数至少包括以下执行步骤:
步骤S22221,获取池参数,其中,池参数用于限定参数取值的分配范围。
池参数是指一个分配范围,提供按列表和按初始值加步长的方式定义参数。
在一个可选实施例中,在步骤S22中,获取依赖关系链可以包括以下执行步骤:
步骤S223,获取协议关系链,其中,协议关系链用于描述网络上待配置的协议中每种协议相互间的依赖关系;
步骤S224,获取池参数关系链,其中,池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;
步骤S225,获取协议关系链与池参数关系链之间的依赖关系,以使池参数关系链为协议关系链中的参数进行取值分配。
依赖关系是指一种配置项需要依赖另外一种配置项来完成特定的功能。依赖关系链是指多个配置项通过依赖关系建立起来的关系链。
依赖关系链可以包括:协议关系链和池参数关系链。协议关系链是指一种协议需要依赖另外一种协议来完成特定的网络功能,并通过协议间依赖关系建立起协议关系链。池参数关系链是指一种池参数的分配依赖另外一种池参数。此外,协议关系链需要同时依赖池参数关系链,以完成协议关系链中协议参数的值分配。
图4是根据本公开其中一可选实施例的一种依赖关系链的示意图,如图4所示,协议关系链定义了本地环回接口(LOOPBACK)、LACP、VLAN、I协议。协议关系可以解释为:如果链路加入聚合组LACP以实现连接可靠性、负载均衡或动态链路备份,则链路是聚合组LACP的依赖。如果聚合组LACP加入VLAN实现网络隔离,则聚合组LACP是VLAN划分的依赖。如果VLAN或者LOOPBACK加入I路由通告接口,则VLAN或LOOPBACK是I的依赖。
池参数关系链定义了Sg池、IP池、VLAN池、I池。通过使用参数编排器,可以对用户参数进行编排,得到高级参数。该高级参数可以包括:
(1)用户参数编排生成的IP池,其中,name是池参数依赖或者协议关系依赖的导入项,编排输出如下:
(2)用户参数编排生成的vlan池,依赖链包括ippool,并通过ippool的导入,同时vlan依赖链也输出name项。在Spine-Leaf组网中,存在两个Spine节点,每个Spine网络的vlan独立分配,所以编排输出如下:
(3)池参数关系链的Sg池负责LACP SMARTGROUP的ID分配、I池负责systemid分配等,此处不再详述。
在一个可选实施例中,在步骤S22中,获取依赖关系链还可以包括以下执行步骤:
步骤S226,根据获取到的依赖关系链建立对应关系,其中,对应关系包括:多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
协议关系链上的每个协议定义了一个编排模板。编排模板定义了协议的编排字段,包括:依赖的池参数和全局参数。编排模板还定义了一个类型,关系链上编排项可以是池,也可以是协议。即一个编排项=类型+模板+依赖。
表1为图4的依赖关系链中各个编排项的解释说明,如表1所示:
表1
编排项 | 类型 | 模板 | 依赖 |
IP池 | 池 | IP列表或者IP起始及步长 | 无 |
VLAN池 | 池 | VLAN ID初始及步长 | IP池 |
SG池 | 池 | SMARTGROUP ID初始及步长 | 无 |
LACP | 协议 | LACP模板 | SG池,拓扑 |
VLAN | 协议 | VLAN模板 | VLAN池,LACP |
LOOPBACK | 协议 | LOOPBACK模板 | IP池 |
I | 协议 | I模板 | VLAN,LOOPBACK |
上述协议关系链上的每个协议还定义一个编排模板。编排模板定义了协议的编排字段,至少包括依赖的池参数和全局参数。并且,编排模板是基于用户初级参数编排的,具体说明如下:
(1)参数编排器生成LOOPBACK模板,依赖链导入ippool:
(2)参数编排器生成LACP模板,依赖链导入到VLAN(即VLAN依赖LACP),参数化sgmode、ifmode等,依赖池sgpool,如下:
(3)参数编排器生成VLAN模板,依赖链至少包括vlanpool,参数化mode、mtu、description,依赖链输出name。由此可以看出,VLAN模板依赖池vlanpool:
(4)参数编排器生成I模板,依赖VLAN(通过intf.vlan导入),依赖LOOPBACK(通过intf.loopback),参数化max_lsp_lifetime、metric_style、is_type,池参数依赖Ipool,分配至少包括area、systemid,具体示例如下:
此外,针对数据中心的业务和存储共用一张underlay基础网络而言,图5是根据本公开其中一可选实施例的另一种依赖关系链的示意图,如图5所示,VRF的编排依赖链是:VRF→LOOPBACK→LACP→VLAN→I,表2为图5所示的依赖关系中各个编排项的具体解释说明,如表2所示:
表2
编排项 | 类型 | 模板 | 依赖 |
IP池 | 池 | IP列表或者IP起始及步长 | 无 |
VLAN池 | 池 | VLAN ID初始及步长 | IP池 |
SG池 | 池 | SMARTGROUP ID初始及步长 | 无 |
LACP | 协议 | LACP模板 | SG池,拓扑 |
VLAN | 协议 | VLAN模板 | VLAN池,LACP,VRF |
LOOPBACK | 协议 | LOOPBACK模板 | IP池,VRF |
I | 协议 | I模板 | VLAN,LOOPBACK,VRF |
VRF | 协议 | VRF模板 | 拓扑 |
在一个可选实施例中,在步骤S22中,获取网络拓扑至少包括以下执行步骤:
步骤S227,获取网络中各个设备之间的邻居关系,其中,邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
在一个可选实施例中,邻居关系还包括:网络中每个设备的网络角色以及相邻设备之间的邻居模型。
网络拓扑用于描述网络中节点之间的邻居关系。该邻居关系包括:分别与网络中设备每个端口相连的对应设备的设备信息和相连端口的信息。
该邻居关系除了包括设备及端口的连接关系,还可以包括:邻居模型,即设备的网络角色及设备间的邻居模型。
网络拓扑是一种中性的网络拓扑描述,与具体的设备类型或设备厂商没有关系,与具体的描述格式与存储也没有关系。
在一个可选实施例中,网络拓扑生成方法,可以采用基于LLDP的邻居发现协议。即,首先根据互联网协议(IP)等信息登录到设备上,查看设备的LLDP信息,包括但不限于:设备本身、对端设备、连接端口;然后,通过汇聚LLDP信息分析出整个网络的拓扑结构以及节点之间的关系和角色。
在另一个可选实施例中,网络拓扑生成方法,可以采用基于图形化方法绘制设备并进行端口连接,以标识出具体的端口号、设备IP、用户名和密码等信息,并在图形上标识出节点的关系和角色,从而得出整个网络的拓扑结构。
在另一个可选实施例中,相互结合使用基于LLDP的拓扑生成方法与基于图形化的拓扑生成方法,以保证网络拓扑结构的正确性。
下面将通过拓扑生成方法可以是基于LLDP动态发现的网络拓扑为例做进一步解释说明,拓扑生成方法可以包括:
(1)配置待部署设备信息,至少包括:设备IP地址,登录用户名和密码,设备类型,角色。在一个可选实施例中,采用IP地址列表方式如下:
[devices]
173.18.101.200=role:spine,username:who,password:who,hostname:spine-1
173.18.101.1=role:leaf,username:who,password:who
173.18.101.2=role:leaf,username:who,password:who
173.18.102.200=role:spine,username:who,password:who,hostname:spine-2
173.18.102.1=role:leaf,username:who,password:who
173.18.102.2=role:leaf,username:who,password:who
(2)邻居拓扑发现,读取待部署列表设备(devices),生成设备邻居关系,邻居关系包括分别与设备每个端口相连的对应设备的设备信息和相连端口的信息,以汇聚交换机1为例,具体示例如下:
(3)邻居关系,上述Spine-leaf的网络拓扑的邻居关系,包括但不限 于up-link(在点到多点***中,由分散点到集中点的传输链路)模型,对等链路(peer-link)模型。
up-link模型表示spine-leaf拓扑结构中的脊叶节点关系,例如:spine-1与leaf-1之间的关系。peer-link模型表示spine-leaf拓扑结构中的叶叶节点关系,例如:leaf-1与leaf-2之间的关系。
通过上述步骤,即初始化网络编排、配置依赖关系链、生成网络拓扑,完成了网络编排的准备工作,下面便可启动编排。
在一个可选实施例中,在步骤S24中,根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息可以包括以下执行步骤:
步骤S241,从网络拓扑选取待编排设备;
步骤S242,读取待编排设备的邻居关系;
步骤S243,按照邻居关系遍历所有邻居设备,分别对待编排设备与每次遍历的邻居设备进行端口连接编排;
步骤S244,判断网络拓扑中是否存在尚未编排的设备,如果是,则返回步骤S241,如果否,则生成网络配置信息。
选取网络拓扑的一个节点,读取该节点的邻居关系。遍历所有邻居节点,对所选节点与邻居节点进行端口连接编排。
图6是根据本公开其中一可选实施例的网络编排过程的流程图,如图6所示,该过程可以包括以下执行步骤:
步骤S602,从网络拓扑选取一个待编排设备;
仍然以图3为例,选取网络拓扑中一个spine-1汇聚交换机作为支点,读取邻居关系,获取该支点的所有邻居关系,包括leaf-1,leaf-2,然后再参考邻居关系,进行编排。
步骤S604,根据待编排设备的邻居关系读取该待编排设备的一个邻居设备;
例如:从邻居关系中读取spine-1的邻居设备leaf-1。
步骤S606,判断该邻居设备是否已经编排完毕,如果是,则返回步骤S604;如果否,则继续执行步骤S608;
步骤S608,编排该待编排设备与该邻居设备之间的端口连接;
由于邻居设备leaf-1尚未编排完毕,因此,需要编排待编排设备spine-1与邻居设备leaf-1之间的端口连接。
在该步骤中,则可以进一步包括以下执行步骤:
步骤S6081,读取该待编排设备的邻居关系;
由于spine-1与leaf-1,leaf-2邻居关系是up-link模型,因此需要按照up-link结构编排。
步骤S6082,读取协议依赖关系链和编排参数;
以spine-1与leaf-1为例,按照up-link模型进行编排,读取协议依赖链,即按照LOOPBACK→LACP→VLAN→I进行编排。
步骤S6083,读取协议依赖关系链的起始协议;
以LOOPBACK为例,编排LOOPBACK,参考LOOPBACK的编排模板,其依赖项为ippool。
步骤S6084,根据该协议的编排器进行网络编排;
从ip池,即ip.service.loopback1分配一个ip地址,对LOOPBACK模板进行替换。
步骤S6085,判断协议依赖关系链中是否还存在尚未编排的协议,如果是,则继续执行步骤S6086;如果否,则转到步骤S608;
步骤S6086,读取协议依赖关系链中下一个待编排的协议,转到步骤S6084。
以LACP为例,其依赖项是邻居拓扑和sg池,参考LACP的编排模板,从sg池申请smartgroupID,获取spine-1到leaf-1的出端口xgei-0/1/1/22 和xgei-0/1/1/24,编排spine-1的lacp组,以及获取leaf-1到spine-1的出端口xgei-0/1/1/2,xgei-0/1/1/4,编排leaf-1的lacp组。以此类推,直至将协议依赖关系链中的全部协议编排关闭。
步骤S610,判断是否还有邻居节点,如果是,则转到步骤S604,如果否,则继续执行步骤S612;
步骤S612,判断是否还有尚未编排的设备,如果是,则转到步骤S602,如果否,则网络协议编排完成。
在一个可选实施例中,在步骤S243中,按照邻居关系遍历所有邻居设备,分别对待编排设备与每次遍历的邻居设备进行端口连接编排可以包括以下执行步骤:
步骤S2431,从协议关系链上的起始协议开始,遍历协议关系链的全部协议;
步骤S2432,针对每个协议,根据当前协议对应的编排模板对待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
端口连接编排包括读取协议关系链及编排参数,然后遍历关系链上的从起始协议开始的所有协议,针对每个协议,选择协议的模板在所选节点及邻居节点上进行编排,输出编排内容。具体编排过程可以参照上述图6所示的流程中所提供的编排示例,此处不再赘述。
在一个可选实施例中,在步骤S2432中,根据当前协议对应的编排模板对待编排设备与每次遍历的邻居设备进行端口连接编排可以包括以下执行步骤:
步骤S24321,按照当前协议对应的编排模板对当前协议进行解析,得到解析字段;
步骤S24322,从池参数所限定的分配范围中确定解析字段对应的池参数的取值,以及将解析字段对应的全局参数的取值替换为全局参数的预定义值。
编排是指分析协议编排模板,对于池参数而言,需要从池参数池申请相关值;对于全局参数而言,需要替换为全局参数定义的值;最后组装或合成得到编排内容(相当于上述网络配置信息)。编排内容是与设备类型和具体厂商产品无关的,是面向协议描述的一种中性组织结构。
仍然以图3为例,选取网络拓扑中一个spine-1汇聚交换机作为支点,读取邻居关系,获取该支点的所有邻居关系,包括leaf-1,leaf-2,然后再参考邻居关系,进行编排。
由于spine-1与leaf-1,leaf-2之间的邻居关系是up-link模型,因此可以按照up-link结构编排。由于leaf-1与leaf-2存在直连关系,是peer-link模型,因此可以按照peer-link结构编排。
以spine-1与leaf-1为例,按照up-link进行编排,读取协议依赖链,即按照LOOPBACK→LACP→VLAN→I进行编排,具体编排过程如下:
(1)编排LOOPBACK,参考LOOPBACK的编排模板,其依赖项为ippool。从ip池,即ip.service.loopback1分配一个ip地址,对LOOPBACK模板进行替换,得到如下编排:
(2)编排LACP,依赖项是邻居拓扑和sg池,参考LACP的编排模板,从sg池申请smartgroupID,获取spine-1到leaf-1的出端口xgei-0/1/1/22和xgei-0/1/1/24,编排spine-1的lacp组,以及获取leaf-1到spine-1的出 端口xgei-0/1/1/2,xgei-0/1/1/4,编排leaf-1的lacp组。编排器输出spine-1的lacp组如下:
编排器输出leaf-1的lacp组如下:
(3)编排VLAN,VLAN依赖项是VLAN池和LACP,参考VLAN的编排模板,根据VLAN池及具体IP分配方案,从VLAN池分配ID 101,spine-1的LACP(smartgroup33)加入VLAN,编排器输出示例如下:
leaf-1的LACP(smartgroup3)加入VLAN,编排器输出示例如下:
编排VLAN(上述生成的vlan101)三层接口,从vlan的IP池分配IP,编排器生成spine-1配置如下:
编排器生成leaf-1配置如下:
(4)编排I,vlan101加入I的interface,参考I的编排模板,编排器生成spine-1配置如下(leaf-1的配置略):
通过上述分析可见,如果确定池参数的定义及依赖关系链,以及编排模板,则网络编排将会成为非常快速的自动化的过程。
进一步地,在上述可选实施例的基础上,新增一个存储面的编排,包括存储面使用VRF隔离。
编排VRF的实例如下:
编排LACP加入VLAN(vlan101,VLAN1101),示例如下:
编排VLAN,即上述编排出的vlan101与lan1101,示例如下:
其他编排过程类似LACP的编排。
在一个可选实施例中,在步骤S26中,将网络配置信息下发至设备可以包括以下执行步骤:
步骤S261,根据下发通道的要求将网络配置信息解析为设备可识别的报文;
步骤S262,将解析后得到可识别报文下发至设备。
编排内容是一种中性组织结构,当下发到厂商设备时,需要进行一次解析以适配到具体的设备。解析可以根据下发通道的要求,例如:远程终端协议(TELNET),安全外壳协议(SSH)或者基于可扩展标记语言的网络配置协议(NETCONF),解析后构造出相关的设备可识别报文。报文经过通道下发设备,即完成网络部署。至此,安装依赖链基本编排并构建出数据中心的underlay基础(业务面)网络。
在一个可选实施例中,在步骤S26中,将网络配置信息下发至设备还可以包括以下执行步骤:
步骤S263,对网络协议编排、网络配置信息解析以及网络配置信息下发的过程进行检测,并生成检测日志。
在编排内容下发到设备之后,可以通过自我检测来验证从编排到解析、再到下发设备的整个过程的正确性,并提供日志。此外,为了提高下发效率,编排器输出以及下发提供并行机制,进而加快部署效率。
通过上述分析,图4和图5所示的可选实施例从实现的层面展开,通常包括初始化编排参数、配置依赖关系链、生成网络拓扑、编排和下发这五个步骤。下面将会从应用的层面介绍如何快速部署网络。
在一个可选实施例的自动化部署underlay网络中,首先,用户定义初 级编排参数的示例如下:
[devices]
173.18.101.200=role:spine,username:who,password:who,hostname:spine-1
173.18.101.1=role:leaf,username:who,password:who
173.18.101.2=role:leaf,username:who,password:who
173.18.102.200=role:spine,username:who,password:who,hostname:spine-2
173.18.102.1=role:leaf,username:who,password:who
173.18.102.2=role:leaf,username:who,password:who
[service]
loopback1=10.30.0.1/32
loopback2=10.30.1.1/32
vlanid=101:200
vlanip=10.30.3.2/30
router=I
[store]
vrf=store
loopback3=10.30.25.1/32
vlanid=1101:200
vlanip=10.30.26.2/30
router=I
然后,再依照上述两个可选实施例介绍的部署过程,完成包括池参数关系链、协议关系依赖链的生成,采用LLDP方法生成网络拓扑以及在基于LLDP发现的拓扑进行网络编排后,下发编排内容即可完成整个部署过程的自动化。
需要说明的是,上述可选实施例的实施过程结合某一具体的商用数据中心交换机,并基于特定网络协议(例如:LACP+VLAN+I的协议链)进行编排,然而这些并不对本公开所提供的技术方案造成不当限制。另外,即使在实施过程中增加协议编排,例如:路由协议启用开放式最短路径优先(OSPF),也并未不超出本公开所提供的技术方案的保护范围。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种网络部署装置,该装置用于实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本公开实施例的网络部署装置的结构框图,如图7所示,该装置包括:网络编排模块10,设置为获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;以及根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;下发模块20,设置为将网络配置信息下发至设备。
在一个可选实施例中,网络编排模块10包括:第一获取单元(图中未示出),设置为获取协议参数,其中,协议参数至少包括:网络上待配 置的协议以及与待配置协议关联的配置参数和全局参数;第二获取单元(图中未示出),设置为获取编排参数,其中,获取编排参数至少包括:获取初级参数,初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
在一个可选实施例中,第二获取单元(图中未示出),还设置为获取高级参数,其中,高级参数是通过对初级参数进行编排得到的参数。
在一个可选实施例中,第二获取单元(图中未示出),还设置为获取池参数,其中,池参数用于限定参数取值的分配范围。
在一个可选实施例中,网络编排模块10包括:第三获取单元(图中未示出),设置为获取协议关系链,其中,协议关系链用于描述网络上待配置的协议中每种协议相互间的依赖关系;第四获取单元(图中未示出),设置为获取池参数关系链,其中,池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;第五获取单元(图中未示出),设置为获取协议关系链与池参数关系链之间的依赖关系,以使池参数关系链为协议关系链中的参数进行取值分配。
在一个可选实施例中,网络编排模块10还包括:建立单元(图中未示出),设置为根据获取到的依赖关系链建立对应关系,其中,对应关系包括:多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
在一个可选实施例中,网络编排模块10包括:第六获取单元(图中未示出),设置为获取网络中各个设备之间的邻居关系,其中,邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
在一个可选实施例中,邻居关系还包括:网络中每个设备的网络角色以及相邻设备之间的邻居模型。
在一个可选实施例中,网络编排模块10包括:选取单元(图中未示出),设置为从网络拓扑选取待编排设备;读取单元(图中未示出),设置为读取待编排设备的邻居关系;编排单元(图中未示出),设置为按照邻居关系遍历所有邻居设备,分别对待编排设备与每次遍历的邻居设备进行 端口连接编排;判断单元(图中未示出),设置为判断网络拓中是否存在尚未编排的设备,如果是,则返回选取单元,如果否,则生成网络配置信息。
在一个可选实施例中,编排单元(图中未示出)包括:遍历子单元(图中未示出),设置为从协议关系链上的起始协议开始,遍历协议关系链的全部协议;编排子单元(图中未示出),设置为针对每个协议,根据当前协议对应的编排模板对待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
在一个可选实施例中,编排子单元(图中未示出),设置为按照当前协议对应的编排模板对当前协议进行解析,得到解析字段;以及从池参数所限定的分配范围中确定解析字段对应的池参数的取值,以及将解析字段对应的全局参数的取值替换为全局参数的预定义值。
在一个可选实施例中,下发模块20包括:解析单元(图中未示出),设置为根据下发通道的要求将网络配置信息解析为设备可识别的报文;下发单元(图中未示出),设置为将解析后得到可识别报文下发至设备。
在一个可选实施例中,下发模块20还包括:检测单元(图中未示出),设置为对网络协议编排、网络配置信息解析以及网络配置信息下发的过程进行检测,并生成检测日志。
需要说明的是,上述各个模块是可以通过软件或硬件来实现的,对于后者,可以通过以下方式实现,但不限于此:上述模块均位于同一处理器中;或者,上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本公开的实施例还提供了一种存储介质,该存储介质中存储有计算机程序,其中,该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地,在本实施例中,上述存储介质可以被设置为存储用于执行以下步骤的计算机程序:
S1,获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;
S2,根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;
S3,将网络配置信息下发至设备。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,获取协议参数,其中,协议参数至少包括:网络上待配置的协议以及与待配置协议关联的配置参数和全局参数;
S2,获取编排参数,其中,获取编排参数至少包括:获取初级参数,初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,获取高级参数,其中,高级参数是通过对初级参数进行编排得到的参数。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,获取池参数,其中,池参数用于限定参数取值的分配范围。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,获取协议关系链,其中,协议关系链用于描述网络上待配置的协议中每种协议相互间的依赖关系;
S2,获取池参数关系链,其中,池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;
S3,获取协议关系链与池参数关系链之间的依赖关系,以使池参数关系链为协议关系链中的参数进行取值分配。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,根据获取到的依赖关系链建立对应关系,其中,对应关系包括: 多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,获取网络中各个设备之间的邻居关系,其中,邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,从网络拓扑选取待编排设备;
S2,读取待编排设备的邻居关系;
S3,按照邻居关系遍历所有邻居设备,分别对待编排设备与每次遍历的邻居设备进行端口连接编排;
S4,判断网络拓扑中是否存在尚未编排的设备,如果是,则返回S1,如果否,则生成网络配置信息。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,从协议关系链上的起始协议开始,遍历协议关系链的全部协议;
S2,针对每个协议,根据当前协议对应的编排模板对待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,按照当前协议对应的编排模板对当前协议进行解析,得到解析字段;
S2,从池参数所限定的分配范围中确定解析字段对应的池参数的取值,以及将解析字段对应的全局参数的取值替换为全局参数的预定义值。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,根据下发通道的要求将网络配置信息解析为设备可识别的报文;
S2,将解析后得到可识别报文下发至设备。
可选地,存储介质还被设置为存储用于执行以下步骤的计算机程序:
S1,对网络协议编排、网络配置信息解析以及网络配置信息下发的过 程进行检测,并生成检测日志。
可选地,在本实施例中,上述存储介质可以包括但不限于:U盘、只读存储器(Read-Only Memory,简称为ROM)、随机存取存储器(Random Access Memory,简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
实施例4
本公开的实施例还提供了一种电子装置,包括存储器和处理器,该存储器中存储有计算机程序,该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地,上述电子装置还可以包括传输设备以及输入输出设备,其中,该传输设备和上述处理器连接,该输入输出设备和上述处理器连接。
可选地,在本实施例中,上述处理器可以被设置为通过计算机程序执行以下步骤:
S1,获取网络编排参数,依赖关系链以及网络拓扑,其中,依赖关系链中的每个协议节点预先配置有对应的编排模板,编排模板用于描述每个协议节点所依赖的参数信息;
S2,根据网络编排参数,依赖关系链以及网络拓扑进行网络协议编排,生成网络配置信息;
S3,将网络配置信息下发至设备。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,获取协议参数,其中,协议参数至少包括:网络上待配置的协议以及与待配置协议关联的配置参数和全局参数;
S2,获取编排参数,其中,获取编排参数至少包括:获取初级参数,初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序 执行以下步骤:
S1,获取高级参数,其中,高级参数是通过对初级参数进行编排得到的参数。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,获取池参数,其中,池参数用于限定参数取值的分配范围。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,获取协议关系链,其中,协议关系链用于描述网络上待配置的协议中每种协议相互间的依赖关系;
S2,获取池参数关系链,其中,池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;
S3,获取协议关系链与池参数关系链之间的依赖关系,以使池参数关系链为协议关系链中的参数进行取值分配。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,根据获取到的依赖关系链建立对应关系,其中,对应关系包括:多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,获取网络中各个设备之间的邻居关系,其中,邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,从网络拓扑选取待编排设备;
S2,读取待编排设备的邻居关系;
S3,按照邻居关系遍历所有邻居设备,分别对待编排设备与每次遍历的邻居设备进行端口连接编排;
S4,判断网络拓中是否存在尚未编排的设备,如果是,则返回S1,如果否,则生成网络配置信息。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,从协议关系链上的起始协议开始,遍历协议关系链的全部协议;
S2,针对每个协议,根据当前协议对应的编排模板对待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,按照当前协议对应的编排模板对当前协议进行解析,得到解析字段;
S2,从池参数所限定的分配范围中确定解析字段对应的池参数的取值,以及将解析字段对应的全局参数的取值替换为全局参数的预定义值。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,根据下发通道的要求将网络配置信息解析为设备可识别的报文;
S2,将解析后得到可识别报文下发至设备。
可选地,在本实施例中,上述处理器还可以被设置为通过计算机程序执行以下步骤:
S1,对网络协议编排、网络配置信息解析以及网络配置信息下发的过程进行检测,并生成检测日志。
可选地,本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例,本实施例在此不再赘述。
显然,本领域的技术人员应该明白,上述的本公开的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已,并不用于限制本公开,对于本领域的技术人员来说,本公开可以有各种更改和变化。凡在本公开的原则之内,所作的任何修改、等同替换、改进等,均应包含在本公开的保护范围之内。
如上所述,本发明实施例提供的一种网络部署方法及装置具有以下有益效果:解决了相关技术中所提供的网络部署方式操作复杂度较高、容错率较低的问题,达到通过建立的依赖关系链,降低网络部署配置过程的操作复杂度,更有助于大型数据中心基础网络的自动部署和快速交付。
Claims (29)
- 一种网络部署方法,包括:获取网络编排参数,依赖关系链以及网络拓扑,其中,所述依赖关系链中的每个协议节点预先配置有对应的编排模板,所述编排模板用于描述每个协议节点所依赖的参数信息;根据所述网络编排参数,所述依赖关系链以及所述网络拓扑进行网络协议编排,生成网络配置信息;将所述网络配置信息下发至设备。
- 根据权利要求1所述的方法,其中,获取所述网络编排参数包括:获取协议参数,其中,所述协议参数至少包括:网络上待配置的协议以及与所述待配置协议关联的配置参数和全局参数;获取编排参数,其中,获取所述编排参数至少包括:获取初级参数,所述初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
- 根据权利要求2所述的方法,其中,获取所述编排参数还包括:获取高级参数,其中,所述高级参数是通过对所述初级参数进行编排得到的参数。
- 根据权利要求3所述的方法,其中,获取所述高级参数至少包括:获取池参数,其中,所述池参数用于限定参数取值的分配范围。
- 根据权利要求1所述的方法,其中,获取所述依赖关系链包括:获取协议关系链,其中,所述协议关系链用于描述网络上待配置 的协议中每种协议相互间的依赖关系;获取池参数关系链,其中,所述池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;获取所述协议关系链与所述池参数关系链之间的依赖关系,以使所述池参数关系链为所述协议关系链中的参数进行取值分配。
- 根据权利要求5所述的方法,其中,获取所述依赖关系链还包括:根据获取到的所述依赖关系链建立对应关系,其中,所述对应关系包括:多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
- 根据权利要求1所述的方法,其中,获取所述网络拓扑至少包括:获取网络中各个设备之间的邻居关系,其中,所述邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
- 根据权利要求7所述的方法,其中,所述邻居关系还包括:所述网络中每个设备的网络角色以及相邻设备之间的邻居模型。
- 根据权利要求1所述的方法,其中,根据所述网络编排参数,所述依赖关系链以及所述网络拓扑进行网络协议编排,生成所述网络配置信息包括:选取步骤,从所述网络拓扑选取待编排设备;读取步骤,读取所述待编排设备的邻居关系;编排步骤,按照所述邻居关系遍历所有邻居设备,分别对所述待编排设备与每次遍历的邻居设备进行端口连接编排;判断步骤,判断所述网络拓中是否存在尚未编排的设备,如果是, 则返回所述选取步骤,如果否,则生成所述网络配置信息。
- 根据权利要求9所述的方法,其中,按照所述邻居关系遍历所有邻居设备,分别对所述待编排设备与每次遍历的邻居设备进行端口连接编排包括:从协议关系链上的起始协议开始,遍历所述协议关系链的全部协议;针对每个协议,根据当前协议对应的编排模板对所述待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
- 根据权利要求10所述的方法,其中,根据当前协议对应的编排模板对所述待编排设备与每次遍历的邻居设备进行端口连接编排包括:按照所述当前协议对应的编排模板对所述当前协议进行解析,得到解析字段;从池参数所限定的分配范围中确定所述解析字段对应的池参数的取值,以及将所述解析字段对应的全局参数的取值替换为所述全局参数的预定义值。
- 根据权利要求1所述的方法,其中,将所述网络配置信息下发至所述设备包括:根据下发通道的要求将所述网络配置信息解析为所述设备可识别的报文;将解析后得到可识别报文下发至所述设备。
- 根据权利要求12所述的方法,其中,将所述网络配置信息下发至所述设备还包括:对网络协议编排、网络配置信息解析以及网络配置信息下发的过程进行检测,并生成检测日志。
- 一种网络部署装置,包括:网络编排模块,设置为获取网络编排参数,依赖关系链以及网络拓扑,其中,所述依赖关系链中的每个协议节点预先配置有对应的编排模板,所述编排模板用于描述每个协议节点所依赖的参数信息;以及根据所述网络编排参数,所述依赖关系链以及所述网络拓扑进行网络协议编排,生成网络配置信息;下发模块,设置为将所述网络配置信息下发至设备。
- 根据权利要求14所述的装置,其中,所述网络编排模块包括:第一获取单元,设置为获取协议参数,其中,所述协议参数至少包括:网络上待配置的协议以及与所述待配置协议关联的配置参数和全局参数;第二获取单元,设置为获取编排参数,其中,获取所述编排参数至少包括:获取初级参数,所述初级参数为面向网络整体结构的、经过简化处理的具有代表性的参数。
- 根据权利要求15所述的装置,其中,所述第二获取单元,还设置为获取高级参数,其中,所述高级参数是通过对所述初级参数进行编排得到的参数。
- 根据权利要求16所述的装置,其中,所述第二获取单元,还设置为获取池参数,其中,所述池参数用于限定参数取值的分配范围。
- 根据权利要求14所述的装置,其中,所述网络编排模块包括:第三获取单元,设置为获取协议关系链,其中,所述协议关系链用于描述网络上待配置的协议中每种协议相互间的依赖关系;第四获取单元,设置为获取池参数关系链,其中,所述池参数关系链用于描述网络上待使用的池参数中每个池参数相互间的依赖关系;第五获取单元,设置为获取所述协议关系链与所述池参数关系链之间的依赖关系,以使所述池参数关系链为所述协议关系链中的参数进行取值分配。
- 根据权利要求18所述的装置,其中,所述网络编排模块还包括:建立单元,设置为根据获取到的所述依赖关系链建立对应关系,其中,所述对应关系包括:多个编排项以及与每个编排项对应的类型、编排模板以及依赖关系。
- 根据权利要求14所述的装置,其中,所述网络编排模块包括:第六获取单元,设置为获取网络中各个设备之间的邻居关系,其中,所述邻居关系至少包括:每个设备的各个端口分别连接的设备信息以及连接的端口信息。
- 根据权利要求20所述的装置,其中,所述邻居关系还包括:所述网络中每个设备的网络角色以及相邻设备之间的邻居模型。
- 根据权利要求14所述的装置,其中,所述网络编排模块包括:选取单元,设置为从所述网络拓扑选取待编排设备;读取单元,设置为读取所述待编排设备的邻居关系;编排单元,设置为按照所述邻居关系遍历所有邻居设备,分别对所述待编排设备与每次遍历的邻居设备进行端口连接编排;判断单元,设置为判断所述网络拓扑中是否存在尚未编排的设备, 如果是,则返回所述选取单元,如果否,则生成所述网络配置信息。
- 根据权利要求22所述的装置,其中,所述编排单元包括:遍历子单元,设置为从协议关系链上的起始协议开始,遍历所述协议关系链的全部协议;编排子单元,设置为针对每个协议,根据当前协议对应的编排模板对所述待编排设备与每次遍历的邻居设备进行端口连接编排,直至全部协议编排完毕。
- 根据权利要求23所述的装置,其中,所述编排子单元,设置为按照所述当前协议对应的编排模板对所述当前协议进行解析,得到解析字段;以及从池参数所限定的分配范围中确定所述解析字段对应的池参数的取值,以及将所述解析字段对应的全局参数的取值替换为所述全局参数的预定义值。
- 根据权利要求14所述的装置,其中,所述下发模块包括:解析单元,设置为根据下发通道的要求将所述网络配置信息解析为所述设备可识别的报文;下发单元,设置为将解析后得到可识别报文下发至所述设备。
- 根据权利要求25所述的装置,其中,所述下发模块还包括:检测单元,设置为对网络协议编排、网络配置信息解析以及网络配置信息下发的过程进行检测,并生成检测日志。
- 一种网络部署设备,包括:网络编排模块,设置为获取网络编排参数,依赖关系链以及网络拓扑,其中,所述依赖关系链中的每个协议节点预先配置有对应的编排模板,所述编排模板用于描述每个协议节点所依赖的参数信息;以及根据所述网络编排参数,所述依赖关系链以及所述网络拓扑进行网 络协议编排,生成网络配置信息;下发模块,设置为将所述网络配置信息下发至设备。
- 一种存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行所述权利要求1至13任一项中所述的方法。
- 一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行所述权利要求1至13任一项中所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
RU2020138543A RU2754487C1 (ru) | 2018-07-09 | 2019-04-10 | Способ и устройство для развертывания сети |
EP19833250.4A EP3780498A4 (en) | 2018-07-09 | 2019-04-10 | NETWORK DEPLOYMENT METHOD AND DEVICE |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810747333.9 | 2018-07-09 | ||
CN201810747333.9A CN110708178B (zh) | 2018-07-09 | 2018-07-09 | 网络部署方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020010887A1 true WO2020010887A1 (zh) | 2020-01-16 |
Family
ID=69142211
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/082109 WO2020010887A1 (zh) | 2018-07-09 | 2019-04-10 | 网络部署方法及装置 |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP3780498A4 (zh) |
CN (1) | CN110708178B (zh) |
RU (1) | RU2754487C1 (zh) |
WO (1) | WO2020010887A1 (zh) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111913700A (zh) * | 2020-06-24 | 2020-11-10 | 北京大学(天津滨海)新一代信息技术研究院 | 一种云-端交互协议分析方法、装置、设备及存储介质 |
CN113703988A (zh) * | 2020-05-21 | 2021-11-26 | ***通信集团北京有限公司 | 能力编排方法、装置、设备及介质 |
CN114697208A (zh) * | 2022-03-30 | 2022-07-01 | 广州晨扬通信技术有限公司 | 一种网元设备的配置分析方法、***、设备以及存储介质 |
CN115150281A (zh) * | 2022-06-22 | 2022-10-04 | 京东科技信息技术有限公司 | 一种数据中心的网络建设方法和装置 |
CN115277428A (zh) * | 2022-07-27 | 2022-11-01 | 京东科技信息技术有限公司 | 用于配置网络的方法和装置 |
CN115297157A (zh) * | 2022-08-01 | 2022-11-04 | 中国电信股份有限公司 | 业务处理方法、装置、***、介质及电子设备 |
CN116260860A (zh) * | 2022-12-09 | 2023-06-13 | 深圳前海环融联易信息科技服务有限公司 | 一种应用部署方法、装置、存储介质及电子设备 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113472558B (zh) * | 2020-03-31 | 2023-11-21 | 北京华为数字技术有限公司 | 网络部署的方法及装置 |
CN111541569B (zh) * | 2020-04-22 | 2022-10-11 | 国家电网有限公司信息通信分公司 | 一种网络节点配置方法和装置 |
CN114553706B (zh) * | 2020-11-18 | 2023-09-19 | ***通信集团广东有限公司 | 网络拓扑发现方法、装置及电子设备 |
CN112398696A (zh) * | 2020-11-30 | 2021-02-23 | 迈普通信技术股份有限公司 | 一种实现零配置开局的***及方法 |
CN112702201A (zh) * | 2020-12-23 | 2021-04-23 | 中移(杭州)信息技术有限公司 | 参数配置方法及***、通信设备和计算机可读存储介质 |
CN112910705B (zh) * | 2021-02-02 | 2023-04-07 | 杭州安恒信息技术股份有限公司 | 网络流量编排的方法、设备和存储介质 |
CN113193980A (zh) * | 2021-03-29 | 2021-07-30 | 中盈优创资讯科技有限公司 | 一种基于新型城域网拓扑快速生成功能配置的方法及装置 |
CN112965745B (zh) * | 2021-04-01 | 2023-09-01 | 北京奇艺世纪科技有限公司 | 一种***接入方法、装置、设备及计算机可读介质 |
CN113612646B (zh) * | 2021-08-30 | 2022-08-02 | 复旦大学 | 一种基于邻居发现的园区网络拓扑可视化方法 |
CN113873548A (zh) * | 2021-09-03 | 2021-12-31 | 中盈优创资讯科技有限公司 | 一种白盒设备一键开局方法及装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104125091A (zh) * | 2013-04-25 | 2014-10-29 | 杭州华三通信技术有限公司 | 网络配置自动部署方法及装置 |
WO2017005813A1 (en) * | 2015-07-06 | 2017-01-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Mapping of service requirements for a virtualized network on a packet flow |
US20170048110A1 (en) * | 2015-08-11 | 2017-02-16 | At&T Intellectual Property I, L.P. | Dynamic Virtual Network Topology Discovery Engine |
CN106685679A (zh) * | 2015-11-09 | 2017-05-17 | 中兴通讯股份有限公司 | 一种网络服务部署方法和装置 |
CN106936619A (zh) * | 2015-12-31 | 2017-07-07 | 华为技术有限公司 | 部署网络服务的方法和装置 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9489110B2 (en) * | 2012-10-29 | 2016-11-08 | Bank Of America Corporation | Automatic deployment, configuration, and lifecycle management of applications and infrastructure components |
US9460286B1 (en) * | 2013-12-19 | 2016-10-04 | Amdocs Software Systems Limited | System, method, and computer program for managing security in a network function virtualization (NFV) based communication network |
EP3148145B1 (en) * | 2014-06-12 | 2019-02-20 | Huawei Technologies Co. Ltd. | Resource allocation method and device |
CN105577409B (zh) * | 2014-10-16 | 2020-08-11 | 中兴通讯股份有限公司 | 一种实现虚拟网络功能自动部署的方法和装置 |
CN106330727A (zh) * | 2015-07-07 | 2017-01-11 | 中兴通讯股份有限公司 | Sdn网络设备建链方法、设备和*** |
US9860164B2 (en) * | 2016-01-21 | 2018-01-02 | Ciena Corporation | Flow based virtual network function orchestration |
CN107147509B (zh) * | 2016-03-01 | 2022-03-11 | 中兴通讯股份有限公司 | 虚拟专用网业务实现方法、装置及通信*** |
WO2018089417A1 (en) * | 2016-11-09 | 2018-05-17 | Interdigital Patent Holdings, Inc. | Systems and methods to create slices at a cell edge to provide computing services |
US20180191607A1 (en) * | 2016-12-29 | 2018-07-05 | Juniper Networks, Inc. | Network service application and customer-aware virtualized network function placement |
EP3563545B1 (en) * | 2016-12-30 | 2024-07-17 | INTEL Corporation | Blockchains for securing iot devices |
-
2018
- 2018-07-09 CN CN201810747333.9A patent/CN110708178B/zh active Active
-
2019
- 2019-04-10 WO PCT/CN2019/082109 patent/WO2020010887A1/zh unknown
- 2019-04-10 RU RU2020138543A patent/RU2754487C1/ru active
- 2019-04-10 EP EP19833250.4A patent/EP3780498A4/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104125091A (zh) * | 2013-04-25 | 2014-10-29 | 杭州华三通信技术有限公司 | 网络配置自动部署方法及装置 |
WO2017005813A1 (en) * | 2015-07-06 | 2017-01-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Mapping of service requirements for a virtualized network on a packet flow |
US20170048110A1 (en) * | 2015-08-11 | 2017-02-16 | At&T Intellectual Property I, L.P. | Dynamic Virtual Network Topology Discovery Engine |
CN106685679A (zh) * | 2015-11-09 | 2017-05-17 | 中兴通讯股份有限公司 | 一种网络服务部署方法和装置 |
CN106936619A (zh) * | 2015-12-31 | 2017-07-07 | 华为技术有限公司 | 部署网络服务的方法和装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3780498A4 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113703988A (zh) * | 2020-05-21 | 2021-11-26 | ***通信集团北京有限公司 | 能力编排方法、装置、设备及介质 |
CN113703988B (zh) * | 2020-05-21 | 2024-01-19 | ***通信集团北京有限公司 | 能力编排方法、装置、设备及介质 |
CN111913700A (zh) * | 2020-06-24 | 2020-11-10 | 北京大学(天津滨海)新一代信息技术研究院 | 一种云-端交互协议分析方法、装置、设备及存储介质 |
CN111913700B (zh) * | 2020-06-24 | 2024-02-13 | 北京大学(天津滨海)新一代信息技术研究院 | 一种云-端交互协议分析方法、装置、设备及存储介质 |
CN114697208A (zh) * | 2022-03-30 | 2022-07-01 | 广州晨扬通信技术有限公司 | 一种网元设备的配置分析方法、***、设备以及存储介质 |
CN114697208B (zh) * | 2022-03-30 | 2023-08-25 | 广州晨扬通信技术有限公司 | 一种网元设备的配置分析方法、***、设备以及存储介质 |
CN115150281A (zh) * | 2022-06-22 | 2022-10-04 | 京东科技信息技术有限公司 | 一种数据中心的网络建设方法和装置 |
CN115277428A (zh) * | 2022-07-27 | 2022-11-01 | 京东科技信息技术有限公司 | 用于配置网络的方法和装置 |
CN115297157A (zh) * | 2022-08-01 | 2022-11-04 | 中国电信股份有限公司 | 业务处理方法、装置、***、介质及电子设备 |
CN116260860A (zh) * | 2022-12-09 | 2023-06-13 | 深圳前海环融联易信息科技服务有限公司 | 一种应用部署方法、装置、存储介质及电子设备 |
Also Published As
Publication number | Publication date |
---|---|
CN110708178A (zh) | 2020-01-17 |
EP3780498A1 (en) | 2021-02-17 |
RU2754487C1 (ru) | 2021-09-02 |
EP3780498A4 (en) | 2021-06-02 |
CN110708178B (zh) | 2022-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020010887A1 (zh) | 网络部署方法及装置 | |
US10554483B2 (en) | Network policy analysis for networks | |
US8830820B2 (en) | Semi-centralized routing | |
US9338097B2 (en) | Method and system for load balancing at a data network | |
CN107409066B (zh) | 用于自动检测和配置服务器上行链路网络接口的***和方法 | |
US10938660B1 (en) | Automation of maintenance mode operations for network devices | |
CN104753697B (zh) | 一种控制网络设备自动开局的方法、设备及*** | |
EP3643011B1 (en) | Network validation between the logical level and the hardware level of a network | |
CN105656653A (zh) | 分布式协调***中新增节点的入网方法、装置和*** | |
EP3643010B1 (en) | Validation of layer 1 interface in a network | |
US9088477B2 (en) | Distributed fabric management protocol | |
US9231848B2 (en) | Method and system for an overlay management control network | |
CN103997414A (zh) | 生成配置信息的方法和网络控制单元 | |
CN106716926B (zh) | 硬件库存的自动化独立式引导电路 | |
US20190372870A1 (en) | Network device snapshots | |
US11522754B2 (en) | Systems and methods for Zero-Touch Provisioning of a switch in intermediate distribution frames and main distribution frames | |
US20220150119A1 (en) | Network scale emulator | |
WO2018231564A1 (en) | Distributed fault code aggregation across application centric dimensions | |
Subratie et al. | EdgeVPN: Self-organizing layer-2 virtual edge networks | |
CN112333014B (zh) | 设备管理方法及通信装置 | |
Matias et al. | The EHU-OEF: an OpenFlow-based layer-2 experimental facility | |
CN113660675A (zh) | 一种5g专线承载网段自动开通方法及装置 | |
CN111538569A (zh) | 一种基于云平台的***一键部署方法 | |
CN115426334B (zh) | 网络地址生成方法、装置、路由设备及存储介质 | |
CN112260847B (zh) | 一种发送ospf域信息的方法、获取ospf域信息的方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19833250 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2019833250 Country of ref document: EP Effective date: 20201030 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |