Azure Deployments¶
The following enhancements relate to deployments on the Microsoft Azure cloud platform:
Simplified Azure Set-up¶
All Azure deployments now use the same basic deployment option (the 'multi-role' option).
It is no longer necessary to select the configuration of modules for each role. Instead the installer will use a default set-up defined in a configuration file, and the user simply selects how many of each pre-defined role they require.
Auto scaling can be enabled via a checkbox in the installer, provided this option is included in the licence.
Note
Note that if any changes do need to be made to the role configuration, this can still be done by editing a conifguration file. However, it is recommended simply to use the default configuration.
Virtual Machine Image Creation¶
The PSO installer now supports the use of pre-built images for Azure deployments. This significantly reduces the boot up time when starting a new instance, or an entire deployment. This has major benefits for example when adding new instances to an existing system as part of auto scaling.
The installer includes options for creating and deleting images, and for creating a deployment using a pre-built image.
Access to Archive Reporting Tables¶
An additional user is now created as part of an Azure installation, with read only access to the Scheduling Archive Database. This user can then be used by customers to access the reporting tables within the Archive database and generate reports from these tables. The connection details for this user are added to the connection details file created as part of the installation.
Interactive Authentication¶
The installer now supports interactive authentication when creating or updating an Azure scheduling system. Previously the only supported authentication mode was 'service principal', which requires the details of the authentication to be embedded in the licence key. This option is still supported, but now an interactive authentication can also be used, where the user is required to login to Azure during the installation process.
This provides additional traceability of the actions taken, and removes the need for the authentication details to be included in the licence. For interactive authentication, only the subscription id is required in the licence.
In addition, all Azure deployments now use a Managed Identity that is associated with a specific deployment to handle interaction with Azure on behalf of PSO.
Note
Please note that in order to use the interactive login it is necessary for the user to have Owner privileges on the Azure subscription.
Monitoring Set-up¶
Azure monitoring can now be set up as part of the installation process, making it much easier to create and maintain a monitoring dashboard.
Case Sensitivity¶
Azure databases are now created with a case sensitive collation, matching the recommended setting for all scheduling databases.
Documentation and Support¶
For full details of all this functionality see the Installation Guide.