QuantumServicesInsertion - Revision history

Corvus at 21:44, 16 February 2013

2013-02-16T21:44:01Z

Edgar at 22:24, 2 January 2012

2012-01-02T22:24:18Z

Emagana at 22:24, 2 January 2012

2012-01-02T22:24:18Z

Edgar at 22:04, 2 January 2012

2012-01-02T22:04:23Z

Emagana at 22:04, 2 January 2012

2012-01-02T22:04:23Z

Edgar at 22:42, 2 December 2011

2011-12-02T22:42:08Z

Emagana at 22:42, 2 December 2011

2011-12-02T22:42:08Z

Edgar at 21:29, 1 December 2011

2011-12-01T21:29:59Z

Emagana at 21:29, 1 December 2011

2011-12-01T21:29:59Z

Edgar at 19:54, 1 December 2011

2011-12-01T19:54:28Z

@@ Line 1: / Line 1: @@
 = [[OpenStack]] Networking Services Framework and Model =
 * '''Launchpad Entry''': [https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper services-insertion]
@@ Line 55: / Line 54: @@
 In this scenario, CSP has been deployed a firewall for all incoming traffic to “Enterprise-B” applications. SP manages and maintenance this networking service (firewall) whereas Enterprise-B does not have any control over it. This use case makes sense for the CSP to become more competitive versus other CSPs and also to enhance connectivity performance, security and scalability for its customers.
-''' [[Image:QuantumServicesInsertion$sp-inserting-services.png]] '''
+''' [[Image:sp-inserting-services.png]] '''
 '''Tenants deploy and administrate network services'''
@@ Line 63: / Line 62: @@
 In this case Enterprise-B has decided to request a firewall services for all its traffic on the Cloud Data Center, this firewall service is deployed and maintained by the CSP. Enterprise B deploys and controls a web optimization service for network segment “V” and Application Control Engine on network “X”. On the other hand, Enterprise A does not require the firewall services offered by the CSP because its network “Z” has a VPN service activated and it is good enough for the applications running on network “Z”.
-''' [[Image:QuantumServicesInsertion$enterprise-inserting-services.png]] '''
+''' [[Image:enterprise-inserting-services.png]] '''
 '''Services Insertion Wiring Modes'''
@@ Line 73: / Line 72: @@
 In this mode, the service is placed in the path of the traffic to the server VMs, by splitting the network into two, and having the service bridge between the two, in the process applying the service. This is achievable with the current set of Quantum APIs. HA in this mode is achieved through an external monitoring entity that monitors the health of the service and kill/re-spins if it went down.
-''' [[Image:QuantumServicesInsertion$in-path.png]] '''
+''' [[Image:in-path.png]] '''
 * Out-of-Path (Redirection)
@@ Line 79: / Line 78: @@
 In this mode, the service (single node or a cluster of nodes) is placed out of the normal traffic flow path, and the gateway redirects the candidate set of traffic to the service. After the service has been provided to the traffic, it is returned back to the gateway for forwarding to the end host.
-''' [[Image:QuantumServicesInsertion$out-of-path.png]] '''
+''' [[Image:out-of-path.png]] '''
 HA in this mode is achieved through an external monitoring entity as in the in-path case. In addition, the VPN gateway could also monitor the state of the service and choose to make alternate redirection decisions.
@@ Line 122: / Line 121: @@
 * plug_iface (tenent_id, net_id, port_id) → Web Opt
-''' [[Image:QuantumServicesInsertion$usecase-serviceinsertion.png]] '''
+''' [[Image:usecase-serviceinsertion.png]] '''

@@ Line 83: / Line 83: @@
 HA in this mode is achieved through an external monitoring entity as in the in-path case. In addition, the VPN gateway could also monitor the state of the service and choose to make alternate redirection decisions.
-=== Use Case 1- Tenants Deploys and Administrate a Service: ===
+''' Use Case - Tenants Deploys and Administrate a Service: '''
 Let's describe a use case where a CSP offers not just conventional computational resources but also networking resources through Quantum APIs. We are assuming that Tenant-A has already few applications deployed along three different networks identified as Network Z, V and X.  All services in this use case are single services and they will be inserted using the “In-Path” mode.
@@ Line 91: / Line 91: @@
 Enterprise A:
 * create_network (net_name, tenant_id) → network-G
 * create_network (net_name, tenant_id) → network-F
-* create_multiport (net_id, number_ports, tenant_id) → Firewall
+* create_port (net_id, tenant_id) → Firewall
-* create_multiport (net_id, number_ports, tenant_id) → Wan Opt
+* create_port (net_id, tenant_id) → Wan Opt
 * unplug_iface (tenent_id, net_id, port_id) → network-X
 * unplug_iface (tenent_id, net_id, port_id) → network-V
-Unplugging interfaces between the GW and Network X and V
+Instantiate both services from VM images:
 * euca-run-instances (Firewall)
 * euca-run-instances (Wan Opt)
-Instantiate both services from VM images
+Connect the interfaces to their corresponding ports
 * plug_iface (tenent_id, net_id, port_id) → From Net-V to FW
 * plug_iface (tenent_id, net_id, port_id) → From Net-F to FW
@@ Line 120: / Line 118: @@
 * create_network (net_name, tenant_id) → management-network
-* create_multiport (net_id, number_ports, tenant_id)
+* create_port (net_id, tenant_id)
 * plug_iface (tenent_id, net_id, port_id) → Firewall
 * plug_iface (tenent_id, net_id, port_id) → Web Opt
-Use Case 2 - CSP Deploys a Service but Tenant Administrate it:
+''' [[Image:QuantumServicesInsertion$usecase-serviceinsertion.png]] '''

@@ Line 83: / Line 83: @@
 HA in this mode is achieved through an external monitoring entity as in the in-path case. In addition, the VPN gateway could also monitor the state of the service and choose to make alternate redirection decisions.
-=== Use Case 1- Tenants Deploys and Administrate a Service: ===
+''' Use Case - Tenants Deploys and Administrate a Service: '''
 Let's describe a use case where a CSP offers not just conventional computational resources but also networking resources through Quantum APIs. We are assuming that Tenant-A has already few applications deployed along three different networks identified as Network Z, V and X.  All services in this use case are single services and they will be inserted using the “In-Path” mode.
@@ Line 91: / Line 91: @@
 Enterprise A:
 * create_network (net_name, tenant_id) → network-G
 * create_network (net_name, tenant_id) → network-F
-* create_multiport (net_id, number_ports, tenant_id) → Firewall
+* create_port (net_id, tenant_id) → Firewall
-* create_multiport (net_id, number_ports, tenant_id) → Wan Opt
+* create_port (net_id, tenant_id) → Wan Opt
 * unplug_iface (tenent_id, net_id, port_id) → network-X
 * unplug_iface (tenent_id, net_id, port_id) → network-V
-Unplugging interfaces between the GW and Network X and V
+Instantiate both services from VM images:
 * euca-run-instances (Firewall)
 * euca-run-instances (Wan Opt)
-Instantiate both services from VM images
+Connect the interfaces to their corresponding ports
 * plug_iface (tenent_id, net_id, port_id) → From Net-V to FW
 * plug_iface (tenent_id, net_id, port_id) → From Net-F to FW
@@ Line 120: / Line 118: @@
 * create_network (net_name, tenant_id) → management-network
-* create_multiport (net_id, number_ports, tenant_id)
+* create_port (net_id, tenant_id)
 * plug_iface (tenent_id, net_id, port_id) → Firewall
 * plug_iface (tenent_id, net_id, port_id) → Web Opt
-Use Case 2 - CSP Deploys a Service but Tenant Administrate it:
+''' [[Image:QuantumServicesInsertion$usecase-serviceinsertion.png]] '''

@@ Line 65: / Line 65: @@
 ''' [[Image:QuantumServicesInsertion$enterprise-inserting-services.png]] '''
-'''CSPs deploy and Tenants administrate network services'''
+'''Services Insertion Wiring Modes'''
 Regardless the service insertion model used and the type of service that will be inserted in the network, there are different modes to wire a service into the network. These are the two proposing configurations:

@@ Line 65: / Line 65: @@
 ''' [[Image:QuantumServicesInsertion$enterprise-inserting-services.png]] '''
-'''CSPs deploy and Tenants administrate network services'''
+'''Services Insertion Wiring Modes'''
 Regardless the service insertion model used and the type of service that will be inserted in the network, there are different modes to wire a service into the network. These are the two proposing configurations:

@@ Line 3: / Line 3: @@
 * '''Launchpad Entry''': [https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper services-insertion]
 * '''Created''': [https://launchpad.net/~emagana Edgar Magana]
-* '''Contributors''': [https://launchpad.net/~emagana Edgar Magana] & everybody else who wants to join!
+* '''Contributors''': [https://launchpad.net/~emagana Edgar Magana], Ram Durairaj, Mani Ramasamy, Nat Chidambaram & everybody else who wants to join!
 == Objective ==