<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<style>
font{
line-height: 1.5;
}
</style>
<div style="font-family:"微软雅黑"; font-size: 13px; color:#000000; line-height:1.5;">
<div>
Hi all.</div><div><br></div><div><div>Before routed network, functions in [1] are used to manage</div><div>network segment. Routed network introduces a plugin [2] to manage</div><div>network segment. So, now there are 2 code paths to do the same job.</div><div>Except <span style="line-height: 1.5;">in ml2, t</span><span style="line-height: 1.5;">he segments plugin will be used to manage network segments.</span></div><div><span style="line-height: 1.5;"><br></span></div><div><span style="line-height: 1.5;">Patch [3] [4] will make ml2 use segments plugin to create/delete segments.</span></div><div><span style="line-height: 1.5;">This </span><span style="line-height: 1.5;">makes code simple and fixes the conflict issue mentioned in [4]. Since</span></div><div>ml2 always uses segments, it brings the requirement to make segments</div><div>plugin always be available. Or else, the segments plugin needs to be constructed</div><div>when used.</div><div><br></div><div>I made this patch [5] to set segments plugin as default plugin.</div><div><br></div><div><div>[1] neutron.db.segments_db</div><div>[2] neutron.services.segments.plugin</div><div>[3] https://review.openstack.org/#/c/317358/</div><div>[4] https://review.openstack.org/#/c/359147/</div></div><div>[5] https://review.openstack.org/#/c/363527/</div><div><br></div></div><div>
--<br>
<div id="ntes-pcmail-signature">
<style type="text/css">
a#ntes-pcmail-signature-default:hover {
text-decoration: underline;
color: #3593db;
cursor: pointer;
}
</style>
<div style="font-size:14px; padding: 0; margin:0;">
HongHui Xiao</div>
</div><br>
</div>
</div>
<br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span></body>
</html>