incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Browning <bbrown...@redhat.com>
Subject Re: Dynamic selection of driver
Date Fri, 12 Nov 2010 14:09:19 GMT

On Nov 11, 2010, at 8:21 PM, David Lutterkort wrote:

> Right now, the deltacloud server only ever uses one driver; that means
> that if you want to talk to multiple clouds, you need to have one
> deltacloud server running for each of them. Clearly, not very admin
> friendly.
> 
> Toby actually experimented with this (wanna share your patch, Toby ?).
> To me, the cleanest way to enable dynamic selection of the driver is to
> select the driver through add'l HTTP headers. For example, by sending
> 
>        X-Deltacloud-Driver: ec2
>        X-Deltacloud-Endpoint: https://eu-west-1.ec2.amazonaws.com/
> 
> you'd be using the eu-west region of EC2.
> 
> We would maintain the current behavior of the driver as the default when
> these headers are absent; so if you start 'deltacloudd -i mock', clients
> that don't set the Deltacloud headers will talk to the mock driver.
> 

+1 from me as well. Should each server advertise the drivers it supports, or is it reasonable
to assume the user knows which drivers are supported for the server they're connected to?
Mime
View raw message