This article provides a comprehensive guide outlining the steps and actions necessary to restart a Rimo3 Gateway deployment within your Azure subscription.
In this article:
- When should I restart the Rimo3 Gateway deployment process
- Deleting previously deployed resources
- Rerunning the Rimo3 deployment process
When should I restart the Rimo3 Gateway deployment process
In most cases you do not need to restart the Rimo3 Gateway deployment if you are encountering issues or failed checks in the Requirements checker. However, in some cases it might be easier to start the process over, such as when:
- You need to moved the Gateway to a new or different virtual network and/or Subnet
- You have opted to pre-create resources, such as a storage account, that failed to get created by the MPO in a previous deployment.
- You need to rename multiple resources after they have been deployed
Deleting previously deployed resources
Before rerunning the Rimo3 Gateway deployment process you will need to delete the Gateway virtual machine, disk and network card as a minimum. See below for details of which resources can be reused and which should be deleted:
- Resource Group - The resource group from a previous deployment can be reused but you should remove the Gateway's system assigned identity from the Owner role to avoid ending up with an orphaned identity after the Gateway virtual machine is deleted.
If you delete the resource group, first delete the resources within it. Otherwise, the resources may be tombstoned for up to 14 days, preventing immediate reuse of the resource names during the redeployment process.
- Virtual Machine - The Gateway virtual machine should be deleted as it cannot be reused when rerunning the deployment process.
- Disk - The Gateway disk should be deleted as it cannot be reused when rerunning the deployment process.
- Network card - The Gateway network card should be deleted as it cannot be reused when rerunning the deployment process.
- Virtual network & subnet - The virtual network and subnet from a previous deployment may be reused, provided they are properly configured, or were existing resources prior to the previous deployment.
- Storage Account - The storage account should be deleted as the MPO is configured to create a new empty storage account as part of the deployment.
- Key Vault - The key vault should be deleted as the MPO is configured to create and permission a new empty key vault as part of the deployment.
Rerunning the Rimo3 deployment process
Before rerunning the deployment process ensure any previously deployed resources that cannot be reused have been delete as described above.
To restart the Rimo3 Deployment Process do the following:
- If you haven't already done so click the dropdown arrow on the Descend button and select Restart deployment.
- When prompted click on Yes, restart
- The deployment status will be cleared, and the deployment wizard will refresh, bringing you back to the initial step of the process.
- From this point you can proceed as you did before; you will need to copy a new registration key and complete the MPO again. Make sure you select pre-existing resource you wish to reuse, and correct anything that was incorrectly configured in the previous deployment.