...
The network between the BRG and the BNG is specific to a particular BNG instance, and thus it is reasonable to model it as part of the same Service (and Service instance) as the BNG.
In the "real world", each instance of the Customer Service will be comprised of:
- A BRG, which will be a physical device (PNF) dedicated to the customer's service instance.
- A vG, which is a virtual network function that is dedicated to the customer's service instance.
- A "slice" of functionality of the vGMUX, which provides a "cross connect" function between the BRG and vG. We use the term "slide" informally to convey the sense that something (capacity) is consumed and dedicated (configuration record) in the vGMUX for this customer's service instance. The way in which SDC models a "slice" of functionality of a VNF is through the "Allotted Resource" construct, because what is being consumed by the customer's service instance is an "allotment" of capacity and configuration from the underlying vGMUX. We will use the term
Because in this sense the vGMUX is providing a "service" an allotment of which is being consumed, we consider the Allotted
As a Release 1 ONAP "stretch goal", we will also attempt to demonstrate how a standalone general TOSCA Orchestrator can be incorporated into SO to provide the "cloud resource orchestration" functionality without relying on HEAT orchestration to provide this functionality. As such we will model the "vCpeCoreInfra" Service in a manner that does not leverage HEAT templates, but rather as pure TOSCA.
...