Bug 1042194

Summary:	[RFE][heat]: Implement resource type AWS::EC2::Route
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/heat/+spec/resource-type-route
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 16:53: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:19:52 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/resource-type-route.

Description:

AWS::EC2::Route
http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-route.html
Creates a new route in a route table within a VPC. The route's target can be either a gateway attached to the VPC or a NAT instance in the VPC.
Each route in a table specifies a destination CIDR and a target (e.g., traffic destined for 172.16.0.0/12 is targeted for the virtual private gateway); we use the most specific route that matches the traffic to determine how to route the traffic.
 
Parameters
DestinationCidrBlock
GatewayId
InstanceId
NetworkInterfaceId
RouteTableId
Tags
 
Maps to no existing concept in Quantum
 
Comments
It could be that a Quantum Router would be an appropriate basis to build Routes on top of. However an alternative might be to develop a separate Quantum featureset which implements the VPC Route Table functionality. 

Specification URL (additional information):

None