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.
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. Steven From: Jaume Devesa [mailto:devv...@gmail.com] Sent: Wednesday, November 13, 2013 10:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association Hi all, 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? Steven: if you still interested in it, please tell us. You asked for it first and it will be yours. Regards On 5 November 2013 07:21, Salvatore Orlando <sorla...@nicira.com <mailto:sorla...@nicira.com> > wrote: I don't think there has been any development in the past 6 months. A few people have shown interest in it in the past, but the blueprint has currently no assignee. So If you want to work on it, feel free to assign to yourself. To quickly sum up the discussion around this blueprint, it could be implemented in two ways: - providing automation in the neutron API (creating the floating IP together with the port) - automating the operation on the orchestration side (nova-api in this case). 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. Regards, Salvatore On 30 October 2013 08:46, Steven Weston <steven-wes...@live.com <mailto:steven-wes...@live.com> > wrote: Does anybody know what the status of this Blueprint is? https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip 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. Anybody? Thanks! Steven Weston _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org <mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org <mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
