Comment 0 for bug 1258490

Currently, when I want create FloatingIP, I should specify port_id.
Unfortunately OS::Neutron::Pool has parameter vip without clarify port_id attribute.
And I am forced use such hack in template :

port_id:
      { 'Fn::Select': ['port_id', {'Fn::GetAtt': [TestPool, vip]}]}

I think, that it is not good way for fixing current problem.
Also neutron team has some plans connected with changing vip resource.
As I know, they want add ability to connect one vip with different LoadBalancers.

So I offer move vip to separate resource or changing current Pool resource, so that it will be more clear for using.

Also I will be glad to hear other solutions for problem.