Open Stack

Hi Artem

Thank you for your pointing out this.
I'm still thinking about the design. Once I got the draft, I'll share
it in the bp and here..

Best
Nachi

2013/10/10 Artem Dmytrenko <nextone92 at yahoo.com>:
> Hi Rudra, Nachi.
>
> Glad to see this discussion on the mailing list! The ExtraRoute routes are
> fairly
> limited and it would be great to be able to store more complete routing
> information in Neutron. I've submitted a blueprint proposing expanding
> ExtraRoute
> parameters to include more information (extended-route-params). But it still
> has a problem where routes are stored in a list and are not indexed. So an
> update
> could be painful.
>
> Could you share what attributes would you like to see in your RIB API?
>
> Thanks!
> Artem
>
> P.S.
>  I'm OpenStack newbie, looking forward to learning from and working with
> you!
>
>>Hi Rudra
>>
>>ExtraRoute bp was designed for adding some "extra" routing for the router.
>>The spec is very handy for simple and small use cases.
>>However it won't fit large use cases, because it takes all route in a Json
>> List.
>># It means we need to send full route for updating.
>>
>>As Salvatore suggests, we need to keep backward compatibility.
>>so, IMO, we should create Routing table extension.
>>
>>I'm thinking about this in the context of L3VPN (MPLS) extension.
>>My Idea is to have a RIB API in the Neutron.
>>For vpnv4 routes it may have RT or RDs.
>>
>>Best
>>Nachi
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>