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

#
#RHQ_AGENT_CMDLINE_OPTS="--daemon --nonative --cleanconfig"
RHQ_AGENT_CMDLINE_OPTS="--daemon --cleanconfig"
# RHQ_AGENT_IN_BACKGROUND - If this is defined, the RHQ Agent JVM will
# be launched in the background (thus causing this
# script to exit immediately). If the value is
# something other than "nofile", it will be assumed
# to be a full file path which this script will
# create and will contain the agent VM's process
# pid value. If this is not defined, the VM is
# launched in foreground and this script blocks
# until the VM exits, at which time this
# script will also exit. NOTE: this should only
# be used by the rhq-agent-wrapper.sh script.
# If you want to launch the agent in the
# background, use that script to do so instead of
# setting this variable.
#
#RHQ_AGENT_IN_BACKGROUND=rhq-agent.pid
#=======================================================================
====
# THE FOLLOWING ARE USED SOLELY FOR THE rhq-agent-wrapper.sh SCRIPT
# RHQ_AGENT_PIDFILE_DIR - When rhq-agent-wrapper.sh is used to start
# the agent, it runs the process in background
# and writes its pid to a pidfile. The default
# location of this pidfile is in the agent's
# /bin directory. If you want to have the pidfile
# written to another location, set this environment
# variable. This value must be a full path to a
# directory with write permissions.
#
RHQ_AGENT_PIDFILE_DIR="/var/run"
# RHQ_AGENT_START_COMMAND - If defined, this is the command that will be
# executed to start the agent.
# Use this to customize how the agent process
# is started (e.g. with "su" or "sudo").
# This completely overrides the command used
# to start the agent - you must ensure you
# provide a valid command that starts the agent
# script 'rhq-agent.sh'
# Note that if this start command requires the
# user to enter a password, you can show a
# prompt to the user if you set the variable
# RHQ_AGENT_PASSWORD_PROMPT.
121
www.redhat.com










