What are some of the challenges traditional Microsoft IT Pro’s deal with moving to a more automated DevOps pattern?
Jessica:
Hard to tell which tools are really going to make their lives easier.
Are the cultures of the companies benefiting the human side of the IT Pro?
Jeffrey:
Because Microsoft has great GUI tools, they become the biggest strength and weakness of the DevOps/IT-Pro
The process of using a GUI is much harder to replicate in documentation. Because most of the community uses powershell commands, Microsoft IT-Pros really need to get on board.
IT-Pros are never done with learning. If you don’t want to learn anything new, get into the lumber business.
Microsoft has been making more open source integration moves, and changing philosophies to accept the Open Source community. “What up with that?”
Jeffrey: “The body follows the head”
It helps when you have a leader with a fresh approach who focuses on customer service and helping users within the community
Jessica: It is really exciting to get behind a leader that is welcoming to the communities.
It is refreshing to see Microsoft becoming a software company, not a “Windows software company”
Microsoft wants you to be successful. Tools such as RESTful APIs are becoming available across all OSs.
What is the acceptance level of the OpenSource movement within Microsoft?
Jessica: Whatever you’re running, we can host it for you
Traditional Configuration Management in Microsoft has been difficult. What are the plans?
Steve Morowski (http://stevenmurawski.com/) has good info for those interested in DevOpsing with Windows.
Current Microsoft tools are really good for enterprise, client management. Not so good for data center management.
We need something different, that is simple, and usable.
The problem is, everyone wants to do configuration their way. They want to be the CTO of their servers.
Jeffrey describes the creation, and idea conception of a Microsoft Configuration Management platform that takes into account the deep differences between Linux, Unix, Windows. Describing different tools currently available, their faults, and how they might be able to connect them for modern, DevOps oriented, Configuration Management.
The ability of chef and puppet, etc. are beneficial because of the ability of devs to pick it up, version it, and insert small parts of just what they need into the configuration.
Jessica: We are getting to the point where Microsoft DevOps engineers are adapting the powershell. Until the powershell is adopted by IT-pros, modern DevOps tools will be a difficult push.
You should already love powershell.
How can people get more comfortable with powershell?
Matt: It is not a scripting language. It is the way you interact with a system. Don’t write scripts in bash, write commands in bash that emulate the scripts.
Poweshell makes your environment repeatable, automatable, stable, etc. It is the future of the IT pro, and people must adopt it.
Are we automating ourselves out of jobs?
Jeff: The cloud is a great, cheap place to offer undifferentiated IT, however, if you can provide differentiated IT you are practically printing money vs. the cloud.
Jessica: We do need a healthy fear. Not of automation though. Be scared of more interesting things. You need to learn automation.
How do we work with Microsoft when its just not the best for DevOps-ing?
As more people us Microsoft, the more Microsoft changes. Jeff discusses the many ways in which Microsoft is using flexible R&D to make a push for DevOps tooling, as well as some tools coming down the pipeline.
Jessica: When choosing a tool, the longevity of the tool and the community around it is critical.
