<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jonathan points out that it needs good configuration reporting capabilities:<div><br><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><br>The other requirement that needs to be there is reporting ablity. One of things that Landscape is currently lacking from what I have heard. The ability to manage a large group of computers, report back on the inventory of the machine (hardware, software, users) and create custom reports for the entire enterprise. An example: Give me all of my servers that have X amount of RAM, plus available slots to put more memory in. </div> <div> </div> <div>Also once this tool is created, expand it more importanlty to my clients. So now I can have one piece of management software that I can manage my entire infrastructre across and deploy patches, install software, setup, create and deploy confirautions and report across the entire enterprise. You get that piece of software that is open source and you will find on of the critical holes.</div> <div> </div> <div>Jonathan</div></blockquote></div><br></div><div><br></div><div>So here are the general requirements so far:</div><div><br>1) Optional - must not be required for Ubuntu Server<br>2) Secure - must not have known security issues, must have good known security architecture<br>3) Scalable - must be able to administer sets of machines<br>4) Open Source<br>5) Easy to use (and setup*) - for 1 or more machines<br></div><div>* I just added the the "setup" part. It seems like that is pretty important for a single machine use case. If people have to spend a lot of time just getting it working for a single machine then it isn't going to get much acceptance.</div><div><br></div><div>And these are the major feature categories:</div><div><br></div><div>1) Package management<br>2) User management<br>3) Security updates<br>4) Repository management<br>5) System monitoring<br>7) Service management (starting/stopping/monitoring)<br>8) Service configuring<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- router<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- dhcp<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- web<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- dns<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- firewall<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- ids - snort<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- ect...<br>9) Change management<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- track changes<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- control changes<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- rollback changes<br>10) Configuration reporting</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- HW<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- SW<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Users<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Global custom reports<br></div><div><br></div><div><br></div></body></html>