Common use of Software Subscription Support Level Unit of Measure Capacity Stackable Clause in Contracts

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform Standard or Premium 16 Virtual Guests on 2 Cores or Physical Node Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform xPaaS Standard or Premium 16 Virtual Guests on 2 Cores or Physical Node Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform xPaaS Standard or Premium 16 Virtual Guests on 2 Cores or Physical Node Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.. Tabelle 1.5.1

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform xPaaS Standard or Premium 16 Virtual Guests on 2 Cores or Physical Node Socket-pair Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform Standard or Premium 16 Virtual Guests on 2 Cores or Physical Node Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.. Tabelle 1.5.1

Software Subscription Support Level Unit of Measure Capacity Stackable. Red Hat JBoss Middleware for OpenShift Container Platform xPaaS Standard or Premium 16 Virtual Guests Guest on 2 Cores or Physical Node Socket-pair Cores: Yes Physical Node: Yes A “Socket-pair” is up to two sockets each occupied by a CPU on the Physical Node. A “Core” is (a) a physical processing core located in a CPU or (b) a virtual processing core within a virtual machine, in each case, that contains or executes the Software running for Production Purposes or Development Purposes.