Bug 1042188

Summary:	[RFE][heat]: Implement OS::Nova::FloatingIP
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-heat	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	breeler, markmc, sbaker, sdake, shardy, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/heat/+spec/nova-networking-floatingip
Whiteboard:	upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	A new feature has been added to implement floating IPs in Compute, using OS::Nova::FloatingIP. Prior to this change, floating IPs could not be used effectively. Now floating IPs can be used effectively.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-22 19:08:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 21:18:55 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/nova-networking-floatingip.

Description:

Currently my heat template works with AWS resource type:

   DatabaseIPAddress:
     Type: AWS::EC2::EIP
   DatabaseIPAssoc :
     Type: AWS::EC2::EIPAssociation
     Properties:
       InstanceId: {Ref: BaseInstance}
       EIP: {Ref: MyIPAddress}

Now if i want to change to OpenStack ( OS ) namespace with a similar
implementation :

   MyIPAddress:
     Type: OS::Neutron::FloatingIP
Properties:
floating_network_id : String
   MyIPAssoc :
     Type: OS::Neutron::FloatingIPAssociation
     Properties:
       floatingip_id : {Ref: MyIPAddress}

I cannot problem is,

a) floating_network_id ( is not known ) which is a required property.
b) Even if its available / defaults to, its an overhead from AWS
simplicity.

Lets have OS::Nova::FloatingIP resource created that can mirror the functionality of AWS::EC2::EIP

Specification URL (additional information):

http://lists.openstack.org/pipermail/openstack-dev/2013-November/018450.html

Comment 2 Stephen Gordon 2014-01-23 20:51:16 UTC

Moving to POST based on upstream status (Implemented).