You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by mu...@apache.org on 2012/12/06 09:09:12 UTC
[75/100] [abbrv] [partial] Revised en-US/network-setup.xml to include
the correct file.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/create-templates-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/create-templates-overview.html b/docs/tmp/en-US/html/create-templates-overview.html
deleted file mode 100644
index 0fa0278..0000000
--- a/docs/tmp/en-US/html/create-templates-overview.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<?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.1. Creating Templates: 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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-templates.html" title="Chapter 12. Working with Templates" /><link rel="prev" href="working-with-templates.html" title="Chapter 12. Working with Templates" /><link rel="next" href="requirements-templates.html" title="12.2. Requirements for Templates" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a clas
s="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="working-with-templates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="requirements-templates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="create-templates-overview" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="create-templates-overview">12.1. Creating Templates: Overview</h2></div></div></div><div class="para">
- CloudStack ships with a default template for the CentOS operating system. There are a variety of ways to add more templates. Administrators and end users can add templates. The typical sequence of events is:
- </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
- Launch a VM instance that has the operating system you want. Make any other desired configuration changes to the VM.
- </div></li><li class="listitem"><div class="para">
- Stop the VM.
- </div></li><li class="listitem"><div class="para">
- Convert the volume into a template.
- </div></li></ol></div><div class="para">
- There are other ways to add templates to CloudStack. For example, you can take a snapshot of the VM's volume and create a template from the snapshot, or import a VHD from another system into CloudStack
- </div><div class="para">
- The various techniques for creating templates are described in the next few sections.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="working-with-templates.html"><strong>Prev</strong>Chapter 12. Working with Templates</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="requirements-templates.html"><strong>Next</strong>12.2. Requirements for Templates</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/create-windows-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/create-windows-template.html b/docs/tmp/en-US/html/create-windows-template.html
deleted file mode 100644
index 6fb97e9..0000000
--- a/docs/tmp/en-US/html/create-windows-template.html
+++ /dev/null
@@ -1,117 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-templates.html" title="Chapter 12. Working with Templates" /><link rel="prev" href="export-template.html" title="12.9. Exporting Templates" /><link rel="next" href="import-ami.html" title="12.11. Importing Amazon Machine Images" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="export-template.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="import-ami.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="create-windows-template" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="create-windows-template">12.10. Creating a Windows Template</h2></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 xml:lang="en-US" class="section" id="sysprep-windows-server-2008R2" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sysprep-windows-server-2008R2">12.10.1. System Preparation for Windows Server 2008 R2</h3></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 xml:lang="en-US" class="section" id="sysprep-for-windows-server-2003R2" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sysprep-for-windows-server-2003R2">12.10.2. Sysprep for Windows Server 2003 R2</h3></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><ul class="docnav"><li class="previous"><a accesskey="p" href="export-template.html"><strong>Prev</strong>12.9. Exporting Templates</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="import-ami.html"><strong>Next</strong>12.11. Importing Amazon Machine Images</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/creating-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/creating-vms.html b/docs/tmp/en-US/html/creating-vms.html
deleted file mode 100644
index af008e0..0000000
--- a/docs/tmp/en-US/html/creating-vms.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="vm-lifecycle.html" title="10.3. VM Lifecycle" /><link rel="next" href="accessing-vms.html" title="10.5. Accessing VMs" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Con
tent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="vm-lifecycle.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="accessing-vms.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="creating-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="creating-vms">10.4. Creating VMs</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="vm-lifecycle.html"><strong>Prev</strong>10.3. VM Lifecycle</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="accessing-vms.html"><strong>Next</strong>10.5. Accessing VMs</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/customizing-dns.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/customizing-dns.html b/docs/tmp/en-US/html/customizing-dns.html
deleted file mode 100644
index 3d73a7e..0000000
--- a/docs/tmp/en-US/html/customizing-dns.html
+++ /dev/null
@@ -1,25 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="manage-cloud.html" title="Chapter 18. Managing the Cloud" /><link rel="prev" href="admin-alerts.html" title="18.3. Administrator Alerts" /><link rel="next" href="stop-restart-management-server.html" title="18.5. Stopping and Restarting the Management Server" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a cla
ss="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="admin-alerts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="stop-restart-management-server.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="customizing-dns" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="customizing-dns">18.4. Customizing the Network Domain Name</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="admin-alerts.html"><strong>Prev</strong>18.3. Administrator Alerts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="stop-restart-management-server.html"><strong>Next</strong>18.5. Stopping and Restarting the Management Serv...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/dates-in-usage-record.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/dates-in-usage-record.html b/docs/tmp/en-US/html/dates-in-usage-record.html
deleted file mode 100644
index 2fffffc..0000000
--- a/docs/tmp/en-US/html/dates-in-usage-record.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<?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>5.4. Dates in the Usage Record</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="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="working-with-usage-data.html" title="Chapter 5. Working With Usage Data" /><link rel="prev" href="example-response-from-listUsageRecords.html" title="5.3. Example response from listUsageRecords" /><link rel="next" href="event-types.html" title="Appendix A. Event Types" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" />
</a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="example-response-from-listUsageRecords.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="event-types.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="dates-in-usage-record" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="dates-in-usage-record">5.4. Dates in the Usage Record</h2></div></div></div><div class="para">
- Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2).
- </div><div class="para">
- Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated.
- </div><div class="para">
- For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent.
- </div><div class="para">
- There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="example-response-from-listUsageRecords.html"><strong>Prev</strong>5.3. Example response from listUsageRecords</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="event-types.html"><strong>Next</strong>Appendix A. Event Types</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/default-account-resource-limit.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/default-account-resource-limit.html b/docs/tmp/en-US/html/default-account-resource-limit.html
deleted file mode 100644
index 90818a7..0000000
--- a/docs/tmp/en-US/html/default-account-resource-limit.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="work-with-usage.html" title="Chapter 14. Working with Usage" /><link rel="prev" href="globally-configured-limit.html" title="14.3. Globally Configured Limits" /><link rel="next" href="per-domain-limits.html" title="14.5. Per-Domain Limits" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http:/
/docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="globally-configured-limit.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="per-domain-limits.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="default-account-resource-limit" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="default-account-resource-limit">14.4. Default Account Resource Limits</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="globally-configured-limit.html"><strong>Prev</strong>14.3. Globally Configured Limits</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="per-domain-limits.html"><strong>Next</strong>14.5. Per-Domain Limits</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/default-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/default-template.html b/docs/tmp/en-US/html/default-template.html
deleted file mode 100644
index 2cbfa2b..0000000
--- a/docs/tmp/en-US/html/default-template.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-templates.html" title="Chapter 12. Working with Templates" /><link rel="prev" href="best-practices-templates.html" title="12.3. Best Practices for Templates" /><link rel="next" href="private-public-template.html" title="12.5. Private and Public Templates" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="r
ight" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="best-practices-templates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="private-public-template.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="default-template" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="default-template">12.4. The Default Template</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="best-practices-templates.html"><strong>Prev</strong>12.3. Best Practices for Templates</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="private-public-template.html"><strong>Next</strong>12.5. Private and Public Templates</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/delete-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/delete-templates.html b/docs/tmp/en-US/html/delete-templates.html
deleted file mode 100644
index 14643d9..0000000
--- a/docs/tmp/en-US/html/delete-templates.html
+++ /dev/null
@@ -1,7 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-templates.html" title="Chapter 12. Working with Templates" /><link rel="prev" href="add-password-management-to-templates.html" title="12.13. Adding Password Management to Your Templates" /><link rel="next" href="storage.html" title="Chapter 13. Working With Storage" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a>
<a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="add-password-management-to-templates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="storage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="delete-templates" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="delete-templates">12.14. Deleting Templates</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="add-password-management-to-templates.html"><strong>Prev</strong>12.13. Adding Password Management to Your Templat...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="storage.html"><strong>Next</strong>Chapter 13. Working With Storage</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/deleting-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/deleting-vms.html b/docs/tmp/en-US/html/deleting-vms.html
deleted file mode 100644
index 0b94b89..0000000
--- a/docs/tmp/en-US/html/deleting-vms.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="virtual-machines.html" title="Chapter 10. Working With Virtual Machines" /><link rel="prev" href="manual-live-migration.html" title="10.9. Moving VMs Between Hosts (Manual Live Migration)" /><link rel="next" href="working-with-iso.html" title="10.11. Working with ISOs" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right"
href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="manual-live-migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="working-with-iso.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="deleting-vms" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="deleting-vms">10.10. Deleting VMs</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="manual-live-migration.html"><strong>Prev</strong>10.9. Moving VMs Between Hosts (Manual Live Migra...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="working-with-iso.html"><strong>Next</strong>10.11. Working with ISOs</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/deployment-architecture-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/deployment-architecture-overview.html b/docs/tmp/en-US/html/deployment-architecture-overview.html
deleted file mode 100644
index b6309f6..0000000
--- a/docs/tmp/en-US/html/deployment-architecture-overview.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<?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="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="concepts.html" title="Chapter 1. Concepts" /><link rel="prev" href="feature-overview.html" title="1.2. What Can CloudStack Do?" /><link rel="next" href="developer-introduction.html" title="Chapter 2. Introduction for Developers" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="feature-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="developer-introduction.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="deployment-architecture-overview" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="deployment-architecture-overview">1.3. Deployment Architecture Overview</h2></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 xml:lang="en-US" class="section" id="management-server-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="management-server-overview">1.3.1. Management Server Overview</h3></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 xml:lang="en-US" class="section" id="cloud-infrastructure-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="cloud-infrastructure-overview">1.3.2. Cloud Infrastructure Overview</h3></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 xml:lang="en-US" class="section" id="networking-overview" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="networking-overview">1.3.3. Networking Overview</h3></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><ul class="docnav"><li class="previous"><a accesskey="p" href="feature-overview.html"><strong>Prev</strong>1.2. What Can CloudStack Do?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="developer-introduction.html"><strong>Next</strong>Chapter 2. Introduction for Developers</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/developer-introduction.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/developer-introduction.html b/docs/tmp/en-US/html/developer-introduction.html
deleted file mode 100644
index 70842a4..0000000
--- a/docs/tmp/en-US/html/developer-introduction.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<?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 2. Introduction for Developers</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="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="index.html" title="CloudStack API Developer's Guide" /><link rel="prev" href="deployment-architecture-overview.html" title="1.3. Deployment Architecture Overview" /><link rel="next" href="roles.html" title="2.1. Roles" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.clouds
tack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="deployment-architecture-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="roles.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="developer-introduction" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Introduction for Developers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="roles.html">2.1. Roles</a></span></dt><dt><span class="section"><a href="api-reference.html">2.2. API Reference Documentation</a></span></dt><dt><span class="section"><a href="getting-started.html">2.3. Getting Started</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="deployment-architecture-overview.html"><strong>Prev</strong>1.3. Deployment Architecture Overview</a></li><li class="up"
><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="roles.html"><strong>Next</strong>2.1. Roles</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/disable-enable-zones-pods-clusters.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/disable-enable-zones-pods-clusters.html b/docs/tmp/en-US/html/disable-enable-zones-pods-clusters.html
deleted file mode 100644
index 4da839d..0000000
--- a/docs/tmp/en-US/html/disable-enable-zones-pods-clusters.html
+++ /dev/null
@@ -1,28 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="working-with-hosts.html" title="Chapter 11. Working With Hosts" /><link rel="prev" href="scheduled-maintenance-maintenance-mode-hosts.html" title="11.2. Scheduled Maintenance and Maintenance Mode for Hosts" /><link rel="next" href="removing-hosts.html" title="11.4. Removing Hosts" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.
png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="scheduled-maintenance-maintenance-mode-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="removing-hosts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="disable-enable-zones-pods-clusters" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="disable-enable-zones-pods-clusters">11.3. Disabling and Enabling Zones, Pods, and Clusters</h2></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" /></span>
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="scheduled-maintenance-maintenance-mode-hosts.html"><strong>Prev</strong>11.2. Scheduled Maintenance and Maintenance Mode ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="removing-hosts.html"><strong>Next</strong>11.4. Removing Hosts</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/dns-dhcp.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/dns-dhcp.html b/docs/tmp/en-US/html/dns-dhcp.html
deleted file mode 100644
index 316525f..0000000
--- a/docs/tmp/en-US/html/dns-dhcp.html
+++ /dev/null
@@ -1,5 +0,0 @@
-<?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="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="networks.html" title="Chapter 15. Managing Networks and Traffic" /><link rel="prev" href="ip-load-balancing.html" title="15.15. IP Load Balancing" /><link rel="next" href="vpn.html" title="15.17. VPN" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/ima
ge_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ip-load-balancing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="vpn.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="dns-dhcp" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="dns-dhcp">15.16. DNS and DHCP</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="ip-load-balancing.html"><strong>Prev</strong>15.15. IP Load Balancing</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="vpn.html"><strong>Next</strong>15.17. VPN</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/enabling-api-call-expiration.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/enabling-api-call-expiration.html b/docs/tmp/en-US/html/enabling-api-call-expiration.html
deleted file mode 100644
index 74d70d9..0000000
--- a/docs/tmp/en-US/html/enabling-api-call-expiration.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<?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>4.2. Enabling API Call Expiration</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="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="api-calls.html" title="Chapter 4. Calling the CloudStack API" /><link rel="prev" href="making-api-request.html" title="4.1. Making API Requests" /><link rel="next" href="signing-api-requests.html" title="4.3. Signing API Requests" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://doc
s.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="making-api-request.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="signing-api-requests.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="enabling-api-call-expiration" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="enabling-api-call-expiration">4.2. Enabling API Call Expiration</h2></div></div></div><div class="para">
- You can set an expiry timestamp on API calls to prevent replay attacks over non-secure channels, such as HTTP. The server tracks the expiry timestamp you have specified and rejects all the subsequent API requests that come in after this validity period.
- </div><div class="para">
- To enable this feature, add the following parameters to the API request:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- signatureVersion=3: If the signatureVersion parameter is missing or is not equal to 3, the expires parameter is ignored in the API request.
- </div></li><li class="listitem"><div class="para">
- expires=YYYY-MM-DDThh:mm:ssZ: Specifies the date and time at which the signature included in the request is expired. The timestamp is expressed in the YYYY-MM-DDThh:mm:ssZ format, as specified in the ISO 8601 standard.
- </div></li></ul></div><div class="para">
- For example:
- </div><pre class="programlisting">expires=2011-10-10T12:00:00+0530</pre><div class="para">
- A sample API request with expiration is given below:
- </div><pre class="programlisting">http://<IPAddress>:8080/client/api?command=listZones&signatureVersion=3&expires=2011-10-10T12:00:00+0530&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="making-api-request.html"><strong>Prev</strong>4.1. Making API Requests</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="signing-api-requests.html"><strong>Next</strong>4.3. Signing API Requests</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d8e31c7a/docs/tmp/en-US/html/event-types.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/event-types.html b/docs/tmp/en-US/html/event-types.html
deleted file mode 100644
index 4731754..0000000
--- a/docs/tmp/en-US/html/event-types.html
+++ /dev/null
@@ -1,446 +0,0 @@
-<?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 A. 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="Apache_CloudStack-API_Developers_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack API Developer's Guide" /><link rel="up" href="index.html" title="CloudStack API Developer's Guide" /><link rel="prev" href="dates-in-usage-record.html" title="5.4. Dates in the Usage Record" /><link rel="next" href="alerts.html" title="Appendix B. Alerts" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Com
mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="dates-in-usage-record.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="alerts.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="event-types" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Event Types</h1></div></div></div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col width="33%" /></colgroup><tbody><tr><td align="left">
- <div class="para">
- VM.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.EXTRACT
- </div>
- </td><td align="left">
- <div class="para">
- SG.REVOKE.INGRESS
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.DESTROY
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.UPLOAD
- </div>
- </td><td align="left">
- <div class="para">
- HOST.RECONNECT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.START
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.CLEANUP
- </div>
- </td><td align="left">
- <div class="para">
- MAINT.CANCEL
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.STOP
- </div>
- </td><td align="left">
- <div class="para">
- VOLUME.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- MAINT.CANCEL.PS
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.REBOOT
- </div>
- </td><td align="left">
- <div class="para">
- VOLUME.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- MAINT.PREPARE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.UPGRADE
- </div>
- </td><td align="left">
- <div class="para">
- VOLUME.ATTACH
- </div>
- </td><td align="left">
- <div class="para">
- MAINT.PREPARE.PS
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VM.RESETPASSWORD
- </div>
- </td><td align="left">
- <div class="para">
- VOLUME.DETACH
- </div>
- </td><td align="left">
- <div class="para">
- VPN.REMOTE.ACCESS.CREATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- VOLUME.UPLOAD
- </div>
- </td><td align="left">
- <div class="para">
- VPN.USER.ADD
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.DESTROY
- </div>
- </td><td align="left">
- <div class="para">
- SERVICEOFFERING.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- VPN.USER.REMOVE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.START
- </div>
- </td><td align="left">
- <div class="para">
- SERVICEOFFERING.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- NETWORK.RESTART
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.STOP
- </div>
- </td><td align="left">
- <div class="para">
- SERVICEOFFERING.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- UPLOAD.CUSTOM.CERTIFICATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.REBOOT
- </div>
- </td><td align="left">
- <div class="para">
- DOMAIN.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- UPLOAD.CUSTOM.CERTIFICATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ROUTER.HA
- </div>
- </td><td align="left">
- <div class="para">
- DOMAIN.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- STATICNAT.DISABLE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- DOMAIN.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.CREATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.DESTROY
- </div>
- </td><td align="left">
- <div class="para">
- SNAPSHOT.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.DESTROY
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.START
- </div>
- </td><td align="left">
- <div class="para">
- SNAPSHOT.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.START
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.STOP
- </div>
- </td><td align="left">
- <div class="para">
- SNAPSHOTPOLICY.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.STOP
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.REBOOT
- </div>
- </td><td align="left">
- <div class="para">
- SNAPSHOTPOLICY.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.REBOOT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- PROXY.HA
- </div>
- </td><td align="left">
- <div class="para">
- SNAPSHOTPOLICY.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- SSVM.H
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- VNC.CONNECT
- </div>
- </td><td align="left">
- <div class="para">
- VNC.DISCONNECT
- </div>
- </td><td align="left">
- <div class="para">
- NET.IPASSIGN
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- NET.IPRELEASE
- </div>
- </td><td align="left">
- <div class="para">
- NET.RULEADD
- </div>
- </td><td align="left">
- <div class="para">
- NET.RULEDELETE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- NET.RULEMODIFY
- </div>
- </td><td align="left">
- <div class="para">
- NETWORK.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- NETWORK.DELETE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- LB.ASSIGN.TO.RULE
- </div>
- </td><td align="left">
- <div class="para">
- LB.REMOVE.FROM.RULE
- </div>
- </td><td align="left">
- <div class="para">
- LB.CREATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- LB.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- LB.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- USER.LOGIN
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- USER.LOGOUT
- </div>
- </td><td align="left">
- <div class="para">
- USER.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- USER.DELETE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- USER.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- USER.DISABLE
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.CREATE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- TEMPLATE.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.UPDATE
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.COPY
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- TEMPLATE.DOWNLOAD.START
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.DOWNLOAD.SUCCESS
- </div>
- </td><td align="left">
- <div class="para">
- TEMPLATE.DOWNLOAD.FAILED
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ISO.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- ISO.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- ISO.COPY
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ISO.ATTACH
- </div>
- </td><td align="left">
- <div class="para">
- ISO.DETACH
- </div>
- </td><td align="left">
- <div class="para">
- ISO.EXTRACT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ISO.UPLOAD
- </div>
- </td><td align="left">
- <div class="para">
- SERVICE.OFFERING.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- SERVICE.OFFERING.EDIT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- SERVICE.OFFERING.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- DISK.OFFERING.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- DISK.OFFERING.EDIT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- DISK.OFFERING.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- NETWORK.OFFERING.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- NETWORK.OFFERING.EDIT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- NETWORK.OFFERING.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- POD.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- POD.EDIT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- POD.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- ZONE.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- ZONE.EDIT
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- ZONE.DELETE
- </div>
- </td><td align="left">
- <div class="para">
- VLAN.IP.RANGE.CREATE
- </div>
- </td><td align="left">
- <div class="para">
- VLAN.IP.RANGE.DELETE
- </div>
- </td></tr><tr><td align="left">
- <div class="para">
- CONFIGURATION.VALUE.EDIT
- </div>
- </td><td align="left">
- <div class="para">
- SG.AUTH.INGRESS
- </div>
- </td><td align="left">
- <div class="para">
- </div>
- </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="dates-in-usage-record.html"><strong>Prev</strong>5.4. Dates in the Usage Record</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="alerts.html"><strong>Next</strong>Appendix B. Alerts</a></li></ul></body></html>