You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/plugins/netris-plugin.rst
+17-11Lines changed: 17 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,21 +22,19 @@ Introduction
22
22
The Netris Plugin introduces Netris as a network service provider in CloudStack to be able to create and manage Virtual Private Clouds (VPCs) in CloudStack, being able to orchestrate the following network functionalities:
23
23
24
24
- Network segmentation with Netris-VXLAN isolation method
25
-
- Routing between “public” IP and network segments with an ACS ROUTED mode offering
26
-
- SourceNAT, DNAT, 1:1 NAT between “public” IP and network segments with an ACS NATTED mode offering
25
+
- Routing between "public" IP and network segments with an ACS ROUTED mode offering
26
+
- SourceNAT, DNAT, 1:1 NAT between "public" IP and network segments with an ACS NATTED mode offering
27
27
- Routing between VPC network segments (tiers in ACS nomenclature)
28
-
- Access Lists (ACLs) between VPC tiers and "public" network (TCP, UDP, ICMP) both as global egress rules and “public” IP specific ingress rules.
28
+
- Access Lists (ACLs) between VPC tiers and "public" network (TCP, UDP, ICMP) both as global egress rules and "public" IP specific ingress rules.
29
29
- ACLs between VPC network tiers (TCP, UDP, ICMP)
30
-
- External load balancing – between VPC network tiers and “public” IP
30
+
- External load balancing – between VPC network tiers and "public" IP
31
31
- Internal load balancing – between VPC network tiers
@@ -62,6 +60,8 @@ The CloudStack Zone creation wizard is extended:
62
60
63
61
- A new isolation method is added for the Core zone, with Advanced networking and KVM hypervisor: NETRIS
64
62
63
+
|netris-isolation-method|
64
+
65
65
- When the NETRIS isolation method is selected, new steps are added to the zone creation wizard:
66
66
- Netris Provider: in this step the administrator must provide:
67
67
- Netris provider URL along with an internal name for reference
@@ -75,19 +75,25 @@ The CloudStack Zone creation wizard is extended:
75
75
76
76
.. |Public IP Pool| image:: /_static/images/netris-sysvm-vr-ip-range.png
77
77
78
+
|Public IP Pool|
79
+
78
80
- Netris IP Pool: Administrators must provide the Public IP range to be used by VPC operations: Source NAT, Load Balancing, Port Forwarding, Static NAT (this range is marked with the tag 'netris')
79
81
80
82
.. |Netris Public IP Pool| image:: /_static/images/netris-public-ip-pool.png
81
83
84
+
|Netris Public IP Pool|
85
+
82
86
- When a new zone is being created, CloudStack will check the Public IP ranges defined and will perform the following actions on Netris:
83
87
- Create an IPAM allocation for the Netris IP Pool range linked to the default VPC.
84
88
- If an existing IPAM allocation contains the Netris IP Pool provided, then the range must be created as a new IPAM subnet as a child entity of the existing allocation on Netris, with purpose: 'common'. The 'common' subnet purpose allows creating 'nat' and 'load-balancer' child subnets.
85
89
86
-
..note::
87
-
Please note CloudStack expects the public IP ranges defined in the same order as the zone wizard creation displays them. The same order must be preserved in case of adding/editing/removing public IP ranges:
88
-
- System VM Public Range
89
-
- VRs Public Range
90
-
- Netris Public Range
90
+
.. note::
91
+
**Important:**
92
+
Please note CloudStack expects the public IP ranges defined in the same order as the zone wizard creation displays them. The same order must be preserved in case of adding/editing/removing public IP ranges:
93
+
94
+
- System VM Public Range
95
+
- VRs Public Range
96
+
- Netris Public Range
91
97
92
98
The subsequent steps of zone creation remain unchanged and once the zone is successfully created and enabled, the system VMs come up with IPs from the Public IP Range reserved for System VMs (not the Netris public IP range).
0 commit comments