Open Stack

'host' can be in either file. It just needs to be in the "DEFAULT" section.

Your description of the floating-ips being in the wrong namespace in the
first setup sounds like a bug or a misconfiguration. I would suggest
troubleshooting that first setup because you won't find a lot of
support/documentation for multiple l3 agents per host since that isn't a
use case the Neutron devs are actively targeting/testing.

Setting 'router_id' is only for use when namespaces are disabled. It's not
meant to be used to try to influence how routers are scheduled.

On Wed, Mar 18, 2015 at 4:49 AM, Akilesh K <akilesh1597 at gmail.com> wrote:

> @Murali
> I am not trying DVR/HA. I am only doing the legacy setup. Its just that I
> wanted multiple external networks and some of them were on a different
> host. The instance was attached to several private/internal networks with
> each internal network attached to an external network through a router.
> When I assign floating-ip I noted that the nat rules were being created in
> a completely wrong namespace, which is why I decided to try out the
> multiple-l3-agent scenario, which did work but with some drawbacks that I
> had mentioned in previous mails.
>
>
> @Kevin
> I apologize for my language. I seriously want to motivate and not insult
> anyone participating in this community be it individual or corporate. May
> be Its just my thinking is wrong, but either ways I wasn't 'accusing'
> anyone. My Intention was only to urge the Individual contributors to catch
> up with the big names out there.
>
> I am running several l3-agents on same host. Its my fault not to mention
> it explicitly, but a lot of people did understand what exactly I was
> trying, except that they were on the same page as I was.
>
> Setting the router-id I believe locks an agent to a router, which is
> exactly what I want.
>
> Meanwhile I did see several posts / mails mentioning the 'host settings'
> but none of them give detailed information. The l3-agent seems to be
> consuming two options file 'neutron.conf' and 'l3-agent.ini'. Which of
> these config file should contain the option and under which group?
>
>
> Thank you,
> Ageeleshwar K
>
> On Wed, Mar 18, 2015 at 3:38 PM, Kevin Benton <blak111 at gmail.com> wrote:
>
>> First, please avoid accusing "corporate interactions" for causing a lack
>> of responses because it distracts from the question by insulting the people
>> that choose to participate in this community.
>>
>> Please provide more details because the current information you have
>> provided isn't enough to troubleshoot the issue you are encountering. What
>> do you mean by running multiple L3 agents? Are you talking about on the
>> same host? If so, that's not the recommended way to do them now that you
>> can have different external networks defined with the physnet mappings in
>> ML2.
>>
>> If you do really want to deploy multiple on the same server that way,
>> they will need different 'host' settings in their ini files. By default the
>> system's hostname is used which obviously will conflict between two agents
>> on the same system.
>>
>> If you are talking about running multiple L3 agents across different
>> hosts, then it sounds like they are sharing the same 'host' setting and in
>> that case it would be a good idea to remove that setting and allow it to
>> use the default of the system hostname (assuming each node has different
>> hostnames).
>>
>> Also, you shouldn't be setting 'router_id' in l3_agent.ini. That's for
>> restricting the agent to one router when namespaces aren't enabled.
>>
>> On Tue, Mar 17, 2015 at 10:26 PM, Akilesh K <akilesh1597 at gmail.com>
>> wrote:
>>
>>> Yes I did the same. But I've heard of people doing multiple l3 agent
>>> scenarios with success, Only that we are not getting replies. I am not sure
>>> If I am being paranoid, but I have a feeling that the community interaction
>>> these days are going down and corporate interactions are dominating.
>>>
>>> Will keep you posted, If I hit anything interesting.
>>>
>>>
>>>
>>> On Wed, Mar 18, 2015 at 12:56 AM, Rafael Barra <faelrba at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>> I've tried to work with multiple l3_agents in Juno using GRE Tunnels
>>>> for external networks without sucess. My second external network did not
>>>> work.
>>>> Then I gave up and moved to one l3_agent with flat networks for my 2
>>>> external networks.
>>>> Now everything works ok.
>>>>
>>>> Ps: I left gateway_external_network_id, router_id and
>>>> external_network_bridge empty in the l3_agent configuration file.
>>>>
>>>> 2015-03-17 10:36 GMT-03:00 Xabier Elkano <xelkano at hostinet.com>:
>>>>
>>>> El 17/03/15 a las 14:18, Antonio Messina escribió:
>>>>> > I haven't tested myself yet, but I will need to have multiple
>>>>> external
>>>>> > networks as well very soon.
>>>>> >
>>>>> > I was looking at this blogpost:
>>>>> >
>>>>> http://www.ajo.es/post/86497974174/using-multiple-external-networks-in-openstack
>>>>> Hi,
>>>>>
>>>>> I've used this method successfully with two external networks, but only
>>>>> one l3 agent.
>>>>>
>>>>> BR,
>>>>> Xabier
>>>>> >
>>>>> > Have you tried it yet?
>>>>> >
>>>>> > .a.
>>>>> >
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list:
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>> Post to     : openstack at lists.openstack.org
>>>>> Unsubscribe :
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> [ ]'s
>>>> Rafael Barra
>>>>
>>>> _______________________________________________
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>> Post to     : openstack at lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>
>>
>> --
>> Kevin Benton
>>
>
>


-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150318/63b90a03/attachment.html>