[MidoNet-dev] [config-cluster] Router_id field in Topology.Route proto

Alexandru Bikfalvi alex.bikfalvi at midokura.com
Wed Apr 15 07:55:30 UTC 2015


Now I am using both, because my understanding was that both can be sources
of distinct routes. If that's not the case, I will use only the ones which
are available. Which fields would work better for you?

On Wed, Apr 15, 2015 at 9:49 AM, Tomohiko Kimura <tomohiko at midokura.com>
wrote:

> Sorry my question was incorrect, I wanted to ask if Router.route_ids and
> Port.route_ids are being used. Do you need both be populated?
>
> Tomohiko
>
> On Wed, Apr 15, 2015 at 4:44 PM, Alexandru Bikfalvi <
> alex.bikfalvi at midokura.com> wrote:
>
>> Hi Tomohiko,
>>
>> Right now now router_id field is not used in the RouterMapper. The mapper
>> loads the routes from the Router.route_ids and Port.route_ids. However, I
>> think internally by the agent is used by the flow tagger. Therefore, if you
>> don't set it, we would need to set it inside the mapper before advertising
>> the route.
>>
>> Cheers,
>> Alex
>>
>> On Wed, Apr 15, 2015 at 9:32 AM, Tomohiko Kimura <tomohiko at midokura.com>
>> wrote:
>>
>>> Hello Alex and others
>>>
>>> Do device Mappers on the Agent side expect that the router_id field in
>>> Route proto has been populated, or do / can they look up the router from
>>> the port ID in the next_hop_port_id field? Is this being handled inside
>>> RouterMapper?
>>>
>>> Best,
>>> Tomohiko
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.midonet.org/pipermail/midonet-dev/attachments/20150415/3593b51b/attachment.html>


More information about the MidoNet-dev mailing list