<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Anne Gentle<div>Content Stacker</div><div><a href="mailto:anne@openstack.org">anne@openstack.org</a></div><div><br></div></div><div><br>On Jun 29, 2013, at 3:26 AM, Christopher Yeoh <<a href="mailto:cbkyeoh@gmail.com">cbkyeoh@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jun 29, 2013 at 7:49 AM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>What does "no plans to port" mean for people already using Floating IPs and Cloudpipe via API extensions? Sounds like it could mean a couple of things - </div>
<div>- these are becoming core and won't be an extension any more</div><div>- these won't be available in v3</div><div>- something else</div></div></div></div></blockquote><div><br><br></div><div>It means that they won't be available in v3. With the exception of baremetal nodes the same functionality will be available through either quantum or cinder directly. Though there is a small exception if someone wants to continue to use nova-network (which is in the process of being removed) rather than Quantum then people will need to use the v2 API.<br>
</div><div> </div></div></div></div></div></blockquote><div><br></div><div>Thanks for the explanation, it helps for the docs.</div><br><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Also should you cast a wider net asking for feedback on this removal (if it is a removal)? I know openstack-dev is about the future but there may be more ways to get input.</div>
<div><br></div></div></div></div></blockquote><div><br></div><div>Do you think a post to the openstack users list would be sufficent for getting further input?<br><br></div></div></div></div></div></blockquote><div><br></div><div>I was thinking of making sure it gets in the weekly newsletter and asking the user committee if they have ideas, plus Twitter. Another mailing list post may not be a different enough channel. </div><br><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Regards,<br><br>Chris<br></div><div class="gmail_extra">
<br></div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-dev mailing list</span><br><span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></blockquote></body></html>