Control Plane. Private / Shared Circuit Configuration Private and shared optical circuits are differed by setting which of the switch's input ports are matched by the rerouting rule of elephant flows through the optical circuit. Therefore, different metadata values are assigned to packets from input ports connected to the lower and the upper packet tiers. Then, by mask matching on the metadata value of an ingress packet, one can configure the switch either to use the optical circuit as private by serving only packets from the lower tier, or shared by serving packets also from the upper tier. Figure 6 demonstrates Open vSwitch [34] configuration for private and shared circuits. At initialization, metadata values of 0b01 and 0b11 are assigned to packets arriving from the upper and lower tier, respectively. For a private circuit, a single OpenFlow rule is set to match packets with metadata values of 0b1* by using 0b10 mask. Therefore, only packets from all input ports connected to the lower tier are matched and transmitted though the circuit. Similarly, for a shared circuit, packets with metadata of 0b*1 are matched by using 0b01 mask. Hence, packets arriving from all input ports connected to both upper and lower tiers are matched and transmitted through the circuit. As described above, the OpenFlow rule is also set to capture the DSCPe value (nwtos), and the lower tier subnet destination (nwdst) of the switch connected to the other end of the optical circuit.
Control Plane. Providing Software as a Service (SaaS) for cloud automation, cloud control and management of software. Control Plane enables self-service environment provisioning, deployment of all tools in DevOps toolchain such as Xxxxxxx, Git, Spinnaker, Sysdig, pre-configured with SSO and RBAC across all tools.
Control Plane. Table 5.3 – DCN Data Plane Requirements This section presents the requirements for the COSIGN DCN control plane, collected through the analysis of the use cases proposed in Section 3, the current challenges of DCN architectures and Control Plane (CP) solutions and the new capabilities provided by the innovative optical technologies adopted in the COSIGN DCN data plane. The CP requirements are summarized in Table 5.4. Requirement ID and Name Requirement Description R-CP-01 Automated provisioning of intra-DC connectivity The COSIGN CP must provide mechanisms for an automated DCN configuration to establish and destroy intra-DC connectivity services on-demand (triggered by external requests) or in support of internal procedures (e.g. re-optimization of DCN resource allocation, connectivity restoration, etc.). R-CP-02 Support for customizable network services The COSIGN CP must provide mechanisms to provide intra-DC connectivity services compliant with a variety of user-level constraints, including QoS parameters (e.g. bandwidth), timing constraints, service resilience guarantees.
Control Plane. Databricks deploys new code to the Databricks Control on an ongoing basis.
