Re: [Xen-users] crossover cable on Xen live migration

[Felipe Gutierrez <felipe.o.gutierrez@xxxxxxxxx>]

Hi, thanks for replys,

I will especify the point I am getting the error. Following this tutorial, what I did was it:

My resource on DRBD is like this. I set up the crossover IPs and I am using LVM:
# cat r8.res 
resource r8 {
  handlers {
    # these handlers are necessary for drbd 8.3 + pacemaker compatibility
    fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
    after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
  }
  startup {
  }
  disk {
    fencing resource-only;
  }
  net {
    allow-two-primaries;
  }
  syncer {
    rate 10M;
    al-extents 257;
  }
  on cloud4 {
    device /dev/drbd8;
    disk /dev/vg_8/lv_8;
    address 10.42.0.4:7789;
    meta-disk internal;
  }
  on cloud11 {
    device /dev/drbd8;
    disk /dev/vg_8/lv_8;
    address 10.42.0.11:7789;
    meta-disk internal;
  }
}


On the tutorial he doesn't explain about the cfg file. My cfg file is like this. And this works when I am not using Pacemaker. I believe with Pacemaker will work.
# vi /xen/vm8.cfg
name = "vm8"
memory = 256
disk = ['drbd:r8,xvda,w']
vif = [' ']

kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
extra = "debian-installer/exit/always_halt=true -- console=hvc0"


On the CRM (pacemaker) I did these configurations:
crm configure
property no-quorum-policy=ignore
property stonith-enabled=false
property default-resource-stickiness=1000
commit
bye

crm configure
primitive drbd_xen ocf:linbit:drbd params drbd_resource="r8" op monitor interval="15s"
ms ms_drbd_xen drbd_xen meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
commit
bye

crm configure
primitive xen_fs ocf:heartbeat:Filesystem params device="/dev/drbd8" directory="/xen" fstype="ext3"
colocation fs_on_drbd inf: xen_fs ms_drbd_xen:Master
order fs_after_drbd inf: ms_drbd_xen:promote xen_fs:start
commit
bye

I just had to add fstype="ext3" to work well. My crm_mon out put shows this:

# crm_mon --one-shot -V
============
Last updated: Wed Dec 12 10:20:41 2012
Last change: Wed Dec 12 10:20:32 2012 via cibadmin on cloud4
Stack: openais
Current DC: cloud4 - partition with quorum
Version: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c
2 Nodes configured, 2 expected votes
3 Resources configured.
============

Online: [ cloud4 cloud11 ]

 Master/Slave Set: ms_drbd_xen [drbd_xen]
     Masters: [ cloud4 ]
     Slaves: [ cloud11 ]
 xen_fs    (ocf::heartbeat:Filesystem):    Started cloud4


And I think here is the error. When I did these configurations on CRM, my crm_mon out put shows an error:
crm configure
primitive debian ocf:heartbeat:Xen params xmfile="/xen/vm8.cfg" op monitor interval="10s" op start interval="0s" timeout="30s" op stop interval="0s" timeout="300s"
colocation debian-with-xen_fs inf: debian xen_fs
order debian-after-xen_fs inf: xen_fs:start debian:start
commit

WARNING: debian: Specified interval for start is 0s, this is greater than 0 thus invalid
WARNING: debian: specified timeout 30s for start is smaller than the advised 60
WARNING: debian: Specified interval for stop is 0s, this is greater than 0 thus invalid
WARNING: debian: default timeout 20s for monitor is smaller than the advised 30

bye

# crm_mon --one-shot -V
============
Last updated: Wed Dec 12 10:33:53 2012
Last change: Wed Dec 12 10:22:31 2012 via cibadmin on cloud4
Stack: openais
Current DC: cloud4 - partition with quorum
Version: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c
2 Nodes configured, 2 expected votes
4 Resources configured.
============

Online: [ cloud4 cloud11 ]

 Master/Slave Set: ms_drbd_xen [drbd_xen]
     Masters: [ cloud11 ]
     Slaves: [ cloud4 ]
 xen_fs    (ocf::heartbeat:Filesystem):    Started cloud11

Failed actions:
    debian_start_0 (node=cloud4, call=6, rc=1, status=complete): unknown error
    debian_start_0 (node=cloud11, call=12, rc=1, status=complete): unknown error



Thanks in advance,
Felipe

On Tue, Dec 11, 2012 at 8:09 PM, Alexandre Kouznetsov <alk@xxxxxxxxxx> wrote:

Hello, Felipe.

El 11/12/12 13:48, Felipe Gutierrez escribió:

But I am not sure where I have to use the IP of crossover board and
network board.

The IP configuration for a two-node network with a cross-over cable is something far from being specific to Xen.

Generally, it is the same configuration as a regular network connection in Linux. Treat it as two network cards connected to the same switch/hub, alone, without any other host. The only possible difference with a "regular" network setup you might have encountered before, is that you will certainly not have a DHCP server available on this network, so the IP configuration must be done strictly manual.

Consider this documentation, for future reference:
http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch03_:_Linux_Networking

This one is old, but still relevant:
http://www.tldp.org/HOWTO/NET3-4-HOWTO.html

Netfilter team has published excellent networking reference, applied to Linux:
http://www.netfilter.org/documentation/index.html#documentation-howto

In case you question is about something else, you will have to state it better.

--
Alexandre Kouznetsov

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

-- 
--
-- Felipe Oliveira Gutierrez
-- Felipe.o.Gutierrez@xxxxxxxxx
-- https://sites.google.com/site/lipe82/Home/diaadia

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users