incubator-cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject git commit: refs/heads/4.1 - CLOUDSTACK-313: fixing cross-references in accessing-vms.xml
Date Mon, 04 Mar 2013 04:50:07 GMT
Updated Branches:
  refs/heads/4.1 69a41b3cc -> 55da4c99a


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/55da4c99
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/55da4c99
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/55da4c99

Branch: refs/heads/4.1
Commit: 55da4c99acc59ac3fb3ce3c38b8fe7dc4787fbc6
Parents: 69a41b3
Author: Joe Brockmeier <jzb@zonker.net>
Authored: Sun Mar 3 22:48:21 2013 -0600
Committer: Joe Brockmeier <jzb@zonker.net>
Committed: Sun Mar 3 22:49:47 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/55da4c99/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 @@
         </orderedlist>
         <para>To access a VM directly over the network:</para>
         <orderedlist>
-            <listitem><para>The VM must have some port open to incoming traffic.
For example, in a basic zone, a new VM might be assigned to a security group which allows
incoming traffic. This depends on what security group you picked when creating the VM. In
other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding
and Firewalling.</para></listitem>
+            <listitem><para>The VM must have some port open to incoming traffic.
For example, in a basic zone, a new VM might be assigned to a security group which allows
incoming traffic. This depends on what security group you picked when creating the VM. In
other cases, you can open a port by setting up a port forwarding policy. See <xref linkend="ip-forwarding-firewalling"/>.</para></listitem>
             <listitem><para>If a port is open but you can not access the VM using
ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether
ssh is enabled in the template you picked when creating the VM. Access the VM through the
&PRODUCT; UI and enable ssh on the machine using the commands for the VM’s operating
system.</para></listitem>
-            <listitem><para>If the network has an external firewall device, you
will need to create a firewall rule to allow access. See IP Forwarding and Firewalling.</para></listitem>
+            <listitem><para>If the network has an external firewall device, you
will need to create a firewall rule to allow access. See <xref linkend="ip-forwarding-firewalling"/>.</para></listitem>
         </orderedlist>
 </section>
 


Mime
View raw message