Add Creating Network Offerings section to fix broken cross-reference that prevented docs from building. This section was already in the repo, but was not previously included in any book file. Removed stray reference to obsolete version number.

This commit is contained in:
Jessica Tomechak 2013-02-05 05:07:56 -08:00
parent 48691bae66
commit 66baa512ad
2 changed files with 3 additions and 3 deletions

View File

@ -138,7 +138,7 @@
&PRODUCT; default system service offering and any custom system service
offerings that have been defined by the &PRODUCT; root administrator.
For more information, see System Service Offerings.</para></listitem>
<listitem><para><emphasis role="bold">Redundant router capability</emphasis>. (v3.0.3 and greater) Available
<listitem><para><emphasis role="bold">Redundant router capability</emphasis>. Available
only when Virtual Router is selected as the Source NAT provider. Select this
option if you want to use two virtual routers in the network for
uninterrupted connection: one operating as the master virtual router and the
@ -160,7 +160,7 @@
<listitem><para><emphasis role="bold">Tags</emphasis>. Network tag to specify which physical network to
use.</para></listitem>
</itemizedlist></listitem>
<listitem><para>Click Add.</para></listitem>
<listitem><para>Click Add.</para></listitem>
</orderedlist>

View File

@ -42,5 +42,5 @@
<note><para>If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the &PRODUCT; virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function.</para></note>
<para>When creating a new virtual network, the &PRODUCT; administrator chooses which network offering to enable for that network. Each virtual network is associated with one network offering. A virtual network can be upgraded or downgraded by changing its associated network offering. If you do this, be sure to reprogram the physical network to match.</para>
<para>&PRODUCT; also has internal network offerings for use by &PRODUCT; system VMs. These network offerings are not visible to users but can be modified by administrators.</para>
<xi:include href="creating-network-offerings.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>