Bug 1042412 - [RFE][neutron]: Quantum v2 Euca-tools Nova CLI compatibility
Summary: [RFE][neutron]: Quantum v2 Euca-tools Nova CLI compatibility
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/neut...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 22:11 UTC by RHOS Integration
Modified: 2015-11-20 19:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:12:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.