• March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
    • Please inform all marketing team members about the same
  • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
  • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
  • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
  • March 27th, Wednesday 10:30 am IST is the down time
  • We need to stop lead processing – Rajesh
    • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
  • Pre warm steps:
    • EC2 is up and running with latest wordpress database
    • WordPress is pointed to new RDS
    • Lead database is empty
    • Setup new ELB
    • Setup EFS
    • Setup memcached
    • Check the URL used by Jenkins (Senthil)
    • Check Redirection plugin database
    • Check S3
    • Check Cron jobs
    • Check large content pasting
    • Run `wp cron event run –due-now`

 

  • During the downtime, steps:
    • Stop Jenkins jobs – Done
    • Make a note of the last  lead id – 116456
    • Migrate the db
    • Update the route53 DNS to new ELB.
    • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
    • Remove the old machine from ELB
    • Shutdown the existing EC2 and RDS machines
    • Plan the test case during the down time
      • Check if S3 integration is working fine (upload images)
      • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
    • We have to take cdn live (cdn5.enchantingtravels.com)
    • We need to enable the wp cron

 

  • Once downtime is over
    • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
    • Start the Jenkins lead processing again
    • Add the EZ backup script for backup
    • Update copperegg
    • Update papertrail
    • Configure the BCP AMI backup

 

  • After one week
    • Terminate the EC2, EFS, Memcached and RDS machines

 

Open questions

  • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

 

  • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
    • Please inform all marketing team members about the same
  • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
  • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
  • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
  • March 27th, Wednesday 10:30 am IST is the down time
  • We need to stop lead processing – Rajesh
    • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
  • Pre warm steps:
    • EC2 is up and running with latest wordpress database
    • WordPress is pointed to new RDS
    • Lead database is empty
    • Setup new ELB
    • Setup EFS
    • Setup memcached
    • Check the URL used by Jenkins (Senthil)
    • Check Redirection plugin database
    • Check S3
    • Check Cron jobs
    • Check large content pasting
    • Run `wp cron event run –due-now`

 

  • During the downtime, steps:
    • Stop Jenkins jobs – Done
    • Make a note of the last  lead id – 116456
    • Migrate the db
    • Update the route53 DNS to new ELB.
    • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
    • Remove the old machine from ELB
    • Shutdown the existing EC2 and RDS machines
    • Plan the test case during the down time
      • Check if S3 integration is working fine (upload images)
      • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
    • We have to take cdn live (cdn5.enchantingtravels.com)
    • We need to enable the wp cron

 

  • Once downtime is over
    • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
    • Start the Jenkins lead processing again
    • Add the EZ backup script for backup
    • Update copperegg
    • Update papertrail
    • Configure the BCP AMI backup

 

  • After one week
    • Terminate the EC2, EFS, Memcached and RDS machines

 

Open questions

  • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
    • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
      • Please inform all marketing team members about the same
    • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
    • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
    • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
    • March 27th, Wednesday 10:30 am IST is the down time
    • We need to stop lead processing – Rajesh
      • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
    • Pre warm steps:
      • EC2 is up and running with latest wordpress database
      • WordPress is pointed to new RDS
      • Lead database is empty
      • Setup new ELB
      • Setup EFS
      • Setup memcached
      • Check the URL used by Jenkins (Senthil)
      • Check Redirection plugin database
      • Check S3
      • Check Cron jobs
      • Check large content pasting
      • Run `wp cron event run –due-now`
    • During the downtime, steps:
      • Stop Jenkins jobs – Done
      • Make a note of the last  lead id – 116456
      • Migrate the db
      • Update the route53 DNS to new ELB.
      • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
      • Remove the old machine from ELB
      • Shutdown the existing EC2 and RDS machines
      • Plan the test case during the down time
        • Check if S3 integration is working fine (upload images)
        • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
      • We have to take cdn live (cdn5.enchantingtravels.com)
      • We need to enable the wp cron
    • Once downtime is over
      • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
      • Start the Jenkins lead processing again
      • Add the EZ backup script for backup
      • Update copperegg
      • Update papertrail
      • Configure the BCP AMI backup
    • After one week
      • Terminate the EC2, EFS, Memcached and RDS machines

    Open questions

    • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
      • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
        • Please inform all marketing team members about the same
      • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
      • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
      • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
      • March 27th, Wednesday 10:30 am IST is the down time
      • We need to stop lead processing – Rajesh
        • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
      • Pre warm steps:
        • EC2 is up and running with latest wordpress database
        • WordPress is pointed to new RDS
        • Lead database is empty
        • Setup new ELB
        • Setup EFS
        • Setup memcached
        • Check the URL used by Jenkins (Senthil)
        • Check Redirection plugin database
        • Check S3
        • Check Cron jobs
        • Check large content pasting
        • Run `wp cron event run –due-now`
      • During the downtime, steps:
        • Stop Jenkins jobs – Done
        • Make a note of the last  lead id – 116456
        • Migrate the db
        • Update the route53 DNS to new ELB.
        • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
        • Remove the old machine from ELB
        • Shutdown the existing EC2 and RDS machines
        • Plan the test case during the down time
          • Check if S3 integration is working fine (upload images)
          • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
        • We have to take cdn live (cdn5.enchantingtravels.com)
        • We need to enable the wp cron
      • Once downtime is over
        • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
        • Start the Jenkins lead processing again
        • Add the EZ backup script for backup
        • Update copperegg
        • Update papertrail
        • Configure the BCP AMI backup
      • After one week
        • Terminate the EC2, EFS, Memcached and RDS machines

      Open questions

      • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
        • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
          • Please inform all marketing team members about the same
        • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
        • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
        • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
        • March 27th, Wednesday 10:30 am IST is the down time
        • We need to stop lead processing – Rajesh
          • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
        • Pre warm steps:
          • EC2 is up and running with latest wordpress database
          • WordPress is pointed to new RDS
          • Lead database is empty
          • Setup new ELB
          • Setup EFS
          • Setup memcached
          • Check the URL used by Jenkins (Senthil)
          • Check Redirection plugin database
          • Check S3
          • Check Cron jobs
          • Check large content pasting
          • Run `wp cron event run –due-now`
        • During the downtime, steps:
          • Stop Jenkins jobs – Done
          • Make a note of the last  lead id – 116456
          • Migrate the db
          • Update the route53 DNS to new ELB.
          • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
          • Remove the old machine from ELB
          • Shutdown the existing EC2 and RDS machines
          • Plan the test case during the down time
            • Check if S3 integration is working fine (upload images)
            • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
          • We have to take cdn live (cdn5.enchantingtravels.com)
          • We need to enable the wp cron
        • Once downtime is over
          • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
          • Start the Jenkins lead processing again
          • Add the EZ backup script for backup
          • Update copperegg
          • Update papertrail
          • Configure the BCP AMI backup
        • After one week
          • Terminate the EC2, EFS, Memcached and RDS machines

        Open questions

        • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
          • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
            • Please inform all marketing team members about the same
          • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
          • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
          • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
          • March 27th, Wednesday 10:30 am IST is the down time
          • We need to stop lead processing – Rajesh
            • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
          • Pre warm steps:
            • EC2 is up and running with latest wordpress database
            • WordPress is pointed to new RDS
            • Lead database is empty
            • Setup new ELB
            • Setup EFS
            • Setup memcached
            • Check the URL used by Jenkins (Senthil)
            • Check Redirection plugin database
            • Check S3
            • Check Cron jobs
            • Check large content pasting
            • Run `wp cron event run –due-now`
          • During the downtime, steps:
            • Stop Jenkins jobs – Done
            • Make a note of the last  lead id – 116456
            • Migrate the db
            • Update the route53 DNS to new ELB.
            • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
            • Remove the old machine from ELB
            • Shutdown the existing EC2 and RDS machines
            • Plan the test case during the down time
              • Check if S3 integration is working fine (upload images)
              • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
            • We have to take cdn live (cdn5.enchantingtravels.com)
            • We need to enable the wp cron
          • Once downtime is over
            • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
            • Start the Jenkins lead processing again
            • Add the EZ backup script for backup
            • Update copperegg
            • Update papertrail
            • Configure the BCP AMI backup
          • After one week
            • Terminate the EC2, EFS, Memcached and RDS machines

          Open questions

          • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
            • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              • Please inform all marketing team members about the same
            • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
            • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
            • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
            • March 27th, Wednesday 10:30 am IST is the down time
            • We need to stop lead processing – Rajesh
              • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
            • Pre warm steps:
              • EC2 is up and running with latest wordpress database
              • WordPress is pointed to new RDS
              • Lead database is empty
              • Setup new ELB
              • Setup EFS
              • Setup memcached
              • Check the URL used by Jenkins (Senthil)
              • Check Redirection plugin database
              • Check S3
              • Check Cron jobs
              • Check large content pasting
              • Run `wp cron event run –due-now`
            • During the downtime, steps:
              • Stop Jenkins jobs – Done
              • Make a note of the last  lead id – 116456
              • Migrate the db
              • Update the route53 DNS to new ELB.
              • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              • Remove the old machine from ELB
              • Shutdown the existing EC2 and RDS machines
              • Plan the test case during the down time
                • Check if S3 integration is working fine (upload images)
                • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
              • We have to take cdn live (cdn5.enchantingtravels.com)
              • We need to enable the wp cron
            • Once downtime is over
              • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
              • Start the Jenkins lead processing again
              • Add the EZ backup script for backup
              • Update copperegg
              • Update papertrail
              • Configure the BCP AMI backup
            • After one week
              • Terminate the EC2, EFS, Memcached and RDS machines

            Open questions

            • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
              • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                • Please inform all marketing team members about the same
              • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
              • March 27th, Wednesday 10:30 am IST is the down time
              • We need to stop lead processing – Rajesh
                • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              • Pre warm steps:
                • EC2 is up and running with latest wordpress database
                • WordPress is pointed to new RDS
                • Lead database is empty
                • Setup new ELB
                • Setup EFS
                • Setup memcached
                • Check the URL used by Jenkins (Senthil)
                • Check Redirection plugin database
                • Check S3
                • Check Cron jobs
                • Check large content pasting
                • Run `wp cron event run –due-now`
              • During the downtime, steps:
                • Stop Jenkins jobs – Done
                • Make a note of the last  lead id – 116456
                • Migrate the db
                • Update the route53 DNS to new ELB.
                • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                • Remove the old machine from ELB
                • Shutdown the existing EC2 and RDS machines
                • Plan the test case during the down time
                  • Check if S3 integration is working fine (upload images)
                  • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                • We have to take cdn live (cdn5.enchantingtravels.com)
                • We need to enable the wp cron
              • Once downtime is over
                • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                • Start the Jenkins lead processing again
                • Add the EZ backup script for backup
                • Update copperegg
                • Update papertrail
                • Configure the BCP AMI backup
              • After one week
                • Terminate the EC2, EFS, Memcached and RDS machines
              • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                • Please inform all marketing team members about the same
              • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
              • March 27th, Wednesday 10:30 am IST is the down time
              • We need to stop lead processing – Rajesh
                • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              • Pre warm steps:
                • EC2 is up and running with latest wordpress database
                • WordPress is pointed to new RDS
                • Lead database is empty
                • Setup new ELB
                • Setup EFS
                • Setup memcached
                • Check the URL used by Jenkins (Senthil)
                • Check Redirection plugin database
                • Check S3
                • Check Cron jobs
                • Check large content pasting
                • Run `wp cron event run –due-now`
              • During the downtime, steps:
                • Stop Jenkins jobs – Done
                • Make a note of the last  lead id – 116456
                • Migrate the db
                • Update the route53 DNS to new ELB.
                • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                • Remove the old machine from ELB
                • Shutdown the existing EC2 and RDS machines
                • Plan the test case during the down time
                  • Check if S3 integration is working fine (upload images)
                  • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                • We have to take cdn live (cdn5.enchantingtravels.com)
                • We need to enable the wp cron
              • Once downtime is over
                • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                • Start the Jenkins lead processing again
                • Add the EZ backup script for backup
                • Update copperegg
                • Update papertrail
                • Configure the BCP AMI backup
              • After one week
                • Terminate the EC2, EFS, Memcached and RDS machines

              Open questions

              • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                  • Please inform all marketing team members about the same
                • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                • March 27th, Wednesday 10:30 am IST is the down time
                • We need to stop lead processing – Rajesh
                  • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                • Pre warm steps:
                  • EC2 is up and running with latest wordpress database
                  • WordPress is pointed to new RDS
                  • Lead database is empty
                  • Setup new ELB
                  • Setup EFS
                  • Setup memcached
                  • Check the URL used by Jenkins (Senthil)
                  • Check Redirection plugin database
                  • Check S3
                  • Check Cron jobs
                  • Check large content pasting
                  • Run `wp cron event run –due-now`
                • During the downtime, steps:
                  • Stop Jenkins jobs – Done
                  • Make a note of the last  lead id – 116456
                  • Migrate the db
                  • Update the route53 DNS to new ELB.
                  • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                  • Remove the old machine from ELB
                  • Shutdown the existing EC2 and RDS machines
                  • Plan the test case during the down time
                    • Check if S3 integration is working fine (upload images)
                    • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                  • We have to take cdn live (cdn5.enchantingtravels.com)
                  • We need to enable the wp cron
                • Once downtime is over
                  • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                  • Start the Jenkins lead processing again
                  • Add the EZ backup script for backup
                  • Update copperegg
                  • Update papertrail
                  • Configure the BCP AMI backup
                • After one week
                  • Terminate the EC2, EFS, Memcached and RDS machines

                Open questions

                • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              Open questions

              • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
              • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                • Please inform all marketing team members about the same
              • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
              • March 27th, Wednesday 10:30 am IST is the down time
              • We need to stop lead processing – Rajesh
                • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              • Pre warm steps:
                • EC2 is up and running with latest wordpress database
                • WordPress is pointed to new RDS
                • Lead database is empty
                • Setup new ELB
                • Setup EFS
                • Setup memcached
                • Check the URL used by Jenkins (Senthil)
                • Check Redirection plugin database
                • Check S3
                • Check Cron jobs
                • Check large content pasting
                • Run `wp cron event run –due-now`
              • During the downtime, steps:
                • Stop Jenkins jobs – Done
                • Make a note of the last  lead id – 116456
                • Migrate the db
                • Update the route53 DNS to new ELB.
                • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                • Remove the old machine from ELB
                • Shutdown the existing EC2 and RDS machines
                • Plan the test case during the down time
                  • Check if S3 integration is working fine (upload images)
                  • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                • We have to take cdn live (cdn5.enchantingtravels.com)
                • We need to enable the wp cron
              • Once downtime is over
                • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                • Start the Jenkins lead processing again
                • Add the EZ backup script for backup
                • Update copperegg
                • Update papertrail
                • Configure the BCP AMI backup
              • After one week
                • Terminate the EC2, EFS, Memcached and RDS machines

              Open questions

              • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                  • Please inform all marketing team members about the same
                • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                • March 27th, Wednesday 10:30 am IST is the down time
                • We need to stop lead processing – Rajesh
                  • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                • Pre warm steps:
                  • EC2 is up and running with latest wordpress database
                  • WordPress is pointed to new RDS
                  • Lead database is empty
                  • Setup new ELB
                  • Setup EFS
                  • Setup memcached
                  • Check the URL used by Jenkins (Senthil)
                  • Check Redirection plugin database
                  • Check S3
                  • Check Cron jobs
                  • Check large content pasting
                  • Run `wp cron event run –due-now`
                • During the downtime, steps:
                  • Stop Jenkins jobs – Done
                  • Make a note of the last  lead id – 116456
                  • Migrate the db
                  • Update the route53 DNS to new ELB.
                  • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                  • Remove the old machine from ELB
                  • Shutdown the existing EC2 and RDS machines
                  • Plan the test case during the down time
                    • Check if S3 integration is working fine (upload images)
                    • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                  • We have to take cdn live (cdn5.enchantingtravels.com)
                  • We need to enable the wp cron
                • Once downtime is over
                  • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                  • Start the Jenkins lead processing again
                  • Add the EZ backup script for backup
                  • Update copperegg
                  • Update papertrail
                  • Configure the BCP AMI backup
                • After one week
                  • Terminate the EC2, EFS, Memcached and RDS machines

                Open questions

                • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                  • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                    • Please inform all marketing team members about the same
                  • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                  • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                  • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                  • March 27th, Wednesday 10:30 am IST is the down time
                  • We need to stop lead processing – Rajesh
                    • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                  • Pre warm steps:
                    • EC2 is up and running with latest wordpress database
                    • WordPress is pointed to new RDS
                    • Lead database is empty
                    • Setup new ELB
                    • Setup EFS
                    • Setup memcached
                    • Check the URL used by Jenkins (Senthil)
                    • Check Redirection plugin database
                    • Check S3
                    • Check Cron jobs
                    • Check large content pasting
                    • Run `wp cron event run –due-now`
                  • During the downtime, steps:
                    • Stop Jenkins jobs – Done
                    • Make a note of the last  lead id – 116456
                    • Migrate the db
                    • Update the route53 DNS to new ELB.
                    • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                    • Remove the old machine from ELB
                    • Shutdown the existing EC2 and RDS machines
                    • Plan the test case during the down time
                      • Check if S3 integration is working fine (upload images)
                      • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                    • We have to take cdn live (cdn5.enchantingtravels.com)
                    • We need to enable the wp cron
                  • Once downtime is over
                    • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                    • Start the Jenkins lead processing again
                    • Add the EZ backup script for backup
                    • Update copperegg
                    • Update papertrail
                    • Configure the BCP AMI backup
                  • After one week
                    • Terminate the EC2, EFS, Memcached and RDS machines

                  Open questions

                  • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                    • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                      • Please inform all marketing team members about the same
                    • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                    • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                    • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                    • March 27th, Wednesday 10:30 am IST is the down time
                    • We need to stop lead processing – Rajesh
                      • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                    • Pre warm steps:
                      • EC2 is up and running with latest wordpress database
                      • WordPress is pointed to new RDS
                      • Lead database is empty
                      • Setup new ELB
                      • Setup EFS
                      • Setup memcached
                      • Check the URL used by Jenkins (Senthil)
                      • Check Redirection plugin database
                      • Check S3
                      • Check Cron jobs
                      • Check large content pasting
                      • Run `wp cron event run –due-now`
                    • During the downtime, steps:
                      • Stop Jenkins jobs – Done
                      • Make a note of the last  lead id – 116456
                      • Migrate the db
                      • Update the route53 DNS to new ELB.
                      • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                      • Remove the old machine from ELB
                      • Shutdown the existing EC2 and RDS machines
                      • Plan the test case during the down time
                        • Check if S3 integration is working fine (upload images)
                        • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                      • We have to take cdn live (cdn5.enchantingtravels.com)
                      • We need to enable the wp cron
                    • Once downtime is over
                      • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                      • Start the Jenkins lead processing again
                      • Add the EZ backup script for backup
                      • Update copperegg
                      • Update papertrail
                      • Configure the BCP AMI backup
                    • After one week
                      • Terminate the EC2, EFS, Memcached and RDS machines

                    Open questions

                    • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                      • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                        • Please inform all marketing team members about the same
                      • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                      • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                      • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                      • March 27th, Wednesday 10:30 am IST is the down time
                      • We need to stop lead processing – Rajesh
                        • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                      • Pre warm steps:
                        • EC2 is up and running with latest wordpress database
                        • WordPress is pointed to new RDS
                        • Lead database is empty
                        • Setup new ELB
                        • Setup EFS
                        • Setup memcached
                        • Check the URL used by Jenkins (Senthil)
                        • Check Redirection plugin database
                        • Check S3
                        • Check Cron jobs
                        • Check large content pasting
                        • Run `wp cron event run –due-now`
                      • During the downtime, steps:
                        • Stop Jenkins jobs – Done
                        • Make a note of the last  lead id – 116456
                        • Migrate the db
                        • Update the route53 DNS to new ELB.
                        • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                        • Remove the old machine from ELB
                        • Shutdown the existing EC2 and RDS machines
                        • Plan the test case during the down time
                          • Check if S3 integration is working fine (upload images)
                          • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                        • We have to take cdn live (cdn5.enchantingtravels.com)
                        • We need to enable the wp cron
                      • Once downtime is over
                        • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                        • Start the Jenkins lead processing again
                        • Add the EZ backup script for backup
                        • Update copperegg
                        • Update papertrail
                        • Configure the BCP AMI backup
                      • After one week
                        • Terminate the EC2, EFS, Memcached and RDS machines

                      Open questions

                      • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                        • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                          • Please inform all marketing team members about the same
                        • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                        • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                        • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                        • March 27th, Wednesday 10:30 am IST is the down time
                        • We need to stop lead processing – Rajesh
                          • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                        • Pre warm steps:
                          • EC2 is up and running with latest wordpress database
                          • WordPress is pointed to new RDS
                          • Lead database is empty
                          • Setup new ELB
                          • Setup EFS
                          • Setup memcached
                          • Check the URL used by Jenkins (Senthil)
                          • Check Redirection plugin database
                          • Check S3
                          • Check Cron jobs
                          • Check large content pasting
                          • Run `wp cron event run –due-now`
                        • During the downtime, steps:
                          • Stop Jenkins jobs – Done
                          • Make a note of the last  lead id – 116456
                          • Migrate the db
                          • Update the route53 DNS to new ELB.
                          • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                          • Remove the old machine from ELB
                          • Shutdown the existing EC2 and RDS machines
                          • Plan the test case during the down time
                            • Check if S3 integration is working fine (upload images)
                            • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                          • We have to take cdn live (cdn5.enchantingtravels.com)
                          • We need to enable the wp cron
                        • Once downtime is over
                          • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                          • Start the Jenkins lead processing again
                          • Add the EZ backup script for backup
                          • Update copperegg
                          • Update papertrail
                          • Configure the BCP AMI backup
                        • After one week
                          • Terminate the EC2, EFS, Memcached and RDS machines

                        Open questions

                        • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
          • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
            • Please inform all marketing team members about the same
          • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
          • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
          • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
          • March 27th, Wednesday 10:30 am IST is the down time
          • We need to stop lead processing – Rajesh
            • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
          • Pre warm steps:
            • EC2 is up and running with latest wordpress database
            • WordPress is pointed to new RDS
            • Lead database is empty
            • Setup new ELB
            • Setup EFS
            • Setup memcached
            • Check the URL used by Jenkins (Senthil)
            • Check Redirection plugin database
            • Check S3
            • Check Cron jobs
            • Check large content pasting
            • Run `wp cron event run –due-now`
          • During the downtime, steps:
            • Stop Jenkins jobs – Done
            • Make a note of the last  lead id – 116456
            • Migrate the db
            • Update the route53 DNS to new ELB.
            • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
            • Remove the old machine from ELB
            • Shutdown the existing EC2 and RDS machines
            • Plan the test case during the down time
              • Check if S3 integration is working fine (upload images)
              • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
            • We have to take cdn live (cdn5.enchantingtravels.com)
            • We need to enable the wp cron
          • Once downtime is over
            • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
            • Start the Jenkins lead processing again
            • Add the EZ backup script for backup
            • Update copperegg
            • Update papertrail
            • Configure the BCP AMI backup
          • After one week
            • Terminate the EC2, EFS, Memcached and RDS machines

          Open questions

          • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
            • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              • Please inform all marketing team members about the same
            • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
            • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
            • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
            • March 27th, Wednesday 10:30 am IST is the down time
            • We need to stop lead processing – Rajesh
              • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
            • Pre warm steps:
              • EC2 is up and running with latest wordpress database
              • WordPress is pointed to new RDS
              • Lead database is empty
              • Setup new ELB
              • Setup EFS
              • Setup memcached
              • Check the URL used by Jenkins (Senthil)
              • Check Redirection plugin database
              • Check S3
              • Check Cron jobs
              • Check large content pasting
              • Run `wp cron event run –due-now`
            • During the downtime, steps:
              • Stop Jenkins jobs – Done
              • Make a note of the last  lead id – 116456
              • Migrate the db
              • Update the route53 DNS to new ELB.
              • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              • Remove the old machine from ELB
              • Shutdown the existing EC2 and RDS machines
              • Plan the test case during the down time
                • Check if S3 integration is working fine (upload images)
                • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
              • We have to take cdn live (cdn5.enchantingtravels.com)
              • We need to enable the wp cron
            • Once downtime is over
              • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
              • Start the Jenkins lead processing again
              • Add the EZ backup script for backup
              • Update copperegg
              • Update papertrail
              • Configure the BCP AMI backup
            • After one week
              • Terminate the EC2, EFS, Memcached and RDS machines

            Open questions

            • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
              • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                • Please inform all marketing team members about the same
              • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
              • March 27th, Wednesday 10:30 am IST is the down time
              • We need to stop lead processing – Rajesh
                • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              • Pre warm steps:
                • EC2 is up and running with latest wordpress database
                • WordPress is pointed to new RDS
                • Lead database is empty
                • Setup new ELB
                • Setup EFS
                • Setup memcached
                • Check the URL used by Jenkins (Senthil)
                • Check Redirection plugin database
                • Check S3
                • Check Cron jobs
                • Check large content pasting
                • Run `wp cron event run –due-now`
              • During the downtime, steps:
                • Stop Jenkins jobs – Done
                • Make a note of the last  lead id – 116456
                • Migrate the db
                • Update the route53 DNS to new ELB.
                • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                • Remove the old machine from ELB
                • Shutdown the existing EC2 and RDS machines
                • Plan the test case during the down time
                  • Check if S3 integration is working fine (upload images)
                  • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                • We have to take cdn live (cdn5.enchantingtravels.com)
                • We need to enable the wp cron
              • Once downtime is over
                • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                • Start the Jenkins lead processing again
                • Add the EZ backup script for backup
                • Update copperegg
                • Update papertrail
                • Configure the BCP AMI backup
              • After one week
                • Terminate the EC2, EFS, Memcached and RDS machines

              Open questions

              • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                  • Please inform all marketing team members about the same
                • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                • March 27th, Wednesday 10:30 am IST is the down time
                • We need to stop lead processing – Rajesh
                  • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                • Pre warm steps:
                  • EC2 is up and running with latest wordpress database
                  • WordPress is pointed to new RDS
                  • Lead database is empty
                  • Setup new ELB
                  • Setup EFS
                  • Setup memcached
                  • Check the URL used by Jenkins (Senthil)
                  • Check Redirection plugin database
                  • Check S3
                  • Check Cron jobs
                  • Check large content pasting
                  • Run `wp cron event run –due-now`
                • During the downtime, steps:
                  • Stop Jenkins jobs – Done
                  • Make a note of the last  lead id – 116456
                  • Migrate the db
                  • Update the route53 DNS to new ELB.
                  • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                  • Remove the old machine from ELB
                  • Shutdown the existing EC2 and RDS machines
                  • Plan the test case during the down time
                    • Check if S3 integration is working fine (upload images)
                    • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                  • We have to take cdn live (cdn5.enchantingtravels.com)
                  • We need to enable the wp cron
                • Once downtime is over
                  • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                  • Start the Jenkins lead processing again
                  • Add the EZ backup script for backup
                  • Update copperegg
                  • Update papertrail
                  • Configure the BCP AMI backup
                • After one week
                  • Terminate the EC2, EFS, Memcached and RDS machines

                Open questions

                • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
              • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                • Please inform all marketing team members about the same
              • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
              • March 27th, Wednesday 10:30 am IST is the down time
              • We need to stop lead processing – Rajesh
                • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              • Pre warm steps:
                • EC2 is up and running with latest wordpress database
                • WordPress is pointed to new RDS
                • Lead database is empty
                • Setup new ELB
                • Setup EFS
                • Setup memcached
                • Check the URL used by Jenkins (Senthil)
                • Check Redirection plugin database
                • Check S3
                • Check Cron jobs
                • Check large content pasting
                • Run `wp cron event run –due-now`
              • During the downtime, steps:
                • Stop Jenkins jobs – Done
                • Make a note of the last  lead id – 116456
                • Migrate the db
                • Update the route53 DNS to new ELB.
                • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                • Remove the old machine from ELB
                • Shutdown the existing EC2 and RDS machines
                • Plan the test case during the down time
                  • Check if S3 integration is working fine (upload images)
                  • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                • We have to take cdn live (cdn5.enchantingtravels.com)
                • We need to enable the wp cron
              • Once downtime is over
                • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                • Start the Jenkins lead processing again
                • Add the EZ backup script for backup
                • Update copperegg
                • Update papertrail
                • Configure the BCP AMI backup
              • After one week
                • Terminate the EC2, EFS, Memcached and RDS machines

              Open questions

              • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                  • Please inform all marketing team members about the same
                • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                • March 27th, Wednesday 10:30 am IST is the down time
                • We need to stop lead processing – Rajesh
                  • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                • Pre warm steps:
                  • EC2 is up and running with latest wordpress database
                  • WordPress is pointed to new RDS
                  • Lead database is empty
                  • Setup new ELB
                  • Setup EFS
                  • Setup memcached
                  • Check the URL used by Jenkins (Senthil)
                  • Check Redirection plugin database
                  • Check S3
                  • Check Cron jobs
                  • Check large content pasting
                  • Run `wp cron event run –due-now`
                • During the downtime, steps:
                  • Stop Jenkins jobs – Done
                  • Make a note of the last  lead id – 116456
                  • Migrate the db
                  • Update the route53 DNS to new ELB.
                  • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                  • Remove the old machine from ELB
                  • Shutdown the existing EC2 and RDS machines
                  • Plan the test case during the down time
                    • Check if S3 integration is working fine (upload images)
                    • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                  • We have to take cdn live (cdn5.enchantingtravels.com)
                  • We need to enable the wp cron
                • Once downtime is over
                  • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                  • Start the Jenkins lead processing again
                  • Add the EZ backup script for backup
                  • Update copperegg
                  • Update papertrail
                  • Configure the BCP AMI backup
                • After one week
                  • Terminate the EC2, EFS, Memcached and RDS machines

                Open questions

                • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                  • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                    • Please inform all marketing team members about the same
                  • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                  • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                  • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                  • March 27th, Wednesday 10:30 am IST is the down time
                  • We need to stop lead processing – Rajesh
                    • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                  • Pre warm steps:
                    • EC2 is up and running with latest wordpress database
                    • WordPress is pointed to new RDS
                    • Lead database is empty
                    • Setup new ELB
                    • Setup EFS
                    • Setup memcached
                    • Check the URL used by Jenkins (Senthil)
                    • Check Redirection plugin database
                    • Check S3
                    • Check Cron jobs
                    • Check large content pasting
                    • Run `wp cron event run –due-now`
                  • During the downtime, steps:
                    • Stop Jenkins jobs – Done
                    • Make a note of the last  lead id – 116456
                    • Migrate the db
                    • Update the route53 DNS to new ELB.
                    • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                    • Remove the old machine from ELB
                    • Shutdown the existing EC2 and RDS machines
                    • Plan the test case during the down time
                      • Check if S3 integration is working fine (upload images)
                      • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                    • We have to take cdn live (cdn5.enchantingtravels.com)
                    • We need to enable the wp cron
                  • Once downtime is over
                    • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                    • Start the Jenkins lead processing again
                    • Add the EZ backup script for backup
                    • Update copperegg
                    • Update papertrail
                    • Configure the BCP AMI backup
                  • After one week
                    • Terminate the EC2, EFS, Memcached and RDS machines

                  Open questions

                  • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                    • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                      • Please inform all marketing team members about the same
                    • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                    • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                    • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                    • March 27th, Wednesday 10:30 am IST is the down time
                    • We need to stop lead processing – Rajesh
                      • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                    • Pre warm steps:
                      • EC2 is up and running with latest wordpress database
                      • WordPress is pointed to new RDS
                      • Lead database is empty
                      • Setup new ELB
                      • Setup EFS
                      • Setup memcached
                      • Check the URL used by Jenkins (Senthil)
                      • Check Redirection plugin database
                      • Check S3
                      • Check Cron jobs
                      • Check large content pasting
                      • Run `wp cron event run –due-now`
                    • During the downtime, steps:
                      • Stop Jenkins jobs – Done
                      • Make a note of the last  lead id – 116456
                      • Migrate the db
                      • Update the route53 DNS to new ELB.
                      • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                      • Remove the old machine from ELB
                      • Shutdown the existing EC2 and RDS machines
                      • Plan the test case during the down time
                        • Check if S3 integration is working fine (upload images)
                        • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                      • We have to take cdn live (cdn5.enchantingtravels.com)
                      • We need to enable the wp cron
                    • Once downtime is over
                      • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                      • Start the Jenkins lead processing again
                      • Add the EZ backup script for backup
                      • Update copperegg
                      • Update papertrail
                      • Configure the BCP AMI backup
                    • After one week
                      • Terminate the EC2, EFS, Memcached and RDS machines

                    Open questions

                    • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                  • v
                  • v
                  • vv
                  • vv
                  • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                    • Please inform all marketing team members about the same
                  • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                  • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                  • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                  • March 27th, Wednesday 10:30 am IST is the down time
                  • We need to stop lead processing – Rajesh
                    • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                  • Pre warm steps:
                    • EC2 is up and running with latest wordpress database
                    • WordPress is pointed to new RDS
                    • Lead database is empty
                    • Setup new ELB
                    • Setup EFS
                    • Setup memcached
                    • Check the URL used by Jenkins (Senthil)
                    • Check Redirection plugin database
                    • Check S3
                    • Check Cron jobs
                    • Check large content pasting
                    • Run `wp cron event run –due-now`
                  • During the downtime, steps:
                    • Stop Jenkins jobs – Done
                    • Make a note of the last  lead id – 116456
                    • Migrate the db
                    • Update the route53 DNS to new ELB.
                    • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                    • Remove the old machine from ELB
                    • Shutdown the existing EC2 and RDS machines
                    • Plan the test case during the down time
                      • Check if S3 integration is working fine (upload images)
                      • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                    • We have to take cdn live (cdn5.enchantingtravels.com)
                    • We need to enable the wp cron
                  • Once downtime is over
                    • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                    • Start the Jenkins lead processing again
                    • Add the EZ backup script for backup
                    • Update copperegg
                    • Update papertrail
                    • Configure the BCP AMI backup
                  • After one week
                    • Terminate the EC2, EFS, Memcached and RDS machines

                  Open questions

                  • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                    • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                      • Please inform all marketing team members about the same
                    • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                    • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                    • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                    • March 27th, Wednesday 10:30 am IST is the down time
                    • We need to stop lead processing – Rajesh
                      • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                    • Pre warm steps:
                      • EC2 is up and running with latest wordpress database
                      • WordPress is pointed to new RDS
                      • Lead database is empty
                      • Setup new ELB
                      • Setup EFS
                      • Setup memcached
                      • Check the URL used by Jenkins (Senthil)
                      • Check Redirection plugin database
                      • Check S3
                      • Check Cron jobs
                      • Check large content pasting
                      • Run `wp cron event run –due-now`
                    • During the downtime, steps:
                      • Stop Jenkins jobs – Done
                      • Make a note of the last  lead id – 116456
                      • Migrate the db
                      • Update the route53 DNS to new ELB.
                      • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                      • Remove the old machine from ELB
                      • Shutdown the existing EC2 and RDS machines
                      • Plan the test case during the down time
                        • Check if S3 integration is working fine (upload images)
                        • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                      • We have to take cdn live (cdn5.enchantingtravels.com)
                      • We need to enable the wp cron
                    • Once downtime is over
                      • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                      • Start the Jenkins lead processing again
                      • Add the EZ backup script for backup
                      • Update copperegg
                      • Update papertrail
                      • Configure the BCP AMI backup
                    • After one week
                      • Terminate the EC2, EFS, Memcached and RDS machines

                    Open questions

                    • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                      • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                        • Please inform all marketing team members about the same
                      • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                      • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                      • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                      • March 27th, Wednesday 10:30 am IST is the down time
                      • We need to stop lead processing – Rajesh
                        • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                      • Pre warm steps:
                        • EC2 is up and running with latest wordpress database
                        • WordPress is pointed to new RDS
                        • Lead database is empty
                        • Setup new ELB
                        • Setup EFS
                        • Setup memcached
                        • Check the URL used by Jenkins (Senthil)
                        • Check Redirection plugin database
                        • Check S3
                        • Check Cron jobs
                        • Check large content pasting
                        • Run `wp cron event run –due-now`
                      • During the downtime, steps:
                        • Stop Jenkins jobs – Done
                        • Make a note of the last  lead id – 116456
                        • Migrate the db
                        • Update the route53 DNS to new ELB.
                        • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                        • Remove the old machine from ELB
                        • Shutdown the existing EC2 and RDS machines
                        • Plan the test case during the down time
                          • Check if S3 integration is working fine (upload images)
                          • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                        • We have to take cdn live (cdn5.enchantingtravels.com)
                        • We need to enable the wp cron
                      • Once downtime is over
                        • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                        • Start the Jenkins lead processing again
                        • Add the EZ backup script for backup
                        • Update copperegg
                        • Update papertrail
                        • Configure the BCP AMI backup
                      • After one week
                        • Terminate the EC2, EFS, Memcached and RDS machines

                      Open questions

                      • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                        • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                          • Please inform all marketing team members about the same
                        • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                        • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                        • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                        • March 27th, Wednesday 10:30 am IST is the down time
                        • We need to stop lead processing – Rajesh
                          • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                        • Pre warm steps:
                          • EC2 is up and running with latest wordpress database
                          • WordPress is pointed to new RDS
                          • Lead database is empty
                          • Setup new ELB
                          • Setup EFS
                          • Setup memcached
                          • Check the URL used by Jenkins (Senthil)
                          • Check Redirection plugin database
                          • Check S3
                          • Check Cron jobs
                          • Check large content pasting
                          • Run `wp cron event run –due-now`
                        • During the downtime, steps:
                          • Stop Jenkins jobs – Done
                          • Make a note of the last  lead id – 116456
                          • Migrate the db
                          • Update the route53 DNS to new ELB.
                          • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                          • Remove the old machine from ELB
                          • Shutdown the existing EC2 and RDS machines
                          • Plan the test case during the down time
                            • Check if S3 integration is working fine (upload images)
                            • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                          • We have to take cdn live (cdn5.enchantingtravels.com)
                          • We need to enable the wp cron
                        • Once downtime is over
                          • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                          • Start the Jenkins lead processing again
                          • Add the EZ backup script for backup
                          • Update copperegg
                          • Update papertrail
                          • Configure the BCP AMI backup
                        • After one week
                          • Terminate the EC2, EFS, Memcached and RDS machines

                        Open questions

                        • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                          • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                            • Please inform all marketing team members about the same
                          • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                          • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                          • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                          • March 27th, Wednesday 10:30 am IST is the down time
                          • We need to stop lead processing – Rajesh
                            • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                          • Pre warm steps:
                            • EC2 is up and running with latest wordpress database
                            • WordPress is pointed to new RDS
                            • Lead database is empty
                            • Setup new ELB
                            • Setup EFS
                            • Setup memcached
                            • Check the URL used by Jenkins (Senthil)
                            • Check Redirection plugin database
                            • Check S3
                            • Check Cron jobs
                            • Check large content pasting
                            • Run `wp cron event run –due-now`
                          • During the downtime, steps:
                            • Stop Jenkins jobs – Done
                            • Make a note of the last  lead id – 116456
                            • Migrate the db
                            • Update the route53 DNS to new ELB.
                            • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                            • Remove the old machine from ELB
                            • Shutdown the existing EC2 and RDS machines
                            • Plan the test case during the down time
                              • Check if S3 integration is working fine (upload images)
                              • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                            • We have to take cdn live (cdn5.enchantingtravels.com)
                            • We need to enable the wp cron
                          • Once downtime is over
                            • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                            • Start the Jenkins lead processing again
                            • Add the EZ backup script for backup
                            • Update copperegg
                            • Update papertrail
                            • Configure the BCP AMI backup
                          • After one week
                            • Terminate the EC2, EFS, Memcached and RDS machines

                          Open questions

                          • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
                • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
                  • Please inform all marketing team members about the same
                • March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
                • Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
                • March 27th, Wednesday 10:00 am IST restore the wordpress DB  
                • March 27th, Wednesday 10:30 am IST is the down time
                • We need to stop lead processing – Rajesh
                  • Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
                • Pre warm steps:
                  • EC2 is up and running with latest wordpress database
                  • WordPress is pointed to new RDS
                  • Lead database is empty
                  • Setup new ELB
                  • Setup EFS
                  • Setup memcached
                  • Check the URL used by Jenkins (Senthil)
                  • Check Redirection plugin database
                  • Check S3
                  • Check Cron jobs
                  • Check large content pasting
                  • Run `wp cron event run –due-now`
                • During the downtime, steps:
                  • Stop Jenkins jobs – Done
                  • Make a note of the last  lead id – 116456
                  • Migrate the db
                  • Update the route53 DNS to new ELB.
                  • Add new EC2 to existing ELB so that if there is traffic it will come to new machines
                  • Remove the old machine from ELB
                  • Shutdown the existing EC2 and RDS machines
                  • Plan the test case during the down time
                    • Check if S3 integration is working fine (upload images)
                    • Junaid – can you add more test cases  – Vivek has list of tests to be done. Vivek will perform the tests.
                  • We have to take cdn live (cdn5.enchantingtravels.com)
                  • We need to enable the wp cron
                • Once downtime is over
                  • Migrate the leads database from old RDS to new RDS (1.7GB data)  – Not required
                  • Start the Jenkins lead processing again
                  • Add the EZ backup script for backup
                  • Update copperegg
                  • Update papertrail
                  • Configure the BCP AMI backup
                • After one week
                  • Terminate the EC2, EFS, Memcached and RDS machines

                Open questions

                • The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.
            • March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

              March 26th, Tuesday 6pm IST Vivek will stop updating any new content in existing wordpress .com, .de
              Please inform all marketing team members about the same
              March 26th if we need to do a dry run with Junaid, Jyothish and Vivek
              Vivek to send notice of downtime, Check with Vidya/Sree to who. Done
              March 27th, Wednesday 10:00 am IST restore the wordpress DB
              March 27th, Wednesday 10:30 am IST is the down time
              We need to stop lead processing – Rajesh
              Need a list of jenkins jobs to stop from Senthil/Sreenath – Isaac
              Pre warm steps:
              EC2 is up and running with latest wordpress database
              Wordpress is pointed to new RDS
              Lead database is empty
              Setup new ELB
              Setup EFS
              Setup memcached
              Check the URL used by Jenkins (Senthil)
              Check Redirection plugin database
              Check S3
              Check Cron jobs
              Check large content pasting
              Run `wp cron event run –due-now`

              During the downtime, steps:
              Stop Jenkins jobs – Done
              Make a note of the last lead id – 116456
              Migrate the db
              Update the route53 DNS to new ELB.
              Add new EC2 to existing ELB so that if there is traffic it will come to new machines
              Remove the old machine from ELB
              Shutdown the existing EC2 and RDS machines
              Plan the test case during the down time
              Check if S3 integration is working fine (upload images)
              Junaid – can you add more test cases – Vivek has list of tests to be done. Vivek will perform the tests.
              We have to take cdn live (cdn5.enchantingtravels.com)
              We need to enable the wp cron

              Once downtime is over
              Migrate the leads database from old RDS to new RDS (1.7GB data) – Not required
              Start the Jenkins lead processing again
              Add the EZ backup script for backup
              Update copperegg
              Update papertrail
              Configure the BCP AMI backup

              After one week
              Terminate the EC2, EFS, Memcached and RDS machines

              Open questions
              The folder we have in website, check with compassites team (isaac/senthil) . Checked with Sreenath. Done.

Contact Us

Our team of experts can help answer any questions you might have. Please fill out the form below and a consultant will respond shortly.

Give us a call:

US & Canada: +1 888 263 2574
UK: +0 800 098 8486
AUS: +1 800 044 986

Send an email:

contact@enchantingtravels.com