WIM

Introduction

WIM is the acronym for WAN Infrastructure Manager, which is a specialized VIM that allows to establish connectivity between different network endpoints at different NFVI-PoPs in the context of a multi-site service Wide Area Network (WAN).

For the establishment of the network connectivity, the WIM may rely on network controllers that handle the fulfilment of the connectivity at a lower level, potentially making use of different network technologies and protocols. The WIM offers to the consumers an abstraction of such network connectivity to ease the provisioning and monitoring of it.

WIM setup through OSM client

The following is the command needed to perform to setup the WIM in OSM. It must be filled with the appropriate parameters (e.g. site name: “wim-demo”, IP address: 10.10.10.10:8080, user: “username”, password: “userpwd”, wim_type: “type” port mapping: “sample_port_mapping.yml”)

osm wim-create --name wim-demo --url http://10.10.10.10:8080 --user username --password userpwd --wim_type type   --description "Demo WIM"   --wim_port_mapping sample_port_mapping.yml

WIM port mapping

The port mapping file indicated above should be adapted to the desired WIM configuration. It should be an .yml file that contains the information of the openstack where the WIM is going to be configured, following one of these schemas [1]

WIM types

• ietfl2vpn: this type allows to manage L2VPN services from OSM. The L2SM Plugin should be used.

L2SM Plugin

The L2SM Plugin is included in the RO component of the OSM version six that allows the management of WIM Services. Those WIMs should be created to support connectivity between VNFs running in different VIMs.

The L2SM WIM plugin allows connecting the OSM to handle the lifecycle of a layer 2 VPN service, request creation, modification and deletion, by utilizing the service delivery model defined in RFC 8466 [2].

L2SM Plugin port mapping

As it was indicated, the port maping should be adapted to the WIM configuration. In this case, for configure the WIM, the port mapping file .yml should be created following the wim_port_mapping_desc schema, as in the following example, where two sites are in the network:

{
  '1': {
    'created_at': '2019-06-04T10:17:03',
    'datacenter_id': '1ca55b42-8625-11e9-887d-02420aff009a',
    'id': 7L,
    'modified_at': '2019-06-04T10:17:03',
    'wan_service_endpoint_id': '1',
    'wan_service_mapping_info': {
      'mapping_type': 'direct-connect1',
      'site-id': '1'
    },
    'wim_id': 'e5dbc834-86b1-11e9-bd95-02420aff0020'
  },
  '2': {
    'created_at': '2019-06-04T10:17:03',
    'datacenter_id': '1cf58c3e-8625-11e9-887d-02420aff009a',
    'id': 8L,
    'modified_at': '2019-06-04T10:17:03',
    'wan_service_endpoint_id': '2',
    'wan_service_mapping_info': {
      'mapping_type': 'direct-connect2',
      'site-id': '2'
    },
    'wim_id': 'e5dbc834-86b1-11e9-bd95-02420aff0020'
  }
}