Use ARM templates instead of MAML

[isaacabraham]

Azure ARM (https://azure.microsoft.com/en-us/documentation/articles/resource-group-authoring-templates/) templates now (allegedly) have support for service bus. We should investigate and move over to this rather than the current C# based approach for creating MBrace clusters. There are several benefits, including: -

1. No need to download publish settings file - users can provide credentials on deploy, or create a service principal to act on their behalf.
2. Deployment fits inside a "resource group" - a logical container of Azure services required by the application. To remove a cluster, you simply remove the resource group and all the resources are removed atomically.
3. Will simplify a lot of the MBrace.Azure.Management codebase.

[isaacabraham]

OK - this is on hold because Cloud Services aren't supported in ARM (yet). I'm waiting for that to become available, or to move across to Service Fabric (which is supported).

[isaacabraham]

We're looking at pushing a lightweight version of MBrace over the Azure App Service in the next days. It'll (hopefully) simplify a lot of the deployment / management side of things, as well as open up a number of doors going forwards.

[isaacabraham]

cc: @bruinbrown

[isaacabraham]

Just an update on this. We have an ARM template model over app service. This really should be merged into this main repo and added to the build / release process. Doing this also means that someone can deploy an MBrace cluster from a single text file - no need to upload the actual MBrace runtime to the service yourself.