Changes between Version 1 and Version 2 of WikiStart


Ignore:
Timestamp:
Nov 20, 2006, 12:21:17 AM (13 years ago)
Author:
bruno
Comment:

migrate page hosted previously at mondorescue.org

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v1 v2  
    1 = Welcome to Trac 0.9.6 =
     1= Welcome to Dploy Wiki =
    22
    3 Trac is a '''minimalistic''' approach to '''web-based''' management of
    4 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.
     3= Design Ideas around a dploy.org project =
    54
    6 All aspects of Trac have been designed with the single goal to
    7 '''help developers write great software''' while '''staying out of the way'''
    8 and imposing as little as possible on a team's established process and
    9 culture.
     5Currently we have great pieces of software such as [http://linuxcoe.sourceforge.net LinuxCOE] and [http://www.mondorescue.org MondoRescue] to manage server deployment from an automatic installation manner or from an imaging manner respectively (multi-distro support in both case). I'll later use the word deployment meaning both scenarios.
    106
    11 As all Wiki pages, this page is editable, this means that you can
    12 modify the contents of this page simply by using your
    13 web-browser. Simply click on the "Edit this page" link at the bottom
    14 of the page. WikiFormatting will give you a detailed description of
    15 available Wiki formatting commands.
     7It would be great to associate the 2 software under a common GPL ombrella to create a multi-purpose deployment server that would allow:
    168
    17 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
    18 a new Trac environment, containing a default set of wiki pages and some sample
    19 data. This newly created environment also contains
    20 [wiki:TracGuide documentation] to help you get started with your project.
     9 * to deploy a known or unknown server with whatever method from a central place
     10 * to manage centraly in a database every information related to the machine deployed. The set of tables could be in a standalone database or integrated in other management platform which are open to such integration ([http://www.hp.com/go/hpsim HP SIM], [http://ocsinventory.sourceforge.net/index.php OCS Inventory]).
     11 * to take in account hardware particularities in the deployment (using manufacturer available tools and/or opensource tools)
     12 * give a standardized method on how to setup such a deployment server from scratch, including mirroring instruction and automatic mirror structure creation from a set of ISOs.
     13 * provide a web interface (what else :-) for the mangement of the systems deployed or to be deployed. Should work in both text and graphical environment for easiest usage (lynx compliant)
     14 * Modular approach of deployement (new features should be easily added)
     15 * architecture neutral (with initial support of i386, x86_64 and ia64), and of course distribution neutral.
    2116
    22 You can use [wiki:TracAdmin trac-admin] to configure
    23 [http://trac.edgewall.com/ Trac] to better fit your project, especially in
    24 regard to ''components'', ''versions'' and ''milestones''.
     17This 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.
    2518
     19= Technical ideas around a dploy.org project =
    2620
    27 TracGuide is a good place to start.
     21 * 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)
     22 * 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.
     23 * 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
     24 * 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.
     25 * following reboot of the server will trigger the installtion planned (deployment through LinuxCOE or image deployment with mondo)
     26 * Full support of proliant hardware (ILO - Raid - Firmware updates)
     27 * For security reason most of the scripts run as dploy user (not root)
    2828
    29 Enjoy! [[BR]]
    30 ''The Trac Team''
     29== Interface functions ==
    3130
    32 == Starting Points ==
     31 * list of servers (automatic addition of PXE based servers, manual addition for others)
     32 * assigning a task to a machine/group of machines
     33 * (proliant) manage already discovered servers (power on, off... ILO functions)
     34 * delete servers to restart discovery / installation
     35 * group servers to apply the same job to multiple servers
     36 * (proliant) firmware update
     37 * (proliant) link to admin page (2381)
     38 * link to webmin page (10000)
     39 * (proliant) link to ACU (started on demand before launching the interface)
     40 * launch any commands thru SSH (password or public key protected)
     41 * launch an imaging job
     42
     43== Proposed Requirements ==
     44
     45 * Perl
     46 * Perl DBI
     47 * dhcpd
     48 * MySQL, PostgreSQL or file
     49 * Perl CGI or TT
     50 * tftpd
     51 * pxelinux
     52
     53== Concerning trac ==
    3354
    3455 * TracGuide --  Built-in Documentation