Page History

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

1. First, you must have a backup of a production deployment of Redesign to restore into the Training 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. Make sure you can log into https://cloud.managementcouncil.org and see "Service Broker", and the catalog items. If this is the first time your ITC is using MCOECN Hosting, we may need to create an MCOECN.ORG account for you, or grant access to the VRA portal to your existing account.

   If you are having trouble logging into https://cloud.managementcouncil.org, you can use the Self Service website to reset your password if you have previously registered an alternative account for password recovery.
   https://selfservice.managementcouncil.org

   
   
   
3. From the VRA Service Broker, run Redesign Train by clicking on Request. 
   
4. Choose the district, and the applications you wish to deploy.
5. Set the number of days for this deployment to exist.  It will be automatically removed after that future date.
   
   
   
   
6. The Redesign Train item will:
   1. Find your backup file by the IRN
   2. Automatically create a new deployment of USAS/USPS/INVENTORY/WORKFLOWS
   3. Will restore your backup into the new deployment
   4. Will email you a notice when the task is complete (takes about 10 minutes per application).
      
      
7. The completion email will have the URL to your new application included.   
   You will be able to log in with the same username/password combinations you use in your production deployment, since you restored from the same production database.