This is the second part of configuring neutron (Networking) on Ubuntu 14.04, you can go through previous article on Configure Neutron #1, in which we have installed and configured Networking components on Controller node.
Here, in this tutorial we will install and configure Compute Node.
To start with, Install the components on compute node.
# apt-get install neutron-plugin-linuxbridge-agent conntrack
Configure Compute Node:
Lets do some command configuration includes the authentication mechanism, message queue, and plug-in
Edit the /etc/neutron/neutron.conf file.
# nano /etc/neutron/neutron.conf
Make appropriate changes to the file.
[DEFAULT] ... rpc_backend = rabbit auth_strategy = keystone verbose = True [oslo_messaging_rabbit] ... rabbit_host = controller rabbit_userid = openstack rabbit_password = password ## Replace "password" with the password you chose for the openstack account in RabbitMQ. [keystone_authtoken] ... auth_uri = https://controller:5000 auth_url = https://controller:35357 auth_plugin = password project_domain_id = default user_domain_id = default project_name = service username = neutron password = password ## Replace "password" with the password you chose for the neutron user in the Identity service. ## Commentout other authentication details. [database] #connection = sqlite:////var/lib/neutron/neutron.sqlite ## Comment out any connection options because compute nodes do not directly access the database.
Configure the Linux bridge agent:
Since we are using Self-service networks, we need to configure Linux bridge agent on a Compute node. The Linux bridge agent makes layer-2 virtual networking infrastructure for instances which includes VXLAN tunnels for private networks and handles security groups.
Edit the /etc/neutron/plugins/ml2/linuxbridge_agent.ini file.
# nano /etc/neutron/plugins/ml2/linuxbridge_agent.ini
Make changes to the file.
[linux_bridge] physical_interface_mappings = public:eth1 ## Replace "eth1" with the name of the physical public facing network interface. [vxlan] enable_vxlan = True local_ip = 192.168.12.22 l2_population = True ## Replace "192.168.12.22" with the management ip-address of compute node. [agent] ... prevent_arp_spoofing = True [securitygroup] ... enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
Configure Compute to use Networking:
Edit the /etc/nova/nova.conf file.
# nano /etc/nova/nova.conf
Do the changes on the file like below.
[neutron] url = https://controller:9696 auth_url = https://controller:35357 auth_plugin = password project_domain_id = default user_domain_id = default region_name = RegionOne project_name = service username = neutron password = password ## Replace "password" with the password you chose for the neutron user in the Identity service.
Finalize installation:
Restart the Compute service:
# service nova-compute restart
Restart the Linux bridge agent:
# service neutron-plugin-linuxbridge-agent restart
Verify:
List agents to verify successful launch of the neutron agents, run this command on the Controller node.
# neutron agent-list +--------------------------------------+--------------------+--------------------------+-------+----------------+---------------------------+ | id | agent_type | host | alive | admin_state_up | binary | +--------------------------------------+--------------------+--------------------------+-------+----------------+---------------------------+ | 02030132-55f1-4136-8b47-7b495b66c672 | L3 agent | controller.itzgeek.local | :-) | True | neutron-l3-agent | | 6b2fd77d-8b23-4932-8010-6436bf01319c | Metadata agent | controller.itzgeek.local | :-) | True | neutron-metadata-agent | | 9324094a-878c-4ba2-b822-7b070268deec | DHCP agent | controller.itzgeek.local | :-) | True | neutron-dhcp-agent | | cac6003d-b25a-4b1f-8144-1ae0293f26b0 | Linux bridge agent | compute.itzgeek.local | :-) | True | neutron-linuxbridge-agent | | faec1d38-5b5a-4c46-a614-4db12b4ff9e6 | Linux bridge agent | controller.itzgeek.local | :-) | True | neutron-linuxbridge-agent | +--------------------------------------+--------------------+--------------------------+-------+----------------+---------------------------+
You should see the above output with four agents on the controller node and one agent on each compute node.