Chapter 2. Managing project networks

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Create a network.

   Example

   $ openstack network create my_network

   Tip

   • If you do not intend to enter the network into production immediately, you can add the --disable option to the create network command.
   • Consider naming your network for the role that the network provides. One example: webservers_122 is a network that host web servers and the VLAN ID is 122.

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the name of the network to which you want to add a subnet:

   $ openstack network list

3. Create a subnet.

   $ openstack subnet create <subnet-name> --subnet-range <CIDR> --network <name>

   • Replace <subnet-name> with the name of the subnet you are creating.

   • Replace <CIDR> with the IP address range and subnet mask in CIDR format.

     To determine the CIDR address, calculate the number of bits masked in the subnet mask and append that value to the IP address range. For example, the subnet mask 255.255.255.0 has 24 masked bits. To use this mask with the IPv4 address range 192.168.122.0, specify the address 192.168.122.0/24.

   • Replace <name> with the name of the network to which you are adding the subnet.

     Tip

     DHCP services automate the distribution of IP settings to your instances and is enabled by default. Specify --no-dhcp to diable DHCP.

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the project ID of the project where you want to create the IPv6 subnet.

   Retain this ID, because you will need it later:

   $ openstack project list

   Sample output

   +----------------------------------+----------+
   | ID                               | Name     |
   +----------------------------------+----------+
   | 25837c567ed5458fbb441d39862e1399 |    QA    |
   | f59f631a77264a8eb0defc898cb836af |  admin   |
   | 4e2e1951e70643b5af7ed52f3ff36539 |   demo   |
   | 8561dff8310e4cd8be4b6fd03dc8acf5 | services |
   +----------------------------------+----------+

3. Obtain the name of the network where you want to host the IPv6 subnet.

   Retain this name, because you will need it later:

   $ openstack network list -c Name -c Subnets --max-width=72

   Sample output

   +-------------+--------------------------------------------------------+
   | Name        | Subnets                                                |
   +-------------+--------------------------------------------------------+
   | private     | 47d34cf0-0dd2-49bd-a985-67311d80c5c4,                  |
   |             | 82014d36-9e60-43eb-92fc-74674573f4e8,                  |
   |             | d7535565-113f-4192-baa6-da21f301f141                   |
   | private2    | 7ee56cef-83c0-40d1-b4e7-5287dae1c23c                   |
   | public      | 6745edd4-d15f-4971-89bf-70307b0ad2f1,                  |
   |             | cc3f81bb-4d55-4ead-aad4-5362a7ca5b04                   |
   | lb-mgmt-net | 5ca08724-568c-4030-93eb-f2e286570a25                   |
   +-------------+--------------------------------------------------------+

4. Using the project ID and network name, create an IPv6 subnet:

   Example

   $ openstack subnet create --ip-version 6 --ipv6-address-mode \
   dhcpv6-stateful --project 25837c567ed5458fbb441d39862e1399 \
   --network private2 --subnet-range fdf8:f53b:82e4::53/125 \
   subnet_name

   Sample output

   +-------------------+--------------------------------------------------------------+
   | Field             | Value                                                        |
   +-------------------+--------------------------------------------------------------+
   | allocation_pools  | {"start": "fdf8:f53b:82e4::52", "end": "fdf8:f53b:82e4::56"} |
   | cidr              | fdf8:f53b:82e4::53/125                                       |
   | dns_nameservers   |                                                              |
   | enable_dhcp       | True                                                         |
   | gateway_ip        | fdf8:f53b:82e4::51                                           |
   | host_routes       |                                                              |
   | id                | cdfc3398-997b-46eb-9db1-ebbd88f7de05                         |
   | ip_version        | 6                                                            |
   | ipv6_address_mode | dhcpv6-stateful                                              |
   | ipv6_ra_mode      |                                                              |
   | name              |                                                              |
   | network_id        | 6aff6826-4278-4a35-b74d-b0ca0cbba340                         |
   | tenant_id         | 25837c567ed5458fbb441d39862e1399                             |
   +-------------------+--------------------------------------------------------------+

Verification

1. Validate this configuration by reviewing the network list.

   $ openstack network list -c Name -c Subnets --max-width=72

   Sample output

   Note that the entry for private2 now reflects the newly created IPv6 subnet:

   ---------------------------------------------------------------------+
   | Name        | Subnets                                                |
   ---------------------------------------------------------------------+
   | private     | 47d34cf0-0dd2-49bd-a985-67311d80c5c4,                  |
   |             | 82014d36-9e60-43eb-92fc-74674573f4e8,                  |
   |             | d7535565-113f-4192-baa6-da21f301f141                   |
   | private2    | 7ee56cef-83c0-40d1-b4e7-5287dae1c23c,                  |
   |             | cdfc3398-997b-46eb-9db1-ebbd88f7de05                   |
   | public      | 6745edd4-d15f-4971-89bf-70307b0ad2f1,                  |
   |             | cc3f81bb-4d55-4ead-aad4-5362a7ca5b04                   |
   | lb-mgmt-net | 5ca08724-568c-4030-93eb-f2e286570a25                   |
   ---------------------------------------------------------------------+

2. Create an instance, and confirm that the instance is associated with a DHCP IPv6 address when added to the private2 subnet:

   $ openstack server list -c Name -c Status -c Networks

   Sample output

   +---------+--------+-----------------------------+
   | Name    | Status | Networks                    |
   +---------+--------+-----------------------------+
   | server1 | ACTIVE | private2=fdf8:f53b:82e4::52 |
   +---------+--------+-----------------------------+

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Create a router.

   $ openstack router create <router-name> --external-gateway <network> \
   --project <name>

   • Replace <router-name> with the name of the router you are creating.
   • Replace <network> with the name of an external network.

   • Replace <name> with the name of your project.

     Tip

     If you want to create a router in an availability zone (AZ) add the --availability-zone-hint <availability-zone> option. Repeat the option to set multiple AZs.

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the virtual router name that you are using to route traffic to and from your network.

   Retain this name, because you will need it later:

   $ openstack router list

   Sample output

   +---------+--------+-------+----------------------------------+
   | Name    | Status | State | Project                          |
   +---------+--------+-------+----------------------------------+
   | router1 | ACTIVE | UP    | 24089d2fe1a94dd29ca2f665794fbe92 |
   | router2 | ACTIVE | UP    | ecf285621c509223ade3358691bbde59 |
   +---------+--------+-------+----------------------------------+

3. Obtain the name of the subnet for which you want to add an interface for your router.

   Retain this name, because you will need it later:

   $ openstack subnet list -c Name -c Network -c Subnet --max-width=72

   Sample output

   +----------------------+-------------------------+---------------------+
   | Name                 | Network                 | Subnet              |
   +----------------------+-------------------------+---------------------+
   | private_subnet24     | 317be3d3-5265-43f7-b52b | 10.0.24.0/24        |
   |                      | -930e3fd19b8b           |                     |
   | lb-mgmt-subnet       | c4588d49-9151-414b-8832 | 172.24.0.0/16       |
   |                      | -37313e3b4c57           |                     |
   | external_subnet      | bcdb3cc0-8c0b-4d2d-813c | 10.0.0.0/24         |
   |                      | -e141bb97aa8f           |                     |
   | external_ipv6_subnet | bcdb3cc0-8c0b-4d2d-813c | 2620:52:0:13b8::/64 |
   |                      | -e141bb97aa8f           |                     |
   | private_subnet       | 317be3d3-5265-43f7-b52b | 10.0.1.0/24         |
   |                      | -930e3fd19b8b           |                     |
   +----------------------+-------------------------+---------------------+

4. Using the router and subnet names, add an interface to your router for the subnet.

   Example

   In this example, private_subnet is added as an interface on router2:

   $ openstack router add subnet router2 private_subnet

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the virtual router name that contains the interface to a subnet that you want to remove.

   Retain this name, because you will need it later:

   $ openstack router list

   Sample output

   +---------+--------+-------+----------------------------------+
   | Name    | Status | State | Project                          |
   +---------+--------+-------+----------------------------------+
   | router1 | ACTIVE | UP    | 24089d2fe1a94dd29ca2f665794fbe92 |
   | router2 | ACTIVE | UP    | ecf285621c509223ade3358691bbde59 |
   +---------+--------+-------+----------------------------------+

3. Obtain the name of the subnet that you are using as the interface for your router.

   Retain this name, because you will need it later:

   $ openstack subnet list -c Name -c Network -c Subnet --max-width=72

   Sample output

   +----------------------+-------------------------+---------------------+
   | Name                 | Network                 | Subnet              |
   +----------------------+-------------------------+---------------------+
   | private_subnet24     | 317be3d3-5265-43f7-b52b | 10.0.24.0/24        |
   |                      | -930e3fd19b8b           |                     |
   | lb-mgmt-subnet       | c4588d49-9151-414b-8832 | 172.24.0.0/16       |
   |                      | -37313e3b4c57           |                     |
   | external_subnet      | bcdb3cc0-8c0b-4d2d-813c | 10.0.0.0/24         |
   |                      | -e141bb97aa8f           |                     |
   | external_ipv6_subnet | bcdb3cc0-8c0b-4d2d-813c | 2620:52:0:13b8::/64 |
   |                      | -e141bb97aa8f           |                     |
   | private_subnet       | 317be3d3-5265-43f7-b52b | 10.0.1.0/24         |
   |                      | -930e3fd19b8b           |                     |
   +----------------------+-------------------------+---------------------+

4. Using the router and subnet names, remove the interface from your router.

   Example

   In this example, private_subnet is removed as an interface on router2:

   $ openstack router remove subnet router2 private_subnet

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Using the project name, delete the project and all of the resources associated with the project:

   Example

   In this example, test-project is deleted:

   $ openstack project purge --project test-project

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the name of the router that you want to delete.

   Retain this name, because you will need it later.

   $ openstack router list -c Name -c Status -c State -c Project

   Sample output

   +---------+--------+-------+----------------------------------+
   | Name    | Status | State | Project                          |
   +---------+--------+-------+----------------------------------+
   | router1 | ACTIVE | UP    | 24089d2fe1a94dd29ca2f665794fbe92 |
   | router2 | ACTIVE | UP    | ecf285621c509223ade3358691bbde59 |
   +---------+--------+-------+----------------------------------+

3. Using the router name, delete the router.

   Example

   In this example, router2 is deleted:

   $ openstack router delete router2

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the name of the subnet that you want to delete.

   Retain this name, because you will need it later.

   $ openstack subnet list

   Sample output

   +----------------------+-------------------------+---------------------+
   | Name                 | Network                 | Subnet              |
   +----------------------+-------------------------+---------------------+
   | private_subnet24     | 317be3d3-5265-43f7-b52b | 10.0.24.0/24        |
   |                      | -930e3fd19b8b           |                     |
   | lb-mgmt-subnet       | c4588d49-9151-414b-8832 | 172.24.0.0/16       |
   |                      | -37313e3b4c57           |                     |
   | external_subnet      | bcdb3cc0-8c0b-4d2d-813c | 10.0.0.0/24         |
   |                      | -e141bb97aa8f           |                     |
   | private2_subnet      | 56e73380-a771-408f-bdc0 | 10.1.2.0/24         |
   |                      | -1e97f79677c6           |                     |
   | private_subnet2      | 317be3d3-5265-43f7-b52b | 10.0.2.0/24         |
   |                      | -930e3fd19b8b           |                     |
   | external_ipv6_subnet | bcdb3cc0-8c0b-4d2d-813c | 2620:52:0:13b8::/64 |
   |                      | -e141bb97aa8f           |                     |
   | private_subnet       | 317be3d3-5265-43f7-b52b | 10.0.1.0/24         |
   |                      | -930e3fd19b8b           |                     |
   +----------------------+-------------------------+---------------------+

3. Using the subnet name, delete the subnet.

   Example

   In this example, private_subnet24 is deleted:

   $ openstack subnet delete private_subnet24

Procedure

1. Confirm that the system OS_CLOUD variable is set for your cloud:

   $ echo $OS_CLOUD
   my_cloud

   Reset the variable if necessary:

   $ export OS_CLOUD=my_other_cloud

   As an alternative, you can specify the cloud name by adding the --os-cloud <cloud_name> option each time you run an openstack command.

2. Obtain the name of the network that you want to delete.

   Retain this name, because you will need it later.

   $ openstack network list -c Name

   Sample output

   +-------------+
   | Name        |
   +-------------+
   | my_network  |
   | private     |
   | public      |
   | lb-mgmt-net |
   +-------------+

3. Using the network name, delete the network.

   Example

   In this example, my_network is deleted:

   $ openstack network delete my_network