For security and stability reasons, we recommend that you deploy
an independent management network and separate it from the
public networks.
The management network we mentioned here is the same as that in
ZStack Private
Cloud. That is,
the management network is the network used to manage hosts,
primary storages, and backup storages. If a management network
was created before, you can use it directly.
Stop DHCP server: Choose whether
to enable the DHCP service.
Note:
By default, this checkbox is not selected, indicating that the
DHCP service is enabled, and IP addresses will be automatically
allocated to VM instances. In this case, you can customize a
DHCP IP address, or let the system randomly specify a DHCP IP
address.
If selected, the DHCP service will be disabled, indicating that
VM instances that use this network cannot obtain IP addresses
automatically, and need to be configured manually with IP
addresses. In this case, you cannot customize the DHCP IP
address. In addition, the system cannot randomly specify a DHCP
IP address.
If you create an L3 network and enable the
DHCP service for the first time, or if you add the
first IP range for the L3 network of the enabled
DHCP service, you can customize the DHCP IP
address.
If the L3 network has a DHCP IP address, you
cannot customize the DHCP IP address when you add
an IP range.
The DHCP IP address can be included or
excluded on the added IP range. However, the DHCP
IP address must be within the CIDR to which the
added IP range belongs, and must not be
occupied.
The IP range specified within the start IP
address and end IP address cannot contain IP
addresses of the link-local address
(169.254.0.0/16).
If not specified, the system will randomly
specify an IP address within the IP range that you
added.
In the navigation pane of the ZStack Private
Cloud UI, choose Network Resource > vRouter Resource > vRouter Image. On the vRouter Image page, click Add
vRouter Image. On the displayed Add vRouter
Image page, set the following parameters:
Name: Enter a name for the vRouter image.
Description: Optional. Enter a description for the
vRouter image.
Backup Storage: Select a backup storage to store the
vRouter image, for example, BS-1.
Image URL: Enter a local URL or upload a local
file.
URL: Enter the path that can download the
vRouter image.
Note:
ZStack provides you with dedicated vRouter
images. Download the latest vRouter images from ZStack Official Website.
Local file: Upload a vRouter image file that
can directly be accessed by the current browser.
Note:
vRouter images can be uploaded to an ImageStore or Ceph
backup storage.
A local browser will serve as a transmission relay used
for uploading vRouter images. Make sure that you do not
refresh or stop the current browser, and do not stop
your management node. Or otherwise, you will fail to add
a vRouter image.
Click OK. Then, a vRouter image will be
added, as shown in Add vRouter Image.Figure 6. Add vRouter Image
Create a vRouter offering.
In the navigation pane of the ZStack Private
Cloud UI, choose Network Resource > vRouter Resource > vRouter Offering. On the vRouter Offering page, click
Create vRouter Offering. On the displayed
Create vRouter Offering page, set the following
parameters:
Name: Enter a name for the vRouter offering.
Description: Optional. Enter a description for the
vRouter offering.
CPU: Set the CPU count for the vRouter offering. In
an actual production environment, we recommend that the CPU count must be
greater than 8.
Memory: Set the memory size for the vRouter offering.
Unit: M | G | T. In an actual production environment, we recommend that the
memory size must be greater than 8 G.
Image: Select the vRouter image that you
added.
Note: If the L3 public network in the vRouter offering has an IP
range with the IPv6 type, when you create a VPC vRouter, you must use
the vRouter image of version 3.10.0 and later.
Management Network: Select the L3 management network
that you created from the network list.
L3 Network: Select an L3 network that you created
from the network list, including public network and flat network.
If the L3 network is a public network, the vRouter or VPC vRouter
created from this vRouter offering can provide various network
services for vRouter networks and VPC networks.
If the L3 network is a public network, the vRouter created from this
vRouter offering can provide load balancing network services for
flat networks.
If the L3 network is a flat network, the vRouter created from this
vRouter offering can provide load balancing network services for
flat networks.
Click OK. Then, a vRouter offering will be
created, as shown in Create vRouter Offering.Figure 7. Create vRouter Offering
Stop DHCP server: Choose whether
to enable the DHCP service.
Note:
By default, this checkbox is not selected, indicating that the
DHCP service is enabled, and IP addresses will be automatically
allocated to VM instances. In this case, you can customize a
DHCP IP address, or let the system randomly specify a DHCP IP
address.
If selected, the DHCP service will be disabled, indicating that
VM instances that use this network cannot obtain IP addresses
automatically, and need to be configured manually with IP
addresses. In this case, you cannot customize the DHCP IP
address. In addition, the system cannot randomly specify a DHCP
IP address.
网络类型选择云路由网络
云路由规格:选择已创建的云路由规格
添加网络段:选择CIDR方式
CIDR:192.168.10.0/24
DHCP服务IP:可选项,可按需设置DHCP服务IP
Note:
If you create an L3 network and enable the
DHCP service for the first time, or if you add the
first network range for the L3 network of the
enabled DHCP service, you can customize the DHCP
IP address.
If the L3 network has a DHCP IP address, you
cannot customize the DHCP IP address when you add
the IP range.
The DHCP IP address can be included or
excluded on the IP range that you added. However,
the DHCP IP address must not be in conflict with
the current CIDR.
If not specified, the system will randomly
specify an IP address within the added IP
range.
The first IP address in a CIDR is deemed as a
gateway by default, and cannot serve as a DHCP IP
address.