As part of the handover of our linux application server automated builds I would like to produce a high level "handover document" which captures the key functions and config items. (This is more of a admin process thing, rather than having a useful technical function) (ie it is a snap shot in time, the source of the data is possibly some export script, notes, or configuration management like chef)
A while back, I did some work for a UK government agency to install and configure an application on a linux server, and they provided a standard template which had sections for various configuration items, which presumably they could lodge in some Document management system. Unfortunately I didn't keep a copy of the sections.
Really this should be considered much like a server "resume", just enough to prime a knowledgeable technical user with the important facts about the server.
Quick brain dump, gave the following categories and values;
XXX is configured as a Web service for the YYY for customer ZZZ
public ipv4: 18.104.22.168 hostname: myserver.mynetwork.country.com OS: MyMonkey Linux 0.1 ???
Service port network sshd 22 public httpd 80 public mysqld 3306 localhost
(this is usually going to be some web app)
Platform: PHP 5.3, mysql public URL: http://someplcae.com/wefwefwef log file location: /var/log/httpd/whatever.log
Admin Interface admin URL admin username admin password?
selinux: Enabled SSH Root Login: Disabled SSH password auth: Enabled Compliance Level: None
Package Updates: Manual
OS level Configuration
Mounted Storage: None kernel parameters: None
Software: None Storage: None
Is there anything else that you would want to see in a high level document, if I was handing the server over to you?