<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Thanks Steven for working on this topic!</div><div><br></div><div>I would prefer the second approach, although there were some discussions during the summit about moving all calls to Neutron instead of having nova involved.</div><div>Anyway, just providing my two cents</div><div><br></div><div>Thanks,</div><div><br></div><div>Edgar</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Salvatore Orlando <<a href="mailto:sorlando@nicira.com">sorlando@nicira.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Date: </span> Thursday, November 14, 2013 3:21 AM<br><span style="font-weight:bold">To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association<br></div><div><br></div><div dir="ltr">Hi Steven,<div><br></div><div>I see three Steven Weston on Launchpad. If you give me your LP ID, I will assign the blueprint to you.</div><div>This is a nova parity item and i'd like to raise the priority to High.</div><div><br></div><div>It would be also good to hear from you about the implementation approach.</div><div>In the past we debated two alternatives: passing a special attribute to a port in order to create a floating IP for it too, or orchestrating the operation from the nova side.</div><div>The first option has the cons of adding a side effect to a REST API call (which is not advisable), and might be a bit complex when the network where the port is on is attached to multiple routers.</div><div>The latter option has the cons of requiring two neutron API calls.</div><div><br></div><div>The input of the whole community on this topic will be very appreciated.</div><div><br></div><div>Salvatore</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 November 2013 05:47, Steven Weston <span dir="ltr"><<a href="mailto:steven-weston@live.com" target="_blank">steven-weston@live.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Thanks for the responses on this. I definitely still interested in implementing the functionality described in this blueprint, but have been reluctant to start on it since I did not get a response.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Yes, please assign it to me and I will get started on it right away! I do not seem to have the capability to assign it to myself.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Steven<u></u><u></u></span></p><p class="MsoNormal"><a name="1425527a0e78f4ec__MailEndCompose"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><u></u> <u></u></span></a></p><p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; ">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; "> Jaume Devesa [mailto:<a href="mailto:devvesa@gmail.com" target="_blank">devvesa@gmail.com</a>] <br><b>Sent:</b> Wednesday, November 13, 2013 10:32 PM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b> Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association<u></u><u></u></span></p><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi all,<u></u><u></u></p></div><p class="MsoNormal" style="margin-bottom:12.0pt">I see it has been passed two weeks since first mail in this thread and that blueprint still without assignee. I also think this is a good option for my first blueprint. However, I can not assign blueprints to myself, only bugs. Can anybody assign to me?<u></u><u></u></p></div><p class="MsoNormal" style="margin-bottom:12.0pt">Steven: if you still interested in it, please tell us. You asked for it first and it will be yours.<u></u><u></u></p></div><p class="MsoNormal">Regards<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><p class="MsoNormal">On 5 November 2013 07:21, Salvatore Orlando <<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>> wrote:<u></u><u></u></p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">I don't think there has been any development in the past 6 months.<u></u><u></u></p><div><p class="MsoNormal">A few people have shown interest in it in the past, but the blueprint has currently no assignee.<u></u><u></u></p></div><div><p class="MsoNormal">So If you want to work on it, feel free to assign to yourself.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">To quickly sum up the discussion around this blueprint, it could be implemented in two ways:<u></u><u></u></p></div><div><p class="MsoNormal">
- providing automation in the neutron API (creating the floating IP together with the port)<u></u><u></u></p></div><div><p class="MsoNormal">- automating the operation on the orchestration side (nova-api in this case).<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">There are pro and cons in both solutions. In my humble opinion, the only thing I would care of is that the existing operation in the Neutron API stay "atomic" as they are.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Regards,<u></u><u></u></p></div><div><p class="MsoNormal">Salvatore<u></u><u></u></p></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><div><div><p class="MsoNormal">On 30 October 2013 08:46, Steven Weston <<a href="mailto:steven-weston@live.com" target="_blank">steven-weston@live.com</a>> wrote:<u></u><u></u></p></div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><div><div><p class="MsoNormal">Does anybody know what the status of this Blueprint is? <a href="https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip" target="_blank">https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip</a><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">I am new to the neutron developer community and I am looking for a first project – this might be a good place to start. But the last update was in March of this year, so I don’t know if the specifications have been locked down yet. <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Anybody?<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Thanks!<u></u><u></u></p><p class="MsoNormal"><span style="color:#888888">Steven Weston<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u></u><u></u></p></blockquote></div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u></u><u></u></p></blockquote></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br><a 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><br></blockquote></div><br></div>
_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</span></body></html>