WIM - Revision history

Sasiain at 13:51, 18 September 2019

2019-09-18T13:51:10Z

← Older revision		Revision as of 13:51, 18 September 2019
Line 16:		Line 16:
	==WIM types==		==WIM types==
	*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466.		*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466.
	*'''DynPaC''': the DynPaC (Dynamic Path Computation Framework) WIM connector allows the creation (and deletion) of layer two services between two VNFs ~~in OSM~~ with given bandwidth requirements.		*'''DynPaC''': the DynPaC (Dynamic Path Computation Framework) WIM connector allows the creation (and deletion) of layer two services between two VNFs with given bandwidth requirements.

	=Network Service creation=		=Network Service creation=

Sasiain: /* DynPaC */

2019-09-18T12:01:56Z

DynPaC

← Older revision		Revision as of 12:01, 18 September 2019
Line 64:		Line 64:
	"<datacenter switch dpid>" and "<datacenter switch port>" here are the same ones as pop_switch_dpid and pop_switch_port as will be seen later in the WIM port mapping example.		"<datacenter switch dpid>" and "<datacenter switch port>" here are the same ones as pop_switch_dpid and pop_switch_port as will be seen later in the WIM port mapping example.

	In order to add a DynPaC WIM to OSM that connects two datacenters (VIMs) with the wim-create command, the file passed to the --wim_port_mapping parameter should have the following structure:		In order to add a DynPaC WIM to OSM that connects two datacenters (VIMs) with the wim-create command, the file passed to the --wim_port_mapping parameter should have the following structure. For example:

	<pre>		<pre>
	- datacenter_name: "~~<vim-~~1~~-name>~~"		- datacenter_name: "VIM 1"
	pop_wan_mappings:		pop_wan_mappings:
	- pop_switch_dpid: "~~<dpid-pop-~~1>"		- pop_switch_dpid: "DC 1"
	pop_switch_port: "~~<port-pop-1>~~"		pop_switch_port: "P1A"
	wan_service_mapping_info:		wan_service_mapping_info:
	mapping_type: 'dpid-port'		mapping_type: 'dpid-port'
	wan_switch_dpid: "~~<dpid-wan-~~1>"		wan_switch_dpid: "WAN 1"
	wan_switch_port: "~~<port-wan-1>~~"		wan_switch_port: "P1B"
	- datacenter_name: "~~<vim-~~2~~-name>~~"		- datacenter_name: "VIM 2"
	pop_wan_mappings:		pop_wan_mappings:
	- pop_switch_dpid: "~~<dpid-pop-~~2>"		- pop_switch_dpid: "DC 2"
	pop_switch_port: "~~<port-pop-2>~~"		pop_switch_port: "P2B"
	wan_service_mapping_info:		wan_service_mapping_info:
	mapping_type: 'dpid-port'		mapping_type: 'dpid-port'
	wan_switch_dpid: "~~<dpid-wan-~~2>"		wan_switch_dpid: "WAN 2"
	wan_switch_port: "~~<port-wan-2>~~"		wan_switch_port: "P2A"
	</pre>		</pre>

			[[File:wim_schema.png\|750px]]

	Where:		Where:
	* ~~"<vim-1-name>" and "<vim-2-name>"~~ are the names of the two VIMs (as displayed by osm vim-list)		* '''datacenter_name''' are the names of the two VIMs (as displayed by osm vim-list)
	* ~~Each "<dpid-pop-N>"~~ is the datapath ID of the datacenter switch that provides the VIM connectivity		* '''pop_switch_dpid''' is the datapath ID of the datacenter switch that provides the VIM connectivity
	* ~~Each "<port-pop-N>"~~ is the port (Openflow number) of the datacenter switch that connects to the immediate WAN switch		* '''pop_switch_port''' is the port (Openflow number) of the datacenter switch that connects to the immediate WAN switch
	* ~~Each "<dpid-wan-N>"~~ is the datapath ID of the immediate WAN switch		* '''wan_switch_dpid''' is the datapath ID of the immediate WAN switch
	* ~~Each "<port-wan-N>"~~ is the port (Openflow number) of the immediate WAN switch that connects to the datacenter switch		* '''wan_switch_port''' is the port (Openflow number) of the immediate WAN switch that connects to the datacenter switch

	~~Which represents:~~
	~~<pre>~~
	~~[dpid-pop-1]-(port-pop-1)-----(port-wan-1)-[dpid-wan-1]-----{WAN}-----[dpid-wan-2]-(port-wan-2)-----(port-pop-2)-[dpid-pop-2]~~
	~~</pre>~~

	DPIDs are in of:xxxxxxxxxxxxxxxx format.		DPIDs are in of:xxxxxxxxxxxxxxxx format.

Pajaresmarti at 11:52, 4 July 2019

2019-07-04T11:52:05Z

← Older revision		Revision as of 11:52, 4 July 2019
Line 51:		Line 51:
	*'''site-id''': UUID of the desried site.		*'''site-id''': UUID of the desried site.
	*'''bearer-reference''': UUID of the desired port of the site to be added to the Network Service.		*'''bearer-reference''': UUID of the desired port of the site to be added to the Network Service.



	=DynPaC=		=DynPaC=

Pajaresmarti at 11:33, 4 July 2019

2019-07-04T11:33:04Z

← Older revision		Revision as of 11:33, 4 July 2019
Line 47:		Line 47:
	For each port of each site wanted to be added to the Network Service, it's needed a port mapping like previous one. The parameters nedded for each port mapping are:		For each port of each site wanted to be added to the Network Service, it's needed a port mapping like previous one. The parameters nedded for each port mapping are:

	*"datacenter_name": name of the desired site.		*'''datacenter_name''': name of the desired site.
	*"wan_service_endpoint_id": UUID of the desired WAN endpoint.		*'''wan_service_endpoint_id''': UUID of the desired WAN endpoint.
	*"site-id": UUID of the desried site.		*'''site-id''': UUID of the desried site.
	*"bearer-reference": UUID of the desired port of the site to be added to the Network Service.		*'''bearer-reference''': UUID of the desired port of the site to be added to the Network Service.

Pajaresmarti at 11:31, 4 July 2019

2019-07-04T11:31:11Z

@@ Line 32: / Line 32: @@
 ==L2SM Plugin port mapping==
-As it was indicated, the port maping should be adapted to the WIM configuration. In this case, to configure the WIM, the port mapping file ''.yml'' should be created following the wim_port_mapping_desc schema, as in the following example, the network has two sites:
+As it was indicated, the port maping should be adapted to the WIM configuration. In this case, to configure the WIM, the port mapping file ''.yml'' should be created following the wim_port_mapping_desc schema, as in the following example:
 =DynPaC=

Sasiain at 12:16, 3 July 2019

2019-07-03T12:16:50Z

@@ Line 16: / Line 16: @@
 ==WIM types==
 *'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466.
 =L2SM Plugin=
@@ Line 51: / Line 60: @@
+    }
+  }

Pajaresmarti at 07:34, 2 July 2019

2019-07-02T07:34:52Z

← Older revision		Revision as of 07:34, 2 July 2019
Line 20:		Line 20:
	The L2SM WIM 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 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 ~~[https://tools.ietf.org/html/rfc8466]~~.		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.

	==L2SM Plugin port mapping==		==L2SM Plugin port mapping==

Pajaresmarti at 07:34, 2 July 2019

2019-07-02T07:34:20Z

← Older revision		Revision as of 07:34, 2 July 2019
Line 15:		Line 15:

	==WIM types==		==WIM types==
	*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466..		*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466.

	=L2SM Plugin=		=L2SM Plugin=

Gonzalezdedi: minor edits

2019-07-01T13:38:18Z

minor edits

← Older revision		Revision as of 13:38, 1 July 2019
Line 15:		Line 15:

	==WIM types==		==WIM types==
	*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM. ~~The L2SM Plugin should be used~~.		*'''ietfl2vpn''': this type allows to manage L2VPN services from OSM using a WIM that exposes a Restconf Interface with the Yang L2SM model defined in RFC 8466..

	=L2SM Plugin=		=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 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 [https://tools.ietf.org/html/rfc8466].		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 [https://tools.ietf.org/html/rfc8466].

	==L2SM Plugin port mapping==		==L2SM Plugin port mapping==
	As it was indicated, the port maping should be adapted to the WIM configuration. In this case, to configure the WIM, the port mapping file ''.yml'' should be created following the wim_port_mapping_desc schema, as in the following example, the network has two sites ~~(Openstacks)~~:		As it was indicated, the port maping should be adapted to the WIM configuration. In this case, to configure the WIM, the port mapping file ''.yml'' should be created following the wim_port_mapping_desc schema, as in the following example, the network has two sites:

	{		{

Pajaresmarti at 11:26, 1 July 2019

2019-07-01T11:26:03Z

← Older revision		Revision as of 11:26, 1 July 2019
Line 23:		Line 23:

	==L2SM Plugin port mapping==		==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, the network has two sites (Openstacks):		As it was indicated, the port maping should be adapted to the WIM configuration. In this case, to configure the WIM, the port mapping file ''.yml'' should be created following the wim_port_mapping_desc schema, as in the following example, the network has two sites (Openstacks):

	{		{