1 # Support of Physical Deployment Units in a VNF #
4 - Gerardo Garcia (Telefonica)
5 - Alfonso Tierno (Telefonica)
6 - Francisco Javier Ramon (Telefonica)
15 **This feature obsoletes feature #641: https://osm.etsi.org/gerrit/#/c/641/**
17 This feature aims to enable the use of Network Functions where some of their
18 Deployment Units are physical (Physical Deployment Units - PDUs), so both pure
19 VNFs, pure PNFs and hybrid network functions can be seamlessly supported in an
20 interchangeable manner in a NS.
22 This feature is also expected to require a specific procedure to add PDUs to a
23 catalog per datacenter, where details of their type (so that they can be
24 pooled. e.g. GPU model), location (datacenter), reachability (e.g. IP
25 address), physical connections to the site (e.g. switches and ports where the
26 PDU is connected), etc. can be provided.
28 In this phase, it will be assumed that, on time of instantiation, these PDUs
29 would map 1-to-1 to VDU instances (or equivalent). In this phase, the same PDU
30 cannot be used twice (in the future we might review this approach).
32 ## Demo or definition of done ##
33 - Successful onboarding of a (V)NF that has 1 VDU and 1 PDU. For instance, in
34 the (V)NF, the VDU could be an SDN controller and the PDU a small physical
36 - Addition a PDUs in datacenter A of a given type.
37 - Successful deployment of a NS with the (V)NF in datacenter A.
38 - Unsuccessful deployment of a second instance of the same NS in the datacenter
39 A (not enough resources available of that PDU type).
40 - Unsuccessful deployment of the same NS in another datacenter (no PDUs of that