Unité de Mesure et Spécifications Sample Clauses

Unité de Mesure et Spécifications d'Achat pour Red Hat Enterprise Linux Server Vous devez acheter le nombre et le type appropriés de Souscription(s) Logiciel pour chaque Unité de Red Hat Enterprise Linux Server, y compris ses variantes comme Red Hat Enterprise Linux Server pour HPC Compute Nodes, Red Hat Enterprise Linux pour IBM POWER et Red Hat Enterprise Linux pour SAP Applications, en fonction de la capacité de ladite Unité telle que décrite dans le Tableau 1 ci-dessous. De multiples Souscriptions Logiciel peuvent être « empilées » pour tenir compte de la capacité d'une Unité donnée. L'« empilage » (ou « empilable ») désigne l'application de plus d'une Souscription du même type pour tenir compte de la capacité supplémentaire. Table 1 Software Subscription Support Level Unit of Measure Capacity Stackable Socket(s) Virtual Nodes Red Hat Enterprise Linux Server (Physical or Virtual Nodes) Red Hat Enterprise Linux for SAP HANA Red Hat Enterprise Linux for IBM PowerLinux Standard or Premium Physical Node OR Virtual Node Socket-pair for each Physical Node OR 2 Virtual Nodes Physical Node: Yes Virtual Node: Yes, up to a maximum of 4 virtual instances2 per Physical Node Red Hat Enterprise Linux for Virtual Datacenters1 Standard or Premium Physical Node Socket-pair Unlimited Virtual Nodes running on a Socket-pair Physical Node: Yes Virtual Node: Yes Red Hat Enterprise Linux Server Entry Level Self-support Physical Node Socket-pair None Physical Node: No Virtual Node: Yes, up to a maximum of 4 virtual instances2 per Physical Node Red Hat Enterprise Linux OpenStack Platform Standard or Premium Physical Node Socket-pair Unlimited Virtual Nodes running on a Socket-pair Physical Node: Yes Virtual Node: Yes Red Hat Enterprise Linux for Hyperscale Standard Physical Node Band of SOCs None Physical Node: No Virtual Node: No Red Hat Enterprise Linux with Smart Virtualization Standard or Premium Physical Node Socket-pair Unlimited Virtual Nodes running on a Socket-pair Physical Node: Yes Virtual Node: Yes Red Hat Enterprise Linux Server Standard or Premium System 1-2 Sockets, 4 Sockets, or 8 Sockets 1 Virtual Guest, 4 Virtual Guests, or Unlimited Virtual Guests Sockets: No Virtual Guest: Yes Red Hat Enterprise Linux Server Self-support System 1-2 Sockets 1 Virtual Guest Sockets: No Virtual Guest: No Red Hat Enterprise Linux for PRIMEQUEST Premium System 1-2 Sockets, 4 Sockets, 6 Sockets or 1 Virtual Guest,4 Virtual Guests, or Unlimited Virtual Sockets: No Virtual Guest: Yes 8 Sockets Guests Tableau 1 Sous...
AutoNDA by SimpleDocs
Unité de Mesure et Spécifications d'Achat pour Red Hat Enterprise Linux Server Vous devez acheter le nombre et le type appropriés de Souscription(s) Logiciel pour chaque Système sur lequel vous déployez, installez, utilisez ou exécutez Red Hat Enterprise Linux Server y compris ses variantes comme Red Hat Enterprise Linux Server pour HPC Compute Nodes, pour Power et pour SAP, en fonction du (1) nombre de Paires de sockets et d'Invités Virtuels lorsque l'Unité est un Système ; ou (2) du nombre de vCPU lorsque l'Unité est un vCPU. A “Socket-pair” is up to two sockets each occupied by a CPU on a System. A “Virtual Guest” is an instance of the Software that is executed or installed on a System that is a virtual machine. When you deploy a guest operating system in a virtualized environment, you are responsible for securing the required license rights for any third party operating systems or other software that you use. Une « paire de socket » contient jusqu'à deux sockets, chacune occupée par un processeur (CPU) sur un Système. Un « Invité Virtuel » est une instance du Logiciel qui est exécutée ou installée sur un système qui est une machine virtuelle. Lorsque vous déployez un système d’exploitation invité dans un environnement virtualisé, il est de votre responsabilité d’obtenir les droits de licence requis de tout système d’exploitation tiers ou autre logiciel que vous utilisez.

Related to Unité de Mesure et Spécifications

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Classification Specifications The Employer agrees to supply the President of the Union or his/her designate with the classification specifications for those classifications in the Bargaining Unit.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Class Specifications The Human Resources Division shall determine:

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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