You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2012/11/07 19:01:12 UTC
[42/52] [abbrv] [partial] CLOUDSTACK-444 Fix from Radhika PC against
docs, adds network setup in the install guide.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/convert-hyperv-vm-to-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/convert-hyperv-vm-to-template.html b/docs/tmp/en-US/epub/OEBPS/convert-hyperv-vm-to-template.html
new file mode 100644
index 0000000..2db1084
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/convert-hyperv-vm-to-template.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.12. Converting a Hyper-V VM to a Template</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="convert-hyperv-vm-to-template"><div class="titlepage"><div><div><h1 class="title" id="convert-hyperv-vm-to-template">12.12. Converting a Hyper-V VM to a Template</h1></div></div></div><div class="para">
+ To convert a Hyper-V VM to a XenServer-compatible CloudStack template, you will need a standalone XenServer host with an attached NFS VHD SR. Use whatever XenServer version you are using with CloudStack, but use XenCenter 5.6 FP1 or SP2 (it is backwards compatible to 5.6). Additionally, it may help to have an attached NFS ISO SR.
+ </div><div class="para">
+ For Linux VMs, you may need to do some preparation in Hyper-V before trying to get the VM to work in XenServer. Clone the VM and work on the clone if you still want to use the VM in Hyper-V. Uninstall Hyper-V Integration Components and check for any references to device names in /etc/fstab:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ From the linux_ic/drivers/dist directory, run make uninstall (where "linux_ic" is the path to the copied Hyper-V Integration Components files).
+ </div></li><li class="listitem"><div class="para">
+ Restore the original initrd from backup in /boot/ (the backup is named *.backup0).
+ </div></li><li class="listitem"><div class="para">
+ Remove the "hdX=noprobe" entries from /boot/grub/menu.lst.
+ </div></li><li class="listitem"><div class="para">
+ Check /etc/fstab for any partitions mounted by device name. Change those entries (if any) to mount by LABEL or UUID (get that information with the "blkid" command)..
+ </div></li></ol></div><div class="para">
+ The next step is make sure the VM is not running in Hyper-V, then get the VHD into XenServer. There are two options for doing this.
+ </div><div class="para">
+ Option one:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Import the VHD using XenCenter. In XenCenter, go to Tools>Virtual Appliance Tools>Disk Image Import.
+ </div></li><li class="listitem"><div class="para">
+ Choose the VHD, then click Next.
+ </div></li><li class="listitem"><div class="para">
+ Name the VM, choose the NFS VHD SR under Storage, enable "Run Operating System Fixups" and choose the NFS ISO SR.
+ </div></li><li class="listitem"><div class="para">
+ Click Next, then Finish. A VM should be created.
+ </div></li></ol></div><div class="para">
+ Option two
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Run XenConvert, under From choose VHD, under To choose XenServer. Click Next.
+ </div></li><li class="listitem"><div class="para">
+ Choose the VHD, then click Next.
+ </div></li><li class="listitem"><div class="para">
+ Input the XenServer host info, then click Next.
+ </div></li><li class="listitem"><div class="para">
+ Name the VM, then click Next, then Convert. A VM should be created
+ </div></li></ol></div><div class="para">
+ Once you have a VM created from the Hyper-V VHD, prepare it using the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Boot the VM, uninstall Hyper-V Integration Services, and reboot.
+ </div></li><li class="listitem"><div class="para">
+ Install XenServer Tools, then reboot.
+ </div></li><li class="listitem"><div class="para">
+ Prepare the VM as desired. For example, run sysprep on Windows VMs. See <a class="xref" href="create-windows-template.html">Section 12.10, “Creating a Windows Template”</a>
+ </div></li></ol></div><div class="para">
+ Either option above will create a VM in HVM mode. This is fine for Windows VMs, but Linux VMs may not perform optimally. Converting a Linux VM to PV mode will require additional steps and will vary by distribution.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Shut down the VM and copy the VHD from the NFS storage to a web server; for example, mount the NFS share on the web server and copy it, or from the XenServer host use sftp or scp to upload it to the web server.
+ </div></li><li class="listitem"><div class="para">
+ In CloudStack, create a new template using the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ URL. Give the URL for the VHD
+ </div></li><li class="listitem"><div class="para">
+ OS Type. Use the appropriate OS. For PV mode on CentOS, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServer.
+ </div></li><li class="listitem"><div class="para">
+ Hypervisor. XenServer
+ </div></li><li class="listitem"><div class="para">
+ Format. VHD
+ </div></li></ul></div></li></ol></div><div class="para">
+ The template will be created, and you can create instances from it.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/create-new-projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/create-new-projects.html b/docs/tmp/en-US/epub/OEBPS/create-new-projects.html
new file mode 100644
index 0000000..0eccc4d
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/create-new-projects.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Creating a New Project</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="create-new-projects"><div class="titlepage"><div><div><h1 class="title" id="create-new-projects">6.3. Creating a New Project</h1></div></div></div><div class="para">
+ CloudStack administrators and domain administrators can create projects. If the global configuration parameter allow.user.create.projects is set to true, end users can also create projects.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in as administrator to the CloudStack UI.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation, click Projects.
+ </div></li><li class="listitem"><div class="para">
+ In Select view, click Projects.
+ </div></li><li class="listitem"><div class="para">
+ Click New Project.
+ </div></li><li class="listitem"><div class="para">
+ Give the project a name and description for display to users, then click Create Project.
+ </div></li><li class="listitem"><div class="para">
+ A screen appears where you can immediately add more members to the project. This is optional. Click Next when you are ready to move on.
+ </div></li><li class="listitem"><div class="para">
+ Click Save.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/create-template-from-existing-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/create-template-from-existing-vm.html b/docs/tmp/en-US/epub/OEBPS/create-template-from-existing-vm.html
new file mode 100644
index 0000000..e929109
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/create-template-from-existing-vm.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.6. Creating a Template from an Existing Virtual Machine</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="create-template-from-existing-vm"><div class="titlepage"><div><div><h1 class="title" id="create-template-from-existing-vm">12.6. Creating a Template from an Existing Virtual Machine</h1></div></div></div><div class="para">
+ Once you have at least one VM set up in the way you want, you can use it as the prototype for other VMs.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create and start a virtual machine using any of the techniques given in <a class="xref" href="creating-vms.html">Section 10.4, “Creating VMs”</a>.
+ </div></li><li class="listitem"><div class="para">
+ Make any desired configuration changes on the running VM, then click Stop.
+ </div></li><li class="listitem"><div class="para">
+ Wait for the VM to stop. When the status shows Stopped, go to the next step.
+ </div></li><li class="listitem"><div class="para">
+ Click Create Template and provide the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name and Display Text</strong></span>. These will be shown in the UI, so choose something descriptive.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>OS Type</strong></span>. This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the operating system of the stopped VM is listed, choose it.
+ </div></li><li class="listitem"><div class="para">
+ If the OS type of the stopped VM is not listed, choose Other.
+ </div></li><li class="listitem"><div class="para">
+ If you want to boot from this template in PV mode, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServere:
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note: Generally you should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other.
+ </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public</strong></span>. Choose Yes to make this template accessible to all users of this CloudStack installation. The template will appear in the Community Templates list. See <a class="xref" href="private-public-template.html">Section 12.5, “Private and Public Templates”</a>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Password Enabled</strong></span>. Choose Yes if your template has the CloudStack password change script installed. See Adding Password Management to Your Templates.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click Add.
+ </div></li></ol></div><div class="para">
+ The new template will be visible in the Templates section when the template creation process has been completed. The template is then available when creating a new VM
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/create-template-from-snapshot.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/create-template-from-snapshot.html b/docs/tmp/en-US/epub/OEBPS/create-template-from-snapshot.html
new file mode 100644
index 0000000..fab9c8d
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/create-template-from-snapshot.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.7. Creating a Template from a Snapshot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="create-template-from-snapshot"><div class="titlepage"><div><div><h1 class="title" id="create-template-from-snapshot">12.7. Creating a Template from a Snapshot</h1></div></div></div><div class="para">
+ If you do not want to stop the VM in order to use the Create Template menu item (as described in <a class="xref" href="create-template-from-existing-vm.html">Section 12.6, “Creating a Template from an Existing Virtual Machine”</a>), you can create a template directly from any snapshot through the CloudStack UI.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/create-windows-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/create-windows-template.html b/docs/tmp/en-US/epub/OEBPS/create-windows-template.html
new file mode 100644
index 0000000..8060e98
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/create-windows-template.html
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.10. Creating a Windows Template</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="create-windows-template"><div class="titlepage"><div><div><h1 class="title" id="create-windows-template">12.10. Creating a Windows Template</h1></div></div></div><div class="para">
+ Windows templates must be prepared with Sysprep before they can be provisioned on multiple machines. Sysprep allows you to create a generic Windows template and avoid any possible SID conflicts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ (XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown.
+ </div></div></div><div class="para">
+ An overview of the procedure is as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Upload your Windows ISO.
+ </div><div class="para">
+ For more information, see <a class="xref" href="working-with-iso.html#add-iso">Section 10.11.1, “Adding an ISO”</a>
+ </div></li><li class="listitem"><div class="para">
+ Create a VM Instance with this ISO.
+ </div><div class="para">
+ For more information, see <a class="xref" href="creating-vms.html">Section 10.4, “Creating VMs”</a>
+ </div></li><li class="listitem"><div class="para">
+ Follow the steps in Sysprep for Windows Server 2008 R2 (below) or Sysprep for Windows Server 2003 R2, depending on your version of Windows Server
+ </div></li><li class="listitem"><div class="para">
+ The preparation steps are complete. Now you can actually create the template as described in Creating the Windows Template.
+ </div></li></ol></div><div class="section" id="sysprep-windows-server-2008R2"><div class="titlepage"><div><div><h2 class="title" id="sysprep-windows-server-2008R2">12.10.1. System Preparation for Windows Server 2008 R2</h2></div></div></div><div class="para">
+ For Windows 2008 R2, you run Windows System Image Manager to create a custom sysprep response XML file. Windows System Image Manager is installed as part of the Windows Automated Installation Kit (AIK). Windows AIK can be downloaded from the Microsoft Download Center at the following location:
+ </div><div class="para">
+ <a href="http://www.microsoft.com/en-us/download/details.aspx?id=9085">http://www.microsoft.com/en-us/download/details.aspx?id=9085</a>Microsoft Download Center.
+ </div><div class="para">
+ Use the following steps to run sysprep for Windows 2008 R2:
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The steps outlined here are derived from the excellent guide by Charity Shelbourne, originally published at <a href="http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx">http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx</a>Windows Server 2008 Sysprep Mini-Setup
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Download and install the Windows AIK
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Windows AIK should not be installed on the Windows 2008 R2 VM you just created. Windows AIK should not be part of the template you create. It is only used to create the sysprep answer file.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Copy the install.wim file in the \sources directory of the Windows 2008 R2 installation DVD to the hard disk. This is a very large file and may take a long time to copy. Windows AIK requires the WIM file to be writable.
+ </div></li><li class="listitem"><div class="para">
+ Start the Windows System Image Manager, which is part of the Windows AIK.
+ </div></li><li class="listitem"><div class="para">
+ In the Windows Image pane, right click “Select a Windows image or catalog file” to load the install.wim file you just copied.
+ </div></li><li class="listitem"><div class="para">
+ Select the Windows 2008 R2 Edition
+ </div><div class="para">
+ You may be prompted with a warning that the catalog file cannot be opened. Click Yes to create a new catalog file.
+ </div></li><li class="listitem"><div class="para">
+ In the Answer File pane, right click to create a new answer file.
+ </div></li><li class="listitem"><div class="para">
+ Generate the answer file from the Windows System Image Manager using the following steps:
+ </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
+ The first page you need to automate is the Language and Country or Region Selection page. To automate this, expand Components in your Windows Image pane, right-click and add the Microsoft-Windows-International-Core setting to Pass 7 oobeSystem. In your Answer File pane, configure the InputLocale, SystemLocale, UILanguage, and UserLocale with the appropriate settings for your language and country or region. Should you have a question about any of these settings, you can right-click on the specific setting and select Help. This will open the appropriate CHM help file with more information, including examples on the setting you are attempting to configure.
+ </div><div class="mediaobject"><img src="./images/sysmanager.png" width="444" alt="sysmanager.png: System Image Manager" /></div></li><li class="listitem"><div class="para">
+ You need to automate the Software License Terms Selection page, otherwise known as the End-User License Agreement (EULA). To do this, expand the Microsoft-Windows-Shell-Setup component. High-light the OOBE setting, and add the setting to the Pass 7 oobeSystem. In Settings, set HideEULAPage true.
+ </div><div class="mediaobject"><img src="./images/software-license.png" width="444" alt="software-license.png: Depicts hiding the EULA page." /></div></li><li class="listitem"><div class="para">
+ Make sure the license key is properly set. If you use MAK key, you can just enter the MAK key on the Windows 2008 R2 VM. You need not input the MAK into the Windows System Image Manager. If you use KMS host for activation you need not enter the Product Key. Details of Windows Volume Activation can be found at <a href="http://technet.microsoft.com/en-us/library/bb892849.aspx">http://technet.microsoft.com/en-us/library/bb892849.aspx</a>
+ </div></li><li class="listitem"><div class="para">
+ You need to automate is the Change Administrator Password page. Expand the Microsoft-Windows-Shell-Setup component (if it is not still expanded), expand UserAccounts, right-click on AdministratorPassword, and add the setting to the Pass 7 oobeSystem configuration pass of your answer file. Under Settings, specify a password next to Value.
+ </div><div class="mediaobject"><img src="./images/change-admin-password.png" width="444" alt="change-admin-password.png: Depicts changing the administrator password" /></div><div class="para">
+ You may read the AIK documentation and set many more options that suit your deployment. The steps above are the minimum needed to make Windows unattended setup work.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ Save the answer file as unattend.xml. You can ignore the warning messages that appear in the validation window.
+ </div></li><li class="listitem"><div class="para">
+ Copy the unattend.xml file into the c:\windows\system32\sysprep directory of the Windows 2008 R2 Virtual Machine
+ </div></li><li class="listitem"><div class="para">
+ Once you place the unattend.xml file in c:\windows\system32\sysprep directory, you run the sysprep tool as follows:
+ </div><pre class="programlisting">cd c:\Windows\System32\sysprep
+sysprep.exe /oobe /generalize /shutdown
+</pre><div class="para">
+ The Windows 2008 R2 VM will automatically shut down after sysprep is complete.
+ </div></li></ol></div></div><div class="section" id="sysprep-for-windows-server-2003R2"><div class="titlepage"><div><div><h2 class="title" id="sysprep-for-windows-server-2003R2">12.10.2. Sysprep for Windows Server 2003 R2</h2></div></div></div><div class="para">
+ Earlier versions of Windows have a different sysprep tool. Follow these steps for Windows Server 2003 R2.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Extract the content of \support\tools\deploy.cab on the Windows installation CD into a directory called c:\sysprep on the Windows 2003 R2 VM.
+ </div></li><li class="listitem"><div class="para">
+ Run c:\sysprep\setupmgr.exe to create the sysprep.inf file.
+ </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
+ Select Create New to create a new Answer File.
+ </div></li><li class="listitem"><div class="para">
+ Enter “Sysprep setup” for the Type of Setup.
+ </div></li><li class="listitem"><div class="para">
+ Select the appropriate OS version and edition.
+ </div></li><li class="listitem"><div class="para">
+ On the License Agreement screen, select “Yes fully automate the installation”.
+ </div></li><li class="listitem"><div class="para">
+ Provide your name and organization.
+ </div></li><li class="listitem"><div class="para">
+ Leave display settings at default.
+ </div></li><li class="listitem"><div class="para">
+ Set the appropriate time zone.
+ </div></li><li class="listitem"><div class="para">
+ Provide your product key.
+ </div></li><li class="listitem"><div class="para">
+ Select an appropriate license mode for your deployment
+ </div></li><li class="listitem"><div class="para">
+ Select “Automatically generate computer name”.
+ </div></li><li class="listitem"><div class="para">
+ Type a default administrator password. If you enable the password reset feature, the users will not actually use this password. This password will be reset by the instance manager after the guest boots up.
+ </div></li><li class="listitem"><div class="para">
+ Leave Network Components at “Typical Settings”.
+ </div></li><li class="listitem"><div class="para">
+ Select the “WORKGROUP” option.
+ </div></li><li class="listitem"><div class="para">
+ Leave Telephony options at default.
+ </div></li><li class="listitem"><div class="para">
+ Select appropriate Regional Settings.
+ </div></li><li class="listitem"><div class="para">
+ Select appropriate language settings.
+ </div></li><li class="listitem"><div class="para">
+ Do not install printers.
+ </div></li><li class="listitem"><div class="para">
+ Do not specify “Run Once commands”.
+ </div></li><li class="listitem"><div class="para">
+ You need not specify an identification string.
+ </div></li><li class="listitem"><div class="para">
+ Save the Answer File as c:\sysprep\sysprep.inf.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ Run the following command to sysprep the image:
+ </div><pre class="programlisting">c:\sysprep\sysprep.exe -reseal -mini -activated</pre><div class="para">
+ After this step the machine will automatically shut down
+ </div></li></ol></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/creating-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/creating-vms.html b/docs/tmp/en-US/epub/OEBPS/creating-vms.html
new file mode 100644
index 0000000..f448adb
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/creating-vms.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4. Creating VMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="creating-vms"><div class="titlepage"><div><div><h1 class="title" id="creating-vms">10.4. Creating VMs</h1></div></div></div><div class="para">
+ Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM.
+ </div><div class="para">
+ To create a VM from a template:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as an administrator or user.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Click Add Instance.
+ </div></li><li class="listitem"><div class="para">
+ Select a template, then follow the steps in the wizard. (For more information about how the templates came to be in this list, see Working with Templates.
+ </div></li><li class="listitem"><div class="para">
+ Be sure that the hardware you have allows starting the selected service offering.
+ </div></li><li class="listitem"><div class="para">
+ Click Submit and your VM will be created and started.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For security reason, the internal name of the VM is visible only to the root admin.
+ </div></div></div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Starting with v3.0.3, you can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A new request parameter, startVM, is introduced in the deployVm API to support this feature. For more information, see the Developer's Guide
+ </div></div></div><div class="para">
+ To create a VM from an ISO:
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ (XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown.
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as an administrator or user.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Click Add Instance.
+ </div></li><li class="listitem"><div class="para">
+ Select ISO Boot, and follow the steps in the wizard.
+ </div></li><li class="listitem"><div class="para">
+ Click Submit and your VM will be created and started.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/customizing-dns.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/customizing-dns.html b/docs/tmp/en-US/epub/OEBPS/customizing-dns.html
new file mode 100644
index 0000000..5a085e4
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/customizing-dns.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.4. Customizing the Network Domain Name</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="customizing-dns"><div class="titlepage"><div><div><h1 class="title" id="customizing-dns">18.4. Customizing the Network Domain Name</h1></div></div></div><div class="para">
+ The root administrator can optionally assign a custom DNS suffix at the level of a network, account, domain, zone, or entire CloudStack installation, and a domain administrator can do so within their own domain. To specify a custom domain name and put it into effect, follow these steps.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Set the DNS suffix at the desired scope
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ At the network level, the DNS suffix can be assigned through the UI when creating a new network, as described in <a class="xref" href="using-multiple-guest-networks.html#add-additional-guest-network">Section 15.6.1, “Adding an Additional Guest Network”</a> or with the updateNetwork command in the CloudStack API.
+ </div></li><li class="listitem"><div class="para">
+ At the account, domain, or zone level, the DNS suffix can be assigned with the appropriate CloudStack API commands: createAccount, editAccount, createDomain, editDomain, createZone, or editZone.
+ </div></li><li class="listitem"><div class="para">
+ At the global level, use the configuration parameter guest.domain.suffix. You can also use the CloudStack API command updateConfiguration. After modifying this global configuration, restart the Management Server to put the new setting into effect.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ To make the new DNS suffix take effect for an existing network, call the CloudStack API command updateNetwork. This step is not necessary when the DNS suffix was specified while creating a new network.
+ </div></li></ol></div><div class="para">
+ The source of the network domain that is used depends on the following rules.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ For all networks, if a network domain is specified as part of a network's own configuration, that value is used.
+ </div></li><li class="listitem"><div class="para">
+ For an account-specific network, the network domain specified for the account is used. If none is specified, the system looks for a value in the domain, zone, and global configuration, in that order.
+ </div></li><li class="listitem"><div class="para">
+ For a domain-specific network, the network domain specified for the domain is used. If none is specified, the system looks for a value in the zone and global configuration, in that order.
+ </div></li><li class="listitem"><div class="para">
+ For a zone-specific network, the network domain specified for the zone is used. If none is specified, the system looks for a value in the global configuration.
+ </div></li></ul></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/default-account-resource-limit.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/default-account-resource-limit.html b/docs/tmp/en-US/epub/OEBPS/default-account-resource-limit.html
new file mode 100644
index 0000000..df28808
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/default-account-resource-limit.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4. Default Account Resource Limits</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="default-account-resource-limit"><div class="titlepage"><div><div><h1 class="title" id="default-account-resource-limit">14.4. Default Account Resource Limits</h1></div></div></div><div class="para">
+ You can limit resource use by accounts. The default limits are set using global configuration parameters, and they affect all accounts within a cloud. The relevant parameters are those beginning with max.account (max.account.snapshots, etc.)..
+ </div><div class="para">
+ To override a default limit for a particular account, set a per-account resource limit.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation tree, click Accounts.
+ </div></li><li class="listitem"><div class="para">
+ Select the account you want to modify. The current limits are displayed. A value of -1 shows that there is no limit in place
+ </div></li><li class="listitem"><div class="para">
+ Click the Edit button
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="editbutton.png: edits the settings." /></span>
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/default-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/default-template.html b/docs/tmp/en-US/epub/OEBPS/default-template.html
new file mode 100644
index 0000000..9c9791b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/default-template.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4. The Default Template</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="default-template"><div class="titlepage"><div><div><h1 class="title" id="default-template">12.4. The Default Template</h1></div></div></div><div class="para">
+ CloudStack includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates.
+ </div><div class="para">
+ The root password for the default template is "password".
+ </div><div class="para">
+ A default template is provided for each of XenServer, KVM, and vSphere. The templates that are downloaded depend on the hypervisor type that is available in your cloud. Each template is approximately 2.5 GB physical size.
+ </div><div class="para">
+ The default template includes the standard iptables rules, which will block most access to the template excluding ssh.
+ </div><pre class="programlisting"># iptables --list
+Chain INPUT (policy ACCEPT)
+target prot opt source destination
+RH-Firewall-1-INPUT all -- anywhere anywhere
+
+Chain FORWARD (policy ACCEPT)
+target prot opt source destination
+RH-Firewall-1-INPUT all -- anywhere anywhere
+
+Chain OUTPUT (policy ACCEPT)
+target prot opt source destination
+
+Chain RH-Firewall-1-INPUT (2 references)
+target prot opt source destination
+ACCEPT all -- anywhere anywhere
+ACCEPT icmp -- anywhere anywhere icmp any
+ACCEPT esp -- anywhere anywhere
+ACCEPT ah -- anywhere anywhere
+ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
+ACCEPT udp -- anywhere anywhere udp dpt:ipp
+ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
+ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
+ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
+REJECT all -- anywhere anywhere reject-with icmp-host-
+</pre></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/delete-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/delete-templates.html b/docs/tmp/en-US/epub/OEBPS/delete-templates.html
new file mode 100644
index 0000000..25956c4
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/delete-templates.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.14. Deleting Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="delete-templates"><div class="titlepage"><div><div><h1 class="title" id="delete-templates">12.14. Deleting Templates</h1></div></div></div><div class="para">
+ Templates may be deleted. In general, when a template spans multiple Zones, only the copy that is selected for deletion will be deleted; the same template in other Zones will not be deleted. The provided CentOS template is an exception to this. If the provided CentOS template is deleted, it will be deleted from all Zones.
+ </div><div class="para">
+ When templates are deleted, the VMs instantiated from them will continue to run. However, new VMs cannot be created based on the deleted template.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/deleting-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/deleting-vms.html b/docs/tmp/en-US/epub/OEBPS/deleting-vms.html
new file mode 100644
index 0000000..c391a8e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/deleting-vms.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.10. Deleting VMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="deleting-vms"><div class="titlepage"><div><div><h1 class="title" id="deleting-vms">10.10. Deleting VMs</h1></div></div></div><div class="para">
+ Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines.
+ </div><div class="para">
+ To delete a virtual machine:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as a user or admin.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Choose the VM that you want to delete.
+ </div></li><li class="listitem"><div class="para">
+ Click the Destroy Instance button
+ <span class="inlinemediaobject"><img src="./images/destroy-instance.png" alt="Destroyinstance.png: button to destroy an instance" /></span>
+
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/deployment-architecture-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/deployment-architecture-overview.html b/docs/tmp/en-US/epub/OEBPS/deployment-architecture-overview.html
new file mode 100644
index 0000000..912cf25
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/deployment-architecture-overview.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Deployment Architecture Overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="deployment-architecture-overview"><div class="titlepage"><div><div><h1 class="title" id="deployment-architecture-overview">1.3. Deployment Architecture Overview</h1></div></div></div><div class="para">
+ A CloudStack installation consists of two parts: the Management Server and the cloud infrastructure that it manages. When you set up and manage a CloudStack cloud, you provision resources such as hosts, storage devices, and IP addresses into the Management Server, and the Management Server manages those resources.
+ </div><div class="para">
+ The minimum production installation consists of one machine running the CloudStack Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). In its smallest deployment, a single machine can act as both the Management Server and the hypervisor host (using the KVM hypervisor).
+ </div><div class="mediaobject"><img src="./images/basic-deployment.png" alt="basic-deployment.png: Basic two-machine deployment" /></div><div class="para">
+ A more full-featured installation consists of a highly-available multi-node Management Server installation and up to tens of thousands of hosts using any of several advanced networking setups. For information about deployment options, see Choosing a Deployment Architecture.
+ </div><div class="section" id="management-server-overview"><div class="titlepage"><div><div><h2 class="title" id="management-server-overview">1.3.1. Management Server Overview</h2></div></div></div><div class="para">
+ The Management Server is the CloudStack software that manages cloud resources. By interacting with the Management Server through its UI or API, you can configure and manage your cloud infrastructure.
+ </div><div class="para">
+ The Management Server runs on a dedicated server or VM. It controls allocation of virtual machines to hosts and assigns storage and IP addresses to the virtual machine instances. The Management Server runs in a Tomcat container and requires a MySQL database for persistence.
+ </div><div class="para">
+ The machine must meet the system requirements described in System Requirements.
+ </div><div class="para">
+ The Management Server:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Provides the web user interface for the administrator and a reference user interface for end users.
+ </div></li><li class="listitem"><div class="para">
+ Provides the APIs for CloudStack.
+ </div></li><li class="listitem"><div class="para">
+ Manages the assignment of guest VMs to particular hosts.
+ </div></li><li class="listitem"><div class="para">
+ Manages the assignment of public and private IP addresses to particular accounts.
+ </div></li><li class="listitem"><div class="para">
+ Manages the allocation of storage to guests as virtual disks.
+ </div></li><li class="listitem"><div class="para">
+ Manages snapshots, templates, and ISO images, possibly replicating them across data centers.
+ </div></li><li class="listitem"><div class="para">
+ Provides a single point of configuration for the cloud.
+ </div></li></ul></div></div><div class="section" id="cloud-infrastructure-overview"><div class="titlepage"><div><div><h2 class="title" id="cloud-infrastructure-overview">1.3.2. Cloud Infrastructure Overview</h2></div></div></div><div class="para">
+ The Management Server manages one or more zones (typically, datacenters) containing host computers where guest virtual machines will run. The cloud infrastructure is organized as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Zone: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage.
+ </div></li><li class="listitem"><div class="para">
+ Pod: A pod is usually one rack of hardware that includes a layer-2 switch and one or more clusters.
+ </div></li><li class="listitem"><div class="para">
+ Cluster: A cluster consists of one or more hosts and primary storage.
+ </div></li><li class="listitem"><div class="para">
+ Host: A single compute node within a cluster. The hosts are where the actual cloud services run in the form of guest virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ Primary storage is associated with a cluster, and it stores the disk volumes for all the VMs running on hosts in that cluster.
+ </div></li><li class="listitem"><div class="para">
+ Secondary storage is associated with a zone, and it stores templates, ISO images, and disk volume snapshots.
+ </div></li></ul></div><div class="mediaobject"><img src="./images/infrastructure-overview.png" width="444" alt="infrastructure_overview.png: Nested organization of a zone" /></div><div class="para">
+ <span class="bold bold"><strong>More Information</strong></span>
+ </div><div class="para">
+ For more information, see documentation on cloud infrastructure concepts.
+ </div></div><div class="section" id="networking-overview"><div class="titlepage"><div><div><h2 class="title" id="networking-overview">1.3.3. Networking Overview</h2></div></div></div><div class="para">
+ CloudStack offers two types of networking scenario:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Basic. For AWS-style networking. Provides a single network where guest isolation can be provided through layer-3 means such as security groups (IP address source filtering).
+ </div></li><li class="listitem"><div class="para">
+ Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks.
+ </div></li></ul></div><div class="para">
+ For more details, see Network Setup.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/disable-enable-zones-pods-clusters.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/disable-enable-zones-pods-clusters.html b/docs/tmp/en-US/epub/OEBPS/disable-enable-zones-pods-clusters.html
new file mode 100644
index 0000000..39f1873
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/disable-enable-zones-pods-clusters.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3. Disabling and Enabling Zones, Pods, and Clusters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="disable-enable-zones-pods-clusters"><div class="titlepage"><div><div><h1 class="title" id="disable-enable-zones-pods-clusters">11.3. Disabling and Enabling Zones, Pods, and Clusters</h1></div></div></div><div class="para">
+ You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default.
+ </div><div class="para">
+ To disable and enable a zone, pod, or cluster:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as administrator
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ In Zones, click View More.
+ </div></li><li class="listitem"><div class="para">
+ If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button.
+ <span class="inlinemediaobject"><img src="./images/enable-disable.png" alt="enable-disable.png: button to enable or disable zone, pod, or cluster." /></span>
+
+ </div></li><li class="listitem"><div class="para">
+ If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster.
+ </div></li><li class="listitem"><div class="para">
+ Click the Compute tab.
+ </div></li><li class="listitem"><div class="para">
+ In the Pods or Clusters node of the diagram, click View All.
+ </div></li><li class="listitem"><div class="para">
+ Click the pod or cluster name in the list.
+ </div></li><li class="listitem"><div class="para">
+ Click the Enable/Disable button.
+ <span class="inlinemediaobject"><img src="./images/enable-disable.png" alt="Disabling and Enabling Zones, Pods, and Clusters" /></span>
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/dns-dhcp.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/dns-dhcp.html b/docs/tmp/en-US/epub/OEBPS/dns-dhcp.html
new file mode 100644
index 0000000..ee0846a
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/dns-dhcp.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.16. DNS and DHCP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="dns-dhcp"><div class="titlepage"><div><div><h1 class="title" id="dns-dhcp">15.16. DNS and DHCP</h1></div></div></div><div class="para">
+ The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/event-types.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/event-types.html b/docs/tmp/en-US/epub/OEBPS/event-types.html
new file mode 100644
index 0000000..f972ce1
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/event-types.html
@@ -0,0 +1,446 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix B. Event Types</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="appendix" id="event-types"><div class="titlepage"><div><div><h1 class="title">Event Types</h1></div></div></div><div class="informaltable"><table border="1"><colgroup><col style="text-align: left" class="c1" width="33%" /><col style="text-align: left" class="c2" width="33%" /><col width="33%" /></colgroup><tbody><tr><td style="text-align: left">
+ <div class="para">
+ VM.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.EXTRACT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SG.REVOKE.INGRESS
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.DESTROY
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.UPLOAD
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ HOST.RECONNECT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.START
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.CLEANUP
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ MAINT.CANCEL
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.STOP
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VOLUME.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ MAINT.CANCEL.PS
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.REBOOT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VOLUME.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ MAINT.PREPARE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.UPGRADE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VOLUME.ATTACH
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ MAINT.PREPARE.PS
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VM.RESETPASSWORD
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VOLUME.DETACH
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VPN.REMOTE.ACCESS.CREATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VOLUME.UPLOAD
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VPN.USER.ADD
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.DESTROY
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SERVICEOFFERING.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VPN.USER.REMOVE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.START
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SERVICEOFFERING.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NETWORK.RESTART
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.STOP
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SERVICEOFFERING.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ UPLOAD.CUSTOM.CERTIFICATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.REBOOT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ DOMAIN.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ UPLOAD.CUSTOM.CERTIFICATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ROUTER.HA
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ DOMAIN.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ STATICNAT.DISABLE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ DOMAIN.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.CREATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.DESTROY
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SNAPSHOT.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.DESTROY
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.START
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SNAPSHOT.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.START
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.STOP
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SNAPSHOTPOLICY.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.STOP
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.REBOOT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SNAPSHOTPOLICY.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.REBOOT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ PROXY.HA
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SNAPSHOTPOLICY.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SSVM.H
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VNC.CONNECT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VNC.DISCONNECT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NET.IPASSIGN
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ NET.IPRELEASE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NET.RULEADD
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NET.RULEDELETE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ NET.RULEMODIFY
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NETWORK.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NETWORK.DELETE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ LB.ASSIGN.TO.RULE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ LB.REMOVE.FROM.RULE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ LB.CREATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ LB.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ LB.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ USER.LOGIN
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ USER.LOGOUT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ USER.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ USER.DELETE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ USER.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ USER.DISABLE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.CREATE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.UPDATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.COPY
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.DOWNLOAD.START
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.DOWNLOAD.SUCCESS
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ TEMPLATE.DOWNLOAD.FAILED
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ISO.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ISO.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ISO.COPY
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ISO.ATTACH
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ISO.DETACH
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ISO.EXTRACT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ISO.UPLOAD
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SERVICE.OFFERING.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SERVICE.OFFERING.EDIT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ SERVICE.OFFERING.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ DISK.OFFERING.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ DISK.OFFERING.EDIT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ DISK.OFFERING.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NETWORK.OFFERING.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ NETWORK.OFFERING.EDIT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ NETWORK.OFFERING.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ POD.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ POD.EDIT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ POD.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ZONE.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ ZONE.EDIT
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ ZONE.DELETE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VLAN.IP.RANGE.CREATE
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ VLAN.IP.RANGE.DELETE
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ CONFIGURATION.VALUE.EDIT
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ SG.AUTH.INGRESS
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ </div>
+ </td></tr></tbody></table></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/export-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/export-template.html b/docs/tmp/en-US/epub/OEBPS/export-template.html
new file mode 100644
index 0000000..b7ffdc9
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/export-template.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.9. Exporting Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="export-template"><div class="titlepage"><div><div><h1 class="title" id="export-template">12.9. Exporting Templates</h1></div></div></div><div class="para">
+ End users and Administrators may export templates from the CloudStack. Navigate to the template in the UI and choose the Download function from the Actions menu.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/external-firewalls-and-load-balancers.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/external-firewalls-and-load-balancers.html b/docs/tmp/en-US/epub/OEBPS/external-firewalls-and-load-balancers.html
new file mode 100644
index 0000000..1f09324
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/external-firewalls-and-load-balancers.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.8. External Firewalls and Load Balancers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="external-firewalls-and-load-balancers"><div class="titlepage"><div><div><h1 class="title" id="external-firewalls-and-load-balancers">15.8. External Firewalls and Load Balancers</h1></div></div></div><div class="para">
+ CloudStack is capable of replacing its Virtual Router with an external Juniper SRX device and an optional external NetScaler or F5 load balancer for gateway and load balancing services. In this case, the VMs use the SRX as their gateway.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/feature-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/feature-overview.html b/docs/tmp/en-US/epub/OEBPS/feature-overview.html
new file mode 100644
index 0000000..1b13aed
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/feature-overview.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. What Can CloudStack Do?</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="feature-overview"><div class="titlepage"><div><div><h1 class="title" id="feature-overview">1.2. What Can CloudStack Do?</h1></div></div></div><div class="para">
+ <span class="bold bold"><strong>Multiple Hypervisor Support</strong></span>
+ </div><div class="para">
+ CloudStack works with a variety of hypervisors, and a single cloud deployment can contain multiple hypervisor implementations. The current release of CloudStack supports pre-packaged enterprise solutions like Citrix XenServer and VMware vSphere, as well as KVM or Xen running on Ubuntu or CentOS.
+ </div><div class="para">
+ <span class="bold bold"><strong>Massively Scalable Infrastructure Management</strong></span>
+ </div><div class="para">
+ CloudStack can manage tens of thousands of servers installed in multiple geographically distributed datacenters. The centralized management server scales linearly, eliminating the need for intermediate cluster-level management servers. No single component failure can cause cloud-wide outage. Periodic maintenance of the management server can be performed without affecting the functioning of virtual machines running in the cloud.
+ </div><div class="para">
+ <span class="bold bold"><strong>Automatic Configuration Management</strong></span>
+ </div><div class="para">
+ CloudStack automatically configures each guest virtual machine’s networking and storage settings.
+ </div><div class="para">
+ CloudStack internally manages a pool of virtual appliances to support the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN access, console proxy, storage access, and storage replication. The extensive use of virtual appliances simplifies the installation, configuration, and ongoing management of a cloud deployment.
+ </div><div class="para">
+ <span class="bold bold"><strong>Graphical User Interface</strong></span>
+ </div><div class="para">
+ CloudStack offers an administrator's Web interface, used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel.
+ </div><div class="para">
+ <span class="bold bold"><strong>API and Extensibility</strong></span>
+ </div><div class="para">
+ CloudStack provides an API that gives programmatic access to all the management features available in the UI. The API is maintained and documented. This API enables the creation of command line tools and new user interfaces to suit particular needs. See the Developer’s Guide and API Reference, both available at <a href="http://incubator.apache.org/cloudstack/docs">Apache CloudStack Guides</a> and <a href="http://incubator.apache.org/cloudstack/docs/api">Apache CloudStack API Reference</a> respectively.
+ </div><div class="para">
+ The CloudStack pluggable allocation architecture allows the creation of new types of allocators for the selection of storage and Hosts. See the Allocator Implementation Guide (<a href="http://docs.cloudstack.org/CloudStack_Documentation/Allocator_Implementation_Guide">http://docs.cloudstack.org/CloudStack_Documentation/Allocator_Implementation_Guide</a>).
+ </div><div class="para">
+ <span class="bold bold"><strong>High Availability</strong></span>
+ </div><div class="para">
+ CloudStack has a number of features to increase the availability of the system. The Management Server itself may be deployed in a multi-node installation where the servers are load balanced. MySQL may be configured to use replication to provide for a manual failover in the event of database loss. For the hosts, CloudStack supports NIC bonding and the use of separate networks for storage as well as iSCSI Multipath.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/global-config.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/global-config.html b/docs/tmp/en-US/epub/OEBPS/global-config.html
new file mode 100644
index 0000000..d88cefb
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/global-config.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 19. Setting Global Configuration Parameters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="global-config"><div class="titlepage"><div><div><h1 class="title">Chapter 19. Setting Global Configuration Parameters</h1></div></div></div><div class="para">
+ CloudStack provides parameters that you can set to control many aspects of the cloud. When CloudStack is first installed, and periodically thereafter, you might need to modify these settings.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the UI as administrator.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In Select View, choose one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Global Settings. This displays a list of the parameters with brief descriptions and current values.
+ </div></li><li class="listitem"><div class="para">
+ Hypervisor Capabilities. This displays a list of hypervisor versions with the maximum number of guests supported for each.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Use the search box to narrow down the list to those you are interested in.
+ </div></li><li class="listitem"><div class="para">
+ Click the Edit icon to modify a value. If you are viewing Hypervisor Capabilities, you must click the name of the hypervisor first to display the editing screen.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/globally-configured-limit.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/globally-configured-limit.html b/docs/tmp/en-US/epub/OEBPS/globally-configured-limit.html
new file mode 100644
index 0000000..66fc3d5
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/globally-configured-limit.html
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.3. Globally Configured Limits</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="globally-configured-limit"><div class="titlepage"><div><div><h1 class="title" id="globally-configured-limit">14.3. Globally Configured Limits</h1></div></div></div><div class="para">
+ In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses.
+ </div><div class="para">
+ The following table lists limits set in the Global Configuration:
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ <div class="para">
+ Parameter Name
+ </div>
+ </th><th>
+ <div class="para">
+ Definition
+ </div>
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ max.account.public.ips
+ </div>
+ </td><td>
+ <div class="para">
+ Number of public IP addresses that can be owned by an account
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.account.snapshots
+ </div>
+ </td><td>
+ <div class="para">
+ Number of snapshots that can exist for an account
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.account.templates
+ </div>
+ </td><td>
+ <div class="para">
+ Number of templates that can exist for an account
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.account.user.vms
+ </div>
+ </td><td>
+ <div class="para">
+ Number of virtual machine instances that can exist for an account
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.account.volumes
+ </div>
+ </td><td>
+ <div class="para">
+ Number of disk volumes that can exist for an account
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.template.iso.size
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum size for a downloaded template or ISO in GB
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ max.volume.size.gb
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum size for a volume in GB
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ network.throttling.rate
+ </div>
+ </td><td>
+ <div class="para">
+ Default data transfer rate in megabits per second allowed per user (supported on XenServer)
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ snapshot.max.hourly
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ snapshot.max.daily
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ snapshot.max.weekly
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled
+ </div>
+ </td></tr><tr><td>
+ <div class="para">
+ snapshot.max.monthly
+ </div>
+ </td><td>
+ <div class="para">
+ Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled.
+ </div>
+ </td></tr></tbody></table></div><div class="para">
+ To modify global configuration parameters, use the global configuration screen in the CloudStack UI. See Setting Global Configuration Parameters
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/guest-ip-ranges.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/guest-ip-ranges.html b/docs/tmp/en-US/epub/OEBPS/guest-ip-ranges.html
new file mode 100644
index 0000000..291c62f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/guest-ip-ranges.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.10. Guest IP Ranges</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="guest-ip-ranges"><div class="titlepage"><div><div><h1 class="title" id="guest-ip-ranges">15.10. Guest IP Ranges</h1></div></div></div><div class="para">
+ The IP ranges for guest network traffic are set on a per-account basis by the user. This allows the users to configure their network in a fashion that will enable VPN linking between their guest network and their clients.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/ha-enabled-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/ha-enabled-vm.html b/docs/tmp/en-US/epub/OEBPS/ha-enabled-vm.html
new file mode 100644
index 0000000..0430196
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/ha-enabled-vm.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2. HA-Enabled Virtual Machines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="ha-enabled-vm"><div class="titlepage"><div><div><h1 class="title" id="ha-enabled-vm">17.2. HA-Enabled Virtual Machines</h1></div></div></div><div class="para">
+ The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudStack has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster.
+ </div><div class="para">
+ HA features work with iSCSI or NFS primary storage. HA with local storage is not supported.
+ </div></div></body></html>