incubator-cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject [46/52] [abbrv] [partial] CLOUDSTACK-444 Fix from Radhika PC against docs, adds network setup in the install guide.
Date Wed, 07 Nov 2012 18:01:12 GMT
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/troubleshooting-working-with-server-logs.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/troubleshooting-working-with-server-logs.html b/docs/tmp/en-US/epub/OEBPS/troubleshooting-working-with-server-logs.html
new file mode 100644
index 0000000..3f08b63
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/troubleshooting-working-with-server-logs.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2. Working with Server Logs</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="troubleshooting-working-with-server-logs"><div class="titlepage"><div><div><h1 class="title" id="troubleshooting-working-with-server-logs">22.2. Working with Server Logs</h1></div></div></div><div class="para">
+		The CloudStack Management Server logs all web site, middle tier, and database activities for diagnostics purposes in /var/log/cloud/management/. The CloudStack logs a variety of error messages. We recommend this command to find the problematic output in the Management Server log:.
+	</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text.
+		</div></div></div><pre class="programlisting">
+        grep -i -E 'exception|unable|fail|invalid|leak|warn|error' /var/log/cloud/management/management-server.log
+</pre><div class="para">
+		The CloudStack processes requests with a Job ID. If you find an error in the logs and you are interested in debugging the issue you can grep for this job ID in the management server log. For example, suppose that you find the following ERROR message:
+	</div><pre class="programlisting">
+        2010-10-04 13:49:32,595 ERROR [cloud.vm.UserVmManagerImpl] (Job-Executor-11:job-1076) Unable to find any host for [User|i-8-42-VM-untagged]
+</pre><div class="para">
+		Note that the job ID is 1076. You can track back the events relating to job 1076 with the following grep:
+	</div><pre class="programlisting">
+        grep "job-1076)" management-server.log
+</pre><div class="para">
+		The CloudStack Agent Server logs its activities in /var/log/cloud/agent/.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/troubleshooting.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/troubleshooting.html b/docs/tmp/en-US/epub/OEBPS/troubleshooting.html
new file mode 100644
index 0000000..c908eae
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/troubleshooting.html
@@ -0,0 +1,47 @@
+<?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 22. Troubleshooting</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="troubleshooting"><div class="titlepage"><div><div><h1 class="title">Chapter 22. Troubleshooting</h1></div></div></div><div class="section" id="events"><div class="titlepage"><div><div><h1 class="title" id="events">22.1. Events</h1></div></div></div><div class="section" id="events-log"><div class="titlepage"><div><div><h2 class="title" id="events-log">22.1.1. Event Logs</h2></div></div></div><div class="para">
+		There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more information on the status of a pending job or can be used to identify a job that is hanging or has not started. The following sections provide more information on these events..
+	</div></div><div class="section" id="standard-events"><div class="titlepage"><div><div><h2 class="title" id="standard-events">22.1.2. Standard Events</h2></div></div></div><div class="para">
+		The events log records three types of standard events.
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				INFO. This event is generated when an operation has been successfully performed.
+			</div></li><li class="listitem"><div class="para">
+				WARN. This event is generated in the following circumstances.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						When a network is disconnected while monitoring a template download.
+					</div></li><li class="listitem"><div class="para">
+						When a template download is abandoned.
+					</div></li><li class="listitem"><div class="para">
+						When an issue on the storage server causes the volumes to fail over to the mirror storage server.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				ERROR. This event is generated when an operation has not been successfully performed
+			</div></li></ul></div></div><div class="section" id="long-running-job-events"><div class="titlepage"><div><div><h2 class="title" id="long-running-job-events">22.1.3. Long Running Job Events</h2></div></div></div><div class="para">
+		The events log records three types of standard events.
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				INFO. This event is generated when an operation has been successfully performed.
+			</div></li><li class="listitem"><div class="para">
+				WARN. This event is generated in the following circumstances.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						When a network is disconnected while monitoring a template download.
+					</div></li><li class="listitem"><div class="para">
+						When a template download is abandoned.
+					</div></li><li class="listitem"><div class="para">
+						When an issue on the storage server causes the volumes to fail over to the mirror storage server.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				ERROR. This event is generated when an operation has not been successfully performed
+			</div></li></ul></div></div><div class="section" id="event-log-queries"><div class="titlepage"><div><div><h2 class="title" id="event-log-queries">22.1.4. Event Log Queries</h2></div></div></div><div class="para">
+		Database logs can be queried from the user interface. The list of events captured by the system includes:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Virtual machine creation, deletion, and on-going management operations
+			</div></li><li class="listitem"><div class="para">
+				Virtual router creation, deletion, and on-going management operations
+			</div></li><li class="listitem"><div class="para">
+				Template creation and deletion
+			</div></li><li class="listitem"><div class="para">
+				Network/load balancer rules creation and deletion
+			</div></li><li class="listitem"><div class="para">
+				Storage volume creation and deletion
+			</div></li><li class="listitem"><div class="para">
+				User login and logout
+			</div></li></ul></div></div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/tuning.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/tuning.html b/docs/tmp/en-US/epub/OEBPS/tuning.html
new file mode 100644
index 0000000..a33821d
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/tuning.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 21. Tuning</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="tuning"><div class="titlepage"><div><div><h1 class="title">Chapter 21. Tuning</h1></div></div></div><div class="para">
+		This section provides tips on how to improve the performance of your cloud.
+	</div><div class="section" id="performance-monitoring"><div class="titlepage"><div><div><h1 class="title" id="performance-monitoring">21.1. Performance Monitoring</h1></div></div></div><div class="para">
+		Host and guest performance monitoring is available to end users and administrators. This allows the user to monitor their utilization of resources and determine when it is appropriate to choose a more powerful service offering or larger disk.
+	</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/ui.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/ui.html b/docs/tmp/en-US/epub/OEBPS/ui.html
new file mode 100644
index 0000000..b6bcda1
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/ui.html
@@ -0,0 +1,62 @@
+<?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 5. User Interface</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="ui"><div class="titlepage"><div><div><h1 class="title">Chapter 5. User Interface</h1></div></div></div><div class="section" id="log-in"><div class="titlepage"><div><div><h1 class="title" id="log-in">5.1. Log In to the UI</h1></div></div></div><div class="para">
+		CloudStack provides a web-based UI that can be used by both administrators and end users. The appropriate version of the UI is displayed depending on the credentials used to log in. The UI is available in popular browsers including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own management server IP address)
+	</div><pre class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre><div class="para">
+		On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you specify the following to proceed to your Dashboard:
+	</div><div class="formalpara"><h5 class="formalpara" id="idm29063216">Username</h5>
+			The user ID of your account. The default username is admin.
+		</div><div class="formalpara"><h5 class="formalpara" id="idm33744264">Password</h5>
+			The password associated with the user ID. The password for the default username is password.
+		</div><div class="formalpara"><h5 class="formalpara" id="idm32433440">Domain</h5>
+			If you are a root user, leave this field blank.
+		</div><div class="para">
+		If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain.
+	</div><div class="para">
+		For example, suppose multiple levels are created under the root domain, such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain field, whereas the users in the Comp1/sales domain should enter Comp1/sales.
+	</div><div class="para">
+		For more guidance about the choices that appear when you log in to this UI, see Logging In as the Root Administrator.
+	</div><div class="section" id="end-user-ui-overview"><div class="titlepage"><div><div><h2 class="title" id="end-user-ui-overview">5.1.1. End User's UI Overview</h2></div></div></div><div class="para">
+		The CloudStack UI helps users of cloud infrastructure to view and use their cloud resources, including virtual machines, templates and ISOs, data volumes and snapshots, guest networks, and IP addresses. If the user is a member or administrator of one or more CloudStack projects, the UI can provide a project-oriented view.
+	</div></div><div class="section" id="root-admin-ui-overview"><div class="titlepage"><div><div><h2 class="title" id="root-admin-ui-overview">5.1.2. Root Administrator's UI Overview</h2></div></div></div><div class="para">
+		The CloudStack UI helps the CloudStack administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings. The first time you start the UI after a fresh Management Server installation, you can choose to follow a guided tour to provision your cloud infrastructure. On subsequent logins, the dashboard of the logged-in user appears. The various links in this screen and the navigation bar on the left provide access to a variety of administrative functions. The root administrator can also use the UI to perform all the same tasks that are present in the end-user’s UI.
+	</div></div><div class="section" id="log-in-root-admin"><div class="titlepage"><div><div><h2 class="title" id="log-in-root-admin">5.1.3. Logging In as the Root Administrator</h2></div></div></div><div class="para">
+		After the Management Server software is installed and running, you can run the CloudStack user interface. This UI is there to help you provision, view, and manage your cloud infrastructure.
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:
+			</div><pre class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre><div class="para">
+				On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you can enter a user ID and password and proceed to your Dashboard.
+			</div></li><li class="listitem"><div class="para">
+				If you see the first-time splash screen, choose one of the following.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Continue with basic setup.</strong></span> Choose this if you're just trying CloudStack, and you want a guided walkthrough of the simplest possible configuration so that you can get started right away. We'll help you set up a cloud with the following features: a single machine that runs CloudStack software and uses NFS to provide storage; a single machine running VMs under the XenServer or KVM hypervisor; and a shared public network.
+					</div><div class="para">
+						The prompts in this guided tour should give you all the information you need, but if you want just a bit more detail, you can follow along in the Trial Installation Guide.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>I have used CloudStack before.</strong></span> Choose this if you have already gone through a design phase and planned a more sophisticated deployment, or you are ready to start scaling up a trial cloud that you set up earlier with the basic setup screens. In the Administrator UI, you can start using the more powerful features of CloudPlatform, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere.
+					</div><div class="para">
+						The root administrator Dashboard appears.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				You should set a new root administrator password. If you chose basic setup, you’ll be prompted to create a new password right away. If you chose experienced user, use the steps in <a class="xref" href="ui.html#changing-root-password">Section 5.1.4, “Changing the Root Password”</a>.
+			</div></li></ol></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+			You are logging in as the root administrator. This account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. Please change the default password to a new, unique password.
+		</div></div></div></div><div class="section" id="changing-root-password"><div class="titlepage"><div><div><h2 class="title" id="changing-root-password">5.1.4. Changing the Root Password</h2></div></div></div><div class="para">
+		During installation and ongoing cloud administration, you will need to log in to the UI as the root administrator. The root administrator account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. When first installing CloudStack, be sure to change the default password to a new, unique value.
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:
+			</div><pre class="programlisting">http://&lt;management-server-ip-address&gt;:8080/client</pre></li><li class="listitem"><div class="para">
+				Log in to the UI using the current root user ID and password. The default is admin, password.
+			</div></li><li class="listitem"><div class="para">
+				Click Accounts.
+			</div></li><li class="listitem"><div class="para">
+				Click the admin account name.
+			</div></li><li class="listitem"><div class="para">
+				Click View Users.
+			</div></li><li class="listitem"><div class="para">
+				Click the admin user name.
+			</div></li><li class="listitem"><div class="para">
+				Click the Change Password button. 
+				<span class="inlinemediaobject"><img src="./images/change-password.png" alt="change-password.png: button to change a user's password" /></span>
+			</div></li><li class="listitem"><div class="para">
+				Type the new password, and click OK.
+			</div></li></ol></div></div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/upload-template.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/upload-template.html b/docs/tmp/en-US/epub/OEBPS/upload-template.html
new file mode 100644
index 0000000..71deb9f
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/upload-template.html
@@ -0,0 +1,41 @@
+<?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.8. Uploading 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="upload-template"><div class="titlepage"><div><div><h1 class="title" id="upload-template">12.8. Uploading Templates</h1></div></div></div><div class="warning"><div class="admonition_header"><h2>vSphere Templates and ISOs</h2></div><div class="admonition"><div class="para">
+			If you are uploading a template that was created using vSphere Client, be sure the OVA file does not contain an ISO. If it does, the deployment of VMs from the template will fail.
+		</div></div></div><div class="para">
+		Templates are uploaded based on a URL. HTTP is the supported access protocol. Templates are frequently large files. You can optionally gzip them to decrease upload times.
+	</div><div class="para">
+		To upload a template:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				In the left navigation bar, click Templates.
+			</div></li><li class="listitem"><div class="para">
+				Click Create Template.
+			</div></li><li class="listitem"><div class="para">
+				Provide the following:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Name and Display Text</strong></span>. These will be shown in the UI, so choose something descriptive.
+					</div></li><li class="listitem"><div class="para">
+						URL. The Management Server will download the file from the specified URL, such as http://my.web.server/filename.vhd.gz.
+					</div></li><li class="listitem"><div class="para">
+						Zone. Choose the zone where you want the template to be available, or All Zones to make it available throughout CloudStack.
+					</div></li><li class="listitem"><div class="para">
+						OS Type: This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following:
+					</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+								If the operating system of the stopped VM is listed, choose it.
+							</div></li><li class="listitem"><div class="para">
+								If the OS type of the stopped VM is not listed, choose Other.
+							</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+									You should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other.
+								</div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Hypervisor</strong></span>
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Format</strong></span>. The format of the template upload file, such as VHD or OVA.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Password Enabled</strong></span>. Choose Yes if your template has the CloudStack password change script installed. See Adding Password Management to Your Templates
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Extractable</strong></span>. Choose Yes if the template is available for extraction. If this option is selected, end users can download a full image of a template.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Public</strong></span>. Choose Yes to make this template accessible to all users of this CloudStack installation. The template will appear in the Community Templates list. See <a class="xref" href="private-public-template.html">Section 12.5, “Private and Public Templates”</a>
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Featured</strong></span>. Choose Yes if you would like this template to be more prominent for users to select. The template will appear in the Featured Templates list. Only an administrator can make a template Featured.
+					</div></li></ul></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/use-project-view.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/use-project-view.html b/docs/tmp/en-US/epub/OEBPS/use-project-view.html
new file mode 100644
index 0000000..0627fe3
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/use-project-view.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>6.7. Using the Project View</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="use-project-view"><div class="titlepage"><div><div><h1 class="title" id="use-project-view">6.7. Using the Project View</h1></div></div></div><div class="para">
+		If you are a member of a project, you can use CloudStack’s project view to see project members, resources consumed, and more. The project view shows only information related to one project. It is a useful way to filter out other information so you can concentrate on a project status and resources.
+	</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">
+				Click Project View.
+			</div></li><li class="listitem"><div class="para">
+				The project dashboard appears, showing the project’s VMs, volumes, users, events, network settings, and more. From the dashboard, you can:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						Click the Accounts tab to view and manage project members. If you are the project administrator, you can add new members, remove members, or change the role of a member from user to admin. Only one member at a time can have the admin role, so if you set another user’s role to admin, your role will change to regular user.
+					</div></li><li class="listitem"><div class="para">
+						(If invitations are enabled) Click the Invitations tab to view and manage invitations that have been sent to new project members but not yet accepted. Pending invitations will remain in this list until the new member accepts, the invitation timeout is reached, or you cancel the invitation.
+					</div></li></ul></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/user-data-and-meta-data.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/user-data-and-meta-data.html b/docs/tmp/en-US/epub/OEBPS/user-data-and-meta-data.html
new file mode 100644
index 0000000..b5a6abe
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/user-data-and-meta-data.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>20.3. User Data and Meta Data</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="user-data-and-meta-data"><div class="titlepage"><div><div><h1 class="title" id="user-data-and-meta-data">20.3. User Data and Meta Data</h1></div></div></div><div class="para">
+		CloudStack provides API access to attach user data to a deployed VM. Deployed VMs also have access to instance metadata via the virtual router.
+	</div><div class="para">
+		User data can be accessed once the IP address of the virtual router is known. Once the IP address is known, use the following steps to access the user data:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Run the following command to find the virtual router.
+			</div><pre class="programlisting"># cat /var/lib/dhclient/dhclient-eth0.leases | grep dhcp-server-identifier | tail -1</pre></li><li class="listitem"><div class="para">
+				Access user data by running the following command using the result of the above command
+			</div><pre class="programlisting"># curl http://10.1.1.1/latest/user-data</pre></li></ol></div><div class="para">
+		Meta Data can be accessed similarly, using a URL of the form http://10.1.1.1/latest/meta-data/{metadata type}. (For backwards compatibility, the previous URL http://10.1.1.1/latest/{metadata type} is also supported.) For metadata type, use one of the following:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				service-offering. A description of the VMs service offering
+			</div></li><li class="listitem"><div class="para">
+				availability-zone. The Zone name
+			</div></li><li class="listitem"><div class="para">
+				local-ipv4. The guest IP of the VM
+			</div></li><li class="listitem"><div class="para">
+				local-hostname. The hostname of the VM
+			</div></li><li class="listitem"><div class="para">
+				public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)
+			</div></li><li class="listitem"><div class="para">
+				public-hostname. This is the same as public-ipv4
+			</div></li><li class="listitem"><div class="para">
+				instance-id. The instance name of the VM
+			</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/user-services-overview.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/user-services-overview.html b/docs/tmp/en-US/epub/OEBPS/user-services-overview.html
new file mode 100644
index 0000000..0338a68
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/user-services-overview.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>Chapter 4. User Services Overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="" /></head><body><div class="chapter" id="user-services-overview"><div class="titlepage"><div><div><h1 class="title">Chapter 4. User Services Overview</h1></div></div></div><div class="para">
+		In addition to the physical and logical infrastructure of your cloud, and the CloudStack software and servers, you also need a layer of user services so that people can actually make use of the cloud. This means not just a user UI, but a set of options and resources that users can choose from, such as templates for creating virtual machines, disk storage, and more. If you are running a commercial service, you will be keeping track of what services and resources users are consuming and charging them for that usage. Even if you do not charge anything for people to use your cloud – say, if the users are strictly internal to your organization, or just friends who are sharing your cloud – you can still keep track of what services they use and how much of them.
+	</div><div class="section" id="offerings-and-templates"><div class="titlepage"><div><div><h1 class="title" id="offerings-and-templates">4.1. Service Offerings, Disk Offerings, Network Offerings, and Templates</h1></div></div></div><div class="para">
+			A user creating a new instance can make a variety of choices about its characteristics and capabilities. CloudStack provides several ways to present users with choices when creating a new instance:
+		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Service Offerings, defined by the CloudStack administrator, provide a choice of CPU speed, number of CPUs, RAM size, tags on the root disk, and other choices. See Creating a New Compute Offering.
+				</div></li><li class="listitem"><div class="para">
+					Disk Offerings, defined by the CloudStack administrator, provide a choice of disk size for primary data storage. See Creating a New Disk Offering.
+				</div></li><li class="listitem"><div class="para">
+					Network Offerings, defined by the CloudStack administrator, describe the feature set that is available to end users from the virtual router or external networking devices on a given guest network. See Network Offerings.
+				</div></li><li class="listitem"><div class="para">
+					Templates, defined by the CloudStack administrator or by any CloudStack user, are the base OS images that the user can choose from when creating a new instance. For example, CloudStack includes CentOS as a template. See Working with Templates.
+				</div></li></ul></div><div class="para">
+			In addition to these choices that are provided for users, there is another type of service offering which is available only to the CloudStack root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings.
+		</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/using-multiple-guest-networks.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/using-multiple-guest-networks.html b/docs/tmp/en-US/epub/OEBPS/using-multiple-guest-networks.html
new file mode 100644
index 0000000..aa5e3ba
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/using-multiple-guest-networks.html
@@ -0,0 +1,51 @@
+<?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.6. Using Multiple Guest 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="using-multiple-guest-networks"><div class="titlepage"><div><div><h1 class="title" id="using-multiple-guest-networks">15.6. Using Multiple Guest Networks</h1></div></div></div><div class="para">
+		In zones that use advanced networking, additional networks for guest traffic may be added at any time after the initial installation. You can also customize the domain name associated with the network by specifying a DNS suffix for each network.
+	</div><div class="para">
+		A VM's networks are defined at VM creation time. A VM cannot add or remove networks after it has been created, although the user can go into the guest and remove the IP address from the NIC on a particular network.
+	</div><div class="para">
+		Each VM has just one default network. The virtual router's DHCP reply will set the guest's default gateway as that for the default network. Multiple non-default networks may be added to a guest in addition to the single, required default network. The administrator can control which networks are available as the default network.
+	</div><div class="para">
+		Additional networks can either be available to all accounts or be assigned to a specific account. Networks that are available to all accounts are zone-wide. Any user with access to the zone can create a VM with access to that network. These zone-wide networks provide little or no isolation between guests.Networks that are assigned to a specific account provide strong isolation.
+	</div><div class="section" id="add-additional-guest-network"><div class="titlepage"><div><div><h2 class="title" id="add-additional-guest-network">15.6.1. Adding an Additional Guest Network</h2></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 Add guest network. 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 name of the zone this network applies to. Each zone is a broadcast domain, and therefore each zone has a different IP range for the guest network. The administrator must configure the IP range for each zone.
+					</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 Create.
+			</div></li></ol></div></div><div class="section" id="change-network-offering-on-guest-network"><div class="titlepage"><div><div><h2 class="title" id="change-network-offering-on-guest-network">15.6.2. Changing the Network Offering on a Guest Network</h2></div></div></div><div class="para">
+		A user or administrator can change the network offering that is associated with an existing guest network.
+	</div><div class="itemizedlist"><ul><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">
+				If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network. See Stopping and Starting VMs. Then return here and continue to the next step
+			</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 you want to modify 
+				<span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="AttachDiskButton.png: button to attach a volume" /></span>
+				.
+			</div></li><li class="listitem"><div class="para">
+				In Network Offering, choose the new network offering, then click Apply.
+			</div></li><li class="listitem"><div class="para">
+				A prompt appears asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected. Choose No to proceed with the change.
+			</div></li><li class="listitem"><div class="para">
+				Wait for the update to complete. Don’t try to restart VMs until after the network change is complete.
+			</div></li><li class="listitem"><div class="para">
+				If you stopped any VMs in step 2, restart them.
+			</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/using-sshkeys.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/using-sshkeys.html b/docs/tmp/en-US/epub/OEBPS/using-sshkeys.html
new file mode 100644
index 0000000..a38bbd5
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/using-sshkeys.html
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Using SSH Keys for Authentication</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="using-sshkeys"><div class="titlepage"><div><div><h1 class="title" id="using-sshkeys">5.2. Using SSH Keys for Authentication</h1></div></div></div><div class="para">
+		In addition to the username and password authentication, CloudStack supports using SSH keys to log in to the cloud infrastructure for additional security. You can use the createSSHKeyPair API to generate the SSH keys.
+	</div><div class="para">
+		Because each cloud user has their own SSH key, one cloud user cannot log in to another cloud user's instances unless they share their SSH key files. Using a single SSH key pair, you can manage multiple instances.
+	</div><div class="section" id="create-ssh-template"><div class="titlepage"><div><div><h2 class="title" id="create-ssh-template">5.2.1.  Creating an Instance Template that Supports SSH Keys</h2></div></div></div><div class="para">
+			Create a instance template that supports SSH Keys.
+		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+					Create a new instance by using the template provided by cloudstack.
+				</div><div class="para">
+					For more information on creating a new instance, see
+				</div></li><li class="listitem"><div class="para">
+					Download the cloudstack script from <a href="http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/">The SSH Key Gen Script</a>to the instance you have created.
+				</div><pre class="programlisting">wget http://downloads.sourceforge.net/project/cloudstack/SSH%20Key%20Gen%20Script/cloud-set-guest-sshkey.in?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fcloudstack%2Ffiles%2FSSH%2520Key%2520Gen%2520Script%2F&amp;ts=1331225219&amp;use_mirror=iweb</pre></li><li class="listitem"><div class="para">
+					Copy the file to /etc/init.d.
+				</div><pre class="programlisting">cp cloud-set-guest-sshkey.in /etc/init.d/</pre></li><li class="listitem"><div class="para">
+					Give the necessary permissions on the script:
+				</div><pre class="programlisting">chmod +x /etc/init.d/cloud-set-guest-sshkey.in</pre></li><li class="listitem"><div class="para">
+					Run the script while starting up the operating system:
+				</div><pre class="programlisting">chkconfig --add cloud-set-guest-sshkey.in</pre></li><li class="listitem"><div class="para">
+					Stop the instance.
+				</div></li></ol></div></div><div class="section" id="create-ssh-keypair"><div class="titlepage"><div><div><h2 class="title" id="create-ssh-keypair">5.2.2. Creating the SSH Keypair</h2></div></div></div><div class="para">
+			You must make a call to the createSSHKeyPair api method. You can either use the CloudStack Python API library or the curl commands to make the call to the cloudstack api.
+		</div><div class="para">
+			For example, make a call from the cloudstack server to create a SSH keypair called "keypair-doc" for the admin account in the root domain:
+		</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+				Ensure that you adjust these values to meet your needs. If you are making the API call from a different server, your URL/PORT will be different, and you will need to use the API keys.
+			</div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+					Run the following curl command:
+				</div><pre class="programlisting">curl --globoff "http://localhost:8096/?command=createSSHKeyPair&amp;name=keypair-doc&amp;account=admin&amp;domainid=5163440e-c44b-42b5-9109-ad75cae8e8a2"</pre><div class="para">
+					The output is something similar to what is given below:
+				</div><pre class="programlisting">&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;&lt;createsshkeypairresponse cloud-stack-version="3.0.0.20120228045507"&gt;&lt;keypair&gt;&lt;name&gt;keypair-doc&lt;/name&gt;&lt;fingerprint&gt;f6:77:39:d5:5e:77:02:22:6a:d8:7f:ce:ab:cd:b3:56&lt;/fingerprint&gt;&lt;privatekey&gt;-----BEGIN RSA PRIVATE KEY-----
+MIICXQIBAAKBgQCSydmnQ67jP6lNoXdX3noZjQdrMAWNQZ7y5SrEu4wDxplvhYci
+dXYBeZVwakDVsU2MLGl/K+wefwefwefwefwefJyKJaogMKn7BperPD6n1wIDAQAB
+AoGAdXaJ7uyZKeRDoy6wA0UmF0kSPbMZCR+UTIHNkS/E0/4U+6lhMokmFSHtu
+mfDZ1kGGDYhMsdytjDBztljawfawfeawefawfawfawQQDCjEsoRdgkduTy
+QpbSGDIa11Jsc+XNDx2fgRinDsxXI/zJYXTKRhSl/LIPHBw/brW8vzxhOlSOrwm7
+VvemkkgpAkEAwSeEw394LYZiEVv395ar9MLRVTVLwpo54jC4tsOxQCBlloocK
+lYaocpk0yBqqOUSBawfIiDCuLXSdvBo1Xz5ICTM19vgvEp/+kMuECQBzm
+nVo8b2Gvyagqt/KEQo8wzH2THghZ1qQ1QRhIeJG2aissEacF6bGB2oZ7Igim5L14
+4KR7OeEToyCLC2k+02UCQQCrniSnWKtDVoVqeK/zbB32JhW3Wullv5p5zUEcd
+KfEEuzcCUIxtJYTahJ1pvlFkQ8anpuxjSEDp8x/18bq3
+-----END RSA PRIVATE KEY-----
+&lt;/privatekey&gt;&lt;/keypair&gt;&lt;/createsshkeypairresponse&gt;</pre></li><li class="listitem"><div class="para">
+					Copy the key data into a file. The file looks like this:
+				</div><pre class="programlisting">-----BEGIN RSA PRIVATE KEY-----
+MIICXQIBAAKBgQCSydmnQ67jP6lNoXdX3noZjQdrMAWNQZ7y5SrEu4wDxplvhYci
+dXYBeZVwakDVsU2MLGl/K+wefwefwefwefwefJyKJaogMKn7BperPD6n1wIDAQAB
+AoGAdXaJ7uyZKeRDoy6wA0UmF0kSPbMZCR+UTIHNkS/E0/4U+6lhMokmFSHtu
+mfDZ1kGGDYhMsdytjDBztljawfawfeawefawfawfawQQDCjEsoRdgkduTy
+QpbSGDIa11Jsc+XNDx2fgRinDsxXI/zJYXTKRhSl/LIPHBw/brW8vzxhOlSOrwm7
+VvemkkgpAkEAwSeEw394LYZiEVv395ar9MLRVTVLwpo54jC4tsOxQCBlloocK
+lYaocpk0yBqqOUSBawfIiDCuLXSdvBo1Xz5ICTM19vgvEp/+kMuECQBzm
+nVo8b2Gvyagqt/KEQo8wzH2THghZ1qQ1QRhIeJG2aissEacF6bGB2oZ7Igim5L14
+4KR7OeEToyCLC2k+02UCQQCrniSnWKtDVoVqeK/zbB32JhW3Wullv5p5zUEcd
+KfEEuzcCUIxtJYTahJ1pvlFkQ8anpuxjSEDp8x/18bq3
+-----END RSA PRIVATE KEY-----</pre></li><li class="listitem"><div class="para">
+					Save the file.
+				</div></li></ol></div></div><div class="section" id="creating-ssh-instance"><div class="titlepage"><div><div><h2 class="title" id="creating-ssh-instance">5.2.3. Creating an Instance</h2></div></div></div><div class="para">
+			After you save the SSH keypair file, you must create an instance by using the template that you created at <a class="xref" href="using-sshkeys.html#create-ssh-template">Section 5.2.1, “ Creating an Instance Template that Supports SSH Keys”</a>. Ensure that you use the same SSH key name that you created at <a class="xref" href="using-sshkeys.html#create-ssh-keypair">Section 5.2.2, “Creating the SSH Keypair”</a>.
+		</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+				You cannot create the instance by using the GUI at this time and associate the instance with the newly created SSH keypair.
+			</div></div></div><div class="para">
+			A sample curl command to create a new instance is:
+		</div><pre class="programlisting">curl --globoff http://localhost:&lt;port numbet&gt;/?command=deployVirtualMachine\&amp;zoneId=1\&amp;serviceOfferingId=18727021-7556-4110-9322-d625b52e0813\&amp;templateId=e899c18a-ce13-4bbf-98a9-625c5026e0b5\&amp;securitygroupids=ff03f02f-9e3b-48f8-834d-91b822da40c5\&amp;account=admin\&amp;domainid=1\&amp;keypair=keypair-doc</pre><div class="para">
+			Substitute the template, service offering and security group IDs (if you are using the security group feature) that are in your cloud environment.
+		</div></div><div class="section" id="logging-in-ssh"><div class="titlepage"><div><div><h2 class="title" id="logging-in-ssh">5.2.4. Logging In Using the SSH Keypair</h2></div></div></div><div class="para">
+			To test your SSH key generation is successful, check whether you can log in to the cloud setup.
+		</div><div class="para">
+			For exaple, from a Linux OS, run:
+		</div><pre class="programlisting">ssh -i ~/.ssh/keypair-doc &lt;ip address&gt;</pre><div class="para">
+			The -i parameter tells the ssh client to use a ssh key found at ~/.ssh/keypair-doc.
+		</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/virtual-machines.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/virtual-machines.html b/docs/tmp/en-US/epub/OEBPS/virtual-machines.html
new file mode 100644
index 0000000..62a92ce
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/virtual-machines.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 10. Working With 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="virtual-machines"><div class="titlepage"><div><div><h1 class="title">Chapter 10. Working With Virtual Machines</h1></div></div></div><div class="section" id="about-working-with-vms"><div class="titlepage"><div><div><h1 class="title" id="about-working-with-vms">10.1. About Working with Virtual Machines</h1></div></div></div><div class="para">
+		CloudStack provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudStack provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed.
+	</div><div class="para">
+		Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123.
+			</div></li><li class="listitem"><div class="para">
+				Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name.
+			</div></li><li class="listitem"><div class="para">
+				Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name
+			</div></li></ul></div><div class="para">
+		Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on
+	</div><div class="para">
+		Each new VM is allocated one public IP address. When the VM is started, CloudStack automatically creates a static NAT between this public IP address and the private IP address of the VM.
+	</div><div class="para">
+		If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs.
+	</div><div class="para">
+		CloudStack cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack will restart it. To shut down an HA-enabled VM, you must go through the CloudStack UI or API.
+	</div></div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/virtual-router.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/virtual-router.html b/docs/tmp/en-US/epub/OEBPS/virtual-router.html
new file mode 100644
index 0000000..877f6cf
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/virtual-router.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.4. Virtual Router</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="virtual-router"><div class="titlepage"><div><div><h1 class="title" id="virtual-router">16.4. Virtual Router</h1></div></div></div><div class="para">
+		The virtual router is a type of System Virtual Machine. The virtual router is one of the most frequently used service providers in CloudStack. The end user has no direct access to the virtual router. Users can ping the virtual router and take actions that affect it (such as setting up port forwarding), but users do not have SSH access into the virtual router.
+	</div><div class="para">
+		There is no mechanism for the administrator to log in to the virtual router. Virtual routers can be restarted by administrators, but this will interrupt public network access and other services for end users. A basic test in debugging networking issues is to attempt to ping the virtual router from a guest VM. Some of the characteristics of the virtual router are determined by its associated system service offering.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/vlan-provisioning.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/vlan-provisioning.html b/docs/tmp/en-US/epub/OEBPS/vlan-provisioning.html
new file mode 100644
index 0000000..8df6314
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/vlan-provisioning.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>11.9. VLAN Provisioning</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="vlan-provisioning"><div class="titlepage"><div><div><h1 class="title" id="vlan-provisioning">11.9. VLAN Provisioning</h1></div></div></div><div class="para">
+		CloudStack automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process.
+	</div><div class="para">
+		CloudStack manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host.
+	</div><div class="para">
+		For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/vm-lifecycle.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/vm-lifecycle.html b/docs/tmp/en-US/epub/OEBPS/vm-lifecycle.html
new file mode 100644
index 0000000..f8ee057
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/vm-lifecycle.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.3. VM Lifecycle</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="vm-lifecycle"><div class="titlepage"><div><div><h1 class="title" id="vm-lifecycle">10.3. VM Lifecycle</h1></div></div></div><div class="para">
+		Virtual machines can be in the following states:
+	</div><div class="mediaobject"><img src="./images/basic-deployment.png" alt="basic-deployment.png: Basic two-machine CloudStack deployment" /></div><div class="para">
+		Once a virtual machine is destroyed, it cannot be recovered. All the resources used by the virtual machine will be reclaimed by the system. This includes the virtual machine’s IP address.
+	</div><div class="para">
+		A stop will attempt to gracefully shut down the operating system, which typically involves terminating all the running applications. If the operation system cannot be stopped, it will be forcefully terminated. This has the same effect as pulling the power cord to a physical machine.
+	</div><div class="para">
+		A reboot is a stop followed by a start.
+	</div><div class="para">
+		CloudPlatform preserves the state of the virtual machine hard disk until the machine is destroyed.
+	</div><div class="para">
+		A running virtual machine may fail because of hardware or network issues. A failed virtual machine is in the down state.
+	</div><div class="para">
+		The system places the virtual machine into the down state if it does not receive the heartbeat from the hypervisor for three minutes.
+	</div><div class="para">
+		The user can manually restart the virtual machine from the down state.
+	</div><div class="para">
+		The system will start the virtual machine from the down state automatically if the virtual machine is marked as HA-enabled.
+	</div></div></body></html>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/8e353282/docs/tmp/en-US/epub/OEBPS/vpn.html
----------------------------------------------------------------------
diff --git a/docs/tmp/en-US/epub/OEBPS/vpn.html b/docs/tmp/en-US/epub/OEBPS/vpn.html
new file mode 100644
index 0000000..0714173
--- /dev/null
+++ b/docs/tmp/en-US/epub/OEBPS/vpn.html
@@ -0,0 +1,295 @@
+<?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.17. VPN</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="vpn"><div class="titlepage"><div><div><h1 class="title" id="vpn">15.17. VPN</h1></div></div></div><div class="para">
+		CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner.
+	</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic.
+		</div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				<span class="bold bold"><strong>Road Warrior / Remote Access</strong></span>. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server.
+			</div></li><li class="listitem"><div class="para">
+				<span class="bold bold"><strong>Site to Site</strong></span>. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user’s subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user’s gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature.
+			</div></li></ul></div><div class="section" id="configure-vpn"><div class="titlepage"><div><div><h2 class="title" id="configure-vpn">15.17.1. Configuring VPN</h2></div></div></div><div class="para">
+		To set up VPN for the cloud:
+	</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, click Global Settings.
+			</div></li><li class="listitem"><div class="para">
+				Set the following global configuration parameters.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						remote.access.vpn.client.ip.range – The range of IP addressess to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server.
+					</div></li><li class="listitem"><div class="para">
+						remote.access.vpn.psk.length – Length of the IPSec key.
+					</div></li><li class="listitem"><div class="para">
+						remote.access.vpn.user.limit – Maximum number of VPN users per account.
+					</div></li></ul></div></li></ol></div><div class="para">
+		To enable VPN for a particular network:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in as a user or administrator to the CloudStack UI.
+			</div></li><li class="listitem"><div class="para">
+				In the left navigation, click Network.
+			</div></li><li class="listitem"><div class="para">
+				Click the name of the network 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 one of the displayed IP address names.
+			</div></li><li class="listitem"><div class="para">
+				Click the Enable VPN button 
+				<span class="inlinemediaobject"><img src="./images/vpn-icon.png" alt="AttachDiskButton.png: button to attach a volume" /></span>
+				.
+			</div><div class="para">
+				The IPsec key is displayed in a popup window.
+			</div></li></ol></div></div><div class="section" id="using-vpn-with-windows"><div class="titlepage"><div><div><h2 class="title" id="using-vpn-with-windows">15.17.2. Using VPN with Windows</h2></div></div></div><div class="para">
+		The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions.
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password.
+			</div></li><li class="listitem"><div class="para">
+				On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network.
+			</div></li><li class="listitem"><div class="para">
+				In the next dialog, select No, create a new connection.
+			</div></li><li class="listitem"><div class="para">
+				In the next dialog, select Use my Internet Connection (VPN).
+			</div></li><li class="listitem"><div class="para">
+				In the next dialog, enter the source NAT IP from step 1 and give the connection a name. Check Don't connect now.
+			</div></li><li class="listitem"><div class="para">
+				In the next dialog, enter the user name and password selected in step 1.
+			</div></li><li class="listitem"><div class="para">
+				Click Create.
+			</div></li><li class="listitem"><div class="para">
+				Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet.
+			</div></li><li class="listitem"><div class="para">
+				Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab.
+			</div></li><li class="listitem"><div class="para">
+				In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from Step 1.
+			</div></li><li class="listitem"><div class="para">
+				The connection is ready for activation. Go back to Control Panel -&gt; Network Connections and double-click the created connection.
+			</div></li><li class="listitem"><div class="para">
+				Enter the user name and password from Step 1.
+			</div></li></ol></div></div><div class="section" id="using-vpn-with-mac"><div class="titlepage"><div><div><h2 class="title" id="using-vpn-with-mac">15.17.3. Using VPN with Mac OS X</h2></div></div></div><div class="para">
+		In Mac OS X, in Network Preferences - Advanced, make sure Send all traffic over VPN connection is not checked.
+	</div></div><div class="section" id="site-to-site-vpn"><div class="titlepage"><div><div><h2 class="title" id="site-to-site-vpn">15.17.4. Setting Up a Site-to-Site VPN Connection</h2></div></div></div><div class="para">
+		A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. Having this facility eliminates the need to establish VPN connections to individual VMs.
+	</div><div class="para">
+		The supported endpoints on the remote datacenters are:
+	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				Cisco ISR with IOS 12.4 or later
+			</div></li><li class="listitem"><div class="para">
+				Juniper J-Series routers with JunOS 9.5 or later
+			</div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections.
+		</div></div></div><div class="para">
+		To set up a Site-to-Site VPN connection, perform the following:
+	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+				Create a Virtual Private Cloud (VPC).
+			</div><div class="para">
+				See <a class="xref" href="configure-vpc.html">Section 15.19, “Configuring a Virtual Private Cloud”</a>.
+			</div></li><li class="listitem"><div class="para">
+				Create a VPN Customer Gateway.
+			</div></li><li class="listitem"><div class="para">
+				Create a VPN gateway for the VPC that you created.
+			</div></li><li class="listitem"><div class="para">
+				Create VPN connection from the VPC VPN gateway to the customer VPN gateway.
+			</div></li></ol></div><div class="section" id="create-vpn-customer-gateway"><div class="titlepage"><div><div><h3 class="title" id="create-vpn-customer-gateway">15.17.4.1. Creating and Updating a VPN Customer Gateway</h3></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+			A VPN customer gateway can be connected to only one VPN gateway at a time.
+		</div></div></div><div class="para">
+		To add a VPN Customer Gateway:
+	</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">
+				In the Select view, select VPN Customer Gateway.
+			</div></li><li class="listitem"><div class="para">
+				Click Add site-to-site VPN.
+			</div><div class="mediaobject"><img src="./images/add-vpn-customer-gateway.png" alt="addvpncustomergateway.png: adding a customer gateway." /></div><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>: A unique name for the VPN customer gateway you create.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Gateway</strong></span>: The IP address for the remote gateway.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>CIDR list</strong></span>: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC’s CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>IPsec Preshared Key</strong></span>: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other.
+					</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+							The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway.
+						</div></div></div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>IKE Encryption</strong></span>: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys.
+					</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+							The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key.
+						</div></div></div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>IKE Hash</strong></span>: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>IKE DH</strong></span>: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit).
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>ESP Encryption</strong></span>: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES.
+					</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+							The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow.
+						</div></div></div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>ESP Hash</strong></span>: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Perfect Forward Secrecy</strong></span>: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges.
+					</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+							When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA’s have expired, the keys used for new phase-2 SA’s have not been generated from the current phase-1 keying material.
+						</div></div></div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>IKE Lifetime (seconds)</strong></span>: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>ESP Lifetime (seconds)</strong></span>: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys.
+					</div></li><li class="listitem"><div class="para">
+						<span class="bold bold"><strong>Dead Peer Detection</strong></span>: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It’s recommended to have the same configuration of DPD on both side of VPN connection.
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Click OK.
+			</div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="idm1437032">Updating and Removing a VPN Customer Gateway</h5>
+			You can update a customer gateway either with no VPN connection, or related VPN connection is in error state.
+		</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">
+				In the Select view, select VPN Customer Gateway.
+			</div></li><li class="listitem"><div class="para">
+				Select the VPN customer gateway you want to work with.
+			</div></li><li class="listitem"><div class="para">
+				To modify the required parameters, click the Edit VPN Customer Gateway button
+				<span class="inlinemediaobject"><img src="./images/edit-icon.png" alt="edit.png: button to edit a VPN customer gateway" /></span>
+			</div></li><li class="listitem"><div class="para">
+				To remove the VPN customer gateway, click the Delete VPN Customer Gateway button
+				<span class="inlinemediaobject"><img src="./images/delete-button.png" alt="delete.png: button to remove a VPN customer gateway" /></span>
+			</div></li><li class="listitem"><div class="para">
+				Click OK.
+			</div></li></ol></div></div><div class="section" id="create-vpn-gateway-for-vpc"><div class="titlepage"><div><div><h3 class="title" id="create-vpn-gateway-for-vpc">15.17.4.2. Creating a VPN gateway for the VPC</h3></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">
+				In the Select view, select VPC.
+			</div><div class="para">
+				All the VPCs that you have created for the account is listed in the page.
+			</div></li><li class="listitem"><div class="para">
+				Click the Configure button of the VPC to which you want to deploy the VMs.
+			</div><div class="para">
+				The VPC page is displayed where all the tiers you created are listed in a diagram.
+			</div></li><li class="listitem"><div class="para">
+				Click the Settings icon.
+			</div><div class="para">
+				The following options are displayed.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						IP Addresses
+					</div></li><li class="listitem"><div class="para">
+						Gateways
+					</div></li><li class="listitem"><div class="para">
+						Site-to-Site VPN
+					</div></li><li class="listitem"><div class="para">
+						Network ACLs
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Select Site-to-Site VPN.
+			</div><div class="para">
+				If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway.
+			</div></li><li class="listitem"><div class="para">
+				In the confirmation dialog, click Yes to confirm.
+			</div><div class="para">
+				Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm.
+			</div><div class="para">
+				The following details are displayed in the VPN Gateway page:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						IP Address
+					</div></li><li class="listitem"><div class="para">
+						Account
+					</div></li><li class="listitem"><div class="para">
+						Domain
+					</div></li></ul></div></li></ol></div></div><div class="section" id="create-vpn-connection-vpc"><div class="titlepage"><div><div><h3 class="title" id="create-vpn-connection-vpc">15.17.4.3. Creating a VPN Connection</h3></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">
+				In the Select view, select VPC.
+			</div><div class="para">
+				All the VPCs that you create for the account are listed in the page.
+			</div></li><li class="listitem"><div class="para">
+				Click the Configure button of the VPC to which you want to deploy the VMs.
+			</div><div class="para">
+				The VPC page is displayed where all the tiers you created are listed in a diagram.
+			</div></li><li class="listitem"><div class="para">
+				Click the Settings icon.
+			</div><div class="para">
+				The following options are displayed.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						IP Addresses
+					</div></li><li class="listitem"><div class="para">
+						Gateways
+					</div></li><li class="listitem"><div class="para">
+						Site-to-Site VPN
+					</div></li><li class="listitem"><div class="para">
+						Network ASLs
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Select Site-to-Site VPN.
+			</div><div class="para">
+				The Site-to-Site VPN page is displayed.
+			</div></li><li class="listitem"><div class="para">
+				From the Select View drop-down, ensure that VPN Connection is selected.
+			</div></li><li class="listitem"><div class="para">
+				Click Create VPN Connection.
+			</div><div class="para">
+				The Create VPN Connection dialog is displayed:
+			</div><div class="mediaobject"><img src="./images/create-vpn-connection.png" alt="createvpnconnection.png: creating a vpn connection to the customer gateway." /></div></li><li class="listitem"><div class="para">
+				Select the desired customer gateway, then click OK to confirm.
+			</div><div class="para">
+				Within a few moments, the VPN Connection is displayed.
+			</div><div class="para">
+				The following information on the VPN connection is displayed:
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						IP Address
+					</div></li><li class="listitem"><div class="para">
+						Gateway
+					</div></li><li class="listitem"><div class="para">
+						State
+					</div></li><li class="listitem"><div class="para">
+						IPSec Preshared Key
+					</div></li><li class="listitem"><div class="para">
+						IKE Policy
+					</div></li><li class="listitem"><div class="para">
+						ESP Policy
+					</div></li></ul></div></li></ol></div></div><div class="section" id="delete-reset-vpn"><div class="titlepage"><div><div><h3 class="title" id="delete-reset-vpn">15.17.4.4. Restarting and Removing a VPN Connection</h3></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">
+				In the Select view, select VPC.
+			</div><div class="para">
+				All the VPCs that you have created for the account is listed in the page.
+			</div></li><li class="listitem"><div class="para">
+				Click the Configure button of the VPC to which you want to deploy the VMs.
+			</div><div class="para">
+				The VPC page is displayed where all the tiers you created are listed in a diagram.
+			</div></li><li class="listitem"><div class="para">
+				Click the Settings icon.
+			</div><div class="para">
+				The following options are displayed.
+			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+						IP Addresses
+					</div></li><li class="listitem"><div class="para">
+						Gateways
+					</div></li><li class="listitem"><div class="para">
+						Site-to-Site VPN
+					</div></li><li class="listitem"><div class="para">
+						Network ASLs
+					</div></li></ul></div></li><li class="listitem"><div class="para">
+				Select Site-to-Site VPN.
+			</div><div class="para">
+				The Site-to-Site VPN page is displayed.
+			</div></li><li class="listitem"><div class="para">
+				From the Select View drop-down, ensure that VPN Connection is selected.
+			</div><div class="para">
+				All the VPN connections you created are displayed.
+			</div></li><li class="listitem"><div class="para">
+				Select the VPN connection you want to work with.
+			</div><div class="para">
+				The Details tab is displayed.
+			</div></li><li class="listitem"><div class="para">
+				To remove a VPN connection, click the Delete VPN connection button
+				<span class="inlinemediaobject"><img src="./images/remove-vpn.png" alt="remove-vpn.png: button to remove a VPN connection" /></span>
+			</div><div class="para">
+				To restart a VPN connection, click the Reset VPN connection button present in the Details tab.
+				<span class="inlinemediaobject"><img src="./images/reset-vpn.png" alt="reset-vpn.png: button to reset a VPN connection" /></span>
+			</div></li></ol></div></div></div></div></body></html>


Mime
View raw message