You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2012/11/07 19:01:13 UTC
[47/52] [abbrv] [partial] CLOUDSTACK-444 Fix from Radhika PC against
docs, adds network setup in the install guide.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/work-with-usage.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/work-with-usage.html b/docs/tmp/en-US/epub/OEBPS/work-with-usage.html
new file mode 100644
index 0000000..3cf7dcd
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/work-with-usage.html
@@ -0,0 +1,129 @@
+<?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 14. Working with Usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="work-with-usage"><div class="titlepage"><div><div><h1 class="title">Chapter 14. Working with Usage</h1></div></div></div><div class="para">
+ The Usage Server is an optional, separately-installed part of CloudStack that provides aggregated usage records which you can use to create billing integration for CloudStack. The Usage Server works by taking data from the events log and creating summary usage records that you can access using the listUsageRecords API call.
+ </div><div class="para">
+ The usage records show the amount of resources, such as VM run time or template storage space, consumed by guest instances.
+ </div><div class="para">
+ The Usage Server runs at least once per day. It can be configured to run multiple times per day.
+ </div><div class="section" id="configure-usage-server"><div class="titlepage"><div><div><h1 class="title" id="configure-usage-server">14.1. Configuring the Usage Server</h1></div></div></div><div class="para">
+ To configure the usage server:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Be sure the Usage Server has been installed. This requires extra steps beyond just installing the CloudStack software. See Installing the Usage Server (Optional) in the Advanced Installation Guide.
+ </div></li><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as administrator.
+ </div></li><li class="listitem"><div class="para">
+ Click Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters.
+ </div></li><li class="listitem"><div class="para">
+ In Actions, click the Edit icon.
+ </div></li><li class="listitem"><div class="para">
+ Type the desired value and click the Save icon.
+ </div></li><li class="listitem"><div class="para">
+ Restart the Management Server (as usual with any global configuration change) and also the Usage Server:
+ </div><pre class="programlisting"># service cloud-management restart
+# service cloud-usage restart
+</pre></li></ol></div><div class="para">
+ The following table shows the global configuration settings that control the behavior of the Usage Server.
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th style="text-align: left">
+ <div class="para">
+ Parameter Name
+ </div>
+ </th><th style="text-align: left">
+ <div class="para">
+ Description
+ </div>
+ </th></tr></thead><tbody><tr><td style="text-align: left">
+ <div class="para">
+ enable.usage.server
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Whether the Usage Server is active.
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ usage.aggregation.timezone
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT:
+ </div>
+
+<pre class="programlisting">usage.stats.job.exec.time = 00:15
+usage.execution.timezone = PST
+usage.aggregation.timezone = GMT
+</pre>
+ <div class="para">
+ Valid values for the time zone are specified in <a class="xref" href="time-zones.html">Appendix A, <em>Time Zones</em></a>
+ </div>
+ <div class="para">
+ Default: GMT
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ usage.execution.timezone
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ The time zone of usage.stats.job.exec.time. Valid values for the time zone are specified in <a class="xref" href="time-zones.html">Appendix A, <em>Time Zones</em></a>
+ </div>
+ <div class="para">
+ Default: The time zone of the management server.
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ usage.sanity.check.interval
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range. If any issue is found, the alert ALERT_TYPE_USAGE_SANITY_RESULT = 21 is sent.
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ usage.stats.job.aggregation.range
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run.
+ </div>
+ <div class="para">
+ There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. CloudStack assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. CloudStack assumes this "midnight to midnight" is relative to the usage.execution.timezone.
+ </div>
+ <div class="para">
+ Default: 1440
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ usage.stats.job.exec.time
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter "10:30".
+ </div>
+ <div class="para">
+ If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time.
+ </div>
+ <div class="para">
+ Default: 00:15.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ enable.usage.server = true
+ </div></li><li class="listitem"><div class="para">
+ usage.execution.timezone = America/New_York
+ </div></li><li class="listitem"><div class="para">
+ usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time.
+ </div></li><li class="listitem"><div class="para">
+ usage.stats.job.aggregation.range = 1440
+ </div></li></ul></div><div class="para">
+ With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New_York) time zone.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage Server will ignore the data between midnight and 2 AM. That data will be included in the next day's run
+ </div></div></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-hosts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-hosts.html b/docs/tmp/en-US/epub/OEBPS/working-with-hosts.html
new file mode 100644
index 0000000..7bef930
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-hosts.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>Chapter 11. Working With Hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="working-with-hosts"><div class="titlepage"><div><div><h1 class="title">Chapter 11. Working With Hosts</h1></div></div></div><div class="section" id="adding-hosts"><div class="titlepage"><div><div><h1 class="title" id="adding-hosts">11.1. Adding Hosts</h1></div></div></div><div class="para">
+ Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see <a class="xref" href="host-add.html">Section 7.5, “Adding a Host”</a>.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-iso.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-iso.html b/docs/tmp/en-US/epub/OEBPS/working-with-iso.html
new file mode 100644
index 0000000..3fec19f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-iso.html
@@ -0,0 +1,125 @@
+<?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.11. Working with ISOs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="working-with-iso"><div class="titlepage"><div><div><h1 class="title" id="working-with-iso">10.11. Working with ISOs</h1></div></div></div><div class="para">
+ CloudStack supports ISOs and their attachment to guest VMs. An ISO is a read-only file that has an ISO/CD-ROM style file system. Users can upload their own ISOs and mount them on their guest VMs.
+ </div><div class="para">
+ ISOs are uploaded based on a URL. HTTP is the supported protocol. Once the ISO is available via HTTP specify an upload URL such as http://my.web.server/filename.iso.
+ </div><div class="para">
+ ISOs may be public or private, like templates.ISOs are not hypervisor-specific. That is, a guest on vSphere can mount the exact same image that a guest on KVM can mount.
+ </div><div class="para">
+ ISO images may be stored in the system and made available with a privacy level similar to templates. ISO images are classified as either bootable or not bootable. A bootable ISO image is one that contains an OS image. CloudStack allows a user to boot a guest VM off of an ISO image. Users can also attach ISO images to guest VMs. For example, this enables installing PV drivers into Windows. ISO images are not hypervisor-specific.
+ </div><div class="section" id="add-iso"><div class="titlepage"><div><div><h2 class="title" id="add-iso">10.11.1. Adding an ISO</h2></div></div></div><div class="para">
+ To make additional operating system or other software available for use with guest VMs, you can add an ISO. The ISO is typically thought of as an operating system image, but you can also add ISOs for other types of software, such as desktop applications that you want to be installed as part of a template.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as an administrator or end user.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Templates.
+ </div></li><li class="listitem"><div class="para">
+ In Select View, choose ISOs.
+ </div></li><li class="listitem"><div class="para">
+ Click Add ISO.
+ </div></li><li class="listitem"><div class="para">
+ In the Add ISO screen, provide the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name</strong></span>: Short name for the ISO image. For example, CentOS 6.2 64-bit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Description</strong></span>: Display test for the ISO image. For example, CentOS 6.2 64-bit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>URL</strong></span>: The URL that hosts the ISO image. The Management Server must be able to access this location via HTTP. If needed you can place the ISO image directly on the Management Server
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Zone</strong></span>: Choose the zone where you want the ISO to be available, or All Zones to make it available throughout CloudStack.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Bootable</strong></span>: Whether or not a guest could boot off this ISO image. For example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable.
+ </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 your desired ISO image is listed, choose it.
+ </div></li><li class="listitem"><div class="para">
+ If the OS Type of the ISO is not listed or if the ISO is not bootable, choose Other.
+ </div></li><li class="listitem"><div class="para">
+ (XenServer only) If you want to boot from this ISO in PV mode, choose Other PV (32-bit) or Other PV (64-bit)
+ </div></li><li class="listitem"><div class="para">
+ (KVM only) If you choose an OS that is PV-enabled, the VMs created from this ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the VMs will have an IDE root disk. The PV-enabled types are:
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td style="text-align: left">
+ <div class="para">
+ Fedora 13
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Fedora 12
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Fedora 11
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ Fedora 10
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Fedora 9
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Other PV
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ Debian GNU/Linux
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ CentOS 5.3
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ CentOS 5.4
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ CentOS 5.5
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Red Hat Enterprise Linux 5.3
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Red Hat Enterprise Linux 5.4
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ Red Hat Enterprise Linux 5.5
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ Red Hat Enterprise Linux 6
+ </div>
+ </td><td style="text-align: left">
+ </td></tr></tbody></table></div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is not recommended to 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 usually not work. In these cases, choose Other.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Extractable</strong></span>: Choose Yes if the ISO should be available for extraction.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public</strong></span>: Choose Yes if this ISO should be available to other users.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Featured</strong></span>: Choose Yes if you would like this ISO to be more prominent for users to select. The ISO will appear in the Featured ISOs list. Only an administrator can make an ISO Featured.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click OK.
+ </div><div class="para">
+ The Management Server will download the ISO. Depending on the size of the ISO, this may take a long time. The ISO status column will display Ready once it has been successfully downloaded into secondary storage. Clicking Refresh updates the download percentage.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Important</strong></span>: Wait for the ISO to finish downloading. If you move on to the next task and try to use the ISO right away, it will appear to fail. The entire ISO must be available before CloudStack can work with it.
+ </div></li></ol></div></div><div class="section" id="attach-iso-to-vm"><div class="titlepage"><div><div><h2 class="title" id="attach-iso-to-vm">10.11.2. Attaching an ISO to a VM</h2></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ In the left navigation, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Choose the virtual machine you want to work with.
+ </div></li><li class="listitem"><div class="para">
+ Click the Attach ISO button
+ <span class="inlinemediaobject"><img src="./images/iso-icon.png" alt="iso.png: Depicts adding an iso image" /></span>
+ </div></li><li class="listitem"><div class="para">
+ In the Attach ISO dialog box, select the desired ISO.
+ </div></li><li class="listitem"><div class="para">
+ Click OK
+ </div></li></ol></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-snapshots.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-snapshots.html b/docs/tmp/en-US/epub/OEBPS/working-with-snapshots.html
new file mode 100644
index 0000000..ca18466
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-snapshots.html
@@ -0,0 +1,13 @@
+<?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>13.5. Working with Snapshots</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="working-with-snapshots"><div class="titlepage"><div><div><h1 class="title" id="working-with-snapshots">13.5. Working with Snapshots</h1></div></div></div><div class="para">
+ (Supported for the following hypervisors: <span class="bold bold"><strong>XenServer</strong></span>, <span class="bold bold"><strong>VMware vSphere</strong></span>, and <span class="bold bold"><strong>KVM</strong></span>)
+ </div><div class="para">
+ CloudStack supports snapshots of disk volumes. Snapshots are a point-in-time capture of virtual machine disks. Memory and CPU states are not captured.
+ </div><div class="para">
+ Snapshots may be taken for volumes, including both root and data disks. The administrator places a limit on the number of stored snapshots per user. Users can create new volumes from the snapshot for recovery of particular files and they can create templates from snapshots to boot from a restored disk.
+ </div><div class="para">
+ Users can create snapshots manually or by setting up automatic recurring snapshot policies. Users can also create disk volumes from snapshots, which may be attached to a VM like any other disk volume. Snapshots of both root disks and data disks are supported. However, CloudStack does not currently support booting a VM from a recovered root disk. A disk recovered from snapshot of a root disk is treated as a regular data disk; the data on recovered disk can be accessed by attaching the disk to a VM.
+ </div><div class="para">
+ A completed snapshot is copied from primary storage to secondary storage, where it is stored until deleted or purged by newer snapshot.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-system-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-system-vm.html b/docs/tmp/en-US/epub/OEBPS/working-with-system-vm.html
new file mode 100644
index 0000000..baec6ff
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-system-vm.html
@@ -0,0 +1,21 @@
+<?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 16. Working with System Virtual Machines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="working-with-system-vm"><div class="titlepage"><div><div><h1 class="title">Chapter 16. Working with System Virtual Machines</h1></div></div></div><div class="para">
+ CloudStack uses several types of system virtual machines to perform tasks in the cloud. In general CloudStack manages these system VMs and creates, starts, and stops them as needed based on scale and immediate needs. However, the administrator should be aware of them and their roles to assist in debugging issues.
+ </div><div class="section" id="system-vm-template"><div class="titlepage"><div><div><h1 class="title" id="system-vm-template">16.1. The System VM Template</h1></div></div></div><div class="para">
+ The System VMs come from a single template. The System VM has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Debian 6.0 ("Squeeze"), 2.6.32 kernel with the latest security patches from the Debian security APT repository
+ </div></li><li class="listitem"><div class="para">
+ Has a minimal set of packages installed thereby reducing the attack surface
+ </div></li><li class="listitem"><div class="para">
+ 32-bit for enhanced performance on Xen/VMWare
+ </div></li><li class="listitem"><div class="para">
+ pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors
+ </div></li><li class="listitem"><div class="para">
+ Xen tools inclusion allows performance monitoring
+ </div></li><li class="listitem"><div class="para">
+ Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed
+ </div></li><li class="listitem"><div class="para">
+ Latest version of JRE from Sun/Oracle ensures improved security and speed
+ </div></li></ul></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-templates.html b/docs/tmp/en-US/epub/OEBPS/working-with-templates.html
new file mode 100644
index 0000000..d112271
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-templates.html
@@ -0,0 +1,21 @@
+<?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 12. Working with Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="working-with-templates"><div class="titlepage"><div><div><h1 class="title">Chapter 12. Working with Templates</h1></div></div></div><div class="para">
+ A template is a reusable configuration for virtual machines. When users launch VMs, they can choose from a list of templates in CloudStack.
+ </div><div class="para">
+ Specifically, a template is a virtual disk image that includes one of a variety of operating systems, optional additional software such as office applications, and settings such as access control to determine who can use the template. Each template is associated with a particular type of hypervisor, which is specified when the template is added to CloudStack.
+ </div><div class="para">
+ CloudStack ships with a default template. In order to present more choices to users, CloudStack administrators and users can create templates and add them to CloudStack.
+ </div><div class="section" id="create-templates-overview"><div class="titlepage"><div><div><h1 class="title" id="create-templates-overview">12.1. Creating Templates: Overview</h1></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></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/working-with-volumes.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/working-with-volumes.html b/docs/tmp/en-US/epub/OEBPS/working-with-volumes.html
new file mode 100644
index 0000000..378cf53
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/working-with-volumes.html
@@ -0,0 +1,9 @@
+<?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>13.4. Using Swift for Secondary Storage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="working-with-volumes"><div class="titlepage"><div><div><h1 class="title" id="working-with-volumes">13.4. Using Swift for Secondary Storage</h1></div></div></div><div class="para">
+ A volume provides storage to a guest VM. The volume can provide for a root disk or an additional data disk. CloudStack supports additional volumes for guest VMs.
+ </div><div class="para">
+ Volumes are created for a specific hypervisor type. A volume that has been attached to guest using one hypervisor type (e.g, XenServer) may not be attached to a guest that is using another hypervisor type (e.g. vSphere, KVM). This is because the different hypervisors use different disk image formats.
+ </div><div class="para">
+ CloudStack defines a volume as a unit of storage available to a guest VM. Volumes are either root disks or data disks. The root disk has "/" in the file system and is usually the boot device. Data disks provide for additional storage (e.g. As "/opt" or "D:"). Every guest VM has a root disk, and VMs can also optionally have a data disk. End users can mount multiple data disks to guest VMs. Users choose data disks from the disk offerings created by administrators. The user can create a template from a volume as well; this is the standard procedure for private template creation. Volumes are hypervisor-specific: a volume from one hypervisor type may not be used on a guest of another hypervisor type.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/zone-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/zone-add.html b/docs/tmp/en-US/epub/OEBPS/zone-add.html
new file mode 100644
index 0000000..057e11e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/zone-add.html
@@ -0,0 +1,379 @@
+<?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>7.2. Adding a Zone</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="zone-add"><div class="titlepage"><div><div><h1 class="title" id="zone-add">7.2. Adding a Zone</h1></div></div></div><div class="para">
+ These steps assume you have already logged in to the CloudStack UI. See <a class="xref" href="ui.html#log-in">Section 5.1, “Log In to the UI”</a>.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ (Optional) If you are going to use Swift for cloud-wide secondary storage, you need to add it before you add zones.
+ </div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as administrator.
+ </div></li><li class="listitem"><div class="para">
+ If this is your first time visiting the UI, you will see the guided tour splash screen. Choose “Experienced user.” The Dashboard appears.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation bar, click Global Settings.
+ </div></li><li class="listitem"><div class="para">
+ In the search box, type swift.enable and click the search button.
+ </div></li><li class="listitem"><div class="para">
+ Click the edit button and set swift.enable to true.
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="edit-icon.png: button to modify data" /></span>
+
+ </div></li><li class="listitem"><div class="para">
+ Restart the Management Server.
+ </div><pre class="programlisting"># service cloud-management restart</pre></li><li class="listitem"><div class="para">
+ Refresh the CloudStack UI browser tab and log back in.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ In the left navigation, choose Infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ On Zones, click View More.
+ </div></li><li class="listitem"><div class="para">
+ (Optional) If you are using Swift storage, click Enable Swift. Provide the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>URL.</strong></span> The Swift URL.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Account.</strong></span> The Swift account.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> The Swift account’s username.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Key.</strong></span> The Swift key.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click Add Zone. The zone creation wizard will appear.
+ </div></li><li class="listitem"><div class="para">
+ Choose one of the following network types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Basic.</strong></span> For AWS-style networking. Provides a single network where each VM instance is assigned an IP directly from the network. 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">
+ <span class="bold bold"><strong>Advanced.</strong></span> For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support.
+ </div></li></ul></div><div class="para">
+ For more information about the network types, see Network Setup.
+ </div></li><li class="listitem"><div class="para">
+ The rest of the steps differ depending on whether you chose Basic or Advanced. Continue with the steps that apply to you:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="zone-add.html#basic-zone-configuration">Section 7.2.1, “Basic Zone Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="zone-add.html#advanced-zone-configuration">Section 7.2.2, “Advanced Zone Configuration”</a>
+ </div></li></ul></div></li></ol></div><div class="section" id="basic-zone-configuration"><div class="titlepage"><div><div><h2 class="title" id="basic-zone-configuration">7.2.1. Basic Zone Configuration</h2></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ After you select Basic in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> A name for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>DNS 1 and 2.</strong></span> These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Internal DNS 1 and Internal DNS 2.</strong></span> These are DNS servers for use by system VMs in the zone (these are VMs used by CloudStack itself, such as virtual routers, console proxies, and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Offering.</strong></span> Your choice here determines what network services will be available on the network for guest VMs.
+ </div><div class="informaltable"><table border="1"><colgroup><col style="text-align: left" class="c1" width="50%" /><col style="text-align: left" class="c2" width="50%" /></colgroup><thead><tr><th style="text-align: left">
+ <div class="para">
+ Network Offering
+ </div>
+ </th><th style="text-align: left">
+ <div class="para">
+ Description
+ </div>
+ </th></tr></thead><tbody><tr><td style="text-align: left">
+ <div class="para">
+ DefaultSharedNetworkOfferingWithSGService
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.)
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ DefaultSharedNetworkOffering
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ If you do not need security groups, choose this.
+ </div>
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ DefaultSharedNetscalerEIPandELBNetworkOffering
+ </div>
+ </td><td style="text-align: left">
+ <div class="para">
+ If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing.
+ </div>
+ </td></tr></tbody></table></div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Domain.</strong></span> (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public.</strong></span> A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Choose which traffic types will be carried by the physical network.
+ </div><div class="para">
+ The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired.
+ </div></li><li class="listitem"><div class="para">
+ (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK.
+ </div><div class="para">
+ These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created.
+ </div></li><li class="listitem"><div class="para">
+ Click Next.
+ </div></li><li class="listitem"><div class="para">
+ (NetScaler only) If you chose the network offering for NetScaler, you have an additional screen to fill out. Provide the requested details to set up the NetScaler, then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>IP address.</strong></span> The NSIP (NetScaler IP) address of the NetScaler device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username/Password.</strong></span> The authentication credentials to access the device. CloudStack uses these credentials to access the device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Type.</strong></span> NetScaler device type that is being added. It could be NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see About Using a NetScaler Load Balancer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public interface.</strong></span> Interface of NetScaler that is configured to be part of the public network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Private interface.</strong></span> Interface of NetScaler that is configured to be part of the private network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Number of retries.</strong></span> Number of times to attempt a command on the device before considering the operation failed. Default is 2.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Capacity.</strong></span> Number of guest networks/accounts that will share this NetScaler device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Dedicated.</strong></span> When marked as dedicated, this device will be dedicated to a single account. When Dedicated is checked, the value in the Capacity field has no significance – implicitly, its value is 1.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ (NetScaler only) Configure the IP range for public traffic. The IPs in this range will be used for the static NAT capability which you enabled by selecting the network offering for NetScaler with EIP and ELB. Enter the following details, then click Add. If desired, you can repeat this step to add more IP ranges. When done, click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Gateway.</strong></span> The gateway in use for these IP addresses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Netmask.</strong></span> The netmask associated with this IP range.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>VLAN.</strong></span> The VLAN that will be used for public traffic.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start IP/End IP.</strong></span> A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest VMs.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see <a class="xref" href="about-pods.html">Section 2.2, “About Pods”</a>.
+ </div><div class="para">
+ To configure the first pod, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Pod Name.</strong></span> A name for the pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system gateway.</strong></span> The gateway for the hosts in that pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system netmask.</strong></span> The network prefix that defines the pod's subnet. Use CIDR notation.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start/End Reserved System IP.</strong></span> The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Configure the network for guest traffic. Provide the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest gateway.</strong></span> The gateway that the guests should use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest netmask.</strong></span> The netmask in use on the subnet the guests will use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest start IP/End IP.</strong></span> Enter the first and last IP addresses that define a range that CloudStack can assign to guests.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet.
+ </div></li><li class="listitem"><div class="para">
+ If one NIC is used, these IPs should be in the same CIDR as the pod CIDR.
+ </div></li></ul></div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see About Clusters.
+ </div><div class="para">
+ To configure the first cluster, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Cluster name.</strong></span> Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see About Hosts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When you add a hypervisor host to CloudStack, the host must not have any VMs already running.
+ </div></div></div><div class="para">
+ Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Citrix XenServer Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ VMware vSphere Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ KVM vSphere Installation and Configuration
+ </div></li></ul></div><div class="para">
+ To configure the first host, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Name.</strong></span> The DNS name or IP address of the host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> The username is root.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Password.</strong></span> This is the password for the user named above (from your XenServer or KVM install).
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Tags.</strong></span> (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set this to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudPlatform adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see About Primary Storage.
+ </div><div class="para">
+ To configure the first primary storage server, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> The name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Protocol.</strong></span> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here.
+ </div></li></ul></div></li></ol></div></div><div class="section" id="advanced-zone-configuration"><div class="titlepage"><div><div><h2 class="title" id="advanced-zone-configuration">7.2.2. Advanced Zone Configuration</h2></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ After you select Advanced in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> A name for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>DNS 1 and 2.</strong></span> These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Internal DNS 1 and Internal DNS 2.</strong></span> These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network Domain.</strong></span> (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Guest CIDR.</strong></span> This is the CIDR that describes the IP addresses in use in the guest virtual networks in this zone. For example, 10.1.1.0/24. As a matter of good practice you should set different CIDRs for different zones. This will make it easier to set up VPNs between networks in different zones.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Public.</strong></span> A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Choose which traffic types will be carried by the physical network.
+ </div><div class="para">
+ The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see <a class="xref" href="about-physical-networks.html#advanced-zone-network-traffic-types">Section 2.7.4, “Advanced Zone Network Traffic Types”</a>. This screen starts out with one network already configured. If you have multiple physical networks, you need to add more. Drag and drop traffic types onto a greyed-out network and it will become active. You can move the traffic icons from one network to another; for example, if the default traffic types shown for Network 1 do not match your actual setup, you can move them down. You can also change the network names if desired.
+ </div></li><li class="listitem"><div class="para">
+ (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK.
+ </div><div class="para">
+ These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created.
+ </div></li><li class="listitem"><div class="para">
+ Click Next.
+ </div></li><li class="listitem"><div class="para">
+ Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Gateway.</strong></span> The gateway in use for these IP addresses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Netmask.</strong></span> The netmask associated with this IP range.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>VLAN.</strong></span> The VLAN that will be used for public traffic.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start IP/End IP.</strong></span> A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest networks.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see <a class="xref" href="about-pods.html">Section 2.2, “About Pods”</a>.
+ </div><div class="para">
+ To configure the first pod, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Pod Name.</strong></span> A name for the pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system gateway.</strong></span> The gateway for the hosts in that pod.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Reserved system netmask.</strong></span> The network prefix that defines the pod's subnet. Use CIDR notation.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Start/End Reserved System IP.</strong></span> The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see <a class="xref" href="about-physical-networks.html#system-reserved-ip-addresses">Section 2.7.7, “System Reserved IP Addresses”</a>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Specify a range of VLAN IDs to carry guest traffic for each physical network (see VLAN Allocation Example ), then click Next.
+ </div></li><li class="listitem"><div class="para">
+ In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see <a class="xref" href="about-clusters.html">Section 2.3, “About Clusters”</a>.
+ </div><div class="para">
+ To configure the first cluster, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Hypervisor.</strong></span> (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere .
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Cluster name.</strong></span> Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see <a class="xref" href="about-hosts.html">Section 2.4, “About Hosts”</a>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When you deploy CloudStack, the hypervisor host must not have any VMs already running.
+ </div></div></div><div class="para">
+ Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Citrix XenServer Installation for CloudStack
+ </div></li><li class="listitem"><div class="para">
+ VMware vSphere Installation and Configuration
+ </div></li><li class="listitem"><div class="para">
+ KVM Installation and Configuration
+ </div></li></ul></div><div class="para">
+ To configure the first host, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Name.</strong></span> The DNS name or IP address of the host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Username.</strong></span> Usually root.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Password.</strong></span> This is the password for the user named above (from your XenServer or KVM install).
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Host Tags.</strong></span> (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see <a class="xref" href="about-primary-storage.html">Section 2.5, “About Primary Storage”</a>.
+ </div><div class="para">
+ To configure the first primary storage server, enter the following, then click Next:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name.</strong></span> The name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Protocol.</strong></span> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here.
+ </div><div class="informaltable"><table border="1"><colgroup><col style="text-align: left" class="c1" width="50%" /><col style="text-align: left" class="c2" width="50%" /></colgroup><tbody><tr><td style="text-align: left">
+ <div class="para">
+ NFS
+ </div>
+ </td><td style="text-align: left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The exported path from the server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ iSCSI
+ </div>
+ </td><td style="text-align: left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Target IQN.</strong></span> The IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Lun.</strong></span> The LUN number. For example, 3.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ preSetup
+ </div>
+ </td><td style="text-align: left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the storage device.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>SR Name-Label.</strong></span> Enter the name-label of the SR that has been set up outside CloudStack.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ SharedMountPoint
+ </div>
+ </td><td style="text-align: left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The path on each host that is where this primary storage is mounted. For example, "/mnt/primary".
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr><tr><td style="text-align: left">
+ <div class="para">
+ VMFS
+ </div>
+ </td><td style="text-align: left">
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Server.</strong></span> The IP address or DNS name of the vCenter server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> A combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore".
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Tags (optional).</strong></span> The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.
+ </div></li></ul></div>
+ <div class="para">
+ The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2.
+ </div>
+
+ </td></tr></tbody></table></div></li></ul></div></li><li class="listitem"><div class="para">
+ In a new zone, CloudStack adds the first secondary storage server for you. For an overview of what secondary storage is, see <a class="xref" href="about-secondary-storage.html">Section 2.6, “About Secondary Storage”</a>.
+ </div><div class="para">
+ Before you can fill out this screen, you need to prepare the secondary storage by setting up NFS shares and installing the latest CloudStack System VM template. See Adding Secondary Storage :
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>NFS Server.</strong></span> The IP address of the server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Path.</strong></span> The exported path from the server.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Click Launch.
+ </div></li></ol></div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/mimetype
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/mimetype b/docs/tmp/en-US/epub/mimetype
new file mode 100644
index 0000000..57ef03f
--- /dev/null
+++ b/docs/tmp/en-US/epub/mimetype
@@ -0,0 +1 @@
+application/epub+zip
\ No newline at end of file