Support private/public cloud spanning
Bug #977481 reported by
Brian Thomason
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
It would be nice if one could use JuJu to scale services between a private cloud and a public cloud, i.e. Eucalyptus and EC2.
For instance, JuJu already has solid charms for deploying CloudFoundry, but the scalability would be even better if one could spawn DEAs in a private cloud until resources are exhausted, and then automatically spawn further DEA instances in EC2.
This is just one use case where spanning could be an important feature.
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in juju: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
Definitely needs to be considered as a long term goal. Bug #829420 would be one way to do it, with two environments being able to relate to one another as external services. But I think what you're talking about is being able to have one environment span multiple providers, which would be interesting.
The challenges that would also need to be overcome (I think this probably should be a blueprint when it is finally taken up):
* Security between the clouds. Right now charms can assume that all the units they're talking to are on the same cloud network, which offers a known degree of protection against unauthorized sniffing and/or man-in-the-middle attacks depend on the cloud provider.
* Latency issues. Some services won't work well at all when scaled out over long distance links.