Comment 5 for bug 806241

I would be hesitant to make iSCSI backed container storage another pre-requisite for co-located service units on physical hardware. It makes sense in the context of EBS+EC2, but network attached storage is a 4 letter word for many admins (especially who are migrating away from EC2 after being bitten by recent EBS problems). Not to mention the overhead in terms of network hardware and admin. that is required to "do it right" at scale.

It seems all of the abstraction (LXC and now iSCSI) that would be required to deploy services onto hardware defeats the purpose of deploying to hardware to begin with. It then begins to look more like deploying services into an ensemble cloud, which may be hosted on our hardware, or ec2, etc. This sounds reasonable and attractive for traditionally elastic workloads like web services, map/reduce, etc. However, when we think of using ensemble to deploy cloud infrastructure or other services that need to be tightly coupled with the hardware that hosts it, the level of abstraction begins to become a show stopper.