Red Hat Enterprise Linux Server Sample Clauses

Red Hat Enterprise Linux Server. Atomic Host. Red Hat Enterprise Linux Server may be deployed in Atomic Host mode. Atomic Host mode is an optional delivery, deployment and updating mechanism designed to support container based environments. At installation, you may elect to install Red Hat Enterprise Linux Server via (a) the RPM package manager based methodology or (b) the Atomic host layered image methodology for container based applications. Each deployment of Red Hat Enterprise Linux, regardless of the method, constitutes a Unit.
AutoNDA by SimpleDocs
Red Hat Enterprise Linux Server. ࢔ࢻ࢜ࣥ Red Hat Enterprise Linux ServerŒサӲࢫPj?ࢩࣙࣥࡣࠊ 1 ࡘࡲ½ࡣ」ᩘŒ࢔ࢻ࢜ࣥ࢜?ࢩࣙࣥ(ࠕ࢔ࢻ࢜ࣥ])௜ࡁ ࡛㉎ධ࡛ࡁࡲࡍ。 ࢔ࢻ࢜ࣥࡣࠊࡑŒࡼỹ࡞࢔ࢻ࢜ࣥÇ$㛤 ࠊイࣥࢫࢺ—Ыࠊ౑⏝ࠊࡲ½ࡣᐇ⾜ࡍࡿlࢽjࢺࡈ࡜࡟ู ಶŒ᭷ᩱ࠾ࡼࡧ࢔Pȳ࢕Ӳ࡞/ࣇࢺ࢘±࢔ サӲࢫPj?ࢩ ࣙࣥÇᚲせ࡜ࡋࡲࡍ。࢔ࢻ࢜ࣥ࡟ࡘ࠸ZŒྛCŒlࢽjࢺ
Red Hat Enterprise Linux Server. Opciones agregadas Las Suscripciones de Red Hat Enterprise Linux Server se pueden comprar con una o más opciones agregadas (“Opciones agregadas”). Las opciones agregadas incluyen: High Availability (alta disponibilidad), Load Balancer (equilibrio xx xxxxxx), Resilient Storage (almacenamiento resistente), Scalable File System (sistema de archivos escalable), Smart Management (gestión inteligente, requiere de RHN Satellite), Extended Update Support (asistencia ampliada de actualizaciones) y High Performance Network (red de alto desempeño).
Red Hat Enterprise Linux Server. 㾱≲ Ⲵ䇑䟿অս4䍝Ҡ 䍥ᯩ‰享᤹➗лQ 1 ᡰtⲴᇩ䟿,Ѫ Red Hat Enterprise Linux Server(वᤜ Red Hat Enterprise Linux Server for HPC Compute NodesǃRed Hat Enterprise Linux for IBM power ৺ Red Hat Enterprise Linux for SAP Applications ㅹਈර)Ⲵ਴ њঅս䍝Ҡ⴨ᓄᮠ䟿4㊫රⲴfiԦ䇒䰵˚Ѫ䗮ࡠ㔉ᇊঅսⲴᇩ䟿㾱≲,4ึਐfiњfiԦ䇒䰵,ਇࡦҾ⢩ᇊⲴ䲀ࡦ(㿱л⌘ 1)˚ “ึਐ”(ᡆ“4ึਐ”)ᱟᤷ䙊䗷ᓄ⭘fiњ⴨਼Ⲵ䇒䰵ᶕᇎ⧠䱴࣐ ᇩ䟿˚ 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 (see Note 1 below) Standard or Premium Physical Node or Virtual Node Socket-pair for each Physical Node or 2 Virtual Nodes Physical Node: Yes Virtual Node: Yes Red Hat Enterprise Linux for Virtual Datacenters (see Note 2 below) 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 Power Standard or Premium Power IFL Up to 4 processor cores N/A Power IFL: Yes Red Hat Enterprise Linux for System z Standard or Premium System z IFL N/A N/A System z IFL: Yes Red Hat Enterprise Linux for Hyperscale Standard Physical Node Band of SOCs None Physical Node: No Virtual Node: No Red Hat Enterprise Linux Server Entry Level (see Note 1 below) Self-support Physical Node Socket-pair None Physical Node: No Virtual Node: Yes Red Ha OpenStack Platform 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 (see Note 1 below) Premium Physical Node 1-2 Sockets, 9 Logical Partitions 4 Sockets, 10 Logical Partitions 6 Sockets 11 Logical Partitions or 8 Sockets 12 Logical Partitions Sockets: No Virtual Guest: Yes Red Hat Enterprise Linux for Premium System 1-2 Sockets, 4 Sockets, 1 Virtual Guest,4 Virtual Guests, or Sockets: No Virtual Guest: Yes PRIMEQUEST 6 Sockets or 8 Sockets Unlimited Virtual Guests Q fiԦ䇒䰵 @ᤱ㓗࡛ ⍻䟿অս ᇩ䟿 ᨂ‭ 㲊ᤏ;⛩ ᱟ੖4ึਐ Red Hat Enterprise Linux Serve(⢙⨶;⛩ᡆ 㲊ᤏ;⛩) Red Hat Enterprise Linux for SAP HANA (㿱л⌘ 1) ḷ߶ᡆ儈㓗 ⢙⨶;⛩ ᡆ 㲊ᤏ;⛩ ⇿њ⢙⨶;⛩ᡆ⇿єњ㲊ᤏ;⛩䝽༷—њ Socket-pair ⢙⨶;⛩:ᱟ 㲊ᤏ;⛩:ᱟ Red Hat Enterprise Linux for...
Red Hat Enterprise Linux Server. 䱴࣐࣏㜭 Red Hat Enterprise Linux Server 䇒䰵4ԕ䲿䱴䍝Ҡ—њᡆfi њ䱴࣐࣏㜭䘹亩(“䱴࣐࣏㜭”)˚䱴࣐࣏㜭䴰㾱䪸ሩ⇿њ䜘㖢ǃ z㻵ǃ֯⭘ᡆᢗ㹼䈕ㅹ䱴࣐࣏㜭Ⲵঅսঅ⤜@Ԉᴹ᭸ⲴfiԦ䇒䰵˚䱴࣐࣏㜭Ⲵ⇿њঅս:(i) ‰享оส⹰ Red Hat Enterprise Linux অսⲴ⍻䟿অս4ᇩ䟿⴨३䝽;ф (ii) 㧧ᗇส⹰ Red Hat Enterprise Linux অսⲴ@ᤱ㓗࡛(ḷ߶4/ᡆ儈㓗)˚䱴 ࣐࣏㜭н@ᤱᑖ㠚ࣙᴽ࣑≤ᒣⲴ Red Hat Enterprise Linux䇒䰵(Ც㜭㇑⨶䱴࣐࣏㜭䲔ཆ)˚䱴࣐࣏㜭वᤜ:儈4⭘ᙗǃ䍏䖭ᒣ㺑ಘǃᕩᙗᆈۘǃ4ᢙg@Ԧ㌫㔏ǃᲪ㜭㇑⨶ǃᔦᵏᴤ ᯠ@ᤱǃᔦᵏRભઘᵏ@ᤱ4Red Hat Insights˚
Red Hat Enterprise Linux Server. Atomic Hostࠋ Red Hat Enterprise Linux Serverª Atomic Host*—t½$㛤@£= ¥‰½€£@ࠋAtomic Host*—tª¸S?YuS4y”ࣂ” —¸$㛤¸7y?y—ࢺ4F9=EŁ½Øk¸*Sz7÷— ^4⎔ቃ€9࣏—ࢺ@££yタィ€¢€fi£@ࠋYS^ࢺ— 04àⒶᵝª¸Red Hat Enterprise Linux Server4YS^ࢺ —0€fif“G㑅ᢥ@£=¥‰½€£@ࠋ(a) RPM¾y9— s™fisÇ—÷—^4F“t¤s—¸£½ª (b)*Sz7÷ —^47?”9—YuS$ Atomic hostUYM—4YF—s 4F“t¤s—ࠋ Red Hat Enterprise Linux4ⓟ$㛤ª¸€ 4F‰‰Y4£y࡞¢4½Ø£“4““ðG¾¸~*4>= yࢺ€ᵓfi5£@ࠋ

Related to Red Hat Enterprise Linux Server

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • 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.

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • INDEPENDENT PERSONAL SERVICES 1. Income derived by a resident of a Contracting State in respect of professional services or other activities of an independent character shall be taxable only in that State except in the following circumstances, when such income may also be taxed in the other Contracting State:

  • DEPENDENT PERSONAL SERVICES 1. Subject to the provisions of Articles 16, 18 and 19, salaries, wages and other similar remuneration derived by a resident of a Contracting State in respect of an employment shall be taxable only in that State unless the employment is exercised in the other Contracting State. If the employment is so exercised, such remuneration as is derived therefrom may be taxed in that other State.

  • Independent Contractor; No Partnership; No Agency; No Utility Services 15.1 Company and Developer shall be independent contractors. This Agreement shall not be interpreted or construed to create an association, joint venture, agency relationship, or partnership between the Parties or to impose any partnership obligation or partnership liability upon any Party. No Party shall have any right, power or authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an agent or representative of, or to otherwise bind, the other Party. This Agreement is not an agreement to provide or take utility services of any kind, including, without limitation, interconnection or other electric transmission services.

  • Indiana Veteran’s Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran’s Business Enterprise (“IVBE”) participation plan. The following IVBE subcontractors will be participating in this Contract: VBE PHONE COMPANY NAME SCOPE OF PRODUCTS and/or SERVICES UTILIZATION DATE PERCENT _____________________________________________________________________________________ _____________________________________________________________________________________ A copy of each subcontractor agreement shall be submitted to IDOA within thirty (30) days of the request. Failure to provide any subcontractor agreement may also be considered a material breach of this Contract. The Contractor must obtain approval from IDOA before changing the IVBE participation plan submitted in connection with this Contract. The Contractor shall report payments made to IVBE subcontractors under this Contract on a monthly basis. Monthly reports shall be made using the online audit tool, commonly referred to as “Pay Audit.” IVBE subcontractor payments shall also be reported to IDOA as reasonably requested and in a format to be determined by IDOA.

  • Indiana Veteran Owned Small Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran Owned Small Business Enterprise (“IVOSB”) participation plan, as detailed in the IVOSB Subcontractor Commitment Form, commonly referred to as “Attachment A-1” in the procurement documentation and incorporated by reference herein. Therefore, any changes to this information during the Contract term must be approved by IDOA’s IVOSB Division (“IVOSB Division”) and may require an amendment. It is the State’s expectation that the Contractor will meet the subcontractor commitments during the Contract term. The following certified IVOSB subcontractor(s) will be participating in this Contract: [Add additional IVOSBs using the same format.] IVOSB COMPANY NAME PHONE EMAIL OF CONTACT PERSON PERCENT Briefly describe the IVOSB service(s)/product(s) to be provided under this Contract and include the estimated date(s) for utilization during the Contract term: A copy of each subcontractor agreement must be submitted to the IVOSB Division within thirty (30) days of the effective date of this Contract. The subcontractor agreements may be uploaded into Pay Audit (Indiana’s subcontractor payment auditing system), emailed to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx, or mailed to IDOA, 000 X. Xxxxxxxxxx Street, Room W-478, Indianapolis, IN 46204. Failure to provide a copy of any subcontractor agreement may be deemed a violation of the rules governing IVOSB procurement and may result in sanctions allowable under 25 IAC 9-5-2. Requests for changes must be submitted to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx for review and approval before changing the participation plan submitted in connection with this Contract. The Contractor shall report payments made to certified IVOSB subcontractors under this Contract on a monthly basis using Pay Audit. The Contractor shall notify subcontractors that they must confirm payments received from the Contractor in Pay Audit. The Pay Audit system can be accessed on the IDOA webpage at: xxx.xx.xxx/xxxx/xxxx/xxxxxxxx.xxx. The Contractor may also be required to report IVOSB certified subcontractor payments directly to the IVOSB Division, as reasonably requested and in the format required by the IVOSB Division. The Contractor’s failure to comply with the provisions in this clause may be considered a material breach of the Contract.

  • State Trading Enterprises The rights and obligations of the Parties in respect of state trading enterprises shall be governed by Article XVII of the GATT 1994 and the Understanding on the Interpretation of Article XVII of the GATT 1994, which are hereby incorporated into and made part of this Agreement.

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