Red Hat Cloud Infrastructure Subscriptions
Red Hat Cloud Infrastructure Subscriptions Sample Clauses
Related to Red Hat Cloud Infrastructure Subscriptions
Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.
Software Subscription Lifecycle During the life cycle of Red Hat Software, the scope of Software Maintenance and Support evolves and, after a number of years, we discontinue Software Maintenance and Support for older versions of Software. The details of the Software Maintenance and Production Support life cycle are set forth at xxxxx://xxxxxx.xxxxxx.xxx/support/policy/update_policies.html. If available, you may purchase Extended Update Support and/or Extended Life Cycle Support, as described in Exhibit 1.G, to extend your Subscription Services for certain versions of Software.
Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.
Software Subscription The Term of any Software Subscription shall automatically renew for an additional Subscription License Term unless written notice of termination is given to the other Party three (3) months prior to the expiration of the then-current Term.
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:
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.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and VarTec, VarTec shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
Sub-projects 1. The Participating Bank shall make Sub-loans to Beneficiaries and appraise, review, approve, and supervise Sub-projects in accordance with the criteria, conditions and procedures set forth in the Operations Manual, including, inter alia, the following eligibility criteria:
wire Unbundled ISDN Digital Loops These will be provisioned according to industry standards for 2-Wire Basic Rate ISDN services and will come standard with a test point, OC, and a DLR. NewPhone will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable Loop and customer. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.
Sub-processing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub-processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.
