[DRAFT] MoM Shared Staging Discussion with Accommodation Team
Hi everyone,
Thank you for your participation during shared staging discussion. Here are the summary:
- We’ll create a substitute of staging06 where each team maintaining their own services and databases on their own instances. Release team will own the process and temporarily own common services/ databases: tv, tap, mongodata, mongofb, and mongoview.
- This shared staging will be on tvlk-dev as temporary solution before site infra creating a new aws staging account which consists of one instance representing one cluster.
- The new process will be as followed:
- Each team will create their own partial release branch. Release team will create partial release branch for tv and tap. Backend infra will create release branch for common component changes.
- On a specific time, each team updating services, configs, and databases on each own instances.
- QE will run automated test and each team should run their own test
- Any fixes should be committed to respective branches
- Each commit in common component should be cherrypicked on develop branch. This commit can be cherrypicked by product teams to their own partial release branch.
- After release, the commit should be cherrypicked/ merged to develop.
- There should be more thorough documentation and strict checking on release dependency to enforce this new process.
- Build versioning may include commit timestamp to ease dependency checking.
- Release team should create a more detailed documentation for new release process based on the existing design and additional considerations during discussion.
- Step 1 will be creating shared staging
- This shared staging will only used for release and hotfix purpose. Stability is expected.
- Deploy config used will be the same with staging06 (Release)
- Currently pg, trip, tv, and tap is on progress. Target to be finished on 10 Feb.
- Each accom team can start by using image and ‘make like this’ from development/testing machine.
- Some hard code issues in accom still should be resolved.
- Some resources in accom team may be co-owned (e.g. hinv and hb, hotel data used by tera and coin, etc)
- Accom team will discuss time allocation and define ETA by Fri 3 Feb.
- Progress tracking on shared staging will be on https://docs.google.com/spreadsheets/d/1jEnRBfJf46tjGYyL7nnVpjA_M8zJuPXRKcdeaAWEx8Y/edit#gid=0
- Expected target will be on mid february considering currently staging06’s certificate is expired and renewal request has been rejected.
Action item from Accommodation:
- TERA create new staging servers: hnet-stg.test.tvlk.cloud, hdemand-stg.test.tvlk.cloud, hdist-stg.test.tvlk.cloud, lca-stg.test.tvlk.cloud
- CustSys & IP join together to create new staging servers: hinv-stg.test.tvlk.cloud, hb-stg.test.tvlk.cloud, hops-stg.test.tvlk.cloud, a database server (hinv-mongod-stg.test.tvlk.cloud?) to be used together with TERA
- Coin create new stating servers: ne-stg.test.tvlk.cloud, nei-stg.test.tvlk.cloud
- TERA to make sure that creating a new hotel in their server will be reflected to hinv
Design document:
Shared staging: https://docs.google.com/document/d/11ICdGIfr6mQc7b9MHj7fDiCI9pS0fIhUC4LdCPBIRQE/edit#
Release process: https://docs.google.com/document/d/1PwlIgVMWbH0X6F-MXtK6VHVvcSTxtuFPaEN0nIWXI2w/edit#heading=h.s4isvklrouma