新的Powershell cmdlet(在此处记录:http://msdn.microsoft.com/en-us/library/windowsazure/jj152841)看起来很可爱,但是其中一个似乎缺少:Get-OperationStatus -WaitToComplete
没有这个,我的Azure操作(例如Set-AzureDeployment
)就不会等待完成。
这使得很难知道何时在执行VIP交换之前,正在运行一个登台实例。
还有其他选择吗?
最佳答案
因此,经过调查,我最初的假设在某种程度上是错误的:对新Powershell cmdlet的调用确实需要等待成功完成,但Set-AzureDeployment -newStatus "Running"
除外。
很好,因为我们不再需要通过脚本分散对Get-OperationStatus
的调用;但是,这很糟糕,因为Set-AzureDeployment
会使部署变得困惑起来。
我们可以调用Get-AzureDeployment
,并遍历RoleInstanceList
找出正在发生的事情。像这样:
function Get-StagingReady {
$stagingStatus = Get-AzureDeployment $azureService -slot staging
if (-not $($stagingStatus.Status -eq "Running")) {
Write-Host $(" ... ... Staging slot status is not Running; value is " + $stagingStatus.Running)
return $False
}
if (-not $stagingStatus.RoleInstanceList) {
Write-Host " ... ... Staging slot has no instances configured yet."
return $False
}
$notReady = $False
Foreach ($roleInstance in $stagingStatus.RoleInstanceList) {
if (-not $($roleInstance.InstanceStatus -eq "ReadyRole")) {
Write-Host $(" ... ... ... Staging slot instance " + $roleInstance.InstanceName + " has status " + $roleInstance.InstanceStatus)
$notReady = $True
}
}
if ($notReady) {
Write-Host " ... ... One or more instances not running."
return $False
}
Write-Host " ... Staging slot ready for use."
return $True
}
function Wait-ForStagingToBeReady {
while ( -not $(Get-StagingReady) ) {
Write-Host " ... ... Staging slot not ready, waiting 15 seconds for Azure to spin up instances."
Start-Sleep -s 15
}
}
function Start-Staging {
Write-Host " ... Starting staging slot."
$staging = Get-Staging $azureService
$result = Set-AzureDeployment `
-Status `
-serviceName $azureService `
-slot "Staging" `
-newStatus "Running"
if (-not $?) {
Write-Host
Write-Host "Unable to start staging slot."
Write-Host "DEPLOY FAILED"
Write-Host
exit 1
}
Wait-ForStagingToBeReady
Write-Host " ... Deployment in Staging slot started."
}