You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by jz...@apache.org on 2012/11/07 19:01:12 UTC
[40/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/about-virtual-networks.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/about-virtual-networks.html b/docs/tmp/en-US/epub/OEBPS/about-virtual-networks.html
new file mode 100644
index 0000000..1d5ff08
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/about-virtual-networks.html
@@ -0,0 +1,27 @@
+<?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.2. About Virtual Networks</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="about-virtual-networks"><div class="titlepage"><div><div><h1 class="title" id="about-virtual-networks">9.2. About Virtual Networks</h1></div></div></div><div class="para">
+ A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated.
+ </div><div class="section" id="isolated-networks"><div class="titlepage"><div><div><h2 class="title" id="isolated-networks">9.2.1. Isolated Networks</h2></div></div></div><div class="para">
+ An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Resources such as VLAN are allocated and garbage collected dynamically
+ </div></li><li class="listitem"><div class="para">
+ There is one network offering for the entire network
+ </div></li><li class="listitem"><div class="para">
+ The network offering can be upgraded or downgraded but it is for the entire network
+ </div></li></ul></div></div><div class="section" id="shared-networks"><div class="titlepage"><div><div><h2 class="title" id="shared-networks">9.2.2. Shared Networks</h2></div></div></div><div class="para">
+ A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished using techniques such as security groups (supported only in basic zones in CloudStack 3.0.3).
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Shared Networks are created by the administrator
+ </div></li><li class="listitem"><div class="para">
+ Shared Networks can be designated to a certain domain
+ </div></li><li class="listitem"><div class="para">
+ Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator
+ </div></li><li class="listitem"><div class="para">
+ Shared Networks are isolated by security groups
+ </div></li><li class="listitem"><div class="para">
+ Public Network is a shared network that is not shown to the end users
+ </div></li></ul></div></div><div class="section" id="runtime-allocation-virtual-network-resources"><div class="titlepage"><div><div><h2 class="title" id="runtime-allocation-virtual-network-resources">9.2.3. Runtime Allocation of Virtual Network Resources</h2></div></div></div><div class="para">
+ When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources..
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/accept-membership-invite.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/accept-membership-invite.html b/docs/tmp/en-US/epub/OEBPS/accept-membership-invite.html
new file mode 100644
index 0000000..2c91280
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/accept-membership-invite.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. Accepting a Membership Invitation</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="accept-membership-invite"><div class="titlepage"><div><div><h1 class="title" id="accept-membership-invite">6.5. Accepting a Membership Invitation</h1></div></div></div><div class="para">
+ If you have received an invitation to join a CloudStack project, and you want to accept the invitation, follow these steps:
+ </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, click Projects.
+ </div></li><li class="listitem"><div class="para">
+ In Select View, choose Invitations.
+ </div></li><li class="listitem"><div class="para">
+ If you see the invitation listed onscreen, click the Accept button.
+ </div><div class="para">
+ Invitations listed on screen were sent to you using your CloudStack account name.
+ </div></li><li class="listitem"><div class="para">
+ If you received an email invitation, click the Enter Token button, and provide the project ID and unique ID code (token) from the email.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/accessing-vms.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/accessing-vms.html b/docs/tmp/en-US/epub/OEBPS/accessing-vms.html
new file mode 100644
index 0000000..5fd46af
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/accessing-vms.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>10.5. Accessing VMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="accessing-vms"><div class="titlepage"><div><div><h1 class="title" id="accessing-vms">10.5. Accessing VMs</h1></div></div></div><div class="para">
+ Any user can access their own virtual machines. The administrator can access all VMs running in the cloud.
+ </div><div class="para">
+ To access a VM through the CloudStack UI:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as a user or admin.
+ </div></li><li class="listitem"><div class="para">
+ Click Instances, then click the name of a running VM.
+ </div></li><li class="listitem"><div class="para">
+ Click the View Console button <img src="images/icon.png" alt="Accessing VMs" />.
+ </div></li></ol></div><div class="para">
+ To access a VM directly over the network:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding and Firewalling.
+ </div></li><li class="listitem"><div class="para">
+ If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudStack UI and enable ssh on the machine using the commands for the VM’s operating system.
+ </div></li><li class="listitem"><div class="para">
+ If the network has an external firewall device, you will need to create a firewall rule to allow access. See IP Forwarding and Firewalling.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/accounts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/accounts.html b/docs/tmp/en-US/epub/OEBPS/accounts.html
new file mode 100644
index 0000000..39a645e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/accounts.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 3. Accounts</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="accounts"><div class="titlepage"><div><div><h1 class="title">Chapter 3. Accounts</h1></div></div></div><div class="section" id="accounts-users-domains"><div class="titlepage"><div><div><h1 class="title" id="accounts-users-domains">3.1. Accounts, Users, and Domains</h1></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm37521864">Accounts</h5>
+ An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm20145824">Domains</h5>
+ Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller.
+ </div><div class="para">
+ For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm5074824">Users</h5>
+ Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts.
+ </div><div class="para">
+ Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1.
+ </div><div class="para">
+ Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm20904696">Domain Administrators</h5>
+ Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm26592168">Root Administrator</h5>
+ Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains
+ </div><div class="para">
+ The resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/acquire-new-ip-address.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/acquire-new-ip-address.html b/docs/tmp/en-US/epub/OEBPS/acquire-new-ip-address.html
new file mode 100644
index 0000000..494568e
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/acquire-new-ip-address.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>15.11. Acquiring a New IP Address</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="acquire-new-ip-address"><div class="titlepage"><div><div><h1 class="title" id="acquire-new-ip-address">15.11. Acquiring a New IP Address</h1></div></div></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, choose Network.
+ </div></li><li class="listitem"><div class="para">
+ Click the name of the network where you want to work with.
+ </div></li><li class="listitem"><div class="para">
+ Click View IP Addresses.
+ </div></li><li class="listitem"><div class="para">
+ Click Acquire New IP, and click Yes in the confirmation dialog.
+ </div><div class="para">
+ You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/add-members-to-projects.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/add-members-to-projects.html b/docs/tmp/en-US/epub/OEBPS/add-members-to-projects.html
new file mode 100644
index 0000000..bc26554
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/add-members-to-projects.html
@@ -0,0 +1,45 @@
+<?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.4. Adding Members to a Project</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="add-members-to-projects"><div class="titlepage"><div><div><h1 class="title" id="add-members-to-projects">6.4. Adding Members to a Project</h1></div></div></div><div class="para">
+ New members can be added to a project by the project’s administrator, the domain administrator of the domain where the project resides or any parent domain, or the CloudStack root administrator. There are two ways to add members in CloudStack, but only one way is enabled at a time:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If invitations have been enabled, you can send invitations to new members.
+ </div></li><li class="listitem"><div class="para">
+ If invitations are not enabled, you can add members directly through the UI.
+ </div></li></ul></div><div class="section" id="send-projects-membership-invitation"><div class="titlepage"><div><div><h2 class="title" id="send-projects-membership-invitation">6.4.1. Sending Project Membership Invitations</h2></div></div></div><div class="para">
+ Use these steps to add a new member to a project if the invitations feature is enabled in the cloud as described in <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>. If the invitations feature is not turned on, use the procedure in Adding Project Members From the UI.
+ </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, 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 Invitations tab.
+ </div></li><li class="listitem"><div class="para">
+ In Add by, select one of the following:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Account – The invitation will appear in the user’s Invitations tab in the Project View. See Using the Project View.
+ </div></li><li class="listitem"><div class="para">
+ Email – The invitation will be sent to the user’s email address. Each emailed invitation includes a unique code called a token which the recipient will provide back to CloudStack when accepting the invitation. Email invitations will work only if the global parameters related to the SMTP server have been set. See <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ Type the user name or email address of the new member you want to add, and click Invite. Type the CloudStack user name if you chose Account in the previous step. If you chose Email, type the email address. You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address.
+ </div></li><li class="listitem"><div class="para">
+ To view and manage the invitations you have sent, return to this tab. When an invitation is accepted, the new member will appear in the project’s Accounts tab.
+ </div></li></ol></div></div><div class="section" id="add-projects-members-from-ui"><div class="titlepage"><div><div><h2 class="title" id="add-projects-members-from-ui">6.4.2. Adding Project Members From the UI</h2></div></div></div><div class="para">
+ The steps below tell how to add a new member to a project if the invitations feature is not enabled in the cloud. If the invitations feature is enabled cloud,as described in <a class="xref" href="configuring-projects.html#set-up-invitations">Section 6.2.1, “Setting Up Invitations”</a>, use the procedure in <a class="xref" href="add-members-to-projects.html#send-projects-membership-invitation">Section 6.4.1, “Sending Project Membership Invitations”</a>.
+ </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, 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 Accounts tab. The current members of the project are listed.
+ </div></li><li class="listitem"><div class="para">
+ Type the account name of the new member you want to add, and click Add Account. You can add only people who have an account in this cloud and within the same domain as the project.
+ </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/add-password-management-to-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/add-password-management-to-templates.html b/docs/tmp/en-US/epub/OEBPS/add-password-management-to-templates.html
new file mode 100644
index 0000000..9d7964d
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/add-password-management-to-templates.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.13. Adding Password Management to Your Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="add-password-management-to-templates"><div class="titlepage"><div><div><h1 class="title" id="add-password-management-to-templates">12.13. Adding Password Management to Your Templates</h1></div></div></div><div class="para">
+ CloudStack provides an optional password reset feature that allows users to set a temporary admin or root password as well as reset the existing admin or root password from the CloudStack UI.
+ </div><div class="para">
+ To enable the Reset Password feature, you will need to download an additional script to patch your template. When you later upload the template into CloudStack, you can specify whether reset admin/root password feature should be enabled for this template.
+ </div><div class="para">
+ The password management feature works always resets the account password on instance boot. The script does an HTTP call to the virtual router to retrieve the account password that should be set. As long as the virtual router is accessible the guest will have access to the account password that should be used. When the user requests a password reset the management server generates and sends a new password to the virtual router for the account. Thus an instance reboot is necessary to effect any password changes.
+ </div><div class="para">
+ If the script is unable to contact the virtual router during instance boot it will not set the password but boot will continue normally.
+ </div><div class="section" id="linux-installation"><div class="titlepage"><div><div><h2 class="title" id="linux-installation">12.13.1. Linux OS Installation</h2></div></div></div><div class="para">
+ Use the following steps to begin the Linux OS installation:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Download the script file cloud-set-guest-password:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Linux: <a href="http://cloudstack.org/dl/cloud-set-guest-password">http://cloudstack.org/dl/cloud-set-guest-password</a>
+ </div></li><li class="listitem"><div class="para">
+ Windows: <a href="http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download">http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download</a>
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Copy this file to /etc/init.d.
+ </div><div class="para">
+ On some Linux distributions, copy the file to /etc/rc.d/init.d.
+ </div></li><li class="listitem"><div class="para">
+ Run the following command to make the script executable:
+ </div><pre class="programlisting">chmod +x /etc/init.d/cloud-set-guest-password</pre></li><li class="listitem"><div class="para">
+ Depending on the Linux distribution, continue with the appropriate step.
+ </div><div class="para">
+ On Fedora, CentOS/RHEL, and Debian, run:
+ </div><pre class="programlisting">chkconfig --add cloud-set-guest-password</pre></li></ol></div></div><div class="section" id="windows-installation"><div class="titlepage"><div><div><h2 class="title" id="windows-installation">12.13.2. Windows OS Installation</h2></div></div></div><div class="para">
+ Download the installer, CloudInstanceManager.msi, from <a href="http://cloudstack.org/download.html">Download page</a> and run the installer in the newly created Windows VM.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/admin-alerts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/admin-alerts.html b/docs/tmp/en-US/epub/OEBPS/admin-alerts.html
new file mode 100644
index 0000000..5bc573b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/admin-alerts.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>18.3. Administrator Alerts</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="admin-alerts"><div class="titlepage"><div><div><h1 class="title" id="admin-alerts">18.3. Administrator Alerts</h1></div></div></div><div class="para">
+ The system provides alerts and events to help with the management of the cloud. Alerts are notices to an administrator, generally delivered by e-mail, notifying the administrator that an error has occurred in the cloud. Alert behavior is configurable.
+ </div><div class="para">
+ Events track all of the user and administrator actions in the cloud. For example, every guest VM start creates an associated event. Events are stored in the Management Server’s database.
+ </div><div class="para">
+ Emails will be sent to administrators under the following circumstances:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The Management Server cluster runs low on CPU, memory, or storage resources
+ </div></li><li class="listitem"><div class="para">
+ The Management Server loses heartbeat from a Host for more than 3 minutes
+ </div></li><li class="listitem"><div class="para">
+ The Host cluster runs low on CPU, memory, or storage resources
+ </div></li></ul></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/advanced-zone-physical-network-configuration.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/advanced-zone-physical-network-configuration.html b/docs/tmp/en-US/epub/OEBPS/advanced-zone-physical-network-configuration.html
new file mode 100644
index 0000000..e09864b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/advanced-zone-physical-network-configuration.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>15.5. Advanced Zone Physical Network Configuration</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="advanced-zone-physical-network-configuration"><div class="titlepage"><div><div><h1 class="title" id="advanced-zone-physical-network-configuration">15.5. Advanced Zone Physical Network Configuration</h1></div></div></div><div class="para">
+ Within a zone that uses advanced networking, you need to tell the Management Server how the physical network is set up to carry different kinds of traffic in isolation.
+ </div><div class="section" id="configure-guest-traffic-in-advanced-zone"><div class="titlepage"><div><div><h2 class="title" id="configure-guest-traffic-in-advanced-zone">15.5.1. Configure Guest Traffic in an Advanced Zone</h2></div></div></div><div class="para">
+ These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ In the left navigation, choose Infrastructure. On Zones, click View More, then click the zone to which you want to add a network.
+ </div></li><li class="listitem"><div class="para">
+ Click the Network tab.
+ </div></li><li class="listitem"><div class="para">
+ Click Add guest network.
+ </div><div class="para">
+ The Add guest network window is displayed:
+ </div><div class="mediaobject"><img src="./images/add-guest-network.png" alt="networksetupzone.png: Depicts network setup in a single zone" /></div></li><li class="listitem"><div class="para">
+ Provide the following information:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Name</strong></span>. The name of the network. This will be user-visible
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Display Text</strong></span>: The description of the network. This will be user-visible
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Zone</strong></span>: The zone in which you are configuring the guest network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Network offering</strong></span>: If the administrator has configured multiple network offerings, select the one you want to use for this network
+ </div></li><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></ul></div></li><li class="listitem"><div class="para">
+ Click OK.
+ </div></li></ol></div></div><div class="section" id="configure-public-traffic-in-an-advanced-zone"><div class="titlepage"><div><div><h2 class="title" id="configure-public-traffic-in-an-advanced-zone">15.5.2. Configure Public Traffic in an Advanced Zone</h2></div></div></div><div class="para">
+ In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/alerts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/alerts.html b/docs/tmp/en-US/epub/OEBPS/alerts.html
new file mode 100644
index 0000000..9a90447
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/alerts.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>Appendix C. Alerts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="appendix" id="alerts"><div class="titlepage"><div><div><h1 class="title">Alerts</h1></div></div></div><div class="para">
+ The following is the list of alert type numbers. The current alerts can be found by calling listAlerts.
+ </div><pre class="programlisting">MEMORY = 0</pre><pre class="programlisting">CPU = 1</pre><pre class="programlisting">STORAGE =2</pre><pre class="programlisting">STORAGE_ALLOCATED = 3</pre><pre class="programlisting">PUBLIC_IP = 4</pre><pre class="programlisting">PRIVATE_IP = 5</pre><pre class="programlisting">HOST = 6</pre><pre class="programlisting">USERVM = 7</pre><pre class="programlisting">DOMAIN_ROUTER = 8</pre><pre class="programlisting">CONSOLE_PROXY = 9</pre><pre class="programlisting">ROUTING = 10// lost connection to default route (to the gateway)</pre><pre class="programlisting">STORAGE_MISC = 11 // lost connection to default route (to the gateway)</pre><pre class="programlisting">USAGE_SERVER = 12 // lost connection to default route (to the gateway)</pre><pre class="programlisting">MANAGMENT_NODE = 13 // lost connection to default route (to the gateway)</pre><pre class="programlisting">DOMAIN_ROUTER_MIGRATE = 14</pre><pre class="programlisting">CONSOLE_PROXY_MIGRATE =
15</pre><pre class="programlisting">USERVM_MIGRATE = 16</pre><pre class="programlisting">VLAN = 17</pre><pre class="programlisting">SSVM = 18</pre><pre class="programlisting">USAGE_SERVER_RESULT = 19</pre><pre class="programlisting">STORAGE_DELETE = 20;</pre><pre class="programlisting">UPDATE_RESOURCE_COUNT = 21; //Generated when we fail to update the resource count</pre><pre class="programlisting">USAGE_SANITY_RESULT = 22;</pre><pre class="programlisting">DIRECT_ATTACHED_PUBLIC_IP = 23;</pre><pre class="programlisting">LOCAL_STORAGE = 24;</pre><pre class="programlisting">RESOURCE_LIMIT_EXCEEDED = 25; //Generated when the resource limit exceeds the limit. Currently used for recurring snapshots only</pre></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/allocators.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/allocators.html b/docs/tmp/en-US/epub/OEBPS/allocators.html
new file mode 100644
index 0000000..fcb308f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/allocators.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>20.2. Allocators</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="allocators"><div class="titlepage"><div><div><h1 class="title" id="allocators">20.2. Allocators</h1></div></div></div><div class="para">
+ CloudStack enables administrators to write custom allocators that will choose the Host to place a new guest and the storage host from which to allocate guest virtual disk images.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/api-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/api-overview.html b/docs/tmp/en-US/epub/OEBPS/api-overview.html
new file mode 100644
index 0000000..eb4edeb
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/api-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>Chapter 20. CloudStack API</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="api-overview"><div class="titlepage"><div><div><h1 class="title">Chapter 20. CloudStack API</h1></div></div></div><div class="para">
+ The CloudStack API is a low level API that has been used to implement the CloudStack web UIs. It is also a good basis for implementing other popular APIs such as EC2/S3 and emerging DMTF standards.
+ </div><div class="para">
+ Many CloudStack API calls are asynchronous. These will return a Job ID immediately when called. This Job ID can be used to query the status of the job later. Also, status calls on impacted resources will provide some indication of their state.
+ </div><div class="para">
+ The API has a REST-like query basis and returns results in XML or JSON.
+ </div><div class="para">
+ See <a href="http://docs.cloudstack.org/CloudStack_Documentation/Developer's_Guide%3A_CloudStack">the Developer’s Guide</a> and <a href="http://docs.cloudstack.org/CloudStack_Documentation/API_Reference%3A_CloudStack">the API Reference</a>.
+ </div><div class="section" id="provisioning-auth-api"><div class="titlepage"><div><div><h1 class="title" id="provisioning-auth-api">20.1. Provisioning and Authentication API</h1></div></div></div><div class="para">
+ CloudStack expects that a customer will have their own user provisioning infrastructure. It provides APIs to integrate with these existing systems where the systems call out to CloudStack to add/remove users..
+ </div><div class="para">
+ CloudStack supports pluggable authenticators. By default, CloudStack assumes it is provisioned with the user’s password, and as a result authentication is done locally. However, external authentication is possible as well. For example, see Using an LDAP Server for User Authentication.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/appe-cloudstack-Revision_History.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/appe-cloudstack-Revision_History.html b/docs/tmp/en-US/epub/OEBPS/appe-cloudstack-Revision_History.html
new file mode 100644
index 0000000..d7d2d96
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/appe-cloudstack-Revision_History.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>Appendix D. Revision History</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="appendix" id="appe-cloudstack-Revision_History"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 0-0</td><td align="left">Tue May 29 2012</td><td align="left"><span class="author"><span class="firstname">Jessica</span> <span class="surname">Tomechak</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Initial creation of book by publican</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/basic-zone-physical-network-configuration.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/basic-zone-physical-network-configuration.html b/docs/tmp/en-US/epub/OEBPS/basic-zone-physical-network-configuration.html
new file mode 100644
index 0000000..af10395
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/basic-zone-physical-network-configuration.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.4. Basic Zone Physical Network Configuration</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="basic-zone-physical-network-configuration"><div class="titlepage"><div><div><h1 class="title" id="basic-zone-physical-network-configuration">15.4. Basic Zone Physical Network Configuration</h1></div></div></div><div class="para">
+ In a basic network, configuring the physical network is fairly straightforward. You only need to configure one guest network to carry traffic that is generated by guest VMs. When you first add a zone to CloudPlatform, you set up the guest network through the Add Zone screens.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/best-practices-templates.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/best-practices-templates.html b/docs/tmp/en-US/epub/OEBPS/best-practices-templates.html
new file mode 100644
index 0000000..4c9b31a
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/best-practices-templates.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.3. Best Practices for Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="best-practices-templates"><div class="titlepage"><div><div><h1 class="title" id="best-practices-templates">12.3. Best Practices for Templates</h1></div></div></div><div class="para">
+ If you plan to use large templates (100 GB or larger), be sure you have a 10-gigabit network to support the large templates. A slower network can lead to timeouts and other errors when large templates are used.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/best-practices-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/best-practices-vm.html b/docs/tmp/en-US/epub/OEBPS/best-practices-vm.html
new file mode 100644
index 0000000..aec5f4b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/best-practices-vm.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>10.2. Best Practices for Virtual Machines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="section" id="best-practices-vm"><div class="titlepage"><div><div><h1 class="title" id="best-practices-vm">10.2. Best Practices for Virtual Machines</h1></div></div></div><div class="para">
+ The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) * (per-host-limit). Once a cluster reaches this number of
VMs, use the CloudStack UI to disable allocation of more VMs to the cluster.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/change-database-config.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/change-database-config.html b/docs/tmp/en-US/epub/OEBPS/change-database-config.html
new file mode 100644
index 0000000..a361c1f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/change-database-config.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>18.2. Changing the Database Configuration</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="change-database-config"><div class="titlepage"><div><div><h1 class="title" id="change-database-config">18.2. Changing the Database Configuration</h1></div></div></div><div class="para">
+ The CloudStack Management Server stores database configuration information (e.g., hostname, port, credentials) in the file /etc/cloud/management/db.properties. To effect a change, edit this file on each Management Server, then restart the Management Server.
+ </div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/change-host-password.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/change-host-password.html b/docs/tmp/en-US/epub/OEBPS/change-host-password.html
new file mode 100644
index 0000000..bcbd77c
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/change-host-password.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.7. Changing Host Password</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="change-host-password"><div class="titlepage"><div><div><h1 class="title" id="change-host-password">11.7. Changing Host Password</h1></div></div></div><div class="para">
+ The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password.
+ </div><div class="para">
+ To change a Node's password:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Identify all hosts in the cluster.
+ </div></li><li class="listitem"><div class="para">
+ Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match.
+ </div></li><li class="listitem"><div class="para">
+ Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname "h" (or vSphere cluster) that you are changing the password for, execute:
+ </div><pre class="programlisting">mysql> select id from cloud.host where name like '%h%';</pre></li><li class="listitem"><div class="para">
+ This should return a single ID. Record the set of such IDs for these hosts.
+ </div></li><li class="listitem"><div class="para">
+ Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to "password".
+ </div><pre class="programlisting">mysql> update cloud.host set password='password' where id=5 or id=10 or id=12;</pre></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/changing-service-offering-for-vm.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/changing-service-offering-for-vm.html b/docs/tmp/en-US/epub/OEBPS/changing-service-offering-for-vm.html
new file mode 100644
index 0000000..5a25c5b
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/changing-service-offering-for-vm.html
@@ -0,0 +1,23 @@
+<?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.8. Changing the Service Offering for a VM</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="changing-service-offering-for-vm"><div class="titlepage"><div><div><h1 class="title" id="changing-service-offering-for-vm">10.8. Changing the Service Offering for a VM</h1></div></div></div><div class="para">
+ To upgrade or downgrade the level of compute resources available to a virtual machine, you can change the VM's compute offering.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as a user or admin.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Choose the VM that you want to work with.
+ </div></li><li class="listitem"><div class="para">
+ Click the Stop button to stop the VM
+ <span class="inlinemediaobject"><img src="./images/stop-instance-icon.png" alt="StopButton.png: button to stop a VM" /></span>
+
+ </div></li><li class="listitem"><div class="para">
+ Click the Change Service button
+ <span class="inlinemediaobject"><img src="./images/change-service-icon.png" alt="ChangeServiceButton.png: button to change the service of a VM" /></span>
+ . The Change service dialog box is displayed.
+ </div></li><li class="listitem"><div class="para">
+ Select the offering you want.
+ </div></li><li class="listitem"><div class="para">
+ Click OK.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/changing-vm-name-os-group.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/changing-vm-name-os-group.html b/docs/tmp/en-US/epub/OEBPS/changing-vm-name-os-group.html
new file mode 100644
index 0000000..c187210
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/changing-vm-name-os-group.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.7. Changing the VM Name, OS, or Group</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="changing-vm-name-os-group"><div class="titlepage"><div><div><h1 class="title" id="changing-vm-name-os-group">10.7. Changing the VM Name, OS, or Group</h1></div></div></div><div class="para">
+ After a VM is created, you can modify the display name, operating system, and the group it belongs to.
+ </div><div class="para">
+ To access a VM through the CloudStack UI:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Log in to the CloudStack UI as a user or admin.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation, click Instances.
+ </div></li><li class="listitem"><div class="para">
+ Select the VM that you want to modify.
+ </div></li><li class="listitem"><div class="para">
+ Click the Stop button to stop the VM
+ <span class="inlinemediaobject"><img src="./images/stop-instance-icon.png" alt="StopButton.png: button to stop a VM" /></span>
+
+ </div></li><li class="listitem"><div class="para">
+ Click Edit
+ <span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="StopButton.png: button to edit the properties of a VM" /></span>
+ .
+ </div></li><li class="listitem"><div class="para">
+ Make the desired changes to the following:
+ </div></li><li class="listitem"><div class="para">
+ Display name: Enter a new display name if you want to change the name of the VM.
+ </div></li><li class="listitem"><div class="para">
+ OS Type: Select the desired operating system.
+ </div></li><li class="listitem"><div class="para">
+ Group: Enter the group name for the VM.
+ </div></li><li class="listitem"><div class="para">
+ Click Apply.
+ </div></li></ol></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/cloud-infrastructure-concepts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/cloud-infrastructure-concepts.html b/docs/tmp/en-US/epub/OEBPS/cloud-infrastructure-concepts.html
new file mode 100644
index 0000000..41972e1
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/cloud-infrastructure-concepts.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Cloud Infrastructure Concepts</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="cloud-infrastructure-concepts"><div class="titlepage"><div><div><h1 class="title">Chapter 2. Cloud Infrastructure Concepts</h1></div></div></div><div class="section" id="about-zones"><div class="titlepage"><div><div><h1 class="title" id="about-zones">2.1. About Zones</h1></div></div></div><div class="para">
+ A zone is the largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
+ </div><div class="para">
+ A zone consists of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers.
+ </div></li><li class="listitem"><div class="para">
+ Secondary storage, which is shared by all the pods in the zone.
+ </div></li></ul></div><div class="mediaobject"><img src="./images/zone-overview.png" width="444" alt="zone-overview.png: Nested structure of a simple zone" /></div><div class="para">
+ Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones.
+ </div><div class="para">
+ Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone.
+ </div><div class="para">
+ Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels.
+ </div><div class="para">
+ For each zone, the administrator must decide the following.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ How many pods to place in a zone.
+ </div></li><li class="listitem"><div class="para">
+ How many clusters to place in each pod.
+ </div></li><li class="listitem"><div class="para">
+ How many hosts to place in each cluster.
+ </div></li><li class="listitem"><div class="para">
+ How many primary storage servers to place in each cluster and total capacity for the storage servers.
+ </div></li><li class="listitem"><div class="para">
+ How much secondary storage to deploy in a zone.
+ </div></li></ul></div><div class="para">
+ When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage.
+ </div></div></div></body></html>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/cluster-add.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/cluster-add.html b/docs/tmp/en-US/epub/OEBPS/cluster-add.html
new file mode 100644
index 0000000..8a914d8
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/cluster-add.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>7.4. Adding a Cluster</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="cluster-add"><div class="titlepage"><div><div><h1 class="title" id="cluster-add">7.4. Adding a Cluster</h1></div></div></div><div class="para">
+ You need to tell CloudStack about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster.
+ </div><div class="section" id="add-clusters-kvm-xenserver"><div class="titlepage"><div><div><h2 class="title" id="add-clusters-kvm-xenserver">7.4.1. Add Cluster: KVM or XenServer</h2></div></div></div><div class="para">
+ These steps assume you have already installed the hypervisor on the hosts and logged in to the CloudStack UI.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster.
+ </div></li><li class="listitem"><div class="para">
+ Click the Compute tab.
+ </div></li><li class="listitem"><div class="para">
+ In the Clusters node of the diagram, click View All.
+ </div></li><li class="listitem"><div class="para">
+ Click Add Cluster.
+ </div></li><li class="listitem"><div class="para">
+ Choose the hypervisor type for this cluster.
+ </div></li><li class="listitem"><div class="para">
+ Choose the pod in which you want to create the cluster.
+ </div></li><li class="listitem"><div class="para">
+ Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack.
+ </div></li><li class="listitem"><div class="para">
+ Click OK.
+ </div></li></ol></div></div><div class="section" id="add-clusters-vsphere"><div class="titlepage"><div><div><h2 class="title" id="add-clusters-vsphere">7.4.2. Add Cluster: vSphere</h2></div></div></div><div class="para">
+ Host management for vSphere is done through a combination of vCenter and the CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack cluster, but the cluster may consist of a single host. As an administrator you must decide if you would like to use clusters of one host or of multiple hosts. Clusters of multiple hosts allow for features like live migration. Clusters also require shared storage such as NFS or iSCSI.
+ </div><div class="para">
+ For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. Follow these requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Do not put more than 8 hosts in a vSphere cluster
+ </div></li><li class="listitem"><div class="para">
+ Make sure the hypervisor hosts do not have any VMs already running before you add them to CloudStack.
+ </div></li></ul></div><div class="para">
+ To add a vSphere cluster to CloudStack:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create the cluster of hosts in vCenter. Follow the vCenter instructions to do this. You will create a cluster that looks something like this in vCenter.
+ </div><div class="mediaobject"><img src="./images/vsphere-client.png" width="444" alt="vsphereclient.png: vSphere client" /></div></li><li class="listitem"><div class="para">
+ Log in to the UI.
+ </div></li><li class="listitem"><div class="para">
+ In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster.
+ </div></li><li class="listitem"><div class="para">
+ Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster.
+ </div></li><li class="listitem"><div class="para">
+ Click View Clusters.
+ </div></li><li class="listitem"><div class="para">
+ Click Add Cluster.
+ </div></li><li class="listitem"><div class="para">
+ In Hypervisor, choose VMware.
+ </div></li><li class="listitem"><div class="para">
+ Provide the following information in the dialog. The fields below make reference to values from vCenter.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Cluster Name. Enter the name of the cluster you created in vCenter. For example, "cloud.cluster.2.2.1"
+ </div></li><li class="listitem"><div class="para">
+ vCenter Host. Enter the hostname or IP address of the vCenter server.
+ </div></li><li class="listitem"><div class="para">
+ vCenter Username. Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges.
+ </div></li><li class="listitem"><div class="para">
+ vCenter Password. Enter the password for the user named above
+ </div></li><li class="listitem"><div class="para">
+ vCenter Datacenter. Enter the vCenter datacenter that the cluster is in. For example, "cloud.dc.VM".
+ </div></li><li class="listitem"><div class="mediaobject"><img src="./images/add-cluster.png" alt="addcluster.png: add cluster" /></div><div class="para">
+ There might be a slight delay while the cluster is provisioned. It will automatically display in the UI
+ </div></li></ul></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/concepts.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/concepts.html b/docs/tmp/en-US/epub/OEBPS/concepts.html
new file mode 100644
index 0000000..d75afc5
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/concepts.html
@@ -0,0 +1,11 @@
+<?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 1. Concepts</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="concepts"><div class="titlepage"><div><div><h1 class="title">Chapter 1. Concepts</h1></div></div></div><div class="section" id="whatis"><div class="titlepage"><div><div><h1 class="title" id="whatis">1.1. What Is CloudStack?</h1></div></div></div><div class="para">
+ CloudStack is an open source software platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudStack manages the network, storage, and compute nodes that make up a cloud infrastructure. Use CloudStack to deploy, manage, and configure cloud computing environments.
+ </div><div class="para">
+ Typical users are service providers and enterprises. With CloudStack, you can:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Set up an on-demand, elastic cloud computing service. Service providers can sell self service virtual machine instances, storage volumes, and networking configurations over the Internet.
+ </div></li><li class="listitem"><div class="para">
+ Set up an on-premise private cloud for use by employees. Rather than managing virtual machines in the same way as physical machines, with CloudStack an enterprise can offer self-service virtual machines to users without involving IT departments.
+ </div></li></ul></div><div class="mediaobject"><img src="./images/1000-foot-view.png" width="444" alt="1000-foot-view.png: Overview of CloudStack" /></div></div></div></body></html>