Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jun 17, 2015 at 11:05:40AM +0200, Dietmar Maurer wrote:
> I have still problems with live migration.
> First, it works now if if set:
>
> # drbdmanage net-options --allow-two-primaries yes --common
>
> But I thought it would be better to do it directly on the resource, so
> I tried:
>
> # drbdmanage net-options --allow-two-primaries yes --resource vm-100-disk-1
>
> That also worked,
Same here...
> so I tried to implement that inside the pve storage library.
> I call set_drbdsetup_props() directly after auto_deploy:
>
> ------------
> ($rc, $res) = $hdl->set_drbdsetup_props(
> {
> target => "resource",
> resource => $name,
> type => 'neto',
> 'allow-two-primaries' => 'yes',
> });
> check_drbd_rc($rc->[0]);
> -----------
Looks good to me.
>
> That seems to work, but I end up with _standalone connections:
>
> Why? How do I correctly set allow-two-primaries on resources?
As far as I can tell set_drbdsetup_props() looks okay. The problem is that we
are not able to reproduce your problem. In a drbdmanage environment[1]
everything looks fine, both nodes are able to switch the resource to primary
(tested with 'drbdadm primary' on both sides)...
Is it reproducible? Even if you start from scratch (drbdmanage unit)?
Regards, rck
[1] drbd9 9.0.0, drbdmanage 0.43, drbd-utils 8.9.3