openstack-manuals/doc/install-guide/source/neutron-compute-install.rst
Matthew Kassawara 5ee72cfa36 [install] Fix various minor problems
Fix the following minor problems to reduce work after
stable/liberty branching:

1) RDO: Revert Python MySQL library from PyMySQL to MySQL-python
   due to lack of support for the former.
2) RDO: Explicitly install 'ebtables' and 'ipset' packages due
   to dependency problems.
3) General: Change numbered list to bulleted list for lists with
   only one item.
4) General: Restructure horizon content to match other services.
   More duplication of content, but sometimes RST conditionals
   are terrible and distro packages should use the same
   configuration files.
5) General: Restructure NoSQL content to match SQL content.
6) General: Improve clarity of NTP content.

Change-Id: I2620250aa27c7d41b525aa2646ad25e0692140c4
Closes-Bug: #1514760
Closes-Bug: #1514683
Implements: bp installguide-liberty
2015-11-13 07:49:53 -07:00

6.3 KiB

Install and configure compute node

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

ubuntu or rdo or obs

Install the components

ubuntu

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

rdo

# yum install openstack-neutron openstack-neutron-linuxbridge ebtables ipset

obs

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

debian

Install and configure the Networking components

  1. # apt-get install neutron-plugin-linuxbridge-agent
  2. Respond to prompts for database management, Identity service credentials, service endpoint, and message queue credentials.

  3. Select the ML2 plug-in:

    Neutron plug-in selection dialog

    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.

    rdo

    • In the [oslo_concurrency] section, configure the lock path:

      [oslo_concurrency]
      ...
      lock_path = /var/lib/neutron/tmp
    • (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

  1. 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
  2. Restart the Compute service:

    # systemctl restart openstack-nova-compute.service
  3. 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

  1. 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"
  2. Restart the Compute service:

    # systemctl restart openstack-nova-compute.service
  3. Start the Linux Bridge agent and configure it to start when the system boots:

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

ubuntu or debian

  1. Restart the Compute service:

    # service nova-compute restart
  2. Restart the Linux bridge agent:

    # service neutron-plugin-linuxbridge-agent restart