Red Hat Cloud Infrastructure 4 Quick Start for Red Hat Enterprise CloudForms

Transcription

Red Hat Cloud Infrastructure 4 Quick Start for Red Hat Enterprise CloudForms
Red Hat Cloud Infrastructure 4
Quick Start for Red Hat Enterprise
Virtualization and Red Hat
CloudForms
Installing Red Hat Cloud Infrastructure
Red Hat Cloud Infrastructure Documentation Team
Red Hat Cloud Infrastructure 4 Quick Start for Red Hat Enterprise
Virtualization and Red Hat CloudForms
Installing Red Hat Cloud Infrastructure
Red Hat Clo ud Infrastructure Do cumentatio n Team
Red Hat Custo mer Co ntent Services
rhci-do [email protected] m
Legal Notice
Co pyright © 20 14 Red Hat.
This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0
Unpo rted License. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide
attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red
Hat trademarks must be remo ved.
Red Hat, as the licenso r o f this do cument, waives the right to enfo rce, and agrees no t to assert,
Sectio n 4 d o f CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shado wman lo go , JBo ss, MetaMatrix, Fedo ra, the Infinity
Lo go , and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o ther
co untries.
Linux ® is the registered trademark o f Linus To rvalds in the United States and o ther co untries.
Java ® is a registered trademark o f Oracle and/o r its affiliates.
XFS ® is a trademark o f Silico n Graphics Internatio nal Co rp. o r its subsidiaries in the United
States and/o r o ther co untries.
MySQL ® is a registered trademark o f MySQL AB in the United States, the Euro pean Unio n and
o ther co untries.
No de.js ® is an o fficial trademark o f Jo yent. Red Hat So ftware Co llectio ns is no t fo rmally
related to o r endo rsed by the o fficial Jo yent No de.js o pen so urce o r co mmercial pro ject.
The OpenStack ® Wo rd Mark and OpenStack Lo go are either registered trademarks/service
marks o r trademarks/service marks o f the OpenStack Fo undatio n, in the United States and o ther
co untries and are used with the OpenStack Fo undatio n's permissio n. We are no t affiliated with,
endo rsed o r spo nso red by the OpenStack Fo undatio n, o r the OpenStack co mmunity.
All o ther trademarks are the pro perty o f their respective o wners.
Abstract
This guide co vers ho w to deplo y Red Hat Clo ud Infrastructure using Red Hat Enterprise
Virtualizatio n as the virtualizatio n layer and Clo udFo rms Management Engine fo r systems
management.
T able of Cont ent s
T able of Contents
. .. .St
⁠1
. .art
. . ing
. . . wit
. . . h. .Red
. . . .Hat
. . . Cloud
. . . . . . Infrast
. . . . . .ruct
. . . .ure:
. . . Red
. . . . Hat
. . . . CloudForms
. . . . . . . . . . . and
. . . .Red
. . . .Hat
. . . .Ent
. . .erprise
.........
Virt ualiz at ion
⁠1.1. Und ers tand ing Red Hat Clo ud Infras truc ture
⁠1.2. Cho o s ing Red Hat Enterp ris e Virtualiz atio n o r Red Hat Enterp ris e Linux O p enStac k Platfo rm
⁠1.3. Und ers tand ing Red Hat Enterp ris e Virtualiz atio n and Red Hat Clo ud Fo rms Ins tallatio n
4
...........
2
2
3
. .. .Inst
⁠2
. . . alling
. . . . . Red
. . . . Hat
. . . . Ent
. . . erprise
. . . . . . .Virt
. . .ualiz
. . . . at
. .ion
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. . . . . . . . . .
⁠2 .1. Req uirements fo r Red Hat Enterp ris e Virtualiz atio n
6
⁠2 .2. Firewall Rules
7
⁠2 .3. Ins talling the Red Hat Enterp ris e Virtualiz atio n Manag er
7
⁠2 .4. Ins talling a Hyp ervis o r
10
⁠2 .5. Co nfig uring the Hyp ervis o r
13
⁠2 .6 . Ap p ro ving the Hyp ervis o r
14
⁠2 .7. Setting Up Sto rag e Do mains
15
. . .Inst
⁠3
. . .alling
. . . . . Red
. . . . Hat
. . . .CloudForms
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 8. . . . . . . . . .
⁠3 .1. Req uirements fo r Red Hat Clo ud Fo rms
19
⁠3 .2. O b taining the Clo ud Fo rms Manag ement Eng ine Ap p lianc e
19
⁠3 .3. Up lo ad ing the Ap p lianc e with the Imag e Up lo ad er
19
⁠3 .4. Imp o rting the Ap p lianc e as a Temp late
20
⁠3 .5. Creating a Virtual Mac hine Bas ed o n the Ap p lianc e Temp late
21
⁠3 .6 . Ad d ing a Virtual Dis k to Ho s t the Datab as e
22
⁠3 .7. Starting and Ac c es s ing the Virtual Mac hine
23
⁠3 .8 . Co nfig uring an Internal Datab as e
24
. .. .Adding
⁠4
. . . . . . Red
. . . . Hat
. . . . Ent
. . . erprise
. . . . . . .Virt
. . .ualiz
. . . . at
. .ion
. . . Providers
. . . . . . . . . t.o. .CloudForms
. . . . . . . . . . .Infrast
. . . . . ruct
. . . . ure
. . . . . . . . . . . . .2. 4. . . . . . . . . .
⁠4 .1. Ad d ing a Red Hat Enterp ris e Virtualiz atio n Pro vid er
25
. . Explore
⁠5
. . . . . . . .What
. . . . 's
. . Next
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. 5. . . . . . . . . .
. .. .Revision
⁠A
. . . . . . . .Hist
. . . ory
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. 6. . . . . . . . . .
1
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
1. St art ing wit h Red Hat Cloud Infrast ruct ure: Red Hat CloudForms and
Red Hat Ent erprise Virt ualiz at ion
This guide will help you install a Red Hat Enterprise Virtualization configuration, then set up an
instance of Red Hat CloudForms to manage it. Red Hat Enterprise Virtualization provides the
underlying structure for running and storing virtual machines. Red Hat CloudForms provides
management capabilities for orchestrating sets of virtual machines, tracking the health of the
infrastructure, and shifting resources to adapt to existing conditions.
Red Hat Enterprise Virtualization and Red Hat CloudForms are part of the Red Hat Cloud
Infrastructure solution, along with Red Hat Enterprise Linux OpenStack Platform. Setting up a Red
Hat Enterprise Virtualization and Red Hat CloudForms installation is a good place to begin forming
the foundation for a potentially larger cloud infrastructure.
Report a bug
1.1. Underst anding Red Hat Cloud Infrast ruct ure
Red Hat Cloud Infrastructure brings together the best open source cloud management, hypervisor,
networking, and orchestration features available today in one integrated and supported solution.
With your Red Hat Cloud Infrastructure cloud, you and your organization can manage:
A few or a few thousand virtual machines.
A couple of hard disks or huge storage arrays.
A single hypervisor or hundreds of them.
One flat network or dozens of physical and virtual networks.
The data center in your small office or all your data centers around the world.
Red Hat Cloud Infrastructure lets you build your own open private hybrid cloud. Open means it can
quickly leverage and adapt to new open source technologies as they become available. Private
means you can secure your most critical data within the infrastructure you own and control. Hybrid
means you can integrate with existing cloud technologies (such as VMware vCenter or Microsoft
Hyper-V Server) or direct some of your workload to public cloud providers, such as Amazon EC2.
All the software you need to establish your own cloud infrastructure is included with Red Hat Cloud
Infrastructure. Red Hat Enterprise Linux, the standard for enterprise-quality Linux systems, forms the
foundation for Red Hat Cloud Infrastructure host and management systems. Within Red Hat Cloud
Infrastructure is a consolidation of three Red Hat products:
R ed H at C lo u d Fo rms
Red Hat CloudForms lets you establish a consistent management interface over part or all
of your company's cloud infrastructure. Red Hat CloudForms can orchestrate (launch a set
of virtual machines together), set policies (when hosts or virtual machines hit limits,
reassign resources), run reports (watch over the health of your cloud), and manage quotas
(set user-based limits on how much memory, processor and storage resources can be
used). For information on supported features in Red Hat CloudForms, see Platform Support
Matrix CloudForms Management Engine 5.3.
R ed H at En t erp rise Virt u aliz at io n
Red Hat Enterprise Virtualization consists of a Red Hat Enterprise Virtualization Manager
(to manage virtual machines and other Red Hat Enterprise Virtualization components) and
one or more host computers for running virtual machines (also referred to as hypervisors or
2
⁠1 . St art ing wit h Red Hat Cloud Infrast ruct ure: Red Hat CloudForms and Red Hat Ent erprise Virt ualiz at ion
compute nodes). From the Red Hat Enterprise Virtualization Manager, you can connect to
storage, configure networking, manage user roles, and run reports. Red Hat CloudForms
makes requests to the Red Hat Enterprise Virtualization Manager for services via the Red
Hat Enterprise Virtualization application programming interface (API).
R ed H at En t erp rise Lin u x O p en St ack Plat f o rm ( R H EL O p en St ack Plat f o rm)
Like Red Hat Enterprise Virtualization, the primary function of RHEL OpenStack Platform is
to launch and manage virtual machines. Instead of a single Red Hat Enterprise
Virtualization Manager, however, RHEL OpenStack Platform can have services split across
multiple controller nodes. As with Red Hat Enterprise Virtualization, Red Hat CloudForms
manages RHEL OpenStack Platform assets via an API.
In the tradition of open source software, Red Hat Cloud Infrastructure can tap into your company's
existing infrastructure, connecting to features from other open source or proprietary solutions. So
you can either add on new peripheral technologies to Red Hat Cloud Infrastructure or use the
following technologies you already have on site:
St o rag e
You can use storage features built into Red Hat Enterprise Linux or other third-party
products that offer NFS, iSCSI, or fibre channel storage. Note that there are additional steps
to perform Red Hat CloudForms SmartState Analysis when using iSCSI or fibre channel
storage. See the Red Hat CloudForms Management Engine 5.2 Installation Guide for
details.
Au t h en t icat io n
Authentication can be handled within Red Hat Enterprise Virtualization without requiring
additional authentication services (with the ad mi n user doing local authentication). This is
how authentication is shown in this guide.
However, if your enterprise already has centrally managed network authentication, such as
Red Hat Identity Management, Microsoft Active D irectory, Red Hat D irectory Server 9, or
some other LD AP-based authentication (such as OpenLD AP), Red Hat Enterprise
Virtualization lets you authenticate through those services. See the Red Hat Enterprise
Virtualization Installation Guide for details. Red Hat CloudForms, however, currently only
supports local (ad mi n user) or Active D irectory authentication when requesting services
from Red Hat Enterprise Virtualization.
So f t ware Man ag emen t
By connecting a Red Hat Satellite server into your computer infrastructure, you can manage
ongoing software updates and deploy systems from bare metal. Future releases of Red Hat
Cloud Infrastructure will include Red Hat Satellite server, as part of the entitlements that
come with Red Hat Cloud Infrastructure, for deploying and managing cloud components.
T h ird - Part y Virt u aliz at io n an d C lo u d Pro vid ers
If you are currently running virtual machines in virtualization or cloud environments such
as VMware vCenter or Microsoft Hyper-V Server, you can begin using Red Hat CloudForms
to manage those environments, along with your Red Hat Enterprise Virtualization and RHEL
OpenStack Platform providers. This allows you to manage all of your cloud platforms from
the same place and in a consistent way.
Report a bug
1.2. Choosing Red Hat Ent erprise Virt ualiz at ion or Red Hat Ent erprise Linux
OpenSt ack Plat form
3
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
OpenSt ack Plat form
Because Red Hat Enterprise Virtualization and RHEL OpenStack Platform provide many of the same
basic features (primarily, the ability to manage and run virtual machines across many host
computers), questions arise about what workloads are most appropriate for those two products. Here
are some comparisons of Red Hat Enterprise Virtualization and RHEL OpenStack Platform:
C o n f ig u rat io n C o mp lexit y
With Red Hat Enterprise Virtualization, most of the services for managing the Red Hat
Enterprise Virtualization environment are built into the Red Hat Enterprise Virtualization
Manager. With RHEL OpenStack Platform, services can be divided up in many different
ways and spread across multiple systems. This makes Red Hat Enterprise Virtualization
easier to set up initially, but more difficult to disperse management services across multiple
manager nodes. RHEL OpenStack Platform, on the other hand, offers much more flexible
configurations that can be more complex to manage, with services spread across multiple
controller nodes.
C u st o miz ed Virt u al Mach in es
Red Hat Enterprise Virtualization is best for running customized virtual machines, such as
desktop installations. RHEL OpenStack Platform is best suited for more generic virtual
machines that do not change much, but need to be deployed over and over again. An
analogy that is sometimes used in this case is that Red Hat Enterprise Virtualization is best
for managing pets (each of which requires personal attention), while RHEL OpenStack
Platform is best suited for handling cattle (which are managed more in a production line
than individually).
D u rat io n
Because Red Hat Enterprise Virtualization is best for holding more individualized virtual
machines, they might tend to stay around longer. For RHEL OpenStack Platform, typical
virtual machines are more likely to do their jobs, then be discarded and spun up fresh
again when needed.
Keep in mind that either Red Hat Enterprise Virtualization or RHEL OpenStack Platform can handle
any of the workloads just described here. What we are talking about is the kinds of workloads that
each is best suited for. An organization might choose to configure separate Red Hat CloudForms
and Red Hat Enterprise Virtualization, and Red Hat CloudForms and RHEL OpenStack Platform
environments, choosing Red Hat Enterprise Virtualization to offer virtual desktop systems and RHEL
OpenStack Platform to run internal web mail or employee information services.
Report a bug
1.3. Underst anding Red Hat Ent erprise Virt ualiz at ion and Red Hat
CloudForms Inst allat ion
The goal of the Red Hat Enterprise Virtualization and Red Hat CloudForms installation process
described in this guide is to create a solid Red Hat Enterprise Virtualization infrastructure that is
managed by Red Hat CloudForms.
Before you begin the actual Red Hat Enterprise Virtualization and Red Hat CloudForms installation
process, you need to have some of the following in place:
C o mp u t ers
The Red Hat Enterprise Virtualization Manager can be installed on a physical host or as a
virtual machine on a KVM host. There is also a feature called Hosted Engine that, with
special setup, allows the Red Hat Enterprise Virtualization Manager to run as a virtual
4
⁠1 . St art ing wit h Red Hat Cloud Infrast ruct ure: Red Hat CloudForms and Red Hat Ent erprise Virt ualiz at ion
machine on a host in the Red Hat Enterprise Virtualization environment. As for host systems
(Red Hat Enterprise Virtualization Hypervisor or Red Hat Enterprise Linux host), they should
run directly on physical computers.
N et wo rk In t erf aces
At least one network interface (referred to as the rhevm network) is required between the Red
Hat Enterprise Virtualization Manager, host systems (which can be Red Hat Enterprise
Virtualization Hypervisor appliances or Red Hat Enterprise Linux hosts) and storage. You
can create additional network interfaces to separate traffic, depending on your needs. For
example, you can separate network that provides access to public networks from your
virtual machines, a fast connection to databases, or a dedicated network for migrating
virtual machines between hosts.
St o rag e
Three different types of storage domains are used in Red Hat Enterprise Virtualization. An
ISO domain stores ISO images you can launch or install from. A data domain is where you
can get space to assign as back-end storage for the virtual machines. An export domain is
used to import and export virtual machines into and out of the Red Hat Enterprise
Virtualization environment. A variety of storage technologies can be used to create the
storage domains, including iSCSI, NFS, Fibre Channel, and Red Hat Storage.
Au t h en t icat io n
Roles to use and administer your Red Hat Enterprise Virtualization environment can be
assigned in a local authentication database or can leverage user accounts from Red Hat
Identity Management, Red Hat D irectory Server 9, or Microsoft Active directory. If you have a
central authentication server in place, you can identify it when you install the Red Hat
Enterprise Virtualization Manager.
Installation of a Red Hat Enterprise Virtualization setup consists of the following basic steps:
1. Install Red Hat Enterprise Linux: You need to install Red Hat Enterprise Linux as a
prerequisite to installing the Red Hat Enterprise Virtualization Manager software.
2. Install the Red Hat Enterprise Virtualization Manager on Red Hat Enterprise Linux: The Red
Hat Enterprise Virtualization Manager is the system that manages your Red Hat Enterprise
Virtualization infrastructure. Using Red Hat Cloud Infrastructure or Red Hat Enterprise
Virtualization entitlements, subscribe your system, then install and configure your Red Hat
Enterprise Virtualization Manager. D uring the configuration process, you need to identify
such things as the system's host name, the storage you will use, how authentication is done,
and other information. For the example in this guide, local authentication and NFS storage is
used.
3. Install Red Hat Enterprise Virtualization Hypervisor: Install the Hypervisor minimal operating
system on one or more physical computers you want to act as your host computers (also
referred to as compute nodes or hypervisors in other environments). To create a Red Hat
Enterprise Virtualization host you can either install a RHEV-H appliance or install a Red Hat
Enterprise Linux system and add the necessary Red Hat Enterprise Virtualization and
hypervisor software to it. For the example in this guide, the RHEV-H appliance is used.
4. Register Red Hat Enterprise Virtualization Hypervisor with Red Hat Enterprise Virtualization
Manager: Once each host is installed, you can have it register itself with the Red Hat
Enterprise Virtualization Manager. After that, the Red Hat Enterprise Virtualization Manager
can begin using it for running virtual machines.
5
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
5. Set up storage domains and connect those storage domains to the Red Hat Enterprise
Virtualization Manager: From the Red Hat Enterprise Virtualization Manager, you need to
identify different storage areas needed by the Red Hat Enterprise Virtualization environment.
6. Configure Red Hat CloudForms: A Red Hat CloudForms appliance can be installed as a
virtual machine on a host in the Red Hat Enterprise Virtualization environment. It can then be
used to manage the assets of the Red Hat Enterprise Virtualization environment.
With Red Hat CloudForms in place and communicating with the Red Hat Enterprise Virtualization
Manager, you can start using Red Hat CloudForms to manage the resources within your Red Hat
Enterprise Virtualization environment. See Section 5, “ Explore What's Next” for ways to start using
your new Red Hat Enterprise Virtualization and Red Hat CloudForms configuration.
Report a bug
2. Inst alling Red Hat Ent erprise Virt ualiz at ion
A Red Hat Enterprise Virtualization environment is installed in three stages. First, install and
configure the Red Hat Enterprise Virtualization Manager on a Red Hat Enterprise Linux physical
machine. Red Hat Enterprise Virtualization Manager provides a graphical user interface to manage
the physical and logical resources of the Red Hat Enterprise Virtualization infrastructure. Second,
install and configure a Red Hat Enterprise Virtualization Hypervisor on a second physical machine,
and add the Hypervisor to the Manager. The Hypervisor is the host on which virtual machines are
run. Third, set up storage domains on a third physical machine, and attach those storage domains
to the Manager. The data, ISO, and export storage domains provide back-end storage for virtual
machine data and ISO files.
Following the procedures in this guide will produce a working environment with a Manager, one
Hypervisor, and three storage domains.
Note
This section outlines only the basic options for installing Red Hat Enterprise Virtualization,
such as using NFS as the back-end storage for the storage domains. For more information on
advanced configuration options, see Red Hat Enterprise Virtualization Installation Guide
2.1. Requirement s for Red Hat Ent erprise Virt ualiz at ion
The following are the requirements for installing a basic Red Hat Enterprise Virtualization
environment:
One physical machine on which to install the Red Hat Enterprise Virtualization Manager. This
machine must have Red Hat Enterprise Linux installed. For this machine, 16 GB of memory is
recommended; a minimum of 4 GB memory is required.
One physical machine on which to install the Red Hat Enterprise Virtualization Hypervisor. This
machine must have Virtualization enabled in the BIOS. For this machine, 8 GB of memory is
recommended; a minimum of 2 GB memory is required.
One physical machine on which to install storage domains. This machine must have Red Hat
Enterprise Linux installed. For this machine, 500 GB of memory is recommended; a minimum of
100 GB memory is required.
The fully qualified domain name of the system on which the Manager is to be installed.
6
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
The organization name to use when creating the Manager's security certificates.
Report a bug
2.2. Firewall Rules
The following table outlines the firewall rules that the eng i ne-setup command configures when you
install the Manager. The Manager uses these ports to communicate with and control other machines
in the environment. This table is provided for your information; no further configuration is necessary
beyond that provided by eng i ne-setup.
T ab le 1. R ed H at En t erp rise Virt u aliz at io n Man ag er Firewall R u les
Po rt s
Pro t o co ls
Service
Pu rp o se
22
TCP
SSH
80, 443
TCP
HTTP,
HTTPS
5432
6100
TCP
TCP
PostgreSQL
noVNC
Connecting to other machines managed by the Red
Hat Enterprise Virtualization Manager.
The JBoss Enterprise Application Platform web server
for hosting the Red Hat Enterprise Virtualization
Manager web user interface.
Communicating with the engine database.
Opening browser based consoles to virtual machines
using the noVNC protocol.
Report a bug
2.3. Inst alling t he Red Hat Ent erprise Virt ualiz at ion Manager
2 .3.1 . Subscribing t o t he Re quire d Channe ls Using Subscript io n Manage r
To install the Red Hat Enterprise Virtualization Manager, you must register the system where you are
installing the Red Hat Enterprise Virtualization Manager with Red Hat Subscription Manager, and
subscribe to the required channels.
1. Register your system with the Content D elivery Network, entering your Customer Portal user
name and password when prompted:
# subscription-manager register
2. Find entitlement pools containing the channels required to install the Red Hat Enterprise
Virtualization Manager:
# subscription-manager list --available | grep -A8 "Red Hat
Enterprise Linux Server"
# subscription-manager list --available | grep -A8 "Red Hat
Enterprise Virtualization"
3. Use the pool identifiers located in the previous step to attach the R ed Hat Enterpri se
Li nux Server and R ed Hat Enterpri se Vi rtual i zati o n entitlements to the system:
# subscription-manager attach --pool=pool_id
4. Enable the required channels:
7
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
# subscription-manager
# subscription-manager
rpms
# subscription-manager
# subscription-manager
rpms
# subscription-manager
repos --enable=rhel-6-server-rpms
repos --enable=rhel-6-server-supplementaryrepos --enable=rhel-6-server-rhevm-3.4-rpms
repos --enable=jb-eap-6-for-rhel-6-serverrepos --enable=rhel-6-server-rhevh-rpms
Report a bug
2 .3.2 . Inst alling and Co nfiguring t he Re d Hat Ent e rprise Virt ualizat io n Manage r
1. Install the rhevm package and dependencies:
# yum update
# yum install rhevm
2. Run the eng i ne-setup command to configure the Red Hat Enterprise Virtualization
Manager:
# engine-setup
3. Press Enter to accept the automatically detected host name:
Host fully qualified DNS name of this server [autodetected host
name]:
4. Press Enter to allow the eng i ne-setup command to modify your firewall configuration:
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
5. Choose to configure a local database. The eng i ne-setup command configures a
PostgreSQL database automatically (including adding a user and a database):
Where is the database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for
the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and
create Engine database, or prefer to perform that manually?
(Automatic, Manual) [Automatic]:
6. Select Bo th:
Application mode (Both, Virt, Gluster) [Both]:
7. Choose NFS as the initial data center storage type:
Default storage type: (NFS, FC, ISCSI, POSIXFS) [NFS]:
8. Set a password for the automatically created administrative user of the Red Hat Enterprise
Virtualization Manager:
8
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
Engine admin password:
Confirm engine admin password:
9. Provide the organization name for the certificate. Press Enter to accept the automatically
detected organization name:
Organization name for certificate [autodetected domain-based name]:
10. By default, external SSL (HTTPS) communication with the Manager is secured with the selfsigned certificate created earlier in the installation process to securely communicate with
hosts:
Setup can configure apache to use SSL using a certificate issued
from the internal CA.
Do you wish Setup to configure that, or prefer to perform that
manually? (Automatic, Manual) [Automatic]:
11. The Red Hat Enterprise Virtualization Manager uses the Apache web server to present a
landing page to users. Press Enter make the landing page of the Manager the default page
presented by Apache:
Setup can configure the default page of the web server to present
the application home page. This may conflict with existing
applications.
Do you wish to set the application as the default web page of the
server? (Yes, No) [Yes]:
12. Create an NFS share on the Manager to use as an ISO storage domain. Hosting the ISO
domain locally to the Manager simplifies keeping some elements of your environment up to
date:
Configure
(Yes, No)
Local ISO
Local ISO
Local ISO
an NFS
[Yes]:
domain
domain
domain
share on this server to be used as an ISO Domain?
path [/var/lib/exports/iso]:
ACL [0.0.0.0/0.0.0.0(rw)]:
name [ISO_DOMAIN]:
13. Configure a websocket proxy server for allowing users to connect to virtual machines via the
noVNC or HTML 5 consoles:
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
14. Optionally, use the eng i ne-setup command to allow a proxy server to broker transactions
from the Red Hat Access plug-in:
Would you like transactions from the Red Hat Access Plugin sent
from the RHEV Manager to be brokered through a proxy server? (Yes,
No) [No]:
15. Review the installation settings, and press Enter to accept the values and proceed with the
installation.
Please confirm installation settings (OK, Cancel) [OK]:
9
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
Report a bug
2.4 . Inst alling a Hypervisor
A hypervisor is a physical machine whose processing capabilities the Manager can use to run virtual
machines. You must add at least one hypervisor to your Red Hat Enterprise Virtualization
environment for it to function.
This section outlines how to set up a hypervisor by installing the Red Hat Enterprise Virtualization
Hypervisor minimal operating system on a physical machine.
2 .4 .1 . Pre paring USB Inst allat io n Me dia Using live cd-iso -t o -disk
D ownload the package containing the Red Hat Enterprise Virtualization Hypervisor disk image, and
the package containing live- cd - iso - t o - d isk. Use live- cd - iso - t o - d isk to write that disk image to a
USB storage device.
1. Install the rhev-hypervisor6 and livecd-tools packages:
# yum install rhev-hypervisor6 livecd-tools
2. Write the disk image to a USB storage device.
# livecd-iso-to-disk --format --reset-mbr /usr/share/rhevhypervisor/rhev-hypervisor.iso /dev/sdc
Report a bug
2 .4 .2 . Inst alling t he Hype rviso r
1. Use the USB storage device that contains the Hypervisor boot image to start the machine on
which you will install the Hypervisor.
2. From the boot splash screen, press any key to open the boot menu.
10
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
Fig u re 1. T h e b o o t sp lash screen
3. From the boot menu, use the directional keys to select Instal l (Basi c Vi d eo ).
11
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
Fig u re 2. T h e b o o t men u
4. Customize the keyboard layout to a specific language or location. Use the directional keys to
highlight the preferred option, and press Enter.
Examp le 1. K eyb o ard Layo u t C o n f ig u rat io n
Keyboard Layout Selection
Avai l abl e Keybo ard Layo uts
Swiss German (latin1)
Turkish
U.S. English
U.S. International
...
(Hit enter to select a layout)
<Quit>
<Back>
<Continue>
5. Select the disk from which the Hypervisor will boot. The Hypervisor's boot loader will be
installed to the master boot record of the disk that is selected on this screen. The Hypervisor
attempts to automatically detect the disks attached to the system and presents a list from
which to choose the boot device.
Select an automatically detected device.
12
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
a. Select the entry for the disk the Hypervisor is to boot from, and press Enter.
b. Select <C o nti nue>, and press Enter.
Important
The selected disk must be identified as a boot device and appear in the boot order
either in the system's BIOS or in a pre-existing boot loader.
6. Select the disk or disks on which the Hypervisor itself will be installed. The Hypervisor
attempts to automatically detect the disks attached to the system and presents a list from
which installation devices are chosen. This disk can be the same disk as the boot device.
Warning
All data on the selected storage devices will be destroyed.
a. Select the entry for the disk on which to install the Hypervisor, and press Enter.
b. Select <C o nti nue>, and press Enter.
7. Configure storage for the Hypervisor.
a. Select the Fi l l d i sk wi th D ata parti ti o n check box.
b. Check the automatically generated values for Swap, C o nfi g , and Lo g g i ng .
c. Select <C o nti nue>, and press Enter.
8. Set a password to secure local access to the Hypervisor using the administrative user
account.
a. Enter the preferred password in both the P asswo rd and C o nfi rm P asswo rd fields.
b. Select <Instal l >, and press Enter.
Note
If you enter a weak password, the Hypervisor provides a warning; however, you can proceed
with the installation using that password. It is recommended that you use a strong password.
Strong passwords comprise a mix of uppercase, lowercase, numeric, and punctuation
characters. They are six or more characters long and do not contain dictionary words.
Report a bug
2.5. Configuring t he Hypervisor
After you have installed the Hypervisor on a physical machine, you must configure the Hypervisor
before you can add it to the Manager. Configuration involves logging in to the Hypervisor using the
administrative user account, initializing the network interfaces attached to the Hypervisor, and
specifying the address of the Manager to which the Hypervisor will be added.
13
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
2 .5 .1 . Lo gging in t o t he Hype rviso r
Log in to the Hypervisor console locally to configure the options required to add the Hypervisor to the
Manager.
1. Enter the user name ad mi n, and press Enter.
2. Enter the password you set during installation, and press Enter.
Report a bug
2 .5 .2 . Co nfiguring Ne t wo rk Int e rface s
After you have installed the Hypervisor, all network interface controllers attached to the Hypervisor
are initially unconfigured. You must configure at least one network interface controller to connect the
Hypervisor with the Manager.
1. Select a network interface from the list beneath Avai l abl e System NIC s, and press Enter
to configure that network interface.
Note
To identify the physical network interface controller associated with the selected
network interface, select <Fl ash Li g hts to Id enti fy>, and press Enter.
2. Select D HC P under IP v4 Setti ng s, and press the space bar.
3. Leave the VLAN ID field blank.
4. Select <Save>, and press Enter.
Report a bug
2 .5 .3. Co nfiguring t he Hype rviso r Manage m e nt Se rve r
Attach the Hypervisor to the Manager. Use the o Vi rt Eng i ne screen in the Hypervisor user
interface to register the Hypervisor with the Manager.
1. Enter the IP address or fully qualified domain name of the Manager in the Manag ement
Server field.
2. Enter the management server port in the Manag ement Server P o rt field. The default value
is 4 4 3.
3. Leave the P asswo rd and C o nfi rm P asswo rd fields blank.
4. Select <Save & R eg i ster>, and press Enter.
5. In the o Vi rt Eng i ne Fi ng erpri nt screen, review the SSL fingerprint retrieved from the
Manager, select <Accept>, and press Enter.
Report a bug
2.6. Approving t he Hypervisor
14
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
The final step in adding the Hypervisor to your Manager is to approve the addition of the Hypervisor
in the Administration Portal. The Hypervisor is automatically initialized and added to the default data
center.
2 .6 .1 . Co nne ct ing t o t he Adm inist rat io n Po rt al
Access the Administration Portal using a web browser.
1. In a web browser, navigate to https: //your-manager-fqdn/o vi rt-eng i ne, replacing
your-manager-fqdn with the fully qualified domain name that you provided during installation.
Important
The first time that you connect to the Administration Portal, you are prompted to trust
the certificate being used to secure communications between your browser and the
web server. You must accept this certificate.
2. Click Ad mi ni strati o n P o rtal .
3. Enter your User Name and P asswo rd . If you are logging in for the first time, use the user
name ad mi n in conjunction with the password that you specified during installation.
4. Select the domain against which to authenticate from the D o mai n list. If you are logging in
using the internal ad mi n user name, select the i nternal domain.
5. You can view the Administration Portal in multiple languages. The default selection will be
chosen based on the locale settings of your web browser. If you would like to view the
Administration Portal in a language other than the default, select your preferred language
from the list.
6. Click Lo g i n.
Report a bug
2 .6 .2 . Appro ving a Re gist e re d Hype rviso r
Approve a Hypervisor that has been registered using the details of the Manager.
1. From the Administration Portal, click the H o st s tab, and then click the host to be approved.
The host is currently listed with the status of Pen d in g Ap p ro val.
2. Click Ap p ro ve to open the Ed i t and Appro ve Ho sts window.
3. Click O K. If you have not configured power management, you are prompted to confirm
whether to proceed without doing so; click O K.
Report a bug
2.7. Set t ing Up St orage Domains
A storage domain is a formatted volume that stores some of the data required to run a Red Hat
Enterprise Virtualization Environment. In order to have a working environment, you must have three
storage domains:
1. D ata D omain
15
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
2. ISO D omain
3. Export D omain
The ISO storage domain is automatically created and added to the Manager during the Manager
installation process. You must set up the data domain and the export domain, and add both to the
Manager.
Use a machine that is neither the machine on which the Hypervisor runs nor the machine on which
the Manager is installed. This means that you must have a third machine (in addition to the machine
on which the Hypervisor runs and the machine on which the Manager is installed) in order to set up
storage domains. Hosting storage on a dedicated machine allows for optimized access to storage
domains, and avoids any conflicts caused by sharing CPU and memory with other processes. The
ISO domain is hosted on the Manager itself, because it stores only moderately-sized ISO files, and
can be easily accessed when creating a new virtual machine or attaching an ISO file to a virtual
machine to perform a task. The data domain and export domain experience a much higher volume of
read and write operations, and benefit from being hosted on a dedicated machine.
The process of setting up storage domains involves two steps: the first step is setting up and turning
on exports from within the file system of the machine hosting the storage domains, and the second
step is logging in to the Red Hat Enterprise Virtualization Manager Administration Portal and adding
the storage domains to the environment.
2 .7 .1 . Pre paring NFS St o rage
Set up NFS shares that will serve as a data domain and an export domain on a Red Hat Enterprise
Linux server. It is not necessary to create an ISO domain because the Red Hat Enterprise
Virtualization Manager installation procedure creates one.
1. Install nfs-utils, the package that provides NFS tools:
# yum install nfs-utils
2. Configure the boot scripts to make shares available every time the system boots:
#
#
#
#
chkconfig
chkconfig
chkconfig
chkconfig
--add rpcbind
--add nfs
rpcbind on
nfs on
3. Start the rpcbind service and the nfs service:
# service rpcbind start
# service nfs start
4. Create the data directory and the export directory:
# mkdir -p /exports/data
# mkdir -p /exports/export
5. Add the newly created directories to the /etc/expo rts file. Add the following to
/etc/expo rts:
/exports/data *(rw)
/exports/export *(rw)
16
⁠2 . Inst alling Red Hat Ent erprise Virt ualiz at ion
6. Export the storage domains:
# exportfs -r
7. Reload the NFS service:
# service nfs reload
8. Create user vd sm:
# useradd vdsm
9. Create the group kvm:
# groupadd kvm
10. Add the user vd sm to the group kvm:
# useradd -G kvm vdsm
11. Set the ownership of your exported directories to 36:36, which gives vdsm:kvm ownership.
This makes it possible for the Manager to store data in the storage domains represented by
these exported directories:
# chown -R 36:36 /exports/data
# chown -R 36:36 /exports/export
12. Change the mode of the directories so that read and write access is granted to the owner, and
so that read and execute access is granted to the group and other users:
# chmod 0755 /exports/data
# chmod 0755 /exports/export
Report a bug
2 .7 .2 . At t aching NFS St o rage
Attach an NFS storage domain to the data center in your Red Hat Enterprise Virtualization
environment. This storage domain provides storage for virtualized guest images and ISO boot
media. This procedure assumes that you have already exported shares. You must create the data
domain before creating the export domain. Use the same procedure to create the export domain,
selecting Expo rt / NFS in the D o mai n Functi o n / Sto rag e T ype list.
1. In the Red Hat Enterprise Virtualization Manager Administration Portal, click the St o rag e
resource tab.
2. Click New D o mai n.
17
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
Fig u re 3. T h e N ew D o main Win d o w
3. Enter a Name for the storage domain.
4. Accept the default values for the D ata C enter, D o mai n Functi o n / Sto rag e T ype,
Fo rmat, and Use Ho st drop-down lists.
5. Enter the Expo rt P ath to be used for the storage domain.
The export path should be in the format of 192.168.0.10:/data or domain.example.com:/data.
6. Click O K.
The new NFS data domain is displayed in the Sto rag e tab with a status of Lo cked until the
disk is prepared. The data domain is then automatically attached to the data center.
Report a bug
3. Inst alling Red Hat CloudForms
Red Hat CloudForms provides a centralized management console for large and distributed
virtualized deployments. It extends Red Hat Enterprise Virtualization and Red Hat Enterprise Linux
OpenStack Platform management capabilities by adding performance monitoring, discovery, selfservice provisioning, policy-based compliance, charge-back, and greater automation capability.
Red Hat CloudForms is comprised of a single component, the CloudForms Management Engine
18
⁠3 . Inst alling Red Hat CloudForms
appliance. After downloading the appliance as a virtual machine image template from the Red Hat
Customer Portal, upload the appliance to a Red Hat Enterprise Virtualization environment. After a few
appliance configuration steps, you are ready to manage your hybrid cloud environment using the
CloudForms web interface.
3.1. Requirement s for Red Hat CloudForms
To use CloudForms Management Engine, the following requirements must be met:
One of the following web browsers:
Mozilla Firefox for versions supported under Mozilla's Extended Support Release (ESR) ⁠ [1]
Internet Explorer 8 or higher
Google Chrome for Business
A monitor with minimum resolution of 1280x1024.
Adobe Flash Player 9 or above. At the time of publication, you can access it at
http://www.adobe.com/products/flashplayer/.
Report a bug
3.2. Obt aining t he CloudForms Management Engine Appliance
1. Go to https://access.redhat.com, and log in to the Red Hat Customer Portal using your
customer account details.
2. Navigate to D o wn lo ad s → Pro d u ct D o wn lo ad s → View All D o wn lo ad s A- Z → R ed H at
C lo u d Fo rms.
3. Click the D o wnl o ad s tab.
4. Click the C FME R ed Hat Vi rtual Appl i ance download link.
Report a bug
3.3. Uploading t he Appliance wit h t he Image Uploader
Upload the CloudForms Management Engine Appliance file to the Red Hat Enterprise Virtualization
Manager.
1. Install the rhevm-i mag e-upl o ad er package containing the eng i ne-i mag e-upl o ad er
script to your local machine:
# yum install rhevm-image-uploader
2. Change to the directory containing the CloudForms Management Engine Appliance.
3. Upload the image using the following command:
# engine-image-uploader -N NEW_IMAGE_NAME -e EXPORT_STORAGE_DOMAIN
-v -m upload cfme-rhevm-5.3-15.x86_64.rhevm.ova
-N NEW_IMAGE_NAME
19
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
Specifies a new name for the image being uploaded.
-e EXPORT_STORAGE_DOMAIN
The export storage domain to which the file is uploaded. An export storage domain
is used to backup virtual machines and templates.
-v
D isplay verbose output.
-m
Specifies that network components in the image will not be removed from the image.
By default, the command removes network interface cards from image being
uploaded to prevent conflicts with network cards on other virtual machines already
in the environment.
4. Enter the username and password of the default administrative user for your Red Hat
Enterprise Virtualization Manager when prompted.
Please provide the REST API username for RHEV-M: admin@ internal
Please provide the REST API password for the admin@ internal RHEV-M
user: **********
It takes approximately 90 minutes to upload the CloudForms Management Engine Appliance file to
the Red Hat Enterprise Virtualization Manager.
Report a bug
3.4 . Import ing t he Appliance as a T emplat e
After you have uploaded the appliance to your export storage domain, you must import the image as
a template so that you can create a virtual machine based on that template.
1. From the Administration Portal, click the Sto rag e tab.
2. Click the T empl ate Impo rt tab in the details pane.
3. Select the image to import and click Impo rt.
20
⁠3 . Inst alling Red Hat CloudForms
Fig u re 4 . T h e Imp o rt T emp lat e( s) Win d o w
4. Select the D efaul t Sto rag e D o mai n and C l uster.
5. Click O K.
Report a bug
3.5. Creat ing a Virt ual Machine Based on t he Appliance T emplat e
Create a virtual machine based on the appliance template on which to host the CloudForms
Management Engine.
Note
Virtual machines created based on a template depend on that template. This means that you
cannot remove that template from the Manager if there is a virtual machine that was created
based on that template. However, you can clone a virtual machine from a template to remove
the dependency on that template.
1. Click the Vi rtual Machi nes tab.
2. Click the New VM button to open the New Vi rtual Machi ne window.
3. Select the C l uster on which the virtual machine will run.
4. Select the appliance template from the Based o n T empl ate list.
5. Select base templ ate (1) from the T empl ate Sub Versi o n list.
6. Enter a Name, D escri pti o n, and any C o mments, and accept the default values inherited
from the template in the rest of the fields. You can change them if needed.
7. Click the R eso urce Al l o cati o n tab.
21
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
8. Select the T hi n radio button in the Sto rag e Al l o cati o n area.
9. Select the disk provisioning policy from the Al l o cati o n P o l i cy list. This policy affects
the speed of the clone operation and the amount of disk space the new virtual machine
initially requires.
Selecting T hi n P ro vi si o n results in a faster clone operation and provides optimized
usage of storage capacity. D isk space is allocated only as it is required. This is the
default selection.
Selecting P real l o cated results in a slower clone operation and provides optimized
virtual machine read and write operations. All disk space requested in the template is
allocated at the time of the clone operation.
10. Use the T arg et list to select the storage domain on which the virtual machine's virtual disk
will be stored.
11. Click O K.
The virtual machine is displayed in the list in the Vi rtual Machi nes tab.
Report a bug
3.6. Adding a Virt ual Disk t o Host t he Dat abase
Add a new disk to the appliance on which to host the database.
1. From the Administration Portal, click the Vi rtual Machi nes tab.
2. Select the appliance virtual machine.
3. Click the D i sks tab in the details pane.
4. Click Ad d .
22
⁠3 . Inst alling Red Hat CloudForms
Fig u re 5. T h e Ad d Virt u al D isk win d o w
5. Click Internal .
6. Enter 20 in the Si ze(G B) field.
7. Enter an Al i as for the virtual disk.
8. Enter a D escri pti o n for the virtual disk.
9. Select Vi rtIO from the Interface list.
10. Select T hi n P ro vi si o n from the Al l o cati o n P o l i cy list.
11. Select the data domain for the Red Hat Enterprise Virtualization environment from the
Sto rag e D o mai n list.
12. Select the Acti vate check box to activate the disk after attaching it to the virtual machine,
and clear the Wi pe After D el ete, Bo o tabl e, Shareabl e, and R ead O nl y check
boxes.
13. Click O K.
Report a bug
3.7. St art ing and Accessing t he Virt ual Machine
After you have created the virtual machine, you must access the console for the virtual machine to
configure the database. A console is a graphical user interface that allows you to interact with a
virtual machine in a similar way as a physical machine.
23
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
1. Click the Vi rtual Machi nes tab.
2. Click the name of the virtual machine.
3. Click
, or right-click the virtual machine and select R u n .
4. Click the console button, or right-click the virtual machine and select C o nso l e.
Fig u re 6 . C o n n ect io n Ico n o n t h e Virt u al Mach in e Men u
Report a bug
3.8. Configuring an Int ernal Dat abase
CloudForms Management Engine uses a database to store information about the cloud environment
it manages. You must configure a database for the appliance before you can use it to administer
your cloud infrastructure.
1. Log in to the appliance using the user name ad mi n and the password smartvm.
2. Press Enter to change to the configuration menu.
3. Select 8) C o nfi g ure D atabase from the menu.
4. When prompted, select the option to create a security key.
5. Choose 1) Internal for the database location.
6. Choose a disk for the database. For example:
1) /dev/vdb: 20480
Choose disk:
Enter 1 to choose /d ev/vd b for the database location.
7. When prompted, enter a three digit region ID to create a region. As your deployment grows,
you can add more regions in the future to manage multiple appliances.
Warning
Creating a new region destroys any existing data on the selected disk.
8. Confirm the configuration when prompted.
Report a bug
4 . Adding Red Hat Ent erprise Virt ualiz at ion Providers t o CloudForms
Infrast ruct ure
24
⁠5 . Explore What 's Next
Adding a Red Hat Enterprise Virtualization provider to Red Hat CloudForms establishes a connection
between the two environments, enabling the appliance to manage the hybrid cloud environment.
4 .1. Adding a Red Hat Ent erprise Virt ualiz at ion Provider
1. In a web browser, navigate to the URL of the CloudForms Management Engine console. By
default, this URL is the IP address of the machine on which the appliance is installed.
2. Enter ad mi n in the Username text field, and smartvm in the P asswo rd text field.
3. Navigate to In f rast ru ct u re → Pro vid ers.
4. Click
C o nfi g urati o n, then click
Ad d a New Infrastructure P ro vi d er.
5. Enter a Name for the provider.
6. From the T ype list, select R ed Hat Enterpri se Vi rtual i zati o n Manag er.
7. Enter the Ho st Name of the provider.
8. Enter the IP Ad d ress of the provider.
9. Enter 4 4 3 in the AP I P o rt field.
10. Enter the username of the default administrative user for the Manager in the User ID field,
and the password in the P asswo rd field.
11. Click Val i d ate to authenticate with the Manager.
12. Click Save.
Report a bug
5. Explore What 's Next
Congratulations! You have now successfully deployed Red Hat Cloud Infrastructure by installing
CloudForms Management Engine on your Red Hat Enterprise Virtualization environment.
Use CloudForms to perform a multitude of management tasks aggregating all information associated
with your virtual infrastructure into a single, unified management console. For virtual environments,
CloudForms provides monitoring and tracking, capacity management and planning, resource usage
and optimization, virtual machine life cycle management, and policies to govern access and usage.
See the following links that describe some of the management tasks you can perform in your
virtualized cloud environment:
Adding a Provider
Provisioning Requests
Performing SmartState Analysis On Hosts
Viewing Capacity and Utilization Charts For a Virtual Machine
Usage, Chargeback, and Timelines
Report a bug
25
Red Hat Cloud Infrast ruct ure 4 Q uick St art for Red Hat Ent erprise Virt ualiz at ion and Red Hat CloudForms
A. Revision Hist ory
R evisio n 4 .0.0- 14 .2
Final build for publication.
T u e O ct 07 2014
An d rew D ah ms
R evisio n 4 .0.0- 13
Wed 1 O ct 2014
Su yo g Sain kar
BZ #1146293 - Added a new topic outlining requirements for CloudForms.
R evisio n 4 .0.0- 12
T u e 30 Sep 2014
BZ #1146302 - Made QE review edits to Topic ID : 41709.
BZ #1146302 - Made QE review edits to Topic ID : 41732.
BZ #1146302 - Made QE review edits to Topic ID : 41679.
Sh ikh a N an si
R evisio n 4 .0.0- 11
T u e 30 Sep 2014
Lu cy B o p f
BZ #1146331 - Added a topic on starting and accessing a virtual machine.
R evisio n 4 .0.0- 10
BZ #1146318 - Applied
BZ #1146315 - Applied
BZ #1146313 - Applied
BZ #1146312 - Applied
minor
minor
minor
minor
Fri 26 Sep 2014
style fixes to topics regarding
style fixes to topics regarding
style fixes to topics regarding
style fixes to topics regarding
Lu cy B o p f
setting up storage domains.
approving the Hypervisor.
installing the Hypervisor.
installing the Manager.
R evisio n 4 .0.0- 9
T h u 25 Sep 2014
Lu cy B o p f
BZ #1144213 - Added topics on how to import an appliance as a template, and how to create a virtual
machine based on a template.
R evisio n 4 .0.0- 8
Fri Sep 19 2014
An d rew D ah ms
BZ #1143950 - Added a procedure on how to add a virtual disk for hosting the appliance database.
R evisio n 4 .0.0- 7
Fri Sep 19 2014
Su yo g Sain kar
BZ #1143945 - Created a new topic on the potential next steps using CloudForms
BZ #1140932 - Created a new topic providing an overview of installing CloudForms
BZ #1140933 - Created a new topic outlining what adding Red Hat Enterprise Virtualization providers
to CloudForms entails
BZ #1140935 - Line edit items for consistency and appropriate word usage
R evisio n 4 .0.0- 6
Wed Sep 17 2014
Sh ikh a N an si
BZ #1135881 - Replaced topic ID 21367 with topic ID 41732 that has the changes mentioned in the
bug.
R evisio n 4 .0.0- 5
Wed Sep 17 2014
Z ac D o ver
BZ #1139084 - Added a section outlining the purpose of storage domains.
BZ #1139083 - Added a section on creating NFS storage domains.
BZ #1139081 - Added a section on preparing NFS storage.
R evisio n 4 .0.0- 4
26
Fri Sep 12 2014
Lu cy B o p f
⁠A. Revision Hist ory
BZ #1139072 - Updated topic on subscribing to channels using Subscription Manager to match a
similar topic in the Quick Start for Red Hat Enterprise Linux OpenStack Platform and CloudForms
guide.
BZ #1139072 - Updated topics on connecting to the Administration Portal and approving a
Hypervisor.
BZ #1139069 - Updated topics on figuring the Hypervisor. Created two topics, specifically for use in
Red Hat Cloud Infrastructure, on configuring network interfaces and configuring the Hypervisor
management server.
BZ #1139068 - Combined and edited topics on starting and installing the Hypervisor.
BZ #1139056 - Updated the topic on preparing USB installation media.
BZ #1139055 - Created a topic, specifically for use in Red Hat Cloud Infrastructure, on installing the
Hypervisor disk image.
BZ #1135858 - Combined and edited topics on installing and configuring the Red Hat Enterprise
Virtualization Manager.
BZ #1135857 - Created a prerequisites topic and an overview topic for installing Red Hat Enterprise
Virtualization.
R evisio n 4 .0.0- 3
T u e Sep 9 2014
Su yo g Sain kar
BZ #1137060 - Added topic 41682 with the changes mentioned in the bug
R evisio n 4 .0.0- 2
Mo n Sep 8 2014
Su yo g Sain kar
BZ #1136585 - Added topic 41679 with the changes mentioned in the bug
R evisio n 4 .0.0- 1
Fri Sep 5 2014
Sh ikh a N an si
BZ #1135891 - Replaced topic id 24989 with topic id 41670. 41670 has the changes mentioned in this
bug.
R evisio n 4 .0.0- 0
Initial book creation.
Mo n Ju l 21 2014
Su yo g Sain kar
[1] http ://www.mo z illa.o rg /en-US/firefo x/o rg aniz atio ns /faq /
27