Chassis controller
A non-transitory machine readable medium storing a program that configures managed forwarding elements to establish tunnels between the managed forwarding elements is described. From a particular managed forwarding element, the program receives information regarding coupling of a network element to the first managed forwarding element. Upon receiving the information, the program generates a set of universal flow entries for configuring another managed forwarding element to establish a tunnel to the particular managed forwarding element.
1. A method of configuring a first managed forwarding element (MFE) executing on a first host computer to implement a logical forwarding element (LFE), the method comprising:
receiving, from a controller operating outside of the first host computer, a first set of configuration data associated with the LFE;
based on the received first set of configuration data, generating a second set of configuration data for defining forwarding behavior of the first MFE to implement the LFE; and
using the second set of configuration data to configure the first MFE to implement the LFE, in conjunction with a plurality of other MFEs executing on a plurality of other host computers;
wherein the LFE belongs to a logical network that logically connects a set of end machines that execute on the first host computer and a plurality of other end machines that execute on the plurality of other host machines, wherein the end machines are sources and destinations of logical network data traffic forwarded by the MFEs implementing the LFE.
2. The method of claim 1 , wherein the generating is performed by a controller application executing on the first host computer.
3. The method of claim 2 , wherein the controller operating outside of the first host computer also provides the first configuration data set to other controller applications executing on the other host computers, and the other controller applications uses the first configuration data set to generate additional configuration data sets for configuring MFEs executing on their respective host computers to implement the LFE.
4. The method of claim 2 , wherein the controller application further comprises a set of instructions for receiving MFE-specific data from the MFE.
5. The method of claim 4 , wherein said generating comprises generating the data based on (i) the received first set of configuration data and (ii) the received MFE-specific data.
6. The method of claim 5 , wherein the received MFE-specific data comprises a physical port number of the MFE to which a logical port of the LFE is mapped.
7. The method of claim 1 , wherein the LFE is a first LFE, the set of end machines is a first set of end machines, the logical network is a first logical network, and the plurality of other MFEs executing on the plurality of other host computers is a first plurality of other MFEs executing on a first plurality of other host computers the method further comprising:
receiving a third set of configuration data associated with a second LFE;
based on the received third set of configuration data, generating a fourth set of configuration data for defining forwarding behavior of the first MFE to implement the second LFE; and
using the fourth set of configuration data to configure the first MFE to implement the second LFE, in conjunction with a second plurality of other MFEs executing on a second plurality of other host computers.
8. The method of claim 7 , wherein
the controller operating outside of the first host computer is a first controller that manages a first logical network to which the first LFE belongs; and
receiving the third set of configuration data comprises receiving the third set of configuration data from a second controller computer that manages a second logical network to which the second LFE belongs.
9. The method of claim 8 , wherein the first logical network belongs to a first tenant while the second logical network belongs to a second different tenant.
10. A non-transitory machine-readable medium storing a first controller application for execution by at least one processing unit of a first host computer, the first controller application comprising sets of instructions for:
receiving, from a controller operating outside of the first host computer, a first set of configuration data associated with the LFE;
based on the received first set of configuration data, generating a second set of configuration data for defining forwarding behavior of the first MFE to implement the LFE; and
using the second set of configuration data to configure the first MFE to implement the LFE, in conjunction with a plurality of other MFEs executing on a plurality of other host computers;
wherein the LFE belongs to a logical network that logically connects a set of end machines that execute on the first host computer and a plurality of other end machines that execute on the plurality of other host machines, wherein the end machines are sources and destinations of logical network data traffic forwarded by the MFEs implementing the LFE.
11. The non-transitory machine-readable medium of claim 10 , wherein the first MFE implements the LFE by mapping one or more logical ports of the LFE to one or more physical ports of the first MFE.
12. The non-transitory machine-readable medium of claim 10 , wherein the controller operating outside of the first host computer also provides the first configuration data set to other controller applications executing on the other host computers, and the other controller applications uses the first configuration data set to generate additional configuration data sets for configuring MFEs executing on their respective host computers to implement the LFE.
13. The non-transitory machine-readable medium of claim 10 , wherein the first controller application further comprises a set of instructions for receiving MFE-specific data from the MFE.
14. The non-transitory machine-readable medium of claim 13 , wherein said generating comprises generating the data based on (i) the received first set of configuration data and (ii) the received MFE-specific data.
15. The non-transitory machine-readable medium of claim 14 , wherein the received MFE-specific data comprises a physical port number of the MFE to which a logical port of the LFE is mapped.
16. The non-transitory machine-readable medium of claim 10 , wherein the LFE is a first LFE, the set of end machines is a first set of end machines, the logical network is a first logical network, and the plurality of other MFEs executing on the plurality of other host computers is a first plurality of other MFEs executing on a first plurality of other host computers the first controller application further comprising sets of instructions for:
receiving a third set of configuration data associated with a second LFE;
based on the received third set of configuration data, generating a fourth set of configuration data for defining forwarding behavior of the first MFE to implement the second LFE; and
using the fourth set of configuration data to configure the first MFE to implement the second LFE, in conjunction with a second plurality of other MFEs executing on a second plurality of other host computers.
17. The non-transitory machine-readable medium of claim 16 , wherein
the controller operating outside of the first host computer is a first controller that manages a first logical network to which the first LFE belongs; and
the set of instructions for receiving the third set of configuration data comprises receiving a set of instructions for the third set of configuration data from a second controller computer that manages a second logical network to which the second LFE belongs.
18. The non-transitory machine-readable medium of claim 17 , wherein the first logical network belongs to a first tenant while the second logical network belongs to a second different tenant.