Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for atomic processing of a group of OpenFlow flows

IP.com Disclosure Number: IPCOM000235066D
Publication Date: 2014-Feb-26
Document File: 5 page(s) / 60K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method to allow services to group arbitrary flows and submit for provisioning. ensure atomicity of the provisioning so that either all or none of the flows get provisioned. And correlate network events with the service defined groups for alerting services of the impact of such events.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 30% of the total text.

Page 01 of 5

Method for atomic processing of a group of OpenFlow flows

Main Idea


1. Background: What is the problem solved by your invention ? Describe known solutions to this problem (if any). What are the drawbacks of such known solutions , or why is an additional solution required ? Cite any relevant technical documents or references .

The available OpenFlow controllers process individual flows, one at a time and provision these on the network. Such an approach has inherent limitations when services need to perform a logical operation that results in more than one flow that need to be provisioned on one or more switches in the network. The typical issues related to this are:


 A higher level SDN service does not have a single mechanism of associating flows related to a particular event -e.g. flows required to enable service to a particular VM/host. Thus, if a host is discovered, taken offline a FTS (Full Table Search) kind of mechanism is needed to identify the affected flows that relate to the particular service on the host. Alternatively, each such service may need to build different semantics to group such flows together.


 When certain parts of the network fails during flow installation, there is a risk of inadvertently leading to an inconsistent network. E.g. Assuming one flow per switch is required to be installed when provisioning a path, if 8 out of 10 switches are online, 2 flows will fail installation and if this were a path, it results in a dangling path. In extreme cases, this may result in loops.


2. Summary of Invention: Briefly describe the core idea of your invention (saving the details for questions #3 below). Describe the advantage (s) of using your invention instead of the known solutions described above.

The proposal is to introduce a construct of a Flow Group and mechanisms that operate on a group of flows in place of a single flow. Thus services are allowed to submit multiple flows logically grouped by a business need - in the example above one group for all flows related to a VM/host. This also allows for a mechanism to atomically provision such a group of flows by implicitly rolling back flow installations that were to fail.


3. Description: Describe how your invention works , and how it could be implemented , using text, diagrams and flow charts as appropriate .

Proposed Solution

The proposal is to introduce a construct of a Flow Group and mechanisms that operate on a group of flows in place of a single flow. Thus services are allowed to submit multiple flows logically grouped by a business need - in the example above one group for all flows related to a VM/host. This also allows for a mechanism to atomically provision such a group of flows by implicitly rolling back flow installations that were to fail.

1


Page 02 of 5

Such a flow group would have attributes as follows:


 serviceOwner - the owner of the flow group that needs to be notified when the group is impacted


 flows list - the list of flows that needs...