Configure controller node

To install the Networking components

• # apt-get install neutron-server neutron-plugin-ml2

To configure the Networking server component

The Networking server component configuration includes the database, authentication mechanism, message broker, topology change notifier, and plug-in.

1. Respond to prompts for database management, Identity service credentials, service endpoint registration, and message broker credentials.

2. Configure Networking to notify Compute about network topology changes:

   Replace SERVICE_TENANT_ID with the service tenant identifier (id) in the Identity service and NOVA_PASS with the password you chose for the nova user in the Identity service.

   1. Edit the /etc/neutron/neutron.conf file and add the following keys to the [DEFAULT] section:

      [DEFAULT]
      ...
      notify_nova_on_port_status_changes = True
      notify_nova_on_port_data_changes = True
      nova_url = http://controller:8774/v2
      nova_admin_username = nova
      nova_admin_tenant_id = SERVICE_TENANT_ID
      nova_admin_password = NOVA_PASS
      nova_admin_auth_url = http://controller:35357/v2.0

   	Note
   	To obtain the service tenant identifier (id): $ source admin-openrc.sh $ keystone tenant-get service +-------------+----------------------------------+ | Property | Value | +-------------+----------------------------------+ | description | Service Tenant | | enabled | True | | id | f727b5ec2ceb4d71bad86dfc414449bf | | name | service | +-------------+----------------------------------+

3. Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:

   1. Edit the /etc/neutron/neutron.conf file and add the following keys to the [DEFAULT] section:

      [DEFAULT]
      ...
      core_plugin = ml2
      service_plugins = router
      allow_overlapping_ips = True

      	Note
      	We recommend adding verbose = True to the [DEFAULT] section in /etc/neutron/neutron.conf to assist with troubleshooting.

4. Comment out any lines in the [service_providers] section.

To configure the Modular Layer 2 (ML2) plug-in

The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances. However, the controller node does not need the OVS agent or service because it does not handle instance network traffic.

• Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file:

  Add the following keys to the [ml2] section:

  [ml2]
  ...
  type_drivers = gre
  tenant_network_types = gre
  mechanism_drivers = openvswitch

  Add the following key to the [ml2_type_gre] section:

  [ml2_type_gre]
  ...
  tunnel_id_ranges = 1:1000

  Add the [securitygroup] section and the following keys to it:

  [securitygroup]
  ...
  firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
  enable_security_group = True

To configure Compute to use Networking

By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking.

• Edit the /etc/nova/nova.conf and add the following keys to the [DEFAULT] section:

  Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service.

  [DEFAULT]
  ...
  network_api_class = nova.network.neutronv2.api.API
  neutron_url = http://controller:9696
  neutron_auth_strategy = keystone
  neutron_admin_tenant_name = service
  neutron_admin_username = neutron
  neutron_admin_password = NEUTRON_PASS
  neutron_admin_auth_url = http://controller:35357/v2.0
  linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
  firewall_driver = nova.virt.firewall.NoopFirewallDriver
  security_group_api = neutron

  	Note
  	By default, Compute uses an internal firewall service. Since Networking includes a firewall service, you must disable the Compute firewall service by using the nova.virt.firewall.NoopFirewallDriver firewall driver.

To finalize installation

1. Restart the Compute services:

   # service nova-api restart
   # service nova-scheduler restart
   # service nova-conductor restart

2. Restart the Networking service:

   # service neutron-server restart