Skip to content

Commit 1e93510

Browse files
committed
Updating docs to match new images / api params
1 parent a1b0c3c commit 1e93510

15 files changed

+300
-860
lines changed

source/adminguide/backup_and_recovery.rst

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
KIND, either express or implied. See the License for the
1313
specific language governing permissions and limitations
1414
under the License.
15-
15+
1616
About Backup And Recovery
1717
--------------------------
1818

@@ -41,7 +41,7 @@ Backup and recovery has been designed to support two modes:
4141
- Adhoc and user scheduled backups
4242

4343
'SLA' based backups are ones where the Cloud provider (ie the root admin) controls the time, and frequency of a backup scheme.
44-
A user signs up for a 'Gold' offering, which might give them a RPO of 12 hours and the last 14 backups kept; however the user would not be
44+
A user signs up for a 'Gold' offering, which might give them a RPO of 12 hours and the last 14 backups kept; however the user would not be
4545
allowed to perform additional backups nor set the exact time that these backups took place. The user might be charged
4646
a fix rate for these backups regardless of the size of the backups.
4747

@@ -89,7 +89,7 @@ backups. Users can list and consume the imported backup offerings, only root adm
8989
delete offerings.
9090

9191
Supported APIs:
92-
~~~~~~~~~~~~~~~~
92+
~~~~~~~~~~~~~~~~
9393

9494
- **listBackupProviders**: lists available backup provider plugins
9595
- **listBackupProviderOfferings**: lists external backup policy/offering from a provider
@@ -109,18 +109,18 @@ To import a backup provider offering;
109109
#. Enter your user-friendly name and description and select the applicable zone. The External ID will then be populated with the
110110
template jobs which CloudStack retrieves from the connected provider.
111111

112-
|B&R-backup_offering_policy.jpg| |B&R-backup_offering.jpg|
112+
|B&R-backup_offering_policy.png| |B&R-backup_offering.png|
113113

114114
Creating VM Backups
115115
---------------------
116116

117117
SLA/Policy Based backups
118118
~~~~~~~~~~~~~~~~~~~~~~~~~
119119

120-
With the backup and recovery feature enabled for a zone, users simply add and
120+
With the backup and recovery feature enabled for a zone, users simply add and
121121
remove a VM from a backup offering.
122122

123-
|B&R-assignOffering.jpg|
123+
|B&R-assignOffering.png|
124124

125125
Adhoc and Scheduled Backups
126126
~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -133,16 +133,16 @@ allowed to add/remove volumes similar to VM snapshots.
133133
To trigger an adhoc backup of a VM, navigate to the instance and click on the 'Create Backup'
134134
icon.
135135

136-
|B&R-createBackup.jpg|
136+
|B&R-createBackup.png|
137137

138138
To setup a recurring backup schedule, navigate to the instance and click on the 'Backup Schedule'
139139
icon.
140140

141-
|B&R-BackupSchedule.jpg|
141+
|B&R-BackupSchedule.png|
142142

143143
Then set the time and frequency of the backups, click 'Configure' and then 'Close'
144144

145-
|B&R-BackupScheduleEntry.jpg|
145+
|B&R-BackupScheduleEntry.png|
146146

147147
Restoring VM Backups
148148
---------------------
@@ -169,21 +169,21 @@ Supported APIs:
169169
- **restoreVolumeFromBackup**: restore and attach a backed-up volume (of a VM backup) to a specified VM.
170170

171171

172-
.. |B&R-assignOffering.jpg| image:: /_static/images/B&R-assignOffering.jpg
172+
.. |B&R-assignOffering.png| image:: /_static/images/B&R-assignOffering.png
173173
:alt: Assigning an SLA/Policy to a VM.
174174
:width: 400 px
175-
.. |B&R-backup_offering_policy.jpg| image:: /_static/images/B&R-backup_offering_policy.jpg
175+
.. |B&R-backup_offering_policy.png| image:: /_static/images/B&R-backup_offering_policy.png
176176
:alt: Importing an SLA/Policy offering.
177177
:width: 300 px
178-
.. |B&R-backup_offering.jpg| image:: /_static/images/B&R-backup_offering.jpg
178+
.. |B&R-backup_offering.png| image:: /_static/images/B&R-backup_offering.png
179179
:alt: Importing a template backup offering.
180180
:width: 300 px
181-
.. |B&R-createBackup.jpg| image:: /_static/images/B&R-createBackup.jpg
181+
.. |B&R-createBackup.png| image:: /_static/images/B&R-createBackup.png
182182
:alt: Triggering an adhoc backup for a VM.
183183
:width: 400 px
184-
.. |B&R-BackupSchedule.jpg| image:: /_static/images/B&R-BackupSchedule.jpg
184+
.. |B&R-BackupSchedule.png| image:: /_static/images/B&R-BackupSchedule.png
185185
:alt: Creating a backup schedule for a VM.
186186
:width: 400 px
187-
.. |B&R-BackupScheduleEntry.jpg| image:: /_static/images/B&R-BackupScheduleEntry.jpg
187+
.. |B&R-BackupScheduleEntry.png| image:: /_static/images/B&R-BackupScheduleEntry.png
188188
:alt: Creating a backup schedule for a VM.
189189
:width: 400px

source/adminguide/networking.rst

Lines changed: 31 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ account. Isolated networks have the following properties.
5959
- The network offering can be upgraded or downgraded but it is for the
6060
entire network
6161

62-
For more information, see `“Configure Guest Traffic in an Advanced Zone”
62+
For more information, see `“Configure Guest Traffic in an Advanced Zone”
6363
<networking_and_traffic.html#configure-guest-traffic-in-an-advanced-zone>`_.
6464

6565

@@ -84,7 +84,7 @@ Basic zones in CloudStack 3.0.3 and later versions.
8484

8585
- Source NAT per zone is not supported in Shared Network when the
8686
service provider is virtual router. However, Source NAT per account
87-
is supported. For information, see `“Configuring a Shared Guest
87+
is supported. For information, see `“Configuring a Shared Guest
8888
Network” <networking_and_traffic.html#configuring-a-shared-guest-network>`_.
8989

9090

@@ -93,7 +93,7 @@ L2 Networks
9393

9494
L2 networks provide network isolation without any other services. This
9595
means that there will be no virtual router. It is assumed that the end
96-
user will have their own IPAM in place, or that they will statically assign
96+
user will have their own IPAM in place, or that they will statically assign
9797
IP addresses.
9898

9999
- L2 networks can be created by the end users, however network offerings
@@ -107,7 +107,7 @@ IP addresses.
107107

108108
Example GUI dialog box (for a regular user account) is shown below:
109109

110-
|L2-networks-gui.JPG|
110+
|L2-networks-gui.png|
111111

112112

113113
Runtime Allocation of Virtual Network Resources
@@ -124,8 +124,8 @@ helps to conserve network resources.
124124
Network Service Providers
125125
-------------------------
126126

127-
.. note::
128-
For the most up-to-date list of supported network service providers,
127+
.. note::
128+
For the most up-to-date list of supported network service providers,
129129
see the CloudStack UI or call `listNetworkServiceProviders`.
130130

131131
A service provider (also called a network element) is hardware or
@@ -179,8 +179,8 @@ offering.
179179
Network Offerings
180180
-----------------
181181

182-
.. note::
183-
For the most up-to-date list of supported network services, see the
182+
.. note::
183+
For the most up-to-date list of supported network services, see the
184184
CloudStack UI or call listNetworkServices.
185185

186186
A network offering is a named set of network services, such as:
@@ -220,12 +220,12 @@ running a web server farm and require a scalable firewall solution, load
220220
balancing solution, and alternate networks for accessing the database
221221
backend.
222222

223-
.. note::
224-
If you create load balancing rules while using a network service
225-
offering that includes an external load balancer device such as
226-
NetScaler, and later change the network service offering to one that
227-
uses the CloudStack virtual router, you must create a firewall rule
228-
on the virtual router for each of your existing load balancing rules
223+
.. note::
224+
If you create load balancing rules while using a network service
225+
offering that includes an external load balancer device such as
226+
NetScaler, and later change the network service offering to one that
227+
uses the CloudStack virtual router, you must create a firewall rule
228+
on the virtual router for each of your existing load balancing rules
229229
so that they continue to function.
230230

231231
When creating a new virtual network, the CloudStack administrator
@@ -298,9 +298,9 @@ To create a network offering:
298298
following supported services:
299299

300300
.. cssclass:: table-striped table-bordered table-hover
301-
301+
302302
=================== ============================================================================ ============= =============
303-
Supported Services Description Isolated Shared
303+
Supported Services Description Isolated Shared
304304
=================== ============================================================================ ============= =============
305305
DHCP For more information, see `“DNS and Supported Supported
306306
DHCP” <networking_and_traffic.html#dns-and-dhcp>`_.
@@ -340,7 +340,7 @@ To create a network offering:
340340
system service offering and any custom system service offerings
341341
that have been defined by the CloudStack root administrator.
342342

343-
For more information, see `“System Service Offerings”
343+
For more information, see `“System Service Offerings”
344344
<service_offerings.html#system-service-offerings>`_.
345345

346346
- **LB Isolation**: Specify what type of load balancer isolation you
@@ -371,7 +371,7 @@ To create a network offering:
371371
balancing traffic to the load balancer behind it. The load
372372
balancer in this case will not have the direct access to the
373373
public network.
374-
374+
375375
- **Side by Side**: In side by side mode, a firewall device is
376376
deployed in parallel with the load balancer device. So the traffic
377377
to the load balancer public IP is not routed through the firewall,
@@ -386,7 +386,7 @@ To create a network offering:
386386

387387
- Elastic IP is enabled.
388388

389-
For information on Elastic IP, see `“About Elastic IP”
389+
For information on Elastic IP, see `“About Elastic IP”
390390
<networking/elastic_ips.html>`_.
391391

392392
- **Redundant router capability**: Available only when Virtual
@@ -409,10 +409,10 @@ To create a network offering:
409409
the conserve mode is on, you can define more than one service on
410410
the same public IP.
411411

412-
.. note::
413-
If StaticNAT is enabled, irrespective of the status of the
414-
conserve mode, no port forwarding or load balancing rule can be
415-
created for the IP. However, you can add the firewall rules by
412+
.. note::
413+
If StaticNAT is enabled, irrespective of the status of the
414+
conserve mode, no port forwarding or load balancing rule can be
415+
created for the IP. However, you can add the firewall rules by
416416
using the createFirewallRule command.
417417

418418
- **Tags**: Network tag to specify which physical network to use.
@@ -428,21 +428,21 @@ To create a network offering:
428428
guest network, rules are added to allow the specified traffic.
429429

430430
- **Public**: Indicate whether the network offering should be available to
431-
all domains or only some domains. Choose Yes to make it available to
431+
all domains or only some domains. Choose Yes to make it available to
432432
all domains. Choose No to limit the scope to one or more domains.
433433

434434
- **Domain**: This is only visible When ‘Public’ is unchecked. When visible,
435-
this controls the domains which will be able to use this network offering.
436-
A multi-selection list box will be displayed. One or more domains can be
437-
selected from this list box by holding down the control key and selecting
435+
this controls the domains which will be able to use this network offering.
436+
A multi-selection list box will be displayed. One or more domains can be
437+
selected from this list box by holding down the control key and selecting
438438
the desired domains.
439439

440-
- **Zone**: This controls which zones a network offering is available in.
441-
‘All zones’ or only specific zones can be selected. One or more zones can be
442-
selected from this list box by holding down the control key and selecting
440+
- **Zone**: This controls which zones a network offering is available in.
441+
‘All zones’ or only specific zones can be selected. One or more zones can be
442+
selected from this list box by holding down the control key and selecting
443443
the desired zones.
444444

445445
#. Click Add.
446446

447-
.. |L2-networks-gui.JPG| image:: /_static/images/L2-networks-gui.JPG
447+
.. |L2-networks-gui.png| image:: /_static/images/L2-networks-gui.png
448448
:alt: Creating L2 network from GUI

source/adminguide/networking/multiple_subnets_in_shared_network.rst

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
KIND, either express or implied. See the License for the
1313
specific language governing permissions and limitations
1414
under the License.
15-
15+
1616
1717
Multiple Subnets in Shared Network
1818
----------------------------------
@@ -90,7 +90,11 @@ Adding Multiple Subnets to a Shared Network
9090
- **Start IP/ End IP**: A range of IP addresses that are accessible
9191
from the Internet and will be allocated to guest VMs. Enter the
9292
first and last IP addresses that define a range that CloudStack
93-
can assign to guest VMs .
93+
can assign to guest VMs.
94+
95+
- **VLAN/VNI**: the ID or VID of the VLAN. If not specified, will be
96+
defaulted to the vlan of the network or if vlan of the network is
97+
null - to Untagged
9498

9599
#. Click OK.
96100

source/adminguide/networking/remote_access_vpn.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The VPN user database is shared across all the VPNs created by the
3333
account owner. All VPN users get access to all VPNs created by the
3434
account owner.
3535

36-
.. note::
36+
.. note::
3737
Make sure that not all traffic goes through the VPN. That is, the route
3838
installed by the VPN should be only for the guest network and not for
3939
all traffic.
@@ -85,7 +85,9 @@ To enable VPN for a particular network:
8585

8686
#. Click one of the displayed IP address names.
8787

88-
#. Click the Enable VPN button. |vpn-icon.png|
88+
#. Click the VPN Tab
89+
90+
#. Click the Enable Remote Access VPN. |vpn-icon.png|
8991

9092
The IPsec key is displayed in a popup window.
9193

source/adminguide/networking/site_to_site_vpn.rst

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The supported endpoints on the remote datacenters are:
2626

2727
- CloudStack virtual routers
2828

29-
.. note::
29+
.. note::
3030
In addition to the specific Cisco and Juniper devices listed above, the
3131
expectation is that any Cisco or Juniper device running on the supported
3232
operating systems are able to establish VPN connections.
@@ -48,7 +48,7 @@ To set up a Site-to-Site VPN connection, perform the following:
4848
Creating and Updating a VPN Customer Gateway
4949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5050

51-
.. note::
51+
.. note::
5252
A VPN customer gateway can be connected to only one VPN gateway at a time.
5353

5454
To add a VPN Customer Gateway:
@@ -79,7 +79,7 @@ To add a VPN Customer Gateway:
7979
authenticate the customer gateway and the VPC VPN gateway to each
8080
other. The sequence cannot contain a newline or double-quote.
8181

82-
.. note::
82+
.. note::
8383
The IKE peers (VPN end points) authenticate each other by
8484
computing and sending a keyed hash of data that includes the
8585
Preshared key. If the receiving peer is able to create the same
@@ -92,7 +92,7 @@ To add a VPN Customer Gateway:
9292
AES256, and 3DES. Authentication is accomplished through the
9393
Preshared Keys.
9494

95-
.. note::
95+
.. note::
9696
The phase-1 is the first phase in the IKE process. In this initial
9797
negotiation phase, the two VPN endpoints agree on the methods to
9898
be used to provide security for the underlying IP traffic. The
@@ -112,7 +112,7 @@ To add a VPN Customer Gateway:
112112
within phase-2. The supported encryption algorithms are AES128,
113113
AES192, AES256, and 3DES.
114114

115-
.. note::
115+
.. note::
116116
The phase-2 is the second phase in the IKE process. The purpose of
117117
IKE phase-2 is to negotiate IPSec security associations (SA) to
118118
set up the IPSec tunnel. In phase-2, new keying material is
@@ -132,7 +132,7 @@ To add a VPN Customer Gateway:
132132
of the key exchanges increase as the DH groups grow larger, as
133133
does the time of the exchanges.
134134

135-
.. note::
135+
.. note::
136136
When PFS is turned on, for every negotiation of a new phase-2 SA
137137
the two gateways must generate a new set of phase-1 keys. This
138138
adds an extra layer of protection that PFS adds, which ensures if
@@ -154,6 +154,9 @@ To add a VPN Customer Gateway:
154154
regular intervals. It's recommended to have the same configuration
155155
of DPD on both side of VPN connection.
156156

157+
- **Force UDP Encapsulation of ESP Packets**: Force Encapsulation for
158+
NAT traversal
159+
157160
#. Click OK.
158161

159162

0 commit comments

Comments
 (0)