| 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. |
| | 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 :-) |
| | 10 | |
| | 11 | So 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). |
| | 12 | |
