You can deploy a physical network function for a tenant in a network service. As physical network functions, you can use dedicated hardware as well as virtual entities created using third-party virtualization environments. The orchestrator does not manage the lifecycle of physical network functions.
For example, you can deploy a physical network function at the central office of your organization to protect user traffic that is transmitted between CPE devices.
Physical network function deployment involves the following steps:
Ensuring network connectivity between the orchestrator and the physical network function
Ensure network connectivity between the virtual machine or physical server on which the orchestrator is deployed and the dedicated hardware or virtual entity on which you want to deploy the physical network function.
Assigning the physical network function to a tenant
Use one of the following methods to assign the physical network function to the tenant for which you want to deploy it:
If necessary, configure the topology and the physical network function. For a description of what you can do with physical network functions, see the Managing physical network functions section.
If you want to deploy a physical network function using a network service template, add the network service template to the topology.
If you want to deploy a physical network function without a network service template, add the physical network function to the topology.
If necessary, configure the topology and the physical network function. For a description of what you can do with physical network functions, see the Managing physical network functions section.
Deploy the physical network function using one of the following methods:
If you added the physical network function to the topology while creating the network service, deploy the network service.
If you added the physical network function to the topology while editing a network service, deploy the modified network service.