Neutron configuration files should depend on target location

Bug #1443927 reported by Matt Kassawara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Low
Tom Cameron
Trunk
Fix Released
Low
Tom Cameron

Bug Description

Neutron configuration files should depend on target location. For example:

1) Only the server container needs the database connection string.

2) Only the agent container needs the L3, DHCP, metadata, and metering agents.

summary: - Neutron configuration files should depend on container type
+ Neutron configuration files should depend on target location
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/174035

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/174035
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=102fa9cf51b6b939418f8409e333103b3f6e74c3
Submitter: Jenkins
Branch: master

commit 102fa9cf51b6b939418f8409e333103b3f6e74c3
Author: Tom Cameron <email address hidden>
Date: Wed Apr 15 15:11:12 2015 -0400

    Perform Neutron actions based on target

    1) Only generate neutron configuration files necessary for
       each target.
    2) Limit database connection string in neutron.conf to server
       container.
    3) Limit database sync to neutron server container.

    Co-Authored-By: Matt Kassawara <email address hidden>
    Change-Id: Iba8903235675dec4e7bf6b01eeb130f7b43bbfef
    Closes-Bug: 1443927

Changed in openstack-ansible:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.