Quantum v2 Euca-tools Nova CLI compatibility

Registered by dan wendlandt on 2012-07-09

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).

Blueprint information

Status:
Complete
Approver:
dan wendlandt
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Armando Migliaccio on 2015-10-13

Related branches

Sprints

Whiteboard

temporarily assigning this to G-3 to see if someone is interested in taking this. Closely related to https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy

We need to keep track of this, but its unlikely to make G-2.

We now proxy nova floating IP calls to quantum (starting in grizzly-1).

Aaron is also contributing code that will add a security groups API, and make sure that API proxies security group calls to quantum.

Together, this should give us what we need for basic euca-tools compat, but we should do a complete audit to make sure.

I'm assigning this to grizzly-2, as it will be easiest to test once the iptables security group stuff is merged.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.