tap-app maintenance : New instances for tap-app

As part of lebaran preparation Enterprise team adding new instance to tap-app.

Site infra team will create 4 new instances for tap-app since current tap-app is still use old method of instance provisioning and configuration.

Current tap version will be released to new instances and application will be stopped on old instances.

Important Note:

No hotfix / release tap-app should be done during maintenance window

Plan:

pre-tasks (on current tap-app cluster):

Change tag Name to old-tap-app-01 and old-tap-app-02
Change tag Cluster to old-tap-app
remove route53 record for tap-app-01.main.tvlk.cloud and tap-app-02.main.tvlk.cloud

New instances:

Create and configure 4 new instances of tap-app
Manually attach 4 new instance to ELB

Release to new instances

@irvan will release tap-app current version ( 2cbf414-enterprise-tap ) to new instances
After ensuring new instances are InService, @irvan will stop-tap at old instances
Site Infra will leave old-tap-app as backup for a week.

Impact:

TAP should still be accessible for end users between maintenance window; we don't expect any issue / downtime, if there is any, should be reported.

Duration:

40 minutes

Time:

Tuesday, 2017-05-16T14:45:00 (UTC+7)

Notes:

Please contact us on #site-infra-channel if after this maintenance you have problems with tap-app cluster.

Related ticket : https://29022131.atlassian.net/servicedesk/customer/portal/11/TOSD-1185