DCN infrastructure Sample Clauses

DCN infrastructure. The DCN infrastructure information model is an uniform model exposed by the abstraction layer for both internal SDN controller modules and external applications and it is used to provide information about the DCN capabilities. The main objective of the abstraction layer is to provide an homogenous view of the DCN infrastructure to facilitate the management and control of the heterogeneous devices and technologies that compose the data plane. To achieve an information model that is generic enough to cope with all the technologies involved in the DCN, we need to simplify the elements and parameters to be used. In this context, at the most simplified view, the DCN can be seen as a set of nodes and links, which are deployed in a specific topology. Hence, in a first phase of the information model, the topology element defines the nodes and links composing the DCN. Then, the nodes provide an abstraction of the different switching devices that can be found in the data plane (e.g. ToRs, optical switches, etc.). Finally, the links connect the different nodes into the given topology. The number of nodes and links characterize the topology element. The nodes may be further divided into different classes according to the role they play in the DCN but, in a first stage, all of them need to keep common attributes such as the number and type of ports. For the links, bandwidth and occupancy attributes are needed. The DCN information model is typically used in read-write mode from some of the internal modules of the SDN controller, since they may need to operate and configure somehow the DCN itself. However, the REST APIs towards external entities may reduce the access to read-only operations. This is typically the case of the cloud management platform, which may need to collect information related to the DCN capabilities for taking internal decisions about cloud service scheduling or VM locations. However, the cloud platform itself is not allowed to operate directly on the DCN (i.e. with writing access on DCN resources), but needs the mediation of other DCN Control Plane services. They will be responsible to configure the DCN while providing higher level APIs to create virtual network slices for IaaS provisioning or end-to-end intra-DC connections to enable DC management procedures.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to DCN infrastructure

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Utility Infrastructure During the term of this Agreement, Company will have the right to receive water, sanitary sewer, electric, storm drainage, telecommunication and data services at the Premises.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Information regarding Interconnection Facilities 4.2.1 The SPD shall be required to obtain all information from the STU/CTU/concerned authority with regard to the Interconnection Facilities as is reasonably necessary to enable it to design, install and operate all interconnection plant and apparatus on the SPD’s side of the Delivery Point to enable delivery of electricity at the Delivery Point. The transmission of power up to the point of interconnection where the metering is done for energy accounting shall be the responsibility of the SPD at his own cost.

  • Energy Resource Interconnection Service (ER Interconnection Service).

  • Critical Infrastructure Subcontracts For purposes of this Paragraph, the designated countries are China, Iran, North Korea, Russia, and any countries lawfully designated by the Governor as a threat to critical infrastructure. Pursuant to Section 113.002 of the Business and Commerce Code, Contractor shall not enter into a subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business and Commerce Code, in this state, other than access specifically allowed for product warranty and support purposes to any subcontractor unless (i) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is majority owned or controlled by citizens or governmental entities of a designated country; and (ii) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is headquartered in a designated country. Contractor will notify the System Agency before entering into any subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business & Commerce Code, in this state.

  • Network Interconnection 26.1 Interconnection between the networks of different SERVICE PROVIDERs shall be as per National Standards of CCS No.7 issued from time to time by Telecom Engineering Centre (TEC) and also subject to technical feasibility and technical integrity of the Networks and shall be within the overall framework of interconnection regulations issued by the TRAI from time to time. However, if situation so arises, INTERCONNECTION with R2MF signaling may be permitted by LICENSOR.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties have agreed to use One-Way Interconnection Trunks for the delivery of traffic from PCS to Verizon, PCS, at PCS’s own expense, shall:

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