Create a Test Deployment of Redesign Applications

Open

If you wish to try out MCOECN hosting, the easiest way is to create a Test copy of one of your local State Software applications in the MCOECN hosting environment.

And if you are already hosting with MCOECN, creating a Test is a great way to troubleshoot problems or try out new features without fear of messing up a production deployment.

Below are the steps to create the test deployment in the MCOECN Service Broker.

1. First, you must have a backup of a production deployment of Redesign to restore into the Test deployment.
   
   

   1. If your ITC hosts Production Redesign with MCOECN, you already have nightly backups that will be used.....proceed to Step 2.
      
      

   2. If your ITC does NOT currently host with MCOECN, but you are copying nightly backups to MCOECN for an offsite copy, you already have a backup that will be used.  Proceed to Step 2.
      
      

   3. If your ITC does NOT host with MCOECN and does not send offsite backups to MCOECN, follow the steps in Upload a Local Docker Backup to the MCOECN to get a backup of your district data to the MCOECN. When the Service Broker task below runs, it will find your backup by IRN and restore it to the new application.
      
      

2. Log into https://cloud.managementcouncil.org and go to the Service Broker.

3. From the Service Broker, run State Software Test by clicking Request. 

   Open

   

4. Choose the District, and check boxes beside each State Software application you wish to deploy. When you check an application, by default, the most recent backup found will be used to create this test (usually, the nightly backup from the previous night). If you check Select a specific USAS backup, you can choose any existing backup from a dropdown list to use instead, allowing you to go back to any day in the last 60 days to restore that data.

Open

5. Repeat this process for any other applications you wish to create as part of this test. You can select as many applications as you want in a single run of State Software Test.

6. Choose the number of days for the Test applications to exist....applications will be automatically deleted by a nightly process once the expiration date is reached.

7. If a Production deployment exists and DUO is configured, you can choose to copy the DUO configuration from the production to the test.

8. Optionally, you can reset the admin account password to something new….if you leave it blank, the admin will keep the same password that was configured in the backup being restored.
   
   

   Open

   

   Submit the form to begin deploying applications.
   
   

9. The State Software Test item will:

   1. Find your backup file by matching on the district IRN and the most recent date found.

   2. Automatically create a new deployments of the selected applications

   3. Will restore your backup into the new applications/

   4. Will email you a notice when the task is complete (takes about 10 minutes per application).
      
      

10. The completion email will have the URL to your new application included.   
    URLs for test are the same as production, but with “test-” on the beginning.
    Example: If your production application was https://meta-marbuc-usas.ssdt-ohio.org, the test will be https://test-meta-marbuc-usas.ssdt-ohio.org

11. IMPORTANT LAST STEP: Run the Service Broker catalog item State Software Maintenance on all applications you just deployed.
    As applications were created, API keys were placed into their configuation files, but these will not take effect until the applications are restarted.
    See this page for information about State Software Maintenance :

11. You will be able to log in with the same username/password combinations you use for production, since the same database was restored to your test.