RAINBOW Actors Sample Clauses

RAINBOW Actors. Taking under consideration the high-level architecture and its brief “walkthrough”, it is worth elaborating on the distinct roles that are identified in the RAINBOW ecosystem. These roles are also depicted on Figure 7, along with the components they are interacting with. Service Developer Refers to the developer of a cloud-native component (or a service graph as a whole). The developer packages his/her application in a cloud-native format; yet s/he can use RAINBOW modelling extensions in order to define exposed metrics and Service Level Objectives (SLOs). Service Provider Refers to the user that aims to instantiate an entire service graph under a specific operational policy. Such a policy includes QoS and security aspects. The Service Provider will be able to author complex policies and enforce them through the RAINBOW orchestration components. IaaS Provider Refers to the cloud provider that offers compute, storage and networking infrastructure along the proper high- level programmability. An IaaS provider should comply with an abstracted/standardized API used by the Resource Manager. Fog Device Vendor Refers to the IoT vendor which can execute the RAINBOW Fog stack. Data Analyst Refers to the user that creates analytics queries on top of an existing service graph deployment. These queries will be analysed and executed by respective orchestrator components.
View Source

Related to RAINBOW Actors

  • Sub-Contractors Transfer Agent may, without further consent on the part of Customer, subcontract with other subcontractors for telephone and mailing services as may be required from time to time; provided, however, that the Transfer Agent shall be as fully responsible to the Customer for the acts and omissions of any subcontractor as it is for its own acts and omissions.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (eff. Sept. 1, 2023, Section 2275.0102(a)(1), pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.) (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 (eff. Sept. 1, 2023, Section 2275.0102, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.), 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 (eff. Sept. 1, 2023, Section 2275.0103, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.), or (2) headquartered in any of those countries.

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.

  • Sub-loop Elements 2.8.1 Where facilities permit, BellSouth shall offer access to its Unbundled Sub-Loop (USL) elements as specified herein.