Thank you to everyone that attended my talk yesterday at the OpenSource North. It was a great group with great discussion. The slides for this talk are available here.
Adding a job to an Azure Batch AI cluster can be a time consuming task to perform prone to errors due to the many fields that need to be configured. Since all jobs end up in the same resource group it can be difficult to tell which is which. Automatically generated names can help solve this problem.
During implementation of the concept in Part 1 I discovered that Traffic Manager probes were not accurately reporting outages of the web app’s and would still route traffic to improperly functioning web apps. This article corrects that oversight, and combined with Part 1 is a complete solution to enable the usage of Traffic Manager, Web Application Firewall, and Web App’s together.
Thank you to everyone that attended my talk yesterday at Global Azure Day Milwaukee. Let me know if any questions didn’t get answered. Attached are the slides and a link to the demo. Expect blog posts in the next couple weeks that cover some of the details that I glossed over to fit in my hour time slot:
What lead me down this path is my desire to use PAAS whenever possible and avoid IAAS unless its absolutely necessary. Often the number one security requirement for a deployment is to put your services behind a WAF (Web Application Firewall) to offer a first line of defense against many different types of attacks.