Aucune remarque pour cette diapositive
Below are products offered by Microsoft to assist in the adoption of DevOps for an organization:
VSTS: CI/CD/RM/Unit Testing
Azure Resource Manager: IaC
Visual Studio Enterprise provides an integrated end to end solution for teams of any size with demanding quality and scale needs. The included set of comprehensive tools and services for designing, building and managing complex enterprise applications begins with Visual Studio Enterprise.
Visual Studio Team Services provides an interface for teams to share code, track work and ship software – for any language, all in a single package. The perfect complement to your IDE.
Connectivity to Azure Marketplace and Developer Services provides you an online store for thousands of certified, open source, and community software applications, developer services and data-pre-configured for Microsoft Azure, Simply download, deploy, and get more done.
Open Source on Azure: Makes DevOps easier to implement because it’s open and flexible, offers a wide range of toolsets for automation and configuration, and simplifies provisioning.
Management: Puppet, Chef, Ansible Mesos
Applications: Drupal, Wordpress, Joomia!
Development frameworks: nodeJS, Python, Java, PHP
Databases: Hadoop, MySQL, MongoDB
Infrastructure: Red Hat, Linux, Ubuntu
Containers: Docker, Mesosphere
Provisionning des machines à la demande (en prod et en tests)
Mise à jour OS/Update/Security par itération (lotissage)
2 axes de collaboration à construire :
La prise de compte du mécanisme d’apps balancer
La remontée de bugs
We mentioned “Team Chat” earlier, but we wanted to talk a little bit more about these. These chats connect senior leadership with the engineering teams to have a quick “scrum standup” style meeting on the progress and direction of the product. That’s not to say that the folks in the middle aren’t involved – they are, but the focus is the discussion between senior leadership and the team.
In the standup style, the Team Chats focus on these three questions:
Are there any issues in the way, any impediments?
What's your technical debt situation?
What's next on your three-sprint roadmap?
This allows for visibility across teams and for senior leadership to make adjustments to deliver on the primary business goals, the focus is on learning as we build software.
We’re going to start shipping every sprint. “You can’t cheat shipping”. Stop shipping and bad behaviors creep in. We will deploy every 3 weeks, period.
Activity Logging. We gather all data about web requests made against the VSO services. This allows us to track execution time and count of every command, so that we can determine if particular calls or dependent services are being slow or retrying too often.
Traces. Any error triggers a stack trace so that we can debug a call sequence after the fact.
Job History. Jobs are workflows that orchestrate activities across the service.
Perf Counters. These counters are familiar to anyone who has done performance debugging and they track that the system resources are in a healthy state. VSO generates about 50M events per day.
Ping Mesh. This is a very quick visualization of the network base layer to make sure that connectivity is available worldwide.
Synthetic Transactions. These are also called “outside-in tests” and are run with our Global Service Monitoring. They report health form points of presence around the world. Our Journey to Cloud Cadence, Lessons Learned at Microsoft Development Division.
Customer Usage. For usage, we measure our “front-doors,” conversion funnel, engagement and top customers.
KPI Metrics. These are aggregated metrics that the telemetry system calculates to determine the business health of the service.