<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thanks Armando.<br>
    <br>
    Another question:<br>
    Every compute node that hosts instances with floating IPs has an IP
    from the external network pool.<br>
    If the SNAT is done by the Network Node what is the reason for the
    compute node to have an external IP?<br>
    <br>
    BR,<br>
    Itzik <br>
    <br>
    <div class="moz-cite-prefix">On 02/11/2015 08:13 PM, Armando M.
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAK+RQebSPmucQNVxwUAOdLuCw8Vj3btf2Zh27sjt=bhFFgJpwA@mail.gmail.com"
      type="cite">
      <div dir="ltr">L2pop is a requirement.
        <div><br>
        </div>
        <div>With the existing agent-based architecture, L2pop is used
          to update the FDB tables on the compute hosts to make
          east/west traffic possible whenever a new port is created or
          existing one is updated.
          <div><br>
          </div>
          <div>Cheers,</div>
          <div>Armando<br>
            <div class="gmail_extra"><br>
              <div class="gmail_quote">On 10 February 2015 at 23:07,
                Itzik Brown <span dir="ltr"><<a
                    moz-do-not-send="true"
                    href="mailto:itzikb@redhat.com" target="_blank">itzikb@redhat.com</a>></span>
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
                  <br>
                  In the Networking guide [1] there is a requirement for
                  l2 population both as<br>
                  a mechanism driver and in OVS agent when enabling DVR.<br>
                  Is this is a requirement and if so what is the reason?<br>
                  <br>
                  Thanks,<br>
                  Itzik<br>
                  <br>
                  <br>
                  [1] <a moz-do-not-send="true"
                    href="http://docs.openstack.org/networking-guide/content/ha-dvr.html"
                    target="_blank">http://docs.openstack.org/networking-guide/content/ha-dvr.html</a><br>
                  <br>
                  __________________________________________________________________________<br>
                  OpenStack Development Mailing List (not for usage
                  questions)<br>
                  Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                    target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
                  <a moz-do-not-send="true"
                    href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                    target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
  </body>
</html>