© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
In response to #9:
Simple example 1:
NFV Use Case.
The user has a pCPE (physical CPE, think a box in a bank branch). The tenant has decided that traffic from that pCPE is to be moved through a variety of Network Service Functions, some physical, some virtual. Because the controller has full scope on the pCPE and the physical network functions, as well as being able to handle the virtual network functions for purposes of Service Function Chaining (SFC) it is handling all of that.
One of those service functions is a vCPE. The tenant would like to deploy a new VM of type vCPE via OpenStack. The downstream controller needs to (in addition to handling normal network plumbing for that VM) *know* that its has a new instance of vCPE it can use. So the tenant uses a label 'vnf-type:vCPE' to indicate it on the 'port', and the controller's SFC subsystem can pick up on that and put it into rotation to handle traffic.
Most of the use cases I've heard for labels are both dynamic and scoped to the tenant deploying the VM .