Creating/Deleting Networks

	Note
	When creating networks, nova-manage must be run on the host that nova-network is running on. This is different from how network creation works for other network managers. When invoking nova-manage, make sure it picks up a config file that specifies network_manager=nova.network.quantum.manager.QuantumManager

	Note
	The content in this section is specific to how Quantum integrates with Nova in the Essex (2012.1) release. In future releases, networks will be created by calling the Quantum API directly.

To create a network using Quantum Manager, run:

nova-manage network create --label=public --fixed_range_v4=8.8.8.0/24

When this command is invoked, the Quantum Manager will contact the Quantum Service to create a corresponding Quantum network, and likewise will create an IPAM subnet using the specified fixed range.

By default, networks are "global" in the sense that they are shared by all tenants (i.e. projects in Nova). To create a tenant-specific network, specify the "--project_id" argument when creating the network. For example:

nova-manage network create --label=tenant2-private --fixed_range_v4=10.0.0.0/24 --project_id=10daaef1-b481-42a6-8653-7a42e982e409

This project_id should be the tenant UUID from keystone. To view all keystone tenant UUIDs, run the following command as a keystone admin user:

keystone tenant-list

When a new VM is created, it is given a vNIC for each global network, as well as a vNIC for each network owned by the tenant associated with the VM. This lets users create hybrid scenarios where a VM has a vNIC both on a shared public network and on a private tenant-specific network.

Networks are deleted by specifying their UUID (specifying their IP range is not sufficient):

nova-manage network delete --uuid 174d677f-7d15-4d7f-9d93-43feaae25d4d