Versions Compared

Old Version 9

changes.mady.by.user Chad Carson

Saved on

compared with

New Version 10

changes.mady.by.user Chad Carson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Make sure you can log into http://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.
  • From the VRA Service Broker, run "USxS-RunAsTest" and choose the information for the district you want to test out.
    Image Removed
    • The USxS-RunAsTest item will:
  • Find your backup file by the IRN
  • Automatically create a new instance of USAS/USPS/INVENTORY/WORKFLOWS
  • Will restore your backup into it
    • Will email you a notice when the task is complete (takes about 10 minutes or less).
    The completion email will have the URL to your new application included.   You should be able to log in with the same username/password combinations you used locally.
    Panel
    borderColor#000099
    bgColor#eeeeee
    titleColor#ffffff
    borderWidth2
    titleBGColor#000099
    borderStylesolid
    titleCreating a Backup and Getting it to the MCOECN

    There are two ways to do upload a backup to the MCOECN:

    1. Create a backup on your local docker instance, and upload it to SSDT-UPLOADS, the same as you would when requesting support from SSDT.
      This backup process is documented in the following SSDT WIKI article:
      https://wiki.ssdt-ohio.org/display/rtd/Backup+USxS+Databases
      The upload process is documented in the following SSDT WIKI article:
      https://wiki.ssdt-ohio.org/display/rtd/Securely+Send+Files+to+SSDT+for+Support

    2. The MCOECN provides a hosted virtual machine for Docker testing to each ITC, and some ITCs do scripted backups of their local Redesign instances to this server.  If you are already backing up local instances to MCOECN, you already have a backup that you can use.
      This process is documented in this following SSDT WIKI article:
      https://wiki.ssdt-ohio.org/display/rtd/Using+Remote+Backup+Script

    Backup Naming Convention

    NOTE: It is important that the backup filename follows a rigid format: <IRN>-<District Name>-<Application>db.<timestamp>.backup.gz
    One small nuance, there is no dash between USAS and "DB" ,USPS and "DB", and WORKFLOWS and "DB" in the name, but there IS a dash between "Inventory" and "DB" in the backup filename.
    Examples: 
      USPS                   047589libertycenter-uspsdb.2022-03-01-03-10-06.backup.gz
      USAS                   043679bryan-usasdb.2022-02-08-02-26-01.backup.gz
      WORKFLOWS      051201ct-workflowsdb.2022-03-03-01-09-35.backup.gz

      INVENTORY        046011unionlocal-inventory-db.2022-02-11-13-00-05.backup.gz

    Tip

    Whatever follows the IRN for the district name/code  is what will be used in the final URL to access the application.

    Tip

    IRN must be a full six digit IRN padded with Leading Zeros.  This is important...the VRA item to create the test instance will fail if it cannot find the full IRN.

    Panel
    borderColor#000099
    bgColor#eeeeee
    titleColor#ffffff
    borderWidth2
    titleBGColor#000099
    borderStylesolid
    titleCreating the Test Instance
    Tip

    If you connect your local USAS/USPS to your own Active Directory, you will need to work with the Management Council Data Center Operations (DCO) team to allow access from the MCOECN hosted environment to your local Active Directory server(s). This will not happen automatically.