HashiCorp Vault on Azure

Meet The Man in the Black Shirt. Donovan Brown is a Principal DevOps Manager on Microsoft's Cloud Developer Advocacy team. Why is DevOps one of the hottest topics? Because it hurts the most. Luckily, Donovan's unofficial tag line is #RubDevOpsOnIt and he's here to make it all better. Before joining Microsoft, Donovan spent seven years as a Process Consultant and a Certified Scrum Master. Developer Tools are his thing. Donovan has travelled the globe helping companies in the U.S., Canada, India, Germany, and the UK develop solutions using agile practices, Visual Studio, and Team Foundation Server in industries as broad as Communications, Health Care, Energy, and Financial Services. What else keeps the wheels spinning on The Man in The Black Shirt? Donovan's also an avid programmer, often finding ways to integrate software into his other hobbies and activities, one of which is Professional Air Hockey where he has ranked as high as 11 in the world.
Comments
How Windows, Windows Store, Xbox & Surface moved their 350gig source repo into Git hosted on VSTS
@Shafiq Jetha: Thanks so much. Here is the book that taught me not to hate Git! :) Ry's Git Tutorial
Interview with Munil Shah (Quality)
I will work with @munils to have him back on the show again.
Interview with Munil Shah (Quality)
Thanks for watching.
Interview with Munil Shah (Safe Deployment Questions Answered)
@Steve: Every ring is production. We just deploy to different rings to control exposer.
You can learn more here RunAsRadio: DevOps Practices inside Microsoft with Donovan Brown and Martin Woodward where Martin shares our DOD as:
Delivered into production, collecting telemetry from customers that proves or disproves the hypothesis of why we added the feature.
You can also watch Munil's first show about Safe Deployment.
Interview with Munil Shah (Safe Deployment Questions Answered)
@Migas: Before replying I took a peek and we were running 10 builds at this very moment in parallel. I posted a pic here.
Interview with Munil Shah (Safe Deployment Questions Answered)
@Stalen: Hi Stalen, I could not agree more. Weird was a bad choice of words. The point we were trying to make was although we use VSTS for 48 hours before we release to the next ring we do not test every scenario.
.NET development in Azure with Visual Studio Team Services
There are a couple options depending on your target.
Azure DevOps Projects
Yo Team
Continuous Delivery Tools for Visual Studio
docs.Microsoft.com
We also have templates to get you started when you create a new build.
What we wanted Jessica to show was a little more advanced scenario.
The links above will point in the right direction to just get started.
Ping me on Twitter @DonovanBrown if you need help.
Interview with Munil Shah (Safe Deployment)
@Manuel Wellman:The issue was in a dependency.
"In that deployment, we pulled in version 5.1.4 of the System.IdentityModel.Tokens.Jwt library. This library had a performance regression in it that caused CPU utilization on the SPS web roles to spike to 100%."
Taking a dependency is not like adding a feature you can turn on or off. Either you take the dependency or you do not.
VSTS Work Item Rules
@David_Lean: I could not agree more. As I said in the video I hope people don't go crazy with this. When I was a consultant I spent a lot of my time talking customers out of customizing the template. Take the time to really learn why the template is the way it is before you change it.
Ask yourself why are we moving from where we are now to VSTS? The answer normally is because the tool/process you have today is lacking. So why customize VSTS back to the tool you are leaving?
The out of the box process templates are great and have been shaped over a long period of time. They have best practices and years of team experiences baked in.
After sitting with a customer and understanding why the made the customization I realized what they wanted was already in the template they just did not know how to use it.
Here you can read how each process was designed to be used https://docs.microsoft.com/en-us/vsts/work/work-items/guidance/choose-process
Interview with Munil Shah (Safe Deployment)
That is correct. We actually let the code bake in Ring 0 for 48 hours before the deployment to the next ring. Munil and I just recorded another episode today (being produced) where we go into more detail.
Interview with Munil Shah (Safe Deployment)
Munil and I will be recording another show and we will be sure to cover these questions. Thanks for watching.
Interview with Munil Shah (Safe Deployment)
@spottedmah:Munil will be returning to the show and we will dive deeper for you.