[Blueprint server-o-ensemble-orchestra-openstack-support] Ensemble should support Orchestra and OpenStack as a deployment medium

[Clint Byrum]

Blueprint changed by Clint Byrum:

Whiteboard set to:
 
 2 basic ways Ensemble could integrate with Orchestra:
  a.) orchestra add an ec2 interface... ensemble is probably pretty low in requirements (ListInstances, RunInstances...) -> Orchestra todo, can use a subset
  b.) ensemble support interacting with orchestra via cobbler's api. -> option a seems agreed on
  
OpenStack:
- need to allow OpenStack object storage (swift) in addition to S3 storage
- need to distinguish between Rackspace and OpenStack, we want to interact with both
- missing python-swift-twisted client library (txRackspace is a placeholder) to OpenStack Object storage (To do for OpenStack)

Not enough resources in ensemble team to work on this

ACTION:
 * gustavo to send soren email regarding needed api functions for twisted client lib
 * cloud init to support Rackspace meta-data (nice, not required)
 * orchestra to give a twisted API to create physilcal machine that ensemble can call (aws or openstack)
 * have a simple way for orchestra to deploy a pool of machine that are made availabe for ensemble

< JAMES PAGE >
 ------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Is he here ? WOW

-- 
Ensemble should support Orchestra and OpenStack as a deployment medium
https://blueprints.launchpad.net/ubuntu/+spec/server-o-ensemble-orchestra-openstack-support