Bug 1042480

Summary: [RFE][neutron]: Change router_id setting in dhcp and l3 agent config
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/change-router-id-setting-in-dhcp-and-l3-config
Whiteboard: upstream_milestone_none upstream_status_started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:28:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 22:24:33 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/change-router-id-setting-in-dhcp-and-l3-config.

Description:

In dhcp_agent.ini and l3_agent.ini configuration file, change namespace and router_id setting.

In Current method :

    -  When the use_namespace's value is false,  it is used such as a static value of router_id. 

        Use_namespace = False
        Route_id = qrouter-xxxxxxx

In New method :

    -  When the use_namespace's value is false,  it is used as a default router instead of static value.

        Use_namesapce = False
        #Route_id =
    
    - when I want to use a specific router instead of default, the traditional method is used. 

        Use_namesapce = False
        Route_id = qrouter-xxxxxxxxxxx


ex) default router attribute
Now in quantum, there is not a default router attribute.
When I create a router, It is created by adding a default attribute to the specific router.
When I create multiple routers, One of them is selected as a default router.
It would work such as a security group

Specification URL (additional information):

None