Changes between Version 3 and Version 4 of WikiStart


Ignore:
Timestamp:
Sep 4, 2007, 8:03:54 PM (17 years ago)
Author:
Bruno Cornec
Comment:

first content

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v3 v4  
    33= Design Ideas around the project-builder.org project =
    44
    5 Since 2005 that I took over the maintenance of the [MondoRescue http://www.mondorescue.org] project, I have passed time developing code on the periphery of the project to allow me to easily build packages from Subversion, deliver them, manage them, ...
     5Since 2005 that I took over the maintenance of the [http://www.mondorescue.org MondoRescue] project, I have passed time developing code on the periphery of the project to allow me to easily build packages from Subversion, deliver them, manage them, ...
    66
    77I met a lot of Open Source project which are suffering from the same barrier for their adoption as mondo suffered in the past: without native packaging for your distribution you have much less people testing your software, trying it, less chance to be integrated in distributions, ...
    88
    9 Then I wanted to also work on another project called [dploy.org http://trac.dploy.org] which uses the great [LinuxCOE http://www.LinuxCOE.org]. However that LinuxCOE project had exactly the same issue as previously mentioned, no packaging, on install from CVS, so smaller community. And in order for me to put something on a prouction server, I want it packaged :-)
     9Then I wanted to also work on another project called [ http://trac.dploy.org dploy.org] which uses the great [http://www.LinuxCOE.org LinuxCOE]. However that LinuxCOE project had exactly the same issue as previously mentioned, no packaging, on install from CVS, so smaller community. And in order for me to put something on a prouction server, I want it packaged :-)
    1010
    1111So I decided it could be a good idea to reuse the scripts made for mondo to package LinuxCOE. However, they were too specific, even if the ideas could be reused (that was my 3rd generation of build scripts, so ideas were more advanced than the code).
    1212
     13= Technical ideas around the project-builder.org (aka pb) project =
    1314
    14 This web page has been written following multiple discussions around these topics with J. Vance, B. Gartner, L. Mayes, G. Renaud, L. Bouchard and many others.
    15 
    16 = Technical ideas around a dploy.org project =
    17 
    18  * use a standard protocol such as HTTP, and apache+wget to allow communication between the machine deployed and and deployment server. This would be the prefered way of exchanging informations (hw inventory typically)
    19  * mindi (minimal boot environement) could be used on the machine deployed at first run, through media or PXE. Or it could also be launched on an already deployed server.
    20  * mindi could also integrate other required components such as lshw, ssst tools, or other manufacturer tools based on a future set of configuration files provided in mindi 2.x
    21  * the inventory is stored in the server DB (standalone RDBMS, or integrated in another tool) and will be maintained as oprations are made on the machine, as well as some status.
    22  * following reboot of the server will trigger the installtion planned (deployment through LinuxCOE or image deployment with mondo)
    23  * Full support of proliant hardware (ILO - Raid - Firmware updates)
    24  * For security reason most of the scripts run as dploy user (not root)
    25 
    26 == Interface functions ==
    27 
    28  * list of servers (automatic addition of PXE based servers, manual addition for others)
    29  * assigning a task to a machine/group of machines
    30  * (proliant) manage already discovered servers (power on, off... ILO functions)
    31  * delete servers to restart discovery / installation
    32  * group servers to apply the same job to multiple servers
    33  * (proliant) firmware update
    34  * (proliant) link to admin page (2381)
    35  * link to webmin page (10000)
    36  * (proliant) link to ACU (started on demand before launching the interface)
    37  * launch any commands thru SSH (password or public key protected)
    38  * launch an imaging job
    39 
    40 == Proposed Requirements ==
    41 
    42  * Perl
    43  * Perl DBI
    44  * dhcpd
    45  * MySQL, PostgreSQL or file
    46  * Perl CGI or TT
    47  * tftpd
    48  * pxelinux
     15 * use perl. It makes coding so more efficient, powerful and also fun
     16 * use AppConfig. A lot of information is managed under a configuration file format and AppConfig makes it tivial to handle them.
    4917
    5018== Concerning trac ==