Skip to content

z Testing a new TRE deployment

Jump to bottom
Tony Wildish edited this page Oct 21, 2024 · 1 revision

Testing a new SDE deployment

This is for TRE Developers only, there's nothing for TRE Users on this page.

There are several things to test with a new SDE, and they have to happen in the right order. A minimal plan looks something like this:

  • Deploy the SDE - follow the documentation in the repository for now
    • Ensure the firewall is deployed (normally as part of the basic deployment)
    • Deploy all workspace and service templates ('make bundle-publish-register-all') These steps happen from the build environment, manually with the 'Makefile' at the moment.

Set up your basic access to the SDE

  • Grant yourself the 'TRE Administrator' and 'TRE User' roles for your SDE, in the Azure portal.

Once the SDE is deployed, start deploying and testing the services, using the UI.

  • Deploy a shared certificate service for Nexus. Make sure the domain prefix is nexus, and the cert name is nexus-ssl

  • Deploy the Nexus shared service

  • Deploy a Base workspace

    • Deploy Guacamole in the workspace
      • Deploy Linux and Windows VMs
      • Test basic functionality:
        • Connect to desktop
        • Connect to shared storage
        • Check that R, RStudio, Jupyter, Python/Anaconda, Azure Storage Explorer, Visual Studio Code, and the web browser all work
        • Check Microsoft Office, or LibreOffice, depending on which is installed
        • Check that you can pull system or Python/R updates via Nexus

  • Deploy an Airlock workspace

    • Deploy the Airlock Notifier shared service
    • Configure the Airlock Notifier - probably by hand (no, we don't have documentation for that yet)
      • Test the airlock from your workspace - make an export from a VM, at least.

  • Deploy the ADF shared service

  • Deploy an ADF workspace

    • Test the ADF workspace... somehow... (Andrii, need docs)

  • Test deploying the remaining shared services, at least some of them:

    • Admin VM
    • Gitea

  • Test the remaining Workspace services, at least the most important ones:

    • Gitea
    • AzureML
    • MySQL
    • MLflow
    • AzureSQL (currently seems to be broken)
    • Azure Databricks

Make sure to clean up afterwards, testing deletion is as important as testing creation.

If there are any errors during deployment, check the upstream repository issues, see if it's already known.

Clone this wiki locally