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/adminguide/networking/dynamic_static_routing.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Network mode indicates the mode with which the isolated network or VPC will oper
41
41
There are two valid options
42
42
43
43
- NATTED. This is the default network mode of isolated networks. The VR of isolated networks and VPCs provides Source NAT services, as well as Static NAT, Load Balancer, Port Forwarding, Vpn if the network offering supports.
44
-
- ROUTED. For isolated networks in ROUTED mode, the VR no longer supports Source NAT, Static NAT, Load Balancer, Port Forwarding and Vpn. The supported services are Dns, Dhcp, Userdata, Firewall (for isolated networks) and Network ACL (for vpc and vpc networks).
44
+
- ROUTED. For isolated networks in ROUTED mode, the VR no longer supports Source NAT, Static NAT, Load Balancer, Port Forwarding and Vpn. The supported services are Dns, Dhcp, User data, Firewall (for isolated networks) and Network ACL (for vpc and vpc networks).
:alt:Provide userdata id or userdata with variables text dialog box
91
+
:alt:Provide userdata id or user data with variables text dialog box
92
92
93
93
These details will be saved as meta-data file(s) in both config drive and virtual router,
94
94
which in turn support jinja based instance meta-data feature of cloud-init,
95
95
refer to https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html.
96
96
97
-
These APIs also support the parameter ``userdata=`` to provide the userdata content
97
+
These APIs also support the parameter ``userdata=`` to provide the user data content
98
98
directly. The value for this parameter must be a `base64 <https://www.base64encode.org/>`_-encoded
99
99
multi-part MIME message. See further below for an example of what this should look like.
100
100
101
-
The registered UserData can be linked to a Template or ISO on registration/upload/editing
102
-
using linkUserDataToTemplate API. The same API can be used to unlink the mapping of userdata and Template.
101
+
The registered User Data can be linked to a Template or ISO on registration/upload/editing
102
+
using linkUserDataToTemplate API. The same API can be used to unlink the mapping of user data and Template.
103
103
104
-
While linking userData to a Template/ISO userdata override policy has to be specified.
104
+
While linking user Data to a Template/ISO user data override policy has to be specified.
105
105
Following are the override policies available:
106
106
107
-
Allow Override: Allow users to override UserData for the Template during instance deployment or on reset.
107
+
Allow Override: Allow users to override User Data for the Template during instance deployment or on reset.
108
108
This is the default override policy if not specified
109
109
110
-
Deny Override: Override of UserData isn’t allowed during instance deployment or on reset.
110
+
Deny Override: Override of User Data isn’t allowed during instance deployment or on reset.
111
111
112
-
Append Only: Don’t allow users to override linked UserData but allow users to pass userdata content
113
-
or ID that should be appended to the linked UserData of the Template. When the users pass userdata it is appended to the Template userdata in the form of a multipart MIME message
112
+
Append Only: Don’t allow users to override linked User Data but allow users to pass user data content
113
+
or ID that should be appended to the linked User Data of the Template. When the users pass user data it is appended to the Template user data in the form of a multipart MIME message
114
114
115
115
This is how it looks like in Template/ISO register/upload/edit forms.
0 commit comments