<div dir="ltr">True. I think if you just want to add segments, making use of the new segments API added as part of the routed networks work would be the way to go.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 7, 2016 at 9:19 AM, Robert Kukura <span dir="ltr"><<a href="mailto:kukura@noironetworks.com" target="_blank">kukura@noironetworks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <p>I'm not sure unbinding ports is necessary unless the segment that
      a port has bound is removed or modified. A reasonable compromise
      might be for ML2 to allow adding new segments, which should not
      require unbinding/rebinding ports, but not allow removing or
      modifying existing segments.</p>
    <p>-Bob<br>
    </p><div><div class="h5">
    <br>
    <div class="m_-1949809341094726734moz-cite-prefix">On 11/5/16 7:59 PM, Kevin Benton wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">To allow that we would have to unbind every port in
        the network and then rebind it with the new segment info
        generated from changing the provider attributes. This requires
        quite a bit of orchestration code in ML2 (to handle failures,
        etc) that doesn't exist right now.</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Sat, Nov 5, 2016 at 7:50 AM, zhuna <span dir="ltr"><<a href="mailto:juno.zhu@huawei.com" target="_blank">juno.zhu@huawei.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div link="blue" vlink="purple" lang="ZH-CN">
              <div class="m_-1949809341094726734m_-1952782099436391396WordSection1">
                <p class="MsoNormal"><span lang="EN-US">Dear,</span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US">Neutron RESTful
                    API support update network provider attributes, but
                    ML2 raises error when update network provider
                    attributes (in function _raise_if_updates_provider_att<wbr>ributes),
                    can anyone tell me why ML2 does not support it?</span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US">BR</span></p>
                <p class="MsoNormal"><span lang="EN-US">Juno</span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
              </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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
            <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="m_-1949809341094726734mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>______________________________<wbr>______________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="m_-1949809341094726734moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a>
<a class="m_-1949809341094726734moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </div></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>