<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">yes Ryan, now we have to solve these
      routing issues. We thought to create a new routing table based on
      sources in the physical host but we haven't got yet.<br>
      <br>
      We'll appreciate any idea or suggestion.<br>
      <br>
      <br>
      On 27/02/13 17:29, Ryan Richard wrote:<br>
    </div>
    <blockquote
cite="mid:4E040F7EFD3B9945A22FB3F837444C5A6EB9E01C@ORD1EXD01.RACKSPACE.CORP"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <style type="text/css" id="owaParaStyle"></style>
      <div style="direction: ltr;font-family: Tahoma;color:
        #000000;font-size: 10pt;">I was going to reply to this but you
        found my bug report already.
        <div><br>
        </div>
        <div>That fix does solve the which interface the floating IPs
          get assigned to but do the floating IPs on attached to eth0.4
          work correctly? I figured there were will be routing issues on
          the physical host.</div>
        <div><br>
        </div>
        <div>Ryan Richard</div>
        <div>OpenStack Engineer</div>
        <div>Rackspace Private Cloud<br>
          <div style="font-family: Times New Roman; color: #000000;
            font-size: 16px">
            <hr tabindex="-1">
            <div id="divRpF268298" style="direction: ltr;"><font
                size="2" color="#000000" face="Tahoma"><b>From:</b>
                Miguel Angel Diaz Corchero [<a class="moz-txt-link-abbreviated" href="mailto:miguelangel.diaz@ciemat.es">miguelangel.diaz@ciemat.es</a>]<br>
                <b>Sent:</b> Wednesday, February 27, 2013 8:22 AM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
                <b>Subject:</b> Re: [Openstack-operators] Problems with
                openstack-nova-network-2012.2.2-1 adding floating_ips
                pools<br>
              </font><br>
            </div>
            <div>
              <div class="moz-cite-prefix">On 26/02/13 16:36, Miguel
                Angel Diaz Corchero wrote:<br>
              </div>
              <blockquote type="cite">Hello.<br>
                <br>
                We've worked with my OpenStack installation for several
                months and now I have to create two pools (public and
                private pools) of floating_ips.<br>
                <br>
                I noticed that the floating_ip doesn't work correctly:<br>
                <br>
                1)cat /etc/nova/nova.conf | grep public<br>
                public_interface=eth0<br>
                <br>
                2) I need to establish the public_interface depending on
                the pool, so that:<br>
                nova-manage floating create --pool=private-ips
                --ip_range=192.168.6.228/30  --interface=eth0<br>
                nova-manage floating create --pool=prublic-ips
                --ip_range=193.144.240.45/30  --interface=eth0.4<br>
                <br>
                3) I listed my pools:<br>
                nova-manage floating list <br>
                2fd8747b4eb64ce4bd7149e2d45ff076    193.144.240.46   
                None    public-ips    eth0.4<br>
                2fd8747b4eb64ce4bd7149e2d45ff076    192.168.7.249   
                None    private-ips    eth0<br>
                <br>
                4) I created the IPs from both pools<br>
                nova floating-ip-create  private-ips<br>
                nova floating-ip-create  prublic-ips<br>
                <br>
                5) I add the IP to some instances ... but I can see that
                all the secondary IPs are created on eth0
                <br>
                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
                1500 qdisc mq state UP qlen 1000<br>
                    link/ether 00:1a:64:5d:60:00 brd ff:ff:ff:ff:ff:ff<br>
                    inet 193.144.240.45/32 scope global eth0<br>
                    inet 192.168.7.250/32 scope global eth0<br>
                    inet6 fe80::21a:64ff:fe5d:6000/64 scope link <br>
                       valid_lft forever preferred_lft forever<br>
                <br>
                Why all the secondary IPs are created on eth0?  It seems
                the public_interfaces of
                <b>"nova-manage floating create</b>" are <b>ignored</b>.
                <br>
                <br>
                Any help?<br>
                <br>
                Regards<br>
                Miguel.<br>
              </blockquote>
              <br>
              Finally I solved this issue applying the modifications
              described in the following link:<br>
              <a moz-do-not-send="true" class="moz-txt-link-freetext"
                href="https://bugs.launchpad.net/nova/+bug/1089709"
                target="_blank">https://bugs.launchpad.net/nova/+bug/1089709</a>
              <br>
              <br>
              Regards<br>
              Miguel.<br>
              <br>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>