Add support for Amazon VPC APIs

Registered by Rudra Rugge on 2013-08-03

Add support for Amazon VPC APIs. Please refer to the wiki link for additional details. The plan is to add support for everything listed in the specification in multiple phases. Currently review is out for phase 1. The next phases may be further split up if the code changes are large.

Phase 1: VPC and Subnet APIs (not dependent on another bp)

Phase 2: SecurityGroup and FloatingIP APIs (not dependent on another bp)

Phase 3: NetworkAcl APIs
(dependent on https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron)

Blueprint information

Status:
Started
Approver:
Joe Gordon
Priority:
Undefined
Drafter:
Rudra Rugge
Direction:
Needs approval
Assignee:
Rudra Rugge
Definition:
Drafting
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Rudra Rugge on 2013-08-13

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/aws-vpc-support,n,z

Addressed by: https://review.openstack.org/40071
    Add support for Amazon VPC APIs in Openstack
Tempest changes at:
https://review.openstack.org/#/c/53171

Too late to go into the queue for Havana. This will have to wait for Icehouse. --russellb

http://lists.openstack.org/pipermail/openstack-dev/2013-August/013607.html

Gerrit topic: https://review.openstack.org/#q,topic:bp/s,n,z

"Can you make sure all the information outlined in http://justwriteclick.com/2013/09/17/openstack-docimpact-flag-walk-through/ is included in the BP" --jogo

jogo - i have updated the document with the details as required by the docimpact walkthrough.

Is there tempest coverage for this? If so, can you please link to it from this blueprint? I think that should be a requirement before this can merge. This also links to a neutron blueprint that doesn't exist. What is this dependent on? --russellb

russellb - Tempest code is out for review and is currently pending commit for this change. The review link is at: https://review.openstack.org/#/c/53171. The link is also present as part of the commit message for this review. Also this review is only for phase 1 which has no other neutron dependency.

I was unable to follow the link for https://blueprints.launchpad.net/neutron/+spec/ipam-policy-extensions-for-neutron. That being said I think steps 1 & 2 are good for Icehouse-2, approving --jogo

jog0 - updated the correct link for phase 3
https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron

The section https://wiki.openstack.org/wiki/Blueprint-aws-vpc-support#EC2_Instance_API_changes needs some change.
The ec2 api has support for a parameter NetworkInterface.n.SubnetId, which means the logic should be repeated for each interface rather than a single SubnetId.

Moving this back to discussion based on http://lists.openstack.org/pipermail/openstack-dev/2014-February/027490.html ~ jogo Feb, 18, 2014

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyGerrit topic: https://review.openstack.org/#q,topic:bp/aws-vpc-support,n,z

Addressed by: https://review.openstack.org/40071
    Add support for Amazon VPC APIs in Openstack
Tempest changes at:
https://review.openstack.org/#/c/53171

Too late to go into the queue for Havana. This will have to wait for Icehouse. --russellb

http://lists.openstack.org/pipermail/openstack-dev/2013-August/013607.html

Gerrit topic: https://review.openstack.org/#q,topic:bp/s,n,z

"Can you make sure all the information outlined in http://justwriteclick.com/2013/09/17/openstack-docimpact-flag-walk-through/ is included in the BP" --jogo

jogo - i have updated the document with the details as required by the docimpact walkthrough.

Is there tempest coverage for this? If so, can you please link to it from this blueprint? I think that should be a requirement before this can merge. This also links to a neutron blueprint that doesn't exist. What is this dependent on? --russellb

russellb - Tempest code is out for review and is currently pending commit for this change. The review link is at: https://review.openstack.org/#/c/53171. The link is also present as part of the commit message for this review. Also this review is only for phase 1 which has no other neutron dependency.

I was unable to follow the link for https://blueprints.launchpad.net/neutron/+spec/ipam-policy-extensions-for-neutron. That being said I think steps 1 & 2 are good for Icehouse-2, approving --jogo

jog0 - updated the correct link for phase 3
https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron

The section https://wiki.openstack.org/wiki/Blueprint-aws-vpc-support#EC2_Instance_API_changes needs some change.
The ec2 api has support for a parameter NetworkInterface.n.SubnetId, which means the logic should be repeated for each interface rather than a single SubnetId.

Moving this back to discussion based on http://lists.openstack.org/pipermail/openstack-dev/2014-February/027490.html ~ jogo Feb, 18, 2014

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items