{"push_id":813966446,"size":1,"distinct_size":1,"ref":"refs/heads/stable/kilo","head":"f1faf0e11430f1bef1d4380c9e5be58e190686cf","before":"b90a35526e891aa9445770c22c12687c13e29a6f","commits":[{"sha":"f1faf0e11430f1bef1d4380c9e5be58e190686cf","author":{"email":"133874ce6cc820a0a30d35948414286b663ea511@gmail.com","name":"Ivar Lazzaro"},"message":"rmd and ipd to support proxy_group extension\n\nAs part of the traffic stitching plumber effort, the resource mapping\ndriver, as well as the IPD, are now able to support the proxy_group\nextension. Whenever a group gets proxied by another one, all its\nL3P interfaces get detached and attached to the proxy instead.\nL2 Proxies will have the same subnet as the proxied PTG but can't\nshare the same L2P! L3 Proxies will have their subnets allocated\nthrough the proxy_ip_pool integrated in the L3P.\n\nA gateway Policy Target can be created using the proxy_gateway\nattribute in order to tell the L3P how to reach the original Group\nby using router and subnet extra routes.\nHow the gateway PT is used is deferred to a third party (user or\nTScP).\n\nPartially implements blueprint node-centric-chain-plugin\n\n(cherry picked from commit 1ffd4ee7ab74ab608f2dcba74d7e983a3bc4111e)\n\nChange-Id: I75d35e488ef50869710d55e6dbf335fda35aa72b","distinct":true,"url":"https://api.github.com/repos/stackforge/group-based-policy/commits/f1faf0e11430f1bef1d4380c9e5be58e190686cf"}]}