Public Network

System Network

Private Network

A private network is known as a business network or an access network. Generally, VM instances use the private network. The private network is specified as the network used by VM instances, and supports three network architecture models: flat network, vRouter network, and VPC network.

Specific Network Scenarios

• Management Network
  A management network is a type of a system network, which can be used for managing and controlling the corresponding physical resources.

  • For example, when you access a host, a backup storage, a primary storage, and other resources that require an IP address, use the management network.
  • When you create vRouters or VPC vRouters, you need an IP address that can be interconnected between management networks in vRouters or VPC vRouters. With this IP address, you can deploy an agent and obtain messages returned by the agent.
• Storage Network

  A storage network is the network specified by the shared storage. You can use the storage network to check the health state of a VM instance. We recommend that you plan for an independent storage network in advance to avoid potential risks.

• VDI Network

  When you create clusters, you can specify CIDR for the VDI network. In the VDI scenario, the network traffics generated by the protocol communication between server side and client side use the VDI network. If you do not make any configuration to the VDI network, notice that the management network will be used by default.

• Migration Network

  When you create clusters, you can specify CIDR for the migration network, which can be used for VM migrations. If you do not make any configuration to the migration network, notice that the management network will be used for VM migrations.

• Image Synchronization Network
  An image synchronization network is the network that images can be synchronized among backup storages with the ImageStore type in the same management node.

  • If you have deployed an independent network for synchronizing images, you can specify CIDR for the image synchronization network.
  • If you do not make any configuration to the image synchronization network, the management network will be used by default.
  • If you set both source image store and target image store as the image synchronization network, only the target image store can take effect.
• Data Network
  A data network is the network where data can transfer between a compute node and a backup storage.

  • If you use an independent data network, you can avoid network congestion, and improve the data transfer rate.
  • If you do not make any configuration to the data network, the management network will be used by default.
• Backup Network
  ZStack Cloud provides backup services, which are add-on licensed features. A backup network is the network where you can back up your local VM instances, volumes, or databases to the local backup storage. Also, the backup network is the network where you can restore the local backup data from the local backup storage.

  • If you deploy an independent network for local backups, you can specify CIDR for the backup network.
  • If you use an independent network, you can avoid network congestion and improve the data transfer rate.
  • If you do not make any configuration to the backup network, note that the management network will be used for local backup by default.

  Note:

  Backup Service is a separate feature module. To use this feature, purchase both the Base License and the Plus License of Backup Service. The Plus License cannot be used independently.

• Traffic Network

  A traffic network is the specified network of a port mirroring, which can be used to mirror the network traffic in the NIC to remote access. In addition, the traffic network cannot act as other networks, and cannot be used to create VM instances.

Notice

• When you create VM instances, you can specify multiple networks. That is, you can specify multiple flat networks, vRouter networks, VPC networks, or a combination of flat networks, vRouter networks, and VPC networks.
• We support multi-layer networks. In addition, the L2 networks of multi-layer networks can intercommunicate. Therefore, you need to pay a special attention to avoid the conflict of IP address spaces.
• You can create multiple L3 networks by using an L2 network. If the L2 network is the HarewareVxlanNetwork type, the private network that you created can only support the flat network and other corresponding network services rather than vRouter network.

Properties

Sample

{
    "inventories": [
        {
            "category": "Private",
            "createDate": "Nov 2, 2017 1:21:40 PM",
            "dns": [
                "223.5.5.5"
            ],
            "ipRanges": [
                {
                    "createDate": "Nov 2, 2017 1:21:41 PM",
                    "endIp": "10.141.74.100",
                    "gateway": "10.141.0.1",
                    "l3NetworkUuid": "a0190782ed35439b92959844c96a7323",
                    "lastOpDate": "Nov 2, 2017 1:21:41 PM",
                    "name": "l3-bp",
                    "netmask": "255.255.0.0",
                    "networkCidr": "10.141.0.1/16",
                    "startIp": "10.141.74.1",
                    "uuid": "954f7884656e48a395a022935569b65d"
                }
            ],
            "l2NetworkUuid": "8f6a39152a72439b9ece210154de0339",
            "lastOpDate": "Nov 2, 2017 1:21:40 PM",
            "name": "l3-bp",
            "networkServices": [
                {
                    "l3NetworkUuid": "a0190782ed35439b92959844c96a7323",
                    "networkServiceProviderUuid": "a903477ad67746e8a4f773c5e28b5884",
                    "networkServiceType": "SecurityGroup"
                },
                {
                    "l3NetworkUuid": "a0190782ed35439b92959844c96a7323",
                    "networkServiceProviderUuid": "a963ab4a76384a4ab3b88fb39ef627fc",
                    "networkServiceType": "Eip"
                },
                {
                    "l3NetworkUuid": "a0190782ed35439b92959844c96a7323",
                    "networkServiceProviderUuid": "a963ab4a76384a4ab3b88fb39ef627fc",
                    "networkServiceType": "DHCP"
                },
                {
                    "l3NetworkUuid": "a0190782ed35439b92959844c96a7323",
                    "networkServiceProviderUuid": "a963ab4a76384a4ab3b88fb39ef627fc",
                    "networkServiceType": "Userdata"
                }
            ],
            "state": "Enabled",
            "system": false,
            "type": "L3BasicNetwork",
            "uuid": "a0190782ed35439b92959844c96a7323",
            "zoneUuid": "e59b71e99d8a4ea1952b578388b8cd1d"
        }
    ],
    "success": true
}

State

DNS Domain

A DNS domain is used to expand hostnames of VM instances on the L3 network to Full Qualified Domain Names (FQDNs). For example, if the hostname of a VM instance is vm1 and the DNS domain of the L3 network is zstack.org, the final hostname of the VM instance will be expanded to vm1.zstack.org.

IP Range

The current ZStack version supports only IPv4 IP range.

{
    "inventories": [
        {
            "createDate": "Oct 30, 2017 3:59:06 PM",
            "endIp": "10.141.250.100",
            "gateway": "10.141.0.1",
            "l3NetworkUuid": "54bc8bea439a49dc82acbe302da05c66",
            "lastOpDate": "Oct 30, 2017 3:59:06 PM",
            "name": "L3-Flat",
            "netmask": "255.255.0.0",
            "networkCidr": "10.141.0.1/16",
            "startIp": "10.141.250.1",
            "uuid": "f0b8e83e4dc646c69c7f9a0ff53b6367"
        }
    ],
    "success": true
}

DNS

An L3 network can have one or more DNS take effect when the DNS network service is enabled.

L2 Network and L3 Network

Similar to a layer 2 broadcast domain that can contain multiple subnets, you can create multiple L3 networks on the same L2 network. However, these L3 networks are not isolated from each other, and can be listened, which might be a potential risk.

L3 Network Service Reference

Network service reference denotes the network services enabled on the L3 network and their service providers.

{
    "inventories": [
        {
            "l3NetworkUuid": "cdb7f3151c50453ba0e8c89356e250f6",
            "networkServiceProviderUuid": "a903477ad67746e8a4f773c5e28b5884",
            "networkServiceType": "SecurityGroup"
        },
        {
            "l3NetworkUuid": "cdb7f3151c50453ba0e8c89356e250f6",
            "networkServiceProviderUuid": "a963ab4a76384a4ab3b88fb39ef627fc",
            "networkServiceType": "Userdata"
        },
        {
            "l3NetworkUuid": "cdb7f3151c50453ba0e8c89356e250f6",
            "networkServiceProviderUuid": "a963ab4a76384a4ab3b88fb39ef627fc",
            "networkServiceType": "DHCP"
        }
    ],
    "success": true
}

Address Pool Inventory

{
  "inventories": [
    {
      "l3NetworkUuid": "81ce7828f3f63c0ea8a69dd9139bdaa0",
      "name": "Test-IPRange",
      "networkCidr": "192.168.10.0/24",
      "ipRangeType": "AddressPool"
    }
  ]
}

Parameters

Note:

• When you create an L3 network in ZStack Cloud, you can specify the port mirroring network by adding the mirrorNetwork option to SystemTags.
  • Format of the mirrorNetwork option: mirrorNetwork::{L3NetworkVOUuid}
  • Example: mirrorNetwork::1c707a63817b4f29b1235fa1f76c0ccc

Parameters

Primitive Fields of Query

See L3 Network Inventory.

Nested and Expanded Fields of Query

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Note:

• When you add an IP range in ZStack Cloud, you can specify the DHCP server address by adding the DhcpServer option to SystemTags.
  • Format of the DhcpServer option: flatNetwork::DhcpServer::{%s}::ipUuid::{%s}
  • Example: flatNetwork::DhcpServer::192.168.1.100::ipUuid::null

Parameters

Primitive Fields of Query

See IP Range Inventory.

Nested and Expanded Fields of Query

Parameters

Parameters

Note:

• When you add an IP range by specifying a network CIDR in ZStack Cloud, you can specify the DHCP server address by adding the affinityGroup option to SystemTags.
  • Format of the affinityGroup option: flatNetwork::DhcpServer::{%s}::ipUuid::{%s}
  • Example: flatNetwork::DhcpServer::192.168.1.100::ipUuid::null

Parameters

Parameters

Parameters

Parameters

Parameters

Note:

• When you add an IPv6 range in ZStack Cloud, you can specify the DHCP server address by adding the affinityGroup option to SystemTags.
  • Format of the affinityGroup option: flatNetwork::DhcpServer::{%s}::ipUuid::{%s}
  • Example: flatNetwork::DhcpServer::192.168.1.100::ipUuid::null

Parameters

Note:

• When you add an IPv6 range by specifying a network CIDR in ZStack Cloud, you can specify the DHCP server address by adding the affinityGroup option to SystemTags.
  • Format of the affinityGroup option: flatNetwork::DhcpServer::{%s}::ipUuid::{%s}
  • Example: flatNetwork::DhcpServer::192.168.1.100::ipUuid::null

Primitive Fields of Query

See IP Address Inventory.

Nested And Expanded Fields of Query

Parameters

Primitive Fields of Query

See Address Pool Inventory.

Nested and Expanded Fields of Query

L3 Network Tag

CreateUserTag resourceType=L3NetworkVO tag=web-tier-l3 \
resourceUuid=f6be73fa384a419986fc6d1b92f95be9

IP Range Tag

CreateUserTag resourceType=IpRangeVO tag=web-tier-IP \
resourceUuid=8191d946954940428b7d003166fa641e

IP Address Tag

CreateUserTag resourceType=IpAddressVO tag=web-tier-IPAddress \
resourceUuid=c0af96be01703fab84495059d3188230