In a previous post I mentioned how Network needed to adopt DevOps principles in order to achieve the speed and agility required to meet the business needs (As a reminder, that post is here [https://blogit.michelin.io/netdevops-or-devnetops/] ). What does that really mean and how does a company start
Here our journey together almost comes to an end with the third article of this series "moving from orchestration to choreography". In part 1 [https://blogit.michelin.io/choregraphy-or-orchestration-thats-the-question/], I explained how we convinced our organization to get rid of our Business Process Management solution and adopt an event driven
Purpose A typical modern cloud-based application is structured as below diagram. Functions are implemented by microservices as APIs, which are running in the containers and managed by Kubernetes cluster. Data are persisted in RDBMS, NoSQL database or Object Storage. Users are accessing the APIs via different type of devices and
/!\/!\/!\---WARNING---/!\/!\/!\ Seizures caused by light are known as photosensitive epilepsy. Content that flickers, flashes, or blinks can trigger photosensitive epilepsy. CRT are known for photosensitive epilepsy issues. Therefore you can use the according button below to disable the flickering. The other button starts the flickering, and/or restore from disabled
> Providing High Performance Computing as a service R&D and simulation Michelin’s HPC (High Performance Computing) clusters run thousands of computations each day. Hundreds of people, whose job is not related to IT, have to familiarize themselves with command line syntaxes and scripting, in order to use these clusters
At Michelin, like most organizations, COVID-19 brought us an increased need and usage of Virtual Desktop Infrastructure (VDI) [https://www.vmware.com/topics/glossary/content/virtual-desktop-infrastructure-vdi#:~:text=Virtual%20desktop%20infrastructure%20%28VDI%29%20is%20a%20technology%20that,to%20end-users%20on%20request.%20How%20does%20VDI%20work%3F] in a Public cloud
Introduction Over the past years, we at Michelin Group, have been trying to think about how to deeply change the way we plan, build and operate our information system to adapt to the VUCA [https://en.wikipedia.org/wiki/Volatility,_uncertainty,_complexity_and_ambiguity] world and we have many transformations
In the first article [https://blogit.michelin.io/choregraphy-or-orchestration-thats-the-question/] of this serie, we've been through the preliminary work to convince our organization to move from a central orchestrator (implemented with a Business Process Management tool) to a choreography of micro-services. This second article will focus on a critical step of
The purpose of this post is to highlight monitoring in Michelin North America; not just the tools and technologies available, but also the different kinds of monitoring, available tools, and our evolving process to add value through these activities. The Problem Michelin instituted a control tower a few years ago.
The intent of this article is to explain how we deployed widely Azure Private Link on PaaS Services and how we tackled the DNS part of this technology, both for on-premise and Azure machines/workstations. Azure Private Link Azure Private Link [https://docs.microsoft.com/en-US/azure/private-link/private-link-overview] is
This article will retrace Michelin journey around containers and container-orchestration (Kubernetes) systems over the last 3 years. We believe that this feedback is interesting because we made strong choices from both a technical and an operational point of views. First things first, why have Michelin invested efforts on such technologies?