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 7F76CE2D6 for ; Tue, 5 Mar 2013 18:37:51 +0000 (UTC) Received: (qmail 41517 invoked by uid 500); 5 Mar 2013 18:37:41 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 41105 invoked by uid 500); 5 Mar 2013 18:37:41 -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 40023 invoked by uid 99); 5 Mar 2013 18:37:40 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Mar 2013 18:37:40 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 3AF02830245; Tue, 5 Mar 2013 18:37:40 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: bfederle@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: [18/50] [abbrv] git commit: refs/heads/ui-multiple-nics - CLOUDSTACK-313: fixing cross-references in accessing-vms.xml Message-Id: <20130305183740.3AF02830245@tyr.zones.apache.org> Date: Tue, 5 Mar 2013 18:37:40 +0000 (UTC) CLOUDSTACK-313: fixing cross-references in accessing-vms.xml Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/13c952e6 Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/13c952e6 Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/13c952e6 Branch: refs/heads/ui-multiple-nics Commit: 13c952e6153120e6cdcb24bab02c040e59ce8511 Parents: d73cd03 Author: Joe Brockmeier Authored: Sun Mar 3 22:48:21 2013 -0600 Committer: Joe Brockmeier Committed: Sun Mar 3 22:50:14 2013 -0600 ---------------------------------------------------------------------- docs/en-US/accessing-vms.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/13c952e6/docs/en-US/accessing-vms.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/accessing-vms.xml b/docs/en-US/accessing-vms.xml index ce780cf..67d9d77 100644 --- a/docs/en-US/accessing-vms.xml +++ b/docs/en-US/accessing-vms.xml @@ -32,9 +32,9 @@ To access a VM directly over the network: - The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding and Firewalling. + The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See . If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the &PRODUCT; UI and enable ssh on the machine using the commands for the VM’s operating system. - If the network has an external firewall device, you will need to create a firewall rule to allow access. See IP Forwarding and Firewalling. + If the network has an external firewall device, you will need to create a firewall rule to allow access. See .