#756521 RFP: kadeploy -- Scalable, efficient and reliable cluster provisioning solution

#756521#5
Date:
2014-07-30 16:02:40 UTC
From:
To:
* Package name    : kadeploy
  Version         : 3.3
  Upstream Author : Kadeploy developers <kadeploy3-devel@lists.gforge.inria.fr>
* URL             : http://kadeploy3.gforge.inria.fr/
* License         : CeCILL version 2.0
  Programming Lang: Ruby
  Description     : Scalable, efficient and reliable cluster provisioning solution

 Kadeploy is a scalable, efficient and reliable deployment system (cluster
 provisioning solution) for cluster and grid computing. It provides a set of
 tools for cloning, configuring (post installation) and managing cluster nodes.
 It can deploy a 300-nodes cluster in a few minutes, and also supports
 authorizing users to initiate their own nodes deployments (including with
 concurrent deployments).

A work-in-progress package is available from:
Vcs-Git: git://scm.gforge.inria.fr/kadeploy3/kadeploy3.git
Vcs-Browser: https://gforge.inria.fr/scm/browser.php?group_id=2026

Lucas

#756521#10
Date:
2014-08-02 07:38:33 UTC
From:
To:
https://github.com/enovance/edeploy

which has nice role-based system, so you can deploy specific systems
depending on what type of hardware (amount of RAM, number of HDD, or
anything else you decide)...

It's been a long time I was thinking about packaging edeploy, but never
found the time to do it. It has a Makefile, but IMO, one would better
write a setup.py for it.

Your thoughts?

Thomas

#756521#15
Date:
2014-08-02 10:39:59 UTC
From:
To:
Hi,

I don't remember the exact details, but I think that edeploy's design
made it scale poorly (especially for the image broadcast part). This
might not be a problem for the typical use case for edeploy (one-time
deployment of small/medium-scale clusters to build an OpenStack
infrastructure), but it would definitely be a problem for the typical
use case for Kadeploy ((re)install medium to large scale HPC clusters
during maintenances). Cloning 112 nodes with a standard Debian image
with Kadeploy takes about 5.5 minutes, with most of it spent waiting for
the nodes to reboot. We are working on using Kexec to make reboots
faster, but unfortunately there are quite a lot lof bugs to work around
there.

Lucas

#756521#20
Date:
2015-12-27 12:17:00 UTC
From:
To:
retitle 756521 RFP: kadeploy -- Scalable, efficient and reliable cluster provisioning solution
noowner 756521
tag 756521 - pending
thanks

Hi,

A long time ago, you expressed interest in packaging kadeploy. Unfortunately,
it seems that it did not happen. In Debian, we try not to keep ITP bugs open
for a too long time, as it might cause other prospective maintainers to
refrain from packaging the software.

This is an automatic email to change the status of kadeploy from ITP
(Intent to Package) to RFP (Request for Package), because this bug hasn't seen
any activity during the last 12 months.

If you are still interested in packaging kadeploy, please send a mail to
<control@bugs.debian.org> with:

 retitle 756521 ITP: kadeploy -- Scalable, efficient and reliable cluster provisioning solution
 owner 756521 !
 thanks

It is also a good idea to document your progress on this ITP from time to
time, by mailing <756521@bugs.debian.org>.  If you need guidance on how to
package this software, please reply to this email, and/or contact the
debian-mentors@lists.debian.org mailing list.

Thank you for your interest in Debian,