Updated Branches:
  refs/heads/4.1 f95b3c76e -> c3cdadebc

Docs: Fixed typo in nicira plugin guide


Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/c3cdadeb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/c3cdadeb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/c3cdadeb

Branch: refs/heads/4.1
Commit: c3cdadebc5caed3bbada31e66d66dd6b1c5989ae
Parents: f95b3c7
Author: Sebastien Goasguen <[email protected]>
Authored: Thu Feb 14 11:27:32 2013 +0100
Committer: Sebastien Goasguen <[email protected]>
Committed: Thu Feb 14 11:27:32 2013 +0100

----------------------------------------------------------------------
 docs/en-US/plugin-niciranvp-devicemanagement.xml |    4 ++--
 docs/en-US/plugin-niciranvp-features.xml         |    8 ++++----
 docs/en-US/plugin-niciranvp-preparations.xml     |    6 +++---
 docs/en-US/plugin-niciranvp-uuidreferences.xml   |    6 +++---
 4 files changed, 12 insertions(+), 12 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c3cdadeb/docs/en-US/plugin-niciranvp-devicemanagement.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/plugin-niciranvp-devicemanagement.xml 
b/docs/en-US/plugin-niciranvp-devicemanagement.xml
index 2423ce3..57b8eee 100644
--- a/docs/en-US/plugin-niciranvp-devicemanagement.xml
+++ b/docs/en-US/plugin-niciranvp-devicemanagement.xml
@@ -22,7 +22,7 @@
 -->
 <section id="Device-management">
     <title>Device-management</title>
-    <para>In CloudStack 4.0.x each Nicira NVP setup is considered a "device" 
that can be added and removed from a physical network. To complete the 
configuration of the Nicira NVP plugin a device needs to be added to the 
physical network using the "addNiciraNVPDevice" API call. The plugin is now 
enabled on the physical network and any guest networks created on that network 
will be provisioned using the Nicra NVP Controller.</para>
+    <para>In &PRODUCT; 4.0.x each Nicira NVP setup is considered a "device" 
that can be added and removed from a physical network. To complete the 
configuration of the Nicira NVP plugin a device needs to be added to the 
physical network using the "addNiciraNVPDevice" API call. The plugin is now 
enabled on the physical network and any guest networks created on that network 
will be provisioned using the Nicira NVP Controller.</para>
     <para>The plugin introduces a set of new API calls to manage the devices, 
see below or refer to the API reference.</para>
     <itemizedlist>
         <listitem><para>addNiciraNvpDevice</para></listitem>
@@ -44,4 +44,4 @@
         <listitem><para>listNiciraNVPDevices</para></listitem>
     </itemizedlist>    
     
-</section>
\ No newline at end of file
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c3cdadeb/docs/en-US/plugin-niciranvp-features.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/plugin-niciranvp-features.xml 
b/docs/en-US/plugin-niciranvp-features.xml
index b71e67f..c346bfb 100644
--- a/docs/en-US/plugin-niciranvp-features.xml
+++ b/docs/en-US/plugin-niciranvp-features.xml
@@ -22,12 +22,12 @@
 -->
 <section id="Features-of-the-Nicira-NVP-Plugin">
     <title>Features of the Nicira NVP Plugin</title>
-    <para>In CloudStack release 4.0.0-incubating this plugin supports the 
Connectivity service. This service is responsible for creating Layer 2 networks 
supporting the networks created by Guests. In other words when an tennant 
creates a new network, instead of the traditional VLAN a logical network will 
be created by sending the appropriate calls to the Nicira NVP Controller.</para>
+    <para>In &PRODUCT; release 4.0.0-incubating this plugin supports the 
Connectivity service. This service is responsible for creating Layer 2 networks 
supporting the networks created by Guests. In other words when an tenant 
creates a new network, instead of the traditional VLAN a logical network will 
be created by sending the appropriate calls to the Nicira NVP Controller.</para>
     <para>The plugin has been tested with Nicira NVP versions 2.1.0, 2.2.0 and 
2.2.1</para>
-    <note><para>In CloudStack 4.0.0-incubating only the XenServer hypervisor 
is supported for use in
+    <note><para>In &PRODUCT; 4.0.0-incubating only the XenServer hypervisor is 
supported for use in
             combination with Nicira NVP.</para>
-        <para>In CloudStack 4.1.0-incubating both KVM and XenServer 
hypervisors are
+        <para>In &PRODUCT; 4.1.0-incubating both KVM and XenServer hypervisors 
are
             supported.</para></note>
-    <note><para>In CloudStack 4.0.0-incubating the UI components for this 
plugin are not complete,
+    <note><para>In &PRODUCT; 4.0.0-incubating the UI components for this 
plugin are not complete,
             configuration is done by sending commands to the API.</para></note>
 </section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c3cdadeb/docs/en-US/plugin-niciranvp-preparations.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/plugin-niciranvp-preparations.xml 
b/docs/en-US/plugin-niciranvp-preparations.xml
index 86b795c..762c941 100644
--- a/docs/en-US/plugin-niciranvp-preparations.xml
+++ b/docs/en-US/plugin-niciranvp-preparations.xml
@@ -23,7 +23,7 @@
 <section id="Prerequisites">
     <title>Prerequisites</title>
     <para>Before enabling the Nicira NVP plugin the NVP Controller needs to be 
configured. Please review the NVP User Guide on how to do that. </para>
-    <para>CloudStack needs to have at least one physical network with the 
isolation method set to "STT". This network should be enabled for the Guest 
traffic type.</para>
+    <para>&PRODUCT; needs to have at least one physical network with the 
isolation method set to "STT". This network should be enabled for the Guest 
traffic type.</para>
         <note><para>The Guest traffic type should be configured with the 
traffic label that matches the name of
             the Integration Bridge on the hypervisor. See the Nicira NVP User 
Guide for more details
             on how to set this up in XenServer or KVM.</para></note>
@@ -33,6 +33,6 @@
         <listitem><para>The username to access the API</para></listitem>
         <listitem><para>The password to access the API</para></listitem>
         <listitem><para>The UUID of the Transport Zone that contains the 
hypervisors in this Zone</para></listitem>
-        <listitem><para>The UUID of the Physical Network that will used for 
the Guest networks</para></listitem>
+        <listitem><para>The UUID of the Physical Network that will be used for 
the Guest networks</para></listitem>
     </itemizedlist>
-</section>
\ No newline at end of file
+</section>

http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c3cdadeb/docs/en-US/plugin-niciranvp-uuidreferences.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/plugin-niciranvp-uuidreferences.xml 
b/docs/en-US/plugin-niciranvp-uuidreferences.xml
index c912971..cb5f1ca 100644
--- a/docs/en-US/plugin-niciranvp-uuidreferences.xml
+++ b/docs/en-US/plugin-niciranvp-uuidreferences.xml
@@ -22,9 +22,9 @@
 -->
 <section id="UUID-references">
     <title>UUID References</title>
-    <para>The plugin maintains several references in the CloudStack database 
to items created on the NVP Controller.</para>
-    <para>Every guest network this is created will have its broadcast type set 
to Lswitch and if the network is in state "Implemented", the broadcast URI will 
have the UUID of the Logical Switch that was created for this network on the 
NVP Controller.</para>
+    <para>The plugin maintains several references in the &PRODUCT; database to 
items created on the NVP Controller.</para>
+    <para>Every guest network that is created will have its broadcast type set 
to Lswitch and if the network is in state "Implemented", the broadcast URI will 
have the UUID of the Logical Switch that was created for this network on the 
NVP Controller.</para>
     <para>The Nics that are connected to one of the Logical Switches will have 
their Logical Switch Port UUID listed in the nicira_nvp_nic_map table</para>
     <note><para>All devices created on the NVP Controller will have a tag set 
to domain-account of the owner of the network, this string can be used to 
search for items in the NVP Controller.</para></note>    
     
-</section>
\ No newline at end of file
+</section>

Reply via email to