<div dir="ltr"><br><div class="gmail_extra">Hi Slawek,</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">2018-04-06 17:38 GMT+09:00 Sławek Kapłoński <span dir="ltr"><<a href="mailto:slawek@kaplonski.pl" target="_blank">slawek@kaplonski.pl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
One more question about implementation of this goal. Should we take care (and add to story board [1]) projects like:<br></blockquote><div><br></div><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">In my understanding, tasks in the storyboard story are prepared per project team listed in the governance.</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)">IMHO, repositories which belong to a project team should be handled as a single task.</div><div><br></div>The situations vary across repositories.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
openstack/neutron-lbaas<br></blockquote><div><br></div><div>This should be covered by octavia team.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
openstack/networking-cisco<br>
openstack/networking-dpm<br>
openstack/networking-infoblox<br>
openstack/networking-l2gw<br>
openstack/networking-lagopus<br></blockquote><div><br></div><div>The above repos are not official repos.</div><div>Maintainers of each repo can follow the community goal, but there is no need to be tracked as the neutron team.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
openstack/neutron-dynamic-<wbr>routing<br></blockquote><div><br></div><div>This repo is part of the neutron team. We, the neutron team need to cover this.</div><div><br></div><div>FYI: The official repositories covered by the neutron team is available here.</div><div><a href="https://governance.openstack.org/tc/reference/projects/neutron.html">https://governance.openstack.org/tc/reference/projects/neutron.html</a><br></div><div><br></div><div>Thanks,</div><div>Akihiro</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Which looks that should be probably also changed in some way. Or maybe list of affected projects in [1] is „closed” and if some project is not there it shouldn’t be changed to accomplish this community goal?<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
[1] <a href="https://storyboard.openstack.org/#!/story/2001545" rel="noreferrer" target="_blank">https://storyboard.openstack.<wbr>org/#!/story/2001545</a><br>
<span class="gmail-im gmail-HOEnZb"><br>
—<br>
Best regards<br>
Slawek Kaplonski<br>
<a href="mailto:slawek@kaplonski.pl">slawek@kaplonski.pl</a><br>
<br>
<br>
<br>
<br>
</span><span class="gmail-im gmail-HOEnZb">> Wiadomość napisana przez ChangBo Guo <<a href="mailto:glongwave@gmail.com">glongwave@gmail.com</a>> w dniu 26.03.2018, o godz. 14:15:<br>
><br>
><br>
</span><div class="gmail-HOEnZb"><div class="gmail-h5">> 2018-03-22 16:12 GMT+08:00 Sławomir Kapłoński <<a href="mailto:slawek@kaplonski.pl">slawek@kaplonski.pl</a>>:<br>
> Hi,<br>
><br>
> I took care of implementation of [1] in Neutron and I have couple questions to about this goal.<br>
><br>
> 1. Should we only change "restart_method" to mutate as is described in [2] ? I did already something like that in [3] - is it what is expected?<br>
><br>
> Yes , let's the only thing. we need test if that if it works .<br>
><br>
> 2. How I can check if this change is fine and config option are mutable exactly? For now when I change any config option for any of neutron agents and send SIGHUP to it it is in fact "restarted" and config is reloaded even with this old restart method.<br>
><br>
> good question, we indeed thought this question when we proposal the goal. But It seems difficult to test that consuming projects like Neutron automatically.<br>
><br>
> 3. Should we add any automatic tests for such change also? Any examples of such tests in other projects maybe?<br>
> There is no example for tests now, we only have some unit tests in oslo.service .<br>
><br>
> [1] <a href="https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html" rel="noreferrer" target="_blank">https://governance.openstack.<wbr>org/tc/goals/rocky/enable-<wbr>mutable-configuration.html</a><br>
> [2] <a href="https://docs.openstack.org/oslo.config/latest/reference/mutable.html" rel="noreferrer" target="_blank">https://docs.openstack.org/<wbr>oslo.config/latest/reference/<wbr>mutable.html</a><br>
> [3] <a href="https://review.openstack.org/#/c/554259/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/554259/</a><br>
><br>
> —<br>
> Best regards<br>
> Slawek Kaplonski<br>
> <a href="mailto:slawek@kaplonski.pl">slawek@kaplonski.pl</a><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
><br>
><br>
> --<br>
> ChangBo Guo(gcb)<br>
> Community Director @EasyStack<br>
> ______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div></div>