DevOps Days Madrid 2020

Si quieres ver el vídeo con las slides: https://youtu.be/eiX-pSdfJEg ------------- We’re told that adopting DevOps can have all sorts of benefits, but many organizations are not getting the results they hoped for. The term “DevOps” has been co-opted to mean anything from tools to a job title. Without an understanding of what DevOps is really all about, success is elusive. In this session, Ken Mugrage presents DevOps as an overhaul to existing software development organizations and processes. He talks about organizational structures that enable team members to take full advantage of the automation and visibility gained with a DevOps-enabled culture. Ken will then discuss evolutionary software architectures and platforms to enable continuous delivery, as well as how to make your CD pipeline available to all parts of your organization. You will leave with an understanding of what DevOps really means and how to begin your journey. You will take home tips and techniques for helping you deliver better software, faster ------------- Otras charlas de DevOps Days también en podcast: https://lk.autentia.com/DevOpsDays20-iVoox ¡Conoce Autentia! Twitter: https://goo.gl/MU5pUQ Instagram: https://lk.autentia.com/instagram LinkedIn: https://goo.gl/2On7Fj/ Facebook: https://goo.gl/o8HrWX

Si quieres ver el vídeo con las slides: https://youtu.be/P-jZX5_sZKo ------------- En esta charla cuento el camino que comenzamos hace algo más de 5 años para implantar automatización tanto de gestión de la configuración como de infraestructura como código y que a día de hoy seguimos llevando a cabo en STR Sistemas principalmente con ansible y terraform. Tenemos la particularidad de gestionar múltiples clientes, con múltiples plataformas, proveedores y tecnologías. En la charla se explora cómo gestionamos el código, cómo hemos evolucionado con las herramientas y cómo sus versiones han influido en ello, cómo gestionamos las credenciales, la importancia en la retrocompatiblidad de cambios, lo que queremos hacer a futuro, etc. ------------- Otras charlas de DevOps Days también en podcast: https://lk.autentia.com/DevOpsDays20-iVoox ¡Conoce Autentia! Twitter: https://goo.gl/MU5pUQ Instagram: https://lk.autentia.com/instagram LinkedIn: https://goo.gl/2On7Fj/ Facebook: https://goo.gl/o8HrWX

Vídeo with the slides: https://youtu.be/gFNTiTMVqjE ------------- Kubernetes helps us tame sprawling microservices architectures and addressing the increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services. Yet, the elephant in the room is that to run, maintain and evolve the Kubernetes clusters, we need more ops expertise and most likely a dedicated team to do so. The question that begs to be asked is if we are going back to pre-DevOps isolation between Dev and Ops teams? Is the tradeoff between better operational tools and introducing a new dependency layer on the path for application teams to deliver and run their services worthwhile? Are we making life easier for application teams or instead reducing their end-to-end ownership? Team Topologies is a structured approach for thinking about teams responsibilities and interactions which can help us get the most value out of Kubernetes adoption. This talk draws on research and case studies from the Team Topologies book by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world. ------------- Otras charlas de DevOps Days también en podcast: https://lk.autentia.com/DevOpsDays20-iVoox ¡Conoce Autentia! Twitter: https://goo.gl/MU5pUQ Instagram: https://lk.autentia.com/instagram LinkedIn: https://goo.gl/2On7Fj/ Facebook: https://goo.gl/o8HrWX

Otras charlas de DevOps Days también en podcast: https://lk.autentia.com/DevOpsDays20-iVoox We now have lots of “tools” for operations in cloud-native. Yet they all seem to suffer from the impact of single POV. And at the same time, we have more complexity, in infrastructure with the adoption of orchestration, cloud elasticity, microservices and FaaS. Piled on with heavily request-driven models, the old style of reacting to anomalies and headaches fails. With RED, unlike the modern belief in metrics, your architecture is watched from aspects of multiple dimensions. You receive alerts and indications not just from anomalies, but also from headache alerts. By seeing multiple dimensions of concerns, be they failures in service or activity to close to the edge of capability, these combined monitors and deep-dive, focused access get you to your root cause faster, with less false positives and quicker resolution. Thus, we need an understanding of RED, designed to meet the precise conditions now prevalent in our applications. RED clearly has advantages over competing models (Golden Signals and USE) specifically with respect to DevOps models (and Devs). Through a deep dive into what this multi-dimensional problem AND multi-dimensional approach to resolution will help reduce the production scale and fail panics we see in the industry. So RED gives you the framework to build alerting, monitoring and analysis into a flexible structure to meet the emerging needs of services-based cloud-native architectures as well as give you the capability to grow as your environment scales. This talk will dive into RED, what it is and how it fits in the modern world of services and explore how RED can expand to deliver faster Mean Time to Recognize and Mean Time to Respond.

Otras charlas de DevOps Days también en podcast: https://lk.autentia.com/DevOpsDays20-iVoox Over an eight-month period, our organization formed a dedicated internal DevOps team. This team initially focused on fighting the fires currently in production and dedicated to improving the reliability of services in the company. The team’s focus was shifted from not just keeping things up, but eventually improving the experience for our own developers. In this talk, attendees will learn about the cultural changes that took place going from reactive operations to being dedicated to improving overall reliability across the technology organization. We’ll look at some of the internal tools we’ve developed to reduce developer onboarding time and support toil. Automation related to provisioning resources and AWS accounts.