General Architecture of the COSIGN Control Plane Sample Clauses

General Architecture of the COSIGN Control Plane. The DC Control and Management layer is built upon Software Defined Networks (SDN) capabilities to leverage the added value of emerging optical technologies and aims to provide a converged network and IT virtualization platform for Data Centres. The DC Control and Management layer will result from the joint effort of WP3 and WP4, where WP3 will mostly focus on the DCN control aspects, while WP4 will address the whole DC management, including network, computing and storage resources, together with the orchestration of cloud services and applications. Figure 5 outlines the most important features and capabilities for each of the COSIGN architectural layers, with particular attention to the DCN Control Plane. These capabilities and how they relate to the internal CP components or to other COSIGN layers will be further discussed in the next sections. Figure 5 – Functions and capabilities of COSIGN architectural layers In COSIGN architecture, the DCN Control Plane is placed between the DCN physical layer (WP2) and the DC Orchestration and Management plane (WP4), which is implemented through a cloud management platform (e.g. OpenStack). The cross-layer interaction is enabled through the northbound interface with the Orchestration and Management plane and the southbound interface with the DCN optical data plane. Considering a deployment where the CP functions are implemented in a centralized SDN controller (optionally with the contribution of some external SDN applications), these interfaces can be easily mapped respectively on the A-CPI and D-CPI interfaces defined in ONF (see Section 2.3 for details). In this view, the DCN Control Plane can be considered as a sort of mediator between the optical hardware devices deployed at the DCN infrastructure and the software platform, running at the upper layer, which is in charge of coordinating the whole DC actions for the provisioning of cloud services. In this role, the control plane needs to ensure a twofold objective:  Translate the abstract network-related directives generated from the software cloud platform and enforce them through the actual configuration of the DCN data plane.  Guarantee the efficient utilization of the DCN data plane, in terms of features and capabilities, to provide the DC network connectivity required by the upper layer software cloud platform, in support of on-demand IaaS provisioning and DC management actions.
Sample 1
AutoNDA by SimpleDocs

Related to General Architecture of the COSIGN Control Plane

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Quality Control Plan Within forty five (45) days after the design development documents are approved, the Design-Builder shall develop a quality control plan for the Project (the “Quality Control Plan”). A draft of the Quality Control Plan shall be submitted to the Department and shall be subject to the Department’s review and approval. The Quality Control Plan shall be tailored to the specific products/type of construction activities contemplated by the GMP Basis Documents, and in general, shall include a table of contents, quality control team organization, duties/responsibilities of quality control personnel, submittal procedures, inspection procedures, deficiency correction procedures, documentation process, and a list of any other specific actions or procedures that will be required for key elements of the Work.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

Time is Money Join Law Insider Premium to draft better contracts faster.