Hi,
I attach cluster configuration:
Note that "migration_network_suffix=tcp://" is correct in my environment as
I have edited the VirtualDomain resource agent in order to build the
correct url "tcp://vdicnode01-priv"
mk_migrateuri() {
local target_node
local migrate_target
show your cluster configuration.
2017-01-17 10:15 GMT+01:00 Oscar Segarra :
> Hi,
>
> Yes, I will try to explain myself better.
>
> Initially
> On node1 (vdicnode01-priv)
>>virsh list
> ==
> vdicdb01 started
>
> On node2 (vdicnode02-priv)
>>virsh list
> ==
> vdicdb02
Hi,
Yes, I will try to explain myself better.
*Initially*
On node1 (vdicnode01-priv)
>virsh list
==
vdicdb01 started
On node2 (vdicnode02-priv)
>virsh list
==
vdicdb02 started
--> Now, I execute the migrate command (outside the cluster <-- not using
pcs resource
sorry,
But do you mean, when you say, you migrated the vm outside of the
cluster? one server out side of you cluster?
2017-01-17 9:27 GMT+01:00 Oscar Segarra :
> Hi,
>
> I have configured a two node cluster whewe run 4 kvm guests on.
>
> The hosts are:
> vdicnode01
> vdicnode02
>
> And I have cre
Hi,
I have configured a two node cluster whewe run 4 kvm guests on.
The hosts are:
vdicnode01
vdicnode02
And I have created a dedicated network card for cluster management. I have
created required entries in /etc/hosts:
vdicnode01-priv
vdicnode02-priv
The four guests have collocation rules in o
