Specifications
Table Of Contents
- 1 Executive Summary
- 2 Cloud Computing Standards
- 3 Red Hat and Cloud Computing
- 4 Red Hat Cloud Foundations Components
- 5 RHCF Proof of Concept Configuration
- 6 Deploying Red Hat Cloud Foundations – Infrastructure Services
- 6.1 Overview
- 6.2 This section moves into the details of what needs to happen to deploy this infrastructure. At a high level, the steps that need to be accomplished.
- 6.3 Download Software
- 6.4 Deploy mgmt1 and Configure
- 6.5 Deploy Satellite Virtual Machine and Install Satellite
- 6.6 Create Kickstart Profiles and Activation Keys
- 6.7 Deploy DHCP / DNS Virtual Machine
- 6.8 Deploy Red Hat Enterprise Virtualization Platform
- 6.9 Deploy the Red Hat Enterprise Virtualization Hypervisor
- 6.10 Deploy the RHEL KVM Hypervisor
- 6.11 Add the RHEV KVM Hypervisor in RHEV-M
- 6.12 Configure RHEV Datacenter, Cluster, and Storage Domain
- 6.13 Configure ISO Domain
- 7 Deploy Tenant Virtual Machines
- 8 Configure High Availability Environment
- 9 Deploy and Scale Applications
- 9.1 Deploy Java Application
- 9.1.1 Configure GPG and Sign the javaApp package
- 9.1.2 Set up Software Channel on Satellite Server
- 9.1.3 Upload Application
- 9.1.4 Create RHN Activation Key for Custom Channel
- 9.1.5 Create a New Kickstart Profile
- 9.1.6 Deploy Virtual Machine with javaApp via PXE
- 9.1.7 Create a Template from the javaApp Virtual Machine
- 9.1.8 Scale the javaApp Virtual Machine
- 9.2 Deploy and Scale JBoss EAP Application
- 9.3 Deploy JBoss Enterprise Application Platform
- 9.4 Deploy and Scale Applications – MRG Manager
- 9.1 Deploy Java Application
- 10 Summary
- 11 Appendix A
- 12 Appendix B Scripts
premise or off-premises. By utilizing a private cloud service model an organization is able to
take advantage of the elasticity and cost effectiveness of cloud technologies as well as
maintain complete control of the infrastructure. See Figure 2.2: Private Cloud for an
example of a private cloud model.
A hybrid cloud provides infrastructure that is a composition of two or more clouds (private,
community, or public) that remain unique entities but are bound together by standardized or
proprietary technology that enables data and application portability (e.g., cloud bursting or
load balancing between clouds). One possible usage model for a hybrid cloud would be to
host all services on the private cloud until those resources became exhausted. At that point,
the resources on the private cloud could scale to the third-party public cloud provider until the
high utilization reduces to a point where the resources could be brought back in-house. See
Figure 2.3: Hybrid Cloud for a hybrid cloud example.
9 www.redhat.com
Figure 2.2: Private Cloud