...
When running the MC in Azure using a managed identity, the clientId and clientSecret should be left out of the mc configuration.
the MC will by default first try to use the managed identity of the virtual machine to contact the azure API to try and control power state (Allocate/deallocate) of the forecasting shells within the group.
If both a system assigned and user assigend managed identity are assigned, the system assigned identity will be used. In case the user assigned managed identity should be used, it has to be configured explicitly by specifying the client id in the azure section.
If the MC does not have a system assigned/user assigned managed identity, you can specify a service principal/app registration by specifying the clientId and clinetSecret explicitly.
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<mc xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews" xsi:schemaLocation="http://www.wldelft.nl/fews https://fewsdocs.deltares.nl/schemas/version1.0/mc.xsd">
<mcId>fssscalingmc00</mcId>
<databaseIntId>0</databaseIntId>
<adminInterface>
<title>FSS Scaling On Premise</title>
</adminInterface>
<azure>
<fssGroup>linux_on_prem_scalable</fssGroup>
<tenantId>XXXXXX</tenantId>
<subscriptionId>XXXXX</subscriptionId>
<resourceGroup>fews-on-prem-fss-scaling</resourceGroup>
<!-- clientId and clientSecret are only required if running from on prem -->
<clientId>%AZURE_DPC_FSS_SCALING_CLIENT_ID%</clientId>
<clientSecret>%AZURE_DPC_FSS_SCALING_CLIENT_SECRET%</clientSecret>
</azure>
<azure>
<fssGroup>windows_on_prem_scalable</fssGroup>
<tenantId>XXXXXXXX</tenantId>
<subscriptionId>XXXXXX</subscriptionId>
<resourceGroup>fews-on-prem-fss-scaling</resourceGroup>
<!-- clientId and clientSecret are only required if running from on prem -->
<clientId>%AZURE_DPC_FSS_SCALING_CLIENT_ID%</clientId>
<clientSecret>%AZURE_DPC_FSS_SCALING_CLIENT_SECRET%</clientSecret>
</azure>
<fssGroups>
<fssGroup id="linux" name="linux" mcId="fssscalingmc00">
<description></description>
<allowUnmapped>true</allowUnmapped>
<minAwakeCount>1</minAwakeCount>
<releaseSlotsMillis unit="hour" multiplier="0"/>
<gotoSleepMillis unit="minute" multiplier="5"/>
</fssGroup>
<fssGroup id="linux_on_prem_scalable" name="linux_on_prem_scalable" mcId="fssscalingmc00">
<description></description>
<allowUnmapped>false</allowUnmapped>
<minAwakeCount>0</minAwakeCount>
<releaseSlotsMillis unit="hour" multiplier="0"/>
<gotoSleepMillis unit="minute" multiplier="5"/>
</fssGroup>
<fssGroup id="windows_on_prem_scalable" name="windows_on_prem_scalable" mcId="fssscalingmc00">
<description></description>
<allowUnmapped>false</allowUnmapped>
<minAwakeCount>0</minAwakeCount>
<releaseSlotsMillis unit="hour" multiplier="0"/>
<gotoSleepMillis unit="minute" multiplier="5"/>
</fssGroup>
</fssGroups>
<workflowMappings>
<workflowMapping workflowId="Import_EarthObservation" fssGroupId="windows_on_prem_scalable" mcId="fssscalingmc00"/>
<workflowMapping workflowId="Import_Forecasts" fssGroupId="linux_on_prem_scalable" mcId="fssscalingmc00"/>
</workflowMappings>
</mc> |
...