Creating a Network Topology

This case demonstrates the hybrid deployment of self-service+OVS networks. The same operations apply to self-service+LinuxBridge networks. OVS and LinuxBridge are different network type implementation mechanisms. OpenStack management and tenants are unaware of the specific network implementation mode.

The figure below shows the network topology in this case. test_selfservice_arm is the tenant network in the Arm network domain, and the network CIDR is 192.168.120.0/24. test_selfservice_x86 is the tenant network in the x86 network domain, and the network CIDR is 192.168.130.0/24. The two networks are connected through the virtual router provided by Neutron. Networks in the same AZ can communicate with each other. Networks in different AZs can communicate with each other through the routers.

Perform the following operations on the controller node.

1. Source the admin credentials to gain access to admin-only CLI commands.

   1	source /etc/keystone/admin-openrc

2. Create a self-service tenant network in the Arm AZ.

   1 2	openstack network create --availability-zone-hint az-arm test_selfservice_arm openstack subnet create --network test_selfservice_arm --gateway 192.168.120.1 --subnet-range 192.168.120.0/24 sub_selfservice_arm

3. Create a self-service tenant network in the x86 AZ.

   1 2	openstack network create --availability-zone-hint az-x86 test_selfservice_x86 openstack subnet create --network test_selfservice_x86 --gateway 192.168.130.1 --subnet-range 192.168.130.0/24 sub_selfservice_x86

4. Create a router named test_router.

   1	openstack router create --availability-zone-hint az-x86 test_router

5. Use the router to connect the two self-service tenant networks.

   1 2	openstack router add subnet test_router sub_selfservice_x86 openstack router add subnet test_router sub_selfservice_arm