Is there a better way to do environment validation? Usecase is a virtualized environment nearing 300 servers created by someone else, and need to validate before accept them (i.e. before I install custom software and find issues after-the-fact).
These are all currently done manually with a paper checklist
- ssh to a linux server [ this is so the following tests are run from the box ]
- for each server it communicates with:
- ping -c 20 X target servers that the linux server is expected to communicate, review packet loss and RTT avg/max/deviation
- telnet target servers to make sure the appropriate ports are open and accessible for the services they offer (i.e. 1433 sql server, 3306 mysql, 80 webservice, 25 smtp)
- nslookup to make sure the server is setup on the DNS.
Is there a better way to do system validation?
These are all currently done manually with a paper checklist
- ssh to linux server
cat /proc/cpuinfo
to review if cpu core count and clock speed are what was requesteddf
to check diskspace allocatedfree -m
to check memory amount
Are there examples of a better approach, such as setting expected values or ranges in the checks then simply run 'all' tests for pass/fail checking?