Re: [Lustre-discuss] [wc-discuss] lustre client on arm debian
Hi Andreas, many vendors are going to put in the market ARM+GPU based cluster. Yes, ARM is a 32bit system, with now a 1 Gbit connection normally, but in few watt could have a performance of 300 GFlops... so I think in the near future could be a player in the HPC market. I'm interested yust for the patchless cluster... thanks On 10/31/2012 04:55 PM, Dilger, Andreas wrote: On 2012-10-31, at 8:27, Gabriele Paciucci paciu...@gmail.com wrote: has anyone tried to compile the lustre patchless client on a debian linux for arm architecture? Could be possible to do? Gabriel, Many years ago, someone was working on a MIPS port for Lustre and I believe they got it working, but I don't think the patches ever landed. You could make a quick search in bugzilla to see what changes they made, and update this for Arm as well. Are you looking for client or server support? My understanding is that Arm is only 32-bit today. While we regularly build for 32-bit kernels, this is not tested automatically on master anymore so it is possible that there have been regressions in this area. If be happy to hear your experiences in this area, and it would be a good time to land any patches needed to make Arm builds working. Cheers, Andreas ___ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
[Lustre-discuss] lctl ping of Pacemaker IP
Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7.I believe I have most of the set-up completed with a particular exception. The lctl ping command cannot ping the pacemaker IP alias (say a.b.c.d). The generic ping command in RHEL 6.2 can successfully access the interface. The Pacemaker alias IP (for failover of the combnied MGSMDS node with Fibre Channel multipath storage shared between both MGS/MDS-configured machines) works in and of itself. I tested with an apache service. The Pacemaker will correctly fail over the MGS/MDS from system1 to system2 properly. If I go to system2 then my Lustre file system stops because it cannot get to the alias IP number. I did configure the lustre OSTs to use --mgsnode=a.b.c.d (a.b.c.d representing my Pacemaker IP alias). A tunefs.lustre confirms the alias IP number. The alias IP number does not appear in LNET (lctl list_nids), and lctl ping a.b.c.d fails. Should this IP alias go into the LNET data base? If yes, how? What steps should I take to generate a successful lctl ping a.b.c.d? Thanks for reading! Cheers, megan ___ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
Re: [Lustre-discuss] lctl ping of Pacemaker IP
Megan, lnet pings aren't the same as tcpip/udp pings. An lnet ping 'lctl ping' would need to touch an active lnet instance on the target address. I don't think you can bind lnet to a pacemaker virtual IP but I'll let someone smarter than me on this list confirm or correct me. In any event an lnet ping and udp ping are completely separate animals. --Jeff Sent from my iPhone On Nov 1, 2012, at 21:04, Ms. Megan Larko dobsonu...@gmail.com wrote: Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7.I believe I have most of the set-up completed with a particular exception. The lctl ping command cannot ping the pacemaker IP alias (say a.b.c.d). The generic ping command in RHEL 6.2 can successfully access the interface. The Pacemaker alias IP (for failover of the combnied MGSMDS node with Fibre Channel multipath storage shared between both MGS/MDS-configured machines) works in and of itself. I tested with an apache service. The Pacemaker will correctly fail over the MGS/MDS from system1 to system2 properly. If I go to system2 then my Lustre file system stops because it cannot get to the alias IP number. I did configure the lustre OSTs to use --mgsnode=a.b.c.d (a.b.c.d representing my Pacemaker IP alias). A tunefs.lustre confirms the alias IP number. The alias IP number does not appear in LNET (lctl list_nids), and lctl ping a.b.c.d fails. Should this IP alias go into the LNET data base? If yes, how? What steps should I take to generate a successful lctl ping a.b.c.d? Thanks for reading! Cheers, megan ___ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss ___ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
