Matthew Kassawara 45e005cbd1 [install] Remove neutron workaround for Ubuntu

Remove neutron workaround for Ubuntu due to patch for
package and fix minor RST issue with code-block type.

Change-Id: Ifdfe22a4e9ed72ceb14a5259a3fd73f50a39a582
Implements: blueprint installguide-liberty

2015-10-06 18:02:09 -06:00

7.3 KiB

Raw Blame History

Install and configure compute node

The compute node handles connectivity and security groups <security group> for instances.

Prerequisites

Before you install and configure OpenStack Networking, you must kernel networking parameters to disable reverse-path filtering:

Edit the /etc/sysctl.conf file to contain the following parameters:
```
net.ipv4.conf.all.rp_filter=0
net.ipv4.conf.default.rp_filter=0
```
Implement the changes:
```
# sysctl -p
```

ubuntu or rdo or obs

Install the components

ubuntu

# apt-get install neutron-plugin-linuxbridge-agent

rdo

# yum install openstack-neutron-linuxbridge

obs

# zypper install --no-recommends openstack-neutron-linuxbridge-agent ipset

debian

Install and configure the Networking components

# apt-get install neutron-plugin-linuxbridge-agent

Respond to prompts for database management, Identity service credentials, service endpoint, and message queue credentials.
Select the ML2 plug-in:

Note

Selecting the ML2 plug-in also populates the service_plugins and allow_overlapping_ips options in the /etc/neutron/neutron.conf file with the appropriate values.

ubuntu or rdo or obs

Configure the common component

The Networking common component configuration includes the authentication mechanism, message queue, and plug-in.

Edit the /etc/neutron/neutron.conf file and complete the following actions:
- In the [database] section, comment out any connection options because compute nodes do not directly access the database.
- In the [DEFAULT] and [oslo_messaging_rabbit] sections, configure RabbitMQ message queue access:
```
[DEFAULT]
...
rpc_backend = rabbit

[oslo_messaging_rabbit]
...
rabbit_host = controller
rabbit_userid = openstack
rabbit_password = RABBIT_PASS
```
  Replace RABBIT_PASS with the password you chose for the openstack account in RabbitMQ.
- In the [DEFAULT] and [keystone_authtoken] sections, configure Identity service access:
```
[DEFAULT]
...
auth_strategy = keystone

[keystone_authtoken]
...
auth_uri = http://controller:5000
auth_url = http://controller:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = neutron
password = NEUTRON_PASS
```
  Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service.
  
  Note
  
  Comment out or remove any other options in the [keystone_authtoken] section.
- (Optional) To assist with troubleshooting, enable verbose logging in the [DEFAULT] section:
```
[DEFAULT]
...
verbose = True
```

Configure networking options

Choose the same networking option that you chose for the controller node to configure services specific to it.

Note

Option 2 augments option 1 with the layer-3 (routing) service and enables self-service (private) networks. If you want to use public (provider) and private (self-service) networks, choose option 2.

neutron-compute-install-option1.rst neutron-compute-install-option2.rst

Configure Compute to use Networking

Edit the /etc/nova/nova.conf file and complete the following actions:

In the [neutron] section, configure access parameters:

[neutron]
...
url = http://controller:9696
auth_url = http://controller:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
region_name = RegionOne
project_name = service
username = neutron
password = NEUTRON_PASS

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

Finalize installation

rdo

The Networking service initialization scripts expect a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in configuration file, /etc/neutron/plugins/ml2/ml2_conf.ini. If this symbolic link does not exist, create it using the following command:
```
# ln -s /etc/neutron/plugins/ml2/ml2_conf.ini /etc/neutron/plugin.ini
```
Due to a packaging issue, the Linux bridge agent initialization script explicitly looks for the Linux bridge plug-in configuration file rather than the agent configuration file. Run the following commands to resolve this issue:
```
# cp /usr/lib/systemd/system/neutron-linuxbridge-agent.service \
  /usr/lib/systemd/system/neutron-linuxbridge-agent.service.orig
# sed -i 's,openvswitch/linuxbridge_neutron_plugin.ini,ml2/linuxbridge_agent.ini,g' \
  /usr/lib/systemd/system/neutron-linuxbridge-agent.service
```
Note

Future upgrades of the neutron-linuxbridge-agent package may overwrite this modification.

Restart the Compute service:

# systemctl restart openstack-nova-compute.service

Start the Linux bridge agent and configure it to start when the system boots:

# systemctl enable neutron-linuxbridge-agent.service
# systemctl start neutron-linuxbridge-agent.service

obs

The Networking service initialization scripts expect the variable NEUTRON_PLUGIN_CONF in the /etc/sysconfig/neutron file to reference the ML2 plug-in configuration file. Edit the /etc/sysconfig/neutron file and add the following:
```
NEUTRON_PLUGIN_CONF="/etc/neutron/plugins/ml2/ml2_conf.ini"
```