Oct 1, 2014 at 1:44 PM
Edited Oct 1, 2014 at 2:00 PM
Sorry my little bit confusing post, but I don't know how to continue with WASABi. I have tried almost every trick and most of problems has been tackled. But still I am wondering can I use WASABi any more. All articles those I read are from year 2012 and this
makes me little bit uncertain. So maybe I describe little bit my environment and statement.
I have Azure solution which is converted to Azure solution. It have one web role for web site and one worker role for In-Role Caching. I want to handle elasticity by custom rules. Major reason to use WASABi is to take average CPU usage from 5-10 minute range
since Azure Autoscaling in management portal uses hour. I don't know the way how to change that hour to e.g. 5min. I have been followed many WASABi tutorials *) but still I am struggling with errors and problems caused by libraries and so on.
My development machine have now Windows 8 and Azure environment is Windows Server 2012 R2. That Azure project has been developed originally with VS2013, .NET 4.5 and Azure SKD 2.4 (currently newest). I have been understood that WASABi works only with Azure
SDK 1.6 so I installed that also and now I have needed dll's included in project. Now I use also VS2012 because Enterprise Library Config editor doesn't work with VS2013.
WASABi has been hosted in In-Role Caching role (in onstart-method) by using simplest routine calls (create scaler and start) which is using .net 4.0. Rules and services has been declared and app.config has been set as in tutorials. I don't believe these are
the problem. I store rules.xml and services.xml in blob storage.
- Is my environment/solution correct to use WASABi?
- Which is best practice to host autoscaling code?
- Can I use dll's from different SDK's in same azure solution?
- Will there be problems when publishing this kind solution to Azure since there is Windows Server 2012 R2?
- Has anyone done solution in year 2014 which implements WASABi and uses Azure SDK 2.4 and also successfully published it to Azure?
*) tutorials used e.g.