EPA and SDN assist

From OSM Public Wiki
Jump to: navigation, search


(THIS IS A DRAFT)

Introduction

OSM can manage the dataplane underlay conectivity with openflow through an external SDN network controller.

By default, when a VIM is added to OSM, it is assumed that the VIM will be in charge of this type of networks. However, when this is not the case, you can instruct OSM to take control of the underlay dataplane connectivity on behalf of the VIM, with the SDN assist capability.

OSM-RO uses a library offered by openvim for this task. Currently there are plugins for FlodLight, ONOS and OpenDayLight OpenVIM installation (Release TWO)#Openflow_controller

The required external components are:

  • An external SDN controller
  • A dataplane swith openflow able, that will connect the physical interfaces of the VIM compute nodes.
  • The mapping between the switch ports (identified by name) and the compute node interfaces (identified by host-id and PCI address)
  • Some VIMs as openstack requires admin credentials in order to be able to get the physical place of the SRIOV/passthrough VM interfaces

Adding a SDN controller to OSM

This is done through the RO CLI.

Enter in the RO container (lxc exec RO bash) and type

export OPENMANO_TENANT=osm   # Indicate the RO tenant to use
root@RO:~# openmano sdn-controller-create mySDN --ip=192.168.15.2 --port=8080 --dpid=56:55:12:12:12:12:12:12 --user sdnuser --passwd sdnpasswd --type 
onos
98113d4a-51b7-11e7-8f07-00163e1229e4   mySDN                ACTIV
root@RO:~# openmano sdn-controller-list
{
   "sdn_controllers": [
       {
           "status": "ACTIVE", 
           "password": "sdnpasswd", 
           "uuid": "98113d4a-51b7-11e7-8f07-00163e1229e4", 
           "last_error": null, 
           "dpid": "56:55:12:12:12:12:12:12", 
           "version": null, 
           "user": "sdnuser", 
           "ip": "192.168.15.2", 
           "nets_with_same_vlan": "false", 
           "type": "onos", 
           "port": 8080, 
           "name": "mySDN"
       }
   ]
}

You can manage SDN controllers with sdn-controller-create/list/edit/delete Note that at SDN creation it is not checked the connectivity and credentials

Asociate a SDN with the VIM

If we check the information of the datacenter we can see no informatio about the sdn in the config section:

root@RO:~# openmano datacenter-list test -vvv
datacenter:
   config: null
   created_at: '2017-06-02T07:55:41'
   description: test
   name: test
   type: openstack
   uuid: dfcd6ca2-4768-11e7-8f07-00163e1229e4
   vim_tenants:
   -   config:
           dataplane_physical_net: physnet_sriov
           use_floating_ip: true
       passwd: '******'
       user: osm
       vim_tenant_id: null
       vim_tenant_name: osm
   vim_url: http://10.0.0.12:5000/v2.0
   vim_url_admin: null

In order to add the sdn controller to the datacenter:

root@RO:~# openmano datacenter-edit test --sdn-controller mySDN
 Edit datacenter test (y/N)? y
dfcd6ca2-4768-11e7-8f07-00163e1229e4   test                2017-06-02T07:55:41 

And now we can see this information in the datacenter:

root@RO:~# openmano datacenter-list test -vvv
datacenter:
   config:
       sdn-controller: 98113d4a-51b7-11e7-8f07-00163e1229e4
   config: null
   created_at: '2017-06-02T07:55:41'
   description: test
   name: test
   type: openstack
   uuid: dfcd6ca2-4768-11e7-8f07-00163e1229e4
   vim_tenants:
   -   config:
           dataplane_physical_net: physnet_sriov
           use_floating_ip: true
       passwd: '******'
       user: osm
       vim_tenant_id: null
       vim_tenant_name: osm
   vim_url: http://10.0.0.12:5000/v2.0
   vim_url_admin: null

In order to remove the sdn controller:

root@RO:~# openmano datacenter-edit test --sdn-controller null
 Edit datacenter test (y/N)? y
dfcd6ca2-4768-11e7-8f07-00163e1229e4   test                2017-06-02T07:55:41

Adding a port mapping

TBC

Managing dataplane networks with external conectivity

TBC

Additional information

TBC Create a new SDN plugin