An overview of the HEAT Cloud refresh/push cycle for NON-package pushes

Version 1

    Details

    What is the development cycle on HEAT Cloud for full/legacy/non-package pushes? 


    Resolution

     

    The development cycle on HEAT Cloud goes:

     

    1.       Customer requests a refresh of STG to start the cycle

    o   Ops refresh STG to create a baseline

    §  A copy of the PRD database is shrunk and scrubbed, leaving only a subset of transaction data, then copied over the STG tenant DB. Everything in STG is lost/replaced.

    §  The PRD tenant is locked if not already locked. Changes to PRD after this time will affect the baseline and may prevent a successful push.

    2.       Development happens on STG

    3.       Customer requests a STG > UAT push

    o   UAT is refreshed from PRD

    §  A copy of the PRD database is shrunk and scrubbed, leaving only a subset of the TRANSACTIONAL data (but keeping all METADATA and MASTER data), then copied over the UAT tenant DB. Everything in UAT is lost/replaced.

    §  This ensures that the push from STG to UAT will accurately reflect what will happen with the push from UAT to PRD.

    §  UAT is locked and should remain so throughout the cycle.

    ·         If UAT is unlocked it will affect the baseline and METADATA changes may not be included in the differential.

    ·         Additionally, if another STG > UAT push occurs, if the changes made in UAT were not also made in STG then they would be lost.  

    o   STG is pushed to UAT

    §  The Ops Console is used to create a comparison of the METADATA between STG (new stuff and existing stuff) and UAT (existing stuff). The differences (new stuff) are copied from STG to UAT.

    §  No TRANSACTIONAL data is copied.

    4.       Users test on UAT to confirm functionality, both new and old

    5.       Customer fixes any issues on STG; can request a refresh & re-push to UAT if required

    6.       Once testing on UAT is complete, Customer requests a UAT > PRD push

    o   UAT is pushed to PRD

    §  The Ops Console is used to create a comparison of the METADATA between UAT (new stuff and existing stuff) and PRD (existing stuff). The differences (new stuff) are copied from UAT to PRD.

    §  No TRANSACTIONAL data is copied.

    §  STG tenant is locked to prevent changes being made before the refresh is done. If changes were to be made to STG they would be lost in the next refresh.

    7.       Customer tests on PRD to confirm functionality, both new and old

     

    o   If there are any issues that cannot be resolved by the customer in PRD, contact HEAT Support as soon as possible to rollback the tenant. Everything that has been created or changed in PRD since the push will be lost. 

    o   If there are no issues, start the process again for the next development cycle