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

# product "S/390.*"
# }
#}
## Use user friendly names, instead of using WWIDs as names.
defaults {
user_friendly_names no
}
##
## Here is an example of how to configure some standard options.
##
#
#defaults {
# udev_dir /dev
# polling_interval 10
# selector "round-robin 0"
# path_grouping_policy multibus
# getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
# prio alua
# path_checker readsector0
# rr_min_io 100
# max_fds 8192
# rr_weight priorities
# failback immediate
# no_path_retry fail
# user_friendly_names yes
#}
##
## The wwid line in the following blacklist section is shown as an example
## of how to blacklist devices by wwid. The 2 devnode lines are the
## compiled in default blacklist. If you want to blacklist entire types
## of devices, such as all scsi devices, you should use a devnode line.
## However, if you want to blacklist specific devices, you should use
## a wwid line. Since there is no guarantee that a specific device will
## not change names on reboot (from /dev/sda to /dev/sdb for example)
## devnode lines are not recommended for blacklisting specific devices.
##
#blacklist {
# wwid 26353900f02796769
# devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
# devnode "^hd[a-z]"
#}
multipaths {
# multipath {
# wwid 3600508b4000156d700012000000b0000
# alias yellow
# path_grouping_policy multibus
# path_checker readsector0
113
www.redhat.com










