Release steps

1. [D] Synchronize database with production (staging only)
2. [D] Make sure the old version runs with the synchronized data (staging only)
3. [D] Shut down DM on both nodes
4. [D] Create database dump in case it was necessary to do a backup
5. [D] Remove no longer necessary records from the database:

   delete from configuration where property in('rest.subscrsstatus.tolerance', 'rest.subscrsstatus.secret', 'rhtit.restServiceGroupName', 'rhtit.streamlineApiSecretKey', 'rhtit.streamlineApiBaseUrl', 'rhtit.restServicesBaseUrl', 'rhtit.restServicesTermsIdCacheRHD');
   ALTER TABLE terms_and_conditions DROP COLUMN htmltext;
   ALTER TABLE terms_and_conditions DROP COLUMN plainttext;
   delete from user_userrights where userrights = 'EDIT_TERMS_AND_CONDITIONS';
   DROP TABLE users_redhatdevelopersubscription;
   DROP TABLE sku_subscription;
   DROP TABLE termsandconditionssigninfo_attributes;
   DROP TABLE termsandconditionssigninfo;
   

6. [L] Prepare the machine for upgrade to EAP 7
   • Cleanup EAP 6 installation (including old Keycloak module)
   • Install EAP 7
   • Configure cluster
   • Prolong transaction timeout to 60 seconds:
     1. find \<cache-container name="web"
     2. make sure the default cache points to cache named dist
     3. make sure the web cache has \<transport lock-timeout="180000"/> set
     4. make sure the definition of dist cache looks like:

        <distributed-cache name="dist" mode="ASYNC" l1-lifespan="0" owners="2">
              <locking acquire-timeout="60000" isolation="REPEATABLE_READ"/>
                    <transaction mode="BATCH"/>
              <file-store/>
        </distributed-cache> 
        

   • Update JDBC driver
   • Configure puppet
   • Install new version of Keycloak client module (2.5.5)
7. [L] Install new DM RPM
8. [L] Run the service
9. [D] Check the log and start testing
   • JBoss Download
   • RHD Download
   • both JBoss and RHD download with modified thank you page
   • check SSO bridge
   • check available REST API
   • check admin REST API
   • check Web UI modification of records and locking
   • check the proper work with user profiles (Keycloak integration)

Emergency Fallback

1. [D] Shut down the service on both nodes
2. [L] Revert EAP 7 to EAP 6 and revert the Keycloak module
3. [L] Restore database from backup
4. [L] start service
5. [D] check it is working

Additional Sources

Configuration Description:

https://code.engineering.redhat.com/gerrit/gitweb?p=jboss-download-manager.git;a=blob;f=README.md;hb=HEAD

Database Dump

https://mojo.redhat.com/docs/DOC-1059314