從映像創建VM並添加到現有的可用性集

Question

如何添加我在門戶中創建的或從vmdepot導入到現有可用性集的現有VM？它似乎不可能從門戶網站，它是否在Powershell中工作？資源管理器部署模型完全可以工作嗎？

Answer 1

目前，ARM部署，設置可用性組目前還不支持。可用性集只能在創建時添加。因此，對於您的情況，您需要刪除當前實例，並使用舊的OSDisk，Vnet和其他設置創建新的部署。

這可以通過使用ARM模板來實現。以下示例顯示如何使用現有的VHD和Vnet部署VM。它還創建一個新的可用性集，並將VM添加到可用性集。

{ 
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", 
    "contentVersion": "1.0.0.0", 
    "parameters": { 
    "location": { 
     "type": "string", 
     "metadata": { 
     "description": "Please enter the location where you want to deploy this VM" 
     } 
    }, 
    "vmName": { 
     "type": "string", 
     "metadata": { 
     "description": "Name of the VM" 
     } 
    }, 
    "osType": { 
     "type": "string", 
     "allowedValues": [ 
     "Windows", 
     "Linux" 
     ], 
     "metadata": { 
     "description": "Type of OS on the existing vhd" 
     } 
    }, 
    "osDiskVhdUri": { 
     "type": "string", 
     "metadata": { 
     "description": "Uri of the existing VHD in ARM standard or premium storage" 
     } 
    }, 
    "vmSize": { 
     "type": "string", 
     "metadata": { 
     "description": "Size of the VM" 
     } 
    }, 
    "existingVirtualNetworkName": { 
     "type": "string", 
     "metadata": { 
     "description": "Name of the existing VNET" 
     } 
    }, 
    "existingVirtualNetworkResourceGroup": { 
     "type": "string", 
     "metadata": { 
     "description": "Name of the existing VNET resource group" 
     } 
    }, 
    "subnetName": { 
     "type": "string", 
     "metadata": { 
     "description": "Name of the subnet in the virtual network you want to use" 
     } 
    }, 
    "dnsNameForPublicIP": { 
     "type": "string", 
     "metadata": { 
     "description": "Unique DNS Name for the Public IP used to access the Virtual Machine." 
     } 
    }, 
    "availabilitySetName": { 
     "type": "string", 
     "metadata": { 
     "description": "The name of your Availability Set." 
     } 
    } 
    }, 
    "variables": { 
    "api-version": "2015-06-15", 
    "publicIPAddressType": "Dynamic", 
    "vnetID": "[resourceId(parameters('existingVirtualNetworkResourceGroup'), 'Microsoft.Network/virtualNetworks', parameters('existingVirtualNetworkName'))]", 
    "subnetRef": "[concat(variables('vnetID'),'/subnets/', parameters('subnetName'))]", 
    "nicName": "[parameters('vmName')]", 
    "publicIPAddressName": "[parameters('vmName')]" 
    }, 
    "resources": [ 
    { 
     "apiVersion": "[variables('api-version')]", 
     "type": "Microsoft.Network/publicIPAddresses", 
     "name": "[variables('publicIPAddressName')]", 
     "location": "[parameters('location')]", 
     "tags": { 
     "displayName": "PublicIPAddress" 
     }, 
     "properties": { 
     "publicIPAllocationMethod": "[variables('publicIPAddressType')]", 
     "dnsSettings": { 
      "domainNameLabel": "[parameters('dnsNameForPublicIP')]" 
     } 
     } 
    }, 
    { 
     "apiVersion": "[variables('api-version')]", 
     "type": "Microsoft.Network/networkInterfaces", 
     "name": "[variables('nicName')]", 
     "location": "[parameters('location')]", 
     "dependsOn": [ 
     "[concat('Microsoft.Network/publicIPAddresses/', variables('publicIPAddressName'))]" 
     ], 
     "tags": { 
     "displayName": "NetworkInterface" 
     }, 
     "properties": { 
     "ipConfigurations": [ 
      { 
      "name": "ipconfig1", 
      "properties": { 
       "privateIPAllocationMethod": "Dynamic", 
       "publicIPAddress": { 
       "id": "[resourceId('Microsoft.Network/publicIPAddresses',variables('publicIPAddressName'))]" 
       }, 
       "subnet": { 
       "id": "[variables('subnetRef')]" 
       } 
      } 
      } 
     ] 
     } 
    }, 
    { 
     "type": "Microsoft.Compute/availabilitySets", 
     "name": "[parameters('availabilitySetName')]", 
     "apiVersion": "2015-06-15", 
     "location": "[parameters('location')]", 
     "properties": { 
     "platformFaultDomainCount": "3", 
     "platformUpdateDomainCount": "20" 
     } 
    }, 
    { 
     "apiVersion": "[variables('api-version')]", 
     "type": "Microsoft.Compute/virtualMachines", 
     "name": "[parameters('vmName')]", 
     "location": "[parameters('location')]", 
     "tags": { 
     "displayName": "VirtualMachine" 
     }, 
     "dependsOn": [ 
     "[concat('Microsoft.Compute/availabilitySets/', parameters('availabilitySetName'))]", 
     "[concat('Microsoft.Network/networkInterfaces/', variables('nicName'))]" 
     ], 
     "properties": { 
     "hardwareProfile": { 
      "vmSize": "[parameters('vmSize')]" 
     }, 
     "AvailabilitySet" : { 
      "id": "[resourceId('Microsoft.Compute/availabilitySets', parameters('availabilitySetName'))]" 
     }, 
     "storageProfile": { 
      "osDisk": { 
      "name": "[concat(parameters('vmName'))]", 
      "osType": "[parameters('osType')]", 
      "caching": "ReadWrite", 
      "vhd": { 
       "uri": "[parameters('osDiskVhdUri')]" 
      }, 
      "createOption": "Attach" 
      } 
     }, 
     "networkProfile": { 
      "networkInterfaces": [ 
      { 
       "id": "[resourceId('Microsoft.Network/networkInterfaces',variables('nicName'))]" 
      } 
      ] 
     } 
     } 
    } 
    ] 
} 

如果你想將虛擬機添加到現有的可用性設置，你可以刪除

{ 
     "type": "Microsoft.Compute/availabilitySets", 
     "name": "[parameters('availabilitySetName')]", 
     "apiVersion": "2015-06-15", 
     "location": "[parameters('location')]", 
     "properties": { 
     "platformFaultDomainCount": "3", 
     "platformUpdateDomainCount": "20" 
     } 
    }, 

和

 "[concat('Microsoft.Compute/availabilitySets/', parameters('availabilitySetName'))]", 

有關創作ARM模板的詳細信息，請參閱Authoring Azure Resource Manager templates

有關如何部署ARM模板的更多信息，請參閱Deploy a Resource Group with Azure Resource Manager template

而上述模板從GitHub的this sample template修改。

我張貼了這個答案後，我就一直在想使用REST API更新與可用性組虛擬機。我想這可能工作，所以我給它一個鏡頭，這裏是錯誤消息我：

Invoke-RestMethod : { 
    "error": { 
    "code": "PropertyChangeNotAllowed", 
    "target": "availabilitySet.id", 
    "message": "Changing property 'availabilitySet.id' is not allowed." 
    } 
} 
At C:\Users\v-dazen\Documents\setVMRestAPI.ps1:13 char:1 
+ Invoke-RestMethod -Method Put -Uri "https://management.azure.com/subs ... 
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
    + CategoryInfo   : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException 
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand 

這意味着設置可用性部署的VM現有的ARM指令集是不可能的呢。