[Ovirt-devel] [PATCH docs] Initial commit of Using Ovirt Admin UI
Jim Meyering
jim at meyering.net
Fri Sep 12 19:01:17 UTC 2008
FYI, here's a patch from Susan Burgess that I pushed several hours ago:
I'm omitting all the binary parts, of course.
>From 4a87b5217e90225c81e64c90f0711d92fc5d07d0 Mon Sep 17 00:00:00 2001
From: Susan Burgess <sburgess at redhat.com>
Subject: [PATCH docs] Initial commit of Using Ovirt Admin UI
Date: Fri, 12 Sep 2008 16:49:21 +1000
---
Using_the_oVirt_Admin_UI/Makefile | 14 +
Using_the_oVirt_Admin_UI/en-US/Appendix-B.xml | 42 +
Using_the_oVirt_Admin_UI/en-US/Appendix.xml | 14 +
Using_the_oVirt_Admin_UI/en-US/Author_Group.xml | 15 +
Using_the_oVirt_Admin_UI/en-US/Book_Info.xml | 30 +
Using_the_oVirt_Admin_UI/en-US/Chapter.xml | 25 +
Using_the_oVirt_Admin_UI/en-US/Getting-Started.xml | 259 ++
Using_the_oVirt_Admin_UI/en-US/Glossary.xml | 390 ++
.../en-US/Installing-the-Admin-UI.xml | 405 ++
.../en-US/Introduction-to-oVirt.xml | 145 +
.../en-US/Managing-User-Permissions.xml | 181 +
Using_the_oVirt_Admin_UI/en-US/Managing-VMs.xml | 306 ++
.../en-US/Managing-the-Hardware.xml | 720 ++++
Using_the_oVirt_Admin_UI/en-US/Preface.xml | 91 +
Using_the_oVirt_Admin_UI/en-US/Quick-Start.xml | 171 +
.../en-US/Revision_History.xml | 42 +
.../en-US/Sample-oVirt-Scenarios.xml | 393 ++
Using_the_oVirt_Admin_UI/en-US/Troubleshooting.xml | 14 +
Using_the_oVirt_Admin_UI/en-US/Using_oVirt.ent | 4 +
Using_the_oVirt_Admin_UI/en-US/Using_oVirt.xml | 22 +
Using_the_oVirt_Admin_UI/en-US/images/AddHost.png | Bin 0 -> 31515 bytes
.../en-US/images/AddNewHWPool.png | Bin 0 -> 26731 bytes
.../en-US/images/AddNewStorageServer.png | Bin 0 -> 27810 bytes
.../en-US/images/AddNewStorageServerView.png | Bin 0 -> 37395 bytes
.../en-US/images/AddNewUser.png | Bin 0 -> 35798 bytes
.../en-US/images/AddNewVMPool.png | Bin 0 -> 25993 bytes
.../en-US/images/AddStorage.png | Bin 0 -> 57297 bytes
.../en-US/images/AddStorageView.png | Bin 0 -> 38595 bytes
Using_the_oVirt_Admin_UI/en-US/images/AddVM.png | Bin 0 -> 42446 bytes
.../en-US/images/Add_StorageSever2.jpg | Bin 0 -> 159949 bytes
.../en-US/images/DeleteVM1.png | Bin 0 -> 38045 bytes
.../en-US/images/DeleteVM2.png | Bin 0 -> 32769 bytes
.../en-US/images/HWresourceMenu.png | Bin 0 -> 17825 bytes
.../en-US/images/HostTab.jpg.svg | 60 +
.../en-US/images/IconHWPool.png | Bin 0 -> 1070 bytes
.../en-US/images/IconVMPool.png | Bin 0 -> 685 bytes
Using_the_oVirt_Admin_UI/en-US/images/MoveHost.png | Bin 0 -> 27347 bytes
.../en-US/images/MoveHostNewPool.png | Bin 0 -> 26758 bytes
.../en-US/images/MoveStorageNewPool.png | Bin 0 -> 32241 bytes
.../en-US/images/MoveStorageNewPoolView.png | Bin 0 -> 35569 bytes
.../en-US/images/MoveStorageNewPoolView1.png | Bin 0 -> 35100 bytes
.../en-US/images/MoveStorageServer.png | Bin 0 -> 37076 bytes
.../en-US/images/MoveStorageServer1.png | Bin 0 -> 36189 bytes
.../en-US/images/MoveStorageServerView.png | Bin 0 -> 38208 bytes
.../en-US/images/QS1-SummaryTab.jpg | Bin 0 -> 23858 bytes
.../en-US/images/QS1-SummaryTab.png | Bin 0 -> 86225 bytes
.../en-US/images/StorageTab.png | Bin 0 -> 21656 bytes
.../en-US/images/UserAccessTab.png | Bin 0 -> 19384 bytes
.../en-US/images/UserAccessTab_roleMenu.png | Bin 0 -> 50512 bytes
.../en-US/images/UserChangeRole.png | Bin 0 -> 29874 bytes
.../en-US/images/VMActions1.png | Bin 0 -> 27317 bytes
.../en-US/images/VMActions2.png | Bin 0 -> 27088 bytes
.../en-US/images/VMProperties.png | Bin 0 -> 66173 bytes
Using_the_oVirt_Admin_UI/en-US/images/VMTab.png | Bin 0 -> 29447 bytes
.../en-US/images/VPool_SummaryTab.jpg | Bin 0 -> 242345 bytes
.../en-US/images/VPool_SummaryTab.png | Bin 0 -> 50970 bytes
.../en-US/images/VPool_VMTab.png | Bin 0 -> 56846 bytes
Using_the_oVirt_Admin_UI/en-US/images/VRMenu.png | Bin 0 -> 22650 bytes
.../en-US/images/ViewHWResources.png | Bin 0 -> 75606 bytes
.../en-US/images/ViewHosts.png | Bin 0 -> 33208 bytes
.../en-US/images/ViewVMPool.png | Bin 0 -> 34258 bytes
.../en-US/images/ViewVMResources.png | Bin 0 -> 51420 bytes
.../en-US/images/amyadmin5.png | Bin 0 -> 108462 bytes
.../en-US/images/helpbutton.png | Bin 0 -> 17253 bytes
Using_the_oVirt_Admin_UI/en-US/images/icon.svg | 3936 ++++++++++++++++++++
.../en-US/images/logical_arch2.gif | Bin 0 -> 20208 bytes
.../en-US/images/navpanel-addhwresource.png | Bin 0 -> 1171 bytes
.../en-US/images/navpanel-addvmresource.png | Bin 0 -> 821 bytes
.../en-US/images/navpanel-delete.png | Bin 0 -> 539 bytes
.../en-US/images/navpanelicons.png | Bin 0 -> 2151 bytes
.../en-US/images/oVirtInterface.png | Bin 0 -> 58844 bytes
.../en-US/images/whatisovirtNEW.png | Bin 0 -> 31892 bytes
72 files changed, 7279 insertions(+), 0 deletions(-)
create mode 100644 Using_the_oVirt_Admin_UI/Makefile
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Appendix-B.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Appendix.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Author_Group.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Book_Info.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Chapter.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Getting-Started.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Glossary.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Installing-the-Admin-UI.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Introduction-to-oVirt.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Managing-User-Permissions.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Managing-VMs.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Managing-the-Hardware.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Preface.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Quick-Start.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Revision_History.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Sample-oVirt-Scenarios.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Troubleshooting.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Using_oVirt.ent
create mode 100644 Using_the_oVirt_Admin_UI/en-US/Using_oVirt.xml
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddHost.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddNewHWPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddNewStorageServer.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddNewStorageServerView.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddNewUser.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddNewVMPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddStorage.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddStorageView.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/AddVM.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/Add_StorageSever2.jpg
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/DeleteVM1.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/DeleteVM2.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/HWresourceMenu.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/HostTab.jpg.svg
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/IconHWPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/IconVMPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveHost.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveHostNewPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageNewPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageNewPoolView.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageNewPoolView1.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageServer.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageServer1.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/MoveStorageServerView.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/QS1-SummaryTab.jpg
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/QS1-SummaryTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/StorageTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/UserAccessTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/UserAccessTab_roleMenu.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/UserChangeRole.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VMActions1.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VMActions2.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VMProperties.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VMTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VPool_SummaryTab.jpg
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VPool_SummaryTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VPool_VMTab.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/VRMenu.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/ViewHWResources.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/ViewHosts.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/ViewVMPool.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/ViewVMResources.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/amyadmin5.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/helpbutton.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/icon.svg
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/logical_arch2.gif
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/navpanel-addhwresource.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/navpanel-addvmresource.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/navpanel-delete.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/navpanelicons.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/oVirtInterface.png
create mode 100644 Using_the_oVirt_Admin_UI/en-US/images/whatisovirtNEW.png
diff --git a/Using_the_oVirt_Admin_UI/Makefile b/Using_the_oVirt_Admin_UI/Makefile
new file mode 100644
index 0000000..963d546
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/Makefile
@@ -0,0 +1,14 @@
+#Makefile for Using_oVirt
+
+XML_LANG = en-US
+BRAND = oVirt
+
+#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
+TRANSLATIONS = $(XML_LANG) $(OTHER_LANGS)
+
+#CHUNK_FIRST = 0
+#CHUNK_SECTION_DEPTH = 1
+
+COMMON_CONFIG = /usr/share/publican
+include $(COMMON_CONFIG)/make/Makefile.common
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Appendix-B.xml b/Using_the_oVirt_Admin_UI/en-US/Appendix-B.xml
new file mode 100644
index 0000000..18af05b
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Appendix-B.xml
@@ -0,0 +1,42 @@
+<?xml version='1.0'?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<appendix id="Appendix-B">
+
+ <title>oVirt Parts and Connections</title>
+ <para>This document provides a high-level view of oVirt's moving parts.
+ </para>
+ <para>oVirt consists of the following bits
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>A stripped-down Fedora build that installs and runs off a CD, a usb key, or a ramdisk (over PXE) on a physical host. The build contains all the necessary pieces to support hosting and managing virtual machines on the host.</para>
+ </listitem>
+ <listitem><para>A web-based management UI application for oVirt hosts, users, and vms</para></listitem>
+ <listitem><para>The FreeIPA ldap/kerberos identity, policy, and audit application</para></listitem>
+ </orderedlist>
+ <para>This is how the parts work together:</para>
+ <itemizedlist>
+ <listitem>
+ <para>The FreeIPA application handles kerberos administration, authentication, and authorization for the entire app.</para>
+ </listitem>
+ <listitem>
+ <para>An oVirt host image is provided with the application. On boot (via cdrom, flash drive, or PXE), the host image loads its keytab and kerberos configuration from the oVirt management application and announces itself.</para>
+ </listitem>
+ <listitem>
+ <para>The oVirt management application authenticates with FreeIPA and can then communicate with the libvirtd running on each oVirt host via an encrypted SASL connection using the libvirt SASL infrastructure.</para>
+ </listitem>
+ <listitem>
+ <para>An iSCSI target, running on any machine reachable from the oVirt host, provides disk storage for oVirt guests. The oVirt host will automatically make the storage targets on the iSCSI server it is configured for available for oVirt guest installs.</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/logical_arch2.gif" format="GIF"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+</appendix>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Appendix.xml b/Using_the_oVirt_Admin_UI/en-US/Appendix.xml
new file mode 100644
index 0000000..39ac1e4
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Appendix.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0'?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<appendix id="Using_oVirt-Revision_Histor">
+ <appendixinfo>
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </appendixinfo>
+ <title>Revision History</title>
+ <para>
+ Empty para tags are not allowed (they break translations), so this boilerplate text is here to keep place until actual text is added. (Note: the file is currently not included in built versions of this book: edit the appropriate xi:include in 'Using_oVirt.xml' to include this file.)
+ </para>
+</appendix>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Author_Group.xml b/Using_the_oVirt_Admin_UI/en-US/Author_Group.xml
new file mode 100644
index 0000000..98def69
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Author_Group.xml
@@ -0,0 +1,15 @@
+<?xml version='1.0'?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<authorgroup>
+ <author>
+ <firstname>Susan</firstname>
+ <surname>Burgess</surname>
+ <affiliation>
+ <orgname>Red Hat</orgname>
+ <orgdiv>Engineering Content Services</orgdiv>
+ </affiliation>
+ <email>sburgess at redhat.com</email>
+ </author>
+</authorgroup>
diff --git a/Using_the_oVirt_Admin_UI/en-US/Book_Info.xml b/Using_the_oVirt_Admin_UI/en-US/Book_Info.xml
new file mode 100644
index 0000000..b15f225
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Book_Info.xml
@@ -0,0 +1,30 @@
+<?xml version='1.0'?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<bookinfo id="Using_oVirt-Product_Name_and_Version">
+ <title>Using oVirt</title>
+ <subtitle>A Guide to the oVirt User Interface</subtitle>
+ <edition>0.1</edition>
+ <pubsnumber>1</pubsnumber>
+ <productname>oVirt</productname>
+ <productnumber>0.6</productnumber>
+ <abstract><para>This online help describes how to use the oVirt Administration User Interface, a means of managing virtual machines and resources.</para></abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" />
+ </imageobject>
+ <textobject><phrase>Logo</phrase></textobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <copyright>
+ <year>&YEAR;</year>
+ <holder>&HOLDER;</holder>
+ </copyright>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
+
+
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Chapter.xml b/Using_the_oVirt_Admin_UI/en-US/Chapter.xml
new file mode 100644
index 0000000..db1ee48
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Chapter.xml
@@ -0,0 +1,25 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Using_oVirt-Test">
+ <title>Test</title>
+ <para>
+ This is a test paragraph
+ </para>
+ <section id="Using_oVirt-Test-Section_1_Test">
+ <title>Section 1 Test</title>
+ <para>
+ Test of a section
+ </para>
+ </section>
+
+ <section id="Using_oVirt-Test-Section_2_Test">
+ <title>Section 2 Test</title>
+ <para>
+ Test of a section
+ </para>
+ </section>
+
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Getting-Started.xml b/Using_the_oVirt_Admin_UI/en-US/Getting-Started.xml
new file mode 100644
index 0000000..63c1bea
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Getting-Started.xml
@@ -0,0 +1,259 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Getting-Started">
+ <title>Getting Started</title>
+ <para>
+ This section enables you to start using the oVirt Administration User Interface. The oVirt Administration User Interface is a graphical interface that enables you to easily manage hosts, storage, user permissions and virtual machines. The parts of the interface and how they work together are described in this section. The user interface provides visibility to your virtualized system at a glance, providing immediate information on loads, performance and usage.
+ </para>
+
+ <section id="Logging-on">
+ <title>Logging on</title>
+ <para> oVirt relies on Kerberos for security. Log in using the <command>kinit </command> command:
+ </para>
+ <para>For example,
+<screen>kinit ovirtadmin at PRIV.OVIRT.ORG
+</screen>
+ Enter the password when prompted.
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>In the developer installation, described in <xref linkend="Installing-the-Admin-UI"/> this is not necessary since the developer appliance maintains a continuous kerberos ticket for the ovirtadmin user.
+ </para>
+ </note>
+ <para>In the bundled installation, kinit as ovirtadmin. This is effectively logging in as the superuser.
+ </para>
+<!-- Hide until implemented - post beta???
+ <section id="The-oVirt-Dashboard">
+ <title>The oVirt Dashboard</title>
+ <para>
+ The Dashboard provides an overview of the resources, their availability, and current levels of load. The overview consists of summaries and graphical displays. In addition to the summary of resources, there are detailed lists of hardware resource pools, hosts and storage servers. To use the dashboard, click the topmost icon in the Navigator. Use the Navigator to browse to the required resource pool. Resources appear as nodes on the browser tree in the Navigator.
+ </para>
+
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Dashboard.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>The Dashboard is the recommended place to add new resources and new users at the highest level. You can do the following directly from the dashboard. </para>
+ <itemizedlist>
+ <listitem><para>Go to a hardware pool. Refer <xref linkend="Managing-the-Hardware"/></para></listitem>
+ <listitem><para>Investigate the detailed usage and performance of a particular host. Refer <xref linkend="Viewing-hardware-resources"/></para></listitem>
+ <listitem><para>Add a new hardware pool. Refer <xref linkend="Creating-Hardware-Resource-Pools"/></para></listitem>
+ <listitem><para>Set up User Access. Refer <xref linkend="Managing-User-Permissions"/></para></listitem>
+ </itemizedlist>
+ </section>
+-->
+ </section>
+
+ <section id="Understanding-the-interface">
+ <title>Using the Interface</title>
+ <para>The user interface enables you to control large or small numbers of managed nodes, create virtual machines and interact with them, and manage users.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <section id="Parts-of-the-interface">
+ <title>About the Interface</title>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/oVirtInterface.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>The ovirt Administration User Interface consists of the following components:</para>
+ <itemizedlist>
+ <listitem>
+ <para>The Resource Navigator on the left-hand side of the page. The Resource Navigator contains:</para>
+ <itemizedlist>
+ <listitem>
+ <para>A browser tree consisting of hardware and virtual machine pools.</para>
+
+ </listitem>
+ <listitem>
+ <para>A toolbar with buttons to Add or Delete Hardware or Virtual Machine Pools.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>The Content Pane on the right-hand side of the page. The Content Pane displays the contents of a resource pool, and menus and toolbars that enable you to manage the resources. In some instances, there may also be descriptions and graphics that add meaning to the lists. It contains:</para>
+ <itemizedlist>
+ <listitem>
+ <para>A menu bar across the top of the page that contains from left to right:</para>
+ <itemizedlist>
+ <listitem>
+ <para>The Product Name
+ </para>
+ </listitem>
+ <listitem>
+ <para>Contextual Menu Options. There are two menus, the Hardware Resource menu and the Virtual Machines menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Search
+ </para>
+ </listitem>
+ <listitem>
+ <para>Online Help
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>The main contents pane that displays information about the selected resource or resource pool. The contents panel may contain lists, descriptions or graphic information, check boxes, action buttons and tabs depending on the context.
+ The contents panel of the Activity page presents a richness of contextual information that enables you to manage, monitor and view the virtualized universe at a glance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The Details pane is the lower part of the content pane. The Details pane displays information about the selected item in the main content pane.
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="Using-the-Navigator">
+ <title>Using the Navigator</title>
+ <para>The Navigator enables you to locate resources ( that is, hardware pools and virtual machine pools) easily and quickly, displaying the pools as nodes in their existing context. You can also use the Navigator to add or delete hardware pools or virtual machine pools.</para>
+ <para>The Navigator displays the hardware and virtual resources in a hierarchy. Hardware Pools can have several levels of hardware and virtual machine subpools. To view sub-pools, click the Expand button on the parent pool.</para>
+
+ <para>Hardware Pools display as follows:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/IconHWPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>Virtual Machine Pools nodes display as follows:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/IconVMPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>To navigate to a resource:</para>
+ <orderedlist>
+ <listitem>
+ <para>Click on the hardware pool in the navigator. The <guilabel>Summary</guilabel> page and the Hardware resource menu display in the Content Pane.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click on the Expand icon to display the virtual machine pools, or hardware sub-pools attached to the hardware resource.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click on a Virtual Machine Pool in the Navigator. The <guibutton>Summary </guibutton>page and the Virtual Machines menu display in the Content Pane.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>To manage resources from the Navigator, you can use the
+ Navigator menu at the bottom of the panel.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/navpanelicons.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ From left to right the buttons are:
+ <itemizedlist>
+ <listitem><para>Add Hardware Pool</para></listitem>
+ <listitem><para>Add Virtual Pool</para></listitem>
+ <listitem><para>Delete Selected Pool</para></listitem>
+ </itemizedlist>
+ Navigate to the appropriate Hardware pool on the browser tree:</para>
+ <itemizedlist>
+ <listitem>
+ <para>To add a hardware pool or sub-pool, click the <guibutton>Add Hardware</guibutton> button. The new hardware pool displays in the Navigator.
+ </para>
+ </listitem>
+ <listitem>
+ <para>To add a virtual machine pool, click the <guibutton>Add Virtual Machine Pool</guibutton> button. The new Virtual Machine pool displays below the selected node.
+ </para>
+ </listitem>
+ <listitem>
+ <para>To delete a pool, click the Delete Selected Pool button. The selected pool is removed from the browser tree.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ <section id="Using-the-Content-Pane">
+ <title>Using the Content and Detail Panes</title>
+ <para>The Content Pane on the right-hand side of the oVirt Administration User Interface displays information on resources or resource collections, and enables management of the resources by means of menus, toolbars and buttons. It displays information and menus appropriate to the pool selected in the Navigator. For example:
+ <itemizedlist>
+ <listitem>
+ <para>If a hardware pool is selected in the Navigator, the Hardware Resources Menu and toolbar display in the Contents Pane.</para>
+ </listitem>
+ <listitem>
+ <para>If a virtual machine pool is selected in the Navigator, the Virtual Machines Pool menu and toolbar display in the Contents Pane.</para>
+ </listitem>
+
+ </itemizedlist>
+ The Details pane on the lower part of the Content pane displays details on the item selected in the Content pane.</para>
+ <section id="Using-the-menus">
+ <title>The Menubar and Toolbar</title>
+ <para>The menubar and toolbar are part of the Content Pane that occupies the right panel of the OUI page. The menus available are:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Hardware Resource menu and toolbar
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/HWresourceMenu.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Virtual Resource menu and toolbar</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/VRMenu.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>These menus are described fully in the following sections.</para>
+ </section>
+
+ </section>
+ </section>
+
+
+ <section id="Using-Online-Help">
+ <title>Using Online Help</title>
+ <para>This online help can be accessed from the oVirt Administration User Interface. Click the <guibutton>Help</guibutton> button on the top right hand corner of the page.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/helpbutton.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </section>
+
+ <section id="Using-Search">
+ <title>Using Search</title>
+ <para>Search can be accessed from the oVirt Administration User Interface. Enter the search term in the Search text box and click the <guibutton>Search</guibutton> icon on the top right hand corner of the page. Use Search to quickly find hardware pools or virtual machine pools. oVirt will find the resource and display it on the Content pane and Navigator.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/helpbutton.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </section>
+
+
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Glossary.xml b/Using_the_oVirt_Admin_UI/en-US/Glossary.xml
new file mode 100644
index 0000000..320a0b6
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Glossary.xml
@@ -0,0 +1,390 @@
+<?xml version='1.0'?>
+<!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+ ]>
+
+<glossary id="Glossary">
+ <para>
+ This glossary is intended to define the terms used in the oVirt Administration User Interface Guide.
+ </para>
+ <glossdiv id="glos-Virtualization-A">
+ <title>A</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-B">
+ <title>B</title>
+ <glossentry id="glos-Virtualization-B-Bare_metal">
+ <glossterm>Bare-metal</glossterm>
+ <glossdef>
+ <para>
+ The term bare-metal refers to the underlying physical architecture of a computer. Running an operating system on bare-metal refers to dom0 (see) or a natively installed operating system.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-C">
+ <title>C</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-D">
+ <title>D</title>
+ <glossentry id="glos-Virtualization-D-dom0">
+ <glossterm>dom0</glossterm>
+ <glossdef>
+ <para>
+ Also known as the <xref linkend="glos-Virtualization-H-Host" /> or host operating system.
+ </para>
+ <para>
+ <command>dom0</command> refers to the host instance of Red Hat Enterprise Linux running the <xref linkend="glos-Virtualization-H-hypervisor" /> which facilitates virtualization of guest operating systems. Dom0 runs on and manages the physical hardware and resource allocation for itself and the guest operating systems.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-D-Domains">
+ <glossterm>Domains</glossterm>
+ <acronym>dom0 or domU</acronym>
+ <glossdef>
+
+ <para>
+ <xref linkend="glos-Virtualization-D-domU" /> and <xref linkend="glos-Virtualization-D-Domains" /> are both domains. Domains run on the <xref linkend="glos-Virtualization-H-hypervisor" />. The term domains has a similar meaning to <xref linkend="glos-Virtualization-V-Virtual_Machines" /> and the two are technically interchangeable. A domain is a Virtual Machine.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-D-domU">
+ <glossterm>domU</glossterm>
+ <glossdef>
+ <para>
+ <command>domU</command> refers to the guest operating system which run on the host system (<xref linkend="glos-Virtualization-D-Domains" /> ).
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-E">
+ <title>E</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-F">
+ <title>F</title>
+ <glossentry id="glos-Virtualization-F-Full_Virtualization">
+ <glossterm>Full Virtualization</glossterm>
+ <glossdef>
+ <para>
+ You can deploy Red Hat Virtualization in one of two choices: full virtualization or paravirtualization. Full virtualization provides total abstraction of the underlying physical system (<xref linkend="glos-Virtualization-B-Bare_metal" /> ) and creates a new virtual system in which the guest operating systems can run. No modifications are needed in the guest OS or application (the guest OS or application is not aware of the virtualized environment and runs normally). Para-virtualization requires user modification of the guest operating systems that run on the virtual machines (these guest operating systems are aware that they are running on a virtual machine) and provide near-native performance. You can deploy both paravirtualization and full virtualization across your virtualization infrastructure.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-F-Fully_Virtualized">
+ <glossterm>Fully Virtualized</glossterm>
+ <glossdef>
+ <para>
+ See <xref linkend="glos-Virtualization-F-Full_Virtualization" />.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-G">
+ <title>G</title>
+ <glossentry id="glos-Virtualization-G-Guest_System">
+ <glossterm>Guest System</glossterm>
+ <glossdef>
+ <para>
+ Also known as <xref linkend="glos-Virtualization-D-domU" />.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-H">
+ <title>H</title>
+ <glossentry id="glos-Virtualization-H-Hardware_Virtual_Machine">
+ <glossterm>Hardware Virtual Machine</glossterm>
+ <acronym>HVM</acronym>
+ <glossdef>
+ <para>
+ See <xref linkend="glos-Virtualization-F-Full_Virtualization" />
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-H-hypervisor">
+ <glossterm>hypervisor</glossterm>
+ <glossdef>
+ <para>
+ The hypervisor is the software layer that abstracts the hardware from the operating system permitting multiple operating systems to run on the same hardware. The hypervisor runs on the host system allowing virtual machines to run on the host's hardware as well.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-H-Host">
+ <glossterm>Host</glossterm>
+ <glossdef>
+ <para>
+ The host operating system, also known as <xref linkend="glos-Virtualization-D-Domains" />.
+ </para>
+ <para>
+ The host environment runs the software for <xref linkend="glos-Virtualization-F-Fully_Virtualized" /> and <xref linkend="glos-Virtualization-F-Fully_Virtualized" /> guest systems.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-I">
+ <title>I</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-J">
+ <title>J</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-K">
+ <title>K</title>
+ <glossentry>
+ <glossterm>Kernel-based Virtual Machine</glossterm>
+ <acronym>KVM</acronym>
+ <glossdef>
+ <para>
+ KVM is a <xref linkend="glos-Virtualization-F-Full_Virtualization" /> kernel module which will be incorporated into future releases of Red Hat Enterprise Linux. KVM is presently available in the fedora Liunx distribution and other Linux distributions.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Kerberos</glossterm>
+
+ <glossdef>
+ <para>
+ Kerberos is the name of a computer network authentication protocol, that allows individuals communicating over a non-secure network to prove their identity to one another in a secure manner. It is aimed primarily at a client-server model, and it provides mutual authentication — both the user and the server verify each other's identity. Kerberos protocol messages are protected against eavesdropping and replay attacks. The protocol was named after the Greek mythological character Kerberos (or Cerberus), known in Greek mythology as being the monstrous three-headed guard dog of Hades.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-L">
+ <title>L</title>
+ <glossentry>
+ <glossterm>LDAP</glossterm>
+ <glossdef>
+ <para>The Lightweight Directory Access Protocol, or LDAP is an application protocol for querying and modifying directory services running over TCP/IP.
+ A directory is a set of objects with similar attributes organized in a logical and hierarchical manner.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-M">
+ <title>M</title>
+ <glossentry id="glos-Virtualization-M-Migration">
+ <glossterm>Migration</glossterm>
+ <glossdef>
+ <para>
+ See also <xref linkend="glos-Virtualization-R-Relocation" />
+ </para>
+ <para>
+ Migration refers to the process of moving a para-virtualized guest images from one Red Hat Virtualization server to another. This other server could be on the same server or a different server, including servers in other locations.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-M-MAC_Addresses">
+ <glossterm>MAC Addresses</glossterm>
+ <glossdef>
+ <para>
+ The Media Access Control Address is the hardware address for a Network Interface Controller. In the context of virtualization MAC addresses must be generated for virtual network interfaces with each MAC on your local domain being unique.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-N">
+ <title>N</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-O">
+ <title>O</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-P">
+ <title>P</title>
+ <glossentry id="glos-Virtualization-P-Para_virtualization">
+ <glossterm>Para-virtualization</glossterm>
+ <glossdef>
+ <para>
+ Para-virtualization uses a special kernel, sometimes referred to as the xen kernel or kernel-xen to virtualize another environment while using the hosts libraries and devices. A para-virtualized installation will have complete access to all devices on the system. Para-virtualization is significantly faster than full virtualization can can be effectively used for load balancing, provisioning, security and consolidation advantages.
+ </para>
+ <para>
+ As of Fedora 9 a special kernel will no longer be needed. Once this patch is accepted into the main Linux tree all linux kernels after that version will have para-virtualization enabled or available.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-P-Para_virtualized_drivers">
+ <glossterm>Para-virtualized drivers</glossterm>
+ <glossdef>
+ <para>
+ Para-virtualized drivers are device drivers that operate on fully virtualized linux guests. These drivers greatly increase performance of network and block device I/O for fully virtualized guests.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-Q">
+ <title>Q</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-R">
+ <title>R</title>
+ <glossentry id="glos-Virtualization-R-Relocation">
+ <glossterm>Relocation</glossterm>
+ <glossdef>
+ <para>
+ Another term for <xref linkend="glos-Virtualization-M-Migration" /> usually used to describe moving a virtual machine image across geographic locations.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-S">
+ <title>S</title>
+ <glossentry>
+ <glossterm>Single Sign-On</glossterm>
+ <glossdef>
+ <para>Single sign-on (SSO) is a method of access control that enables a user to authenticate once and gain access to the resources of multiple software systems. Single sign-off is the reverse process whereby a single action of signing out terminates access to multiple software systems.
+ </para>
+ <para>
+ In a homogeneous IT infrastructure or at least where a single user entity authentication scheme exists or where a user database is centralized, single sign-on is a visible benefit. All users in this infrastructure would have a single set of authentication credentials; for example, in an organization which stores its user database in a LDAP database. All information processing systems can use such an LDAP database for user authentication and authorization, which in turn means single sign-on has been achieved organization-wide.
+ </para>
+ <para>
+ Benefits of single sign-on include reducing the amount of internal fraud by malicious employee contact, convenience of password access, security on all levels of entry/exit/access to systems, and centralized reporting for compliance adherence.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-T">
+ <title>T</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-U">
+ <title>U</title>
+ <glossentry>
+ <glossterm>UUID</glossterm>
+ <glossdef>
+ <para>Universally Unique Identifier is an identifier standard standardized by the Open Software Foundation (OSF) as part of the Distributed Computing Environment (DCE). The intent of UUIDs is to enable distributed systems to uniquely identify information without significant central coordination. Thus, anyone can create a UUID and use it to identify something with reasonable confidence that the identifier will never be unintentionally used by anyone for anything else. Information labeled with UUIDs can therefore be later combined into a single database without needing to resolve name conflicts.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-V">
+ <title>V</title>
+ <glossentry id="glos-Virtualization-V-Virtual_cpu">
+ <glossterm>Virtual cpu</glossterm>
+ <acronym>vcpu</acronym>
+ <glossdef>
+ <para>
+ A system running Red Hat Virtualization has a number of virtual cpus, or vcpus. The number of vcpus is finite and represents the total number of vcpus that can be assigned to guest virtual machines.
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="glos-Virtualization-V-Virtual_Machines">
+ <glossterm>Virtual Machines</glossterm>
+ <acronym>vcpu</acronym>
+ <glossdef>
+ <para>
+ A virtual machine is a software implementation of a physical machine or programming language (for example the Java Runtime Environment or LISP). Virtual machines in the context of virtualization are operating systems running on virtualized hardware.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-W">
+ <title>W</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-X">
+ <title>X</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-Y">
+ <title>Y</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="glos-Virtualization-Z">
+ <title>Z</title>
+ <glossentry>
+ <glossterm>test</glossterm>
+ <glossdef>
+ <para>
+ No current entries.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+</glossary>
diff --git a/Using_the_oVirt_Admin_UI/en-US/Installing-the-Admin-UI.xml b/Using_the_oVirt_Admin_UI/en-US/Installing-the-Admin-UI.xml
new file mode 100644
index 0000000..5ab492c
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Installing-the-Admin-UI.xml
@@ -0,0 +1,405 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Installing-oVirt">
+ <title>Installing the oVirt Administration User Interface</title>
+
+ <para>There are currently two ways to install oVirt. The developer version allows you to start using oVirt quickly with the minimal amount of hardware and configuration. The bundled version allows you to manage physical hardware. It requires a separately cabled network and a minimum of 2 machines to demonstrate the full power of oVirt.
+ </para>
+ <para>oVirt can also be installed and integrated manually with the services that come as part of the bundled install (including FreeIPA and postgres), however the manual method is not described in this document.</para>
+ <para>This guide, the oVirt Administration User Interface Online Help, distinguishes between commands to be run as root and commands to be run as a regular user.
+ <itemizedlist>
+ <listitem>
+ <para>Commands to be run as root are prefixed with a # symbol.</para>
+ </listitem>
+ <listitem>
+ <para>Commands to be run as a regular user are prefixed with a $ symbol.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </para>
+
+ <section id="Installing-the-Admin-UI">
+ <title>Installing oVirt Developer Version</title>
+ <para>
+ This section describes how to install the developer version of the oVirt Administration User Interface. Installing the developer version is the fastest way to get oVirt up and running and become familiar with the user interface. The developer version of the oVirt appliance cannot be used to manage physical hosts. To manage physical hosts, you must install the bundled version of the appliance, using the instructions in <xref linkend="Installing-the-Bundled-Appliance"/>.
+ </para>
+ <section id="Prerequisites-for-Installation">
+ <title>Prerequisites for the Development Version</title>
+ <para>
+ The developer version has the following prerequisites:
+ </para>
+ <itemizedlist>
+
+ <listitem>
+ <para>A machine that supports hardware virtualization. This machine is called a host machine throughout the rest of the document.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Fedora 9 must be installed on the host machine with the latest versions of the following:
+ <itemizedlist>
+ <listitem>
+ <para>kernel version >= 2.6.24</para>
+ </listitem>
+ <listitem>
+ <para>kvm version >= 60</para>
+ </listitem>
+ <listitem>
+ <para>libvirt >= 0.4.1-3</para>
+ </listitem>
+ <listitem>
+ <para>virt-manager</para>
+ </listitem>
+ <listitem>
+ <para>virt-viewer</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The Fedora 9 repository install tree or boot CD or DVD.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ <section id="Preparing-for-Installation">
+ <title>Preparing to Install the Developer Version</title>
+ <para>
+ The following steps prepare your host machine for a successful installation of the oVirt Administration User Interface.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Ensure that the host machine supports full hardware virtualization. If you have an Intel processor use this command:
+<screen>
+# cat /proc/cpuinfo | grep vmx
+</screen>
+ or if you have an AMD processor use this command:
+<screen>
+# cat /proc/cpuinfo | grep svm
+</screen> </para>
+ </listitem>
+ <listitem>
+ <para>Ensure that the correct bare metal kernel is available.
+<screen>
+# uname -r
+2.6.24.14107.fc9
+</screen> </para>
+ </listitem>
+ <listitem>
+ <para>Ensure that the <filename>kvm</filename>, <filename>libvirt </filename>and <filename>virt-manager</filename> packages are installed on the host machine.
+
+<screen>
+# rpm -q libvirt kvm virt-manager
+</screen> </para>
+ </listitem>
+ <listitem>
+ <para>Ensure that the host system has <filename>kvm</filename>, and <filename>kvm_intel</filename> or <filename>kvm_amd modules</filename> are loaded. For example,
+<screen>
+# lsmod | grep kvm
+ kvm_intel 29677 0
+ kvm 88609 1 kvm_intel
+</screen>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+ </section>
+
+ <section id="Installing-the-Appliance">
+ <title>Installing the Appliance</title>
+ <para>This section describes how to install the developer version using the pre-built appliance provided on the oVirt website download page.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>You must be the root user to perform the installation.</para>
+ </note>
+ <orderedlist>
+ <listitem>
+ <para>Download the <ulink url="http://ovirt.org/download/ovirt-developer-appliance-0.91-1-x86_64.tar"> appliance</ulink> script onto the host machine.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Uncompress the image to <filename>/var/lib/libvirt/images/</filename>
+<screen># tar xf ovirt-developer-appliance-0.91-1-*.tar -C /var/lib/libvirt/images/</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Run the <filename>create-wui-appliance.sh</filename> script to create the virtual machine:</para>
+<screen>
+# cd /var/lib/libvirt/images/ovirt-developer-appliance-*; bash create-wui-appliance.sh -d "`pwd`" -v
+</screen>
+ </listitem>
+ <listitem>
+ <para>Remove the list of known hosts:
+<screen>
+#rm -Rf ~/.ssh/known_hosts
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Start the virtual machine named <filename>developer</filename>.
+<screen>
+virsh start developer
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Start up some fake managed nodes. These are additional KVM guests
+ on the same host machine, but they act as if they were separate
+ physical nodes. You can use up to 3 fake managed nodes, named
+ node3, node4, and node5. To start the
+ nodes:
+<screen>
+# virsh start node3
+# virsh start node4
+# virsh start node5
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Invoke the main oVirt page by running Firefox on the guest.
+
+<screen>
+# ssh -fY root at 192.168.50.2 firefox -no-remote
+</screen>
+ Enter the root password: <code>ovirt</code>
+ </para>
+ <para>A browser window opens displaying the oVirt User Administration Interface.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>To connect to the console of a virtual machine running on a managed node:
+<screen>
+# ssh -fY root at 192.168.50.2 virt-viewer -c qemu+tcp://node3.priv.ovirt.org/system VM_NAME
+</screen>
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <note id="Kickstart-Note">
+ <title>Note</title>
+ <para>The kickstart can be copied to a local webserver
+ and modified so that the repos referenced in the kickstart point to local
+ mirrors. In this case, the command is:
+<screen>
+# create-wui-appliance.sh -t http://foo/f9-x86_64 -k http://foo/wui-rel-x86_64.ks -v
+</screen>
+ </para>
+ </note>
+
+ </section>
+</section>
+ <section id="Installing-the-Bundled-Appliance">
+ <title>Installing oVirt on a Physical Network</title>
+ <para>Set up the bundled oVirt appliance if you wish to manage physical hosts. This version allows you to manage physical hardware. It requires a minimum of 2 machines and a separately cabled network.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>You must be the root user to perform the installation.</para>
+ </note>
+ <section id="Prerequisites-Bundled-Installation">
+ <title>Prerequisites</title>
+ <para>There are a number of prerequisites for the bundled install:</para>
+ <itemizedlist>
+ <listitem>
+ <para>A machine that supports hardware virtualization. This machine is called a host machine throughout the rest of the document.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The management host machine must have at least two network interfaces.</para>
+ </listitem>
+ <listitem>
+ <para>The managed nodes are one or more additional machines that support hardware virtualization. These machines are the physical machines on which VMs are run.</para>
+ </listitem>
+ <listitem>
+ <para>Fedora 9 must be installed on the host machine with the following:
+ <itemizedlist>
+ <listitem>
+ <para>kernel version >= 2.6.24</para>
+ </listitem>
+ <listitem>
+ <para>kvm version >= 60</para>
+ </listitem>
+ <listitem>
+ <para>libvirt >= 0.4.1-3</para>
+ </listitem>
+ <listitem>
+ <para>virt-manager</para>
+ </listitem>
+ <listitem>
+ <para>virt-viewer</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The Fedora 9 repository install tree or boot CD or DVD.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <section id="Setting-up-the-hardware">
+ <title>Setting up the Hardware</title>
+ <para>This section describes how to set up the hardware for a simple bundled oVirt installation.</para>
+ <orderedlist>
+ <listitem>
+ <para>Set up the management node to enable it to run the management console as a KVM guest, and take over the second network card (for example, eth1) for a private oVirt network.</para>
+ </listitem>
+ <listitem>
+ <para>Set up the managed nodes. Connect the managed nodes to the same network as the second network interface on the management host.</para>
+ </listitem>
+ <listitem><para>Set up the private network. This step is fully automated by <command>create-wui-appliance.sh</command>.</para>
+ </listitem>
+ <listitem><para>Set up storage.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+ <section id="Steps-installing-the-Bundled-Appliance">
+ <title>Installing the Appliance</title>
+ <para>This section describes how to install the pre-built appliance from the oVirt website download page to manage physical hardware. Ensure that you have a free eth1 network interface so that the bridge works properly.
+ </para>
+
+ <orderedlist>
+ <listitem>
+ <para>Download the <ulink url="http://ovirt.org/download/ovirt-developer-appliance-0.91-1-x86_64.tar">appliance</ulink> script onto the host machine.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Uncompress the image to <filename>/var/lib/libvirt/images/</filename>
+<screen># tar xf ovirt-developer-appliance-0.91-1-*.tar -C /var/lib/libvirt/images/</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Run the <filename>create-wui-appliance.sh</filename> script to create the virtual machine:
+<screen># cd /var/lib/libvirt/images/ovirt-developer-appliance-*; bash create-wui-appliance.sh -d "`pwd`" -b
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Remove the list of known hosts:
+<screen>
+#rm -Rf ~/.ssh/known_hosts
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Start the virtual machine.
+<screen>
+virsh start bundled
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Start up some managed nodes.
+<screen>
+# virsh start node3
+# virsh start node4
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Invoke the main oVirt page by running Firefox on the guest.
+
+<screen>ssh -fY root at 192.168.50.2 firefox -no-remote
+</screen>
+ Enter the root password: <code>ovirt</code>
+ </para>
+ <para>A browser window opens displaying the oVirt User Administration Interface.</para>
+ </listitem>
+ <listitem>
+ <para>To connect to the console of a virtual machine running on a managed node:
+<screen>
+# ssh -fY root at 192.168.50.2 virt-viewer -c qemu+tcp://node3.priv.ovirt.org/system VM_NAME
+</screen>
+
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <note id="Kickstart-Note1"><title>Note</title>
+ <para>The kickstart can be copied to a local webserver
+ and modified so that the repos referenced in the kickstart point to local
+ mirrors. In this case, the command is:
+<screen>
+# create-wui-appliance.sh -t http://foo/f9-x86_64 -k http://foo/wui-rel-x86_64.ks -b
+</screen>
+ </para>
+ </note>
+ </section>
+</section>
+
+<section id="create-wui-appliance">
+ <title>About create-wui-appliance.sh</title>
+ <para>create-wui-appliance is the pre-built appliance that is available from the oVirt website download page. Use this appliance to install either version of oVirt.</para>
+ <para>If you have not already done so, you can download the <ulink url="http://ovirt.org/download/ovirt-developer-appliance-0.91-1-x86_64.tar"> appliance</ulink> onto the host machine, and follow the instructions in either <xref linkend="Installing-the-Admin-UI"/> or <xref linkend="Installing-the-Bundled-Appliance"/> to install the appliance.
+ </para>
+ <table>
+ <title>create-wui-appliance.sh Parameters</title>
+ <tgroup cols="1">
+ <thead><row><entry><para>Usage</para></entry></row>
+ </thead>
+ <tbody><row>
+ <entry>
+ <para>
+ <command>create-wui-appliance.sh -i install_iso | -t install_tree [-d image_dir] [-a x86_64|i686]
+ </command>
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ <tgroup cols="2" >
+ <thead>
+ <row>
+ <entry>
+ <para>Parameter</para>
+ </entry>
+ <entry><para>Description</para>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>-i</entry>
+ <entry>Location of installation ISO (required if -t not present)</entry>
+ </row>
+ <row>
+ <entry>-t</entry>
+ <entry>Location of installation tree (required if -i not present)</entry>
+ </row>
+ <row>
+ <entry>-k</entry>
+ <entry>URL of kickstart file for use with installation tree</entry>
+ </row>
+ <row>
+ <entry>-d</entry>
+ <entry>Directory to place virtual disk (default: /var/lib/libvirt/images)</entry>
+ </row>
+ <row>
+ <entry>-a</entry>
+ <entry>Architecture for the virtual machine (default: x86_64)</entry>
+ </row>
+ <row>
+ <entry>-v</entry>
+ <entry>Install in developer mode</entry>
+ </row>
+ <row>
+ <entry>-b</entry>
+ <entry>Install in bundled mode </entry>
+ </row>
+ <row>
+ <entry>-h</entry>
+ <entry>Display this help and exit</entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Introduction-to-oVirt.xml b/Using_the_oVirt_Admin_UI/en-US/Introduction-to-oVirt.xml
new file mode 100644
index 0000000..c905173
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Introduction-to-oVirt.xml
@@ -0,0 +1,145 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Introduction-to-oVirt">
+ <title>Introduction</title>
+
+ <para>oVirt is the next step in Red Hat's Virtualization platform for any application, anywhere, anytime because it provides a simple yet powerful way to manage virtual machines. With the enormous flexibility and choice that the Red Hat Virtualization platform affords, you need an easy, visual way of managing virtual machines (VMs) that could be running thousands of software applications, deployed in a myriad ways, using different operating systems and hardware platforms.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/logical_arch2.gif" format="GIF"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>From running a few VMs on a single host to managing thousands of VMs over hundreds of hosts on a network, oVirt makes virtualization easy and scales to meet your needs. The oVirt Administration User Interface runs on any platform with a web browser that can authenticate with a kerberos server.
+ </para>
+ <section id="Overview">
+ <title>Overview</title>
+
+ <para>oVirt allows centralized management of your computing environment, reducing the costs of management of the infrastructure and allowing people to focus on their core tasks instead of the infrastructure itself.
+ </para>
+ <para>The oVirt host image is a small, stateless Fedora build that can run from a flash drive, a CDROM, or entirely in RAM via PXE. It enables users to manipulate virtual machines, provides a secure authenticated channel (GSSAPI/SASL2) for remote access and allows easy management and allocation of storage.
+
+
+ oVirt has several components:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/whatisovirtNEW.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ <itemizedlist>
+
+ <listitem>
+ <para>A host browser and status update daemon that keeps the oVirt
+ database in sync with the available hosts and virtual machines on
+ the network, updating the oVirst database when new hosts appear, old hosts disappear, and VMs change their status;
+ </para>
+ </listitem>
+ <listitem>
+ <para>A task engine that reads a task queue from the oVirt database and
+ makes appropriate libvirt calls, updating the database on the
+ success or failure of those tasks;
+ </para>
+ </listitem>
+ <listitem>
+ <para>A monitoring agent that receives performance data from oVirt
+ hosts and stores it for display in the user interface;
+ </para>
+ </listitem>
+ <listitem><para>An administration node that allows users to manage virtual
+ machines, view usage and performance, manage hosts and storage
+ servers, manage user permissions, and perform many other
+ management tasks.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
+
+
+ <section id="Prerequisites">
+ <title>Prerequisites</title>
+ <para>To use the oVirt Administration UI, the following is required:</para>
+ <itemizedlist>
+ <listitem>
+ <para>An oVirt host image. On boot (via cdrom, flash drive, or PXE), the host image loads its keytab and kerberos configuration from the oVirt management application or from local storage and announces itself.
+ </para>
+ </listitem>
+ <listitem>
+ <para>A kerberos/LDAP server for authentication and authorization (oVirt ships with FreeIPA).
+ </para>
+ </listitem>
+ <listitem><para>A database for storing oVirt data. oVirt comes bundled with Postgres. Future releases will support additional databases.</para></listitem>
+ <listitem>
+ <para>DNS/DHCP services on the local LAN. If not available, oVirt can provide them for oVirt hosts over a private network if desired.</para>
+ </listitem>
+ <listitem>
+ <para>Network attached storage (NFS, iSCSI or Fibre Channel) for hosting oVirt Guests running on any machine reachable from the oVirt host. The oVirt host will automatically make the storage targets on the iSCSI server it is configured for available for oVirt guest installs.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+ <section id="Users">
+ <title>Types of Users</title>
+ <para>Understanding what kind of user you are will help you to quickly identify the features of oVirt that are of the most benefit to you, and the sections where you can find this information. There are two kinds of users, developers and users. Users can range from individuals, to small
+ businesses or labs to enterprise large-scale deployments.</para>
+ <section id="Open-Source-Developer">
+ <title>Open Source Developers</title>
+ <para>Red Hat supports open source developers and so we'd like ourselves and others to be able to use the oVirt system easily and effectively. Follow the instructions in
+ <xref linkend="Installing-the-Admin-UI"/> to quickly get a development system up and running. Once a system is up and running you can use the oVirt management interface to create new Virtual Machines to run on the managed node.
+ </para>
+ </section>
+ <section id="Enterprise-users">
+ <title>Users</title>
+ <para>Medium to large scale enterprises who need to manage large numbers of virtual machines and physical hosts need a system that scales to their usage. oVirt is designed to scale from a small number of virtual machines and hosts to thousands of virtual machines and hosts. There are three different types of users in the enterprise:</para>
+ <itemizedlist>
+ <listitem><para>Hardware Administrators</para>
+ <para>
+ <itemizedlist>
+ <listitem><para>Rack physical hosts and provision them with the oVirt managed node image</para></listitem>
+ <listitem><para>Create Virtual Pools for teams and assign hosts and storage to teams of users</para></listitem>
+ <listitem><para>Group hosts and storage in physical networks</para></listitem>
+ <listitem><para>Connect network attached storage (iSCSI, NFS)</para></listitem>
+ <listitem><para>Manage top-level user group membership</para></listitem>
+ <listitem><para>View usage and loading of resources, prepare hosts for downtime by migrating VMs</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Team administrators</para>
+ <itemizedlist>
+ <listitem>
+ <para>Manage user quotas, permissions, and subgroups for team hardware</para>
+ </listitem>
+ <listitem>
+ <para>Monitor physical hosts for resource issues, bottlenecks</para>
+ </listitem>
+ <listitem>
+ <para>Maintain available team VM install images/appliances</para>
+ </listitem>
+ <listitem>
+ <para>Define SLA for team hardware, in terms of: CPU availability; memory usage; network bandwidth</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>oVirt Users</para>
+ <para>
+ <itemizedlist>
+ <listitem><para>Connect to VMs from the browser interface with a console plug-in</para></listitem>
+ <listitem><para>Create, destroy, pause, resume, save, restore VMs on a team hardware collection</para></listitem>
+ <listitem><para>Configure VMs as virtual clusters </para></listitem>
+ <listitem><para>View current and historic performance information for VMs to determine SLA needs</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Managing-User-Permissions.xml b/Using_the_oVirt_Admin_UI/en-US/Managing-User-Permissions.xml
new file mode 100644
index 0000000..68c0328
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Managing-User-Permissions.xml
@@ -0,0 +1,181 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Managing-User-Permissions">
+ <title>Managing User Access</title>
+ <para>oVirt's user access management is integrated with the Kerberos infrastructure that provides a single sign-on environment. oVirt is tightly integrated with the freeIPA project, so that administrators can authenticate, authorize, and audit their virtual resources across the enterprise. Permissions are defined by User Roles which allocate specific permissions to users in hardware or virtual pools. oVirt accesses the LDAP database for valid users, who can then be set up with permissions for oVirt resources. </para>
+ <para>Users must be logged in via Kerberos to access oVirt. oVirt user permissions determine the hardware and virtual pools that are accessible to the user.</para>
+
+
+ <section id="User-Roles">
+ <title>Assigning Permissions with User Roles</title>
+ <para>oVirt has four hierarchical permission levels that are reflected in four User Roles. The top-level role implies all lower levels and so on, with each role assuming all the permissions of the roles beneath it. Thus, the top-level role of Super Admin has its own permissions as well as all the permissions of all the roles beneath it. In contrast, because Monitor is the lowest role, it has only its own permissions.
+ Permission levels are attached to "pools", either hardware pools or VM resource
+ pools, and they are inherited by subpools of those pools. Individual VMs do not have permission levels.
+ </para>
+ <section id="How-User-Roles-Work">
+ <title>How User Roles Work</title>
+ <para>oVirt's hierarchical permissions model means that user permissions are set by the hardware administrator at the top level, and the finer detail is added by the team administrator:</para>
+ <itemizedlist>
+ <listitem><para>Rather than specifying which box a particular application is running on, hardware administrators dedicate machines and storage to discrete groups, which then treat those resources generically.</para></listitem>
+ <listitem><para>Team administrators determine hardware and virtual resource usage based on software-defined resource limits and SLA definitions.</para></listitem>
+ <listitem><para>Users manage their own VMs, within their assigned quota/SLA, as required without requiring administrator attention.</para></listitem>
+ </itemizedlist>
+ <section id="oVirt-User-Roles">
+ <title>User Roles in oVirt</title>
+ <para>Users are granted access in a particular role within a hardware or virtual pool. However users can be granted access to multiple pools, and can have different roles in different pools.
+ </para>
+ <para>User Roles are:</para>
+ <itemizedlist>
+ <listitem><para>User Admin or Super Admin</para>
+ <para> A User Admin or Super Admin user can grant permissions and
+ quota to other users, along with all other permissions. Typically the hardware administrator is the Super Admin, who can assign permissions to groups or teams, allowing access to resources and storage.
+ </para></listitem>
+ <listitem><para>Administrator</para>
+ <para> An Administrator can create and delete hardware
+ pools and virtual machine resource pools, and create, delete, and
+ manipulate the objects in those pools (hosts, storage servers, quota,
+ VMs,).
+ This includes the ability to create and delete
+ VMs in a VM resource pool.
+ Typically the team administrator is the Administrator. The Administrator must understand and determine the physical and virtual resource that a team requires for their work.
+ </para>
+ </listitem>
+ <listitem><para>User</para>
+ <para>A user can access a VM page and do the following (with a VM in a VM resource pool):</para>
+ <itemizedlist>
+ <listitem><para>start</para></listitem>
+ <listitem><para>stop</para></listitem>
+ <listitem><para>suspend</para></listitem>
+ <listitem><para>resume</para></listitem>
+ <listitem><para>restore</para></listitem>
+ </itemizedlist>
+
+ <para>
+ Typically, most users who need to use the VMs for their work will have this role.</para>
+ </listitem>
+ <listitem><para>Monitor or View</para>
+ <para>A user with Monitor or View privileges can only view objects in the assigned VM pool.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </section>
+
+
+ <section id="Assigning-Resource-Pool-Permissions">
+ <title>Managing Users</title>
+
+ <para>
+ The oVirt Administration User Interface provides the ability to manage users. Users are created within a hardware or virtual resource pool context, and cannot be moved between resource pools. However, user roles can be changed as necessary by the team or hardware administrator.
+ </para>
+ <section id="Using-the-User-Access-Tab">
+ <title>The User Access Page</title>
+ <para>Before you can assign user permissions, you must be logged into the oVirt Administration User Interface as the administrator. This gives you the requisite privileges.</para>
+ <orderedlist>
+
+ <listitem><para>kinit as the kerberos admin user. (If you are using the developer installation this is "ovirtadmin").</para></listitem>
+ <listitem><para>Browse to the oVirt Administration User Interface.</para></listitem>
+ <listitem><para>Navigate either to top-level, or required resource or virtual pool and click <guimenu>User Access</guimenu> on the menubar.</para>
+ <para>The <guilabel>User Access</guilabel> page displays. The list of existing users, their roles and status display in the list.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/UserAccessTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>You can add users from the LDAP database, change user roles within a pool and remove users for the selected pool.</para>
+ </listitem>
+
+ </orderedlist>
+ </section>
+ <section id="Adding-Users">
+ <title>Adding Users to a Pool</title>
+ <para>To add a user to a hardware or virtual resource pool:</para>
+ <orderedlist>
+ <listitem><para>Select the appropriate Hardware or Virtual Resource pool.</para></listitem>
+ <listitem><para>From the menu, select <guimenuitem>User Access</guimenuitem>. The <guilabel>User Access</guilabel> page displays.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/UserAccessTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para></listitem>
+ <listitem><para>Click <guibutton>Add User</guibutton> on the tool bar. The <guilabel>Add User</guilabel> dialog box displays.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewUser.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para></listitem>
+ <listitem><para>Select the appropriate <guilabel>Role</guilabel> from:</para>
+ <itemizedlist>
+ <listitem><para>Super Admin</para></listitem>
+ <listitem><para>Administrator</para></listitem>
+ <listitem><para>User</para></listitem>
+ <listitem><para>Monitor</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>Select the <guilabel>User</guilabel> name from the <guilabel>Users</guilabel> listbox.</para></listitem>
+ <listitem><para>Click <guibutton>Add User</guibutton>.</para></listitem>
+ <listitem><para>The new user's User name displays in the list of existing users.</para></listitem>
+ </orderedlist>
+ </section>
+ <section id="Changing-User-Roles">
+ <title>Changing Users Roles</title>
+ <para>Users may need to change their roles as required by project requirements o or staff movement. For example, a team administrator may be required to take on the super admin role, or a person with monitor privileges may need user privileges. </para>
+ <para>To change a User role:</para>
+ <orderedlist>
+ <listitem><para>Select the appropriate Hardware or Virtual Resource pool.</para></listitem>
+ <listitem><para>From the menu bar, select <guimenuitem>User Access</guimenuitem>. The <guilabel>User Access</guilabel> page displays a list of existing users.</para></listitem>
+ <listitem><para>Select the check box to the left of the user name.
+ </para></listitem>
+ <listitem><para>Click <guibutton>Change Role</guibutton> on the tool bar. The <guilabel>Change Role menu</guilabel> displays if at least one user was selected in the previous step.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/UserChangeRole.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Click the required role from the list:</para>
+ <itemizedlist>
+ <listitem><para>Super Administrator</para></listitem>
+ <listitem><para>Administrator</para></listitem>
+ <listitem><para>User</para></listitem>
+ <listitem><para>Monitor</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>The User name appears in the list of existing users on the page with the changed role.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="Revoke-User-Permissions">
+ <title>Revoking User Permissions</title>
+ <para>You can revoke a user's permission to view or work in a hardware or virtual resource pool.</para>
+ <para>To revoke user permissions:</para>
+ <orderedlist>
+ <listitem><para>Select the appropriate Hardware or Virtual Resource pool.</para></listitem>
+ <listitem><para>From the menu, select <guimenuitem>User Access</guimenuitem>. The <guilabel>User Access</guilabel> page displays with a list of existing users.</para></listitem>
+ <listitem><para>Select the check box to the left of the user name.</para></listitem>
+ <listitem>
+ <para>Click <guimenuitem>Remove</guimenuitem> on the tool bar. A message displays prompting you to select at least one user if no user was selected in the previous step.
+ </para>
+ </listitem>
+ <listitem>
+ <para>A message prompts you to confirm. Click <guibutton>OK</guibutton>.</para>
+ </listitem>
+ <listitem>
+ <para>A message confirms the removal and the user name no longer appears in the list of existing users.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ </section>
+
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Managing-VMs.xml b/Using_the_oVirt_Admin_UI/en-US/Managing-VMs.xml
new file mode 100644
index 0000000..97fc154
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Managing-VMs.xml
@@ -0,0 +1,306 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Managing-VMs">
+ <title>Managing Virtual Resources</title>
+ <para>
+ Managing virtual resources is a simple task using oVirt's Administration User Interface. Virtual resources include virtual pools and virtual machines. Virtual machines run inside the Virtual Machine Pools. This section describes how to view, set up and manage virtual resources using the oVirt Administration User Interface.
+ Typically, hardware administrators or team administrators set up the virtual resources, users start and manage the virtual machines required for their work.
+
+ </para>
+ <section id="Working-with-Virtual-Resource-Pools">
+ <title>Working with Virtual Machine Pools</title>
+ <para>Virtual Machines reside in virtual pools. While users can use and manage virtual machines according to their needs, team administrators would typically set up the virtual pools. Virtual pools are set up within a hardware resource pool, and once created cannot be moved to another hardware resource pool, so it is important to provide the virtual resource pool with the correct hardware resources.</para>
+ <section id="Viewing-Virtual-Pools">
+ <title>Viewing Virtual Pools</title>
+ <para>
+ The oVirt Administration UI page provides an overview of the resources, their availability, and current levels of load of the entire system.
+ </para>
+ <para>To view the resources of a specific Virtual Machine Pool:</para>
+ <orderedlist>
+ <listitem>
+ <para>Use the Navigator panel to select the Virtual Machine Pool node.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click the pool name and the <guilabel>Summary </guilabel>Page displays on the Virtual Contents Pane on the right-hand side of the oVirt Administration User Interface.
+ </para>
+ <para>
+
+
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/ViewVMResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The Virtual Machine Pool page displays a list of the virtual machines and the following information about the pool quota:
+ <itemizedlist>
+ <listitem><para>CPU - Usage and Availability</para></listitem>
+ <listitem><para>Memory - Usage and Availability</para></listitem>
+ <listitem><para>NICs - Usage and Availability</para></listitem>
+ <listitem><para>Number of Virtual Machines - Usage and Availability</para></listitem>
+ <listitem><para>Storage - Usage and Availability</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>To see details of the virtual machines, click <guimenuitem>Virtual Machines</guimenuitem> on the menu bar. The Virtual Machines page displays the Virtual Machine toolbar and the list of virtual machines, if any, in the resource pool.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/VMTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+
+ <listitem><para>You can use the Virtual Machine toolbar to add, delete and manage the virtual machines within the pool.</para></listitem>
+ </orderedlist>
+
+ </section>
+
+ <section id="Creating-Virtual-Resource-Pools">
+ <title>Creating Virtual Machine Pools</title>
+ <para>Creating a Virtual Machine Pool in which the virtual machines can run in an optimal fashion is crucial for system performance. For example, the hardware administrator might need to create a VM Resource Pool out of 5 physical nodes and a set of iSCSI targets. Once the hardware resources are set up the next step is to create the Virtual Machine Pools.
+ </para>
+
+ <orderedlist>
+ <title>To create a resource pool from the Navigator Panel</title>
+ <listitem>
+ <para>Use the Navigator panel to select the Hardware Resource Pool node within which to create the Virtual Machine Pool. The <guilabel>Summary</guilabel> page and the Hardware Resource menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewVMResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Navigator toolbar appears at the bottom on the panel. Click <guimenuitem>Add Virtual Machine Pool</guimenuitem>. The <guimenu>Add Virtual Machine Pool</guimenu> dialog box displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewVMPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Enter the name of the new resource pool and click the <guibutton>Create Virtual Machine Pool</guibutton> button. A message indicates that the virtual machine resource pool was successfully created. Click <guibutton>OK</guibutton>
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>You must enter a name for the new Virtual Machine Resource Pool. oVirt validates the name field and prompts you to enter a name before the resource pool is created.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>You can now add virtual machines and users to the new Virtual Machine Pool. Click the appropriate option on the menubar. Adding virtual machines is described later in this section.</para>
+ </listitem>
+ </orderedlist>
+ <formalpara>
+ <title>Virtual Machine Pool Names</title>
+ <para>Names can be any combination of alphanumeric characters, spaces and special characters. Valid name lengths are 1-256 characters. It is recommended that you use meaningful names for the resource pools.</para>
+ </formalpara>
+ </section>
+ <section id="Deleting-Virtual-Resource-Pools">
+ <title>Deleting Virtual Machine Pools</title>
+ <para>From time to time you will need to remove resource pools; for example, a project no longer requires a particular Virtual Machine Pool, or you need to optimise performance of the data center. Virtual Machine Pools are removed from the Navigator panel.
+ </para>
+ <note><title>Note</title>
+ <para>You can only remove a Virtual Machine Pool if there are no virtual machines in the pool.</para>
+ </note>
+ <orderedlist>
+ <title>To delete a resource pool:</title>
+ <listitem>
+ <para>Use the Navigator panel to select the required Virtual Machine Pool node. The <guilabel>Summary</guilabel> page and the Virtual Resource menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewVMResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Navigator toolbar appears at the bottom on the panel. Click <guimenuitem>Delete Selected Pool</guimenuitem>. A message appears prompting you to confirm that you wish to delete the selected resource. Click <guibutton>OK</guibutton>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The Virtual Machine Pool is removed and no longer displays in the Navigator Panel.</para>
+ </listitem>
+
+ </orderedlist>
+ </section>
+ </section>
+
+ <section id="Working-with-Virtual-Machines">
+ <title>Working with Virtual Machines</title>
+ <para>Virtual machines are created within Virtual Machine Pools.</para>
+ <section id="Viewing-Virtual-Machines">
+ <title>Viewing Virtual Machines</title>
+ <para>
+ Navigate to an existing Virtual Machine Pool and click the <guimenuitem>Virtual Machines</guimenuitem> tab to view, add or manage virtual machines. The Virtual Resource page and toolbar displays. The Virtual Machines toolbar enables you to add virtual machines (VMs), use the VMs and delete VMs.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewVMPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>The Virtual machines page displays a list of existing virtual machines. The following information is displayed for each virtual machine:
+ <itemizedlist>
+ <listitem><para>Description - the name of the VM</para></listitem>
+ <listitem><para>UUID - the unique identifier</para></listitem>
+ <listitem><para>CPUs - the number of CPUs assigned to the VM</para></listitem>
+ <listitem><para>Memory - the amount of memory assigned to the VM</para></listitem>
+ <listitem><para>vNic Mac Address - </para></listitem>
+ <listitem><para>State - the status of the VM</para></listitem>
+ <listitem><para>Load - the current load </para></listitem>
+ </itemizedlist>
+ </para>
+ </section>
+
+ <section id="Adding-Virtual-Machines">
+ <title>Adding Virtual Machines</title>
+ <para>
+ Adding a virtual machine includes specifying the name and defining the resources and quotas that the VM can use.
+ </para>
+ <orderedlist>
+ <listitem><para>To create a virtual machine, navigate to the appropriate virtual pool and select the <guimenuitem>Virtual Machines</guimenuitem> tab.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/VMTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+
+ <listitem><para>Click <guimenuitem>Add Virtual Machine</guimenuitem> from the Virtual Machine Pool toolbar. The <guilabel>Add a Virtual Machine</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddVM.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>Enter the following information:</para>
+ <itemizedlist>
+ <listitem><para>Name of the Virtual Machine</para></listitem>
+ <listitem><para>Operating System</para>
+ <para>Select from</para>
+ <itemizedlist>
+ <listitem><para>Fedora 9</para></listitem>
+ <listitem><para>Windows</para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>CPUs - Enter the maximum number of CPUs the VM is permitted to use.</para>
+ <para>oVirt indicates the maximum that is permitted at start-up. Entering a value in this field is mandatory.</para></listitem>
+ <listitem><para>Memory (MB) - Enter the maximum amount of memory that the VM is permitted to use.</para>
+ <para>oVirt indicates the maximum that is permitted at start-up. Entering a value in this field is mandatory.</para>
+ </listitem>
+ <listitem><para>Select the Storage Servers that the VM is permitted to use. The Storage table displays the Alias, Size and Type of Storage that is available.</para></listitem>
+ <listitem><para>The network VNIC is entered by default. You can change this if necessary.</para></listitem>
+ <listitem><para>The UUID is assigned by oVirt. You can change this if necessary.</para></listitem>
+ <listitem><para>Select the Start VM Now check box to start the VM immediately. The VM will start depending on the availability of resources. </para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>Click <guibutton>Add Virtual Machine</guibutton>. A message indicates that the VM was successfully created. Click <guibutton>OK</guibutton>.</para>
+ <para>The VM appears in the list of VMs on the Virtual Machine Pool page.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewVMPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para></listitem>
+ </orderedlist>
+
+ </section>
+ <section id="Using-Virtual-Machines">
+ <title>Using Virtual Machines</title>
+ <orderedlist>
+ <listitem><para>
+ Navigate to an existing Virtual Machine Pool and click the Virtual Machines tab to view, add or manage virtual machines.
+ </para>
+
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/VMActions1.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the check box of a virtual machine and click the <guisubmenu>Actions</guisubmenu> option on the toolbar. The Actions menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/VMActions2.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>From the Actions menu you can do the following to a virtual machine:</para>
+ <itemizedlist>
+ <listitem><para>Start</para></listitem>
+ <listitem><para>Shutdown</para></listitem>
+ <listitem><para>Suspend</para></listitem>
+ <listitem><para>Resume</para></listitem>
+ <listitem><para>Save</para></listitem>
+ <listitem><para>Restore</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem><para>A <guilabel>Virtual Machine Actions Result</guilabel> dialog box displays, indicating the result or results of the Action. </para></listitem>
+ </orderedlist>
+ </section>
+ <section id="Deleting-Virtual-Machines">
+ <title>Deleting Virtual Machines</title>
+ <para>
+ Deletion of a virtual machine is a permanent action that cannot be undone.
+ </para>
+ <orderedlist>
+ <listitem><para>To delete a virtual machine, navigate to the appropriate virtual pool and select the <guimenuitem>Virtual Machines</guimenuitem> tab.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/DeleteVM1.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+ <listitem><para>Select the check box of the VM to be deleted.</para></listitem>
+ <listitem><para>Click <guimenuitem>Delete</guimenuitem> from the Virtual Machine Pool toolbar. A message prompts you to confirm the deletion. Click <guibutton>OK.</guibutton></para>
+ </listitem>
+ <listitem><para>A message indicates that the VM was successfully deleted.
+ The VM does not display in the list of VMs on the Virtual Machine Pool page.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/DeleteVM2.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </section>
+
+</section>
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Managing-the-Hardware.xml b/Using_the_oVirt_Admin_UI/en-US/Managing-the-Hardware.xml
new file mode 100644
index 0000000..176c317
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Managing-the-Hardware.xml
@@ -0,0 +1,720 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Managing-the-Hardware">
+ <title>Managing Hardware Resources</title>
+ <para>
+ This section describes how to set up and manage hardware resources. In a typical data center, a hardware administrator would need to:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem><para>Create Hardware Pools</para></listitem>
+ <listitem><para>Create Virtual Pools for teams and assign hosts and storage to teams of users</para></listitem>
+ <listitem><para>Group hosts and storage in physical networks</para></listitem>
+ <listitem><para>Connect network attached storage (iSCSI, NFS)</para></listitem>
+ <listitem><para>Manage top-level user group membership</para></listitem>
+ <listitem><para>View usage and loading of resources, prepare hosts for downtime by migrating VMs</para></listitem>
+ </itemizedlist>
+ </para>
+ <para>This section describes how a hardware administrator can perform the hardware related tasks of the above list in oVirt.</para>
+ <section id="Logging-in-as-the-hardware-admin">
+ <title>Logging in as the Hardware Administrator</title>
+ <para>
+ Before you can manage any hardware resources, you must be logged into the oVirt Administration User Interface as the administrator. This gives you the requisite privileges.
+ </para>
+ <orderedlist>
+
+ <listitem><para>kinit as the kerberos admin user. (If you are using the developer installation, the password is is "ovirtadmin").</para></listitem>
+ <listitem><para>Browse to oVirt Administration User Interface page.</para></listitem>
+ <listitem><para>The main page displays, with a summary of resources and lists of hardware pools, hosts and storage servers. On the left hand side of the page is the Navigator panel. Click the expand button on the default hardware pool. The resources display in a tree browser. On the right hand side is the Content Pane where details of the selected node and contextual menus display.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/oVirtInterface.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Use the Navigator panel to navigate to a Hardware (or Virtual Machine Pool). You can also use the Navigator menu to add or delete hardware (and virtual machine pools).</para>
+ </listitem>
+
+ </orderedlist>
+
+ </section>
+
+ <section id="Working-with-hardware-pools">
+ <title>Working with Hardware Pools</title>
+ <para>Setting up, managing and monitoring the hardware resources is the key role of a hardware administrator. While this can be a complex task in any environment, it can become even more complex in a data centre with virtualized servers, hosts and storage. However, oVirt's Administration User Interface enables hardware administrators to manage a virtualized system effectively and efficiently.</para>
+ <section id="Viewing-hardware-resources">
+ <title>Viewing Hardware Resources</title>
+ <para>
+ The oVirt Administration UI page provides an overview of the resources, their availability, and current levels of load of the entire system.
+ </para>
+ <para>To view the resources of a specific hardware pool:</para>
+ <orderedlist>
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click the pool name and the <guilabel>Summary </guilabel>Page displays on the Contents Pane on the right-hand side of the oVirt Administration UI.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The numbers and amounts of used and available memory, storage and virtual resources appear in both a graphical and list form. Information on network traffic is also displayed.</para>
+ <para>
+
+
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>To see details on the physical host machines, click <guimenuitem>Hosts</guimenuitem> on the menu bar. The Hosts page displays the list of hosts in the resource pool.</para>
+ <para>
+
+
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/ViewHosts.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>To see details on the storage in the pool, click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of storage servers in the resource pool.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/StorageTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </orderedlist>
+
+ </section>
+ <section id="Creating-and-Deleting-Hardware-Resource-Pools">
+ <title>Creating and Deleting Hardware Pools</title>
+ <para>Creating and deleting Hardware Pools is a simple task using oVirt's Administration User Interface.
+ </para>
+ <section id="Creating-Hardware-Resource-Pools">
+ <title>Creating Hardware Pools</title>
+ <para>Creating a hardware pool in which the virtual machines can run in an optimal fashion is crucial for system performance. For example, the hardware administrator might need to create a VM Resource Pool out of 5 physical nodes and a set of iSCSI targets. The resource pool would contain a
+ combined total of 10 processors, 20GB RAM, 100GB storage. The hardware administrator then assigns 3 users to this resource pool and assigns
+ constraints on those users, for example;
+ Each user may use 3 VCPUs, 30GB storage and 6GB RAM. However, the first step is to create the Hardware Pools.
+ </para>
+ <para>To do this you need to know the following:</para>
+
+ <itemizedlist>
+ <listitem><para>The number of hosts required</para></listitem>
+ <listitem><para>The number of processors required</para></listitem>
+ <listitem><para>The amount of storage required</para></listitem>
+ <listitem><para>The amount of RAM required</para></listitem>
+ <listitem><para>The permissions and privileges of the users</para></listitem>
+ </itemizedlist>
+
+ <orderedlist>
+ <title>To create a resource pool from the Navigator Panel</title>
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Navigator toolbar appears at the bottom on the panel. Click <guimenuitem>Add Hardware Pool</guimenuitem>. The <guimenu>Add Hardware Pool</guimenu> dialog box displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewHWPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Enter the name of the new resource pool and click the <guibutton>Create Hardware Pool</guibutton> button. A message indicates that the hardware pool was successfully created. Click <guibutton>OK</guibutton>
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>You must enter a name for the new hardware pool. oVirt validates the name field and prompts you to enter a name before the resource pool is created.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>You can now add hosts, storage, virtual machines and users to the new hardware pool. Click the appropriate option on the menubar. Adding hosts, storage and virtual machines is described later in this section.</para>
+ </listitem>
+ </orderedlist>
+ <formalpara>
+ <title>Hardware Pool Names</title>
+ <para>Names can be any combination of alphanumeric characters, spaces and special characters. Valid name lengths are 1-256 characters. It is recommended that you use meaningful names for the resource pools.</para>
+ </formalpara>
+ </section>
+ <section id="Deleting-Resource-Pools">
+ <title>Deleting Hardware Pools</title>
+ <para>From time to time you will need to remove hardware pools; for example, a project no longer requires a particular hardware pool, or you need to optimise performance of the data center. Hardware Pools are removed from the Navigator panel.
+ </para>
+ <para>To do this you need to ensure the following:</para>
+
+ <itemizedlist>
+ <listitem><para>There are no virtual machines in any sub-pools.</para></listitem>
+ <listitem><para>There are no virtual machine pools and virtual machine sub-pools in the pool or sub-pools.</para></listitem>
+ <listitem><para>There are no hardware resource sub-pools.</para></listitem>
+ </itemizedlist>
+
+ <orderedlist>
+ <title>To delete a resource pool:</title>
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool or sub-pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Navigator toolbar appears at the bottom on the panel. Click <guimenuitem>Delete Selected Pool</guimenuitem>. A message appears prompting you to confirm that you wish to delete the selected resource. Click <guibutton>OK</guibutton>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The hardware pool is removed and no longer displays in the Navigator Panel.</para>
+ </listitem>
+
+ </orderedlist>
+ <note><title>Note</title>
+ <para>If there are any sub-pools or virtual machines in any node beneath the resource pool, the resource pool will not be deleted.</para>
+ </note>
+ </section>
+ </section>
+ <section id="Adding-and-Removing-Physical-Hosts">
+ <title>Adding and Removing Physical Hosts</title>
+ <para>Creating and deleting hosts is a simple task using oVirt's Administration User Interface.</para>
+ <section id="Adding-Physical-Hosts">
+ <title>Adding Physical Hosts</title>
+ <para>As the hardware administrator you will frequently need to add physical hosts to new or existing resource pools.
+ </para>
+
+ <orderedlist>
+ <title>To add a host to an existing hardware pool:</title>
+ <listitem><para>Navigate to the hardware pool, click <guibutton>Hosts</guibutton> to view existing hosts.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHosts.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>From the <guimenu>Hosts</guimenu> toolbar, click <guimenuitem>Add Host</guimenuitem>. The <guimenu>Add Host</guimenu> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddHost.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>The <guilabel>Add Host</guilabel> dialog box displays the availability and usage statistics of the available hosts.
+ These include:
+ <itemizedlist>
+ <listitem><para>Host Name - The name of the host</para></listitem>
+ <listitem><para>UUID - The unique identifier of the host</para></listitem>
+ <listitem><para>Hypervisor Type - the type of hypervisor</para></listitem>
+ <listitem><para>CPUs - the number of processors in the host</para></listitem>
+ <listitem><para>Speed - the speed of the processors</para></listitem>
+ <listitem><para>RAM - the size of the memory, and the percentage currently in use</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem><para>Select an available host. An available host is any host that the user has permissions on and does not have any VMs currently running on it.</para></listitem>
+ <listitem><para>Select the check box of the hosts that you wish to add to the hardware pool. At least one check box must be selected for the <guibutton>Add Host</guibutton> button to be enabled.</para></listitem>
+ <listitem><para>Click <guibutton>Add Host</guibutton>. The host displays on the Summary Page of the hardware pool.</para></listitem>
+ <listitem><para>To view all the hosts in the hardware pool, Click <guibutton>Hosts</guibutton> on the menubar. The new host displays in the list of hosts on the Hosts Page of the hardware pool.</para></listitem>
+ </orderedlist>
+ </section>
+ <section id="Removing-Physical-Hosts">
+ <title>Removing Physical Hosts from a Hardware Pool</title>
+ <para>As the hardware administrator you will frequently need to remove physical hosts. Hosts are only removed from the specific hardware pool, they remain available for allocation to other pools, or to the same pool.
+ </para>
+
+ <orderedlist>
+ <title>To remove a host from an existing hardware pool:</title>
+ <listitem><para>Navigate to the hardware pool, click <guibutton>Hosts</guibutton> to view existing hosts.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHosts.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Select the check box of the host that you wish to delete.</para></listitem>
+ <listitem><para>From the <guimenu>Hosts</guimenu> toolbar, click <guimenuitem>Remove</guimenuitem>.
+ </para>
+ </listitem>
+ <listitem><para>A message displays indicating that the host was successfully moved. Click <guibutton>OK</guibutton>.</para></listitem>
+ <listitem><para>To view all the hosts in the hardware pool, Click <guibutton>Hosts</guibutton> on the menubar. The removed host does not display in the list of hosts on the Hosts Page of the hardware pool.</para></listitem>
+ </orderedlist>
+ <note><title>Note</title>
+ <para>The host will still appear in the list of Hosts in the <guilabel>Add Hosts</guilabel> dialog box, and can be assigned to hardware pools as required.</para></note>
+ </section>
+ </section>
+ <section id="Move-Hosts">
+ <title>Moving Hosts between Hardware Pools</title>
+ <para>This process shows how to move hosts into new or existing Hardware Pools. For example, you may need to do this to balance the load, improve performance for particular applications, or if hosts are being replaced or retired. </para>
+ <section id="Moving-Hosts-to-an-existing-hardware-resource-pool">
+ <title>Move Hosts to Existing Hardware Pools</title>
+ <para>To move hosts to existing Hardware Pools:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Hosts</guimenuitem> on the menu bar. The Hosts page displays the list of existing Hosts, and the Hosts toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHosts.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>On the Hosts page, select the check box of the hosts to be moved. If no hosts are selected, you will be prompted to select at least one host before the <guilabel>Move Hosts</guilabel> dialog box displays.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Move</guimenuitem> menu on the Hosts toolbar. The <guilabel>Move Hosts</guilabel> dialog box appears.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveHost.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>If necessary navigate to the destination resource pool node in the <guilabel>Move Hosts</guilabel> dialog box.</para></listitem>
+ <listitem><para>Click the destination resource pool node in the <guilabel>Move Hosts</guilabel> dialog box.</para></listitem>
+ <listitem><para>The selected host is removed from the current hardware pool, and the dialog box closes.</para></listitem>
+ <listitem><para>To view the hosts in the destination hardware pool, click the destination host node in the Navigator panel. The <guilabel>Summary</guilabel> page for the destination host resource pool displays.</para>
+ </listitem>
+ <listitem><para>Click <guibutton>Hosts</guibutton> on the menu bar. The moved host displays in the list of hosts for the destination hardware pool.</para></listitem>
+ </orderedlist>
+ </section>
+ <section id="Moving-Hosts-to-a-new-hardware-resource-pool">
+ <title>Move Hosts to a New Hardware Pool</title>
+ <para>You can use the <guilabel>Move Hosts</guilabel> dialog box to move hosts directly to a new hardware resource sub-pool. To move hosts to a new hardware resource sub-pool:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>In the Navigator panel, select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Hosts</guimenuitem> on the menu bar. The Hosts page displays the list of existing Hosts, and the Hosts toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHosts.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>On the Hosts page, select the check box of the hosts to be moved. If no hosts are selected, you will be prompted to select at least one host before the <guilabel>Move Hosts</guilabel> dialog box displays.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Move</guimenuitem> menu on the Hosts toolbar. The <guilabel>Move Hosts</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveHost.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+
+ <listitem><para>Click the <guibutton>Move to new Hardware Pool</guibutton> button in the <guilabel>Move Hosts</guilabel> dialog box. The <guilabel>Add New Hardware Pool</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveHostNewPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Enter the name of the new resource pool and click the <guibutton>Create Hardware Pool</guibutton> button. </para>
+ <note>
+ <title>Note:</title>
+ <para>You must enter a name for the new hardware pool. oVirt validates the name field and prompts you to enter a name before the resource pool is created.</para>
+ </note>
+ </listitem>
+ <listitem><para>The selected host is removed from the resource pool, and the dialog box closes.</para></listitem>
+ <listitem><para>To view the hosts in the destination hardware pool, click the destination host node in the Navigator panel. The <guilabel>Summary</guilabel> page for the destination host resource pool displays.</para>
+ </listitem>
+ <listitem><para>Click <guibutton>Hosts</guibutton> on the menubar. The moved host displays in the list of hosts on the Hosts Page of the destination hardware pool.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+ </section>
+ <section id="Managing-Storage-Servers">
+ <title>Managing Storage Servers</title>
+ <para>Setting up, managing and monitoring the storage is the key role of a hardware administrator. While this can be a complex task in any environment, it can become even more complex in a data centre with virtualized storage. oVirt's Administration User Interface provides hardware administrators with tools to assign and manage virtualized storage effectively and efficiently.</para>
+ <section id="Add-Storage">
+ <title>Adding Storage to the Resource Pool</title>
+
+ <para>This process shows how to add an existing storage server to an existing hardware pool using the Storage Tab. The Storage toolbar allows you to add a storage server, create storage servers, move servers and delete storage.</para>
+ <note>
+ <title>Note:</title>
+ <para>You can also add storage servers from the Summary page.
+ </para>
+ </note>
+
+ <orderedlist>
+ <listitem>
+ <para>In the Navigator panel, select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu display.
+ </para>
+ </listitem>
+
+ <listitem><para>From the menu bar, click the <guimenuitem>Storage</guimenuitem> tab. The Storage page and toolbar display.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/StorageTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Click <guilabel>Add Storage Server</guilabel> from the toolbar. The <guilabel>Add Storage Server</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddStorage.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ <para>The <guilabel>Add Storage</guilabel> dialog box displays the alias, IP and Type of the available Storage Servers:
+ <itemizedlist>
+ <listitem><para>Alias - The alias of the storage server</para></listitem>
+ <listitem><para>IP - The IP address of the storage server</para></listitem>
+ <listitem><para>Type - the type of hypervisor, either iSCSI or NFS</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem><para>Select the storage server is located.</para></listitem>
+ <listitem><para>Select the check box of the storage servers that you wish to add to the hardware pool. At least one storage server must be selected for the <guibutton>Add Selected Storage Pools</guibutton> button to be enabled.</para></listitem>
+ <listitem><para>Click <guibutton>Add Selected Storage Pools</guibutton>. The storage server displays on the Storage Page of the hardware pool.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddStorageView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="Adding-Storage-Servers">
+ <title>Creating Storage Servers</title>
+ <para>As the hardware administrator you may be required to provide additional storage servers to the system as more projects commence or grow to require more storage resources.
+ </para>
+
+ <orderedlist>
+ <title>To create a storage server:</title>
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click the pool name and the <guilabel>Summary </guilabel>Page displays on the Contents Pane on the right-hand side of the oVirt Administration UI.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The numbers and amounts of used and available memory, storage and virtual resources appear in both a graphical and list form.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>To see details on the storage in the pool, click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of storage servers in the resource pool.</para>
+ </listitem>
+
+ <listitem><para>From the menu bar, click the <guimenuitem>Storage</guimenuitem> tab. The Storage page and toolbar display.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/StorageTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Click <guilabel>Create Storage Server</guilabel> from the toolbar. The <guilabel>Add New Storage Server</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServer.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ <para>Enter the following in the <guilabel>Add New Storage Pool</guilabel> dialog box
+ <itemizedlist>
+ <listitem><para>Storage Type - iSCSI or NFS</para></listitem>
+ <listitem><para>IP Address</para></listitem>
+ <listitem><para>Port</para></listitem>
+ <listitem><para>Target</para></listitem>
+ </itemizedlist>
+ </para>
+ <note>
+ <title>Note</title>
+ <para>It is mandatory to provide details for each of the above fields.</para>
+ </note>
+ </listitem>
+ <listitem><para>Click <guibutton>Add Storage Server</guibutton>. The new storage server displays on the Storage Page of the hardware pool.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServerView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="Move-Storage-Servers">
+ <title>Moving Storage Servers between Hardware Pools</title>
+ <para>This process shows how to move storage servers into new or existing Hardware Pools. For example, you may need to do this to balance the load, improve performance for particular applications, or if storage servers are being replaced or retired. </para>
+ <section id="Moving-Storage-Servers-to-an-existing-hardware-resource-pool">
+ <title>Move Storage Servers to Existing Hardware Pools</title>
+ <para>To move storage to existing Hardware Pools:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu display.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of existing Storage Servers, and the Storage toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServerView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>On the Storage page, select the check box of the storage servers to be moved. If no storage servers are selected, you will be prompted to select at least one storage server before the <guilabel>Move Storage Server</guilabel> dialog box displays.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Move</guimenuitem> on the Storage Server toolbar. The <guilabel>Move Storage Server</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageServer.png" format="png"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Select the destination resource pool node in the <guilabel>Move Storage Server</guilabel> dialog box.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageServer1.png" format="png"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>The selected storage server is removed from the current hardware pool, and the dialog box closes.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageServerView.png" format="png"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>To view the storage server in the destination hardware pool, click the destination host node in the Navigator panel. The <guilabel>Summary</guilabel> page for the destination host resource pool displays.</para>
+ </listitem>
+ <listitem><para>Click <guibutton>Storage</guibutton> on the menu bar. The moved storage server displays in the list of storage servers for the destination hardware pool.</para></listitem>
+ </orderedlist>
+ </section>
+ <section id="Moving-Storage-Server-to-a-new-hardware-resource-pool">
+ <title>Move Storage Servers to a New Hardware Pool</title>
+ <para>You can also move a storage server directly to a new hardware resource sub-pool. To move a storage server to a new hardware resource sub-pool:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>In the Navigator panel, select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu displays.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of existing storage servers, and the Storage toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServerView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>On the Storage page, select the check box of the storage server to be moved. If no Storage Server are selected, you will be prompted to select at least one host before the <guilabel>Move Storage Server</guilabel> dialog box displays.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Move</guimenuitem> menu on the Storage Server toolbar. The <guilabel>Move Storage</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageServer.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+
+ <listitem><para>Click the <guibutton>Move to New Hardware Pool</guibutton> button in the <guilabel>Move Storage</guilabel> dialog box. The <guilabel>Add New Hardware Pool</guilabel> dialog box displays.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageNewPool.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Enter the name of the new resource pool and click the <guibutton>Create Hardware Pool</guibutton> button. A message indicates that the new resource pool has been successfully created. Click <guibutton>OK</guibutton>.
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>You must enter a name for the new hardware pool. oVirt validates the name field and prompts you to enter a name before the resource pool is created.</para>
+ </note>
+ </listitem>
+ <listitem><para>The selected storage server is removed from the resource pool, and the dialog box closes.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageNewPoolView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>To view the storage server in the destination hardware pool, click the destination host node in the Navigator panel. The <guilabel>Summary</guilabel> page for the destination host resource pool displays.</para>
+
+ </listitem>
+ <listitem><para>Click <guibutton>Storage</guibutton> on the menu bar. The moved storage server displays in the list on the Storage page of the destination hardware pool.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/MoveStorageNewPoolView1.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+ <section id="Delete-Storage-Servers">
+ <title>Deleting Storage Servers</title>
+ <para>This process shows how to remove storage servers. For example, you may need to do this if storage servers are being replaced or retired. There are two ways to do this, you can choose to remove a storage server from a particular hardware pool, or you may choose to delete it altogether.</para>
+ <section id="Removing-Storage-Servers-from-a-hardware-resource-pool">
+ <title>Removing Storage Servers from a Hardware Pool</title>
+ <para>Storage servers that are merely removed from a hardware pool remain available to be reassigned later, or assigned to other hardware pools. After removal they will still appear in the lists of assigned or unassigned storage servers, for example in the <guilabel>Add Storage Server</guilabel> dialog box.</para>
+ <para>To remove a storage server from a hardware pool:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu display.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of existing Storage Servers, and the Storage toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServerView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+ <listitem><para>On the Storage page, select the check box of the storage servers to be removed. If no storage servers are selected, you will be prompted to select at least one storage server when you click <guilabel>Remove</guilabel>.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Remove</guimenuitem> on the Storage Server toolbar. The storage server is removed and no longer appears on the page.</para>
+ </listitem>
+ <listitem><para>Click <guibutton>Storage</guibutton> on the menu bar. The removed storage server no longer displays in the list of storage servers for the hardware pool.</para></listitem>
+ </orderedlist>
+ <note>
+ <title>Note</title>
+ <para>To check if the storage server is still available, use the <guibutton>Add Storage Server</guibutton> button on the Storage toolbar. Refer <xref linkend="Add-Storage"/>.</para>
+ </note>
+ </section>
+ <section id="Deleting-Storage-Servers-from-a-hardware-resource-pool">
+ <title>Deleting Storage Servers from oVirt</title>
+ <para>Storage servers that are deleted from a hardware pool are also deleted from the system. After deletion they will no longer display in the lists of storage servers, for example in the <guilabel>Add Storage Server</guilabel> dialog box.</para>
+ <para>To delete a storage server from a hardware pool:</para>
+ <orderedlist>
+
+ <listitem>
+ <para>Use the Navigator panel to select the required hardware pool node. The <guilabel>Summary</guilabel> page and the Hardware Pool menu display.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Click <guimenuitem>Storage</guimenuitem> on the menu bar. The Storage page displays the list of existing Storage Servers, and the Storage toolbar displays.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/AddNewStorageServerView.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>On the Storage page, select the check box of the storage servers to be deleted. If no storage servers are selected, you will be prompted to select at least one storage server when you click <guilabel>Delete</guilabel>.</para>
+ </listitem>
+ <listitem><para>Click <guimenuitem>Delete</guimenuitem> on the Storage Server toolbar.</para></listitem>
+ <listitem><para>Click <guibutton>Storage</guibutton> on the menu bar. The deleted storage server no longer displays in the list of storage servers for the hardware pool.</para></listitem>
+ </orderedlist>
+ <note>
+ <title>Note</title>
+ <para>To check that the deleted storage server is no longer available, use the <guibutton>Add Storage Server</guibutton> button on the Storage toolbar. Refer <xref linkend="Add-Storage"/>.</para>
+ </note>
+ </section>
+ </section>
+</section>
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Preface.xml b/Using_the_oVirt_Admin_UI/en-US/Preface.xml
new file mode 100644
index 0000000..0ef7989
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Preface.xml
@@ -0,0 +1,91 @@
+<?xml version='1.0'?>
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<preface id="Using_oVirt-Preface">
+ <title>Preface</title>
+ <para>oVirt is an open cross-platform virtualization management system. oVirt provides a small image that runs on a host and provides virtualization services to VMs, and a web-based management interface that lets you manage hosts and storage, install and remove virtual machines and level resources across a large group of machines. oVirt scales from a small group of users with little need for access control and quota management, all the way up to hundreds or even thousands of hosts with robust control over grouping, permissions, and quotas.
+ </para>
+ <formalpara>
+ <title>About &PRODUCT; Administration User Interface</title>
+ <para>
+ &PRODUCT; Administration User Interface is a web-based management UI application for oVirt hosts, users, and virtual machines.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>About Using the &PRODUCT; Administration User Interface</title>
+ <para>The guide is provided as online help and as html pages. It describes how to perform a developer install of &PRODUCT; and how to use the interface to manage virtual hosts, users and virtual machines.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>The &PRODUCT; Documentation Suite</title>
+ <para>&PRODUCT; documentation suite provides information on installation, development of applications, and all the latest changes.
+ </para>
+ </formalpara>
+
+ <itemizedlist>
+ <listitem>
+ <para>&PRODUCT; Release Notes - this document contains release specific information and known issues with the beta release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Online Help - this document describes how to use the &PRODUCT; Administration User Interface.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Developer Installation Guide - this document describes how to install a developer version of &PRODUCT; correctly and quickly.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Production Installation Guide - this document describes how to install &PRODUCT; correctly and quickly. A production install of &PRODUCT; allows a user to manage physical hosts.
+ </para>
+ </listitem>
+ <listitem>
+ <para>&PRODUCT; Configuration Guide - this document describes how to configure &PRODUCT;
+ </para>
+ </listitem>
+ <listitem>
+ <para>Appliance Development Kit User's Guide - this document describes the &PRODUCT; ADK.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <formalpara>
+ <title>About the Audience</title>
+ <para> This documentation suite is intended for</para>
+ </formalpara>
+ <itemizedlist>
+ <listitem><para>Anyone who wants to manage virtual machines! oVirt is lightweight enough to work for a developer managing, say, a single host with four VMs, yet robust enough for a large organization managing tens of thousands of VMs. Although oVirt is developed using Fedora, oVirt is not tied to a particular platform. Solaris and Windows users can use the oVirt browser interface, and in the future the oVirt Administration Interface will run across platforms as well.</para></listitem>
+ <listitem>
+ <para>
+ Open Source Developers
+ who are prototyping and experimenting with &PRODUCT;. Important aspects are an easy installation of the system and the ability to make changes in order to build a community of users and developers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Users at the enterprise level: Hardware Administrators, team administrators and virtual machine users at large or small IT facilities.
+ <itemizedlist>
+ <listitem>
+ <para>Typically, hardware administrators can use oVirt to manage thousands of Virtual Machines running on thousands of Host systems, often with complex user roles involved.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Team administrators manage user quotas, permissions, and subgroups for team hardware, Monitors physical hosts, Maintains available team VMs, install images/appliances
+ </para>
+ </listitem>
+ <listitem><para>oVirt users create, destroy, and generally use VMs available to them after connecting to VMs from a browser interface.</para></listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
+ <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
+ <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </xi:fallback>
+ </xi:include>
+</preface>
diff --git a/Using_the_oVirt_Admin_UI/en-US/Quick-Start.xml b/Using_the_oVirt_Admin_UI/en-US/Quick-Start.xml
new file mode 100644
index 0000000..4b82532
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Quick-Start.xml
@@ -0,0 +1,171 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Quick-Start">
+ <title>Quick Start</title>
+ <para>
+ This section is intended for users who wish to start using oVirt quickly without reading the online help from end to end. While it is recommended that you do read this document, this section gives you a high level look at how to apply the oVirt's functionality to typical virtualization tasks.
+ This section provides examples of how you can use oVirt to set up a number of managed nodes and how to set up a team environment.
+ </para>
+ <section id="Create-a-Hardware-Pool">
+ <title>Create a Hardware Pool</title>
+ <para> oVirt enables a development team to access hardware, storage and virtual machines for a new project in a quick, efficient and balanced way. A development team requires hardware resources, storage and a number of virtual machines to proceed with their project. In this exercise, the hardware administrator sets up the hardware resources, the team administrator assigns user permissions, and the developers can define, start or stop the VMs.
+ </para>
+ <section id="Scenario-1">
+ <title>Scenario 1</title>
+
+ <para>The scenario is as follows, given five physical hosts and adequate networked storage:
+ <itemizedlist>
+ <listitem>
+ <para>Create a hardware pool for a team.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>In the hardware pool, make a set of VMs with appropriate resource allocations and limits for three developers working on a project.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Assign the developers appropriate permissions to use and manage their VMs.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>This exercise demonstrates the following tasks</para>
+ <itemizedlist>
+ <listitem><para>Authentication/authorization as admin</para></listitem>
+ <listitem><para>Host/storage resource display</para></listitem>
+ <listitem><para>Pool creation</para></listitem>
+ <listitem><para>Adding resources to a pool</para></listitem>
+ <listitem><para>VM resource pool creation</para></listitem>
+ <listitem><para>Assign user group to pool/user-group-perms system</para></listitem>
+ <listitem><para>Define resource limits and resource guarantees for pool members</para></listitem>
+ <listitem><para>Authentication/authorization as non-privileged user</para></listitem>
+ <listitem><para>Define VMs</para></listitem>
+ <listitem><para>Start/stop VMs</para></listitem>
+ <listitem><para>Install available OS image in VMs</para></listitem>
+ <listitem><para>View VM console</para></listitem>
+ <listitem><para>Enforce resource limits and resource guarantees</para></listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="Hardware-Admin">
+ <title>Set up the Hardware Pool</title>
+ <para>This process shows the steps taken by the hardware administrator</para>
+
+ <orderedlist>
+
+ <listitem><para>kinit as admin (ovirtadmin?)</para></listitem>
+ <listitem><para>Browse to oVirt UI</para></listitem>
+ <listitem><para>Navigate to top-level hardware pool, view available hosts and
+ storage</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/QS1-SummaryTab.jpg" format="JPG" scale="50%"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+ <listitem><para>Create team hardware pool</para>
+ <para>The Hardware Admin creates a VM Resource Pool out of 5 physical
+ nodes and a set of iSCSI targets. The resource pool contain a
+ combined total of 10 processors, 20GB RAM, 100GB storage.</para>
+ </listitem>
+ <listitem><para>Move hosts and storage to team pool</para></listitem>
+ <listitem><para>Create VMResourcePool for the project</para></listitem>
+ </orderedlist>
+
+ <orderedlist>
+ <title>Team Administrator</title>
+ <listitem><para>kinit as admin (ovirtadmin?)</para>
+ </listitem>
+ <listitem><para>Browse to oVirt UI</para>
+ </listitem>
+ <listitem><para>Navigate to team hardware pool, view available hosts and
+ storage</para>
+ </listitem>
+ <listitem><para>Give team members access to the project. Assigns 3 users to this resource pool and assigns constraints on those users </para>
+ </listitem>
+ <listitem><para>Give each team member appropriate resources to go with, or Each user may use 3 VCPUs, 30GB storage, 6GB RAM. </para>
+ <para>User A creates 6 VMs each using 5GB of disk, 2GB RAM and 1VCPU. Given his
+ resource constraints, he can only run 3 of them simultaneously, but
+ because he's got enough storage he is able to define 6, run 3 and leave 3
+ offline. If he brings down a VM, he can then fire up a different one.
+ So the limit shouldn't be on the # of virtual machines that a user can
+ create, but it should be on their resource consumption in terms of
+ storage/processor/memory.</para>
+ </listitem>
+ </orderedlist>
+
+ <orderedlist>
+ <title>User - Team Member</title>
+ <listitem><para>kinit as team member</para></listitem>
+ <listitem><para>Log in as a team member, create VMs in the new pool using available OS images (that is, pull down a menu to choose the OS that cobbler will install via PXE when the VM starts). Start/stop VMs, see console (via console plugin link), etc.</para></listitem>
+ <listitem><para>Attempt to start a VM which goes over quota, show that quota limits are enforced.</para></listitem>
+ </orderedlist>
+
+ </section>
+ </section>
+ <section id="QS-2">
+ <title>Create a team development box</title>
+ <para>Amy Admin is starting a project with 5 developers. The project requires a private network since it has a special authentication component. Amy needs to allocate and isolate 3 virtual machines to each developer, so that they can do network development that would otherwise be disruptive to the company network.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Amy logs into oVirt and selects a Group of hosts with several unallocated hosts.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin1.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>She selects the under-utilized / unallocated hosts.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin2.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>She moves the selected hosts to a new group.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin3.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>OR she could create a new resource group first and then add hosts and storage
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin4.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>The new group is created successfully</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin5.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Revision_History.xml b/Using_the_oVirt_Admin_UI/en-US/Revision_History.xml
new file mode 100644
index 0000000..f14cfd6
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Revision_History.xml
@@ -0,0 +1,42 @@
+<?xml version='1.0'?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<appendix id="appe-Publican-Revision_History">
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>1.0</revnumber>
+ <date>3rd September 2008</date>
+ <author>
+ <firstname>Susan</firstname>
+ <surname>Burgess</surname>
+ <email>sburgess at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Updates</member>
+ <member>TBD</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>.6-1</revnumber>
+ <date>Wednesday June 18th 2008</date>
+ <author>
+ <firstname>Susan</firstname>
+ <surname>Burgess</surname>
+ <email>sburgess at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Resolves: #232215</member>
+ <member>Need to have a BZ. Also, need a real bug#</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+</appendix>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Sample-oVirt-Scenarios.xml b/Using_the_oVirt_Admin_UI/en-US/Sample-oVirt-Scenarios.xml
new file mode 100644
index 0000000..60b9e9d
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Sample-oVirt-Scenarios.xml
@@ -0,0 +1,393 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="Sample-oVirt-Scenarios">
+ <title>Using oVirt - Sample Scenarios</title>
+<!--
+ <para>
+ > Task One overview: Given three physical hosts and adequate networked storage,
+ > > create a hardware pool for a team. In the hardware pool, make a set of
+ > > VMs with appropriate resource allocations and limits for three
+ > > developers working on a project. Assign the developers appropriate
+ > > permissions to use and manage their VMs.
+
+ > > Step-by-step:
+
+ * kinit as admin (ovirtadmin?)
+ * Browse to oVirt UI
+ * Navigate to top-level hardware pool, view available hosts and
+ storage
+ * Create team hardware pool
+ * Move hosts and storage to team pool
+ * Create VMResourcePool for the project
+ * Give team members access to the project
+ * Give each team member a 3-VM limit and appropriate resources to go
+ with
+
+ What does a 3-VM limit serve? I would think that it would be more
+ important to limit the number of simultaneous processors/total RAM
+ usage/total storage used (online and offline).
+
+ So the Hardware Admin might create a VM Resource Pool out of 5 physical
+ nodes and a set of iSCSI targets. The resource pool would contain a
+ combined total of 10 processors, 20GB RAM, 100GB storage.
+
+ The Hardware Admin then assigns 3 users to this resource pool and assigns
+ constraints on those users like the following:
+
+ Each user may use 3 VCPUs, 30GB storage, 6GB RAM.
+
+ User A creates 6 VMs each using 5GB of disk, 2GB RAM and 1VCPU. Given his
+ resource constraints, he can only run 3 of them simultaneously, but
+ because he's got enough storage he is able to define 6, run 3 and leave 3
+ offline. If he brings down a VM, he can then fire up a different one.
+
+ So the limit shouldn't be on the # of virtual machines that a user can
+ create, but it should be on their resource consumption in terms of
+ storage/processor/memory.
+
+ If you allow over commit of CPU/RAM, you might decide to allocate each
+ user 4VCPUs, 30GB storage and 8GB of RAM.
+
+ Does this all make sense???
+
+ * kinit as team member
+ * Log in as a team member, create VMs in the new pool using available
+ OS images (that is, pull down a menu to choose the OS that cobbler
+ will install via PXE when the VM starts). Start/stop VMs, see
+ console (via console plugin link), etc.
+
+ The drop down list will contain items like "Fedora 8, Fedora 8, RHEL5.1"
+ but in reality cobbler will be set to only serve out one OS to all MACs
+ booting to it, since we won't have tight integration with cobbler by the
+ Summit.
+
+ Cobbler will still need to be able to differentiate between boxes it
+ should let PXE boot to the oVirt Managed Node and boxes that it should let
+ PXE boot to the Fedora/RHEL OS install. This could be done by telling
+ cobbler have a default selection of "oVirt Managed Node" for hosts that do
+ not match a MAC filter.
+
+ Hosts that do match a MAC prefix (like lets say we create all virtual
+ machines with MAC address that start with FF or something like that) would
+ by default boot to the Fedora/RHEL install.
+
+ Following the provisioning of the VM, we'd need to provide a way to switch
+ the guest config to boot from hd instead of network.
+
+ * Attempt to start a VM which goes over quota, show that quota limits
+ are enforced.
+
+ Areas of the app this exercises:
+
+ * authentication/authorization as admin
+ * host/storage resource display
+ * pool creation
+ * adding resources to a pool
+ * vm resource pool creation
+ * assign user group to pool/user-group-perms system
+ * define resource limits and resource guarantees for pool members
+ * authentication/authorization as non-privileged user
+ * define VMs
+ * start/stop VMs
+ * install available OS image in VMs
+ * view* enforce resource limits and resource guarantees
+ -->
+ <para>
+ This section provides a high level look at how to apply the oVirt's functionality to typical virtualization tasks.
+ This section provides a number of examples of how you can use oVirt in a virtualized environment.
+ </para>
+ <section id="Create-a-Hardware-Pool">
+ <title>Create a Hardware Pool</title>
+ <para> oVirt enables a development team to access hardware, storage and virtual machines for a new project in a quick, efficient and balanced way. A development team requires hardware resources, storage and a number of virtual machines to proceed with their project. In this exercise, the hardware administrator sets up the hardware resources, the team administrator assigns user permissions, and the developers can define, start or stop the VMs.
+ </para>
+ <section id="Scenario-1">
+ <title>Scenario 1</title>
+
+ <para>The scenario is as follows, given five physical hosts and adequate networked storage:
+ <itemizedlist>
+ <listitem>
+ <para>Create a hardware pool for a team.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>In the hardware pool, make a set of VMs with appropriate resource allocations and limits for three developers working on a project.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Assign the developers appropriate permissions to use and manage their VMs.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>This exercise demonstrates the following tasks</para>
+ <itemizedlist>
+ <listitem><para>Authentication/authorization as admin</para></listitem>
+ <listitem><para>Host/storage resource display</para></listitem>
+ <listitem><para>Pool creation</para></listitem>
+ <listitem><para>Adding resources to a pool</para></listitem>
+ <listitem><para>VM resource pool creation</para></listitem>
+ <listitem><para>Assign user group to pool/user-group-perms system</para></listitem>
+ <listitem><para>Define resource limits and resource guarantees for pool members</para></listitem>
+ <listitem><para>Authentication/authorization as non-privileged user</para></listitem>
+ <listitem><para>Define VMs</para></listitem>
+ <listitem><para>Start/stop VMs</para></listitem>
+ <listitem><para>Install available OS image in VMs</para></listitem>
+ <listitem><para>View VM console</para></listitem>
+ <listitem><para>Enforce resource limits and resource guarantees</para></listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="Hardware-Admin">
+ <title>Set up the Hardware Pool</title>
+ <para>This process shows the steps taken by the hardware administrator</para>
+
+ <orderedlist>
+
+ <listitem><para>kinit as admin</para></listitem>
+ <listitem><para>Browse to the oVirt Administration User Interface</para></listitem>
+ <listitem><para>Navigate to top-level hardware pool, view available hosts and
+ storage</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/ViewHWResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ </listitem>
+ <listitem><para>Create team hardware pool</para>
+ <para>The Hardware Admin creates a VM Resource Pool out of 5 physical
+ nodes and a set of iSCSI targets. The resource pool contain a
+ combined total of 10 processors, 20GB RAM, 100GB storage.</para>
+ </listitem>
+ <listitem><para>Move hosts and storage to team pool</para></listitem>
+ <listitem><para>Create VMResourcePool for the project</para>
+ <para>
+
+
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/ViewVMResources.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <orderedlist>
+ <title>Team Administrator</title>
+ <listitem><para>kinit as admin (ovirtadmin?)</para>
+ </listitem>
+ <listitem><para>Browse to oVirt UI</para>
+ </listitem>
+ <listitem><para>Navigate to team hardware pool, view available hosts and
+ storage</para>
+ </listitem>
+ <listitem><para>Give team members access to the project. Assigns 3 users to this resource pool and assigns constraints on those users </para>
+ </listitem>
+ <listitem><para>Give each team member appropriate resources to go with, or Each user may use 3 VCPUs, 30GB storage, 6GB RAM. </para>
+ <para>User A creates 6 VMs each using 5GB of disk, 2GB RAM and 1VCPU. Given his
+ resource constraints, he can only run 3 of them simultaneously, but
+ because he's got enough storage he is able to define 6, run 3 and leave 3
+ offline. If he brings down a VM, he can then fire up a different one.
+ So the limit shouldn't be on the # of virtual machines that a user can
+ create, but it should be on their resource consumption in terms of
+ storage/processor/memory.</para>
+ </listitem>
+ </orderedlist>
+
+ <orderedlist>
+ <title>User - Team Member</title>
+ <listitem><para>kinit as team member</para></listitem>
+ <listitem><para>Log in as a team member, create VMs in the new pool using available OS images (that is, pull down a menu to choose the OS that cobbler will install via PXE when the VM starts). Start/stop VMs, see console (via console plugin link), etc.</para></listitem>
+ <listitem><para>Attempt to start a VM which goes over quota, show that quota limits are enforced.</para></listitem>
+ </orderedlist>
+
+ </section>
+ </section>
+ <section id="QS-2">
+ <title>Create a team development box</title>
+ <para>Amy Admin is starting a project with 5 developers. The project requires a private network since it has a special authentication component. Amy needs to allocate and isolate 3 virtual machines to each developer, so that they can do network development that would otherwise be disruptive to the company network.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Amy logs into oVirt and selects a Group of hosts with several unallocated hosts.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin1.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>She selects the under-utilized / unallocated hosts.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin2.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem>
+ <para>She moves the selected hosts to a new group.
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin3.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>OR she could create a new resource group first and then add hosts and storage
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin4.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>The new group is created successfully</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/amyadmin5.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+ <section id="Manage-resource-Loads">
+ <title>Manage Resource Loads</title>
+ <para>Given a pool of production hosts, examine load and resource
+ usage graphs to find VMs that need additional peak resources. Having
+ found one, migrate low-load VMs away from the resource-bound
+ machine. Alternatively, migrate the loaded VM to a larger, empty
+ machine.</para>
+
+ <para>This sample demonstrates the following tasks in oVirt:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Authentication/authorization</para>
+ </listitem>
+ <listitem>
+ <para>Navigate to/view physical hosts</para>
+ </listitem>
+ <listitem>
+ <para>View performance graphs and statistics for physical hosts and VMs</para>
+ </listitem>
+ <listitem>
+ <para>Migrate VMs off loaded hosts to unloaded hosts</para>
+ </listitem>
+ <listitem>
+ <para>Change VM resource limits on the fly.</para>
+ </listitem>
+ </itemizedlist>
+ <para>To manage the resource loads effectively in this scenario:</para>
+ <orderedlist>
+ <listitem><para>kinit as admin (ovirtadmin?)</para></listitem>
+ <listitem><para>Browse to oVirt UI</para></listitem>
+ <listitem><para>Navigate to a pool of physical hosts. The physical hosts must have VMs running on them and some load history.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/QS1-SummaryTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Show load graphs for physical hosts for the prior 24 hours. Identify one that is regularly overloaded.</para></listitem>
+ <listitem><para>Look at load graphs for VMs on the overloaded host. Identify one
+ that is regularly running out of resources/overloaded.</para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/VPool_VMTab.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ <listitem><para>Migrate lightly loaded VMs off the overloaded host to make room.</para>
+ <para>Alternatively, migrate the loaded VM to a bigger host to make room.</para>
+ <para>Alternatively, lower resource limits of VMs to make more resources
+ available for the loaded VM</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="Sample-2">
+ <title>Setting up User Permissions</title>
+ <para>
+ Set a new user up with a virtual desktop. Given a
+ VM Resource Group for virtual desktop hosts, give the new user
+ permission to access the group, and resource allocations for a single
+ desktop host. Then create a VM for the user and install a desktop OS
+ in it. The user should be able to log in to the machine console and
+ use the VM.</para>
+ <para>This sample demonstrates the following tasks in oVirt.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Authentication/authorization</para>
+ </listitem>
+ <listitem>
+ <para>Navigate to hardware pools/resource pools</para>
+ </listitem>
+ <listitem>
+ <para>Grant permission</para>
+ </listitem>
+ <listitem>
+ <para>Allocate resources</para>
+ </listitem>
+ <listitem>
+ <para>Create VM for another user</para>
+ </listitem>
+ <listitem>
+ <para>Provision VM for another user</para>
+ </listitem>
+ <listitem>
+ <para>Navigate as non-privileged user to allowed VM</para>
+ </listitem>
+ <listitem>
+ <para>Viewing the VM console</para>
+ </listitem>
+ </itemizedlist>
+ <para>The process is</para>
+ <orderedlist>
+ <listitem>
+ <para>kinit as admin (ovirtadmin?)</para>
+ </listitem>
+ <listitem>
+ <para>Browse to oVirt UI</para>
+ </listitem>
+ <listitem>
+ <para>Navigate to virtual-desktop VM Resource Group</para>
+ </listitem>
+ <listitem>
+ <para>Give new user permission on VM Resource Group</para>
+ </listitem>
+ <listitem>
+ <para>Give new user resource grants for a single desktop host</para>
+ </listitem>
+ <listitem>
+ <para>Create VM for user, install a desktop OS in it.</para>
+ </listitem>
+ <listitem>
+ <para>kinit as user</para>
+ </listitem>
+ <listitem>
+ <para>Navigate oVirt UI to VM console, launch console.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+</chapter>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Troubleshooting.xml b/Using_the_oVirt_Admin_UI/en-US/Troubleshooting.xml
new file mode 100644
index 0000000..c6c3313
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Troubleshooting.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0'?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<appendix id="Using_oVirt-Revision">
+ <appendixinfo>
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </appendixinfo>
+ <title>Troubleshooting</title>
+ <para>
+ Empty para tags are not allowed (they break translations), so this boilerplate text is here to keep place until actual text is added. (Note: the file is currently not included in built versions of this book: edit the appropriate xi:include in 'Using_oVirt.xml' to include this file.)
+ </para>
+</appendix>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.ent b/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.ent
new file mode 100644
index 0000000..7b9380a
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.ent
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "oVirt">
+<!ENTITY BOOKID "Using_oVirt">
+<!ENTITY YEAR "2008">
+<!ENTITY HOLDER "Red Hat Incorporated">
diff --git a/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.xml b/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.xml
new file mode 100644
index 0000000..8b8dd73
--- /dev/null
+++ b/Using_the_oVirt_Admin_UI/en-US/Using_oVirt.xml
@@ -0,0 +1,22 @@
+<?xml version='1.0'?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Introduction-to-oVirt.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Installing-the-Admin-UI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Quick-Start.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <xi:include href="Getting-Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Managing-the-Hardware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Managing-VMs.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Managing-User-Permissions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Sample-oVirt-Scenarios.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <xi:include href="Glossary.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Appendix-B.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+<!-- <xi:include href="Troubleshooting.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+
+</book>
+
diff --git a/Using_the_oVirt_Admin_UI/en-US/images/AddHost.png b/Using_the_oVirt_Admin_UI/en-US/images/AddHost.png
new file mode 100644
index 0000000000000000000000000000000000000000..16b9f0a27db85877537b42905411050302f5bc26
GIT binary patch
More information about the ovirt-devel
mailing list