1 # Alternatives for underlay network management from OSM #
13 Most common VIMs (Openstack, VMware, AWS) do not provide management of native L2
14 underlay connections (E-Line, E-LAN) suitable for EPA. In the case of Openstack,
15 there are proprietary solutions based on neutron ML2 plugins for the
16 connectivity of SR-IOV interfaces. However, those solutions are not suitable for
19 * It is not possible to connect PT (pass-through) NIC interfaces (there are no
20 neutron ports associated to PT interfaces).
21 * It is also impossible to connect multitenant VNFs (using VLAN tags per tenant)
22 with single tenant VNFs, where the VLAN tag must be automatically removed/added
25 The proposal is to enable OSM to manage underlay networks directly through an
26 SDN controller (SDNC) whenever that feature is not provided by the VIM. In those
27 cases, the VIM would only in charge of the creation of VM instances and the
28 creation of overlay networks, while the SDNC, governed by OSM (the RO, in this
29 case), would be in charge of the creation and deletion of underlay networks.
31 It is devised that OSM should get from the VIM the physical allocation of the
32 interfaces (SRIOV, PT) once the VM is deployed, and it will command the SDNC to
33 connect these interfaces in E-Line or E-LAN networks. Common SDNCs that are
34 expected to be supported should be ODL and ONOS.
36 ## Demo or definition of done ##