Bug 1042412

Summary: [RFE][neutron]: Quantum v2 Euca-tools Nova CLI compatibility
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/quantum-v2-euca-compat
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:12:00 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 22:11:32 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-v2-euca-compat.

Description:

Currently, the euca-API is implemented as a nova API that passes calls to nova-network.

With quantum v2 nova-network is no longer used, so we would either need the euca-api code to pass these calls to quantum (e.g., floating IPs, security groups), to catch these calls in the network.API() and proxy them to quantum, or to not support euca-commands.

The same applies for 'nova' commands for creating floating-ips, security-groups, etc.

we should coordinate with the rest of the openstack community on this, as I expect that we have the same problem with cinder. (Update: apparently cinder is entirely proxied via nova, so they don't really have this problem). 

Specification URL (additional information):

None