{"push_id":594040286,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9b40581c2530cb5e6819d2601289265012e6601c","before":"73208f78523f18fe68e12683e5772bf1dc79f382","commits":[{"sha":"4ede11a4127a5c2cba65e87b6b23d498934d5fb7","author":{"email":"458bba2e4a8704776b33478100c98529b639cd9e@valinux.co.jp","name":"YAMAMOTO Takashi"},"message":"ofagent: Switch to flow-based tunneling\n\nSwitch from port-based tunneling to flow-based tunneling.\nThis would improve scalability as a single vport per\nnetwork_type is enough even when there are a ton of tunnel\npeers.\n\nThis commit makes ofagent use some of NXMs.  Namely, tun_ipv4_src\nand tun_ipv4_dst.  While the use of NXMs contradicts with one of\ngoals of ofagent, i.e. portablity to other switch implementations,\nit isn't a problem right now because tunnel port support is\nOVS-dependant anyway.  There are no widely implemented standards\ncovering tunnel port managements.\n\nImplements: blueprint ofagent-flow-based-tunneling\nChange-Id: I7e4b226c56bc549fe2feb1b0afab03cd63f3c589","distinct":true,"url":"https://api.github.com/repos/stackforge/networking-ofagent/commits/4ede11a4127a5c2cba65e87b6b23d498934d5fb7"},{"sha":"9b40581c2530cb5e6819d2601289265012e6601c","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"ofagent: Switch to flow-based tunneling\"","distinct":true,"url":"https://api.github.com/repos/stackforge/networking-ofagent/commits/9b40581c2530cb5e6819d2601289265012e6601c"}]}