Patent Grant
9008087
Many current enterprises have large and sophisticated networks comprising switches, hubs, routers, servers, workstations and other networked devices, which support a variety of connections, applications and systems. The increased sophistication of computer networking, including virtual machine migration, dynamic workloads, multi-tenancy, and customer specific quality of service and security configurations require a better paradigm for network control. Networks have traditionally been managed through low-level configuration of individual components. Network configurations often depend on the underlying network: for example, blocking a user's access with an access control list (“ACL”) entry requires knowing the user's current IP address. More complicated tasks require more extensive network knowledge: forcing guest users' port 80 traffic to traverse an HTTP proxy requires knowing the current network topology and the location of each guest. This process is of increased difficulty where the network switching elements are shared across multiple users.
In response, there is a growing movement, driven by both industry and academia, towards a new network control paradigm called Software-Defined Networking (SDN). In the SDN paradigm, a network controller, running on one or more servers in a network, controls, maintains, and implements control logic that governs the forwarding behavior of shared network switching elements on a per user basis. Making network management decisions often requires knowledge of the network state. To facilitate management decision making, the network controller creates and maintains a view of the network state and provides an application programming interface upon which management applications may access a view of the network state.
Three of the many challenges of large networks (including datacenters and the enterprise) are scalability, mobility, and multi-tenancy and often the approaches taken to address one hamper the other. For instance, one can easily provide network mobility for virtual machines (VMs) within an L2 domain, but L2 domains cannot scale to large sizes. Also, retaining tenant isolation greatly complicates mobility. Despite the high-level interest in SDN, no existing products have been able to satisfy all of these requirements.
Some embodiments of the invention provide a system that allows several different logical datapath sets to be specified for several different users through one or more shared network infrastructure switching elements (referred to as “switching elements” below). In some embodiments, the system includes a set of software tools that allows the system to accept logical datapath sets from users and to configure the switching elements to implement these logical datapath sets. These software tools allow the system to virtualize control of the shared switching elements and the network that is defined by the connections between these shared switching elements, in a manner that prevents the different users from viewing or controlling each other's logical datapath sets (i.e., each other's switching logic) while sharing the same switching elements.
In some embodiments, one of the software tools that allows the system to virtualize control of a set of switching elements (i.e., to allow several users to share the same switching elements without viewing or controlling each other's logical datapath sets) is an intermediate data storage structure that (1) stores the state of the network, (2) receives and records modifications to different parts of the network from different users, and (3), in some embodiments, provides different views of the state of the network to different users. For instance, in some embodiments, the intermediate data storage structure is a network information base (NIB) data structure that stores the state of the network that is defined by one or more switching elements. The system uses this NIB data structure as an intermediate storage structure for reading the state of the network and writing modifications to the state of the network. In some embodiments, the NIB also stores the logical configuration and the logical state for each user specified logical datapath set. In these embodiments, the information in the NIB that represents the state of the actual switching elements accounts for only a subset of the total information stored in the NIB.
In some embodiments, the system has (1) a network operating system (NOS) to create and maintain the NIB storage structure, and (2) one or more applications that run on top of the NOS to specify logic for reading values from and writing values to the NIB. When the NIB is modified in order to effectuate a change in the switching logic of a switching element, the NOS of some embodiments also propagates the modification to the switching element.
The system of different embodiments uses the NIB differently to virtualize access to the shared switching elements and network. In some embodiments, the system provides different views of the NIB to different users in order to ensure that different users do not have direct view and control over each other's switching logic. For instance, in some embodiments, the NIB is a hierarchical data structure that represents different attributes of different switching elements as elements (e.g., different nodes) in a hierarchy. The NIB in some of these embodiments is a multi-layer hierarchical data structure, with each layer having a hierarchical structure and one or more elements (e.g., nodes) on each layer linked to one or more elements (e.g., nodes) on another layer. In some embodiments, the lowest layer elements correspond to the actual switching elements and their attributes, while each of the higher layer elements serve as abstractions of the actual switching elements and their attributes. As further described below, some of these higher layer elements are used in some embodiments to show different abstract switching elements and/or switching element attributes to different users in a virtualized control system.
In some embodiments, the definition of different NIB elements at different hierarchical levels in the NIB and the definition of the links between these elements are used by the developers of the applications that run on top of the NOS in order to define the operations of these applications. For instance, in some embodiments, the developer of an application running on top of the NOS uses these definitions to enumerate how the application is to map the logical datapath sets of the user to the physical switching elements of the control system. Under this approach, the developer would have to enumerate all different scenarios that the control system may encounter and the mapping operation of the application for each scenario. This type of network virtualization (in which different views of the NIB are provided to different users) is referred to below as Type I network virtualization.
Another type of network virtualization, which is referred to below as Type II network virtualization, does not require the application developers to have intimate knowledge of the NIB elements and the links (if any) in the NIB between these elements. Instead, this type of virtualization allows the application to simply provide user specified, logical switching element attributes in the form of one or more tables, which are then mapped to NIB records by a table mapping engine. In other words, the Type II virtualized system of some embodiments accepts the logical switching element configurations (e.g., access control list table configurations, L2 table configurations, L3 table configurations, etc.) that the user defines without referencing any operational state of the switching elements in a particular network configuration. It then maps the logical switching element configurations to the switching element configurations stored in the NIB.
To perform this mapping, the system of some embodiments uses a database table mapping engine to map input tables, which are created from (1) logical switching configuration attributes, and (2) a set of properties associated with switching elements used by the system, to output tables. The content of these output tables are then transferred to the NIB elements. In some embodiments, the system uses a variation of the datalog database language, called n Log, to create the table mapping engine that maps input tables containing logical datapath data and switching element attributes to the output tables. Like datalog, n Log provides a few declaratory rules and operators that allow a developer to specify different operations that are to be performed upon the occurrence of different events. In some embodiments, n Log provides a limited subset of the operators that are provided by datalog in order to increase the operational speed of n Log. For instance, in some embodiments, n Log only allows the AND operator to be used in any of the declaratory rules.
The declaratory rules and operations that are specified through n Log are then compiled into a much larger set of rules by an n Log compiler. In some embodiments, this compiler translates each rule that is meant to address an event into several sets of database join operations. Collectively the larger set of rules forms the table-mapping rules engine that is referred to below as the n Log engine. In some embodiments, the n Log virtualization engine also provides feedback (e.g., from one or more of the output tables or from NIB records that are updated to reflect values stored in the output tables) to the user in order to provide the user with state information about the logical datapath set that he or she created. In this manner, the updates that the user gets are expressed in terms of the logical space that the user understands and not in terms of the underlying switching element states, which the user does not understand.
The use of n Log serves as a significant distinction between Type I virtualized control systems and Type II virtualized control systems, even for Type II systems that store user specified logical datapath sets in the NIB. This is because n Log provides a machine-generated rules engine that addresses the mapping between the logical and physical domains in a more robust, comprehensive manner than the hand-coded approach used for Type I virtualized control systems. In the Type I control systems, the application developers need to have a detailed understanding of the NIB structure and need to use this detailed understanding to write code that addresses all possible conditions that the control system would encounter at runtime. On the other hand, in Type II control systems, the application developers only need to produce applications that express the user-specified logical datapath sets in terms of one or more tables, which are then mapped in an automated manner to output tables and later transferred from the output tables to the NIB. This approach allows the Type II virtualized systems to forego maintaining the data regarding the logical datapath sets in the NIB. However, some embodiments maintain this data in the NIB in order to distribute this data among other NOS instances, as further described below.
As apparent from the above discussion, the applications that run on top of a NOS instance can perform several different sets of operations in several different embodiments of the invention. Examples of such operations include providing an interface to a user to access NIB data regarding the user's switching configuration, providing different layered NIB views to different users, providing control logic for modifying the provided NIB data, providing logic for propagating received modifications to the NIB, etc.
In some embodiments, the system embeds some or all such operations in the NOS instead of including them in an application operating on top of the NOS. Alternatively, in other embodiments, the system separates some or all of these operations into different subsets of operations and then has two or more applications that operate above the NOS perform the different subsets of operations. One such system runs two applications on top of the NOS: a control application and a virtualization application. In some embodiments, the control application allows a user to specify and populate logical datapath sets, while the virtualization application implements the specified logical datapath sets by mapping the logical datapath sets to the physical switching infrastructure. In some embodiments, the virtualization application translates control application input into records that are written into the NIB, and then these records are subsequently transferred from the NIB to the switching infrastructure through the operation of the NOS. In some embodiments, the NIB stores both the logical datapath set input received through the control application and the NIB records that are produced by the virtualization application.
In some embodiments, the control application can receive switching infrastructure data from the NIB. In response to this data, the control application may modify record(s) associated with one or more logical datapath sets (LDPS). Any such modified LDPS record would then be translated to one or more physical switching infrastructure records by the virtualization application, which might then be transferred to the physical switching infrastructure by the NOS.
In some embodiments, the NIB stores data regarding each switching element within the network infrastructure of a system, while in other embodiments, the NIB stores state information about only switching elements at the edge of a network infrastructure. In some embodiments, edge switching elements are switching elements that have direct connections with the computing devices of the users, while non-edge switching elements only connect to edge switching elements and other non-edge switching elements.
The system of some embodiments only controls edge switches (i.e., only maintains data in the NIB regarding edge switches) for several reasons. Controlling edge switches provides the system with a sufficient mechanism for maintaining isolation between computing devices, which is needed, as opposed to maintaining isolation between all switch elements, which is not needed. The interior switches forward between switching elements. The edge switches forward between computing devices and other network elements. Thus, the system can maintain user isolation simply by controlling the edge switching elements because the edge switching elements are the last switches in line to forward packets to hosts.
Controlling only edge switches also allows the system to be deployed independent of concerns about the hardware vendor of the non-edge switches. Deploying at the edge allows the edge switches to treat the internal nodes of the network as simply a collection of elements that moves packets without considering the hardware makeup of these internal nodes. Also, controlling only edge switches makes distributing switching logic computationally easier. Controlling only edge switches also enables non-disruptive deployment of the system. Edge switching solutions can be added as top of rack switches without disrupting the configuration of the non-edge switches.
In addition to controlling edge switches, the network control system of some embodiments also utilizes and controls non-edge switches that are inserted in the switch network hierarchy to simplify and/or facilitate the operation of the controlled edge switches. For instance, in some embodiments, the control system requires the switches that it controls to be interconnected in a hierarchical switching architecture that has several edge switches as the leaf nodes in this switching architecture and one or more non-edge switches as the non-leaf nodes in this architecture. In some such embodiments, each edge switch connects to one or more of the non-leaf switches, and uses such non-leaf switches to facilitate its communication with other edge switches. Examples of functions that such non-leaf switches provide to facilitate such communications between edge switches in some embodiments include (1) routing of a packet with an unknown destination address (e.g., unknown MAC address) to the non-leaf switch so that this switch can route this packet to the appropriate edge switch, (2) routing a multicast or broadcast packet to the non-leaf switch so that this switch can convert this packet to a series of unicast packets for routing to the desired destinations, (3) bridging remote managed networks that are separated by one or more networks, and (4) bridging a managed network with an unmanaged network.
Some embodiments employ one level of non-leaf (non-edge) switches that connect to edge switches and in some cases to other non-leaf switches. Other embodiments, on the other hand, employ multiple levels of non-leaf switches, with each level of non-leaf switch after the first level serving as a mechanism to facilitate communication between lower level non-leaf switches and leaf switches. In some embodiments, the non-leaf switches are software switches that are implemented by storing the switching tables in the memory of a standalone computer instead of an off-the-shelf switch. In some embodiments, the standalone computer may also be executing a hypervisor and one or more virtual machines on top of that hypervisor. Irrespective of the manner by which the leaf and non-leaf switches are implemented, the NIB of the control system of some embodiments stores switching state information regarding the leaf and non-leaf switches.
The above discussion relates to the control of edge switches and non-edge switches by a network control system of some embodiments. In some embodiments, edge switches and non-edge switches (leaf and non-leaf nodes) may be referred to as managed switches. This is because these switches are managed by the network control system (as opposed to unmanaged switches, which are not managed by the network control system, in the network) in order to implement logical datapath sets through the managed switches.
In addition to using the NIB to store switching-element data, the virtualized network-control system of some embodiments also stores other storage structures to store data regarding the switching elements of the network. These other storage structures are secondary storage structures that supplement the storage functions of the NIB, which is the primary storage structure of the system while the system operates. In some embodiments, the primary purpose for one or more of the secondary storage structures is to back up the data in the NIB. In these or other embodiments, one or more of the secondary storage structures serve a purpose other than backing up the data in the NIB (e.g., for storing data that is not in the NIB).
In some embodiments, the NIB is stored in system memory (e.g., RAM) while the system operates. This allows for fast access of the NIB records. In some embodiments, one or more of the secondary storage structures, on the other hand, are stored on disks, or other non-volatile memories, which can be slower to access. Such non-volatile disks or other non-volatile memories, however, improve the resiliency of the system as they allow the data to be stored in a persistent manner.
The system of some embodiments uses multiple types of storages in its pool of secondary storage structures. These different types of structures store different types of data, store data in different manners, and provide different query interfaces that handle different types of queries. For instance, in some embodiments, the system uses a persistent transactional database (PTD) and a hash table structure. The PTD in some embodiments is a database that is stored on disk or other non-volatile memory. In some embodiments, the PTD is a commonly available database, such as MySQL or SQLite. The PTD of some embodiments can handle complex transactional queries. As a transactional database, the PTD can undo a series of earlier query operations that it has performed as part of a transaction when one of the subsequent query operations of the transaction fails.
Moreover, some embodiments define a transactional guard processing (TGP) layer before the PTD in order to allow the PTD to execute conditional sets of database transactions. The TGP layer allows the PTD to avoid unnecessary later database operations when conditions of earlier operations are not met. The PTD in some embodiments stores an exact replica of the data that is stored in the NIB, while in other embodiments it stores only a subset of the data that is stored in the NIB. In some embodiments, some or all of the data in the NIB is stored in the PTD in order to ensure that the NIB data will not be lost in the event of a crash of the NOS or the NIB.
While the system is running, the hash table in some embodiments is not stored on a disk or other non-volatile memory. Instead, it is a storage structure that is stored in volatile system memory when the system is running. When the system is powered down, the contents of the hash table are stored on disk. The hash table uses hashed indices that allow it to retrieve records in response to queries. This structure combined with the hash table's placement in the system's volatile memory allows the table to be accessed very quickly. To facilitate this quick access, a simplified query interface is used in some embodiments. For instance, in some embodiments, the hash table has just two queries: a Put query for writing values to the table and a Get query for retrieving values from the table. The system of some embodiments uses the hash table to store data that the NOS needs to retrieve very quickly. Examples of such data include network entity status, statistics, state, uptime, link arrangement, and packet handling information. Furthermore, in some embodiments, the NOS uses the hash tables as a cache to store information that is repeatedly queried, such as flow entries that will be written to multiple nodes.
Using a single NOS instance to control a network can lead to scaling and reliability issues. As the number of network elements increases, the processing power and/or memory capacity that are required by those elements will saturate a single node. Some embodiments further improve the resiliency of the control system by having multiple instances of the NOS running on one or more computers, with each instance of the NOS containing one or more of the secondary storage structures described above. Each instance in some embodiments not only includes a NOS instance, but also includes a virtualization application instance and/or a control application instance. In some of these embodiments, the control and/or virtualization applications partition the workload between the different instances in order to reduce each instance's control and/or virtualization workload. Also, in some embodiments, the multiple instances of the NOS communicate the information stored in their secondary storage layers to enable each instance of the NOS to cover for the others in the event of a NOS instance failing. Moreover, some embodiments use the secondary storage layer (i.e., one or more of the secondary storages) as a channel for communicating between the different instances.
The distributed, multi-instance control system of some embodiments maintains the same switch element data records in the NIB of each instance, while in other embodiments, the system allows NIBs of different instances to store different sets of switch element data records. Some embodiments that allow different instances to store different portions of the NIB, divide the NIB into N mutually exclusive portions and store each NIB portion in one NIB of one of N controller instances, where N is an integer value greater than 1. Other embodiments divide the NIB into N portions and store different NIB portions in different controller instances, but allow some or all of the portions to partially (but not completely) overlap with the other NIB portions.
The hash tables in the distributed control system of some embodiments form a distributed hash table (DHT), with each hash table serving as a DHT instance. In some embodiments, the DHT instances of all controller instances collectively store one set of records that is indexed based on hashed indices for quick access. These records are distributed across the different controller instances to minimize the size of the records within each instance and to allow for the size of the DHT to be increased by adding other DHT instances. According to this scheme, each DHT record is not stored in each controller instance. In fact, in some embodiments, each DHT record is stored in at most one controller instance. To improve the system's resiliency, some embodiments, however, allow one DHT record to be stored in more than one controller instance, so that in case one instance fails, the DHT records of that failed instance can be accessed from other instances. Some embodiments do not allow for replication of records across different DHT instances or allow only a small amount of such records to be replicated because these embodiments store in the DHT only the type of data that can be quickly re-generated.
The distributed control system of some embodiments replicates each NIB record in the secondary storage layer (e.g., in each PTD instance and/or in the DHT) in order to maintain the records in the NIB in a persistent manner. For instance, in some embodiments, all the NIB records are stored in the PTD storage layer. In other embodiments, only a portion of the NIB data is replicated in the PTD storage layer. For instance, some embodiments store a subset of the NIB records in another one of the secondary storage records, such as the DHT.
By allowing different NOS instances to store the same or overlapping NIB records, and/or secondary storage structure records, the system improves its overall resiliency by guarding against the loss of data due to the failure of any NOS or secondary storage structure instance. For instance, in some embodiments, the portion of NIB data that is replicated in the PTD (which is all of the NIB data in some embodiments or part of the NIB data in other embodiments) is replicated in the NIBs and PTDs of all controller instances, in order to protect against failures of individual controller instances (e.g., of an entire controller instance or a portion of the controller instance).
In some embodiments, each of the storages of the secondary storage layer uses a different distribution technique to improve the resiliency of a multiple NOS instance system. For instance, as mentioned above, the system of some embodiments replicates the PTD across NOS instances so that every NOS has a full copy of the PTD to enable a failed NOS instance to quickly reload its PTD from another instance. In some embodiments, the system distributes the DHT fully or with minimal overlap across multiple controller instances in order to minimize the size of the DHT instance (e.g., the amount of memory the DHT instance utilizes) within each instance. This approach also allows the size of the DHT to be increased by adding additional DHT instances, and this in turn allows the system to be more scalable.
For some or all of the communications between the distributed instances, the distributed system of some embodiments uses coordination managers (CM) in the controller instances to coordinate activities between the different controllers. Examples of such activities include writing to the NIB, writing to the PTD, writing to the DHT, controlling the switching elements, facilitating intra-controller communication related to fault tolerance of controller instances, etc.
To distribute the workload and to avoid conflicting operations from different controller instances, the distributed control system of some embodiments designates one controller instance within the system as the master of any particular NIB portion (e.g., as the master of a logical datapath set) and one controller instance within the system as the master of any given switching element. Even with one master controller, a different controller instance can request changes to different NIB portions and/or to different switching elements controlled by the master. If allowed, the master instance then effectuates this change and writes to the desired NIB portion and/or switching element. Otherwise, the master rejects the request.
The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this document. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description and the Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description and the Drawings, but rather are to be defined by the appended claims, because the claimed subject matters can be embodied in other specific forms without departing from the spirit of the subject matters.
The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, several embodiments of the invention are set forth in the following figures.
In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.
Some embodiments of the invention provide a method that allows several different logical datapath sets to be specified for several different users through one or more shared switching elements without allowing the different users to control or even view each other's switching logic. In some embodiments, the method provides a set of software tools that allows the system to accept logical datapath sets from users and to configure the switching elements to implement these logical datapath sets. These software tools allow the method to virtualize control of the shared switching elements and the network that is defined by the connections between these shared switching elements, in a manner that prevents the different users from viewing or controlling each other's logical datapath sets while sharing the same switching elements.
In some embodiments, one of the software tools that the method provides that allows it to virtualize control of a set of switching elements (i.e., to enable the method to allow several users to share the same switching elements without viewing or controlling each other's logical datapath sets) is an intermediate data storage structure that (1) stores the state of the network, (2) receives modifications to different parts of the network from different users, and (3), in some embodiments, provides different views of the state of the network to different users. For instance, in some embodiments, the intermediate data storage structure is a network information base (NIB) data structure that stores the state of the network that is defined by one or more switching elements. In some embodiments, the NIB also stores the logical configuration and the logical state for each user specified logical datapath set. In these embodiments, the information in the NIB that represents the state of the actual switching elements accounts for only a subset of the total information stored in the NIB.
The method uses the NIB data structure to read the state of the network and to write modifications to the state of the network. When the data structure is modified in order to effectuate a change in the switching logic of a switching element, the method propagates the modification to the switching element.
In some embodiments, the method is employed by a virtualized network control system that (1) allows user to specify different logical datapath sets, (2) maps these logical datapath sets to a set of switching elements managed by the control system. In some embodiments, the switching elements include virtual or physical network switches, software switches (e.g., Open vSwitch), routers, and/or other switching elements, as well as any other network elements (such as load balancers, etc.) that establish connections between these switches, routers, and/or other switching elements. Such switching elements (e.g., physical switching elements, such as physical switches or routers) are implemented as software switches in some embodiments. Software switches are switches that are implemented by storing the switching tables in the memory of a standalone computer instead of an off the shelf switch. In some embodiments, the standalone computer may also be executing in some cases a hypervisor and one or more virtual machines on top of that hypervisor
These switches are referred to below as managed switching elements or managed forwarding elements as they are managed by the network control system in order to implement the logical datapath sets. In some embodiments described below, the control system manages these switching elements by pushing physical control plane data to them, as further described below. Switching elements generally receive data (e.g., a data packet) and perform one or more processing operations on the data, such as dropping a received data packet, passing a packet that is received from one source device to another destination device, processing the packet and then passing it a destination device, etc. In some embodiments, the physical control plane data that is pushed to a switching element is converted by the switching element (e.g., by a general purpose processor of the switching element) to physical forwarding plane data that specify how the switching element (e.g., how a specialized switching circuit of the switching element) process data packets that it receives.
The virtualized control system of some embodiments includes (1) a network operating system (NOS) that creates and maintains the NIB storage structure, and (2) one or more applications that run on top of the NOS to specify control logic for reading values from and writing values to the NIB. The NIB of some of these embodiments serves as a communication channel between the different controller instances and, in some embodiments, a communication channel between different processing layers of a controller instance.
Several examples of such systems are described below in Section I. Section II then describes the NIB data structure of some embodiments of the invention. Section III then describes a distributed, multi-instance architecture of some embodiments in which multiple stacks of the NOS and the control applications are used to control the shared switching elements within a network in a scalable and resilient manner. Section IV then provides a more detailed example of the NOS of some embodiments of the invention. Section V then describes several other data storage structures that are used by the NOS of some embodiments of the invention. Finally, Section VI describes the computer systems and processes used to implement some embodiments of the invention.
I. Virtualized Control System
As shown in
The virtual or physical switching elements 105 typically include control switching logic 125 and forwarding switching logic 130. In some embodiments, a switch's control logic 125 specifies (1) the rules that are to be applied to incoming packets, (2) the packets that will be discarded, and (3) the packet processing methods that will be applied to incoming packets. The virtual or physical switching elements 105 use the control logic 125 to populate tables governing the forwarding logic 130. The forwarding logic 130 performs lookup operations on incoming packets and forwards the incoming packets to destination addresses.
As further shown in
To provide the applications 120 programmatic access to the switching elements, the NOS 110 itself needs to be able to control the switching elements 105. The NOS uses different techniques in different embodiments to control the switching elements. In some embodiments, the NOS can specify both control and forwarding switching logic 125 and 130 of the switching elements. In other embodiments, the NOS 110 controls only the control switching logic 125 of the switching elements, as shown in
In order to define the control switching logic 125 for physical switching elements, the NOS of some embodiments uses the Open Virtual Switch protocol to create one or more control tables within the control plane of a switch element. The control plane is typically created and executed by a general purpose CPU of the switching element. Once the system has created the control table(s), the system then writes flow entries to the control table(s) using the OpenFlow protocol. The general purpose CPU of the physical switching element uses its internal logic to convert entries written to the control table(s) to populate one or more forwarding tables in the forwarding plane of the switch element. The forwarding tables are created and executed typically by a specialized switching chip of the switching element. Through its execution of the flow entries within the forwarding tables, the switching chip of the switching element can process and route packets of data that it receives.
To enable the programmatic access of the applications 120 to the switching elements 105, the NOS also creates the network information base (NIB) 115. The NIB is a data structure in which the NOS stores a copy of the switch-element states tracked by the NOS. The NIB of some embodiments is a graph of all physical or virtual switch elements and their interconnections within a physical network topology and their forwarding tables. For instance, in some embodiments, each switching element within the network infrastructure is represented by one or more data objects in the NIB. However, in other embodiments, the NIB stores state information about only some of the switching elements. For example, as further described below, the NIB in some embodiments only keeps track of switching elements at the edge of a network infrastructure. In yet other embodiments, the NIB stores state information about edge switching elements in a network as well as some non-edge switching elements in the network that facilitate communication between the edge switching elements. In some embodiments, the NIB also stores the logical configuration and the logical state for each user specified logical datapath set. In these embodiments, the information in the NIB that represents the state of the actual switching elements accounts for only a subset of the total information stored in the NIB.
In some embodiments, the NIB 115 is the heart of the NOS control model in the virtualized network system 100. Under one approach, applications control the network by reading from and writing to the NIB. Specifically, in some embodiments, the application control logic can (1) read the current state associated with network entity objects in the NIB, (2) alter the network state by operating on these objects, and (3) register for notifications of state changes to these objects. Under this model, when an application 120 needs to modify a record in a table (e.g., a control plane flow table) of a switching element 105, the application 120 first uses the NOS' APIs to write to one or more objects in the NIB that represent the table in the NIB. The NOS then, acting as the switching element's controller, propagates this change to the switching element's table.
Next, in the third stage, the NOS uses the set of switch-access APIs to write a new set of values into the switch. In some embodiments, the NIB performs a translation operation that modifies the format of the records before writing these records into the NIB. This operation is pictorially illustrated in
In yet other embodiments, the NOS' translation operation might modify the set of values in the NIB (e.g., the values d, e, and f) into a different set of values with fewer values (e.g., values x and y, where x and y might be a subset of d, e, and f, or completely different) or additional values (e.g., the w, x, y, and z, where w, x, y, and z might be a super set of all or some of d, e, and f, or completely different). The NOS in these embodiments would then write this modified set of values (e.g., values x and y, or values w, x, y and z into the switching element).
The fourth stage finally shows the switch 205 after the old values a, b, and c have been replaced in the switch control record 230 with the values d′, e′, and f′. Again, in the example shown in
A. Different NIB Views
In some embodiments, the virtualized system 100 of
In system 300, the NIB 115 stores sets of data records for each of the switching elements 105a-105d. In some embodiments, a system administrator can access these four sets of data through an application 120 that interfaces with the NOS. However, other users that are not system administrators do not have access to all of the four sets of records in the NIB, because some switch logic records in the NIB might relate to the logical switching configuration of other users.
Instead, each non-system-administrator user can only view and modify the switching element records in the NIB that relate to the logical switching configuration of the user.
In some embodiments, each user's NIB view is a higher level NIB view that represents an abstraction of the lowest level NIB view that correlates to the actual network infrastructure that is formed by the switching elements 105a-105d. For instance, as shown in
The first layered NIB view is a reflection of a first set of data records 365 that the application 120 allows the first user to access from the NIB, while the second layered NIB view is a representation of a second set of data records 370 that the application 120 allows the second user to access from the NIB. In some embodiments, the application 120 retrieves the two sets of data records 365 and 370 from the NIB and maintains these records locally, as shown in
Irrespective of whether the application maintains a local copy of the first and second data records or whether the application only provides the switching element abstractions in its higher layered NIB views, the application 120 serves as an interface through which each user can view and modify the user's logical switching configuration, without being able to view or modify the other user's logical switching configuration. Through the set of APIs provided by the NOS 110, the application 120 propagates to the NIB 115 changes that a user makes to the logical switching configuration view that the user receives from the application. The propagation of these changes entails the transferring, and in some cases of some embodiments, the transformation, of the high level data entered by a user for a higher level NIB view to lower level data that is to be written to lower level NIB data that is stored by the NOS.
In the system 300 of
The system of some embodiments embeds all such operations in the NOS 110 instead of in the application 120 operating on top of the NOS. Alternatively, in other embodiments the system separates these operations into several applications that operate above the NOS.
In some embodiments, the virtualization application 425 interfaces with the NOS 110 to provide different views of different NIB records to different users through the control application 420. The control application 420 also provides the control logic for allowing a user to specify different operations with respect to the limited NIB records/views provided by the virtualization application. Examples of such operations can be read operations from the NIB or write operations to the NIB. The virtualization application then translates these operations into operations that access the NIB. In translating these operations, the virtualization application in some embodiments also transfers and/or transforms the data that are expressed in terms of the higher level NIB records/views to data that are expressed in terms of lower level NIB records.
Even though
B. Type I Versus Type II Virtualized System
Different embodiments of the invention use different types of virtualization applications. One type of virtualization application exposes the definition of different elements at different hierarchical levels in the NIB and the definition of the links between these elements to the control applications that run on top of the NOS and the virtualization application in order to allow the control application to define its operations by reference to these definitions. For instance, in some embodiments, the developer of the control application running on top of the virtualization application uses these definitions to enumerate how the application is to map the logical datapath sets of the user to the physical switching elements of the control system. Under this approach, the developer would have to enumerate all different scenarios that the control system may encounter and the mapping operation of the application for each scenario. This type of virtualization is referred to below as Type I network virtualization.
Another type of network virtualization, which is referred to below as Type II network virtualization, does not require the application developers to have intimate knowledge of the NIB elements and the links in the NIB between these elements. Instead, this type of virtualization allows the application to simply provide user specified switching element attributes in the form of one or more tables, which are then mapped to NIB records by a table mapping engine. In other words, the Type II virtualized system of some embodiments accepts switching element configurations (e.g., access control list table configurations, L2 table configurations, L3 table configurations, etc.) that the user defines without referencing any operational state of the switching elements in a particular network configuration. It then maps the user-specified switching element configurations to the switching element configurations stored in the NIB.
More specifically, the control application 520 allows (1) a user to specify abstract switching element configurations, which the virtualization application 525 then maps to the data records in the NIB, and (2) the user to view the state of the abstract switching element configurations. In some embodiments, the control application 520 uses a network template library 530 to allow a user to specify a set of logical datapaths by specifying one or more switch element attributes (i.e., one or more switch element configurations). In the example shown in
In specifying these tables, the user simply specifies desired switch configuration records for one or more abstract, logical switching elements. When specifying these records, the user of the system 500 does not have any understanding of the switching elements 105a-105d employed by the system nor any data regarding these switching elements from the NIB 115. The only switch-element specific data that the user of the system 500 receives is the data from the network template library, which specifies the types of network elements that the user can define in the abstract, which the system can then process.
While the example in
Irrespective of the abstraction level of the switch-element attributes produced through the control logic application, the virtualization application 525 performs a mapping operation that maps the specified switch-element attributes (e.g., the specific or generic switch table records) to records in the NIB. In some embodiments, the virtualization application translates control application input into one or more NIB records 585 that the virtualization application then writes to the NIB through the API set provided by the NOS. From the NIB, these records are then subsequently transferred to the switching infrastructure through the operation of the NOS. In some embodiments, the NIB stores both the logical datapath set input received through the control application as well as the NIB records that are produced by the virtualization application.
In some embodiments, the control application can receive switching infrastructure data from the NIB. In response to this data, the control application may modify record(s) associated with one or more logical datapath sets (LDPS). Any such modified LDPS record would then be translated to one or more physical switching infrastructure records by the virtualization application, which might then be transferred to the physical switching infrastructure by the NOS.
To map the control application input to physical switching infrastructure attributes for storage in the NIB, the virtualization application of some embodiments uses a database table mapping engine to map input tables, which are created from (1) the control-application specified input tables, and (2) a set of properties associated with switching elements used by the system, to output tables. The content of these output tables are then transferred to the NIB elements.
Some embodiments use a variation of the datalog database language to allow application developers to create the table mapping engine for the virtualization application, and thereby to specify the manner by which the virtualization application maps logical datapath sets to the controlled physical switching infrastructure. This variation of the datalog database language is referred to below as n Log. Like datalog, n Log provides a few declaratory rules and operators that allow a developer to specify different operations that are to be performed upon the occurrence of different events. In some embodiments, n Log provides a limited subset of the operators that are provided by datalog in order to increase the operational speed of n Log. For instance, in some embodiments, n Log only allows the AND operator to be used in any of the declaratory rules.
The declaratory rules and operations that are specified through n Log are then compiled into a much larger set of rules by an n Log compiler. In some embodiments, this compiler translates each rule that is meant to address an event into several sets of database join operations. Collectively the larger set of rules forms the table-mapping rules engine that is referred to below as the n Log engine. The n Log mapping techniques of some embodiments are further described in U.S. patent application entitled “Network Virtualization Apparatus and Method,” filed Jul. 6, 2011, with application Ser. No. 13/177,533, now issued as U.S. Pat. No. 8,817,620.
In some embodiments, the n Log virtualization engine provides feedback (e.g., from one or more of the output tables or from NIB records that are updated to reflect values stored in the output tables) to the user in order to provide the user with state information about the logical datapath set that he or she created. In this manner, the updates that the user gets are expressed in terms of the logical space that the user understands and not in terms of the underlying switching element states, which the user does not understand.
The use of n Log serves as a significant distinction between Type I virtualized control systems and Type II virtualized control systems, even for Type II systems that store user specified logical datapath sets in the NIB. This is because n Log provides a machine-generated rules engine that addresses the mapping between the logical and physical domains in a more robust, comprehensive manner than the hand-coded approach used for Type I virtualized control systems. In the Type I control systems, the application developers need to have a detailed understanding of the NIB structure and need to use this detailed understanding to write code that addresses all possible conditions that the control system would encounter at runtime. On the other hand, in Type II control systems, the application developers only need to produce applications that express the user-specified logical datapath sets in terms of one or more tables, which are then automatically mapped to output tables whose contents are in turn transferred to the NIB. This approach allows the Type II virtualized systems to forego maintaining the data regarding the logical datapath sets in the NIB. However, some embodiments maintain this data in the NIB in order to distribute this data among other NOS instances, as further described below.
In some embodiments, the system 500 propagates instructions to control a set of the switching elements 105a-105d through the control application 520, the virtualization application 525, and the NOS 110. Specifically, in some embodiment, the control application 520, the virtualization application 525, and the NOS 110 collectively translate and propagate control plane data through the three layers to a set of the switching elements 105a-105d.
The control application 520 of some embodiments has two logical planes that can be used to express the input to and output from this application. In some embodiments, the first logical plane is a logical control plane that includes a collection of higher-level constructs that allow the control application 520 and its users to define a logical plane for a logical switching element by specifying one or more logical datapath sets for a user. The second logical plane in some embodiments is the logical forwarding plane, which represents the logical datapath sets of the users in a format that can be processed by the virtualization application 525. In this manner, the two logical planes are logical space analogs of physical control and forwarding planes that are typically found in a typical managed switch.
In some embodiments, the control application 520 defines and exposes the logical control plane constructs with which the application itself or users of the application specifies different logical datapath sets. For instance, in some embodiments, the logical control plane data 520 includes the logical ACL table 545, the logical L2 table 535, and the logical L3 table 540. Some of this data can be specified by the user, while other such data are generated by the control application. In some embodiments, the control application 520 generates and/or specifies such data in response to certain changes to the NIB (which indicate changes to the switching elements 105a-105d and the managed datapath sets) that the control application 520 detects.
In some embodiments, the logical control plane data (i.e., the LDPS data 550 that is expressed in terms of the control plane constructs) can be initially specified without consideration of current operational data from the switching elements 105a-105d and without consideration of the manner by which this control plane data will be translated to physical control plane data. For instance, the logical control plane data might specify control data for one logical switch that connects five computers, even though this control plane data might later be translated to physical control data for three of the switching elements 105a-105d that implement the desired switching between the five computers.
The control application 520 of some embodiments includes a set of modules (not shown) for converting any logical datapath set within the logical control plane to a logical datapath set in the logical forwarding plane of the control application 520. Some embodiments may express the logical datapath set in the logical forwarding plane of the control application 520 as a set of forwarding tables (e.g., the L2 table 535 and L3 table 540). The conversion process of some embodiments includes the control application 520 populating logical datapath tables (e.g., logical forwarding tables) that are created by the virtualization application 525 with logical datapath sets. In some embodiments, the control application 520 uses an n Log table mapping engine to perform this conversion. The control application's use of the n Log table mapping engine to perform this conversion is further described in U.S. patent application entitled “Network Control Apparatus and Method,” filed Jul. 6, 2011, with application Ser. No. 13/177,532, now issued as U.S. Pat. No. 8,743,888.
The virtualization application 525 of some embodiments also has two planes of data, a logical forwarding plane and a physical control plane. The logical forwarding plane is identical or similar to the logical forwarding plane produced by the control application 520. In some embodiments, the logical forwarding plane of the virtualization application 525 includes one or more logical datapath sets of one or more users. The logical forwarding plane of the virtualization application 525 in some embodiments includes logical forwarding data for one or more logical datapath sets of one or more users. Some of this data is pushed directly or indirectly to the logical forwarding plane of the virtualization application 525 by the control application 520, while other such data are pushed to the logical forwarding plane of the virtualization application 525 by the virtualization application 525 detecting events in the NIB.
The physical control plane of the virtualization application 525 includes one or more physical datapath sets of one or more users. Some embodiments of the virtualization application 525 include a set of modules (not shown) for converting any LDPS within the logical forwarding plane of the virtualization application 525 to a physical datapath set in the physical control plane of the virtualization application 525. In some embodiments, the virtualization application 525 uses the n Log table mapping engine to perform this conversion. The virtualization application 525 also includes a set of modules (not shown) for pushing the control plane data from the physical control plane of the virtualization application 525 into the NIB of the NOS 110.
From the NIB, the physical control plane data is later pushed into a set of the switching elements 105a-105d (e.g., switching elements 105a and 105c). In some embodiments, the physical control plane data is pushed to each of the set of the switching elements 105a-105d by the controller instance that is the master of the switching element. In some cases, the master controller instance of the switching element is the same controller instance that converted the logical control plane data to the logical forwarding plane data and the logical forwarding plane data to the physical control plane data. In other cases, the master controller instance of the switching element is not the same controller instance that converted the logical control plane data to the logical forwarding plane data and the logical forwarding plane data to the physical control plane data. The set of the switching elements 105a-105d then converts this physical control plane data to physical forwarding plane data that specifies the forwarding behavior of the set of the switching elements 105a-105d.
In some embodiments, the physical control plane data that is propagated to the set of the switching elements 105a-105d allows the set of the switching elements 105a-105d to perform the logical data processing on data packets that it processes in order to effectuate the processing of the logical datapath sets specified by the control application 520. In some such embodiments, physical control planes include control plane data for operating in the physical domain and control plane data for operating in the logical domain. In other words, the physical control planes of these embodiments include control plane data for processing network data (e.g., packets) through switching elements to implement physical switching and control plane data for processing network data through switching elements in order to implement the logical switching. In this manner, the physical control plane facilitates implementing logical switches across the switching elements. The use of the propagated physical control plane to implement logical data processing in the switching elements is further described in U.S. Patent Application entitled “Hierarchical Managed Switch Architecture,” filed Jul. 6, 2011, with application Ser. No. 13/177,535, issue as U.S. Pat. No. 8,750,164.
In addition to pushing physical control plane data to the NIB 115, the control and virtualization applications 520 and 525 also store logical control plane data and logical forwarding plane data in the NIB 115. These embodiments store such data in the NIB 115 for a variety of reasons. For instance, in some embodiments, the NIB 115 serves as a medium for communications between different controller instances, and the storage of such data in the NIB 115 facilitates the relaying of such data across different controller instances.
The NIB 115 in some embodiments serves as a hub for all communications among the control application 520, the virtualization application 525, and the NOS 110. For instance, the control application 520 may store in the NIB logical datapath sets in the logical forwarding plane that have been converted from logical datapath sets in the logical control plane. The virtualization application 525 may retrieve from the NIB the converted logical datapath sets in the logical forwarding plane and then convert the logical datapath sets to physical datapath sets in the physical control plane of the virtualization application 525. Thus, the NIB of some embodiments serves as a medium for communication between the different processing layers. Also, the NIB 115 in these embodiments stores logical control plane data and logical forwarding plane data as well as physical control plane data.
The above description describes a control data pipeline through three processing layers to a set of the switching elements 105a-105d. However, in some embodiments, the control data pipeline may have two processing layers instead of three with the upper layer being a single application that performs the functionalities of both the control application 520 and the virtualization application 525. For example, a single virtualization application (also called a network hypervisor) may replace these the control application 520 and the virtualization application 525 in some embodiments. In such embodiments, the control application 520 would form the front end of this network hypervisor, and would create and populate the logical datapath sets. The virtualization application 525 in these embodiments would form the back end of the network hypervisor, and would convert the logical datapath sets to physical datapath sets that are defined in the physical control plane.
In some embodiments, the different processing layers are implemented on a single computing device. Referring to
C. Edge and Non-Edge Switch Controls
As mentioned above, the NIB in some embodiments stores data regarding each switching element within the network infrastructure of a system, while in other embodiments, the NIB stores state information about only switching elements at the edge of a network infrastructure.
The system of some embodiments only controls edge switches (i.e., only maintains data in the NIB regarding edge switches) for several reasons. Controlling edge switches provides the system with a sufficient mechanism for maintaining isolation between computing devices, which is needed, as opposed to maintaining isolation between all switch elements, which is not needed. The interior switches forward between switching elements. The edge switches forward between computing devices and other network elements. Thus, the system can maintain user isolation simply by controlling the edge switch because the edge switch is the last switch in line to forward packets to a host.
Controlling only edge switches also allows the system to be deployed independent of concerns about the hardware vendor of the non-edge switches, because deploying at the edge allows the edge switches to treat the internal nodes of the network as simply a collection of elements that moves packets without considering the hardware makeup of these internal nodes. Also, controlling only edge switches makes distributing switching logic computationally easier. Controlling only edge switches also enables non-disruptive deployment of the system because edge-switching solutions can be added as top of rack switches without disrupting the configuration of the non-edge switches.
In addition to controlling edge switches, the network control system of some embodiments also utilizes and controls non-edge switches that are inserted in the switch network hierarchy to simplify and/or facilitate the operation of the controlled edge switches. For instance, in some embodiments, the control system requires the switches that it controls to be interconnected in a hierarchical switching architecture that has several edge switches as the leaf nodes in this switching architecture and one or more non-edge switches as the non-leaf nodes in this architecture. In some such embodiments, each edge switch connects to one or more of the non-leaf switches, and uses such non-leaf switches to facilitate its communication with other edge switches. Examples of functions that a non-leaf switch of some embodiments may provide to facilitate such communications between edge switches in some embodiments include (1) routing of a packet with an unknown destination address (e.g., unknown MAC address) to the non-leaf switch so that this switch can route this packet to the appropriate edge switch, (2) routing a multicast or broadcast packet to the non-leaf switch so that this switch can convert this packet to a series of unicast packets to the desired destinations, (3) bridging remote managed networks that are separated by one or more networks, and (4) bridging a managed network with an unmanaged network.
Some embodiments employ one level of non-leaf (non-edge) switches that connect to edge switches and in some cases to other non-leaf switches. Other embodiments, on the other hand, employ multiple levels of non-leaf switches, with each level of non-leaf switch after the first level serving as a mechanism to facilitate communication between lower level non-leaf switches and leaf switches. In some embodiments, the non-leaf switches are software switches that are implemented by storing the switching tables in the memory of a standalone computer instead of an off-the-shelf switch. In some embodiments, the standalone computer may also be executing in some cases a hypervisor and one or more virtual machines on top of that hypervisor. Irrespective of the manner by which the leaf and non-leaf switches are implemented, the NIB of the control system of some embodiments stores switching state information regarding the leaf and non-leaf switches.
The above discussion relates to the control of edge switches and non-edge switches by a network control system of some embodiments. In some embodiments, edge switches and non-edge switches (leaf and non-leaf nodes) may be referred to as managed switches. This is because these switches are managed by the network control system (as opposed to unmanaged switches, which are not managed by the network control system, in the network) in order to implement logical datapath sets through the managed switches.
D. Secondary Storage Structure
In addition to using the NIB to store switching-element data, the virtualized network-control system of some embodiments also stores other storage structures to store data regarding the switching elements of the network. These other storage structures are secondary storage structures that supplement the storage functions of the NIB, which is the primary storage structure of the system while the system operates. In some embodiments, the primary purpose for one or more of the secondary storage structures is to back up the data in the NIB. In these or other embodiments, one or more of the secondary storage structures serves a purpose other than backing up the data in the NIB (e.g., for storing data that are not in the NIB).
In some embodiments, the NIB is stored in system memory (e.g., RAM) while the system operates. This allows for fast access of the NIB records. In some embodiments, one or more of the secondary storage structures, on the other hand, are stored on disk or other non-volatile memories that are slower to access. Such non-volatile disk or other storages, however, improve the resiliency of the system as they allow the data to be stored in a persistent manner.
In some embodiments, the PTD 810 is a database that is stored on disk or other non-volatile memory. In some embodiments, the PTD is a commonly available database, such as MySQL or SQLite. The PTD of some embodiments can handle complex transactional queries. As a transactional database, the PTD can undo a series of prior query operations that it has performed as part of a transaction when one of the subsequent query operations of the transaction fails. Moreover, some embodiments define a transactional guard processing (TGP) layer before the PTD in order to allow the PTD to execute conditional sets of database transactions. The TGP layer allows the PTD to avoid unnecessary later database operations when conditions of earlier operations are not met.
The PTD in some embodiments stores an exact replica of the data that is stored in the NIB, while in other embodiments it stores only a subset of the data that is stored in the NIB. Some or all of the data in the NIB is stored in the PTD in order to ensure that the NIB data will not be lost in the event of a crash of the NOS or the NIB.
The PNTD 815 is another persistent database that is stored on disk or other non-volatile memory. Some embodiments use this database to store data (e.g., statistics, computations, etc.) regarding one or more switch element attributes or operations. For instance, this database is used in some embodiments to store the number of packets routed through a particular port of a particular switching element. Other examples of types of data stored in the database 815 include error messages, log files, warning messages, and billing data. Also, in some embodiments, the PNTD stores the results of operations performed by the application(s) 830 running on top of the NOS, while the PTD and hash table store only values generated by the NOS.
The PNTD in some embodiments has a database query manager that can process database queries, but as it is not a transactional database, this query manager cannot handle complex conditional transactional queries. In some embodiments, accesses to the PNTD are faster than accesses to the PTD but slower than accesses to the hash table 820.
Unlike the databases 810 and 815, the hash table 820 is not a database that is stored on disk or other non-volatile memory. Instead, it is a storage structure that is stored in volatile system memory (e.g., RAM). It uses hashing techniques that use hashed indices to quickly identify records that are stored in the table. This structure combined with the hash table's placement in the system memory allows this table to be accessed very quickly. To facilitate this quick access, a simplified query interface is used in some embodiments. For instance, in some embodiments, the hash table has just two queries: a Put query for writing values to the table and a Get query for retrieving values from the table. Some embodiments use the hash table to store data that changes quickly. Examples of such quick-changing data include network entity status, statistics, state, uptime, link arrangement, and packet handling information. Furthermore, in some embodiments, the NOS uses the hash tables as a cache to store information that is repeatedly queried for, such as flow entries that will be written to multiple nodes. Some embodiments employ a hash structure in the NIB in order to quickly access records in the NIB. Accordingly, in some of these embodiments, the hash table 820 is part of the NIB data structure.
The PTD and the PNTD improve the resiliency of the NOS system by preserving network data on hard disks. If a NOS system fails, network configuration data will be preserved on disk in the PTD and log file information will be preserved on disk in the PNTD.
E. Multi-Instance Control System
Using a single NOS instance to control a network can lead to scaling and reliability issues. As the number of network elements increases, the processing power and/or memory capacity that are required by those elements will saturate a single node. Some embodiments further improve the resiliency of the control system by having multiple instances of the NOS running on one or more computers, with each instance of the NOS containing one or more of the secondary storage structures described above. The control applications in some embodiments partition the workload between the different instances in order to reduce each instance's workload. Also, in some embodiments, the multiple instances of the NOS communicate the information stored in their storage layers to enable each instance of the NOS to cover for the others in the event of a NOS instance failing.
As shown in
In some embodiments, the system 900 maintains the same switch element data records in the NIB of each instance, while in other embodiments, the system 900 allows NIBs of different instances to store different sets of switch element data records.
The system 900 of some embodiments also replicates each NIB record in each instance in the PTD 945 of that instance in order to maintain the records of the NIB in a persistent manner. Also, in some embodiments, the system 900 replicates each NIB record in the PTDs of all the controller instances 905, 910, or 915, in order to protect against failures of individual controller instances (e.g., of an entire controller instance or a portion of the controller instance). Other embodiments, however, do not replicate each NIB record in each PTD and/or do not replicate the PTD records across all the PTDs. For instance, some embodiments replicate only a part but not all of the NIB data records of one controller instance in the PTD storage layer of that controller instance, and then replicate only this replicated portion of the NIB in all of the NIBs and PTDs of all other controller instances. Some embodiments also store a subset of the NIB records in another one of the secondary storage records, such as the DHT instance 950.
In some embodiments, the DHT instances (DHTI) 950 of all controller instances collectively store one set of records that are indexed based on hashed indices for quick access. These records are distributed across the different controller instances to minimize the size of the records within each instance and to allow the size of the DHT to be increased by adding additional DHT instances. According to this scheme, one DHT record is not stored in each controller instance. In fact, in some embodiments, each DHT record is stored in at most one controller instance. To improve the system's resiliency, some embodiments, however, allow one DHT record to be stored in more than one controller instance, so that in case one DHT record is no longer accessible because of one instance failure, that DHT record can be accessed from another instance. Some embodiments store in the DHT only the type of data that can be quickly re-generated, and therefore do not allow for replication of records across different DHT instances or allow only a small amount of such records to be replicated.
The PNTD 955 is another distributed data structure of the system 900 of some embodiments. For example, in some embodiments, each instance's PNTD stores the records generated by the NOS 925 or applications 930 or 935 of that instance or another instance. Each instance's PNTD records can be locally accessed or remotely accessed by other controller instances whenever the controller instances need these records. This distributed nature of the PNTD allows the PNTD to be scalable as additional controller instances are added to the control system 900. In other words, addition of other controller instances increases the overall size of the PNTD storage layer.
The PNTD in some embodiments is replicated partially across different instances. In other embodiments, the PNTD is replicated fully across different instances. Also, in some embodiments, the PNTD 955 within each instance is accessible only by the application(s) that run on top of the NOS of that instance. In other embodiments, the NOS can also access (e.g., read and/or write) the PNTD 955. In yet other embodiments, the PNTD 955 of one instance is only accessible by the NOS of that instance.
By allowing different NOS instances to store the same or overlapping NIB records, and/or secondary storage structure records, the system improves its overall resiliency by guarding against the loss of data due to the failure of any NOS or secondary storage structure instance. In some embodiments, each of the three storages of the secondary storage layer uses a different distribution technique to improve the resiliency of a multiple NOS instance system. For instance, as mentioned above, the system 900 of some embodiments replicates the PTD across NOS instances so that every NOS has a full copy of the PTD to enable a failed NOS instance to quickly reload its PTD from another instance. In some embodiments, the system 900 distributes the PNTD with overlapping distributions of data across the NOS instances to reduce the damage of a failure. The system 900 in some embodiments also distributes the DHT fully or with minimal overlap across multiple controller instances in order to maintain the DHT instance within each instance small and to allow the size of the DHT to be increased by adding additional DHT instances.
For some or all of the communications between the distributed instances, the system 900 uses the CMs 920. The CM 920 in each instance allows the instance to coordinate certain activities with the other instances. Different embodiments use the CM to coordinate the different sets of activities between the instances. Examples of such activities include writing to the NIB, writing to the PTD, writing to the DHT, controlling the switching elements, facilitating intra-controller communication related to fault tolerance of controller instances, etc. Several more detailed examples of the operations of the CMs in some embodiments are further described below in Section III.B.
As mentioned above, different controller instances of the system 900 can control the operations of the same switching elements or different switching elements. By distributing the control of these operations over several instances, the system can more easily scale up to handle additional switching elements. Specifically, the system can distribute the management of different switching elements and/or different portions of the NIB to different NOS instances in order to enjoy the benefit of processing efficiencies that can be realized by using multiple NOS instances. In such a distributed system, each NOS instance can have a reduced number of switches or a reduce portion of the NIB under management, thereby reducing the number of computations each controller needs to perform to distribute flow entries across the switches and/or to manage the NIB. In other embodiments, the use of multiple NOS instances enables the creation of a scale-out network management system. The computation of how best to distribute network flow tables in large networks is a CPU intensive task. By splitting the processing over NOS instances, the system 900 can use a set of more numerous but less powerful computer systems to create a scale-out network management system capable of handling large networks.
As noted above, some embodiments use multiple NOS instance in order to scale a network control system. Different embodiments may utilize different methods to improve the scalability of a network control system. Three example of such methods include (1) partitioning, (2) aggregation, and (3) consistency and durability. For a first method, the network control system of some embodiments configures the NOS instances so that a particular controller instance maintains only a subset of the NIB in memory and up-to-date. Further, in some of these embodiments, a particular NOS instance has connections to only a subset of the network elements, and subsequently, can have less network events to process.
A second method for improving scalability of a network control system is referred to as aggregation. In some embodiments, aggregation involves the controller instances grouping NOS instances together into sets. All the NOS instances within a set have complete access to the NIB entities representing network entities connected to those NOS instances. The set of NOS instances then exports aggregated information about its subset of the NIB to other NOS instances (which are not included in the set of NOS instances)
Consistency and durability is a third method for improving scalability of a network control system. For this method, the controller instances of some embodiments are able to dictate the consistency requirements for the network state that they manage. In some embodiments, distributed locking and consistency algorithms are implemented for network state that requires strong consistency, and conflict detection and resolution algorithms are implemented for network state that does not require strong consistency (e.g., network state that is not guaranteed to be consistent). As mentioned above, the NOS of some embodiments provides two data stores that an application can use for network state with differing preferences for durability and consistency. The NOS of some embodiments provides a replicated transactional database for network state that favors durability and strong consistency, and provides a memory-based one-hop DHT for volatile network state that can sustain inconsistencies.
In some embodiments, the above methods for improving scalability can be used alone or in combination. They can also be used to manage networks too large to be controlled by a single NOS instance. These methods are described in further detail in U.S. patent application entitled “A Distributed Control Platform for Large-scale Production Networks,” filed Jul. 6, 2011, with application Ser. No. 13/177,538, now issued as U.S. Pat. No. 8,830,823.
To distribute the workload and to avoid conflicting operations from different controller instances, the system 900 of some embodiments designates one controller instance (e.g., 905) within the system 900 as the master of any particular NIB portion and/or any given switching element (e.g., 990). Even with one master controller, different controller instance (e.g., 910 and 915) can request changes to different NIB portions and/or to different switching elements (e.g., 990) controlled by the master (e.g., 905). If allowed, the master instance then effectuates this change and writes to the desired NIB portion and/or switching element. Otherwise, the master rejects the request. More detailed examples of processing such requests are described below.
In the example illustrated in
Different embodiments use different techniques to propagate changes from the NIB 1360 of controller instance 1310 to NIB 1355 of the controller instance 1305. For instance, to propagate changes, the system 1300 in some embodiments uses the secondary storage structures (not shown) of the controller instances 1305 and 1310. More generally, the distributed control system of some embodiments uses the secondary storage structures as communication channels between the different controller instances. Because of the differing properties of the secondary storage structures, these structures provide the controller instances with different mechanisms for communicating with each other. For instance, in some embodiments, different DHT instances can be different, and each DHT instance is used as a bulletin board for one or more instances to store data so that they or other instances can retrieve this data later. In some of these embodiments, the PTDs are replicated across all instances, and some or all of the NIB changes are pushed from one controller instance to another through the PTD storage layer. Accordingly, in the example illustrated in
Instead of propagating the NIB changes through the secondary storages, the system 1300 uses other techniques to change the record S2a1 in the switch S2 in response to the request from control application 1320. For instance, to propagate this update, the NOS 1350 of the controller 1310 in some embodiments sends an update command to the NOS 1345 of the controller 1305 (with the requisite NIB update parameters that identify the record and one or more new values for the record) to direct the NOS 1345 to modify the record in the NIB 1355 or in the switch S2. In response, the NOS 1345 would make the changes to the NIB 1355 and the switch S2 (if such a change is allowed). After this change, the controller instance 1310 would change the corresponding record in its NIB 1360 once it receives notification (from controller 1305 or from another notification mechanism) that the record in the NIB 1355 and/or switch S2 has changed.
Other variations to the sequence of operations shown in
In the embodiments where the system 1300 allows for the designation of masters for switching elements and NIB records, the example illustrated in
In other embodiments, the controller instance 1305 might be the master of the NIB record S2a1, or the controller instance 1305 is the master of switch S2 and all the records for this NIB. In these embodiments, the request for the NIB record modification from the control application 1320 would have to be propagated the controller instance 1305, which would then modify the records in the NIB 1355 and the switch S2. Once this modification is made, the NIB 1360 would modify its record S2a1 once the controller instance 1310 is notified of this modification through any number of mechanisms that would propagate this modification to the controller instance 1310.
As mentioned above, different embodiments employ different techniques to facilitate communication between different controller instances. In addition, different embodiments implement the controller instances differently. For instance, in some embodiments, the stack of the control application(s) (e.g., 935 or 1315 in
II. NIB
The NIB 1400 performs functions that compose the heart of the NOS for several reasons. First, the NIB functions as a data storage structure for storing network configuration state information. In some embodiments, the NIB contains only physical network configuration state information while in other embodiments the NIB contains logical network configuration state information as well.
Second, in some embodiments, the NIB functions as a communication medium between NOS instances. The NOS instances replicate the NIB to some degree, with different embodiments of the invention replicating the NIB to varying degrees. This degree of replication allows the NIB to serve as a communication medium between NOS instances. For example, changes to the forwarding engine object 1460 and the forwarding table objects 1465 and 1470 may be replicated amongst all NOS instances, thereby sharing that information between NOS instances.
Third, in some embodiments, the NIB functions as an interface to allow higher-level applications to configure the underlying network. The NOS propagates changes made to the NIB to the underlying network, thus allowing higher-level applications to control underlying network state using the NIB. For example, if a higher-level application changes the configuration of forwarding engine 1410, then the NOS instance with authority over the physical switch corresponding to forwarding engine 1410 will propagate any changes made to forwarding engine 1410 down to the physical switch represented by forwarding engine 1410.
Fourth, in some embodiments, the NIB functions as a view of the network topology that the NOS can present to higher-level applications, and in some embodiments, application users. The conceptualization of NIB 1400 shown in
For sake of simplicity,
The operation of the NIB 1400 will now be discussed in conjunction with
The attributes shown in
The node class 1810 represents a point on the network that network data can move between. Examples are physical or virtual switches and hosts. As described in
The port class 1820 is the NIB analog to a port on a node. Ports are bound to nodes 1810. Ports have many statistics that are not shown in
The link class 1830 is the NIB analog to links between ports. Network data moves across links. Links have statistics describing their speed, weight, and usage. A link may have one start port and one end port. Typically, a port's incoming and outgoing link are bound to the same link object, to enable a link to serve as a bi-directional communication point. This is shown by the a solid arrow going from the attached link of port class 1820 to the link class 1830.
The queue-collection class 1840 is the NIB analog to the set of 8 queues associated with the egress ports of industry standard top of rack switches. Queue-collections are groups of queues that can have ports bound to them. The queue-collection class enables network administrators to select one queue-collection to manage many ports, thereby placing a consistent quality of service policy across many ports. The queue class 1850 is the NIB analog to the queues attached to egress ports that schedule packets for processing. The queue class contains statistics and information regarding which queue-collection the queue is bound to. Additionally, the queue class has an attribute to describe the identity of the queues above and below the queue.
The chassis class 1910 is the NIB analog to a physical rack of switches. The chassis class contains a plurality of forwarding engines and addresses the chassis manages. The NIB 1400 has a chassis 1440 with pointers to forwarding engines 1460 and 1410. The forwarding engine class 1920 is the NIB analog to a network switch. The forwarding engine contains a set of forwarding tables that can define the forwarding behavior of a switch on the network. The NIB 1400 has a forwarding engine 1460 with two pointers to two forwarding tables 1465 and 1470. The forwarding engine also contains the datapath ID that a controller uses to communicate with the forwarding engine.
The forwarding table class 1930 is the NIB analog of the forwarding tables within switches that contain rules governing how packets will be forwarded. The forwarding table class 1930 contains flow entries to be propagated by NOS instances to the forwarding tables of network switches. The flow entries contained in the forwarding table class are the basic unit of network management. A flow entry contains a rule for deciding what to do with a unit of network information when that unit arrives in a node on the network. The forwarding table class further supports search functions to find matching flow entries on a forwarding table object.
The host class 1950 is the NIB analog to the physical computers of the network. Typical hosts often have many virtual machines contained within them. A host's virtual machines may belong to different users. The host class 1950 supports a list of users. The user class 1960 is the NIB analog to the owner of virtual machines on a host. The network class 1940 serves as a black box of network elements that behave in a similar fashion to a node. Packets enter a network and exit a network, but the NOS instances are not concerned with the internal workings of a network class object.
An application can query a NIB object to learn its status. A NOS instance can create a NIB entity to reflect a new element being added to the physical network. A user can destroy a logical datapath in some embodiments. A NOS instance can access the attributes of another NOS instance's NIB entities. A transfer module may register for notification for changes to the data of a NIB entity object. A NOS instance can issue a synchronize command to synchronize NIB entity object data with data gathered from the physical network. An application can issue a “pull entity into the NIB” command to compel a NOS instance to add a new entity object to the NIB.
III. Multi-Instance Architecture
Also, like the control system 900, each controller instance includes a NOS 2125, a virtualization application 2130, one or more control applications 2135, and a coordination manager (CM) 2120. Each NOS in the system 2100 includes a NIB 2140 and at least two secondary storage structures, e.g., a distributed hash table (DHT) 2150 and a PNTD 2155.
However, as illustrated in
In some embodiments, the notification module 2170 in each controller instance allows applications (e.g., a control application) that run on top of the NOS to register for callbacks when changes occur within the NIB. This module in some embodiments has two components, which include a notification processor and a notification registry. The notification registry stores the list of applications that need to be notified for each NIB record that the module 2170 tracks, while the notification processor reviews the registry and processes the notifications upon detecting a change in a NIB record that it tracks. The notification module as well as its notification registry and notification processor are a conceptual representation of the NIB-application layer notification components of some embodiments, as the system of these embodiments provides a separate notification function and registry within each NIB object that can be tracked by the application layer.
The transfer modules 2175 include one or more modules that allow data to be exchanged between the NIB 2140 on one hand, and the PTD or DHT storage layers in each controller instance on the other hand. In some embodiments, the transfer modules 2175 include an import module for importing changes from the PTD/DHT storage layers into the NIB, and an export module for exporting changes in the NIB to the PTD/DHT storage layers. The use of these modules to propagate data between the NIB and PTD/DHT storage layers will be further described below.
Unlike the control system 900 that has the same type of PTD in each instance, the control system 2100 only has PTDs in some of the NOS instances, and of these PTDs, one of them serves as master PTD 2145, while the rest serve as slave PTDs 2147. In some embodiments, NIB changes within a controller instance that has a slave PTD are first propagated to the master PTD 2145, which then directs the controller instance's slave PTD to record the NIB changes. The master PTD 2145 similarly receives NIB changes from controller instances that do not have either master or slave PTDs. The use of the master PTDs in processing NIB changes will be further described below.
In the control system 2100, the coordination manager 2120 includes the CM interface 2160 to facilitate communication between the NIB storage layer and the PTD storage layer. The CM interface also maintains the PTD trigger list 2180, which identifies the modules of the system 2100 to call back whenever the CM interface 2160 is notified of a PTD record change. A similar trigger list 2185 for handling DHT callbacks is maintained by the DHT instance 2150. The CM 2120 also has a DHT range identifier (not shown) that allows the DHT instances of different controller instances to store different DHT records in different DHT instances. The operations that are performed through the CM, the CM interface, the PTD trigger list, and the DHT trigger list will be further described below.
Also, in the control system 2100, the PNTD is not placed underneath the NIB storage layer. This placement is to signify that the PNTD in the control system 2100 does not exchange data directly with the NIB storage layer, but rather is accessible solely by the application(s) (e.g., the control application) running on top of the NOS 2125 as well as other applications of other controller instances. This placement is in contrast to the placement of the PTD storage layer 2145/2147 and DHT storage layers 2150, which are shown to be underneath the NIB storage layer because the PTD and DHT are not directly accessible by the application(s) running on top of the NOS 2125. Rather, in the control system 2100, data are exchanged between the NIB storage layer and the PTD/DHT storage layers of the same or different instances.
The control system 2100 uses the PTD, DHT and PNTD storage layers to facilitate communication between the different controller instances. In some embodiments, each of the three storages of the secondary storage layer uses a different storage and distribution technique to improve the resiliency of the distributed, multi-instance system 2100. For instance, as further described below, the system 2100 of some embodiments replicates the PTD across NOS instances so that every NOS has a full copy of the PTD to enable a failed NOS instance to quickly reload its PTD from another instance. On the other hand, the system 2100 in some embodiments distributes the PNTD with partial overlapping distributions of data across the NOS instances to reduce the damage of a failure. Similarly, the system 2100 in some embodiments distributes the DHT fully or with minimal overlap across multiple controller instances in order to minimize the size of the DHT instance (e.g., the amount of memory the DHT instance utilizes) within each instance. Also, using this approach allows the system to increase the size of the DHT by adding additional DHT instances in order to make the system more scalable.
One of the advantages of this system is that it can be configured in any number of ways. In some embodiments, this system provides great flexibility to specify the configurations for the components of the system in order to customize its storage and data distribution scheme to achieve the best tradeoff of scalability and speed on one hand, and reliability and consistency on the other hand. Attributes of the storage structures that affect scalability, speed, reliability and consistency considerations include the speed of the storage (e.g., RAM versus disk access speed), the reliability of the storage (e.g., persistent non-volatile storage of disk versus volatile storage of RAM), the query interface of the storage (e.g., simple Put/Get query interface of DHT versus more robust transactional database queries of PTD in some embodiments), and the number of points of failure in the system (e.g., a single point of failure for a DHT record versus multiple points of failure for a PTD record in some embodiments).
Through the configurations of its components, the system can be configured to (1) distribute the data records between the NIB and the secondary storage structures within one instance (e.g., which secondary storage should store which NIB record), (2) distribute the data records between the NIBs of different instances (e.g., which NIB records should be replicated across different controller instances), (3) distribute the data records between the secondary storage structures within one instance (e.g., which secondary storage records contain which records), (4) distribute the data records between the secondary storage structures of different instances (e.g., which secondary storage records are replicated across different controller instances), (5) distribute secondary storage instances across controller instances (e.g., whether to put a PTD, a DHT, or a Stats database instance within each controller or whether to put different subsets of these storages within different instances), and (6) replicate data records in the distributed secondary storage structures (e.g., whether to replicated PTD fully across all instances, whether to replicate some or all DHT records across more than one instance, etc.). The system also allows the coordination between the different controller instances as to the master control over different switching elements or different portions of the NIB to be configured differently. In some embodiments, some or all of these configurations can be specified by applications (e.g., a control application or a virtualization application) that run on top of the NOS.
In some embodiments, as noted above, the CMs facilitate intra-controller communication related to fault tolerance of controller instances. For instance, the CMs implement the intra-controller communication through the secondary storage layers described above. A controller instance in the control system may fail due to any number of reasons (e.g., hardware failure, software failure, network failure, etc.). Different embodiments may use different techniques for determining whether a controller instance has failed. In some embodiments, Paxos protocol is used to determine whether a controller instance in the control system has failed. While some of these embodiments may use Apache Zookeeper to implement the Paxos protocol, other of these embodiments may implement Paxos protocol in other ways.
Some embodiments of the CM 2120 may utilize defined timeouts to determine whether a controller instance has failed. For instance, if a CM of a controller instance does not respond to a communication (e.g., sent from another CM of another controller instance in the control system) within an amount of time (i.e., a defined timeout amount), the non-responsive controller instance is determined to have failed. Other techniques may be utilized to determine whether a controller instance has failed in other embodiments.
When a controller instance fails, a new master for the logical datapath sets and the switching elements, of which the failed controller instance was a master, needs to be determined. Some embodiments of the CM 2120 make such determination by performing a master election process that elects a master controller instance (e.g., for partitioning management of logical datapath sets and/or partitioning management of switching elements). The CM 2120 of some embodiments may perform a master election process for electing a new master controller instance for both the logical datapath sets and the switching elements of which the failed controller instance was a master. However, the CM 2120 of other embodiments may perform (1) a master election process for electing a new master controller instance for the logical datapath sets of which the failed controller instance was a master and (2) another master election process for electing a new master controller instance for the switching elements of which the failed controller instance was a master. In these cases, the CM 2120 may determine two different controller instances as new controller instances: one for the logical datapath sets of which the failed controller instance was a master and another for the switching elements of which the failed controller instance was a master.
In some embodiments, the master election process is further for partitioning management of logical datapath sets and/or management of switching elements when a controller instance is added to the control system. In particular, some embodiments of the CM 2120 perform the master election process when the control system 2100 detects a change in membership of the controller instances in the control system 2100. For instance, the CM 2120 may perform the master election process to redistribute a portion of the management of the logical datapath sets and/or the management of the switching elements from the existing controller instances to the new controller instance when the control system 2100 detects that a new network controller has been added to the control system 2100. However, in other embodiments, redistribution of a portion of the management of the logical datapath sets and/or the management of the switching elements from the existing controller instances to the new controller instance does not occur when the control system 2100 detects that a new network controller has been added to the control system 2100. Instead, the control system 2100 in these embodiments assigns unassigned logical datapath sets and/or switching elements (e.g., new logical datapath sets and/or switching elements or logical datapath sets and/or switching elements from a failed network controller) to the new controller instance when the control system 2100 detects the unassigned logical datapath sets and/or switching elements have been added.
The control system's use of the PTD, DHT and PNTD storage layers to facilitate communication between the different controller instances will be described further in sub-section III.A below. This discussion will then be followed by a discussion of the operations of the CM 2120 in sub-section III.B. Section IV then describes the architecture of a single controller instance of the system 2100 in some embodiments.
A. Facilitating Communication in Distributed System
The distributed control system 2100 of some embodiments uses the secondary storage structures as communication channels between the different controller instances 2105, 2110, and 2115. The distributed control system of some embodiments makes such a use of the secondary storage structures because it provides a robust distributed logic, where often the rules for distributing a data record reside in the storage layer adjacent to the data record. This scheme is also advantageous as it modularizes the design of the different components of the distributed system. It also simplifies the addition of new controller instances in the system. It further allows some or all of the applications running on top of the NOS (e.g., the control application(s) and/or the virtualization application) within each instance to operate as an independent logical silo from the other controller instances, as the application does not need to know how the system distributes control over the switching elements.
Because of the differing properties of the secondary storage structures, the secondary storage structures provide the controller instances with different mechanisms for communicating with each other. For instance, the control system 2100 uses the PTD storage layer to push data between different controller instances, while it uses the DHT storage layer to enable different controller instances to post data and pull data from the DHT storages.
Specifically, in some embodiments, different DHT instances can be different, and each DHT instance is used as a bulletin board for one or more instances to store data so that they or other instances can retrieve this data later. In some embodiments, the DHT is a one-hop, eventually-consistent, memory-only DHT. A one-hop DHT, in some embodiments, is configured in a full mesh such that each DHT instance is connected to each other DHT instance. In this way, if a particular DHT instance does not have piece of data, the particular DHT instance can retrieve the piece of data from another DHT instance that is “one-hop” away instead of having to traverse multiple DHT instances in order to retrieve the piece of data. However, the system 2100 in some embodiments maintains the same switch element data records in the NIB of each instance, and replicates some or all of the NIB records in the PTDs 2145 and 2147 of the controller instances 2105 and 2110. By replicating the PTDs across all instances, the system 2100 pushes NIB changes from one controller instance to another through the PTD storage layer. Pushing the NIB changes through the PTD storage layer involves the use of the master PTD 2145.
While maintaining some of the NIB records in the PTD, the system 2100 in some embodiments maintains a portion of the NIB data in the DHT instance 2150. The DHT instance in some embodiments is a distributed storage structure that is stored in the volatile system memory with minimal replications to enable greater scalability. As discussed above, applications can configure the distribution of NIB data records between the PTD and the DHT. In some embodiments, the typical configuration distributes fast changing information (e.g., link state, statistics, entity status) to the DHT and slow changing information (e.g., existence node and port entities) to the PTD.
Performing NIB and PTD replication through the master PTD will be described in sub-section III.A.1 below. Sub-section III.A.2 will then describe distributing data among the controller instances through the DHT storage layer. Sub-section III.A.3 then describes distributing data among controller instances through the PNTD storage layer.
1. PTD Replication
In some embodiments, the system 2100 maintains the same switch element data records in the NIB of each instance. In the NIBs, the system 2100 stores physical network data and in some embodiments logical network data. The system 2100 of some embodiments stores some or all of the records of each instance's NIB in that instance's PTD. For instance, in some embodiments, the system 2100 stores in the PTDs slow changing network state data (e.g., network policy declarations, switching element inventories, other physical network element inventories, etc.) that needs to be stored in a more durable manner but does not need to be frequently updated.
By replicating the PTDs across all instances, the system 2100 pushes some or all of the NIB changes from one controller instance to another through the PTD storage layer.
The flow diagram 2205 conceptually illustrates the propagation of a change in a NIB 2235 of the first controller 2220 to a NIB 2245 of the second controller 2225, through the PTDs 2240 and 2250 of these two controllers 2220 and 2225. In this diagram as well as the other three diagrams, the NIBs 2235 and 2245 are shown above a dashed line 2255 and the PTDs 2240 and 2250 are shown below the dashed line 2255 in order to convey that the NIBs are part of a NIB storage layer across all of the controller instances, while the PTDs are part of a PTD storage layer across all of the controller instances.
In the flow diagram 2205 as well as the other three diagrams, the flow of data between components is indicated by way of arrows and numbers, with each number indicating an order of an operation in the flow of data between the layers. Accordingly, the flow diagram 2205 shows that the change in the NIB 2235 is initially transferred to the PTD 2240 within the same controller instance 2220. This change is then pushed to the PTD 2250 of the second controller instance 2225. From there, the change is propagated to the NIB 2245 of the second controller instance 2225.
The flow diagram 2205 is illustrative of the sequence of operations that are performed to propagate a NIB change through the PTD storage layer. However, for the control system 2100 of some embodiments, the flow diagram 2205 simply illustrates the concept of propagating a NIB change through the PTD storage layer. It is not an illustration of the actual sequence of operations for propagating a NIB change in such a system, because the control system 2100 uses a master PTD 2145 as a single point of replication to ensure consistency across the PTD layers 2240, 2260, and 2250.
While ignoring the operations of the CM and CM interface, the flow diagram 2210 provides a more representative diagram of the sequence of operations for propagating a NIB change in the system 2100 for some embodiments of the invention. This diagram shows that in the system 2100 of some embodiments, the first controller's PTD 2240 pushes a NIB change that it receives from its NIB 2235 to a master PTD 2260, which may reside in another controller instance 2230, as illustrated in diagram 2210. The master PTD 2260 then directs each slave PTD 2240 and 2250 to update their records based on the received NIB change. In the embodiment illustrated in flow diagram 2210, the master PTD 2260 even notifies the PTD 2240 to update its records. In other words, the system of some embodiments does not make a NIB change in the PTD of the instance that originated the NIB change, without the direction of the master PTD 2260. In some embodiments, instead of the master PTD sending the changed PTD record to each slave PTD, the master PTD notifies the slave instances of the PTD change, and then the slave instances query the master PTD to pull the changed PTD record.
Once the slave PTDs 2240 and 2250 notify the master PTD 2260 that they have updated their records based on the NIB change, the master PTD directs all the NIBs (including the NIB 2245 of the second controller instance 2225 as well as a NIB 2270 of the third controller instance 2230) to modify their records in view of the NIB change that originated from controller instance 2220. The master PTD 2260 in some embodiments effectuates this modification through the CM interface and a NIB import module that interfaces with the CMI. This NIB import module is part of the NIB transfer module 2175 that also includes a NIB export module, which is the module used to propagate the NIB change from the NIB 2235 to the PTD 2240. In some embodiments, the master PTD notifies the NIB import module of the changed PTD record, and in response the NIB import module queries the master PTD for the changed record. In other embodiments, the master PTD sends to the NIB import module the changed PTD record along with its notification regarding the change to its record. The use of the CM interface, the NIB export module, and the NIB import module to effectuate NIB-to-NIB replication will be further described below.
The flow diagram 2215 presents an alternative data flow to the diagram 2210 for the NIB-to-NIB replication operations that involve the master PTD in some embodiments. The flow 2215 is identical to the flow 2210 except that in the flow 2215, the master PTD is only responsible for notifying its own NIB 2270 of the NIB change as it is not responsible for directing the NIB 2245 of the instance 2225 (or the NIB of any other slave instance) to make the desired NIB change. The NIB change is propagated in the diagram 2215 to the NIB 2245 through the PTD 2250 of the second instance. In different embodiments, the PTD 2250 uses different techniques to cause the NIB 2245 to change a record. In some embodiments, the PTD 2250 notifies the import module of NIB 2245 of the changed PTD record, and in response the NIB import module queries the PTD 2250 for the changed record. In other embodiments, the PTD 2250 sends to the import module of the NIB 2245 the changed PTD record along with its notification regarding the change to its record.
The flow diagram 2217 presents yet another alternative data flow to the diagrams 2210 and 2215 for the NIB-to-NIB replication operations that involve the master PTD in some embodiments. The flow 2217 is identical to the flow 2210 except that in the flow 2217, the slave NIB 2235 directly notifies the master PTD 2260 of the change to its NIB. In other words, the notification regarding the change in the NIB 2235 is not relayed through slave PTD 2240. Instead, the export module of the slave NIB 2235 directly notifies the master PTD 2260 (through the CM interface (not shown)). After being notified of this change, the master PTD 2260 in the flow 2217 first notifies the slave PTDs 2240 and 2250, and then notifies the slave NIB 2245 and its own NIB 2270, as in the flow diagram 2210.
The control systems of other embodiments use still other alternative flows to those illustrated in diagrams 2210, 2215 and 2217. For instance, another flow involves the same sequence of operations as illustrated in diagrams 2210 and 2215, except that the PTD 2240 of the instance 2220 records the NIB change before the master PTD is notified of this change. In this approach, the master PTD would not have to direct the PTD 2240 to modify its records based on the received NIB change. The master PTD would only have to notify the other slave PTDs of the change under this approach.
Other control systems of other embodiments use still other flows to those illustrated in diagrams 2210, 2215, and 2217. For instance, in some systems that do not use master PTDs, the flow illustrated in diagram 2205 is used to replicate a NIB change across instances. Yet another flow that such systems use in some embodiments would be similar to the flow illustrated in the diagram 2205, except that the PTD 2240 would be the component that notifies the NIB 2245 of the NIB change after the PTD 2240 notifies the PTD 2250 of the NIB change.
2. DHT Access
In the control system 2100 of some embodiments, the DHT instances 2150 of all controller instances collectively store one set of records that are indexed based on hashed indices for quick access. These records are distributed across the different controller instances to minimize the size of the records within each instance and to allow for the size of the DHT to be increased by adding additional DHT instances. According to this scheme, one DHT record is not stored in each controller instance. In fact, in some embodiments, each DHT record is stored in at most one controller instance. To improve the system's resiliency, some embodiments, however, allow one DHT record to be stored in more than one controller instance, so that in case one DHT record is no longer accessible because of one instance failure, that DHT record can be accessed from another instance. The system of some embodiments stores in the DHT rapidly changing network state that is more transient in nature. This type of data often can be quickly re-generated. Accordingly, some of these embodiments do not allow for replication of records across different DHT instances or only allow a small amount of such records to be replicated. In some embodiments, rapidly changing NIB data is stored in the DHT to take advantage of the DHT's aforementioned properties.
Because the system of these embodiments does not replicate DHT records across all DHT instances, it needs to have a mechanism for identifying the location (or the primary location in case of a DHT record that is stored within more than one DHT) of a DHT record. The CM 2120 provides such a mechanism in some embodiments of the invention. Specifically, as further described below, the CM 2120 of some embodiments maintains a hash value range list that allows the DHT instances of different controller instances to store different DHT records in different DHT instances.
In
The flow diagram 2405 shows that the change in the NIB 2430 is initially transferred to the DHT instance 2435 within the same controller instance 2415. The DHT instance does not necessarily change the records that it keeps because the DHT instance 2435 might not store a DHT record that corresponds to the changed NIB record for which it receives the notification from NIB 2430. Hence, in response to the NIB change notification that it receives, the DHT instance checks the hash value range list 2460 to identify the DHT instance that stores the DHT-layer record that corresponds to the modified NIB record. To identify this DHT instance, the DHT instance 2435 uses a hash index for the DHT record that it needs to locate. In some embodiments, the DHT instance 2435 generates this hash value when it receives the NIB change notification from the NIB 2430.
Based on the hash index, the DHT instance 2435 obtains the identity of DHT instance 2440 from the DHT range list 2460. The DHT instance 2435 then directs the DHT instance 2440 to modify its DHT record to reflect the received NIB change. In some embodiments, the DHT instance 2435 directs the DHT instance 2440 to modify its records, by supplying the DHT instance 2440 with a Put command, which supplies the DHT instance 2440 with a key, a hash value based on the key, and a value to store along with the hash value. The DHT instance 2440 then modifies its DHT records based on the request that it receives from the DHT instance 2435.
The flow diagram 2410 shows the NIB 2450 of the third controller instance 2425 pulling from DHT instance 2440 the record that was created at the end of the flow illustrated in diagram 2405. Specifically, it shows the DHT instance 2445 of the third controller instance 2425 receiving a DHT record request from its corresponding NIB 2450. The NIB 2450 might need to pull a DHT record for a variety of reasons. For instance, when the NIB creates a new node for a new port, it might need to obtain some statistics regarding the port to populate its NIB records.
In response to the received DHT record request, the DHT instance 2445 checks the hash value range list 2460 to identify the DHT instance that stores the requested DHT record. To identify this DHT instance, the DHT instance 2445 uses a hash index for the DHT record that it needs to locate. In some embodiments, the DHT instance 2445 generates this hash value when it receives the request from the NIB 2450.
Based on the hash index, the DHT instance 2445 obtains the identity of DHT instance 2440 from the DHT range list 2460. The DHT instance 2445 then directs the DHT instance 2440 to provide the requested DHT record. In some embodiments, the DHT instance 2445 directs the DHT instance 2440 for the requested record, by supplying the DHT instance 2440 with a Get command, which supplies the DHT instance 2440 with a key and/or a hash value based on the key. The DHT instance 2440 then supplies the value stored in the specified DHT record to the DHT instance 2445, which, in turn, supplies this value to the NIB 2450.
3. PNTD
As described above, the system 2100 includes a PNTD 2155 in some embodiments of the invention. The PNTD stores information for a user or application to review. Examples of such information include error messages, log files, and billing information. The PNTD can receive push or pull commands from the application layer above the NOS, as illustrated in
In some embodiments, the PNTD is a distributed software database, such as Cassandra. For example, in some embodiments, each instance's PNTD stores the records generated by that instance's applications or by other applications of other instances. Each instance's PNTD records can be locally accessed or remotely accessed by the other controller instances whenever these instances need these records. This distributed nature of the PNTD allows the PNTD to be scalable as additional controller instances are added to the control system. In other words, addition of other controller instances increases the overall size of the PNTD storage layer.
The system 2100 uses the PNTD to store information in a durable manner that does not require the same degree of replication as the PTD 2145. In some embodiments, the PNTD is stored on a non-volatile storage medium, such as a hard disk.
The PNTD 2155 is a distributed storage structure similar to the DHT instance 2150. Similar to the DHT, data records in the PNTD are distributed across each NOS controller instance that has a PNTD. However, unlike the DHT or the PTD, the PNTD 2155 has no support for any trigger or notification functionality. Similar to the DHT instance 2150, the PNTD 2155 has a configurable level of replication. In some embodiments, data records are stored only once across the entire system, in other embodiments the data records are replicated across a configurable portion of the controller instances running a PNTD to improve the resiliency of the data records. In other words, the PNTD in some embodiments is not replicated across different instances or is only partially replicated across different instances, while in other embodiments, the PNTD is replicated fully across different instances.
B. Coordination Manager
In some embodiments, the different controller instances of the system 2100 communicate with each other through the secondary storage structures, as described above. Also, as described above, the system 2100 in some embodiments uses the CMs 2120 to facilitate much of the communication between the secondary storages of the different controller instances. The CM 2120 in each instance is also configured in some embodiments to specify control of different controller instances over different switching elements.
As shown in
The NIB-to-PTD interface 2510 serves as the interface to facilitate communications between NIB and PTD storage layers. On the NIB side, the interface 2510 communicates with transfer modules that import and export data to and from the NIB. On the PTD side, the interface 2510 in some embodiments communicates (1) with the CM-to-CM interface 2505 (through the CM processor 2530) to facilitate communication between master and slave PTDs, (2) with the query manager of the PTD to effectuate a PTD access (e.g., a PTD write), and (3) with the query manager of the PTD to receive PTD layer callbacks when records change in the PTD. In some embodiments, the interface 2510 converts NIB queries to the PTD into a query format that is suitable for the PTD. In other embodiments, however, the NIB transfer modules provide the PTD queries in a format suitable for the PTD.
The CM processor 2530 receives communications from each interface 2505 or 2510. It routes such communications to the other interface, if needed, or to the other modules of the CM 2500, if needed. One example of a communication that the CM processor routes to the appropriate CM module is a PTD trigger call back that it receives from the PTD of its controller instance. As further described below, the PTD can be configured on a record-by-record basis to call back the CM when a particular record has changed. The CM uses the PTD trigger tracker 2525 to maintain a PTD trigger list 2570 that allows the CM to identify for different PTD records, different sets of modules within the same controller instance or within other controller instances that the CM needs to notify of the particular record's change in its associated PTD. Maintaining the PTD trigger list outside of the PTD is beneficial for several reasons, including keeping the size of the PTD small, avoiding replication of such lists across PTDs, etc.
The CM processor 2530 also uses the ordering module 2550 to maintain the ordering of the inter-instance communications and/or tasks. To maintain such ordering, the ordering modules of different embodiments use different processes and ordering schemes. Some of these ordering processes maintain total ordering among packets exchanged between the different controller instances. Examples of such ordering processes include the Paxos protocols and processes.
In some embodiments, the ordering module includes a time stamper to timestamp each communication that it receives that needs inter-instance coordination. The timestamps allow the CM 2500 to process communications in an appropriate sequential manner to ensure data consistency and reliability across the instances for the communications (e.g., PTD storage layer communications) that need such consistency and reliability. Instead of a time stamper, the CM processor 2530 uses other techniques or modules in other embodiments to ensure that the communications that it receives are processed in the appropriate sequential manner to facilitate the proper coordination of activities between the different controller instances, as mentioned above.
The CM processor 2530 also directs the DHT range identifier 2545 to generate and update the DHT range list 2565. In some embodiments, the CM processor directs the range identifier to update the range list 2565 periodically or upon receiving a communication through one of the interfaces 2505 or 2510. As discussed above, the DHT instances use the range list 2565 to identify the location of each DHT record in the DHT instances. In some embodiments, the DHT instances access the DHT range list directly, while in other embodiments the DHT instances access this list through the CM, which they access through a DHT-to-CM interface (not shown).
In addition to the DHT range list and the PTD trigger list, the CM 2500 maintains four other lists, which are the CM instance list 2560, the NOS instance list 2540, the switching element master list 2520, and the NIB master list 2575. The CM instance list 2560 is a list of all active CM instances, and this list is maintained by CM Instance tracker 2555. The NOS instance list 2540 is a list of all active NOS instances and this list is maintained by the NOS tracker 2535.
The switch element and the NIB master lists 2520 and 2575 are maintained by the master tracker 2515. In some embodiments, the switching element master list identifies a master controller instance for each switching element, and one or more back-up controller instances for each master controller in case the master controller fails. The CM 2500 designates one controller instance within the control system as the master of any given switching element, in order to distribute the workload and to avoid conflicting operations from different controller instances. By distributing the control of these operations over several instances, the system can more easily scale up to handle additional switching elements.
In some embodiments, the NIB master list 2575 identifies (1) a master for each portion (e.g., each record or set of records) of the NIB, (2) one or more back up controller instances for each identified master to use in case the master fails, and (3) access and/or modification rights for each controller instance with respect to each portion of NIB. Even with one master controller as master of a portion of the NIB, different controller instances can request a change to the portion controlled by the master. If allowed, the master instance effectuates this change, which is subsequently written to the switching element by the switch element master. Otherwise, the master rejects the request.
Some embodiments use the access and/or modification rights in the NIB master list to restrict changes to different portions of the NIB to different subsets of the controller instances. Each subset might only include in some embodiments the master controller instance that can modify the NIB portion or the switching element record that corresponds to the NIB portion that is subject to the requested change. Alternatively, in some embodiments, a subset might include one or more controller instances in addition to the master controller instance for the NIB portion.
In some embodiments, a first controller instance can be master of a switch and a second controller instance can be master of a corresponding record for that switch in the NIB. In such a case, the second controller instance would determine whether a requested change to the NIB is allowed (e.g., from a control application of any of the controller instances), while the first controller instance would modify the switch records if the second controller instance modifies the NIB in response to the requested change. If a request to change the NIB is not allowed, the NIB master controller (e.g., the second instance in the example above) would reject the request. Different embodiments use different techniques to propagate NIB modification requests through a control system, and some of these techniques are described below.
In some embodiments, each controller instance queries its CM 2500 to determine whether it is the master of the NIB portion for which it receives a NIB change, or whether it is the master of the switching element for which it has detected a change in the NIB. The CM 2500 then examines its NIB master list 2575 (e.g., through the CM processor 2530 and master tracker 2515) or its switch master list 2520 (e.g., through the CM processor 2530 and master tracker 2515) to determine whether the instance is the master of the switching element.
By allowing rights to be specified for accessing and/or modifying NIB records, the CM 2500 allows the control system 2100 to partition management of logical datapath sets (also referred to as serialized management of logical datapath sets). Each logical datapath set includes one or more logical datapaths that are specified for a single user of the control system. Partitioning management of the logical datapath sets involves specifying for each particular logical datapath set only one controller instance as the instance responsible for changing NIB records associated with that particular logical datapath set. For instance, when the control system uses three switching elements to specify five logical datapath sets for five different users with two different controller instances, one controller instance can be the master for NIB records relating to two of the logical datapath sets while the other controller instance can be the master for the NIB records for the other three logical datapath sets. Portioning management of logical datapath sets ensures that conflicting values for the same logical datapath sets are not written to the NIB by two different controller instances, and thereby alleviates the applications running on top of the NOS from guarding against the writing of such conflicting values.
Irrespective of whether the control system partitions management of logical datapath sets, the control system of some embodiments allows one control application that operates on controller instance to request that the control system lock down or otherwise restrict access to one or more NIB records for an entire logical datapath set or a portion of it, even when that controller instance is not the master of that logical datapath set. In some embodiments, this request is propagated through the system (e.g., by any propagation mechanism, including NIB/PTD replication, etc.) until it reaches the controller instance that is the master of the NIB portion. In some embodiments, the system allows each lock down operation to be specified in terms of one or more tasks that can be performed on one or more data records in the NIB.
The CM 2500 of the master controller determines whether a request to lock down or otherwise restrict access to a set of NIB records is allowed. If so, it will modify the records in its NIB master list so that subsequent requests for modifying the affected set of NIB records by other controller instances will be appropriately restricted.
In some embodiments, the CMs across all of the controller instances perform unified coordination activity management in a distributed manner. This coordination is facilitated by the CM processor 2530 and the procedures that it follows. In some embodiments, some or all of the modules of the CM 2500 are implemented by using available coordination management applications. For instance, some embodiments employ the Apache Zookeeper application to implement some or all of the modules of the CM 2500.
As mentioned above, the CMs of some embodiments facilitate intra-controller communication related to fault tolerance of controller instances. As such, some embodiments of the CM-to-CM interface 2505 pass these fault tolerance communications between the different CMs of the different controller instances. In some of these embodiments, the CM processor 2530 executes Apache Zookeeper, which implements the Paxos protocols, for determining whether a controller instance has failed. In addition, the CM processor 2530 of some such embodiments defines a timeout for determining that a controller instance is non-responsive and thus has failed. In other such embodiments, the timeout may be predefined. Furthermore, upon failure of a controller instance, some embodiments of the CM processor 2530 may be responsible for performing a master election process(es) to elect a new master controller instance (e.g., for logical datapath sets and switching elements of which the failed controller instance was a master) to replace the failed controller instance.
IV. Controller Instance
A. Architecture
Also, in some embodiments, the NOS instance 2600 provides multiple methods for applications to gain access to network entities. For instance, in some embodiments, it maintains an index of all of its entities based on the entity identifier, allowing for direct querying of a specific entity. The NOS instance of some embodiments also supports registration for notifications on state changes or the addition/deletion of an entity. In some embodiments, the applications may further extend the querying capabilities by listening for notifications of entity arrival and maintaining their own indices. In some embodiments, the control for a typical application is fairly straightforward. It can register to be notified on some state change (e.g., the addition of new switches and ports), and once notified, it can manipulate the network state by modifying the NIB data tuple(s) (e.g., key-value pairs) of the affected entities.
As shown in
The application interface 2605 is a conceptual illustration of the interface between the NOS and the applications (e.g., control and virtualization applications) that can run on top of the NOS. The interface 2605 includes the NOS APIs that the applications (e.g., control or virtualization application) running on top of the NOS use to communicate with the NOS. In some embodiments, these communications include registrations for receiving notifications of certain changes in the NIB 2620, queries to read certain NIB attributes, queries to write to certain NIB attributes, requests to create or destroy NIB entities, instructions for configuring the NOS instance (e.g., instructions regarding how to import or export state), requests to import or export entities on demand, and requests to synchronize NIB entities with switching elements or other NOS instances.
The switch interface 2655 is a conceptual illustration of the interface between the NOS and the switching elements that run below the NOS instance 2600. In some embodiments, the NOS accesses the switching elements by using the OpenFlow or OVS APIs provided by the switching elements. Accordingly, in some embodiments, the switch interface 2655 includes the set of APIs provided by the OpenFlow and/or OVS protocols.
The NIB 2620 is the data storage structure that stores data regarding the switching elements that the NOS instance 2600 is controlling. In some embodiments, the NIB just stores data attributes regarding these switching elements, while in other embodiments, the NIB also stores data attributes for the logical datapath sets defined by the user. Also, in some embodiments, the NIB is a hierarchical object data structure (such as the ones described above) in which some or all of the NIB objects not only include data attributes (e.g., data tuples regarding the switching elements) but also include functions to perform certain functionalities of the NIB. For these embodiments, one or more of the NOS functionalities that are shown in modular form in
The hash table 2624 is a table that stores a hash value for each NIB object and a reference to each NIB object. Specifically, each time an object is created in the NIB, the object's identifier is hashed to generate a hash value, and this hash value is stored in the hash table along with a reference (e.g., a pointer) to the object. The hash table 2624 is used to quickly access an object in the NIB each time a data attribute or function of the object is requested (e.g., by an application or secondary storage). Upon receiving such requests, the NIB hashes the identifier of the requested object to generate a hash value, and then uses that hash value to quickly identify in the hash table a reference to the object in the NIB. In some cases, a request for a NIB object might not provide the identity of the NIB object but instead might be based on non-entity name keys (e.g., might be a request for all entities that have a particular port). For these cases, the NIB includes an iterator that iterates through all entities looking for the key specified in the request.
The notification processor 2610 interacts with the application interface 2605 to receive NIB notification registrations from applications running on top of the NOS and other modules of the NOS (e.g., such as an export module within the transfer modules 2630). Upon receiving these registrations, the notification processor 2610 stores notification requests in the notification registry 2615 that identifies each requesting party and the NIB data tuple(s) that the requesting party is tracking.
As mentioned above, the system of some embodiments embeds in each NIB object a function for handling notification registrations for changes in the value(s) of that NIB object. For these embodiments, the notification processor 2610 is a conceptual illustration of the amalgamation of all the NIB object notification functions. Other embodiments, however, do not provide notification functions in some or all of the NIB objects. The NOS of some of these embodiments therefore provides an actual separate module to serve as the notification processor for some or all of the NIB objects.
When some or all of the NIB objects have notification functions in some embodiments, the notification registry for such NIB objects are typically kept with the objects themselves. Accordingly, for some of these embodiments, the notification registry 2615 is a conceptual illustration of the amalgamation of the different sets of registered requestors maintained by the NIB objects. Alternatively, when some or all of the NIB objects do not have notification functions and notification services are needed for these objects, some embodiments use a separate notification registry 2615 for the notification processing module 2610 to use to keep track of the notification requests for such objects.
The notification process serves as only one manner for accessing the data in the NIB. Other mechanisms are needed in some embodiments for accessing the NIB. For instance, the secondary storage structures (e.g., the PTD 2640 and the DHT instance 2650) also need to be able to import data from and export data to the NIB. For these operations, the NOS 2600 uses the transfer modules 2630 to exchange data between the NIB and the secondary storage structure.
In some embodiments, the transfer modules include a NIB import module and a NIB export module. These two modules in some embodiments are configured through the NOS controller 2622, which processes configuration instructions that it receives through the interfaces 2605 from the applications above the NOS. The NOS controller 2622 also performs several other operations. As with the notification processor, some or all of the operations performed by the NOS controller are performed by one or more functions of NIB objects, in some of the embodiments that implement one or more of the NOS 2600 operations through the NIB object functions. Accordingly, for these embodiments, the NOS controller 2622 is a conceptual amalgamation of several NOS operations, some of which are performed by NIB object functions.
Other than configuration requests, the NOS controller 2622 of some embodiments handles some of the other types of requests directed at the NOS instance 2600. Examples of such other requests include queries to read certain NIB attributes, queries to write to certain NIB attributes, requests to create or destroy NIB entities, requests to import or export entities on demand, and requests to synchronize NIB entities with switching elements or other NOS instances.
In some embodiments, the NOS controller stores requests to change the NIB on the NIB request list 2660. Like the notification registry, the NIB request list in some embodiments is a conceptual representation of a set of distributed requests that are stored in a distributed manner with the objects in the NIB. Alternatively, for embodiments in which some or all of the NIB objects do not maintain their modification requests locally, the request list is a separate list maintained by the NOS 2600. The system of some of these embodiments that maintains the request list as a separate list, stores this list in the NIB in order to allow for its replication across the different controller instances through the PTD storage layer. As further described below, this replication allows the distributed controller instances to process in a uniform manner a request that is received from an application operating on one of the controller instances.
Synchronization requests are used to maintain consistency in NIB data in some embodiments that employ multiple NIB instances in a distributed control system. For instance, in some embodiments, the NIB of some embodiments provides a mechanism to request and release exclusive access to the NIB data structure of the local instance. As such, an application running on top of the NOS instance(s) is only assured that no other thread is updating the NIB within the same controller instance; the application therefore needs to implement mechanisms external to the NIB to coordinate an effort with other controller instances to control access to the NIB. In some embodiments, this coordination is static and requires control logic involvement during failure conditions.
Also, in some embodiments, all NIB operations are asynchronous, meaning that updating a network entity only guarantees that the update will eventually be pushed to the corresponding switching element and/or other NOS instances. While this has the potential to simplify the application logic and make multiple modifications more efficient, often it is useful to know when an update has successfully completed. For instance, to minimize disruption to network traffic, the application logic of some embodiments requires the updating of forwarding state on multiple switches to happen in a particular order (to minimize, for example, packet drops). For this purpose, the API of some embodiments provides the synchronization request primitive that calls back one or more applications running on top of the NOS once the state has been pushed for an entity. After receiving the callback, the control application of some embodiments will then inspect the content of the NIB and determine whether its state is still as originally intended. Alternatively, in some embodiments, the control application can simply rely on NIB notifications to react to failures in modifications as they would react to any other network state changes.
The NOS controller 2622 is also responsible for pushing the changes in its corresponding NIB to switching elements for which the NOS 2600 is the master. To facilitate writing such data to the switching element, the NOS controller 2622 uses the switch controller 2625. It also uses the switch controller 2625 to read values from a switching element. To access a switching element, the switch controller 2625 uses the switch interface 2655, which, as mentioned above, uses OpenFlow or OVS, or other known sets of APIs in some embodiments.
Like the PTD and DHT storage structures 2145 and 2150 of the control system 2100 of
Also, like structures 2145 and 2150, the PTD 2640 and DHT instance 2650 have corresponding lists of triggers that are respectively maintained in the CM interface 2642 and the DHT instance 2650. The use of these triggers will be further described below. Also, like the PNTD 2155 of the control system 2100, the PNTD 2645 of
The process for applications registering for NIB notifications will next be described in sub-section IV.B. After this discussion, the process for interacting with the DHT and/or PTD upon modification of the NIB will be described in sub-section IV.C. Next, the process for handling NIB change requests from the application will be described in sub-section IV.D.
B. Application Registering for NIB Notification
As shown in
When the process determines (at 2720) that it should not end, the process determines (at 2730) whether the particular NIB data has changed. If not, the process transitions to 2760, which will be further described below. When the process determines (at 2730) that the particular NIB data has changed, the process determines (at 2740) whether any application callbacks were triggered by the NIB data change. Such callbacks would be triggered always in embodiments that call back one or more applications when one or more callback notifications are on the notification lists. For such embodiments, the determination (at 2740) is not needed. Other embodiments, however, allow the callbacks to be set conditionally (e.g., based on the value of the changed record). In these embodiments, the determination (at 2740) entails determining whether the condition for triggering the callback has been met.
When the process determines (at 2740) that it needs to call back one or more applications and notify them of the changes to the NIB records, the process sends (at 2750) the notification of the NIB record change along with the new value for the changed NIB record to each application that it needs to notify (i.e., to each application that is on the notification list and that needs to be notified). From 2750, the process transitions to 2760. The process also transitions to 2760 from 2740 when it determines that no application callbacks were triggered by the NIB record change.
At 2760, the process determines whether any new notification requests need to be registered on the callback notification list. If so, the process transitions to 2710, which was described above. Otherwise, the process transitions to 2770, where it determines whether any request to delete notification requests from the notification list has been received. If not, the process transitions to 2720, which was described above. However, when the process determines (at 2770) that it needs to delete a notification request, it transitions to 2780 to delete the desired notification request from the notification list. From 2780, the process transitions to 2720, which was described above.
C. Secondary Storage Records and Callbacks
As shown in
After 2805, the process determines (at 2810) whether the notification relates to creation of a new object in the NIB. If the notification does not correspond to a new NIB object, the process transitions to 2845, which will be described further below. Otherwise, the process determines (at 2815) whether it needs to direct one or more secondary storages to create one or more records to correspond to the newly created NIB record. When the process determines (at 2815) that it does not need to direct any secondary storages to create any new records, the process ends. Otherwise, the process selects (at 2820) a secondary storage structure and directs (at 2825) this secondary storage structure to create a record that would correspond to the newly created NIB object. In the case of the DHT, the process 2800 directly interfaces with a query manager of the DHT to make this request for a new record. In the case of the PTD, however, this request is routed to the master PTD through the CM(s) and CM interface(s) that serve as the interface between the PTD and the NIB layers.
After 2825, the process, if necessary, registers (at 2830) for a callback from the selected secondary storage structure to the import module of the transfer modules 2630. This callback is triggered in some embodiments whenever the newly created record in the selected secondary storage structure changes. In some embodiments, this callback notifies the import module that a record has changed in the secondary storage structure.
In the case of the PTD 2640, the process 2800 in some embodiments directs the CM interface 2642 of the master PTD to create a trigger for the newly created PTD record and to identify the import module as the module to call back when the newly created PTD record has changed. As mentioned above, the CM processor then receives this request and directs the PTD trigger tracker of the master PTD to create such a trigger record in its PTD trigger list for the newly created PTD record.
In the case of the DHT, the process in some embodiments directs the DHT query manager to register a trigger for the newly created DHT record and to identify the import module of the NIB that originated the change as the module to call back, when the newly created DHT record has changed.
Instead of registering for a callback at 2830 upon creation of a new NIB record, the process 2800 of other embodiments uses other techniques for registering callbacks to the NIB from one or more of the secondary storage structures. For instance, in some embodiments, the NIB import module of a controller instance registers for callbacks from the master PTD when the NIB and the import module are instantiated. In some embodiments, such callbacks are registered with the CM interface of the master PTD, and the CM interface performs these callbacks when the master PTD notifies it that one of its records has changed. Some embodiments use a similar approach to register for callbacks from the DHT, while other embodiments use the process 2800 (or similar process) to register callbacks (e.g., at 2830) for the DHT.
After 2830, the process adds (at 2835) the selected secondary storage structure to the list of modules that it needs to notify when the newly created NIB record has changed. The process then determines (at 2840) whether it has to select another secondary storage structure in which it has to create a new record to correspond to the newly created NIB record. In some embodiments, the process 2800 can at most create a new record in the master PTD and a new record in one DHT instance. In other embodiments, however, the process can create more than these two records in more than two secondary storages of the controller instances of the control system.
When the process determines (at 2840) that it does not need to create a record in any other secondary storage structure, it ends. However, when the process determines (at 2840) that it needs to create a new record in another secondary storage structure, it returns to 2820 to select another secondary storage structure and repeat its operations 2825 to 2840 for this structure.
When the process determines (at 2810) that the NIB change notification that it has received does not correspond to a new NIB object, the process transitions to 2845. At 2845, the process determines whether any secondary storages need to be notified of this NIB change. If not, the process ends. Otherwise, the process selects (at 2850) a secondary storage to notify and then notifies (at 2855) the selected secondary storage. In some embodiments, the notification of the selected secondary storage always or at times entails generating a write command to the secondary storage to direct it to modify a value of its record that corresponds to the NIB record which has been modified (i.e., which was the NIB record identified at 2805).
After 2855, the process determines (at 2860) whether it needs to notify any other secondary storage of the NIB change. If so, the process returns to 2850 to select another secondary storage structure to notify. Otherwise, the process ends.
As shown in
In the second stage 3202, the NIB 3210 adds a new NIB entity, which is illustrated by an arrow pointing to a new NIB node 3260. The value of this new NIB record 3260 is “X” in this example. Next, in the third stage 3203, the export module 3230 in the set of transfer modules receives notification of the newly created entity 3260 in the NIB. Upon receipt of this notification, the export module 3230 creates a new record 3270 in the secondary storage layer as illustrated by the arrow starting at the export module and ending at the box 3270 in the secondary storage layer 3250. The third stage 3203 shows that the value “X” is stored in the newly created record 3270 in the secondary storage layer 3250. In the third stage, the export module 3230 also directs the secondary storage layer to create a trigger in the secondary storage layer (e.g., to create a DHT trigger in the DHT, or to create a PTD trigger in the CM) and register the identity of the import module 3240 as a module to call back in case the new record 3270 changes subsequently.
The fourth stage 3204 illustrates the updating of the record 3270 in the secondary storage at a subsequent point in time. This updating results in a new value “S” being stored in this record 3270. This updating results in the identification of the notification trigger stored at the direction of the export module 3230, and the subsequent identification of the import module 3240 as a module to notify of the NIB change.
The fifth stage 3205 illustrates that after the identification of the import module 3240, this module 3240 receives notification of the change to the record 3270 that occurred in the fourth stage 3204. With the double arrow connection between the import module 3240 and the record 3270, the fifth stage 3205 also shows that the import module queries the secondary storage structure to receive the new value “S” once it determines that it needs to import this new value into the NIB. In the sixth, and final stage 3206, the import module 3240 imports the new value “S” into the NIB record 3260 to reflect the change that occurred to the corresponding record 3270 in the secondary storage layer in the fourth stage 3204. This process shows how the transfer modules maintain consistency between the NIB and the secondary storage layer through use of export and import modules.
D. Application Requesting NIB Changes
The discussion above describes how the applications and export modules register notifications with the NIB and how the import modules import data into the NIB, in some embodiments of the invention. Another NIB layer interaction involves the applications requesting through the application interface 2605 changes in the NIB. Some embodiments allow all applications to make such requests, but only make changes based on some of the application requests.
As further described below, in some embodiments, the system replicates the PTDs and NIBs across multiple controller instances. In some embodiments, the system takes advantage of this replication to distribute a request by one application to modify the NIB. For instance, in some embodiments, a request to modify the NIB from one controller instance's application is stored in a NIB request list 2660 within the NIB 2620. As this list is part of the NIB, additions to it are propagated to the NIBs of the other controller instances through the NIB/PTD replication process, which will be further described below.
Each controller instance then subsequently retrieves the request from its NIB's request list and determines whether it should process the NIB change. The controller instance that should process the received NIB modification request and change the NIB then determines whether this change should be made, and if it determines that it should, it then modifies its NIB based on the request. If this controller instance determines that it should not grant this request, it rejects the request. In some embodiments, the NOS controller 2622 of the NOS 2600 is the module of the controller instance that decides whether it should process the request, and if so, whether it should make the desired change based on the request or deny this request. As mentioned above, the NOS controller 2622 in some embodiments is a conceptual amalgamation of several different functions in several different NIB objects that process NIB modification requests from the application layer.
In some embodiments, the NOS controller 2622, which makes or denies the requested NIB modification, records a response to the specified request in a response list in the NIB. This response list is part of the request list in some embodiments. Alternatively, this response list is a conceptual amalgamation of various response fields or attributes in various NIB objects. This response list is propagated to the other NIBs through the NIB/PTD replication process. Each NOS controller 2622 of each controller instance examines the response list to determine whether there are any responses that it needs to process. Accordingly, the NOS controller 2622 of the controller instance that originated the NIB request modification removes the response added to the list by the controller that made or denied the NIB modification. Based on this response, this NOS controller then supplies an acknowledgment or a denial of the change to the application that originated the request.
For some embodiments of the invention,
Process 3310 is a process that each controller instance subsequently performs when it receives notification of the change to the request list. In some embodiments, this process previously registered to be notified of NIB modifications (e.g., with the notification processor 2610) whenever the request list is modified. As shown in
When the process 3310 determines (at 3330) that its controller instance is not the master of the NIB portion being changed, it ends. Otherwise, the process calls (at 3335) the NIB updater process 3315, and then ends.
Process 3315 is the process that is performed by the controller instance that should process the received NIB modification request (i.e., by the controller instance that is the master of the NIB portion being changed). As shown in
When the process determines (at 3340) the requested NIB modification should not be made, it transitions to 3355, which will be described further below. Otherwise, when the process determines (at 3340) that it should perform the requested NIB modification, it makes (at 3350) this modification in the NIB and then transitions to 3355.
At 3355, the process removes the modification request from the request list. After 3355, the process transitions to 3360, at which point it updates the response list in the NIB to reflect an acknowledgement that it has made the desired modification. After 3360, the process ends.
The response list is propagated to the other NIBs through the NIB/PTD replication process. The NOS controller of the controller instance that originated the NIB request modification removes the response added to the list by the controller that made or denied the NIB modification. Based on this response, this NOS controller then supplies an acknowledgment or a denial of the change to the application that originated the request.
Some embodiments perform variations of the processes 3305-3315. For instance, in some embodiments, the process 3305 that handles the incoming NIB modification request from an application of its controller instance, initially determines whether the NIB modification needs a master controller to perform the modification. If not, the process 3305 implements this change in some embodiments. Also, while some embodiments propagate the NIB modification request through the PTD storage layer, other embodiments propagate the NIB modifications through the DHT storage layer.
As described above,
V. Secondary Storage
A. DHT
In several embodiments described below, the query manager 3405 receives queries only from other DHT storage structures and from the import and export modules of the controller instance that includes the DHT storage structure 3400. In other embodiments, the query manager 3405 also receives queries from applications running on top of the NOS instances.
The query manager 3405 interacts with the other software modules contained inside of the DHT storage structure 3400 in order to process queries. In some embodiments, the query manager 3405 can handle “put” and “get” queries. When the query manager 3405 receives a “put” query, it adds or changes a data record in the hash table 3430. When the query manager 3405 receives a “get” query, the query manager 3405 retrieves a data record from the hash table 3430 and returns this data record to the querying entity.
The query manager in some embodiments can receive a query with a key value for a record in the hash table. In some of these embodiments, the query in some cases can also include a hash value that corresponds to the hash of the key value, whereas the query in other cases does not include a hash value.
The hash generator 3425 is used by the query manager 3405 to generate a hash value for a received key value. For instance, when query manager receives a query that does not specify a hash value, it sends the query along with the received key value. The hash generator 3425 contains and executes one or more hash functions on the received key value to generate a hash value. The hash generator 3425 sends hash values that it generates to the query manager 3405.
The DHT range list 3415 contains a list of hash value ranges, with different ranges being associated with different DHT instances of different controller instances. The CM (e.g., CM 2635) periodically updates the DHT range list 3415, as described above and further described below. The query manager 3405 uses the DHT range list to identify the DHT instance that contains a DHT record associated with a hash value that it receives from the hash generator 3425 or receives with the query. For a particular hash value, the DHT range list 3415 might specify the current DHT instance (i.e., the DHT instance whose query manager is currently processing the DHT query) as the location of the corresponding DHT record, or alternatively, it can specify another DHT instance that runs in another controller instance as the location of the desired DHT record.
When the DHT range list 3415 shows that the hash value falls within a range of another DHT instance, the query manger 3405 uses its remote DHT module interface to pass the query to the remote DHT that contains the desired DHT record. In some embodiments, the query manager 3405 also sends the hash value the local hash generator 3425 so that the remote hash generator does not need to re-compute this hash value. After processing the query, the remote DHT data structure will send the requested data record to the requesting query manager 3405 through its remote DHT interface module 3420. Thus, the remote DHT interface module 3420 serves two functions. First, the remote DHT interface module 3420 sends queries, data records, and hash values to remote DHT storage structures. Second, the remote DHT interface module 3420 receives queries, data records, and hash values from remote DHT storage structures. The remote DHT interface module 3420 enables the query managers of all the DHT storage structures in the network to share the information stored in their local hash tables.
When the DHT range list 3415 shows that a hash value is stored locally, the query manager 3405 will use the hash value to access its local hash table 3430 for the hash record associated with the hash value. The hash table 3430 contains several data records and a hash value for each data record. When this table receives a hash value, it returns the data record associated with the hash value.
The trigger processor 3410 handles trigger notifications when the query manager modifies a record in the local hash table 3430. Whenever the query manager writes a new value in the hash table, the hash table in some embodiments returns a set of identities for a set of modules to notify in the same or different controller instances. The trigger processor receives this set of identities. It then notifies the associated modules of the change to the DHT record. If needed, the modules then query the DHT instance to retrieve the new value for the DHT record.
Other embodiments may implement the triggering process differently. For instance, in conjunction with or instead of triggering based on writes to the hash table, the triggering in some embodiments is performed based on deletes from the hash table. Also, instead of just calling back modules to notify them that a DHT record value has changed, some embodiments send the new value of the DHT record along with the notification to the modules that are called back.
The description of the operation of the DHT storage structure 3400 will now be described in reference to
In this example, the query manager 3610 initially receives from a querying entity a put query 3680 includes a key 3660 and a value 3670. The query manager 3610 then sends the key 3660 to the hash generator 3620, which generates hash 3665 and returns this hash to the query manager 3610. The query manager 3610 then provides the hash 3665 to the DHT range list 3630. The DHT range list 3630 then identifies a range of hash values in which the hash 3665 falls.
Based on the range that the DHT range list 3630 identifies, it identifies a corresponding controller instance whose DHT instance contains the desired DHT record (i.e., the record corresponding to the generated hash value). The DHT range list 3630 returns the identification 3675 of this controller instance to the query manager 3610. In this case, the identified controller instance is the local controller instance.
Hence, the query manager 3610 next performs a put query on its local hash table 3640. With this query, the query manager 3610 sends the hash 3665, and the value 3670 to write in the corresponding DHT record in the hash table 3640. Because the put query 3680 is a put command, the hash table 3640 writes the value 3670 in the hash table. If the accessed DHT record did not exist before this put query, the hash table generates a DHT record based on this query and stores in this record the hash 3665 along with the value 3670.
In this example, the modified DHT record has a set of notification triggers (i.e., a set of identities of modules that need to be notified). Accordingly, after modifying its DHT record, the hash tables 3640 sends the list 3690 of modules that need to be notified of the DHT record modification. The query manager 3610 then sends the key 3660 that identifies the modified record along with the trigger list 3690 to the trigger processor 3650. The trigger processor 3650 processes the triggers in the trigger list 3690 by sending a notification 3695 to all entities that have registered triggers (i.e., all modules on the trigger list 3690) that the DHT record (with the key 3660) has been modified. The three arrows exiting the trigger processor 3650 represent the key 3660 and notification 3695 are being sent to three registered modules in this example. In addition to sending the key and trigger list to the trigger processor, the query manager also sends a confirmation 3685 of the completion of the Put request to the source that sent it the Put query.
The example begins when the query manager 3710 receives a put query 3780 that includes key 3760 and value 3770. The query manager 3710 then sends the key 3760 to the hash generator 3720. The hash generator 3720 generates hash 3765 and sends the hash 3765 to the query manager 3710.
The query manager 3710 then sends the hash 3765 to the DHT range list 3730. As was the case in
Because instance 3706 manages the desired DHT record, the query manager 3710 relays the key 3760, put query 3780, hash 3765, and value 3770 to the query manager 3715 of the instance 3706. The query manager 3715 then sends the value 3770 and the hash 3765 to the hash table 3745, which then writes value 3770 to its record at hash 3765.
In this example, the modified DHT record has a set of notification triggers. Accordingly, after modifying its DHT record, the hash tables 3745 sends to the query manager 3715 the trigger list 3790 of modules that need to be notified of the DHT record modification. The query manager 3715 then sends key 3760 and trigger list 3790 to the trigger processor 3750. The trigger processor 3750 processes the triggers 3790 by sending a notification 3795 to all entities that have registered triggers (i.e., all modules on the trigger list 3790) that the DHT record (with key 3760) has been modified. The three arrows exiting the trigger processor 3750 represent the key 3760 and notification 3795 are being sent to three registered modules in this example.
In addition to sending the key and trigger list to the trigger processor, the query manager of instance B also sends a confirmation 3705 of the completion of the Put request to the query manager 3710 of the instance A. The query manager 3710 then relays this confirmation 3785 to the source that sent it the Put query.
As shown in
The process 3800 then uses the hash value it generated (at 3820) or received (at 3810) with the access request to check (at 3830) the DHT range list. The DHT range list contains a list of hash ranges associated with DHT instances and is locally cached by the query manager 3405. If a hash value is within a DHT range for a DHT instance on the DHT range list, then that DHT instance can process an access request for said hash value.
After referencing the DHT range list (at 3830), the process determines (at 3840) whether the access request can be processed locally. If so, the process executes (at 3850) the access request. In some embodiments, the execution of the access request consists of the process performing a “put” function or a “get” function on the records requested by the access request. After executing the access request 3850, the process receives (at 3860) triggers from the local DHT records on data that the access request operated on, if any. A trigger is list of entities that the query manager must notify if the query manager accesses the record associated with the trigger. In some embodiments, the entities that could have triggers on DHT data are the notification processors 2610, the transfer modules 2630, or the application interface 2605. In some embodiments, the triggers are stored with the local DHT records as shown in
When the process determines (at 3840) that the access request cannot be processed locally, the process sends (at 3880) the access request to the remote DHT node identified (at 3830) on the DHT range list. The process sends (at 3880) the access request to the remote DHT node including any hash values received (at 3810) or generated (at 3820). After sending the access request to a remote DHT node 3880, the process transitions to 3885 to wait for a confirmation from the remote DHT node. Once the process receives (at 3885) confirmation from the remote DHT node, the process transitions to 3890.
At 3890, the process sends a confirmation to the source that sent it the query. When the query is a Put query, the confirmation confirms the completion of the query. However, when the query is a Get query, the confirmation relays the data retrieved from the DHT. Also, in cases that the remote DHT node does not return a confirmation (at 3885) within a timely manner, the process 3800 has an error handling procedure to address the failure to receive the confirmation. Different embodiments employ different error handling procedures. In some embodiments, the error handler has the DHT node re-transmit the query several times to the remote node, and in case of repeated failures, generate an error to the source of the query and/or an error for a system administrator to address the failure. Other embodiments, on the other hand, do not re-transmit the query several times, and instead generate an error to the source of the query and/or an error for a system administrator to address upon failure to receive confirmation.
B. PTD
As described above and as illustrated in
As further illustrated in
Some embodiments define a transactional guard processing (TGP) layer before the PTD in order to allow the PTD to execute conditional sets of database transactions. In some embodiments, this TGP layer is built as part of the CM interface 3925 or the query manager 3930 and it allows the transfer modules 3920 to send conditional transactions to the PTD.
In some embodiments, the controller instances maintain identical data records in the NIBs and PTDs of all controller instances. In other embodiments, only a portion of the NIB data is replicated in the PTD. In some embodiments, the portion of NIB data that is replicated in the PTD is replicated in the NIBs and PTDs of all controller instances.
As shown in
After 4010, the process replicates (at 4020) the change across the PTDs of the PTD layer. In some embodiments, the change is replicated across all PTDs by having the PTD of the instance that received the NIB change notify the other PTDs. However, as described below, the process 4000 of some embodiments employs the master PTD to notify all other slave PTDs to replicate the change in their PTDs.
After the process completes the PTD replication operation 4020, the process propagates (at 4030) the NIB change to all the NIBs of all other controller instances. In some embodiments, this process is performed by each controller instance's transfer modules retrieving the modified PTD record from its local PTD after being locally notified by its PTD storage layer (e.g., by the local CM interface of that instance) of the local PTD change. However, as mentioned above, the process 4000 in some embodiments replicates the NIB change in all the NIBs by having the master PTD notify each instance's transfer module of the PTD layer change, and then supplying each instance's NIB with the modified record. As further described above, the master PTD supplies the modified record with the notification of PTD layer change to each NIB instance in some embodiments, while in other embodiments, the master PTD supplies the modified record to each NIB instance after it notifies the NIB instance and the NIB instance in response queries the master PTD for the modified record. After 4030, the process ends.
After 4110, the process determines (at 4120) whether this instance is the master PTD instance. A slave PTD instance is PTD without the authority to write to that PTD without direction from a master PTD instance, while a master PTD instance is a PTD that has the authority to make updates to its PTD and distributes updates to the PTDs of the slave PTD instances.
When the process 4100 determines that it is the master PTD, it initiates (at 4170) the master update process, and then terminates. The master update process will be described below by reference to
For some embodiments, the wait state 4140 in
As shown in
After 4210, the process directs (at 4220) the slave PTD instances to update their PTDs and the process requests acknowledgment of completion of the PTD update from all slave PTD instances. In some embodiments, the direction to update PTDs is sent from the master PTD instance's CM interface to the CM interfaces of the slave PTD instances, and the master PTD instance's CM interface will receive acknowledgment of the completion of the PTD update from the slave PTD instances' CM interfaces.
After 4220, the process in some embodiments determines (at 4230) whether it has received acknowledgement from all slave instances of completion of the PTD update process. Instead of requiring acknowledgments from all slave instances, the process 4200 of some embodiments only requires (at 4230) acknowledgments from a majority of slave instances.
When the process determines (at 4230) that it has not yet received acknowledgement from a sufficient number of slave instances (e.g., from all slave instances or a majority of slave instances), the process determines (at 4240) whether to call an error handler. If not, the process returns to 4230 to wait for acknowledgements from the slave instances. Otherwise, the process calls (at 4250) the error handler to address the lack of acknowledgement from the slave PTDs. In some embodiments, the error handler flags the unresponsive slave PTDs for a system administrator to examine to determine the reason for their lack of response. In some embodiments, the process 4200 re-transmits the PTD update command a set number of times to each unresponsive slave instance, before calling the error handler to address these unresponsive slave instances. After calling the error handler (at 4250), the process ends.
When the process determines (at 4230) that it has received acknowledgement from a sufficient number of slave instances (e.g., from all slave instances or a majority of slave instances), the process transitions to 4260. At 4260, the process records the PTD update in its master PTD. It then sends (at 4270) a PTD update notification to all NIB import modules (including the import module of the master PTD controller) to update their NIBs based on the received NIB modification and requests acknowledgement of completion of those NIB update from a sufficient number instances. This PTD update notification causes each NIB import module to update its NIB based on the change in the PTD. In some embodiments, this PTD update notification is accompanied with the updated record, while in other embodiments, this notification causes the import module to query the master PTD to retrieve the updated record. In some embodiments, the process also sends the NIB import module of its controller instance a PTD update notification, in order to cause this import module to update its NIB. Alternatively, the process 4200 makes the modifications to its NIB at 4220 instead of at 4270 in some embodiments.
At 4280, the process determines whether it has received acknowledgement from all slave instances of the completion of the NIB update process. If so, the process ends. Otherwise, the process determines (at 4290) whether to call an error handler. If not, the process returns to 4280 to wait for acknowledgements from the slave instances. When the process determines (at 4290) that it should call the error handler (e.g., that sufficient time has passed for it to call an error handler), the process calls (at 4295) the error handler to address the lack of acknowledgement from the slave instances. In some embodiments, the error handler flags the unresponsive slave instances for a system administrator to examine to determine the reason for their lack of response. In some embodiments, the process 4200 re-transmits the NIB update command a set number of times to each unresponsive slave instance, before calling the error handler to address these unresponsive slave instances. Also, in some embodiments, the process 4200 does not request acknowledgments at 4270 or wait for such acknowledgments at 4280. In some of these embodiments, the process 4200 simply ends after sending the PTD update notification at 4270.
As shown in
In the fourth stage 4320, the CM interface 4364 of the master instance 4360 pushes the requested change to the master PTD 4394. In this case the master instance 4360 approved the change and wrote it to the master PTD. However, in other cases, the master could have refused the change and sent an error message back to the slave controller instance 4350.
The fifth stage 4325 shows the CM interface 4364 of the master instance 4360 sending notification 4395 to the CM interfaces of the slave instances 4350 and 4380 of the change that the master has made to the master PTD. In some embodiments, the master PTD sends the updated PTD record with its notification 4395 to the CM interfaces of the slave instances, while in other embodiments, the slave CM interfaces retrieve the updated PTD record from the master after receiving notification of the change from the master.
In the sixth stage 4330, the CM interfaces of the slave instances 4350 and 4380 write an update 4396 to change to their slave PTDs. In the seventh stage 4335, the CM interface 4364 of the master instance 4360 receives acknowledgements 4397 from the slave instances 4350 and 4380 that the slaves have performed the PTD change the master instance pushed to the slave instances during the fifth stage.
In the eighth stage 4340, the CM interface 4364 of the master instance pushes the change made to the PTD by sending a PTD update notification to the NIB import modules inside the transfer modules 4362 of all the controller instances 4250, 4260, 4270, and 4280. In some embodiments, the PTD update notification causes each NIB import module to update its NIB based on the change in the PTD. In some embodiments, this PTD update notification is accompanied with the updated record, while in other embodiments, this notification causes the import module to query the master PTD to retrieve the updated record. Also, in some embodiments, the master PTD does not send a PTD update notification to the NIB import module of the slave controller instance 4350 that detected the NIB change for some or all NIB changes detected by this slave controller instance.
C. NIB Replication Through DHT
As mentioned above, the controller instances replicate data records in the NIBs of all controller instances. In some embodiments, some of this replication is done through the PTD storage layer (e.g., by using the processes described in Section V.B. above, or similar processes) while the rest of this replication is done through the DHT storage layer.
After 4410, the DHT instance then modifies (at 4420) according to the update notification its record that corresponds to the updated NIB record. Next, at 4430, the DHT instance retrieves for the updated DHT record a list of all modules to call back in response to the updating of the DHT record. As mentioned above, one such list is stored with each DHT record in some embodiments. Also, to effectuate NIB replication through the DHT storage layer, this list includes the identity of the import modules of all NIB instances in some embodiments. Accordingly, at 4430, the process 4400 retrieves the list of all NIB import modules and sends to each of these modules a notification of the DHT record update. In response to this update notification, each of the other NIB instances (i.e., the NIB instances other than the one that made the original modification that resulted in the start of the process 4400) update their records to reflect this modification. After 4430, the process 4400 ends.
VI. Electronic System
Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
In this specification, the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
The bus 4505 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 4500. For instance, the bus 4505 communicatively connects the processing unit(s) 4510 with the read-only memory 4530, the system memory 4525, and the permanent storage device 4535.
From these various memory units, the processing unit(s) 4510 retrieve instructions to execute and data to process in order to execute the processes of the invention. The processing unit(s) may be a single processor or a multi-core processor in different embodiments.
The read-only-memory (ROM) 4530 stores static data and instructions that are needed by the processing unit(s) 4510 and other modules of the electronic system. The permanent storage device 4535, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 4500 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 4535.
Other embodiments use a removable storage device (such as a floppy disk, flash drive, etc.) as the permanent storage device. Like the permanent storage device 4535, the system memory 4525 is a read-and-write memory device. However, unlike storage device 4535, the system memory is a volatile read-and-write memory, such a random access memory. The system memory stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 4525, the permanent storage device 4535, and/or the read-only memory 4530. 2655From these various memory units, the processing unit(s) 4510 retrieve instructions to execute and data to process in order to execute the processes of some embodiments.
The bus 4505 also connects to the input and output devices 4540 and 4545. The input devices enable the user to communicate information and select commands to the electronic system. The input devices 4540 include alphanumeric keyboards and pointing devices (also called “cursor control devices”). The output devices 4545 display images generated by the electronic system. The output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some embodiments include devices such as a touchscreen that function as both input and output devices.
Finally, as shown in
Some embodiments include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions that are stored on the circuit itself.
As used in this specification, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification, the terms “computer readable medium,” “computer readable media,” and “machine readable medium” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. In addition, a number of the figures (including
Also, several embodiments were described above in which a user provide logical datapath sets in terms of logical control plane data. In other embodiments, however, a user may provide logical datapath sets in terms of logical forwarding plane data. In addition, several embodiments were described above in which a controller instance provide physical control plane data to a switching element in order to manage the switching element. In other embodiments, however, the controller instance may provide the switching elements with physical forwarding plane data. In such embodiments, the NIB would store physical forwarding plane data and the virtualization application would generate such data.
Furthermore, in several examples above, a user specifies one or more logic switches. In some embodiments, the user can provide physical switch configurations along with such logic switch configurations. Also, even though controller instances are described that in some embodiments are individually formed by several application layers that execute on one computing device, one of ordinary skill will realize that such instances are formed by dedicated computing devices or other machines in some embodiments that perform one or more layers of their operations. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details.
This application is a continuation application of U.S. patent application Ser. No. 13/177,529, filed on Jul. 6, 2011, now issued as U.S. Pat. No. 8,743,889. U.S. patent application Ser. No. 13/177,529, now issued as U.S. Pat. No. 8,743,889 claims the benefit of U.S. Provisional Patent Application 61/361,912, filed on Jul. 6, 2010; U.S. Provisional Patent Application 61/361,913, filed on Jul. 6, 2010; U.S. Provisional Patent Application 61/429,753, filed on Jan. 4, 2011; U.S. Provisional Patent Application 61/429,754, filed on Jan. 4, 2011; U.S. Provisional Patent Application 61/466,453, filed on Mar. 22, 2011; U.S. Provisional Patent Application 61/482,205, filed on May 3, 2011; U.S. Provisional Patent Application 61/482,615, filed on May 4, 2011; U.S. Provisional Patent Application 61/482,616, filed on May 4, 2011; U.S. Provisional Patent Application 61/501,743, filed on Jun. 27, 2011; and U.S. Provisional Patent Application 61/501,785, filed on Jun. 28, 2011. This application is a continuation-in-part application of U.S. patent application Ser. No. 13/177,538, filed on Jul. 6, 2011, now issued as U.S. Pat. No. 8,830,823. This application is also a continuation-in-part application of U.S. application Ser. No. 13/177,536, filed on Jul. 6, 2011, now issued as U.S. Pat. No. 8,959,215. U.S. patent application Ser. No. and 13/177,536, now issued as U.S. Pat. No. 8,959,215, and 13/177,538, now issued as U.S. Pat. No. 8,830,823, claim the benefit of U.S. Provisional Patent Application 61/361,912, filed on Jul. 6, 2010; U.S. Provisional Patent Application 61/361,913, filed on Jul. 6, 2010; U.S. Provisional Patent Application 61/429,753, filed on Jan. 4, 2011; U.S. Provisional Patent Application 61/429,754, filed on Jan. 4, 2011; U.S. Provisional Patent Application 61/466,453, filed on Mar. 22, 2011; U.S. Provisional Patent Application 61/482,205, filed on May 3, 2011; U.S. Provisional Patent Application 61/482,615, filed on May 4, 2011; U.S. Provisional Patent Application 61/482,616, filed on May 4, 2011; U.S. Provisional Patent Application 61/501,743, filed on Jun. 27, 2011; and U.S. Provisional Patent Application 61/501,785, filed on Jun. 28, 2011. This application claims the benefit of U.S. Provisional Patent Application 61/505,100, filed on Jul. 6, 2011; U.S. Provisional Patent Application 61/505,103, filed on Jul. 6, 2011; and U.S. Provisional Patent Application 61/505,102, filed on Jul. 6, 2011. U.S. patent application Ser. Nos. 13/177,536, now issued as U.S. Pat. No. 8,959,215, and 13/177,538, now issued as U.S. Pat. No. 8,830,823, and U.S. Provisional Patent Applications 61/361,912, 61/361,913, 61/429,753, 61/429,754, 61/466,453, 61/482,205, 61/482,615, 61/482,616, 61/501,743, 61/501,785, and 61/505,102 are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4961139 | Hong et al. | Oct 1990 | A |
| 5049873 | Robins et al. | Sep 1991 | A |
| 5265092 | Soloway et al. | Nov 1993 | A |
| 5504921 | Dev et al. | Apr 1996 | A |
| 5550816 | Hardwick et al. | Aug 1996 | A |
| 5729685 | Chatwani et al. | Mar 1998 | A |
| 5751967 | Raab et al. | May 1998 | A |
| 5796936 | Watabe et al. | Aug 1998 | A |
| 5832222 | Dziadosz et al. | Nov 1998 | A |
| 5926463 | Ahearn et al. | Jul 1999 | A |
| 6006275 | Picazo, Jr. et al. | Dec 1999 | A |
| 6055243 | Vincent et al. | Apr 2000 | A |
| 6088694 | Burns et al. | Jul 2000 | A |
| 6104699 | Holender et al. | Aug 2000 | A |
| 6104700 | Haddock et al. | Aug 2000 | A |
| 6219699 | McCloghrie et al. | Apr 2001 | B1 |
| 6324275 | Yagel et al. | Nov 2001 | B1 |
| 6363453 | Esposito et al. | Mar 2002 | B1 |
| 6366657 | Yagel et al. | Apr 2002 | B1 |
| 6512745 | Abe et al. | Jan 2003 | B1 |
| 6539432 | Taguchi et al. | Mar 2003 | B1 |
| 6680934 | Cain | Jan 2004 | B1 |
| 6697338 | Breitbart et al. | Feb 2004 | B1 |
| 6735602 | Childress et al. | May 2004 | B2 |
| 6785843 | McRae et al. | Aug 2004 | B1 |
| 6894983 | Lederman et al. | May 2005 | B1 |
| 6912221 | Zadikian et al. | Jun 2005 | B1 |
| 6941487 | Balakrishnan et al. | Sep 2005 | B1 |
| 6963585 | Le Pennec et al. | Nov 2005 | B1 |
| 7042912 | Ashwood Smith et al. | May 2006 | B2 |
| 7046630 | Abe et al. | May 2006 | B2 |
| 7120819 | Gürer et al. | Oct 2006 | B1 |
| 7126923 | Yang et al. | Oct 2006 | B1 |
| 7158972 | Marsland | Jan 2007 | B2 |
| 7197561 | Lovy et al. | Mar 2007 | B1 |
| 7209439 | Rawlins et al. | Apr 2007 | B2 |
| 7263290 | Fortin et al. | Aug 2007 | B2 |
| 7266556 | Coates | Sep 2007 | B1 |
| 7283473 | Arndt et al. | Oct 2007 | B2 |
| 7286490 | Saleh et al. | Oct 2007 | B2 |
| 7342916 | Das et al. | Mar 2008 | B2 |
| 7343410 | Mercier et al. | Mar 2008 | B2 |
| 7359971 | Jorgensen | Apr 2008 | B2 |
| 7450598 | Chen et al. | Nov 2008 | B2 |
| 7460482 | Pike | Dec 2008 | B2 |
| 7463579 | Lapuh et al. | Dec 2008 | B2 |
| 7478173 | Delco | Jan 2009 | B1 |
| 7483370 | Dayal et al. | Jan 2009 | B1 |
| 7555002 | Arndt et al. | Jun 2009 | B2 |
| 7587492 | Dyck et al. | Sep 2009 | B2 |
| 7590669 | Yip et al. | Sep 2009 | B2 |
| 7606260 | Oguchi et al. | Oct 2009 | B2 |
| 7643488 | Khanna et al. | Jan 2010 | B2 |
| 7649851 | Takashige et al. | Jan 2010 | B2 |
| 7710874 | Balakrishnan et al. | May 2010 | B2 |
| 7764599 | Doi et al. | Jul 2010 | B2 |
| 7778996 | Burger | Aug 2010 | B2 |
| 7783856 | Hashimoto et al. | Aug 2010 | B2 |
| 7792987 | Vohra et al. | Sep 2010 | B1 |
| 7802251 | Kitamura | Sep 2010 | B2 |
| 7818452 | Matthews et al. | Oct 2010 | B2 |
| 7826482 | Minei et al. | Nov 2010 | B1 |
| 7839847 | Nadeau et al. | Nov 2010 | B2 |
| 7856549 | Wheeler | Dec 2010 | B2 |
| 7885276 | Lin | Feb 2011 | B1 |
| 7912955 | Machiraju et al. | Mar 2011 | B1 |
| 7925661 | Broussard et al. | Apr 2011 | B2 |
| 7936770 | Frattura et al. | May 2011 | B1 |
| 7937438 | Miller et al. | May 2011 | B1 |
| 7945658 | Nucci et al. | May 2011 | B1 |
| 7948986 | Ghosh et al. | May 2011 | B1 |
| 7953865 | Miller et al. | May 2011 | B1 |
| 7970917 | Nakano et al. | Jun 2011 | B2 |
| 7991859 | Miller et al. | Aug 2011 | B1 |
| 7995483 | Bayar et al. | Aug 2011 | B1 |
| 8027354 | Portolani et al. | Sep 2011 | B1 |
| 8031633 | Bueno et al. | Oct 2011 | B2 |
| 8032899 | Archer et al. | Oct 2011 | B2 |
| 8046456 | Miller et al. | Oct 2011 | B1 |
| 8054832 | Shukla et al. | Nov 2011 | B1 |
| 8055789 | Richardson et al. | Nov 2011 | B2 |
| 8060875 | Lambeth | Nov 2011 | B1 |
| 8089871 | Iloglu et al. | Jan 2012 | B2 |
| 8130648 | Kwan et al. | Mar 2012 | B2 |
| 8131852 | Miller et al. | Mar 2012 | B1 |
| 8144630 | Orr | Mar 2012 | B1 |
| 8149737 | Metke et al. | Apr 2012 | B2 |
| 8155028 | Abu-Hamdeh et al. | Apr 2012 | B2 |
| 8161152 | Ogielski et al. | Apr 2012 | B2 |
| 8166201 | Richardson et al. | Apr 2012 | B2 |
| 8199750 | Schultz et al. | Jun 2012 | B1 |
| 8223668 | Allan et al. | Jul 2012 | B2 |
| 8224931 | Brandwine et al. | Jul 2012 | B1 |
| 8224971 | Miller et al. | Jul 2012 | B1 |
| 8265075 | Pandey | Sep 2012 | B2 |
| 8312129 | Miller et al. | Nov 2012 | B1 |
| 8339959 | Moisand et al. | Dec 2012 | B1 |
| 8339994 | Gnanasekaran et al. | Dec 2012 | B2 |
| 8351418 | Zhao et al. | Jan 2013 | B2 |
| 8413216 | Hughes et al. | Apr 2013 | B2 |
| 8456984 | Ranganathan et al. | Jun 2013 | B2 |
| 8504718 | Wang et al. | Aug 2013 | B2 |
| 8612627 | Brandwine | Dec 2013 | B1 |
| 8644188 | Brandwine et al. | Feb 2014 | B1 |
| 8717895 | Koponen et al. | May 2014 | B2 |
| 8718070 | Koponen et al. | May 2014 | B2 |
| 8743888 | Casado et al. | Jun 2014 | B2 |
| 8743889 | Koponen et al. | Jun 2014 | B2 |
| 8750119 | Lambeth et al. | Jun 2014 | B2 |
| 8750164 | Casado et al. | Jun 2014 | B2 |
| 8761036 | Fulton et al. | Jun 2014 | B2 |
| 8775594 | Koponen et al. | Jul 2014 | B2 |
| 20010043614 | Viswanadham et al. | Nov 2001 | A1 |
| 20020034189 | Haddock et al. | Mar 2002 | A1 |
| 20020093952 | Gonda | Jul 2002 | A1 |
| 20020161867 | Cochran et al. | Oct 2002 | A1 |
| 20020194369 | Rawlins et al. | Dec 2002 | A1 |
| 20030009552 | Benfield et al. | Jan 2003 | A1 |
| 20030058850 | Rangarajan et al. | Mar 2003 | A1 |
| 20030069972 | Yoshimura et al. | Apr 2003 | A1 |
| 20030204768 | Fee | Oct 2003 | A1 |
| 20040047286 | Larsen et al. | Mar 2004 | A1 |
| 20040054680 | Kelley et al. | Mar 2004 | A1 |
| 20040054793 | Coleman | Mar 2004 | A1 |
| 20040073659 | Rajsic et al. | Apr 2004 | A1 |
| 20040098505 | Clemmensen | May 2004 | A1 |
| 20040210889 | Childress et al. | Oct 2004 | A1 |
| 20040267866 | Carollo et al. | Dec 2004 | A1 |
| 20040267897 | Hill et al. | Dec 2004 | A1 |
| 20050018669 | Arndt et al. | Jan 2005 | A1 |
| 20050021683 | Newton et al. | Jan 2005 | A1 |
| 20050027881 | Figueira et al. | Feb 2005 | A1 |
| 20050050377 | Chan et al. | Mar 2005 | A1 |
| 20050083953 | May | Apr 2005 | A1 |
| 20050120160 | Plouffe et al. | Jun 2005 | A1 |
| 20050132044 | Guingo et al. | Jun 2005 | A1 |
| 20050201398 | Naik et al. | Sep 2005 | A1 |
| 20050232230 | Nagami et al. | Oct 2005 | A1 |
| 20060026225 | Canali et al. | Feb 2006 | A1 |
| 20060028999 | Iakobashvilli et al. | Feb 2006 | A1 |
| 20060037075 | Frattura et al. | Feb 2006 | A1 |
| 20060092976 | Lakshman et al. | May 2006 | A1 |
| 20060174087 | Hashimoto et al. | Aug 2006 | A1 |
| 20060178898 | Habibi | Aug 2006 | A1 |
| 20060184653 | van Riel | Aug 2006 | A1 |
| 20060184937 | Abels et al. | Aug 2006 | A1 |
| 20060187908 | Shimozono et al. | Aug 2006 | A1 |
| 20060190243 | Barkai et al. | Aug 2006 | A1 |
| 20060193266 | Siddha et al. | Aug 2006 | A1 |
| 20060221961 | Basso et al. | Oct 2006 | A1 |
| 20060248179 | Short et al. | Nov 2006 | A1 |
| 20060282895 | Rentzis et al. | Dec 2006 | A1 |
| 20070028239 | Dyck et al. | Feb 2007 | A1 |
| 20070043860 | Pabari | Feb 2007 | A1 |
| 20070050763 | Kagan et al. | Mar 2007 | A1 |
| 20070055789 | Claise et al. | Mar 2007 | A1 |
| 20070156919 | Potti et al. | Jul 2007 | A1 |
| 20070174429 | Mazzaferri et al. | Jul 2007 | A1 |
| 20070220358 | Goodill et al. | Sep 2007 | A1 |
| 20070234302 | Suzuki et al. | Oct 2007 | A1 |
| 20070239987 | Hoole et al. | Oct 2007 | A1 |
| 20070240160 | Paterson-Jones et al. | Oct 2007 | A1 |
| 20070245082 | Margolus et al. | Oct 2007 | A1 |
| 20070250608 | Watt | Oct 2007 | A1 |
| 20070260721 | Bose et al. | Nov 2007 | A1 |
| 20070266433 | Moore | Nov 2007 | A1 |
| 20070286185 | Eriksson et al. | Dec 2007 | A1 |
| 20070297428 | Bose et al. | Dec 2007 | A1 |
| 20080002579 | Lindholm et al. | Jan 2008 | A1 |
| 20080002683 | Droux et al. | Jan 2008 | A1 |
| 20080005334 | Utard et al. | Jan 2008 | A1 |
| 20080034249 | Husain et al. | Feb 2008 | A1 |
| 20080040467 | Mendiratta et al. | Feb 2008 | A1 |
| 20080049614 | Briscoe et al. | Feb 2008 | A1 |
| 20080049621 | McGuire et al. | Feb 2008 | A1 |
| 20080052206 | Edwards et al. | Feb 2008 | A1 |
| 20080059556 | Greenspan et al. | Mar 2008 | A1 |
| 20080071900 | Hecker et al. | Mar 2008 | A1 |
| 20080163207 | Reumann et al. | Jul 2008 | A1 |
| 20080189769 | Casado et al. | Aug 2008 | A1 |
| 20080196100 | Madhavan et al. | Aug 2008 | A1 |
| 20080212963 | Fortin et al. | Sep 2008 | A1 |
| 20080225780 | McCormick et al. | Sep 2008 | A1 |
| 20080225853 | Melman et al. | Sep 2008 | A1 |
| 20080240122 | Richardson et al. | Oct 2008 | A1 |
| 20080291910 | Tadimeti et al. | Nov 2008 | A1 |
| 20080301303 | Matsuoka | Dec 2008 | A1 |
| 20090031041 | Clemmensen | Jan 2009 | A1 |
| 20090043823 | Iftode et al. | Feb 2009 | A1 |
| 20090049241 | Ohno et al. | Feb 2009 | A1 |
| 20090083445 | Ganga | Mar 2009 | A1 |
| 20090089625 | Kannappan et al. | Apr 2009 | A1 |
| 20090097495 | Palacharla et al. | Apr 2009 | A1 |
| 20090113031 | Ruan et al. | Apr 2009 | A1 |
| 20090122710 | Bar-Tor et al. | May 2009 | A1 |
| 20090138577 | Casado et al. | May 2009 | A1 |
| 20090144220 | Feng et al. | Jun 2009 | A1 |
| 20090150527 | Tripathi et al. | Jun 2009 | A1 |
| 20090161547 | Riddle et al. | Jun 2009 | A1 |
| 20090222924 | Droz et al. | Sep 2009 | A1 |
| 20090249473 | Cohn | Oct 2009 | A1 |
| 20090276661 | Deguchi et al. | Nov 2009 | A1 |
| 20090279536 | Unbehagen et al. | Nov 2009 | A1 |
| 20090292858 | Lambeth et al. | Nov 2009 | A1 |
| 20090303880 | Maltz et al. | Dec 2009 | A1 |
| 20100046531 | Louati et al. | Feb 2010 | A1 |
| 20100061231 | Harmatos et al. | Mar 2010 | A1 |
| 20100082799 | DeHaan et al. | Apr 2010 | A1 |
| 20100115101 | Lain et al. | May 2010 | A1 |
| 20100131636 | Suri et al. | May 2010 | A1 |
| 20100138830 | Astete et al. | Jun 2010 | A1 |
| 20100153554 | Anschutz et al. | Jun 2010 | A1 |
| 20100165877 | Shukla et al. | Jul 2010 | A1 |
| 20100169467 | Shukla et al. | Jul 2010 | A1 |
| 20100191612 | Raleigh | Jul 2010 | A1 |
| 20100191846 | Raleigh | Jul 2010 | A1 |
| 20100192207 | Raleigh | Jul 2010 | A1 |
| 20100192225 | Ma et al. | Jul 2010 | A1 |
| 20100205479 | Akutsu et al. | Aug 2010 | A1 |
| 20100214949 | Smith et al. | Aug 2010 | A1 |
| 20100257263 | Casado et al. | Oct 2010 | A1 |
| 20100275199 | Smith et al. | Oct 2010 | A1 |
| 20100290485 | Martini et al. | Nov 2010 | A1 |
| 20110004913 | Nagarajan et al. | Jan 2011 | A1 |
| 20110010578 | Anúndez Dominguez et al. | Jan 2011 | A1 |
| 20110016215 | Wang | Jan 2011 | A1 |
| 20110026521 | Gamage et al. | Feb 2011 | A1 |
| 20110032830 | Merwe et al. | Feb 2011 | A1 |
| 20110075664 | Lambeth et al. | Mar 2011 | A1 |
| 20110075674 | Li et al. | Mar 2011 | A1 |
| 20110085557 | Gnanasekaram et al. | Apr 2011 | A1 |
| 20110085559 | Chung et al. | Apr 2011 | A1 |
| 20110119748 | Edwards et al. | May 2011 | A1 |
| 20110134931 | Merwe et al. | Jun 2011 | A1 |
| 20110142053 | Van Der Merwe et al. | Jun 2011 | A1 |
| 20110225167 | Bhattacharjee et al. | Sep 2011 | A1 |
| 20110261825 | Ichino | Oct 2011 | A1 |
| 20110271007 | Wang et al. | Nov 2011 | A1 |
| 20110310899 | Alkhatib et al. | Dec 2011 | A1 |
| 20110318011 | Brassil | Dec 2011 | A1 |
| 20120014386 | Xiong et al. | Jan 2012 | A1 |
| 20120120964 | Koponen et al. | May 2012 | A1 |
| 20120147898 | Koponen et al. | Jun 2012 | A1 |
| 20120151550 | Zhang | Jun 2012 | A1 |
| 20130058208 | Pfaff et al. | Mar 2013 | A1 |
| 20130058215 | Koponen et al. | Mar 2013 | A1 |
| 20130058225 | Casado et al. | Mar 2013 | A1 |
| 20130058226 | Casado et al. | Mar 2013 | A1 |
| 20130058228 | Koponen et al. | Mar 2013 | A1 |
| 20130058229 | Casado et al. | Mar 2013 | A1 |
| 20130058250 | Casado et al. | Mar 2013 | A1 |
| 20130058251 | Koponen et al. | Mar 2013 | A1 |
| 20130058252 | Casado et al. | Mar 2013 | A1 |
| 20130058255 | Casado et al. | Mar 2013 | A1 |
| 20130058331 | Thakkar et al. | Mar 2013 | A1 |
| 20130058334 | Koponen et al. | Mar 2013 | A1 |
| 20130058335 | Koponen et al. | Mar 2013 | A1 |
| 20130058339 | Casado et al. | Mar 2013 | A1 |
| 20130058340 | Lambeth et al. | Mar 2013 | A1 |
| 20130058341 | Fulton et al. | Mar 2013 | A1 |
| 20130058342 | Casado et al. | Mar 2013 | A1 |
| 20130058343 | Casado et al. | Mar 2013 | A1 |
| 20130058344 | Casado et al. | Mar 2013 | A1 |
| 20130058348 | Koponen et al. | Mar 2013 | A1 |
| 20130058350 | Fulton | Mar 2013 | A1 |
| 20130058351 | Casado et al. | Mar 2013 | A1 |
| 20130058353 | Koponen et al. | Mar 2013 | A1 |
| 20130058354 | Casado et al. | Mar 2013 | A1 |
| 20130058356 | Koponen et al. | Mar 2013 | A1 |
| 20130058357 | Koponen et al. | Mar 2013 | A1 |
| 20130058358 | Fulton et al. | Mar 2013 | A1 |
| 20130060736 | Casado et al. | Mar 2013 | A1 |
| 20130060737 | Koponen et al. | Mar 2013 | A1 |
| 20130060738 | Koponen et al. | Mar 2013 | A1 |
| 20130060817 | Koponen et al. | Mar 2013 | A1 |
| 20130060819 | Lambeth et al. | Mar 2013 | A1 |
| 20130060922 | Koponen et al. | Mar 2013 | A1 |
| 20130060929 | Koponen et al. | Mar 2013 | A1 |
| 20130060940 | Koponen et al. | Mar 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 0737921 | Oct 1996 | EP |
| 1443423 | Aug 2004 | EP |
| 1653688 | May 2006 | EP |
| 2002-141905 | May 2002 | JP |
| 2003-124976 | Apr 2003 | JP |
| 2003-318949 | Nov 2003 | JP |
| WO 9506989 | Mar 1995 | WO |
| WO 2005112390 | Nov 2005 | WO |
| WO 2008095010 | Aug 2008 | WO |
| WO 2009042919 | Apr 2009 | WO |
| WO 2010115060 | Oct 2010 | WO |
| Entry |
|---|
| Karger, David, et al., “Consistent Hashing and Random Trees: Distributed Caching Protocols for Relieving Hot Spots on the World Wide Web,” In Proc. of the 29th Symposium on Theory of Computing, May 1997, 10 pages. |
| Phaal, Peter, et al., “sFlow Version 5,” Jul. 2004, 46 pages, available at http://www.sflow.org/sflow—version—5.txt. |
| Shenker, Scott, et al., “The Future of Networking, and the Past of Protocols,” Dec. 2, 2011, pp. 1-30, USA. |
| Updated portions of prosecution history of U.S. Appl. No. 12/753,044, Feb. 19, 2013, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,529, Feb. 13, 2013, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,530, Mar. 1, 2013, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,531, Feb. 14, 2013, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,532, Mar. 15, 2013, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,533, Mar. 5, 2013, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,534, Apr. 9, 2013, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,535, Jan. 17, 2013, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,536, May 15, 2012, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,537, Dec. 19, 2012, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,538, Nov. 28, 2012, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,539, Mar. 6, 2013, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,540, Mar. 15, 2013, Lambeth, W. Andrew, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,543, Apr. 22, 2013, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,545, Feb. 8, 2013, Fulton, Bryan J. et al. |
| Portions of prosecution history of U.S. Appl. No. 13/177,546, Sep. 26, 2011, Fulton, Bryan J., et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,433, Apr. 22, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 12/286,098, Jan. 29, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,529, Apr. 15, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,537, Jan. 10, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,543, Apr. 18, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/218,433, Jan. 27, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,532, Apr. 15, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,534, Apr. 16, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,540, Mar. 4, 2014, Lambeth, W. Andrew, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,545, Apr. 15, 2014, Fulton, Bryan J., et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,533, Apr. 3, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,531, Mar. 27, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,530, Apr. 4, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,539, Apr. 9, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,535, Feb. 24, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,471, Mar. 18, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/219,533, Feb. 28, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,468, Mar. 10, 2014, Pfaff, Benjamin L., et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,464, Apr. 4, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/543,784, Apr. 17, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,538, Apr. 14, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,536, Feb. 28, 2014, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/269,409, Apr. 22, 2014, Koponen, Teemu, et al. |
| Das, Suarav, et al., “Unifying Packet and Circuit Switched Networks with OpenFlow,” Dec. 7, 2009, 10 pages. |
| Das, Suarav, et al. “Simple Unified Control for Packet and Circuit Networks,” Month Unknown, 2009, pp. 147-148, IEEE. |
| Updated portions of prosecution history of U.S. Appl. No. 12/286,098, May 7, 2013, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,529, May 31, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,530, May 31, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,531, May 2, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,533, May 31, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,537, May 20, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,538, May 28, 2013, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,539, May 31, 2013, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,545, May 31, 2013, Fulton, Bryan J., et al. |
| Portions of prosecution history of commonly owned U.S. Appl. No. 12/286,098, listed as item #63 above, including action(s) dated Nov. 7, 2012, Feb. 21, 2012, Nov. 8, 2011, Jun. 22, 2011, Mar. 24, 2011, Aug. 18, 2010, and May 5, 2010; and response(s)/amendment(s) filed Jun. 21, 2012, Oct. 24, 2011, Apr. 14, 2011, Mar. 14, 2011, Feb. 18, 2011, Jun. 4, 2010, and Sep. 24, 2009 (177 pages). |
| Portions of prosecution history of commonly owned U.S. Appl. No. 12/753,044, listed as item #72 above, including action(s) dated Sep. 24, 2012, Jan. 24, 2012, and Nov. 8, 2011; and response(s)/amendment(s) filed Jul. 24, 2012, Dec. 8, 2011, and Mar. 31, 2011 (108 pages). |
| Adya, Atul, et al., “Cooperative Task Management without Manual Stack Management,” Jun. 2002, 14 pages, Proceedings of the Usenix Annual Technical Conference, Monterey, CA, USA. |
| Andersen, David, et al., “Resilient Overlay Networks,” Oct. 2001, 15 pages, 18th ACM Symp. on Operating Systems Principles (SOSP), Banff, Canada, ACM. |
| Anderson, Thomas, et al., “Overcoming the Internet Impasse through Virtualization,” Apr. 2005, pp. 34-41, IEEE Computer Society. |
| Anhalt, Fabienne, et al., “Analysis and evaluation of a XEN based virtual router,” Sep. 2008, pp. 1-60, Unite de recherché INRA Phone-Alpes, Montbonnot Saint-Ismier, France. |
| Anwer, Muhammad Bilal, et al., “Building a Fast, Virtualized Data Plane with Programmable Hardware,” Aug. 17, 2009, pp. 1-8, VISA'09, Barcelona, Spain, ACM. |
| Author Unknown , “Cisco Nexis 1000V Series Switches,” Date Unknown but prior to Jul. 29, 2010, 2 pages, Cisco Systems, Inc., http://web.archive.org/web/20100729045626/http://www.cisco.com/en/US/Products/ps9902/index.html. |
| Author Unknown , “Cisco VN-Link: Virtualization-Aware Networking,” Month Unknown, 2009, 10 pages, Cisco Systems, Inc. |
| Author Unknown , “Citrix Launches New XenServer Release as Market Share Growth Continues,” Oct. 6, 2010, 3 pages, Citrix Systems, Inc. (http://www.citrix.com/English/ne/news/news.asp?newsID=2304355). |
| Author Unknown, “HP OpenView Enterprise Management Starter Solution,” Jun. 2006, p. 1-4, Hewlett-Packard Development Company, HP. |
| Author Unknown, “HP OpenView Operations 8.0 for UNIX Developer's Toolkit,” Month Unlknown, 2004, pp. 1-4, Hewlett-Packard Development Company, HP. |
| Author Unknown , “HP Web Jetadmin Integration into HP OpenView Network Node Manager,” Feb. 2004, pp. 1-12, HP. |
| Author Unknown , “IEEE Standard for Local and metropolitan area networks—Virtual Bridged Local Area Networks, Amendment 5: Connectivity Fault Management,” IEEE Std 802.1ag, Dec. 17, 2007, 260 pages, IEEE, New York, NY, USA. |
| Author Unknown, “Intel 82599 10 Gigabit Ethernet Controller: Datasheet, Revision: 2.73,” Dec. 2011, 930 pages, Intel Corporation. |
| Author Unknown , “Introduction to VMware Infrastructure: ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5,” Revision Dec. 13, 2007, pp. 1-46, VMware, Inc., Palo Alto, California, USA. |
| Author Unknown , “iSCSI SAN Configuration Guide: ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5,” Revision Nov. 29, 2007, pp. 1-132, VMware, Inc., Palo Alto, CA, USA. |
| Author Unknown , “Open vSwitch, An Open Virtual Switch,” Date Unknown but prior to Dec. 30, 2010, 2 pages, http://www.openvswitch.org/, Open vSwitch. |
| Author Unknown, “OpenFlow Switch Specification, Version 0.9.0 (Wire Protocol 0x98),” Jul. 20, 2009, pp. 1-36, Open Networking Foundation. |
| Author Unknown, OpenFlow Switch Specification, Version 1.0.0 (Wire Protocol 0x01), Dec. 31, 2009, pp. 1-42, Open Networking Foundation. |
| Author Unknown, “Private Network—Network Interface Specification Version 1.1 (PNNI 1.1),” The ATM Forum Technical Committee, Apr. 2002, 536 pages, The ATM Forum. |
| Author Unknown , “Single Root I/O Virtualization and Sharing Specification, Revision 1.0,” Sep. 11, 2007, pp. 1-84, PCI-SIG. |
| Author Unknown, “Virtual Machine Device Queues,” White Paper, Month Unknown, 2007, pp. 1-4, Intel Corporation. |
| Author Unknown , “VMare for Linus Networking Support,” Date Unknown but prior to Nov. 17, 1999, pp. 1-5, VMWare, Inc. |
| Ballani, Hitesh, et al., “Making Routers Last Longer with ViAggre,” NSDI'09: 6th USENIX Symposium on Networked Systems Design and Implementation, Apr. 2009, pp. 453-466, USENIX Association. |
| Barham, Paul, et al., “Xen and the Art of Virtualization,” Oct. 19-22, 2003, pp. 1-14, SOSP'03, Bolton Landing New York, USA. |
| Bavier, Andy, et. al., “In VINI Veritas: Realistic and Controlled Network Experimentation,” SIGCOMM'06, Sep. 2006, pp. 1-14, Pisa, Italy. |
| Bhatia, Sapan, et al., “Trellis: A Platform for Building Flexible, Fast Virtual Networks on Commodity Hardware,” ROADS'08, Dec. 9, 2008, pp. 1-6, Madrid, Spain, ACM. |
| Caesar, Matthew, et al., “Design and Implementation of a Routing Control Platform,” NSDI '05: 2nd Symposium on Networked Systems Design & Implementation , Apr. 2005, pp. 15-28, Usenix Association. |
| Cai, Zheng, et al., “The Preliminary Design and Implementation of the Maestro Network Control Platform,” Oct. 1, 2008, pp. 1-17, NSF. |
| Casado, Martin, et al. “Ethane: Taking Control of the Enterprise,” SIGCOMM'07, Aug. 27-31, 2007, pp. 1-12, ACM, Kyoto, Japan. |
| Casado, Martin, et al., “Rethinking Packet Forwarding Hardware,” Seventh ACM SIGCOMM' HotNets Workshop, Nov. 2008, pp. 1-6, ACM. |
| Casado, Martin, et al., “SANE: A Protection Architecture for Enterprise Networks,” In proceedings of Usenix Security, Aug. 2006, pp. 1-15. |
| Casado, Martin, et al., “Virtualizing the Network Forwarding Plane,” Dec. 2010, pp. 1-6. |
| Congdon, Paul, “Virtual Ethernet Port Aggregator Standards body Discussion,” Nov. 10, 2008, pp. 1-26, HP. |
| Cooper, Brian F., et al., “PNUTS: Yahoo!'s Hosted Data Serving Platform,” VLDB'08, Aug. 24-30, 2008, pp. 1-12, ACM , Auckland, New Zealand. |
| Davoli, Renzo, “VDE: Virtual Distributed Ethernet,” TRIDENTCOM'05, Feb. 23-25, 2005, pp. 1-8, IEEE Computer Society. |
| Dixon, Colin, et al., “An End to the Middle,” Proceedings of the 12th conference on Hot topics in operating systems USENIX Association, May 2009, pp. 1-5, Berkeley, CA, USA. |
| Dobrescu, Mihai, et al., “RouteBricks: Exploiting Parallelism to Scale Software Routers,” SOSP'09, Proceedings of the ACM SIGOPS 22nd Symposium on Operating Systems Principles, Oct. 2009, pp. 1-17, ACM New York, NY. |
| Enns, R., “NETCONF Configuration Protocol,” Dec. 2006, pp. 1-96, IETF Trust (RFC 4741). |
| Farinacci, D., et al., “Generic Routing Encapsulation (GRE),” Mar. 2000, pp. 1-9, The Internet Society (RFC 2784). |
| Farrel, A., “A Path Computation Element (PCS)—Based Architecture,” Aug. 2006, pp. 1-41, RFC 4655. |
| Fischer, Anna, “[PATCH][RFC] net/bridge: add basic VEPA support,” Jun. 2009, pp. 1-5, GMANE Org. |
| Garfinkel, Tal, et al., “A Virtual Machine Introspection Based Architecture for Intrusion Detection,” In Proc. Network and Distributed Systems Security Symposium, Feb. 2003, pp. 1-16. |
| Godfrey, P. Brighten, et al., “Pathlet Routing,” SIGCOMM, Aug. 2009, pp. 1-6, ACM. |
| Greenberg, Albert, et al., “A Clean Slate 4D Approach to Network Control and Management,” ACM SIGCOMM Computer Communication Review, Oct. 2005, 12 pages, vol. 35, No. 5. |
| Greenberg, Albert, et al., “VL2: A Scalable and Flexible Data Center Network,” SIGCOMM'09, Aug. 17-21, 2009, pp. 51-62, ACM, Barcelona, Spain. |
| Greenhalgh, Adam, et al., “Flow Processing and the Rise of Commodity Network Hardware,” ACM SIGCOMM Computer Communication Review, Apr. 2009, pp. 21-26, vol. 39, No. 2. |
| Gude, Natasha, et al., “NOX: Towards an Operating System for Networks,” ACM SIGCOMM Computer communication Review, Jul. 2008, pp. 105-110, vol. 38, No. 3. |
| Guo, Chanxiong, et al., “BCube: A High Performance, Server-centric Network Architecture for Modular Data Centers,” SIGCOMM'09, Aug. 17-21, 2009, pp. 1-12, ACM, Barcelona, Spain. |
| Hamilton, James, et al., “Datacenter Networks Are in My Way,” Principals of Amazon Series, Oct. 28, 2010, pp. 1-14. |
| Handley, Mark, et al., “Designing Extensible IP Router Software,” Proc. of NSDI, May 2005, pp. 1-14. |
| Hinrichs, Timothy L., et al., “Practical Declarative Network Management,” WREN'09, Aug. 21, 2009, pp. 1-10, Barcelona, Spain. |
| Hunt, Patrick, et al., “ZooKeeper: Wait-free Coordination for Internet-Scale Systems,” Proc. of USENIX Annual Technical Conference, Month Unknown, 2010, pp. 1-14. |
| Ioannidis, Sotiris, et al., “Implementing a Distributed Firewall,” CCS'00, Month Unknown, 2000, pp. 1-10, ACM, Athens, Greece. |
| John, John P., et al., “Consensus Routing: The Internet as a Distributed System,” Proc. of NSDI , Apr. 2008, pp. 1-14. |
| Kamath, Daya, et. al., “Edge virtual Bridge Proposal, Version 0. Rev. 0.1,” Apr. 23, 2010, pp. 1-72, IEEE. |
| Katz, D., et. al, “Bidirectional Forwarding Detection, draft-ietf-bfd-base-11.txt,” Month Unknown, 2009, pp. 1-51, IETF Trust. |
| Keller, Eric, et al., “The ‘Platform as a Service’ Model for Networking,” Month Unknown, 2010, pp. 1-6. |
| Kim, Changhoon, et al., “Floodless in SEATTLE: A Scalable Ethernet Architecture for Large Enterprises,” SIGCOMM'08, Aug. 17-22, 2008, pp. 3-14, ACM, Seattle, Washington, USA. |
| Kohler, Eddie, et al., “The Click Modular Router,” ACM Trans. On Computer Systems, Aug. 2000, 34 pages, vol. 18, No. 3. |
| Koponen, Teemu, et al., “Onix: A Distributed Control Platform for Large-scale Production Networks,” In Proc. OSDI, Oct. 2010, pp. 1-14. |
| Labovitz, Craig, et al., “Delayed Internet Routing Convergence,” SIGCOMM'00, Month Unknown, 2000, pp. 175-187, Stockholm, Sweden. |
| Labovitz, Craig, et al., “Internet Routing Instability,” ACM SIGCOMM '97, Month Unknown, 1997, pp. 1-12, Association for Computing Machinery, Inc. |
| Lakshminarayanan, Karthik, et al., “Routing as a Service,” Month Unknown, 2004, pp. 1-15, Berkeley, California. |
| Luo, Jianying, et al., “Prototyping Fast, Simple, Secure Switches for Ethane,” Month Unknown, 2007, pp. 1-6. |
| Maltz, David A., et al., “Routing Design in Operational Networks: A Look from the Inside,” SIGCOMM'04, Aug. 30-Sep. 3, 2004, pp. 1-14, ACM, Portland, Oregon, USA. |
| McKeown, Nick, et al., “OpenFlow: Enabling Innovation in Campus Networks,” ACS SIGCOMM Computer communication Review, Apr. 2008, pp. 69-74, vol. 38, No. 2. |
| Mogul, Jeffrey C., et al., “API Design Challenges for Open Router Platforms on Proprietary Hardware,” Oct. 2008, pp. 1-6. |
| Mysore, Radhka Niranjan, et al., “PortLand: A Scalable Fault-Tolerant Layer 2 Data Center Network Fabric,” Proc. of SIGCOMM, Aug. 17-21, 2009, pp. 1-12. |
| Partridge, Craig, et al., “A 50-Gb/s IP Router,” IEEE/ACM Transactions on Networking Jun. 1998, pp. 237-248. |
| Pelissier, Joe, “Network Interface Virtualization Review,” Jan. 2009, pp. 1-38. |
| Pelissier, Joe, “VNTag 101,” May 2008, pp. 1-87. |
| Peterson, Larry L., et al., “OS Support for General-Purpose Routers,” Month Unknown, 1999, 6 pages. |
| Pettit, Justin, et al., “Virtual Switching in an Era of Advanced Edges,” Sep. 2010, 7 pages. |
| Pfaff, Ben., et al., “Extending Networking into the Virtualization Layer,” Proc. Of HotNets, Oct. 2009, pp. 1-6. |
| Phan, Doantam, et al., “Visual Analysis of Network Flow Data with Timelines and Event Plots,” Month Unknown, 2007, pp. 1-16, VizSEC. |
| Rosen, E., et al., “Applicant Statement for BGP/MPLS IP Virtual Private Networks (VPNs),” The Internet Society, RFC 4365, Feb. 2006, pp. 1-32. |
| Sherwood, Rob, et al., “Can the Production Network Be the Testbed?,” Month Unknown, 2010, pp. 1-14. |
| Sherwood, Rob, et al., “Carving Research Slices Out of Your Production Networks with OpenFlow,” ACM SIGCOMM Computer Communications Review, Jan. 2010, pp. 129-130, vol. 40, No. 1. |
| Sherwood, Rob, et al., “FlowVisor: A Network Virtualization Layer,” Oct. 14, 2009, pp. 1-14, OPENFLOW-TR-2009-1. |
| Spalink, Tammo, et al., “Building a Robust Software-Based Router Using Network Processors,” Month Unknown, 2001, pp. 216-229, ACM, Banff, CA. |
| Tavakoli, Arsalan, et al., “Applying NOX to the Datacenter,” Proc. HotNets, Month Unknown, 2009, 6 pages. |
| Touch, J., et al., “Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement,” May 2009, pp. 1-17, IETF Trust, RFC 5556. |
| Turner, Jon, et al., “Supercharging PlanetLab—High Performance, Multi-Application Overlay Network Platform,” SIGCOMM-07, Aug. 27-31, 2007, 12 pages, ACM, Koyoto, Japan. |
| Turner, Jonathan S., “A Proposed Architecture for the GENI Backbone Platform,” ANCS'06, Dec. 3-5, 2006, 10 pages, ACM, San Jose, California, USA. |
| Wang, Yi, et al., “Virtual Routers on the Move: Live Router Migration as a Network-management Primitive,” SIGCOMM 08, Aug. 17-22, 2008, 12 pages, ACM, Seattle, Washington, USA. |
| Xie, Geoffrey G., et al., “On Static Reachability Analysis of IP Networks,” Month Unknown, 2005, pp. 1-14. |
| Yang, L., et al., “Forwarding and Control Element Separation (ForCES) Framework,” Apr. 2004, pp. 1-40, The Internet Society. |
| Yu, Minlan, et al., “Scalable Flow-Based Networking with DIFANE,” In Proc. SIGCOMM Aug. 2010, 16 pages. |
| Portions of prosecution history of U.S. Appl. No. 13/177,541, Jun. 25, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 12/286,098, Aug. 14, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 12/753,044, Jun. 10, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,529, May 6, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,537, Jun. 20, 2014, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/219,557, Jun. 2, 2014, Koponen, Teemu, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,427, Aug. 15, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,543, Aug. 14, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/218,433, Jun. 5, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,532, May 2, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,534, Aug. 1, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,540, May 8, 2014, Lambeth, W. Andrew, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,545, Apr. 30, 2014, Fulton, Bryan J., et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,546, Jun. 5, 2014, Fulton, Bryan J., et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,533, Aug. 1, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,539, Jul. 31, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,535, May 16, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,472, Jun. 2, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/218,471, Aug. 5, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/219,533, May 6, 2014, Casado, Martin, et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,470, Jun. 16, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/218,468, Aug. 15, 2014, Pfaff, Benjamin L., et al. |
| Portions of prosecution history of U.S. Appl. No. 13/218,467, Jul. 14, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/218,464, Aug. 4, 2014, Casado, Martin, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,538, Aug. 7, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/177,536, May 2, 2014, Koponen, Teemu, et al. |
| Updated portions of prosecution history of U.S. Appl. No. 13/269,409, Aug. 15, 2014, Koponen, Teemu, et al. |
| Wang, Wei-Ming, et al., “Analysis and Implementation of an Open Programmable Router Based on Forwarding and Control Element Separation,” Sep. 2008, pp. 769-779, Journal of Computer Science and Technology. |
| Number | Date | Country | |
|---|---|---|---|
| 20130060818 A1 | Mar 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61361912 | Jul 2010 | US | |
| 61361913 | Jul 2010 | US | |
| 61429753 | Jan 2011 | US | |
| 61429754 | Jan 2011 | US | |
| 61466453 | Mar 2011 | US | |
| 61482205 | May 2011 | US | |
| 61482615 | May 2011 | US | |
| 61482616 | May 2011 | US | |
| 61501743 | Jun 2011 | US | |
| 61501785 | Jun 2011 | US | |
| 61505100 | Jul 2011 | US | |
| 61505102 | Jul 2011 | US | |
| 61505103 | Jul 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13177529 | Jul 2011 | US |
| Child | 13219562 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13177536 | Jul 2011 | US |
| Child | 13177529 | US | |
| Parent | 13177538 | Jul 2011 | US |
| Child | 13177536 | US |
