Saving full azure configuration to file?

Is there a way to save the complete state of my azure configuration?

Basically, I just created a demo for a project I am working on. This demo has a website / webjob, scheduler, storage queue, memory block, redis cache, and documentDB. I configured these components in terms of size / scale / schedules, but the demo is now complete.

I don’t want to pay for these services and now I don’t need them online. However, I don't want to create and reconfigure them if I need to restart the demo in a month. Is there a way to keep my current blueprint configurations for a file and then re-create all services again (with a script or a small program)?

Thank!

+3


source to share


2 answers


This is a very good question that summarizes the historical issue that we are trying to make more flexible and flexible. I will answer this question in two parts.

First of all, you now have tools like PowerShell cmdlets that you can script to create an entire "world" in Azure and then re-run when you want, against a subscription, going beyond the whole architecture. You can also use the .NET control libraries to do this from within a .NET application. For example, when we started working with the VS WebJobs tools, I developed a prototype for my developers to use MAML to create collections of WebJobs and scheduler jobs. You can see the demo code for that here: https://github.com/bradygaster/maml-demo-scheduled-webjob-creator



We also recently embarked on a new mission to re-create many of the management APIs to support the notion of templates and resource groups to marry a new portal experience. Here's an excellent MSDN article that discusses how the Gallery PowerShell cmdlets can be used to list various templates that could then be discarded as fully baked architectures running in Azure. You have the ability to create these templates yourself, then you can use these cmdlets to overclock and create things that you write in your own templates. http://msdn.microsoft.com/en-us/library/dn654596.aspx

Hope this helps!

+1


source


For Azure websites, you can use Back and Restore to save the site and restore it back when you want to demo again, but all you have to do is stop the services and you should be able to save the demo cost.



0


source







All Articles