DevOps Role = Automation Engineers + Ops + Quality Engineers + Security/Network
Characteristics Of DevOps Work:
- Different projects/products usually have many similar requirements or overlapped tasks.
- Most tasks are off the record and trivial to plan, therefore hard to track effort for credit in-return
- If fail to foresee potential risks of critical envs, DevOps life can easily be frustrating and fruitless.
- All team members may contact with DevOps, so watch out low efficiency of communication.
Note: Percentage means how easy we can get the task done offline without intensive communication.
| Name | Comment |
|---|---|
| DevOps Guide | Guide links for questions frequently asked by dev team |
| DevOps Common libraries | Scripts and common libraries for DevOps daily work |
| DevOps Process Template | Routine DevOps work provide reusable process template |
| DevOps TechStack | Tech stack people should be familiar with, when doing DevOps |
| DevOps BusinessValue | What business values do DevOps mean to customers |
| DevOps Consultant | Experience for doing DevOps Consultant |
We maintain current github repo, in hope of:
- Standardize routine work with minimum effort and maximum output.
- Separate what tasks need intensive communication/prompt response from those don't
- Measure key tasks by statistics and generate visualize report.
- Figure out a way to keep things/tasks in order and properly tracked
- Interest
- Adaptive to change and comfortable to play with latest technology
- Strong desire to automate any routine work
- Trouble shooting skills
Link Of Current Page: https://github.com/DennyZhang/devops-knowledgebase