MBrace.StarterKit Config.ProvisionCluster() failing due to incompatible region & VM size

[roguetrainer]

I am a newbie MBrace user, so this is likely a stupid error by me. :)

I have tried many combinations of region & VM size but always get the same error:

System.Exception: Region "East US" does not support VM size "Standard_D1"
at MBrace.Azure.Management.Infrastructure.checkCompatibility@350-2.Invoke(String message)
at MBrace.Azure.Management.Infrastructure.checkCompatibility@349-1.Invoke(Tuple2[] _arg1) at [email protected](a a) at MBrace.Core.Internals.AsyncExtensions.Async.RunSync[T](FSharpAsync1 workflow, FSharpOption`1 cancellationToken) in C:\Users\eirik\Development\mbrace\MBrace.Core\src\MBrace.Core\Utils\AsyncExtensions.fs:line 101
at <StartupCode$FSI_0021>.$FSI_0021.main@() in C:\Users\XXXXXYYYYY\Documents\Visual Studio 2015\Projects\MBrace.StarterKit-master\HandsOnTutorial\0-provision-azure-cluster.fsx:line 33
Stopped due to error

I have installed the Azure CLI
https://azure.microsoft.com/en-us/documentation/articles/xplat-cli-install/
and checked regions using:
azure vm sizes --location "eastus"
& made sure that the vm size that I am using is supported.

I have tried re downloading the starter kit, rebuilding the solution, editing AzureCluster.fsx etc. but still get the same error. My subscription is "Visual Studio Professional with MSDN".

[isaacabraham]

Hey. Indeed, D1 is definitely support in East US. I'm assuming that you set the subscription appropriately in azure cli before checking regions? VM sizes can be restricted at the subscription level (although I'd be surprised if an MSDN subscription didn't allow D1s).

[roguetrainer]

Isaac, Thanks for responding, esp on a Saturday. I did go through some sort
of procedure in the CLI in which I went to a website, logged in using my MS
ID & then typed in a code. AFAIK, I only have one type of Azure
subscription, which is the MSDN one. I spent a few hours bashing my head on
this one, so will come back to it on another day with a fresh perspective.
I may be doing something silly. Thanks,
Ian

On 23 April 2016 at 16:50, Isaac Abraham [email protected] wrote:

Hey. Indeed, D1 is definitely support in East US. I'm assuming that you
set the subscription appropriately in azure cli before checking regions? VM
sizes can be restricted at the subscription level (although I'd be
surprised if an MSDN subscription didn't allow D1s).

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#152 (comment)

Ian

Ian Buckley
416 538 1678

[isaacabraham]

No worries.

Can you try with an A series VM e.g. A4? I've just tried with a D1 and D2 here and both failed with a different error to you, so I'm starting to think that it might be something to do with the D-series cloud service images that we've built.

[roguetrainer]

Hi Isaac,

I tried this code:
let pubSettingsFile = Config.pubSettingsFile
let pubSettings = PublishSettings.ParseFile pubSettingsFile
let subscription = pubSettings.GetSubscriptionById "Visual Studio
Professional with MSDN"
let myRegion = Region.East_US_2
let manager = SubscriptionManager.Create(subscription, myRegion)
let deployment = manager.Provision(serviceName = "mbracetest", vmCount = 4,
vmSize = VMSize.A4)

The error is:

INFO : using vm size ExtraLarge
System.Exception: Region "East US 2" does not support VM size "ExtraLarge"
at MBrace.Azure.Management.Infrastructure.checkCompatibility@350-2.Invoke(String
message)
at MBrace.Azure.Management.Infrastructure.checkCompatibility@349-1.Invoke(Tuple`2[]
_arg1)
at [email protected](a a)

at
MBrace.Core.Internals.AsyncExtensions.Async.RunSync[T](FSharpAsync1 workflow, FSharpOption1 cancellationToken) in
C:\Users\eirik\Development\mbrace\MBrace.Core\src\MBrace.Core\Utils\AsyncExtensions.fs:line
101
at <StartupCode$FSI_0043>.$FSI_0043.main@() in C:\Users\Ian
Buckley\Documents\Visual Studio
2015\Projects\MBrace.StarterKit-master\HandsOnTutorial\0-provision-azure-cluster.fsx:line
43
Stopped due to error

It could just be a silly error I made early on. I will try to repeat the
process from a clean zip of the starterkit.

Thanks for looking anyway. :)
Ian

On 23 April 2016 at 16:58, Isaac Abraham [email protected] wrote:

No worries.

Can you try with an A series VM e.g. A4? I've just tried with a D1 and D2
here and both failed with a different error to you, so I'm starting to
think that it might be something to do with the D-series cloud service
images that we've built.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#152 (comment)

Ian

Ian Buckley
416 538 1678

[eiriktsarpalis]

I've experienced this before. In my case it was simply related to my subscription's allowance. After spending some time with Azure tech support my problem was resolved by moving to a different region. The problem is that the management API's error messages are often misguiding.

That said, could you try deploying a worker role build of your own through Visual Studio? It still might be an issue with our code.