Return-Path: X-Original-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5208DD5BE for ; Thu, 8 Nov 2012 05:30:40 +0000 (UTC) Received: (qmail 79439 invoked by uid 500); 8 Nov 2012 05:30:40 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 79201 invoked by uid 500); 8 Nov 2012 05:30:39 -0000 Mailing-List: contact cloudstack-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-commits@incubator.apache.org Received: (qmail 78658 invoked by uid 99); 8 Nov 2012 05:30:38 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 05:30:38 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id C6FAD45646; Thu, 8 Nov 2012 05:30:37 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: jzb@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: [1/7] git commit: CLOUDSTACK-403: New Doc file on About password and key encryption. In the Install guide, fixed references to the same section. Message-Id: <20121108053037.C6FAD45646@tyr.zones.apache.org> Date: Thu, 8 Nov 2012 05:30:37 +0000 (UTC) Updated Branches: refs/heads/master d118a3d76 -> 35dcda2e8 CLOUDSTACK-403: New Doc file on About password and key encryption. In the Install guide, fixed references to the same section. Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/35dcda2e Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/35dcda2e Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/35dcda2e Branch: refs/heads/master Commit: 35dcda2e88dc8f9dc9a933533c8758778de409bf Parents: ffdf19d Author: Radhika PC Authored: Wed Nov 7 23:29:55 2012 -0600 Committer: Joe Brockmeier Committed: Wed Nov 7 23:29:55 2012 -0600 ---------------------------------------------------------------------- docs/tmp/en-US/html/accounts-users-domains.html | 10 +- docs/tmp/en-US/html/configure-vpc.html | 8 +- docs/tmp/en-US/html/host-add.html | 8 +- docs/tmp/en-US/html/index.html | 4 +- docs/tmp/en-US/html/log-in.html | 6 +- docs/tmp/en-US/html/network-service-providers.html | 2 +- ...oting-dataloss-on-exported-primary-storage.html | 8 +- .../en-US/html/troubleshooting-lb-rules-fails.html | 6 +- ...ng-maintenance-mode-not-working-on-vCenter.html | 8 +- ...roubleshooting-recover-lost-virtual-router.html | 6 +- .../html/troubleshooting-unable-to-deploy-vms.html | 6 +- .../troubleshooting-unable-to-power-on-vm.html | 6 +- docs/tmp/en-US/html/upgrade-instructions.html | 4 +- docs/tmp/en-US/html/vpn.html | 2 +- ...4.0.0-incubating-API_Developers_Guide-en-US.pdf | Bin 463686 -> 463683 bytes ...oudStack-4.0.0-incubating-Admin_Guide-en-US.pdf | Bin 1913994 -> 1913997 bytes ...dStack-4.0.0-incubating-Release_Notes-en-US.pdf | Bin 274657 -> 274651 bytes docs/tmp/en-US/xml/API_Developers_Guide.fo | 470 ++-- docs/tmp/en-US/xml/Admin_Guide.fo | 2522 +++++++------- docs/tmp/en-US/xml/Release_Notes.fo | 494 ++-- .../xml/management-server-install-db-external.xml | 20 +- .../xml/management-server-install-db-local.xml | 20 +- .../en-US/xml/management-server-install-flow.xml | 1 + docs/tmp/en-US/xml/prepare-system-vm-template.xml | 12 +- .../management-server-install-db-external.xml | 181 +- .../xml_tmp/management-server-install-db-local.xml | 144 +- .../xml_tmp/management-server-install-flow.xml | 1 + .../en-US/xml_tmp/prepare-system-vm-template.xml | 15 +- 28 files changed, 2024 insertions(+), 1940 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/accounts-users-domains.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/accounts-users-domains.html b/docs/tmp/en-US/html/accounts-users-domains.html index 360c8b2..19b5e83 100644 --- a/docs/tmp/en-US/html/accounts-users-domains.html +++ b/docs/tmp/en-US/html/accounts-users-domains.html @@ -1,20 +1,20 @@ -3.1. Accounts, Users, and Domains

Product SiteDocumentation Site

3.1. Accounts, Users, and Domains

Accounts
+3.1. Accounts, Users, and Domains

Product SiteDocumentation Site

3.1. Accounts, Users, and Domains

Accounts
An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account. -
Domains
+
Domains
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.
For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user. -
Users
+
Users
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.
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.
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. -
Domain Administrators
+
Domain Administrators
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. -
Root Administrator
+
Root Administrator
Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains
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. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/configure-vpc.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/configure-vpc.html b/docs/tmp/en-US/html/configure-vpc.html index 2748895..02d902e 100644 --- a/docs/tmp/en-US/html/configure-vpc.html +++ b/docs/tmp/en-US/html/configure-vpc.html @@ -4,7 +4,7 @@ CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range.
For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on. -
Major Components of a VPC:
+
Major Components of a VPC:
A VPC is comprised of the following network components:
Network Architecture in a VPC
+
Network Architecture in a VPC
In a VPC, the following four basic options of network architectures are present:
  • VPC with a public gateway only @@ -34,7 +34,7 @@ VPC with public and private gateways and site-to-site VPN access
  • VPC with a private gateway only and site-to-site VPN access -
Connectivity Options for a VPC
+
Connectivity Options for a VPC
You can connect your VPC to:
  • The Internet through the public gateway. @@ -42,7 +42,7 @@ The corporate datacenter by using a site-to-site VPN connection through the VPN gateway.
  • Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway. -
VPC Network Considerations
+
VPC Network Considerations
Consider the following before you create a VPC:
  • A VPC, by default, is created in the enabled state. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/host-add.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/host-add.html b/docs/tmp/en-US/html/host-add.html index 31aab80..2d27af7 100644 --- a/docs/tmp/en-US/html/host-add.html +++ b/docs/tmp/en-US/html/host-add.html @@ -14,7 +14,7 @@ Section 7.5.2, “Adding a Host (vSphere)”

7.5.1. Adding a Host (XenServer or KVM)

XenServer and KVM hosts can be added to a cluster at any time. -

7.5.1.1. Requirements for XenServer and KVM Hosts

Warning

+

7.5.1.1. Requirements for XenServer and KVM Hosts

Warning

Make sure the hypervisor host does not have any VMs already running before you add it to CloudStack.
Configuration requirements: @@ -26,7 +26,7 @@ For KVM, do not put more than 16 hosts in a cluster.
For hardware requirements, see the installation section for your hypervisor in the CloudStack Installation Guide. -
7.5.1.1.1. XenServer Host Additional Requirements
+
7.5.1.1.1. XenServer Host Additional Requirements
If network bonding is in use, the administrator must cable the new host identically to other hosts in the cluster.
For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool. @@ -38,11 +38,11 @@ Copy the script from the Management Server in /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable.
  • Run the script: - 
    # ./cloud-setup-bonding.sh
    • 7.5.1.1.2. KVM Host Additional Requirements
    • + 
      # ./cloud-setup-bonding.sh
    7.5.1.1.2. KVM Host Additional Requirements
    • If shared mountpoint storage is in use, the administrator should ensure that the new host has all the same mountpoints (with storage mounted) as the other hosts in the cluster.
    • Make sure the new host has the same network configuration (guest, private, and public network) as other hosts in the cluster. -

    7.5.1.2. Adding a XenServer or KVM Host

    • +

    7.5.1.2. Adding a XenServer or KVM Host

    • If you have not already done so, install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see the appropriate section for your hypervisor in the CloudStack Installation Guide.
    • Log in to the CloudStack UI as administrator. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/index.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/index.html b/docs/tmp/en-US/html/index.html index 229192f..89a0e0c 100644 --- a/docs/tmp/en-US/html/index.html +++ b/docs/tmp/en-US/html/index.html @@ -1,9 +1,9 @@ -Version 4.0.0-incubating Release Notes

      Product SiteDocumentation Site

      Apache CloudStack

      Version 4.0.0-incubating Release Notes

      Revised October 17, 2012 19:49 UTC

      +Version 4.0.0-incubating Release Notes

      Product SiteDocumentation Site

      Apache CloudStack

      Version 4.0.0-incubating Release Notes

      Revised October 17, 2012 19:49 UTC

      -

      Apache CloudStack

      Legal Notice

      +

      Apache CloudStack

      Legal Notice

      Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
      http://www.apache.org/licenses/LICENSE-2.0 http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/log-in.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/log-in.html b/docs/tmp/en-US/html/log-in.html index 6ece78e..30f6307 100644 --- a/docs/tmp/en-US/html/log-in.html +++ b/docs/tmp/en-US/html/log-in.html @@ -4,11 +4,11 @@ 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) 
      http://<management-server-ip-address>:8080/client
      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: -
      Username
      +
      Username
      The user ID of your account. The default username is admin. -
      Password
      +
      Password
      The password associated with the user ID. The password for the default username is password. -
      Domain
      +
      Domain
      If you are a root user, leave this field blank.
      If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/network-service-providers.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/network-service-providers.html b/docs/tmp/en-US/html/network-service-providers.html index 4c59e84..48b4b54 100644 --- a/docs/tmp/en-US/html/network-service-providers.html +++ b/docs/tmp/en-US/html/network-service-providers.html @@ -8,6 +8,6 @@ You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device).
      If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, CloudPlatform will choose which provider to use whenever the service is called for. -
      Supported Network Service Providers
      +
      Supported Network Service Providers
      CloudPlatform ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering.
      http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-dataloss-on-exported-primary-storage.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-dataloss-on-exported-primary-storage.html b/docs/tmp/en-US/html/troubleshooting-dataloss-on-exported-primary-storage.html index 91bfe53..0981ebc 100644 --- a/docs/tmp/en-US/html/troubleshooting-dataloss-on-exported-primary-storage.html +++ b/docs/tmp/en-US/html/troubleshooting-dataloss-on-exported-primary-storage.html @@ -1,13 +1,13 @@ -22.3. Data Loss on Exported Primary Storage

      Product SiteDocumentation Site

      22.3. Data Loss on Exported Primary Storage

      Symptom
      +22.3. Data Loss on Exported Primary Storage

      Product SiteDocumentation Site

      22.3. Data Loss on Exported Primary Storage

      Symptom
      Loss of existing data on primary storage which has been exposed as a Linux NFS server export on an iSCSI volume. -
      Cause
      +
      Cause
      It is possible that a client from outside the intended pool has mounted the storage. When this occurs, the LVM is wiped and all data in the volume is lost -
      Solution
      +
      Solution
      When setting up LUN exports, restrict the range of IP addresses that are allowed access by specifying a subnet mask. For example: 
      echo “/export 192.168.1.0/24(rw,async,no_root_squash)” > /etc/exports
      Adjust the above command to suit your deployment needs. -
      More Information
      +
      More Information
      See the export procedure in the "Secondary Storage" section of the CloudStack Installation Guide
      http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-lb-rules-fails.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-lb-rules-fails.html b/docs/tmp/en-US/html/troubleshooting-lb-rules-fails.html index adb82ff..fc73fba 100644 --- a/docs/tmp/en-US/html/troubleshooting-lb-rules-fails.html +++ b/docs/tmp/en-US/html/troubleshooting-lb-rules-fails.html @@ -1,9 +1,9 @@ -22.8. Load balancer rules fail after changing network offering

      Prod uct SiteDocumentation Site

      22.8. Load balancer rules fail after changing network offering

      Symptom
      +22.8. Load balancer rules fail after changing network offering

      Prod uct SiteDocumentation Site

      22.8. Load balancer rules fail after changing network offering

      Symptom
      After changing the network offering on a network, load balancer rules stop working. -
      Cause
      +
      Cause
      Load balancing rules were created while using a network service offering that includes an external load balancer device such as NetScaler, and later the network service offering changed to one that uses the CloudPlatform virtual router. -
      Solution
      +
      Solution
      Create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function.
      http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-maintenance-mode-not-working-on-vCenter.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-maintenance-mode-not-working-on-vCenter.html b/docs/tmp/en-US/html/troubleshooting-maintenance-mode-not-working-on-vCenter.html index 867ad3d..7b86c4a 100644 --- a/docs/tmp/en-US/html/troubleshooting-maintenance-mode-not-working-on-vCenter.html +++ b/docs/tmp/en-US/html/troubleshooting-maintenance-mode-not-working-on-vCenter.html @@ -1,11 +1,11 @@ -22.5. Maintenance mode not working on vCenter

      Product SiteDocumentation Site

      22.5. Maintenance mode not working on vCenter

      Symptom
      +22.5. Maintenance mode not working on vCenter

      Product SiteDocumentation Site

      22.5. Maintenance mode not working on vCenter

      Symptom
      Host was placed in maintenance mode, but still appears live in vCenter. -
      Cause
      +
      Cause
      The CloudPlatform administrator UI was used to place the host in scheduled maintenance mode. This mode is separate from vCenter's maintenance mode. -
      Solution
      +
      Solution
      Use vCenter to place the host in maintenance mode. -
      More Information
      +
      More Information
      See Section 11.2, “Scheduled Maintenance and Maintenance Mode for Hosts”
      http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-recover-lost-virtual-router.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-recover-lost-virtual-router.html b/docs/tmp/en-US/html/troubleshooting-recover-lost-virtual-router.html index 8f16d7e..685f2f5 100644 --- a/docs/tmp/en-US/html/troubleshooting-recover-lost-virtual-router.html +++ b/docs/tmp/en-US/html/troubleshooting-recover-lost-virtual-router.html @@ -1,10 +1,10 @@ -22.4. Recovering a Lost Virtual Router

      Product SiteDocumentation Site

      22.4. Recovering a Lost Virtual Router

      Symptom
      +22.4. Recovering a Lost Virtual Router

      Product SiteDocumentation Site

      22.4. Recovering a Lost Virtual Router

      Symptom
      A virtual router is running, but the host is disconnected. A virtual router no longer functions as expected. -
      Cause
      +
      Cause
      The Virtual router is lost or down. -
      Solution
      +
      Solution
      If you are sure that a virtual router is down forever, or no longer functions as expected, destroy it. You must create one afresh while keeping the backup router up and running (it is assumed this is in a redundant router setup):
      • Force stop the router. Use the stopRouter API with forced=true parameter to do so. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-unable-to-deploy-vms.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-unable-to-deploy-vms.html b/docs/tmp/en-US/html/troubleshooting-unable-to-deploy-vms.html index 0f42235..c017acb 100644 --- a/docs/tmp/en-US/html/troubleshooting-unable-to-deploy-vms.html +++ b/docs/tmp/en-US/html/troubleshooting-unable-to-deploy-vms.html @@ -1,9 +1,9 @@ -22.6. Unable to deploy VMs from uploaded vSphere template

        Product SiteDocumentation Site

        22.6. Unable to deploy VMs from uploaded vSphere template

        Symptom
        +22.6. Unable to deploy VMs from uploaded vSphere template

        Product SiteDocumentation Site

        22.6. Unable to deploy VMs from uploaded vSphere template

        Symptom
        When attempting to create a VM, the VM will not deploy. -
        Cause
        +
        Cause
        If the template was created by uploading an OVA file that was created using vSphere Client, it is possible the OVA contained an ISO image. If it does, the deployment of VMs from the template will fail. -
        Solution
        +
        Solution
        Remove the ISO and re-upload the template.
        http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/troubleshooting-unable-to-power-on-vm.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/troubleshooting-unable-to-power-on-vm.html b/docs/tmp/en-US/html/troubleshooting-unable-to-power-on-vm.html index f5ad17c..2d53a1f 100644 --- a/docs/tmp/en-US/html/troubleshooting-unable-to-power-on-vm.html +++ b/docs/tmp/en-US/html/troubleshooting-unable-to-power-on-vm.html @@ -1,6 +1,6 @@ -22.7. Unable to power on virtual machine on VMware

        Product SiteDocumentation Site

        22.7. Unable to power on virtual machine on VMware

        Symptom
        +22.7. Unable to power on virtual machine on VMware

        Product SiteDocumentation Site

        22.7. Unable to power on virtual machine on VMware

        Symptom
        Virtual machine does not power on. You might see errors like:
        • Unable to open Swap File @@ -8,9 +8,9 @@ Unable to access a file since it is locked
        • Unable to access Virtual machine configuration -
        Cause
        +
      Cause
      A known issue on VMware machines. ESX hosts lock certain critical virtual machine files and file systems to prevent concurrent changes. Sometimes the files are not unlocked when the virtual machine is powered off. When a virtual machine attempts to power on, it can not access these critical files, and the virtual machine is unable to power on. -
      Solution
      +
      Solution
      See the following:
      VMware Knowledge Base Article http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/upgrade-instructions.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/upgrade-instructions.html b/docs/tmp/en-US/html/upgrade-instructions.html index 442b2d7..0068516 100644 --- a/docs/tmp/en-US/html/upgrade-instructions.html +++ b/docs/tmp/en-US/html/upgrade-instructions.html @@ -574,14 +574,14 @@ Done restarting router(s). If you would like additional confirmation that the new system VM templates were correctly applied when these system VMs were rebooted, SSH into the System VM and check the version.
      Use one of the following techniques, depending on the hypervisor. -
      XenServer or KVM:
      +
      XenServer or KVM:
      SSH in by using the link local IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own link local IP.
      Run the following commands on the XenServer or KVM host on which the system VM is present: 
      # ssh -i private-key-path link-local-ip -p 3922
 # cat /etc/cloudstack-release
      The output should be like the following: - 
      Cloudstack Release 4.0.0-incubating Mon Oct 9 15:10:04 PST 2012
      ESXi
      + 
      Cloudstack Release 4.0.0-incubating Mon Oct 9 15:10:04 PST 2012
      ESXi
      SSH in using the private IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own private IP.
      Run the following commands on the Management Server: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/html/vpn.html ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/html/vpn.html b/docs/tmp/en-US/html/vpn.html index f873ebf..59b71e1 100644 --- a/docs/tmp/en-US/html/vpn.html +++ b/docs/tmp/en-US/html/vpn.html @@ -140,7 +140,7 @@ Dead Peer Detection: 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.
  • Click OK. -
    • Updating and Removing a VPN Customer Gateway
    +
    Updating and Removing a VPN Customer Gateway
    You can update a customer gateway either with no VPN connection, or related VPN connection is in error state.
    1. Log in to the CloudStack UI as an administrator or end user. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf index c4e90e6..0beeff2 100644 Binary files a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf and b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-API_Developers_Guide-en-US.pdf differ http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf index 6d4d06b..82cdd99 100644 Binary files a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf and b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Admin_Guide-en-US.pdf differ http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/35dcda2e/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf index 82b5c89..283f880 100644 Binary files a/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf and b/docs/tmp/en-US/pdf/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf differ