Activity log for bug #1552952

Date Who What changed Old value New value Message
2016-03-03 23:11:36 Nischal Sheth bug added bug
2016-03-03 23:11:42 Nischal Sheth juniperopenstack: assignee Nischal Sheth (nsheth)
2016-03-03 23:11:52 Nischal Sheth nominated for series juniperopenstack/trunk
2016-03-03 23:11:52 Nischal Sheth bug task added juniperopenstack/trunk
2016-03-03 23:12:06 Nischal Sheth juniperopenstack/trunk: milestone r3.1.0.0-fcs
2016-03-03 23:19:02 Nischal Sheth description BGPaaS was implemented via bug 1518047. BGPaaS was implemented via bug 1518047. The initial implementation has a limitation that routes can only be advertised from the bgpaas-client to the bgpaas-server. Assumption is that the client has a static default route with the subnet default gateway as the nexthop. This bug tracks an enhancement to remove above limitation and allow bidirectional exchange of routes between the client and server. The server will advertise routes to the client with the bgp nexthop set to the default gateway of the subnet to which the client belongs.
2016-03-04 18:04:03 Nischal Sheth tags config contrail-control bgpaas config contrail-control
2016-03-05 05:33:21 OpenContrail Admin juniperopenstack/trunk: status New In Progress
2016-03-06 06:54:47 Nischal Sheth juniperopenstack/trunk: importance High Wishlist
2016-03-28 21:46:31 Nischal Sheth tags bgpaas config contrail-control bgpaas contrail-control
2016-03-28 22:14:51 Nischal Sheth description BGPaaS was implemented via bug 1518047. The initial implementation has a limitation that routes can only be advertised from the bgpaas-client to the bgpaas-server. Assumption is that the client has a static default route with the subnet default gateway as the nexthop. This bug tracks an enhancement to remove above limitation and allow bidirectional exchange of routes between the client and server. The server will advertise routes to the client with the bgp nexthop set to the default gateway of the subnet to which the client belongs. BGPaaS was implemented via bug 1518047. The initial implementation has a limitation that routes can only be advertised from the bgpaas-client to the bgpaas-server. Assumption is that the client has a static default route with the subnet default gateway as the nexthop. This bug tracks an enhancement to remove above limitation and allow bidirectional exchange of routes between the client and server. The server will advertise routes to the client with the bgp nexthop set to the default gateway of the subnet to which the client belongs. Config changes are tracked via bug 1563075. UI changes are tracked via bug 1558168.
2016-05-02 16:54:31 Nischal Sheth juniperopenstack/trunk: status In Progress Fix Committed