Open Shift Subscription Guide
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 14
| Download | |
| Open PDF In Browser | View PDF |
TECHNOLOGY DETAIL RED HAT OPENSHIFT SUBSCRIPTION AND SIZING GUIDE TABLE OF CONTENTS INTRODUCTION..................................................................................................................... 2 RED HAT OPENSHIFT SUBSCRIPTION OFFERINGS......................................................... 2 RED HAT OPENSHIFT CONTAINER PLATFORM................................................................. 2 Subscription components........................................................................................................................... 2 Subscription types......................................................................................................................................... 3 Disaster recovery.......................................................................................................................................... 3 Cores versus vCPUs and hyperthreading.............................................................................................. 4 Splitting cores................................................................................................................................................. 4 OpenShift Container Platform environments....................................................................................... 4 ADDITIONAL RED HAT PRODUCTS FOR USE WITH OPENSHIFT.................................... 5 RED HAT CONSULTING OPENSHIFT OFFERINGS............................................................. 6 RED HAT TRAINING OPENSHIFT OFFERINGS................................................................... 6 RED HAT TECHNICAL ACCOUNT MANAGEMENT SERVICES............................................7 RED HAT OPENSHIFT DEDICATED.......................................................................................7 OpenShift Dedicated Base Package........................................................................................................ 7 Additional resources and products.......................................................................................................... 8 SUGGESTED INITIAL OPENSHIFT DEPLOYMENT............................................................. 9 RED HAT OPENSHIFT CONTAINER PLATFORM SIZING................................................... 9 Infrastructure nodes and masters........................................................................................................... 9 Cores and vCPUs........................................................................................................................................... 10 Sizing process................................................................................................................................................ 10 Step 1: Determine standard VM or hardware cores and memory.......................................... 11 Step 2: Calculate the number of application instances needed............................................ 11 Step 3: Determine preferred maximum OpenShift node utilization..................................... 11 Step 4: Determine the total memory footprint...........................................................................12 facebook.com/redhatinc @RedHat linkedin.com/company/red-hat Step 5: Calculate totals.......................................................................................................................12 RED HAT JBOSS MIDDLEWARE INTEGRATION.................................................................14 Portability....................................................................................................................................................... 14 redhat.com Partial coverage............................................................................................................................................ 14 Developer access.......................................................................................................................................... 14 INTRODUCTION This document describes the subscription model for Red Hat ® OpenShift ® Container Platform and provides easy-to-follow, step-by-step instructions for how to approximate the size of an OpenShift environment. More specific sizing information is available on request. RED HAT OPENSHIFT SUBSCRIPTION OFFERINGS Red Hat OpenShift Online: Multitenant OpenShift environment hosted by Red Hat. Red Hat OpenShift Dedicated: Single-tenant OpenShift environment hosted by Red Hat. Customers work with Red Hat to determine requirements and integrations, and Red Hat implements and maintains the environment. Red Hat OpenShift Container Platform: OpenShift environment that is implemented and maintained by the customer. Red Hat OpenShift Container Lab: Sales promotional program for first-time OpenShift Container Platform customers for nonproduction workloads. Red Hat Container Development Kit (CDK): No-cost, local development virtual machine (VM) offered as part of the Red Hat Developer Program. Includes a full installation of OpenShift Container Platform. Red Hat Cloud Suite: Comprehensive integrated solution that provides a complete cloud infrastructure, including Red Hat OpenShift Container Platform. For more information, visit redhat.com/en/technologies/cloud-computing/cloud-suite. RED HAT OPENSHIFT CONTAINER PLATFORM Subscription components 1. 2. Red Hat Enterprise Linux®/Red Hat Enterprise Linux Atomic Host Each OpenShift subscription includes Red Hat Enterprise Linux/Red Hat Enterprise Linux Atomic Host entitlements.1 Red Hat OpenShift Container Platform Each subscription includes entitlements for OpenShift and its integrated components, including the following integrated solutions: • Log aggregation Aggregates container logs and platform logs using Elasticsearch, Fluentd, and Kibana • Metrics aggregation Aggregates container performance metrics — memory use, central processing unit (CPU) use, network throughput — using Heapster, Cassandra, and Hawkular These solutions are supported only in their native integrations with OpenShift, with limited support for customization. These solutions are not supported for general use outside of OpenShift. If you wish to use them outside of OpenShift, several third-party providers support these open source projects. 1 Customers with existing, excess entitlements may want to consider Red Hat OpenShift Container Platform for Red Hat Enterprise Linux as an alternative. This offering, available at a slightly lower cost, does not include Red Hat Enterprise Linux/Red Hat Enterprise Linux Atomic Host entitlements. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 2 3. Red Hat Software Collections OpenShift lets you use the container images provided in Red Hat Software Collections. These images include popular languages and runtimes — such as PHP, Python, Perl, Node.js, and Ruby — as well as databases, such as MySQL, MariaDB, MongoDB, and Redis. This offering also includes an OpenJDK image for JavaTM frameworks, such as Spring Boot. For more information, read the technology brief at redhat.com/en/resources/red-hat-software-collections. 4. Red Hat JBoss® Web Server OpenShift subscriptions include Red Hat JBoss Web Server, an enterprise solution that combines the Apache web server with the Apache Tomcat servlet engine, supported by Red Hat. OpenShift includes an unlimited right to use JBoss Web Server. Learn more at redhat.com/en/technologies/jboss-middleware/web-server. 5. Single sign-on (SSO) Red Hat provides Web SSO and identity federation based on Security Assertion Markup Language (SAML) 2.0, OpenID Connect, and Open Authorization (OAuth) 2.0 specifications. This capability, included in OpenShift subscriptions, may only be deployed inside OpenShift environments. However, any application — whether deployed inside or outside of OpenShift — may use Red Hat’s SSO. 6. Red Hat CloudForms® Red Hat CloudForms provides capacity, trending, showback, security enforcement, and other capabilities for OpenShift. CloudForms entitlements are included in OpenShift subscriptions. However, the right to use is limited to management of and visibility into the OpenShift environment and its underlying hosts and infrastructure. For more details on the limited acceptable uses of the included CloudForms, refer to the Red Hat OpenShift FAQ for included Red Hat CloudForms at https://pnt.redhat.com/pnt/p-6562043/openshift-clo...-jul-2017.pdf. Subscription types There is one base subscription for OpenShift Container Platform. The OpenShift Container Platform, 2 Core subscription is based on the number of logical cores on the CPUs in the system where OpenShift runs. As with Red Hat Enterprise Linux: • OpenShift Container Platform subscriptions are stackable to cover larger hosts. • Cores can be distributed across as many VMs as needed. For example, 10 2-core subscriptions will provide 20 cores that can be used across any number of VMs. OpenShift Container Platform subscriptions are available with Premium or Standard support. Disaster recovery OpenShift does not offer disaster recovery (DR), cold backup, or other subscription types. Any system with OpenShift installed, powered-on or powered-off, running workload or not, requires an active subscription. See the section titled Infrastructure nodes and masters to understand more about subscription requirements. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 3 Cores versus vCPUs and hyperthreading Making a determination about whether a particular system consumes 1 or more cores is currently dependent on whether that system has hyperthreading available. Note that hyperthreading is only a feature of Intel CPUs. To determine whether a particular system supports hyperthreading, visit https://access.redhat.com/solutions/7714. For systems where hyperthreading is enabled and where 1 hyperthread equates to 1 visible system core, then a calculation of cores at a ratio of 2 cores = 4 vCPUs is used. In other words, a 2-core subscription covers 4 vCPUs in a hyperthreaded system. A large VM might have 8 vCPUs, equating to 4 subscription cores. As subscriptions come in 2-core units, you would need two 2-core subscriptions to cover these 4 cores or 8 vCPUs. Where hyperthreading is not enabled, and where each visible system core correlates directly to an underlying physical core, a calculation of 2 cores = 2 vCPUs is used. Splitting cores Systems that require an odd number of cores will need to consume a full 2-core subscription. For example, a system that is calculated to require only 1 core will end up consuming a full 2-core subscription once it is registered and subscribed. When a single VM with 2 vCPUs uses hyperthreading (see prior section), resulting in 1 calculated vCPU, a full 2-core subscription is required for that VM. A single 2-core subscription may not be split across two similar VMs using hyperthreading. It is recommended that virtual instances be sized so that they require an even number of cores. OpenShift Container Platform environments OpenShift Container Platform can be used anywhere that 64-bit x86 Red Hat Enterprise Linux or Red Hat Enterprise Linux Atomic Host are certified and supported. For on-premise deployments, OpenShift can be installed on: • Bare metal. • Virtualized environments, including: • VMware. • Microsoft Hyper-V. • Red Hat Virtualization. • Private clouds, including Red Hat OpenStack® Platform. OpenShift also can be installed and used on any Red Hat Enterprise Linux-certified public cloud, such as: • Amazon Web Services (AWS). • Google Cloud Platform (GCP). • Microsoft Azure. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 4 Registration for Red Hat Cloud Access is required to use your OpenShift subscriptions on certified public clouds. For more information, visit redhat.com/en/technologies/cloud-computing/cloud-access. For more information on platforms and clouds that OpenShift has been tested and certified on, refer to OpenShift Container Platform Tested Integrations at https://access.redhat.com/articles/2176281. ADDITIONAL RED HAT PRODUCTS FOR USE WITH OPENSHIFT Many of Red Hat’s middleware, storage, and management offerings may be purchased for use with OpenShift. Some middleware offerings are also available as curated bundles for use with OpenShift. These solutions include: • Container registry • Red Hat Quay2 • Middleware: • Red Hat JBoss Enterprise Application Platform (EAP) • Red Hat Data Grid • Red Hat JBoss Data Virtualization • Red Hat AMQ • Red Hat Decision Manager • Red Hat Process Automation Manager • Red Hat Fuse • Red Hat OpenShift Application Runtimes2 • Red Hat Mobile Application Platform2 • Red Hat 3scale API Management2 • Storage: • Red Hat OpenShift Container Storage2 • Management: • Red Hat CloudForms 2 Not currently available for use with Red Hat OpenShift Dedicated redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 5 RED HAT CONSULTING OPENSHIFT OFFERINGS Red Hat has an extensive catalog of consulting offerings, ranging from initial software deployment to complete programs that support your organization’s digital transformation journey. • Red Hat Consulting Discovery Session: No-cost Discovery Sessions create open discussion on how an organization can adopt OpenShift, take advantage of DevOps practices, and establish innovative application development. Discovery Sessions are designed to produce a summary report presenting the focus areas discussed, scope and priority information, and a proposed approach for continuing to work with Red Hat Consulting to increase adoption. • OpenShift Container Platform pilot: This eight-week, extended introductory services engagement puts organizations on a path to modernizing application delivery through efficient use of container and container orchestration technologies. • Container adoption program: This comprehensive program supports enterprise-scale container adoption, including establishing container platform infrastructure, deployment pipeline automation, and mass migration of applications to containers. The program begins with a pilot offering and incorporates Red Hat Open Innovation Labs to support faster innovation and time to market. • Red Hat Open Innovation Labs: In this immersive experience program, customers visit Red Hat’s labs to experiment, become more agile, learn DevOps practices, and catalyze innovation alongside Red Hat experts. Learn more at redhat.com/en/open-innovation-labs. RED HAT TRAINING OPENSHIFT OFFERINGS Red Hat Training courses can help you and your staff quickly become familiar with OpenShift and related technologies. Red Hat offers a variety of ways to access training — from no-cost online webinars available on demand to scheduled training held on-premises at your location. Paid, instructor-led training: • Introduction to containers, Kubernetes, and Red Hat OpenShift (DO180) • Red Hat OpenShift Administration I (DO280) • Red Hat OpenShift Administration II (DO380) • Red Hat OpenShift Development I: Containerizing Applications (DO288) • Red Hat OpenShift Development II: Creating Microservices with Red Hat OpenShift Application Runtimes (DO292) No-cost, self-paced training: • Deploying containerized applications technical overview (DO080) • Red Hat OpenShift Interactive Learning Portal: https://learn.openshift.com redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 6 RED HAT TECHNICAL ACCOUNT MANAGEMENT SERVICES Red Hat offers Technical Account Management services to support your organization’s adoption, deployment, and management of Red Hat technologies. Red Hat Technical Account Managers (TAMs) are highly technical product specialists who partner with your organization. Your TAM will develop a personal relationship with you to understand your unique business needs, strategically plan deployments, and assist with faster issue resolution. Your TAM is your advocate at Red Hat. With a direct line to the Red Hat engineering organization, you can impact product feature requests and updates. TAMs work with Red Hat Product Security, providing you with proactive notifications and resolutions for critical security issues. They also organize multivendor collaboration to solve technical issues. TAMs deliver new information and insight to influence your IT strategy and how you manage risk, reliability, and security. Your TAM is there to help your organization evolve and succeed. RED HAT OPENSHIFT DEDICATED Red Hat OpenShift Dedicated provides one or more single-tenant, high-availability OpenShift clusters delivered as a public cloud service. OpenShift Dedicated clusters are managed by Red Hat OpenShift operations experts, who use years of experience to increase security while providing a streamlined path to use OpenShift in public cloud environments. As is the case with OpenShift Container Platform, the right number of application nodes for OpenShift Dedicated depends on the size of applications — their memory footprint — and the total number of application instances. Note that application node size and capacity are fixed. See the sizing section of this document for examples. OpenShift Dedicated Base Package The OpenShift Dedicated Base Package is the smallest environment available. It provides an entire OpenShift cluster that is implemented and maintained by Red Hat — and, optionally, securely connected to your internal network. There is a choice of public cloud providers and hosting regions. Currently, OpenShift Dedicated is available on AWS and GCP. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 7 TABLE 1. RED HAT OPENSHIFT DEDICATED BASE PACKAGE OVERVIEW ITEM AMOUNT/TYPE DESCRIPTION Base platform -- Includes 3 x multimaster high-availability (HA) VMs and 2 x infrastructure nodes for OpenShift’s containerized components Application nodes 4 Each application node includes 4 vCPUs and 16GB of memory. Network input/output (I/O) 48TB Each application node includes 12TB of network I/O per year. A total of 48TB (4 x 12TB) is included. Persistent storage 100GB High-speed solid-state drive (SSD) persistent storage for application use Support Premium Red Hat Premium Support, which includes 24x7 coverage Additional resources and products Application nodes, persistent storage, and network I/O can be added to OpenShift Dedicated to expand the capacity of the cluster as needed. Other Red Hat middleware products can also be added to an OpenShift Dedicated environment (Table 2). TABLE 2. RED HAT OPENSHIFT DEDICATED ADD-ONS redhat.com ITEM AMOUNT DESCRIPTION Application node 1 Adds memory and compute resources. Each application node includes 12TB of network I/O per year. Network I/O 12TB Additional network I/O for data transfer Persistent storage 500GB Additional persistent storage Red Hat JBoss EAP 1 year Red Hat JBoss EAP subscription covering 1 node with Premium support Red Hat Fuse 1 year Red Hat Fuse subscription covering 1 node with Premium support Red Hat AMQ 1 year Red Hat AMQ subscription covering 1 node with Premium support Red Hat Decision Manager 1 year Red Hat Decision Manager subscription covering 1 node with Premium support Red Hat Process Automation Manager 1 year Red Hat Process Automation Manager subscription covering 1 node with Premium support Red Hat Data Grid 1 year Red Hat Data Grid subscription covering 1 node with Premium support Red Hat JBoss Data Virtualization 1 year Red Hat JBoss Data Virtualization covering 1 node with Premium support TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 8 SUGGESTED INITIAL OPENSHIFT DEPLOYMENT The following suggested bill of materials provides an extremely flexible, scalable OpenShift environment to run in VMs and support hundreds of application containers: • 16 x OpenShift Container Platform, 2-Core Premium subscriptions, including: • Multimaster HA (3 VMs). • Redundant infrastructure nodes (2 VMs). • Application nodes (16 VMs). • 2 x Red Hat OpenShift Container Storage: Adds scalable block and file storage for applications inside OpenShift. • 16 x Red Hat JBoss Enterprise Application Platform for OpenShift Container Platform, 2-Core Premium service: Adds support for Java EE applications on OpenShift. RED HAT OPENSHIFT CONTAINER PLATFORM SIZING To conduct a more thorough sizing exercise to determine how many OpenShift Container Platform or add-on subscriptions you need, use the following questions and examples. A few basic OpenShift terms are used in these sizing exercises: • Pod: The deployed unit in OpenShift. A running instance of an application — for example, an app server or database. • Application instance: Effectively the same as a pod and used interchangeably. • Node: Instances of Red Hat Enterprise Linux or Red Hat Enterprise Linux Atomic Host where pods run. OpenShift environments can have many nodes. • Masters: Instances of Red Hat Enterprise Linux or Red Hat Enterprise Linux Atomic Host that act as the orchestration or management layer for OpenShift. Masters are included in OpenShift Container Platform subscriptions. See the Infrastructure nodes and masters section for more details. • Infrastructure nodes: Instances of Red Hat Enterprise Linux or Red Hat Enterprise Linux Atomic Host that are running pods supporting OpenShift’s infrastructure. Infrastructure nodes are included in OpenShift Container Platform subscriptions. See the IInfrastructure nodes and masters section for more details. • Cluster: A group of OpenShift masters and nodes. In summary: • Applications are packaged in container images. • Containers are grouped in pods. • Pods run on nodes, which are managed by masters. Infrastructure nodes and masters Each OpenShift Container Platform subscription provides extra entitlements for OpenShift, Red Hat Enterprise Linux, and other OpenShift-related components. These extra entitlements are included for the purpose of running either OpenShift Container Platform masters or infrastructure nodes. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 9 INFRASTRUCTURE NODES To qualify as an infrastructure node and use the included entitlement, only the following included OpenShift components may be run as application instances: • Registry • Router • Metrics aggregation • Logging aggregation • Red Hat CloudForms • Red Hat OpenShift Container Storage No other application instances or types may be run on an infrastructure node using the included entitlement. To run other infrastructure workloads as application instances on an OpenShift node, you must run those instances on regular application nodes. MASTERS Masters generally are not used as nodes and, by default, will not run application instances. However, you could use a master as a functional node. Whether a master requires a full OpenShift Container Platform subscription depends on the application instances it runs. See the Infrastructure nodes section above. Cores and vCPUs Because of the way that Red Hat Enterprise Linux recognizes CPUs — and due to how modern CPUs work — it often appears that there are twice as many CPUs present. Because of this effect and how virtualization works, Red Hat implements a 2:1 mapping of subscription cores to vCPUs. In the case of a VM — whether in a public cloud, private cloud, or local virtualized environment — 1 subscription core would cover 2 vCPUs. In other words, if a VM has 4 vCPUs assigned, a 2-core subscription would be required. Sizing process OpenShift subscriptions do not limit application instances. You can run as many application instances in the OpenShift environment as the underlying hardware and infrastructure will support. Larger-capacity hardware can run many application instances on a small number of hosts, while smaller-capacity hardware will require many hosts to run many application instances. The primary factor in determining the size of an OpenShift environment is how many pods, or application instances, will be running at any given time. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 10 STEP 1: DETERMINE STANDARD VM OR HARDWARE CORES AND MEMORY You may have a standard VM size for application instances or, if you typically deploy on bare metal, a standard server configuration. The following questions will help you more accurately understand your VM and hardware needs. Remember that in most cases, 2 vCPUs is equivalent to 1 core. TABLE 3. VM AND HARDWARE SIZING QUESTIONS RELEVANT QUESTIONS EXAMPLE ANSWERS What is the memory capacity of the VMs you will use for nodes? Our VMs have 64GB of memory. What is the number of vCPUs for the VMs you will use for nodes? We will use 4 vCPUs for the nodes. Is hyperthreading in use? Yes. STEP 2: CALCULATE THE NUMBER OF APPLICATION INSTANCES NEEDED Next, determine how many application instances, or pods, you plan to deploy. When sizing the environment, any application component deployed on OpenShift — such as a database, front-end static server, or message broker instance — is considered an application instance. This figure can simply be an approximation to help you calculate a gross estimate of your OpenShift environment size. CPU, memory oversubscription, quotas and limits, and other features can be used to further refine this estimate. TABLE 4. OPENSHIFT APPLICATION INSTANCE ESTIMATE QUESTIONS RELEVANT QUESTIONS EXAMPLE ANSWERS How many application instances do you anticipate deploying in each OpenShift environment? We have around 1,250 application instances in our development environment and around 250 application instances in production. What type of applications are they (e.g., language, framework, database)? We mainly deploy Java but have some Microsoft .NET Core and Ruby applications as well. We also use a lot of MySQL. STEP 3: DETERMINE PREFERRED MAXIMUM OPENSHIFT NODE UTILIZATION We recommend reserving some space in case of increased demand, especially if autoscaling is enabled for workloads. Your preferred utilization will vary, based on historical load for the applications that will run on OpenShift. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 11 TABLE 5. OPENSHIFT NODE UTILIZATION QUESTIONS RELEVANT QUESTION EXAMPLE ANSWER How much space do you want to reserve for increased demand? We want to run nodes at a maximum average of 80% of total capacity (leaving 20% in reserve). STEP 4: DETERMINE THE TOTAL MEMORY FOOTPRINT Next, calculate the total memory footprint of the deployed applications. If you are considering a completely greenfield environment, memory use data might not be available. But you can use educated approximations — for example, 1GB of memory per Java application instance — to make an estimate. TABLE 6. OPENSHIFT MEMORY FOOTPRINT QUESTIONS RELEVANT QUESTION EXAMPLE ANSWERS What is the average memory footprint of applications? Our application instances use 2GB of memory or less. OR We typically allocate 2 GB for Java Virtual Machine (JVM) heap. STEP 5: CALCULATE TOTALS Finally, determine the number of OpenShift subscriptions needed based on the data gathered in steps 1-4. • Effective per-node memory capacity (GB) = Preferred maximum OpenShift node utilization * Standard VM or hardware memory • Total memory utilization = Application instances * Average application memory footprint • Number of nodes required to cover utilization = Total memory utilization / Standard VM or hardware memory cores • Total required cores = Number of nodes required to cover utilization * Standard VM or hardware cores • Effective virtual cores = total required cores / 2 • Number of OpenShift Container Platform subscriptions3 = Total cores / 2 OR = Effective virtual cores / 2 3 If hyperthreading is in use, 2 virtual cores count as only 1 core of a subscription. See the section titled Cores versus vCPUs and hyperthreading for details on whether to use effective or actual cores in this calculation. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 12 Example calculation for virtualized environments: System sizing (from steps 1-6, above) • Standard number of VM cores = 4 (hyperthreading used, 2 effective virtual cores) • Standard VM memory = 64GB • Preferred maximum node utilization = 80% • Average application memory footprint = 2GB • Number of application instances = 1500 Subscription calculations • Effective node memory capacity = 80% preferred maximum node utilization * 64GB standard VM memory = 51GB • Total memory utilization = 1500 application instances * 2GB average application memory footprint = 3000GB • Nodes required to cover utilization = 3000GB total memory utilization / 51GB effective node memory capacity = 59 nodes • Total cores = 59 nodes required * 2 cores per node = 118 total cores • Total subscriptions = 118 total cores / 2 cores per subscription = 59 subscriptions In this example, 59 2-core OpenShift Container Platform subscriptions would be needed. Note: OpenShift supports many scalability, overcommitment, idling, and resource quota or limiting features. The calculations above are guidelines, and you might be able to tune your actual environment for better resource use and smaller total environment size. redhat.com TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide 13 TECHNOLOGY DETAIL Red Hat OpenShift subscription and sizing guide RED HAT JBOSS MIDDLEWARE INTEGRATION Portability Red Hat JBoss Middleware subscriptions not specifically designed for OpenShift may be used in OpenShift environments or across OpenShift and non-OpenShift environments. If you have existing JBoss Middleware subscriptions, you can use them in OpenShift without having to purchase OpenShift-specific subscriptions. If you purchase OpenShift-specific JBoss Middleware subscriptions, you may use them outside of OpenShift. All cases are valid with correct core or socket accounting. For more details on JBoss Middleware portability, refer to Section 1.5.2 of the Red Hat Global Subscription Services Appendix, Appendix 1 of the Enterprise Agreement, available at redhat.com/en/about/licenses. Partial coverage You are not required to provide middleware subscription coverage for an entire OpenShift Container Platform environment. Platform administrators can work to ensure that the middleware workload runs only on the correct, subscribed hosts inside your OpenShift environment. Developer access OpenShift does not have a developer access model for JBoss Middleware products. Customers who wish to use Red Hat JBoss Middleware products on OpenShift must purchase subscriptions, regardless of whether the use is for development, test, or production environments. ABOUT RED HAT Red Hat is the world’s leading provider of open source software solutions, using a communitypowered approach to provide reliable and high-performing cloud, Linux, middleware, storage, and virtualization technologies. Red Hat also offers award-winning support, training, and consulting services. As a connective hub in a global network of enterprises, partners, and open source communities, Red Hat helps create relevant, innovative technologies that liberate resources for growth and prepare customers for the future of IT. facebook.com/redhatinc @RedHat linkedin.com/company/red-hat redhat.com f13893_0818 NORTH AMERICA 1 888 REDHAT1 EUROPE, MIDDLE EAST, AND AFRICA 00800 7334 2835 europe@redhat.com ASIA PACIFIC +65 6490 4200 apac@redhat.com LATIN AMERICA +54 11 4329 7300 info-latam@redhat.com Copyright © 2018 Red Hat, Inc. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. The OpenStack® Word Mark and OpenStack Logo are either registered trademarks / service marks or trademarks / service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation or the OpenStack community.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.7 Linearized : Yes Language : en-US XMP Toolkit : Adobe XMP Core 5.6-c143 79.161210, 2017/08/11-10:28:36 Create Date : 2018:08:31 14:06:43-04:00 Metadata Date : 2018:08:31 14:06:46-04:00 Modify Date : 2018:08:31 14:06:46-04:00 Creator Tool : Adobe InDesign CC 13.0 (Macintosh) Instance ID : uuid:464657a3-fd7a-9b40-b6f3-d96b748206a1 Original Document ID : xmp.did:FA7F11740720681197A5A4B46E65AE7B Document ID : xmp.id:8478c3f2-8e8e-401d-a99d-d776a8f9f988 Rendition Class : proof:pdf Derived From Instance ID : xmp.iid:1a29372b-7c71-4987-8636-06cee63e3ea7 Derived From Document ID : xmp.did:218a2451-f288-492c-93c0-4086a23256e0 Derived From Original Document ID: xmp.did:FA7F11740720681197A5A4B46E65AE7B Derived From Rendition Class : default History Action : converted History Parameters : from application/x-indesign to application/pdf History Software Agent : Adobe InDesign CC 13.0 (Macintosh) History Changed : / History When : 2018:08:31 14:06:43-04:00 Format : application/pdf Producer : Adobe PDF Library 15.0 Trapped : False Page Count : 14 Creator : Adobe InDesign CC 13.0 (Macintosh)EXIF Metadata provided by EXIF.tools