Abstract:
A network function virtualization (NFV) platform can support hybrid and elastic scaling and recovery services. In one example, a system can deploy a cloud virtual network function manager (VNFM) and one or more cloud virtual network functions (VNFs) on a cloud. The system can monitor, via the cloud VNFM, a local VNFM on a local network, the cloud VNFM, and/or the one or more cloud VNFs. Based on the monitoring, the system can determine, via the cloud VNFM, a respective status of the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs. Based on the respective status of the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs, the system can then scale, via the cloud VNFM, the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs.
Abstract:
A network function virtualization (NFV) platform can support virtual network functions (VNFs) whose behavior can change during their lifecycles. For example, a VNF manager of the NFV platform can receive a request to update a condition of a VNF and/or an action to perform upon satisfaction of the condition. Based on the condition and action, the VNF manager can create or store a lifecycle management policy in an extensible lifecycle management model associated with the virtual network function. Based on the lifecycle management policy, the VNF manager can monitor the virtual network function to detect satisfaction of the condition and, in response to detecting satisfaction of the condition, the VNF manager can perform the action associated with the lifecycle management policy.
Abstract:
A device is configured to support one or more virtual networking functions at a branch in a network. The device receives from a central control entity a command to deploy a particular virtual networking function, the command including or accompanied by a deployment file that identifies an external port at which the particular virtual networking function is accessed externally at the device. The device maps the external port to an internal port on an internal management network of the device, and stores a portmapping entry for the particular virtual networking function based on the mapping. The device sends to the central control entity a notification containing portmapping information that indicates the internal port to which the external port is mapped.
Abstract:
This disclosure describes lifecycle management (LCM) techniques for improving high availability (HA) and scalability in a virtual network. The techniques include empowering virtual network function managers (VNFMs) to provide LCM to other VNFMs in the virtual network. For example, a VNFM instance in the virtual network may autonomously update and/or improve the virtual network design, such as by deploying additional VNFM instances. A VNFM network may be able to self-organize, such as by designating a primary cluster and/or autonomously holding an election. A VNFM instance may also heal and/or redeploy another VNFM instance. The present virtual network LCM techniques may allow a virtual network to be self-sustaining while providing HA.
Abstract:
This disclosure describes lifecycle management (LCM) techniques for improving high availability (HA) and scalability in a virtual network. The techniques include empowering virtual network function managers (VNFMs) to provide LCM to other VNFMs in the virtual network. For example, a VNFM instance in the virtual network may autonomously update and/or improve the virtual network design, such as by deploying additional VNFM instances. A VNFM network may be able to self-organize, such as by designating a primary cluster and/or autonomously holding an election. A VNFM instance may also heal and/or redeploy another VNFM instance. The present virtual network LCM techniques may allow a virtual network to be self-sustaining while providing HA.
Abstract:
A network function virtualization (NFV) platform can support virtual network functions (VNFs) whose behavior can change during their lifecycles. For example, a VNF manager of the NFV platform can receive a request to update a condition of a VNF and/or an action to perform upon satisfaction of the condition. Based on the condition and action, the VNF manager can create or store a lifecycle management policy in an extensible lifecycle management model associated with the virtual network function. Based on the lifecycle management policy, the VNF manager can monitor the virtual network function to detect satisfaction of the condition and, in response to detecting satisfaction of the condition, the VNF manager can perform the action associated with the lifecycle management policy.
Abstract:
In one example, a Virtual Network Function Manager (VNFM) obtains, from a monitoring agent that is configured to monitor a Virtual Network Function (VNF) for a presence of a technical issue with the VNF, an indication of the presence of the technical issue with the VNF. The monitoring agent is deployed at a remote site. Based on the indication of the presence of the technical issue with the VNF, the VNFM determines a resolution for the presence of the technical issue with the VNF. The VNFM automatically implements the resolution for the presence of the technical issue with the VNF.
Abstract:
A network function virtualization (NFV) platform can support hybrid and elastic scaling and recovery services. In one example, a system can deploy a cloud virtual network function manager (VNFM) and one or more cloud virtual network functions (VNFs) on a cloud. The system can monitor, via the cloud VNFM, a local VNFM on a local network, the cloud VNFM, and/or the one or more cloud VNFs. Based on the monitoring, the system can determine, via the cloud VNFM, a respective status of the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs. Based on the respective status of the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs, the system can then scale, via the cloud VNFM, the local VNFM, the cloud VNFM, and/or the one or more cloud VNFs.
Abstract:
A device is configured to support one or more virtual networking functions at a branch in a network. The device receives from a central control entity a command to deploy a particular virtual networking function, the command including or accompanied by a deployment file that identifies an external port at which the particular virtual networking function is accessed externally at the device. The device maps the external port to an internal port on an internal management network of the device, and stores a portmapping entry for the particular virtual networking function based on the mapping. The device sends to the central control entity a notification containing portmapping information that indicates the internal port to which the external port is mapped.
Abstract:
A network function virtualization (NFV) platform can support virtual network functions (VNFs) whose behavior can change during their lifecycles. For example, a VNF manager of the NFV platform can receive a request to update a condition of a VNF and/or an action to perform upon satisfaction of the condition. Based on the condition and action, the VNF manager can create or store a lifecycle management policy in an extensible lifecycle management model associated with the virtual network function. Based on the lifecycle management policy, the VNF manager can monitor the virtual network function to detect satisfaction of the condition and, in response to detecting satisfaction of the condition, the VNF manager can perform the action associated with the lifecycle management policy.