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
# Use this to enble / disable dynamic dns updates globally.
#ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.10 192.168.0.30;
option domain-name-servers 192.168.0.2; # DNS DHCP Virtual Machine
option domain-name "rhcf.lab";
option routers 192.168.0.1;
option broadcast-address 192.168.0.255;
default-lease-time 600;
max-lease-time 7200;
next-server 192.168.0.3; # Satellite Server
filename = "pxelinux.0";
}
host X {
hardware ethernet 0:0:c0:5d:bd:95;
fixed-address 192.168.50.1
server-name "rhevm-vm";
}
# Continue adding hosts
Multipath.conf File (Changes are in bold):
# This is a basic configuration file with some examples, for device mapper
# multipath.
# For a complete list of the default configuration values, see
# /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.defaults
# For a list of configuration options with descriptions, see
# /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.annotated
## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
#blacklist_exceptions {
# device {
# vendor "IBM"
www.redhat.com 112