Devops Onboarding

For the actual onboarding process, please refer to Gitbook.

The following page is to document personal steps taken to onboard to Harmony’s engineering team. If you have refered to Gitbook, you may have noticed that some of the information have been outdated (eng team should update in the near future). Along with its immense amount of information and the use of various tech stacks (> 15), it might not be easy to determine where to start. Referencing the steps I have taken can provide hints on the process, thus is the reason for this page.

My first task for Harmony was to verify and validate the cost and utilization for all of our services. Harmony’s services are currently located in various cloud providers (AWS, Digital Ocean, Hetzner and Latitude). Each cloud providers have different interfaces and data models. All of the above information were only known by the Devops team. Nothing was documented so everytime someone had questions regarding the cloud costs, they needed to reach out to the Devops team.

In order to solve the inefficiency, I have documented cost, utilization, status, and projections for each cloud provider (/e). Analyzing different instances in the cloud providers helped me understand Harmony’s network structure. Knowing the location of the instances, current cost situation and migration / termination projections will really assist in understanding the architecture.

I have also developed a program to automate the process of accumulating all the project costs for different cloud providers (cloud-cost in github).