<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Correct if I'm wrong but what value ips
      core api bring to us currently?<br>
      It offers you two calls: <br>
      GET on <a class="moz-txt-link-freetext" href="http://localhost:8774/v3/servers/">http://localhost:8774/v3/servers/</a><instance-id>/ips 
      => returns instance ips<br>
      GET on
      <a class="moz-txt-link-freetext" href="http://localhost:8774/v3/servers/">http://localhost:8774/v3/servers/</a><instance-id>/ips/{network-id}
      => returns instance ips that are member of the specified
      networl.<br>
      <br>
      both information can be found in servers/detail. <br>
      <br>
      So I'm asking you guys if you agree to remove it too. I could also
      think about just demote it from core, but I really cant see any
      use for it right now. <br>
      <br>
      <br>
      On 06/28/2013 09:31 AM, Christopher Yeoh wrote:<br>
    </div>
    <blockquote
cite="mid:CANCY3edbUN8WuUVYc81+cC=juiYFQbakQ9uxAs11y59JZ-x1hA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>Hi,<br>
              <br>
              The following is a list of API extensions for which there
              are no plans to port. Please shout if you think any of
              them needs to be!<br>
              <br>
              <div class="" id="magicdomid179"><span class="">baremetal_nodes.p</span><span
                  class="">y</span></div>
              <div class="" id="magicdomid75"><span class="">os_networks.py</span></div>
              <div class="" id="magicdomid76"><span class="">networks_associate.py</span></div>
              <div class="" id="magicdomid77"><span class="">os_tenant_networks.py</span></div>
              <div class="" id="magicdomid78"><span class="">virtual_interfaces.py</span></div>
              <div class="" id="magicdomid79"><span class="">createserverext.py</span><span
                  class=""></span></div>
              <div class="" id="magicdomid132"><span class="">floating_ip_dns.py</span></div>
              <div class="" id="magicdomid135"><span class="">floating_ip_pools.py</span><span
                  class=""></span></div>
              <div class="" id="magicdomid136"><span class="">floating_ips_bulk.py</span></div>
              <div class="" id="magicdomid138"><span class="">floating_ips.py</span></div>
              <div class="" id="magicdomid139">cloudpipe.py</div>
              <span class=""></span>
              <div class="" id="magicdomid83"><span class="">cloudpipe_update.py</span></div>
              <div class="" id="magicdomid84"><span class="">volumes.py</span></div>
              <div class="" id="magicdomid85"><br>
              </div>
              Also I'd like to propose that after H2 any new API
              extension submitted HAS to have a v3 version. That will
              give us enough time to ensure that the V3 API in Havana
              can do everything that the V2 one except where we
              explicitly don't want to support something.<br>
              <br>
            </div>
            For developers who have had new API extensions merged in H2
            but haven't submitted a v3 version, I'd appreciate it if you
            could check the following etherpad to see if your extension
            is on the list and put it on there ASAP if it isn't there
            already:<br>
            <br>
            <a moz-do-not-send="true"
              href="https://etherpad.openstack.org/NovaV3ExtensionPortWorkList">https://etherpad.openstack.org/NovaV3ExtensionPortWorkList</a><br>
            <br>
          </div>
          I've tried to keep track of new API extensions to make sure we
          do v3 ports but may have missed some.<br>
          <br>
        </div>
        Chris<br>
      </div>
      <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>
  </body>
</html>