Controller Node |
Runs the Networking service, Identity
Service, and Compute services that are
required to deploy VMs (nova-api,
nova-scheduler, for
example). The node must have at least one
network interface, which is connected to the
Management Network. The host name is
controller, which every
other node resolves to the IP of the
controller node.
The nova-network service
should not be running. This is replaced by the OpenStack Networking component,
neutron.
To delete a network, run this command:
# nova-manage network delete --help
Usage: nova-manage network delete <args> [options]
Options:
-h, --help show this help message and exit
--fixed_range=<x.x.x.x/yy>
Network to delete
--uuid=<uuid> UUID of network to delete
Note that a network must first be disassociated from a project
using the nova network-disassociate command before it can be
deleted.
|
Compute Node |
Runs the Networking L2 agent and the
Compute services that run VMs (nova-compute
specifically, and optionally other nova-* services
depending on configuration). The node must have at
least two network interfaces. The first
communicates with the controller node through the
management network. The second interface handles
the VM traffic on the data network. The VM can
receive its IP address from the DHCP agent on this
network. |
Network Node |
Runs Networking L2 agent and the DHCP agent. The
DHCP agent allocates IP addresses to the VMs on
the network. The node must have at least two
network interfaces. The first communicates with
the controller node through the management
network. The second interface handles the VM
traffic on the data network. |
Router |
Router has IP 30.0.0.1, which is the default
gateway for all VMs. The router must be able to
access public networks. |