Replacement for Azure SDK Powershell Commands for Deployment
We are experiencing a New-Deployment Azure Powershell command line timeout issue; we have delivered a bug report with MS. Although they gave us an explanation (the path and timeout threshold used for uploading via cmdlets is different from what the web portal uses); they have no problem for us.
We need to do this run so we can automate the build deployment, so we are looking into developing a custom command item to replace a new deployment using the Azure SDK; hoping that this path won't have a timeout problem that the command signal gave. But before we go down this route; are there any other scripting tools I can use to replace the functionality of the new deployment? I looked at Cloudberry for Windows Azure ; but it doesn't have a scripting interface yet.
Any constructive input is appreciated.
a source to share
FYI, we solved this problem by writing a custom tool to download the package with a higher allowed latency; and also using CSManage ( http://code.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=windowsazuresamples&ReleaseId=3233 ) to create a post-download deployment.
a source to share
If you are developing worker roles, you can reuse the dynamic build loading system that comes with the Lokad.Cloud runtime.
Basically, you just need to upload a ZIP archive containing all your DLLs into the Blob store and the framework takes care of the rest. Added bonus: Workplace reboot takes about 10 seconds (vs + 10min for classic deployment).
Similar behavior could be obtained with web roles, but this part has not yet been implemented in Lokad.Cloud.
a source to share