Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jun 03, 2014 at 08:38:53AM +1000, Igor Cicimov wrote: > > Each VM has its own "kernel", its own "drbd" module. > > => works. > > But even there, usually you put the VM image on top of DRBD, > > not some DRBD inside the VM (even though that is possible). > > > > Container: does not work. > > Possibly could be made to work. > > Probably would not only require changes in DRBD module code, > > but in generic kernel as well. I don't know. > > I do not see that happening anytime soon. > > > > Maybe find someone who knows, > > and get them to explain to me > > what would be necessary to do in DRBD > > to make it play nice from within containers... > > > > But I really don't see why. > > > > If you create a container, > > you tell it what "storage" to use. > > Put that on top of DRBD. > > Done. > Thanks Lars, sounds like a lots of work. The only difference is that the > control over drbd is outside the container it self making the drbd > invisible for the inside users. Which IMO is an improvement. Why would you want to make it visisble. > But it is what it is so we have to skip > drbd from the cluster stack on container level. I'd see the container be a *resource* manged by a cluster, rather than being a cluster member itself. But maybe I just don't get your use case yet ... -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com