From a31442758c5aaeb7cd5c96b0c2f6e1f2a1e6464f Mon Sep 17 00:00:00 2001 From: tierno Date: Tue, 17 Dec 2019 11:35:11 +0000 Subject: [PATCH] PDU selection at instantiation Signed-off-by: tierno --- 06-osm-platform-configuration.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/06-osm-platform-configuration.md b/06-osm-platform-configuration.md index 2cf8591..55d8a7d 100644 --- a/06-osm-platform-configuration.md +++ b/06-osm-platform-configuration.md @@ -103,7 +103,7 @@ OSM can handle Physical Network Functions through managing the lifecycle, in par Some relevant concepts are: - PNF: Physical network function. It refers to a HW box that provides a networking function. For example: Routers, firewalls and load balancers. -- PDU: Physical deployment unit. It refers to the instance of the PNF that will be managed. +- PDU: Physical deployment unit. It refers to the instance of the PNF in a VIM or VIM_account that will be managed. - HNF: Hybrid network function: Network function composed of both physical and virtual elements. In OSM, there are no fundamental differences between modelling a VNF, a PNF or a Hybrid Network Function (HNF). In those cases where we want to define NS packages consisting of PNF packages or HNF packages, OSM needs to be instructed about the available PDUs. @@ -138,7 +138,7 @@ Then, using the OSM CLI, the yaml file is used to register the PDU. osm pdu-create --descriptor_file PDU_router.yaml ``` -Finally, the PDU is included in the descriptor as it was any VDU (with the applicable parameters), and Day1/2 configurations can be applied to it. For example, a PDU could be modeled like this: +Finally, the PDU is included in the descriptor as it was any VDU (with the applicable parameters) by setting `pdu-type`, and Day1/2 configurations can be applied to it. For example, a PDU could be modeled like this: ```yaml vdu: @@ -153,6 +153,8 @@ Finally, the PDU is included in the descriptor as it was any VDU (with the appli ... ``` +At instantiation time, OSM looks for a free PDU in the target `VIM_account` with the same type declared at `VNFD.vdu.pdu_type` and having al least all the interfaces declared at `VNFD.vdu`, that is, each `VNFD.vdu.interfaces.name` must be present at `PDU.interfaces.name`. + ## Intra-VIM SDN management (for SDN Assist) TODO: Page in elaboration. -- GitLab