<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
    <div id="smartTemplate4-quoteHeader">Thank you Mark for the answer.<br>
      <br>
      andrey<br>
      <br>
    </div>
    <div class="moz-cite-prefix">On 29.09.2014 18:31, Mark McClain
      wrote:<br>
    </div>
    <blockquote
      cite="mid:4881CD3C-CA23-4B4F-BC32-EC7E0165143B@mcclain.xyz"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br>
      <div>
        <div>On Sep 29, 2014, at 7:09 AM, Andrey Epifanov <<a
            moz-do-not-send="true" href="mailto:aepifanov@mirantis.com">aepifanov@mirantis.com</a>>
          wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <meta http-equiv="content-type" content="text/html;
            charset=windows-1252">
          <div smarttemplateinserted="true" bgcolor="#FFFFFF"
            text="#000000"> Hi All,<br>
            <br>
            I started working on the the <a moz-do-not-send="true"
              class="moz-txt-link-freetext"
              href="https://bugs.launchpad.net/neutron/+bug/1339028">https://bugs.launchpad.net/neutron/+bug/1339028</a><br>
            and realized that we have the same issue with other
            connected resources in Neutron.<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>The is a bug in how we’re implementing the logic to manage
          routes on the router instance in the l3-agent implementation.
           There are other implementations of the logical router that do
          not need this restriction. </div>
        <br>
        <blockquote type="cite">
          <div smarttemplateinserted="true" bgcolor="#FFFFFF"
            text="#000000"> <br>
            The problem is that we have API for the modification of any
            resources without<br>
            limitations, for example, we can modify Router IP and
            connected to this subnet<br>
            VMs never will know about it and lose the default router.
            The same situation<br>
            with routes and IP for DHCP/DNS ports.<br>
             <br>
            <a moz-do-not-send="true" class="moz-txt-link-freetext"
              href="https://bugs.launchpad.net/neutron/+bug/1374398">https://bugs.launchpad.net/neutron/+bug/1374398</a><br>
            <a moz-do-not-send="true" class="moz-txt-link-freetext"
              href="https://bugs.launchpad.net/neutron/+bug/1267310">https://bugs.launchpad.net/neutron/+bug/1267310</a><br>
          </div>
        </blockquote>
        <div><br>
        </div>
        I don’t see any of these as a bug.  If tenant wants to make
        changes to their network (even ill advised ones), we should
        allow it.  Restricting these API operations to admin’s means
        we’re inhibiting users from making changes that could be regular
        maintenance operations of a tenant.<br>
      </div>
      <div><br>
      </div>
      <div>mark</div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
    <br>
    <div id="smartTemplate4-template"><br>
      <br>
       </div>
  </body>
</html>