Missing host parameter in neutron conf files

Bug #1406052 reported by ofer blaut
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Numan Siddique

Bug Description

Version
=======

Juno on rhel

Description
===========
When working on HA setups, we need to change host parameter in neutron.conf/L3 agent.conf
"host = " is not present in any neutron conf files , and it will be great if we can add it as a comment

ofer blaut (oblaut)
summary: - Missing host parameter in neuton.conf and L3 agent.conf
+ Missing host parameter in neutron conf files
Changed in neutron:
assignee: nobody → Numan Siddique (numansiddique)
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

I don't think it's necessary.
Default value of the parameter is host name and in most cases it even doesn't make sense to specify it.

It's not necessary to have each and every conf parameter commented in neutron.conf

Changed in neutron:
status: New → Opinion
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: Opinion → In Progress
Revision history for this message
Assaf Muller (amuller) wrote :

It's used in specific HA solutions. I figure if there's use for it, it might as well be documented. Since it's trivial and risk-free to 'close' this bug, I don't see why not. If/when we start generating conf files, it will be there in the new template.

Revision history for this message
Numan Siddique (numansiddique) wrote :

@ofer @Assaf - can you please tell what is the use case for changing the default host value in the case of HA setups ?
If host value is not defined in neutron.conf/agent.ini, then the system host name is used. Is there a need to change the default value in case of HA setups ?

Revision history for this message
Assaf Muller (amuller) wrote :

Here's a slight simplification: One approach is to install two nodes with the 4 agents (Metadata, DHCP, OVS and L3). Start the agents on only one node. Then if an external system (Say: Pacemaker) detects an issue with the first node, you configure the 2nd node with the host of the first, and start all of those agents. When they start and sync with the controller, they identify themselves using the old host, and will all of the already schedules resources (Routers, DHCP networks, ports).

Revision history for this message
Assaf Muller (amuller) wrote :

*and will configure all of the...

Revision history for this message
Numan Siddique (numansiddique) wrote :

Thank you Assaf for the explanation.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/144228
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d50595d5fae105e7c4cdb8a2b78302a6883e2033
Submitter: Jenkins
Branch: master

commit d50595d5fae105e7c4cdb8a2b78302a6883e2033
Author: Numan Siddique <email address hidden>
Date: Sun Dec 28 17:33:57 2014 +0530

    Add help text for 'host' parameter in neutron.conf file

    This patch adds the help text for 'host' parameter in
    neutron.conf which is presently missing and updates
    the neutron/common/config.py accordingly

    Change-Id: Iddfc9c44b3fae95cbae1cfe1142c3d3a92749799
    Closes-bug: #1406052

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → kilo-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: kilo-2 → 2015.1.0
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.