• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 148
  • Last Modified:

Server Deployment Documentation

Hi,
I need some help with Server Deployment Documentation

I have been to interview where they ask me "What documentation do you use to deploy a server" or "What is your deployment procedure" ... the deployment could be a full server or a database or a web application but specifically how to deploy Linux Server in Production

Does anyone have a sample document they can share? Is it a Plan or Checklist or a template?

Please help,

Thanks
Zen
0
zen shaw
Asked:
zen shaw
  • 2
1 Solution
 
Zephyr ICTCloud ArchitectCommented:
I think these kinds of questions are to check if you know what is needed to configure a server, what the initial steps are, what you would specifically do, these can be different for any admins out there, something good to get started would be something like this maybe. That's security out of the way, next start listing things like slicing the disk or creating extra users...

Just make a list for yourself on what it is you would do after initial setup, memorise it somewhat so that you can list the things you do, the interviewer will check his list and see if you know what you are talking about. If it is more specific to webapps, see what you would do to initially secure the webserver, create specific directories and secure them, add users to these folders ... And so on.
0
 
zen shawAuthor Commented:
Thanks for the link.

I guess in process oriented companies they have Change Control Management and templates / plans to deploy servers or apps. I was looking for things they record and a sample doc.
0
 
Zephyr ICTCloud ArchitectCommented:
Yes of course they have Change Management, and they use some form of CM tool or use templates to fill in what will be changed, what the impact is etc... That's a tad different than a deployment procedure. Change Management is a process, you record what the change is, what the impact will be, rollback plan in case things go south, the engineer that does the implementation usually has to give his estimate on the impact though, so that's an important factor, he also has to have a plan to roll back to a previous state, so mentioning of backups from the "before" situation will score points (or an alternative like a snapshot in a virtual environment). Communication, who will be contacted for what, who is responsible for what ... And so on.

There are documents out there that can give you an idea of Change Management processes, specific deployment documents are out there, but for now I found this or something like this more specific to implementation or deployment...
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now