From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 90E0513829C for ; Sun, 12 Jun 2016 23:12:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E5F31E0A44; Sun, 12 Jun 2016 23:12:42 +0000 (UTC) Received: from omr-a007e.mx.aol.com (omr-a007e.mx.aol.com [204.29.186.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EA4B0E09BC for ; Sun, 12 Jun 2016 23:12:41 +0000 (UTC) Received: from mtaout-aaa01.mx.aol.com (mtaout-aaa01.mx.aol.com [172.27.1.225]) by omr-a007e.mx.aol.com (Outbound Mail Relay) with ESMTP id D30CB3800085 for ; Sun, 12 Jun 2016 19:12:40 -0400 (EDT) Received: from [192.168.1.52] (0x5b3139322e3136382e312e35325d [71.122.242.106]) by mtaout-aaa01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 890BF3800008E; Sun, 12 Jun 2016 19:12:40 -0400 (EDT) Subject: Re: [gentoo-dev] Packages up for grabs To: gentoo-dev@lists.gentoo.org References: <575053CB.1000900@verizon.net> <20160613000102.2328c75abc24c22eaceeb335@gentoo.org> From: james Message-ID: <575DFAF2.5010405@verizon.net> Date: Sun, 12 Jun 2016 19:14:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20160613000102.2328c75abc24c22eaceeb335@gentoo.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit x-aol-global-disposition: G x-aol-sid: 3039ac1b01e1575dec6834ca X-AOL-IP: 71.122.242.106 X-Archives-Salt: fef38920-46a1-4442-a24a-7b5da0b3d389 X-Archives-Hash: 68bb6ce7745bcaf9d5ff7a5dc7fa1103 On 06/12/2016 04:01 PM, Andrew Savchenko wrote: > On Thu, 2 Jun 2016 10:42:03 -0500 james wrote: >> On 06/01/2016 06:20 PM, Justin Bronder wrote: >> > Due to a lack of time and the fact I don't use any of these packages >> > anymore, they are all up for grabs. >> > >> > - media-gfx/openmesh [no project] >> > - sys-cluster/ganglia [cluster] >> > - sys-cluster/ganglia-web [cluster] >> > - sys-cluster/torque [cluster] >> > - sys-cluster/munge [cluster] dependency of sys-cluster/torque >> > - sys-cluster/mpe2 [cluster] >> > >> > Also, if there's anyone out there using the science overlay and empi >> > who's feeling motivated, that work still needs a champion to get it >> > into the main tree. If not, I'll probably drop it in a few months >> > and open openmpi and mpich2 to project maintenance as well. I >> > haven't been involved in HPC for over a decade now, it's time to >> > pass the torch. >> >> >> Hello Justin, >> >> I've been working on cluster ebuilds for a while (Apache Mesos, spark, >> etc). I'm willing to proxy maintain these except torque. Assuming there >> are no users of torque on gentoo (bgo seems inactive...it's dead; how >> would I know?). > > Hey, don't be too quick on your judgement :) We are using torque > (and maui) on three HPC setups, though we had to patch torque for > various features. Ian picked up torque:: "I can step up and maintain or co-maintain sys-cluster/torque , I use it at work and have contributed to it in the past." Which was written on 6/2/16 by axs@gentoo.org. > By the way, what scheduler/resource manager are you using for HPC? I'm more focused on small clusters and the ability to 'reboot' identical hardware into a variety of HPC or container cluster configurations. My immediate goal is fast and small clusters to run 'cluster-benchmarks' and compare different cluster offerings, for a particular problem. The emphasis is the hardware which is identical, so the cluster codes are the only difference. NO elaborate Schedulers or Framework schedulers, just testing everything, atm. That said, you may want to look at Mesos, as that cluster OS, it supports a myriad of Schedulers and Framework schedulers. It fact it encourages custom scheduler development. http://mesos.apache.org/ http://mesos.apache.org/documentation/latest/app-framework-development-guide/ > slurm ebuild seems to be even in worse state than torque one (2.6.3 > is present, 16.05.0 is the latest upstream). I do not know why more gentoo devs have not been bitten by the sys-cluster bug. Slurm is still widely used. SchedMD is hiring. > Best regards, > Andrew Savchenko > Best regards, > Andrew Savchenko James [1] http://mesos.apache.org/documentation/latest/app-framework-development-guide/