teraapi.traveloka.com Alias Migration
Please refer to SSOT Document for more details (check list, plan, etc.)
Background
As part of multi-account project, we're ready to try to migrate our teraapi.traveloka.com load balancer alias from tvlk-prod to tvlk-ast-prod.
Currently we have one alias behind teraapi.traveloka.com which targets hnet load balancer in tvlk-prod. Meaning that all traffics coming to this URL will go to tvlk-prod/hnet service.
Preparation
- Add weight value of 100 into existing alias
- Create new alias with weight value of 0, targeting astcnt load balancer in tvlk-ast-prod
- At this step, all traffics would still go to tvlk-prod/hnet service in the end (no behavior changes)
- Existing alias (tvlk-prod/hnet) weight value = 100
- New alias (tvlk-ast-prod/astcnt) weight value = 0
Transition and Migration Plan
- Increase new alias weight value to 1 and existing alias weight value to 99
- Meaning 1% traffics would go to tvlk-ast-prod/astcnt
- Monitor for any anomalies and until ready to go to next step
- New alias = 10, existing alias = 90
- 10% traffics would go to tvlk-ast-prod/astcnt
- Monitor
- Repeat...
- Until new alias = 100 and existing alias = 0
When
- 29-Jan-2020
- Execute all preparation steps
- Try to 1% traffic from migration plan
- 30-Jan-2020
- Continue to 50% traffic
- Until 100% traffic
Affected Clients
Risk
- New exception in tvlk-ast-prod/astcnt service
- Connectivity error between clients and tvlk-ast-prod/astcnt service
Mitigation
- Set weight value of new alias to 0 and existing alias to 100
- All traffics should be back to tvlk-prod/hnet
PIC
@micky