Skip to content

Commit 6dab9a8

Browse files
author
radhikap
committed
CLOUDSTACK-4565 review comments on network section has been fixed
1 parent acc35a1 commit 6dab9a8

5 files changed

Lines changed: 99 additions & 67 deletions

File tree

‎docs/en-US/Release_Notes.xml‎

Lines changed: 28 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -222,26 +222,26 @@ under the License.
222222
policy.</para>
223223
</section>
224224
<section id="rbd-primary-storage">
225-
<title>Snaphotting, backups, cloning and System VMs for RBD Primary Storage</title>
226-
<note>
227-
<para>These new RBD features require at least librbd 0.61.7 (Cuttlefish) and libvirt 0.9.14
228-
on the KVM hypervisors.</para>
229-
</note>
230-
<para>With this release &PRODUCT; will leverage the features of RBD format 2. This allows
231-
snapshotting and backing up those snapshots.</para>
232-
<para>Backups of snapshots to Secondary Storage are full copies of the RBD snapshot,
233-
they are not RBD diffs. This because when restoring a backup of a snapshot it is not mandatory
234-
that this backup is deployed on RBD again, it could also be a NFS Primary Storage.</para>
235-
<para>Another key feature of RBD format 2 is cloning and with this release templates will
236-
be copied to Primary Storage once and using the cloning mechanism new disks will be cloned
237-
from this parent template. This saves space and decreases deployment time for Instances
238-
dramatically.</para>
239-
<para>Before this release a NFS Primary Storage was still required for running the System VMs
240-
from. The reason behind this was a so called 'patch disk' which was generated by the hypervisor
241-
which contained metadata for the System VM. The scripts generating this disk didn't support
242-
RBD and thus System VMs had to be deployed from NFS. With 4.2 instead of the patch disk a
243-
VirtIO serial console is used to pass meta information to System VMs. This enabled the deployment
244-
of System VMs on RBD Primary Storage.</para>
225+
<title>Snaphotting, backups, cloning and System VMs for RBD Primary Storage</title>
226+
<note>
227+
<para>These new RBD features require at least librbd 0.61.7 (Cuttlefish) and libvirt
228+
0.9.14 on the KVM hypervisors.</para>
229+
</note>
230+
<para>With this release &PRODUCT; will leverage the features of RBD format 2. This allows
231+
snapshotting and backing up those snapshots.</para>
232+
<para>Backups of snapshots to Secondary Storage are full copies of the RBD snapshot, they
233+
are not RBD diffs. This because when restoring a backup of a snapshot it is not mandatory
234+
that this backup is deployed on RBD again, it could also be a NFS Primary Storage.</para>
235+
<para>Another key feature of RBD format 2 is cloning and with this release templates will be
236+
copied to Primary Storage once and using the cloning mechanism new disks will be cloned
237+
from this parent template. This saves space and decreases deployment time for Instances
238+
dramatically.</para>
239+
<para>Before this release a NFS Primary Storage was still required for running the System
240+
VMs from. The reason behind this was a so called 'patch disk' which was generated by the
241+
hypervisor which contained metadata for the System VM. The scripts generating this disk
242+
didn't support RBD and thus System VMs had to be deployed from NFS. With 4.2 instead of
243+
the patch disk a VirtIO serial console is used to pass meta information to System VMs.
244+
This enabled the deployment of System VMs on RBD Primary Storage.</para>
245245
</section>
246246
</section>
247247
<section id="issues-fixed-4.2">
@@ -408,6 +408,14 @@ under the License.
408408
</row>
409409
</thead>
410410
<tbody>
411+
<row>
412+
<entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-2709"
413+
>CLOUDSTACK-2709</ulink></para></entry>
414+
<entry>
415+
<para>VM Migration across VMware clusters which are added with different switches
416+
(Standard Swith,Vmware DVS, Cisco Nexus 1000v) is not supported..</para>
417+
</entry>
418+
</row>
411419
<row>
412420
<entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-4207"
413421
>CLOUDSTACK-4207</ulink></para></entry>
@@ -1290,7 +1298,6 @@ service cloudstack-agent start
12901298
<para><command># apt-get update</command></para>
12911299
<para><command># apt-get upgrade cloud-*</command></para>
12921300
</listitem>
1293-
12941301
<listitem>
12951302
<para>Edit <filename>/etc/cloudstack/agent/agent.properties</filename> to change the
12961303
resource parameter from

‎docs/en-US/change-network-offering-on-guest-network.xml‎

Lines changed: 45 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -20,34 +20,49 @@
2020
KIND, either express or implied. See the License for the
2121
specific language governing permissions and limitations
2222
under the License.
23-
-->
23+
-->
2424
<section id="change-network-offering-on-guest-network">
25-
<title>Changing the Network Offering on a Guest Network</title>
26-
<para>A user or administrator can change the network offering that is associated with an existing guest network.</para>
27-
<itemizedlist>
28-
<listitem><para>Log in to the &PRODUCT; UI as an administrator or end user. </para></listitem>
29-
<listitem><para>If you are changing from a network offering that uses the &PRODUCT; virtual router to one
30-
that uses external devices as network service providers, you must first stop all the
31-
VMs on the network.
32-
<phrase condition="install">See "Stopping and Starting Virtual Machines" in the Administrator's Guide.</phrase>
33-
<phrase condition="admin">See <xref linkend="stopping-and-starting-vms"/>.</phrase></para></listitem>
34-
<listitem><para>In the left navigation, choose Network.</para></listitem>
35-
<listitem><para>Click the name of the network you want to modify.</para></listitem>
36-
<listitem><para>In the Details tab, click Edit.<inlinemediaobject>
37-
<imageobject>
38-
<imagedata fileref="./images/edit-icon.png"/>
39-
</imageobject>
40-
<textobject>
41-
<phrase>EditButton.png: button to edit a network</phrase>
42-
</textobject>
43-
</inlinemediaobject></para></listitem>
44-
<listitem><para>In Network Offering, choose the new network offering, then click Apply.</para></listitem>
45-
<listitem><para>A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you
46-
know that if you change the network offering, the CIDR will be affected. Choose No
47-
to proceed with the change.</para></listitem>
48-
<listitem><para>Wait for the update to complete. Don’t try to restart VMs until the network change is
49-
complete.</para></listitem>
50-
<listitem><para>If you stopped any VMs, restart them.</para></listitem>
51-
</itemizedlist>
52-
</section>
53-
25+
<title>Changing the Network Offering on a Guest Network</title>
26+
<para>A user or administrator can change the network offering that is associated with an existing
27+
guest network.</para>
28+
<orderedlist>
29+
<listitem>
30+
<para>Log in to the &PRODUCT; UI as an administrator or end user. </para>
31+
</listitem>
32+
<listitem>
33+
<para>If you are changing from a network offering that uses the &PRODUCT; virtual router to
34+
one that uses external devices as network service providers, you must first stop all the VMs
35+
on the network. See <xref linkend="stopping-and-starting-vms"/>.</para>
36+
</listitem>
37+
<listitem>
38+
<para>In the left navigation, choose Network.</para>
39+
</listitem>
40+
<listitem>
41+
<para>Click the name of the network you want to modify.</para>
42+
</listitem>
43+
<listitem>
44+
<para>In the Details tab, click Edit.<inlinemediaobject>
45+
<imageobject>
46+
<imagedata fileref="./images/edit-icon.png"/>
47+
</imageobject>
48+
<textobject>
49+
<phrase>EditButton.png: button to edit a network</phrase>
50+
</textobject>
51+
</inlinemediaobject></para>
52+
</listitem>
53+
<listitem>
54+
<para>In Network Offering, choose the new network offering, then click Apply.</para>
55+
<para>A prompt is displayed asking whether you want to keep the existing CIDR. This is to let
56+
you know that if you change the network offering, the CIDR will be affected.</para>
57+
<para>If you upgrade between virtual router as a provider and an external network device as
58+
provider, acknowledge the change of CIDR to continue, so choose Yes.</para>
59+
</listitem>
60+
<listitem>
61+
<para>Wait for the update to complete. Don’t try to restart VMs until the network change is
62+
complete.</para>
63+
</listitem>
64+
<listitem>
65+
<para>If you stopped any VMs, restart them.</para>
66+
</listitem>
67+
</orderedlist>
68+
</section>

‎docs/en-US/guest-traffic.xml‎

Lines changed: 14 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,20 @@
2323
-->
2424
<section id="guest-traffic">
2525
<title>Guest Traffic</title>
26-
<para>A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address.</para>
27-
<para>This figure illustrates a typical guest traffic setup:</para>
28-
<mediaobject>
29-
<imageobject>
30-
<imagedata fileref="./images/guest-traffic-setup.png" />
31-
</imageobject>
32-
<textobject><phrase>Depicts a guest traffic setup.</phrase></textobject>
33-
</mediaobject>
34-
<para>The Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router has three network interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual router. Its eth2 interface is assigned a public IP address for public traffic.</para>
26+
<para>A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address.</para>
27+
<para>See a typical guest traffic setup given below:</para>
28+
<mediaobject>
29+
<imageobject>
30+
<imagedata fileref="./images/guest-traffic-setup.png" />
31+
</imageobject>
32+
<textobject><phrase>guest-traffic-setup.png: Depicts a guest traffic setup</phrase></textobject>
33+
</mediaobject>
34+
<para>The Management Server automatically creates a virtual router for each network. A virtual
35+
router is a special virtual machine that runs on the hosts. Each virtual router in an isolated
36+
network has three network interfaces. If multiple public VLAN is used, the router will have
37+
multiple public interfaces. Its eth0 interface serves as the gateway for the guest traffic and
38+
has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the
39+
virtual router. Its eth2 interface is assigned a public IP address for public traffic.</para>
3540
<para>The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses.</para>
3641
<para>Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs</para>
3742
</section>

‎docs/en-US/pvlan.xml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -223,15 +223,15 @@
223223
<listitem>
224224
<para><emphasis role="bold">IP Range</emphasis>: A range of IP addresses that are
225225
accessible from the Internet and are assigned to the guest VMs.</para>
226-
<para>If one NIC is used, these IPs should be in the same CIDR in the case of
227-
IPv6.</para>
226+
<!--<para>If one NIC is used, these IPs should be in the same CIDR in the case of
227+
IPv6.</para> -->
228228
</listitem>
229-
<listitem>
229+
<!-- <listitem>
230230
<para><emphasis role="bold">IPv6 CIDR</emphasis>: The network prefix that defines the
231231
guest network subnet. This is the CIDR that describes the IPv6 addresses in use in the
232232
guest networks in this zone. To allot IP addresses from within a particular address
233233
block, enter a CIDR.</para>
234-
</listitem>
234+
</listitem> -->
235235
<listitem>
236236
<para><emphasis role="bold">Network Domain</emphasis>: A custom DNS suffix at the level
237237
of a network. If you want to assign a special domain name to the guest VM network,

‎docs/en-US/site-to-site-vpn.xml‎

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,17 @@
33
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
44
%BOOK_ENTITIES;
55
]>
6+
67
<!-- Licensed to the Apache Software Foundation (ASF) under one
78
or more contributor license agreements. See the NOTICE file
89
distributed with this work for additional information
910
regarding copyright ownership. The ASF licenses this file
1011
to you under the Apache License, Version 2.0 (the
1112
"License"); you may not use this file except in compliance
1213
with the License. You may obtain a copy of the License at
14+
1315
http://www.apache.org/licenses/LICENSE-2.0
16+
1417
Unless required by applicable law or agreed to in writing,
1518
software distributed under the License is distributed on an
1619
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
@@ -25,6 +28,10 @@
2528
establishing a VPN connection to the virtual router of the account from a device in the
2629
datacenter of the enterprise. Having this facility eliminates the need to establish VPN
2730
connections to individual VMs.</para>
31+
<para>The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each
32+
other, for example, connecting a branch office network to a company headquarters network. In a
33+
site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP
34+
traffic through a VPN gateway.</para>
2835
<para>The supported endpoints on the remote datacenters are: </para>
2936
<itemizedlist>
3037
<listitem>
@@ -39,6 +46,7 @@
3946
that any Cisco or Juniper device running on the supported operating systems are able to
4047
establish VPN connections.</para>
4148
</note>
49+
<para></para>
4250
<para> To set up a Site-to-Site VPN connection, perform the following:</para>
4351
<orderedlist>
4452
<listitem>
@@ -55,9 +63,6 @@
5563
<para>Create VPN connection from the VPC VPN gateway to the customer VPN gateway.</para>
5664
</listitem>
5765
</orderedlist>
58-
<note><para>Appropriate events are generated on the &PRODUCT; UI when status of a Site-to-Site VPN
59-
connection changes from connected to disconnected, or vice versa. Currently no events are generated
60-
when establishing a VPN connection fails or pending.</para></note>
6166
<xi:include href="create-vpn-customer-gateway.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
6267
<xi:include href="create-vpn-gateway-for-vpc.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
6368
<xi:include href="create-vpn-connection-vpc.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>

0 commit comments

Comments
 (0)