Forwarding element slice identifying control plane
Some embodiments of the invention provide a novel method of performing network slice-based operations on a data message at a hardware forwarding element (HFE) in a network. For a received data message flow, the method has the HFE identify a network slice associated with the received data message flow. This network slice in some embodiments is associated with a set of operations to be performed on the data message by several network elements, including one or more machines executing on one or more computers in the network. Once the network slice is identified, the method has the HFE process the data message flow based on a rule that applies to data messages associated with the identified slice.
1. A hardware forwarding element comprising:
a data plane forwarding circuit to perform slice-based data plane forwarding operations on a set of data messages received by the forwarding element; and
a control plane circuit comprising a set of processing units and a non-transitory machine-readable medium storing a slice identifier (ID) specifying program for execution by the set of processing units,
the program to specify slice IDs of network slices associated with data messages and to provide the slice IDs to the data plane forwarding circuit to perform slice-based forwarding operation based on the provided slice IDs,
the control plane providing the slice ID for a data message with a configuration instruction to configure the data plane forwarding circuit to store a record that associates a flow identifier of the data message with the slice ID,
wherein after matching another data message's flow identifier with the record's flow identifier, the data plane circuit uses the record's slice ID to identify another record that specifies a forwarding operation based on the slice ID.
2. The hardware forwarding element of claim 1 , wherein the data plane forwarding circuit provides to the control plane circuit each data message for which the control plane circuit needs to specify the slice ID.
3. The hardware forwarding element of claim 1 , wherein the data plane forwarding circuit provides to the control plane circuit a flow identifier for each data message for which the control plane circuit needs to specify the slice ID.
4. The hardware forwarding element of claim 1 , wherein the non-transitory machine readable further stores a set of one or more service programs to perform a set of slice-based service operations on data messages for which the slice-ID specifying program identifies slice IDs.
5. A hardware forwarding element comprising:
a data plane forwarding circuit to perform slice-based data plane forwarding operations on a set of data messages received by the forwarding element; and
a control plane circuit comprising a set of processing units and a non-transitory machine-readable medium storing a slice identifier (ID) specifying program for execution by the set of processing units,
the program to specify slice IDs of network slices associated with data messages and to provide the slice IDs to the data plane forwarding circuit to perform slice-based forwarding operation based on the provided slice IDs,
wherein:
the non-transitory machine readable further stores a set of one or more service programs to perform a set of slice-based service operations on data messages for which the slice-ID specifying program identifies slice IDs;
the control plane circuit configures, for each slice ID that the slice-ID specifying program specifies the slice ID, the data plane forwarding circuit to identify the slice ID; and
before the data plane forwarding circuit is configured for a flow, the set of service programs perform the set of slice-based operations on a group of data messages in the flow and the control plane circuit provides the processed data messages in the group to the data plane forwarding circuit to forward within a network.
6. A hardware forwarding element comprising:
a data plane forwarding circuit to perform slice-based data plane forwarding operations on a set of data messages received by the forwarding element; and
a control plane circuit comprising a set of processing units and a non-transitory machine-readable medium storing a slice identifier (ID) specifying program for execution by the set of processing units,
the program to specify slice IDs of network slices associated with data messages and to provide the slice IDs to the data plane forwarding circuit to perform slice-based forwarding operation based on the provided slice IDs,
wherein:
the non-transitory machine readable further stores a set of one or more service programs to perform a set of slice-based service operations on data messages for which the slice-ID specifying program identifies slice IDs;
the control plane circuit comprises a network interface controller;
the control plane circuit configures, for each slice ID that the slice-ID specifying program specifies the slice ID, the data plane forwarding circuit to identify the slice ID; and
before the data plane forwarding circuit is configured for a flow, the set of service programs perform the set of slice-based operations on a group of data messages in the flow and the control plane circuit uses the network interface controller to forward in a network the processed data messages in the group.
7. The hardware forwarding element of claim 1 , wherein the program is a Linux operating system with which at least one container is defined to perform a second set of data plane forwarding operations.
8. The hardware forwarding element of claim 1 , wherein the program is a container machine.
9. The hardware forwarding element of claim 1 , wherein the program is a virtual machine executing over a hypervisor executed by the set of processing units.
10. The hardware forwarding element of claim 1 , wherein the program is a hypervisor comprising at least one module that performs at least a subset of a second set of data plane forwarding operations.