Open Stack

+1 to Soren's argument that ec2 is the 1000lb gorilla and should be central to nova. We definitely need to support it with as close to 100% compatibility as we can. 

Sounds like the only option is to "embrace and extend" it. Do everything it can do, and layer on what we need provided it doesn't break the core EC2 commands. If the customer wants pure EC2, they'll have to live with the limitations.

That said, is this the proposal I'm hearing? ...

Since our separation is done at the service.api layer, the service.api's get pulled in two directions with each change in ec2/os. The idea is to have ec2 be a translation layer to os api? Preventing ec2 api from calling [service].api directly?

So, instead of 

EC2 Client   OS Client
   |             |
EC2 API        OS API
    \           /
   [Service] API

We'd be shifting to:

EC2 Client ---- EC2 API
                        |
OS Client ------ OS API
                        |
                 [Service] API

I need to think more about this, but at first blush, it doesn't seem like such a thing? At some point the abstraction layer needs to be locked down doesn't it?

-S

> Put another way: do we want to expend more resources on an API we don't control?
> 
> -jay
This email may include confidential information. If you received it in error, please delete it.