Network Configuration

ZStack supports complex network scenarios. This topic lists several common network architectures according to business requirements and practical environments.
  1. LocalStorage+Flat Network
    Features of this architecture are as follows:
    • Hosts use LocalStorage to store the system disks and data disks of VM instances.
    • The RAID array technology of hosts is required to protect VM data.
    • Hosts and VM instances are in the same L2 network. Therefore, VM IP addresses and host IP addresses can ping each other.
    • This architecture supports distributed DHCP, distributed EIP, and Userdata services.
    • By default, VM online migration is not supported. But you can enable VM online migration in global settings.
    • Featuring low costs and high concurrency performance, this architecture can be applied to software development and testing environments, and the scenario where the application layer can provide high availability.
    Management Network:
    • The management network manages resources in each compute node and storage node.
    • In the preceding figure, em01 is the NIC used by the management node to communicate with the compute nodes and the backup storage.
    Business Network:
    • The business network is used by the compute nodes and the backup storage for data communication.
    • In the preceding figure, em02 is the network used for creating VM instances. If the VM network and host network are in the same network segment, the corresponding VM instances and hosts can ping each other. Note that the IP ranges of the VM network and host network cannot be overlapped when you ping the VM instances and hosts.
    • You can set VLAN or VXLAN for L2 isolation. After L2 isolation is implemented, VM instances can only be used in private networks and cannot directly access the Internet. In this case, EIPs are required to achieve network interconnection.
    Backup Storage:
    • The backup storage can use an independent server to provide services.
    • In small data centers, the backup storage can also share the same server with the management node.
  2. NAS/SAN+vRouter Network
    Features of this architecture are as follows:
    • The VM data is stored in a centralized storage, and volume data is protected by the dual-controller of the storage and the RAID technology.
    • A storage network and a centralized storage are required. We recommend that the storage network be equal to or greater than 10 Gigabit. VM instances are protected by high availability.
    • When you add a primary storage to ZStack, you can add it as NFS or Shared Mount Point primary storage.
    • This architecture sets up a storage network, supports VM high availability, and protects VM data. However, the I/O performance has bottlenecks. Therefore, we recommend that 8 to 10 compute nodes share a storage.
    • This architecture uses vRouters to provide network services such as DNS, SNAT, EIP, port forwarding, load balancing, IPsec, and security group.
    • This architecture supports distributed DHCP network.
    • This architecture requires some investments, and is suitable for traditional applications, intensive data, SLA high availability guarantee, and data security scenarios.
    Management Network:
    • The management network manages resources in each compute node and storage node.
    • In the preceding figure, em01 is the NIC used by the management node to communicate with the compute nodes and the backup storage.
    Business Network:
    • The business network is used by the compute nodes and the backup storage for data communication.
    • You can set public and private networks for the same hosts by setting VLAN. Note that the hosts are connected by the same physical cable.
    • In the preceding figure, the em02 without a VLAN tag is the public network, which can access the Internet. The em02 tagged with VLAN 10 is the private network. You need to set the switch to Trunk mode. Then, VM instances can access the Internet through the vRouter, and the vRouter network uses the vRouter to provide various network services. The default IP address of the vRouter network is the IP address of the public network.
    Note:

    If the host NICs are insufficient, you can combine the management network and business network into one.

    Storage Network:
    • The storage network is used to provide NAS and SAN storages.
    • We recommend that you use a 10 Gigabit Ethernet or Fibre Channel (FC) to accelerate storage access. In the preceding figure, em03 is dedicated to providing access to storage network traffics.
    Backup Storage:
    • The backup storage can use an independent server to provide services.
    • In small data centers, the backup storage can also share the same server with the management node.
  3. Ceph+VXLAN vRouter Network
    Features of this architecture are as follows:
    • The VM data is stored in distributed storages and protected by multiple copies or erasure coding mechanisms.
    • A storage network is required. VM instances are protected by high availability.
    • The Ceph primary storage and the Ceph backup storage use the same distributed storage.
    • This architecture sets up a storage network, and supports VM high availability and multiple copies for data. Both computing and storage can be scaled horizontally.
    • This architecture uses the VXLAN VTEP to provide L2 logical subnet. The VXLAN underlay network is accessed by VM instances.
    • This architecture uses vRouters to provide network services such as DNS, SNAT, EIP, port forwarding, load balancing, IPsec, and security group.
    • This architecture supports distributed DHCP network.
    • This architecture is suitable for renting platforms, general-purpose applications, intensive data, SLA high availability guarantee, and large scale scenarios.
    Management Network:
    • The management network manages resources in each compute node and storage node.
    • In the preceding figure, em01 is the NIC used by the management node to communicate with the compute nodes and the distributed storage nodes.
    Public Network:
    • The public network can access the Internet.
    • VM instances can access the Internet through the vRouter. The vRouter network uses the vRouter to provide various network services. The default IP address of the vRouter network is the IP address of the public network.
    • In the preceding figure, em02 is used to provide public network services. If the NICs are insufficient, you can combine the management network and the public network into one.
    VXLAN Underlay Network
    • The VXLAN underlay network is a private network used by VM instances.
    • The VXLAN underlay network is an L2 logical network based on L3 IP addresses. For example, in the preceding figure, the VTEP of 192.168.1.x/24 is used to provide the private network whose VNI is 201.
    Storage Network:
    • The storage network is used to provide distributed block storages.
    • The storage networks provides distributed block storages. We recommend that you use a 10 Gigabit Ethernet or FC to accelerate storage access.
    • In the preceding figure, em03 is the storage network. A Ceph distributed storage needs at least one Mon IP to interconnect with the management network.
  4. Ceph+VPC Network
    Features of this architecture are as follows:
    • The VM data is stored in distributed storages and protected by multiple copies or erasure coding mechanisms.
    • A storage network is required. VM instances are protected by high availability.
    • The Ceph primary storage and the Ceph backup storage use the same distributed storage.
    • This architecture sets up a storage network, and supports VM high availability and multiple copies for data. Both computing and storage can be scaled horizontally.
    • This architecture uses vRouters to provide network services such as DNS, SNAT, EIP, port forwarding, load balancing, IPsec, and security group.
    • This architecture supports distributed DHCP network.
    • This architecture is suitable for renting platforms, general-purpose applications, intensive data, SLA high availability guarantee, and large scale scenarios.
    Management Network:
    • The management network manages resources in each compute node and storage node.
    • In the preceding figure, em01 is the NIC used by the management node to communicate with the compute nodes and the backup storages of the distributed storage type.
    Business Network:
    • You can set public and private networks for the same hosts by setting VLAN. Note that the hosts are connected by the same physical cable.
    • In the preceding figure, the em02 without a VLAN tag is the public network, which can access the Internet. The em02s tagged with VLAN 10 and 20 are the private network (VPC network). You need to set the switch to Trunk mode. Then, VM instances can access the Internet through the VPC vRouter, and the VPC network uses the VPC vRouter to provide various network services. The default IP address of the VPC network is the IP address of the public network.
    Note:

    If the host NICs are insufficient, you can combine the management network and business network into one.

    Storage Network:
    • The storage network is used to provide distributed block storages.
    • The storage network provides distributed storages. We recommend that you use a 10 Gigabit Ethernet or FC to accelerate storage access.
    • In the preceding figure, em03 is the storage network. A Ceph distributed storage needs at least one Mon IP to interconnect with the management network.

Back to Top

Download

Already filled the basic info?Click here.

Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

An email with a verification code will be sent to you. Make sure the address you provided is valid and correct.

Download

Not filled the basic info yet? Click here.

Invalid email address or mobile number.

Email Us

contact@zstack.io
ZStack Training and Certification
Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

Email Us

contact@zstack.io
Request Trial
Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

Email Us

contact@zstack.io

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder. After receiving the email, click the URL to download the documentation.

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder.
Or click on the URL below. (For Internet Explorer, right-click the URL and save it.)

Thank you for using ZStack products and services.

Submit successfully.

We'll connect soon.

Thank you for using ZStack products and services.