<div dir="ltr">Since the patches for layer 3 networking automation has been merged, I think we'd better include the patches for resource cleaning in the tagged branch. Here is the list:<div><br></div><div>Floating ip deletion: <a href="https://review.openstack.org/354604">https://review.openstack.org/354604</a></div><div>Subnet cleaning: <a href="https://review.openstack.org/355847">https://review.openstack.org/355847</a></div><div>Router cleaning: <a href="https://review.openstack.org/360848">https://review.openstack.org/360848</a></div><br><div class="gmail_quote"><div dir="ltr">Shinobu Kinjo <<a href="mailto:shinobu.kj@gmail.com">shinobu.kj@gmail.com</a>>于2016年9月20日周二 下午12:04写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This announcement should have been first to avoid any unnecessary work -;<br>
<br>
On Tue, Sep 20, 2016 at 12:51 PM, joehuang <<a href="mailto:joehuang@huawei.com" target="_blank">joehuang@huawei.com</a>> wrote:<br>
> Hello, as the Trio2o repository has been established, it's time for us to<br>
> discuss the freeze date and tagging(newton branch) for the last release of<br>
> Tricircle with gateway function.<br>
><br>
> The freeze date is the gate for patches to be merged before tagging(newton<br>
> branch). If a patch can't finish review process before the freeze date, and<br>
> not able to be merged in Tricircle, then it's suggested to be handled like<br>
> this:<br>
><br>
> 1. If it's networking automation related patch, continue the review process<br>
> in Tricircle after tagging(newton branch), will be merged in Tricircle trunk<br>
> in the future .<br>
><br>
> 2. If it's gateway related patch, abandon the patch, re-submit the patch in<br>
> Trio2o.<br>
><br>
> 3. If it's patch about pod management, for it's common feature, so continue<br>
> the review process in tricircle after tagging(newton branch) , and submit a<br>
> new patch for this feature in Trio2o separately.<br>
><br>
> Exception request after freeze date, before tagging(newton branch): If there<br>
> is some patch must be merged before the tagging(newton branch), then need to<br>
> send the exception request in the mail-list for the patch, and approved by<br>
> PTL.<br>
><br>
> That means we need to define a deadline for patches to be merged in<br>
> Tricircle before tagging(newton branch), and define the scope of patches<br>
> wish to be merged in Trcircle before splitting.<br>
><br>
> Your thoughts, proposal for the freeze date and patches to be merged?<br>
><br>
> (As the old thread containing both Trio2o and Tricircle in the subject, not<br>
> good to follow, so a new thread is started)<br>
><br>
> Best Regards<br>
> Chaoyi Huang (joehuang)<br>
><br>
> ________________________________<br>
> From: joehuang<br>
> Sent: 18 September 2016 16:34<br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> Subject: RE: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and<br>
> tricircle splitting<br>
><br>
> Thank you for your comment, Zhiyuan.<br>
><br>
> For pod management, because these two projects need to run independently, I<br>
> think submit patches separately as needed may be a better choice.<br>
><br>
> Best Regards<br>
> Chaoyi Huang(joehuang)<br>
> ________________________________<br>
> From: Vega Cai [<a href="mailto:luckyvega.g@gmail.com" target="_blank">luckyvega.g@gmail.com</a>]<br>
> Sent: 18 September 2016 16:27<br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> Subject: Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and<br>
> tricircle splitting<br>
><br>
> +1 for the proposal. What about the codes for Pod operation? It seems that<br>
> both Tricircle and Trio2o need these codes. We submit patches to these two<br>
> projects separately?<br>
><br>
> Zhiyuan<br>
><br>
> joehuang <<a href="mailto:joehuang@huawei.com" target="_blank">joehuang@huawei.com</a>>于2016年9月18日周日 下午4:17写道：<br>
>><br>
>> hello, team,<br>
>><br>
>> Trio2o git repository is ready now: <a href="https://github.com/openstack/trio2o" rel="noreferrer" target="_blank">https://github.com/openstack/trio2o</a><br>
>><br>
>> The repository inherited all files and commit messages from Tricircle.<br>
>><br>
>> It's now the time start to do the tricircle splitting: a blue print is<br>
>> registere for Tricircle cleaning:<br>
>> <a href="https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.There" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.There</a><br>
>> are lots of documentation work to do. Please review these doc in the BP,<br>
>> thanks.<br>
>><br>
>> There are some proposal for patches during the splitting:<br>
>><br>
>> 1. For patch which is already in review status, let's review it in<br>
>> Tricircle (no matter it's for Trio2o or Tricircle), after it's get merged,<br>
>> then port it to Trio2o. After all patches get merged, let's have a last tag<br>
>> for Tricircle to cover both gateway and networking automation function. Then<br>
>> the cleaning will be done in Tricircle to make Tricircle as a project for<br>
>> networking automation only<br>
>> 2. For new patch which is only applicable to Trio2o, I propose that we<br>
>> submit such patches in Trio2o only, no need to submit in Tricircle.<br>
>><br>
>> Would like to know your thoughts on the splitting.<br>
>><br>
>> Best Regards<br>
>> Chaoyi Huang(joehuang)<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Email:<br>
<a href="mailto:shinobu@linux.com" target="_blank">shinobu@linux.com</a><br>
<a href="mailto:shinobu@redhat.com" target="_blank">shinobu@redhat.com</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr">BR<div>Zhiyuan</div></div></div>