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 2013/01/11 22:02:57 UTC
[43/52] [partial] CLOUDSTACK-961: Added dependencies for building
RPMs.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/configuring-projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/configuring-projects.html b/docs/tmp/en-US/html/configuring-projects.html
new file mode 100644
index 0000000..efd1ee9
--- /dev/null
+++ b/docs/tmp/en-US/html/configuring-projects.html
@@ -0,0 +1,184 @@
+<?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.2. Configuring Projects</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="projects.html" title="Chapter 6. Using Projects to Organize Users and Resources" /><link rel="prev" href="projects-overview.html" title="6.1. Overview of Projects" /><link rel="next" href="create-new-projects.html" title="6.3. Creating a New Project" /></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="projects-overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="create-new-projects.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="configuring-projects" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="configuring-projects">6.2. Configuring Projects</h2></div></div></div><div class="para">
+ Before CloudStack users start using projects, the CloudStack administrator must set up various systems to support them, including membership invitations, limits on project resources, and controls on who can create projects.
+ </div><div xml:lang="en-US" class="section" id="set-up-invitations" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="set-up-invitations">6.2.1. Setting Up Invitations</h3></div></div></div><div class="para">
+ CloudStack can be set up either so that project administrators can add people directly to a project, or so that it is necessary to send an invitation which the recipient must accept. The invitation can be sent by email or through the user’s CloudStack account. If you want administrators to use invitations to add members to projects, turn on and set up the invitations feature in CloudStack.
+ </div><div class="itemizedlist"><ul><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 Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type project and click the search button.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type project and click the search button.
+ <span class="inlinemediaobject"><img src="./images/search-button.png" alt="searchbutton.png: Searches projects" /></span>
+ </div></li><li class="listitem"><div class="para">
+ In the search results, you will see a few other parameters you need to set to control how invitations behave. The table below shows global configuration parameters related to project invitations. Click the edit button to set each parameter
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th align="left">
+ <div class="para">
+ Configuration Parameters
+ </div>
+ </th><th align="left">
+ <div class="para">
+ Description
+ </div>
+ </th></tr></thead><tbody><tr><td align="left">
+ <div class="para">
+ project.invite.required
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Set to true to turn on the invitations feature.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.email.sender
+ </div>
+ </td><td align="left">
+ <div class="para">
+ The email address to show in the From field of invitation emails.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.invite.timeout
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Amount of time to allow for a new member to respond to the invitation.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.smtp.host
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Name of the host that acts as an email server to handle invitations.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.smtp.password
+ </div>
+ </td><td align="left">
+ <div class="para">
+ (Optional) Password required by the SMTP server. You must also set project.smtp.username and set project.smtp.useAuth to true.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.smtp.port
+ </div>
+ </td><td align="left">
+ <div class="para">
+ SMTP server’s listening port.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.smtp.useAuth
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Set to true if the SMTP server requires a username and password.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ project.smtp.username
+ </div>
+ </td><td align="left">
+ <div class="para">
+ (Optional) User name required by the SMTP server for authentication. You must also set project.smtp.password and set project.smtp.useAuth to true..
+ </div>
+ </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
+ Restart the Management Server
+ </div><pre class="programlisting">service cloud-management restart</pre></li></ul></div></div><div xml:lang="en-US" class="section" id="set-resource-limits-for-projects" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="set-resource-limits-for-projects">6.2.2. Setting Resource Limits for Projects</h3></div></div></div><div class="para">
+ The CloudStack administrator can set global default limits to control the amount of resources that can be owned by each project in the cloud. This serves to prevent uncontrolled usage of resources such as snapshots, IP addresses, and virtual machine instances. Domain administrators can override these resource limits for individual projects with their domains, as long as the new limits are below the global defaults set by the CloudStack root administrator. The root administrator can also set lower resource limits for any project in the cloud
+ </div><div xml:lang="en-US" class="section" id="set-per-project-resource-limits" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="set-per-project-resource-limits">6.2.2.1. Setting Per-Project Resource Limits</h4></div></div></div><div class="para">
+ The CloudStack root administrator or the domain administrator of the domain where the project resides can set new resource limits for an individual project. The project owner can set resource limits only if the owner is also a domain or root administrator.
+ </div><div class="para">
+ The new limits must be below the global default limits set by the CloudStack administrator (as described in <a class="xref" href="configuring-projects.html#set-resource-limits-for-projects">Section 6.2.2, “Setting Resource Limits for Projects”</a>). If the project already owns more of a given type of resource than the new maximum, the resources are not affected; however, the project can not add any new resources of that type until the total drops below the new limit.
+ </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, choose Projects.
+ </div></li><li class="listitem"><div class="para">
+ Click the name of the project you want to work with.
+ </div></li><li class="listitem"><div class="para">
+ Click the Resources tab. This tab lists the current maximum amount that the project is allowed to own for each type of resource.
+ </div></li><li class="listitem"><div class="para">
+ Type new values for one or more resources.
+ </div></li><li class="listitem"><div class="para">
+ Click Apply.
+ </div></li></ol></div></div><div xml:lang="en-US" class="section" id="set-global-project-resource-limits" lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="set-global-project-resource-limits">6.2.2.2. Setting the Global Project Resource Limits</h4></div></div></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 Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type max.projects and click the search button.
+ </div></li><li class="listitem"><div class="para">
+ In the search results, you will see the parameters you can use to set per-project maximum resource amounts that apply to all projects in the cloud. No project can have more resources, but an individual project can have lower limits. Click the edit button to set each parameter.
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="editbutton.png: Edits parameters" /></span>
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td align="left">
+ <div class="para">
+ max.project.public.ips
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ max.project.snapshots
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Maximum number of snapshots that can be owned by any project in the cloud. See Working with Snapshots.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ max.project.templates
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Maximum number of templates that can be owned by any project in the cloud. See Working with Templates.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ max.project.uservms
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Maximum number of guest virtual machines that can be owned by any project in the cloud. See Working With Virtual Machines.
+ </div>
+ </td></tr><tr><td align="left">
+ <div class="para">
+ max.project.volumes
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes.
+ </div>
+ </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
+ Restart the Management Server.
+ </div><pre class="programlisting"># service cloud-management restart</pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="set-projects-creator-permissions" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="set-projects-creator-permissions">6.2.3. Setting Project Creator Permissions</h3></div></div></div><div class="para">
+ You can configure CloudStack to allow any user to create a new project, or you can restrict that ability to just CloudStack administrators.
+ </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 Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type allow.user.create.projects.
+ </div></li><li class="listitem"><div class="para">
+ Click the edit button to set the parameter.
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="editbutton.png: Edits parameters" /></span>
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td align="left">
+ <div class="para">
+ allow.user.create.projects
+ </div>
+ </td><td align="left">
+ <div class="para">
+ Set to true to allow end users to create projects. Set to false if you want only the CloudStack root administrator and domain administrators to create projects.
+ </div>
+ </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
+ Restart the Management Server.
+ </div><pre class="programlisting"># service cloud-management restart</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="projects-overview.html"><strong>Prev</strong>6.1. Overview of Projects</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="create-new-projects.html"><strong>Next</strong>6.3. Creating a New Project</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/console-proxy.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/console-proxy.html b/docs/tmp/en-US/html/console-proxy.html
new file mode 100644
index 0000000..55792a5
--- /dev/null
+++ b/docs/tmp/en-US/html/console-proxy.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>16.3. Console Proxy</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-system-vm.html" title="Chapter 16. Working with System Virtual Machines" /><link rel="prev" href="multiple-system-vm-vmware.html" title="16.2. Multiple System VM Support for VMware" /><link rel="next" href="virtual-router.html" title="16.4. Virtual Router" /></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="multiple-system-vm-vmware.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="virtual-router.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="console-proxy" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="console-proxy">16.3. Console Proxy</h2></div></div></div><div class="para">
+ The Console Proxy is a type of System Virtual Machine that has a role in presenting a console view via the web UI. It connects the user’s browser to the VNC port made available via the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a console connection.
+ </div><div class="para">
+ Clicking on a console icon brings up a new window. The AJAX code downloaded into that window refers to the public IP address of a console proxy VM. There is exactly one public IP address allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then proxies the connection to the VNC port for the requested VM on the Host hosting the guest. .
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The hypervisors will have many ports assigned to VNC usage so that multiple VNC sessions can occur simultaneously.
+ </div></div></div><div class="para">
+ There is never any traffic to the guest virtual IP, and there is no need to enable VNC within the guest.
+ </div><div class="para">
+ The console proxy VM will periodically report its active session count to the Management Server. The default reporting interval is five seconds. This can be changed through standard Management Server configuration with the parameter consoleproxy.loadscan.interval.
+ </div><div class="para">
+ Assignment of guest VM to console proxy is determined by first determining if the guest VM has a previous session associated with a console proxy. If it does, the Management Server will assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. Failing that, the first available running Console Proxy VM that has the capacity to handle new sessions is used.
+ </div><div class="para">
+ Console proxies can be restarted by administrators but this will interrupt existing console sessions for users.
+ </div><div class="para">
+ The console viewing functionality uses a dynamic DNS service under the domain name realhostip.com to assist in providing SSL security to console sessions. The console proxy is assigned a public IP address. In order to avoid browser warnings for mismatched SSL certificates, the URL for the new console window is set to the form of https://aaa-bbb-ccc-ddd.realhostip.com. Customers will see this URL during console session creation. CloudStack includes the realhostip.com SSL certificate in the console proxy VM. Of course, CloudStack cannot know about DNS A records for our customers' public IPs prior to shipping the software. CloudStack therefore runs a dynamic DNS server that is authoritative for the realhostip.com domain. It maps the aaa-bbb-ccc-ddd part of the DNS name to the IP address aaa.bbb.ccc.ddd on lookups. This allows the browser to correctly connect to the console proxy's public IP, where it then expects and receives a SSL certificate for realhostip.com, and SSL is set up wi
thout browser warnings.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="multiple-system-vm-vmware.html"><strong>Prev</strong>16.2. Multiple System VM Support for VMware</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="virtual-router.html"><strong>Next</strong>16.4. Virtual Router</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/convert-hyperv-vm-to-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/convert-hyperv-vm-to-template.html b/docs/tmp/en-US/html/convert-hyperv-vm-to-template.html
new file mode 100644
index 0000000..6afcc87
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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="import-ami.html" title="12.11. Importing Amazon Machine Images" /><link rel="next" href="add-password-management-to-templates.html" title="12.13. Adding Password Management to Your 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="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="import-ami.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="add-password-management-to-templates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="convert-hyperv-vm-to-template" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="convert-hyperv-vm-to-template">12.12. Converting a Hyper-V VM to a Template</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="import-ami.html"><strong>Prev</strong>12.11. Importing Amazon Machine Images</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="add-password-management-to-templates.html"><strong>Next</strong>12.13. Adding Password Management to Your Templat...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/create-new-projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/create-new-projects.html b/docs/tmp/en-US/html/create-new-projects.html
new file mode 100644
index 0000000..0451f35
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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="projects.html" title="Chapter 6. Using Projects to Organize Users and Resources" /><link rel="prev" href="configuring-projects.html" title="6.2. Configuring Projects" /><link rel="next" href="add-members-to-projects.html" title="6.4. Adding Members to a Project" /></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="configuring-projects.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="add-members-to-projects.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="create-new-projects" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="create-new-projects">6.3. Creating a New Project</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring-projects.html"><strong>Prev</strong>6.2. Configuring Projects</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="add-members-to-projects.html"><strong>Next</strong>6.4. Adding Members to a Project</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/create-template-from-existing-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/create-template-from-existing-vm.html b/docs/tmp/en-US/html/create-template-from-existing-vm.html
new file mode 100644
index 0000000..d8c5543
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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="private-public-template.html" title="12.5. Private and Public Templates" /><link rel="next" href="create-template-from-snapshot.html" title="12.7. Creating a Template from a Snapshot" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_le
ft.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="private-public-template.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="create-template-from-snapshot.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="create-template-from-existing-vm" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="create-template-from-existing-vm">12.6. Creating a Template from an Existing Virtual Machine</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="private-public-template.html"><strong>Prev</strong>12.5. Private and Public 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="create-template-from-snapshot.html"><strong>Next</strong>12.7. Creating a Template from a Snapshot</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/create-template-from-snapshot.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/create-template-from-snapshot.html b/docs/tmp/en-US/html/create-template-from-snapshot.html
new file mode 100644
index 0000000..aa165d0
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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="create-template-from-existing-vm.html" title="12.6. Creating a Template from an Existing Virtual Machine" /><link rel="next" href="upload-template.html" title="12.8. Uploading Templates" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="P
roduct 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="create-template-from-existing-vm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="upload-template.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="create-template-from-snapshot" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="create-template-from-snapshot">12.7. Creating a Template from a Snapshot</h2></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><ul class="docnav"><li class="previous"><a accesskey="p" href="create-template-from-existing-vm.html"><strong>Prev</strong>12.6. Creating a Template from an Existing Virtua...</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="upload-template.html"><strong>Next</strong>12.8. Uploading Templates</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/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
new file mode 100644
index 0000000..0fa0278
--- /dev/null
+++ b/docs/tmp/en-US/html/create-templates-overview.html
@@ -0,0 +1,15 @@
+<?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/92d4b214/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
new file mode 100644
index 0000000..6fb97e9
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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/92d4b214/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
new file mode 100644
index 0000000..af008e0
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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/92d4b214/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
new file mode 100644
index 0000000..8c72e2d
--- /dev/null
+++ b/docs/tmp/en-US/html/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.5. 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.4. Administrator Alerts" /><link rel="next" href="stop-restart-management-server.html" title="18.6. 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.5. 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.4. 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.6. Stopping and Restarting the Management Serv...</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/docs/tmp/en-US/html/database-replication.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/html/database-replication.html b/docs/tmp/en-US/html/database-replication.html
new file mode 100644
index 0000000..73cbd3c
--- /dev/null
+++ b/docs/tmp/en-US/html/database-replication.html
@@ -0,0 +1,96 @@
+<?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>9.3. Database Replication (Optional)</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-Installation_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Installation Guide" /><link rel="up" href="additional-installation-options.html" title="Chapter 9. Additional Installation Options" /><link rel="prev" href="ssl.html" title="9.2. SSL (Optional)" /><link rel="next" href="choosing-a-deployment_architecture.html" title="Chapter 10. Choosing a Deployment Architecture" /></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="ssl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="choosing-a-deployment_architecture.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="database-replication" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="database-replication">9.3. Database Replication (Optional)</h2></div></div></div><div class="para">
+ CloudStack supports database replication from one MySQL node to another. This is achieved using standard MySQL replication. You may want to do this as insurance against MySQL server or storage loss. MySQL replication is implemented using a master/slave model. The master is the node that the Management Servers are configured to use. The slave is a standby node that receives all write operations from the master and applies them to a local, redundant copy of the database. The following steps are a guide to implementing MySQL replication.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Creating a replica is not a backup solution. You should develop a backup procedure for the MySQL data that is distinct from replication.
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Ensure that this is a fresh install with no data in the master.
+ </div></li><li class="listitem"><div class="para">
+ Edit my.cnf on the master and add the following in the [mysqld] section below datadir.
+ </div><pre class="programlisting">
+log_bin=mysql-bin
+server_id=1
+</pre><div class="para">
+ The server_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc.
+ </div></li><li class="listitem"><div class="para">
+ Restart the MySQL service:
+ </div><pre class="programlisting">
+# service mysqld restart
+</pre></li><li class="listitem"><div class="para">
+ Create a replication account on the master and give it privileges. We will use the "cloud-repl" user with the password "password". This assumes that master and slave run on the 172.16.1.0/24 network.
+ </div><pre class="programlisting">
+# mysql -u root
+mysql> create user 'cloud-repl'@'172.16.1.%' identified by 'password';
+mysql> grant replication slave on *.* TO 'cloud-repl'@'172.16.1.%';
+mysql> flush privileges;
+mysql> flush tables with read lock;
+</pre></li><li class="listitem"><div class="para">
+ Leave the current MySQL session running.
+ </div></li><li class="listitem"><div class="para">
+ In a new shell start a second MySQL session.
+ </div></li><li class="listitem"><div class="para">
+ Retrieve the current position of the database.
+ </div><pre class="programlisting">
+# mysql -u root
+mysql> show master status;
++------------------+----------+--------------+------------------+
+| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
++------------------+----------+--------------+------------------+
+| mysql-bin.000001 | 412 | | |
++------------------+----------+--------------+------------------+
+</pre></li><li class="listitem"><div class="para">
+ Note the file and the position that are returned by your instance.
+ </div></li><li class="listitem"><div class="para">
+ Exit from this session.
+ </div></li><li class="listitem"><div class="para">
+ Complete the master setup. Returning to your first session on the master, release the locks and exit MySQL.
+ </div><pre class="programlisting">
+mysql> unlock tables;
+</pre></li><li class="listitem"><div class="para">
+ Install and configure the slave. On the slave server, run the following commands.
+ </div><pre class="programlisting">
+# yum install mysql-server
+# chkconfig mysqld on
+</pre></li><li class="listitem"><div class="para">
+ Edit my.cnf and add the following lines in the [mysqld] section below datadir.
+ </div><pre class="programlisting">
+server_id=2
+innodb_rollback_on_timeout=1
+innodb_lock_wait_timeout=600
+</pre></li><li class="listitem"><div class="para">
+ Restart MySQL.
+ </div><pre class="programlisting">
+# service mysqld restart
+</pre></li><li class="listitem"><div class="para">
+ Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps.
+ </div><pre class="programlisting">
+mysql> change master to
+ -> master_host='172.16.1.217',
+ -> master_user='cloud-repl',
+ -> master_password='password',
+ -> master_log_file='mysql-bin.000001',
+ -> master_log_pos=412;
+</pre></li><li class="listitem"><div class="para">
+ Then start replication on the slave.
+ </div><pre class="programlisting">
+mysql> start slave;
+</pre></li><li class="listitem"><div class="para">
+ Optionally, open port 3306 on the slave as was done on the master earlier.
+ </div><div class="para">
+ This is not required for replication to work. But if you choose not to do this, you will need to do it when failover to the replica occurs.
+ </div></li></ol></div><div class="section" id="database-failover"><div class="titlepage"><div><div><h3 class="title" id="database-failover">9.3.1. Failover</h3></div></div></div><div class="para">
+ This will provide for a replicated database that can be used to implement manual failover for the Management Servers. CloudStack failover from one MySQL instance to another is performed by the administrator. In the event of a database failure you should:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Stop the Management Servers (via service cloud-management stop).
+ </div></li><li class="listitem"><div class="para">
+ Change the replica's configuration to be a master and restart it.
+ </div></li><li class="listitem"><div class="para">
+ Ensure that the replica's port 3306 is open to the Management Servers.
+ </div></li><li class="listitem"><div class="para">
+ Make a change so that the Management Server uses the new database. The simplest process here is to put the IP address of the new database server into each Management Server's /etc/cloud/management/db.properties.
+ </div></li><li class="listitem"><div class="para">
+ Restart the Management Servers:
+ </div><pre class="programlisting">
+# service cloud-management start
+</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ssl.html"><strong>Prev</strong>9.2. SSL (Optional)</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="choosing-a-deployment_architecture.html"><strong>Next</strong>Chapter 10. Choosing a Deployment Architecture</a></li></ul></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/92d4b214/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
new file mode 100644
index 0000000..90818a7
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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/92d4b214/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
new file mode 100644
index 0000000..2cbfa2b
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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/92d4b214/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
new file mode 100644
index 0000000..14643d9
--- /dev/null
+++ b/docs/tmp/en-US/html/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="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>