Serverless computing is more than just "someone else's server.” Correctly applied, it can speed up your time to market and reduce costs - but it requires a new way of thinking about software.
In this talk, David will share key learnings from his upcoming book, The Value Flywheel Effect with IT Revolution. During his tenure with Liberty Mutual, a Fortune 100 company, they shifted their mindset to stop building commodity products and learn to leverage the true potential of serverless.
This document summarizes a presentation on "Infrastructure as Code" for beginners. It discusses automating deployment, provisioning, environments, and virtual machine management through continuous integration/delivery practices and configuration management tools. Specific topics covered include deployment pipelines, desired state configuration, separating configuration for different environments, immutable infrastructure patterns, building golden images, and infrastructure automation through tools like Ansible, Packer and Terraform. A demo is provided to illustrate these concepts in action.
Nasuni provides a cloud-based file storage solution that offers unlimited scalability, built-in data protection with infinite snapshots, and accessible files from any location. It has over 200 clients with over 8 petabytes of stored data across 1,400 filers in 46 countries. Case studies show Nasuni providing significant cost savings over traditional file storage systems, improved file access times, and better data protection capabilities.
Sécurisez votre software supply chain avec SLSA, Sigstore et KyvernoMohamed Abdennebi
Si vous tombez un jour sur une clé USB posée négligemment sur la table d'une salle de réunion, la brancheriez-vous dans votre portable ? "Jamais !" me diriez-vous.
Pourtant, c'est ce que nous faisons presque tout le temps avec les dépendances logicielles que nous récupérons d'Internet.
Ces dépendances ou artefacts sont devenus si complexes que nous ne maîtrisons plus leur contenu ou leurs dépendances transitives. Cette complexité s’étend à nos chaînes de production logicielle qui peuvent être corrompues à des endroits multiples : le référentiel de code source, le système de build ou le registre d'artefacts.Pour sécuriser notre chaîne de build ou "software supply chain", nous devons être capables de vérifier l'authenticité et l'intégrité des dépendances. De même, en tant que producteurs d'artefacts, nous devons garantir un niveau équivalent de sécurité et de transparence à nos consommateurs. Mais comment faire sans alourdir la chaîne CI/CD ni nuire à la productivité du développeur ?
La réponse ? C’est la communauté open source qui l’a apportée avec SLSA et Sigstore, principaux sujets de ce talk.
Pour commencer, nous parlerons de SLSA dont le but est de vous accompagner dans l’amélioration de votre chaîne de build en appliquant de bonnes pratiques de sécurité par paliers successifs.
Nous parlerons également de Sigstore et de la manière avec laquelle il permet d’implémenter SLSA en rendant transparente la signature et l’attestation des artefacts.
Nous clôturerons le talk par une démo sur la protection des déploiements dans Kubernetes à l'aide du moteur de règles "Kyverno".
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
This document outlines the key responsibilities and skills required for a DevOps role, including experience with systems administration, virtualization, scripting, development, continuous integration, automation, cloud platforms, and monitoring tools. It also emphasizes the importance of configuration management, strict service level agreements, and an escalation process for problem resolution.
18 Months to Migrate 800 Applications: State Farm’s Transformation JourneyVMware Tanzu
SpringOne 2020
Jeff Anderson: Architecture Manager, State Farm Insurance;
Ryan Alberti: Technology Manager, State Farm Insurance;
Matt Hubbard, Technology Engineer, State Farm Insurance
Serverless computing is more than just "someone else's server.” Correctly applied, it can speed up your time to market and reduce costs - but it requires a new way of thinking about software.
In this talk, David will share key learnings from his upcoming book, The Value Flywheel Effect with IT Revolution. During his tenure with Liberty Mutual, a Fortune 100 company, they shifted their mindset to stop building commodity products and learn to leverage the true potential of serverless.
This document summarizes a presentation on "Infrastructure as Code" for beginners. It discusses automating deployment, provisioning, environments, and virtual machine management through continuous integration/delivery practices and configuration management tools. Specific topics covered include deployment pipelines, desired state configuration, separating configuration for different environments, immutable infrastructure patterns, building golden images, and infrastructure automation through tools like Ansible, Packer and Terraform. A demo is provided to illustrate these concepts in action.
Nasuni provides a cloud-based file storage solution that offers unlimited scalability, built-in data protection with infinite snapshots, and accessible files from any location. It has over 200 clients with over 8 petabytes of stored data across 1,400 filers in 46 countries. Case studies show Nasuni providing significant cost savings over traditional file storage systems, improved file access times, and better data protection capabilities.
Sécurisez votre software supply chain avec SLSA, Sigstore et KyvernoMohamed Abdennebi
Si vous tombez un jour sur une clé USB posée négligemment sur la table d'une salle de réunion, la brancheriez-vous dans votre portable ? "Jamais !" me diriez-vous.
Pourtant, c'est ce que nous faisons presque tout le temps avec les dépendances logicielles que nous récupérons d'Internet.
Ces dépendances ou artefacts sont devenus si complexes que nous ne maîtrisons plus leur contenu ou leurs dépendances transitives. Cette complexité s’étend à nos chaînes de production logicielle qui peuvent être corrompues à des endroits multiples : le référentiel de code source, le système de build ou le registre d'artefacts.Pour sécuriser notre chaîne de build ou "software supply chain", nous devons être capables de vérifier l'authenticité et l'intégrité des dépendances. De même, en tant que producteurs d'artefacts, nous devons garantir un niveau équivalent de sécurité et de transparence à nos consommateurs. Mais comment faire sans alourdir la chaîne CI/CD ni nuire à la productivité du développeur ?
La réponse ? C’est la communauté open source qui l’a apportée avec SLSA et Sigstore, principaux sujets de ce talk.
Pour commencer, nous parlerons de SLSA dont le but est de vous accompagner dans l’amélioration de votre chaîne de build en appliquant de bonnes pratiques de sécurité par paliers successifs.
Nous parlerons également de Sigstore et de la manière avec laquelle il permet d’implémenter SLSA en rendant transparente la signature et l’attestation des artefacts.
Nous clôturerons le talk par une démo sur la protection des déploiements dans Kubernetes à l'aide du moteur de règles "Kyverno".
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
This document outlines the key responsibilities and skills required for a DevOps role, including experience with systems administration, virtualization, scripting, development, continuous integration, automation, cloud platforms, and monitoring tools. It also emphasizes the importance of configuration management, strict service level agreements, and an escalation process for problem resolution.
18 Months to Migrate 800 Applications: State Farm’s Transformation JourneyVMware Tanzu
SpringOne 2020
Jeff Anderson: Architecture Manager, State Farm Insurance;
Ryan Alberti: Technology Manager, State Farm Insurance;
Matt Hubbard, Technology Engineer, State Farm Insurance
The document is a presentation on Azure DevOps. It introduces Azure DevOps as a solution for continuous delivery that brings together people, processes, and products. It discusses key DevOps concepts like continuous integration, continuous deployment, and continuous monitoring. It then describes the main Azure DevOps services - Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for build/release, Azure Test Plans for testing, and Azure Artifacts for packages. It emphasizes that Azure DevOps supports all languages/platforms and can integrate with other tools.
Learn why VSTS and Azure should be core components of your DevOps strategy. This presentation will be an excellent resource to discover key DevOps practices, for example, CI/CD pipeline automation and environment provisioning.
Windows Azure Backup provides a simple and reliable way to backup server data to the cloud. It encrypts backup data stored in Windows Azure storage for security. Backup and recovery is efficient using network and storage resources optimally. Windows Azure Backup integrates with existing Microsoft backup tools and provides offsite data protection in the cloud. To use it, organizations sign up for a Windows Azure account, enable Windows Azure Backup, configure backups and it charges per GB of storage used each month.
Azure Migrate is a central hub of tools for datacenter cloud migrations that provides:
1) Discovery, assessment, and migration of servers, databases, applications, and data to Azure.
2) End-to-end visibility and tracking of the migration process through a centralized migration repository.
3) Diverse capabilities powered by Azure and partners to discover, assess, and migrate servers, databases, web apps, and virtual desktops.
Presentation is about benefits of Azure Automation. How Azure Automation service can help you to automate your on premises as well as off premises resources.
Azure DevOps provides enterprise-grade continuous delivery and release automation capabilities in the cloud with a 99.9% SLA and 24x7 support or on-premises with DevOps Server. It offers source code management, automated builds, requirements management, reporting and new features every three weeks in both cloud and on-premises environments.
Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anyt...Janusz Nowak
Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anything to Anywhere with Azure DevOps
Janusz Nowak
@jnowwwak
https://www.linkedin.com/in/janono
https://github.com/janusznowak
https://blog.janono.pl
The document contains a series of links to images without any connecting text. The images appear to be related to agile software development practices and include depictions of sprints, backlogs, planning poker, burndowns, retrospectives and other agile concepts.
This document provides an overview of agile methodology. It begins with an introduction to the author and their background. It then discusses what agile is, the history and development of agile practices, the 12 principles of the agile manifesto, advantages and disadvantages of agile, how agile addresses software requirements, and common agile methodologies like Scrum, Kanban, and Extreme Programming that are used to implement agile. The document aims to explain agile in simple terms and provide context around its origins and framework.
This document provides an overview of Azure Boards and its key features for tracking work, managing backlogs and sprints, running queries, and viewing dashboards. Azure Boards allows teams to track work using Kanban boards, backlogs, and dashboards. It enables tracking work from idea to release with all code changes linked to work items. Teams can also use built-in tools to help run scrum processes. The tool provides insights into project health using analytics and widgets.
This document discusses agile software development processes. It outlines some common reasons for challenged, failed, and successful projects. Some key problems with the traditional waterfall model are that mistakes are hard to find early on and requirements often change. The document then introduces agile concepts like iterative development, test-driven development, extreme programming, scrum, and their benefits like producing working software earlier, adapting to change, and improved communication.
Enterprise agile transformation is a complex journey. It involves cultural change, org restructuring, reinventing processes and tools, and a visionary who can lead the change.
Steampipe - use SQL to retrieve data from cloud, platforms and files (Code Ca...Lucas Jellema
Introduction to Steampipe - a tool for retrieving data and metadata about cloud resources, platform resources and file content - all through SQL. Data from clouds, files and platforms can be joined, filtered, sorted, aggregated using regular SQL. Steampipe offers a very convenient way to get hold of data that describes the environment in detail.
Microsoft Azure and Windows Application monitoringSite24x7
Monitor all your Microsoft applications and Azure services from a single console.
About Site24x7:
Site24x7 offers unified cloud monitoring for DevOps and IT operations. Monitor the experience of real users accessing websites and applications from desktop and mobile devices. In-depth monitoring capabilities enable DevOps teams to monitor and troubleshoot applications, servers and network infrastructure including private and public clouds. End user experience monitoring is done from 50+ locations across the world and various wireless carriers. For more information on Site24x7, please visit http://www.site24x7.com/.
Forums: https://forums.site24x7.com/
Facebook: http://www.facebook.com/Site24x7
Twitter: http://twitter.com/site24x7
Google+: https://plus.google.com/+Site24x7
LinkedIn: https://www.linkedin.com/company/site...
View Blogs: http://blogs.site24x7.com/
Make It Cooler: Using Decentralized Version Controlindiver
A commonly used version control system in the ColdFusion community is Subversion -- a centralized system that relies on being connected to a central server. The next generation version control systems are “decentralized”, in that version control tasks do not rely on a central server.
Decentralized version control systems are more efficient and offer a more practical way of software development.
In this session, Indy takes you through the considerations in moving from Subversion to Git, a decentralized version control system. You also get to understand the pros and cons of each and hear of the practical experience of migrating projects to decentralized version control.
Version control is often used in conjunction with a testing framework and continuous integration. To complete the picture, Indy walks you through how to integrate Git with a testing framework, MXUnit, and a continuous integration server, Hudson.
Que nos espera a los ALM Dudes para el 2013?Bruno Capuano
The document discusses challenges with application lifecycle management (ALM) and recommends adopting agile practices like Scrum and Kanban to improve project predictability, lower costs, and increase team responsiveness. It emphasizes establishing continuous integration using automated testing, version control like Git, and configuration management. Adopting practices like test-driven development, behavior-driven development, and continuous integration can help address typical ALM problems like lack of visibility, ineffective communication, undefined requirements, and inadequate testing.
The document is a presentation on Azure DevOps. It introduces Azure DevOps as a solution for continuous delivery that brings together people, processes, and products. It discusses key DevOps concepts like continuous integration, continuous deployment, and continuous monitoring. It then describes the main Azure DevOps services - Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for build/release, Azure Test Plans for testing, and Azure Artifacts for packages. It emphasizes that Azure DevOps supports all languages/platforms and can integrate with other tools.
Learn why VSTS and Azure should be core components of your DevOps strategy. This presentation will be an excellent resource to discover key DevOps practices, for example, CI/CD pipeline automation and environment provisioning.
Windows Azure Backup provides a simple and reliable way to backup server data to the cloud. It encrypts backup data stored in Windows Azure storage for security. Backup and recovery is efficient using network and storage resources optimally. Windows Azure Backup integrates with existing Microsoft backup tools and provides offsite data protection in the cloud. To use it, organizations sign up for a Windows Azure account, enable Windows Azure Backup, configure backups and it charges per GB of storage used each month.
Azure Migrate is a central hub of tools for datacenter cloud migrations that provides:
1) Discovery, assessment, and migration of servers, databases, applications, and data to Azure.
2) End-to-end visibility and tracking of the migration process through a centralized migration repository.
3) Diverse capabilities powered by Azure and partners to discover, assess, and migrate servers, databases, web apps, and virtual desktops.
Presentation is about benefits of Azure Automation. How Azure Automation service can help you to automate your on premises as well as off premises resources.
Azure DevOps provides enterprise-grade continuous delivery and release automation capabilities in the cloud with a 99.9% SLA and 24x7 support or on-premises with DevOps Server. It offers source code management, automated builds, requirements management, reporting and new features every three weeks in both cloud and on-premises environments.
Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anyt...Janusz Nowak
Continues Integration and Continuous Delivery with Azure DevOps - Deploy Anything to Anywhere with Azure DevOps
Janusz Nowak
@jnowwwak
https://www.linkedin.com/in/janono
https://github.com/janusznowak
https://blog.janono.pl
The document contains a series of links to images without any connecting text. The images appear to be related to agile software development practices and include depictions of sprints, backlogs, planning poker, burndowns, retrospectives and other agile concepts.
This document provides an overview of agile methodology. It begins with an introduction to the author and their background. It then discusses what agile is, the history and development of agile practices, the 12 principles of the agile manifesto, advantages and disadvantages of agile, how agile addresses software requirements, and common agile methodologies like Scrum, Kanban, and Extreme Programming that are used to implement agile. The document aims to explain agile in simple terms and provide context around its origins and framework.
This document provides an overview of Azure Boards and its key features for tracking work, managing backlogs and sprints, running queries, and viewing dashboards. Azure Boards allows teams to track work using Kanban boards, backlogs, and dashboards. It enables tracking work from idea to release with all code changes linked to work items. Teams can also use built-in tools to help run scrum processes. The tool provides insights into project health using analytics and widgets.
This document discusses agile software development processes. It outlines some common reasons for challenged, failed, and successful projects. Some key problems with the traditional waterfall model are that mistakes are hard to find early on and requirements often change. The document then introduces agile concepts like iterative development, test-driven development, extreme programming, scrum, and their benefits like producing working software earlier, adapting to change, and improved communication.
Enterprise agile transformation is a complex journey. It involves cultural change, org restructuring, reinventing processes and tools, and a visionary who can lead the change.
Steampipe - use SQL to retrieve data from cloud, platforms and files (Code Ca...Lucas Jellema
Introduction to Steampipe - a tool for retrieving data and metadata about cloud resources, platform resources and file content - all through SQL. Data from clouds, files and platforms can be joined, filtered, sorted, aggregated using regular SQL. Steampipe offers a very convenient way to get hold of data that describes the environment in detail.
Microsoft Azure and Windows Application monitoringSite24x7
Monitor all your Microsoft applications and Azure services from a single console.
About Site24x7:
Site24x7 offers unified cloud monitoring for DevOps and IT operations. Monitor the experience of real users accessing websites and applications from desktop and mobile devices. In-depth monitoring capabilities enable DevOps teams to monitor and troubleshoot applications, servers and network infrastructure including private and public clouds. End user experience monitoring is done from 50+ locations across the world and various wireless carriers. For more information on Site24x7, please visit http://www.site24x7.com/.
Forums: https://forums.site24x7.com/
Facebook: http://www.facebook.com/Site24x7
Twitter: http://twitter.com/site24x7
Google+: https://plus.google.com/+Site24x7
LinkedIn: https://www.linkedin.com/company/site...
View Blogs: http://blogs.site24x7.com/
Make It Cooler: Using Decentralized Version Controlindiver
A commonly used version control system in the ColdFusion community is Subversion -- a centralized system that relies on being connected to a central server. The next generation version control systems are “decentralized”, in that version control tasks do not rely on a central server.
Decentralized version control systems are more efficient and offer a more practical way of software development.
In this session, Indy takes you through the considerations in moving from Subversion to Git, a decentralized version control system. You also get to understand the pros and cons of each and hear of the practical experience of migrating projects to decentralized version control.
Version control is often used in conjunction with a testing framework and continuous integration. To complete the picture, Indy walks you through how to integrate Git with a testing framework, MXUnit, and a continuous integration server, Hudson.
Que nos espera a los ALM Dudes para el 2013?Bruno Capuano
The document discusses challenges with application lifecycle management (ALM) and recommends adopting agile practices like Scrum and Kanban to improve project predictability, lower costs, and increase team responsiveness. It emphasizes establishing continuous integration using automated testing, version control like Git, and configuration management. Adopting practices like test-driven development, behavior-driven development, and continuous integration can help address typical ALM problems like lack of visibility, ineffective communication, undefined requirements, and inadequate testing.
The document summarizes Mozilla's migration of its Socorro crash analysis system from its original infrastructure to a new architecture. It describes Socorro and its purpose of analyzing crash data. It then discusses the rationale for migrating to improve stability, the planning process, building out the new infrastructure with automation and configuration management, load testing the new system, troubleshooting issues during the migration, and lessons learned from the process.
Kris Buytaert discusses GitOps and continuous infrastructure. He outlines three cases of organizations transitioning to DevOps and continuous delivery. In Case 1, they started by preparing ops teams to automate. In Case 2, ops were not initially involved, delaying collaboration. In Case 3, "devops" teams dictated tools they did not use, leading to high turnover. Overall, earlier ops involvement creates higher success rates. Ops should use CI/CD tools themselves and treat infrastructure as code to better support applications teams.
Moving to the cloud isn’t easy, transforming your engineering team to adopt to the cloud and services lifestyle is therefore crucial. It all starts with creating a common understanding of the engineering and development principles which are important in the cloud, which are different then building regular applications. This session will take you on a road trip based on the presenters experience developing and more importantly operating Azure Active Directory, SQL Server Azure and most recently the Xbox Live Services to support Xbox One.
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
Devops For Drupal explains the Devops problem, to a Drupal audience .
How Percolate uses CFEngine to Manage AWS Stateless InfrastructurePercolate
The document discusses how Percolate uses CFEngine to manage their infrastructure on AWS in a stateless way. Some key points:
1) CFEngine allows Percolate to define infrastructure policies that automatically enforce the desired configuration on servers, providing a documented and scalable approach.
2) By managing all infrastructure as code in Git, and avoiding server state, Percolate's infrastructure is resilient and can be migrated or changed easily.
3) This stateless approach means Percolate avoids backup overhead and can freely launch/replace instances, reducing costs through use of spot instances.
Continuous Integration, the minimum viable productJulian Simpson
What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration
Database as a Service (DBaaS) on KubernetesObjectRocket
Learn about ObjectRocket's adventures in Kubernetes. We'll cover why we chose Kubernetes for our DBaaS platform, the challenges we faced, and how we overcame them. A presentation for DevWeek Austin 2018.
This document provides an overview of Kubernetes concepts and best practices for evolving applications to run on Kubernetes. It discusses initial "lift and shift" approaches as well as principles for container and application design that are well-suited for Kubernetes. These include having containers do one thing, making images immutable, ensuring self-containment and runtime confinement, and designing for process disposability and observability. The document also covers how people and processes need to change, such as adopting new deployment strategies, defining interaction contracts, and being comfortable with change and new approaches to debugging.
The document discusses challenges with deploying a SaaS platform on-premises for customers. It notes that automation and tools developed for internal use may not work well for external customers due to different constraints around access, networking, security policies and variability between customer environments. Deploying on-premises requires implementing customizations for each unique customer setup, reduces ability to easily fix issues, and significantly increases costs compared to hosting in one's own infrastructure. The document recommends choosing a SaaS model over on-premises if possible to avoid these challenges.
Detecting secrets in code committed to gitlab (in real time)Chandrapal Badshah
Slides from my talk "Detecting secrets in code committed to Gitlab" at OWASP Suffolk on 15th May 2020.
This talk will cover the following:
* Problem we had
* Techniques to solve that
* Existing tools that can help us
* Comparison of tools
* Final architecture and product
* What we learnt from the experiment
* Future enhancements
This talk discusses Stripe's experience adopting Consul early on to manage service discovery and configuration. Some key lessons learned include:
- Initial rollouts had issues like memory leaks and TLS verification failures that caused outages
- Watching all services at once in Consul template led to self-DDOS due to high churn
- Stripe encountered goroutine leaks that consumed memory until fixes were merged upstream
- Moving to generate DNS from Consul template improved stability over watching directly
- Incremental rollout, monitoring, limiting scope, isolation and being willing to help upstream improved experience as an early adopter over time.
Automation: The Good, The Bad and The Ugly with DevOpsGuys - AppD Summit EuropeAppDynamics
A cornerstone of the DevOps philosophy, investment in automation at all stages across the SDLC has increased over recent years. Automation promises velocity and reduced errors, helps foster repeatable processes, and removes the need for long hours on dull, repetitive tasks. So what’s not to like? The downside of automation is that unless applied at the right place in your SDLC it can make a bad process worse. Automation also raises questions around job security, the need for re-skilling in other areas, and tool sprawl if different teams each choose their preferred technology. This session will outline:
-A short chronology of where automation has impacted the modern software stack
-Where it makes the most sense to automate (by identifying your key constraints)
-Best practices for adopting automation and how to identify where it’s working — and where it isn’t
For more information, visit: www.appdynamics.com
DevOpsGuys - DevOps Automation - The Good, The Bad and The UglyDevOpsGroup
DevOpsGuys - DevOps Automation - The Good, The Bad and The Ugly gives an overview of the strengths and weaknesses of DevOps automation, tips on developing your automation strategy, and a high level overview of automation options across the DevOps toolchain.
The options for hosting ruby web application are plentiful, all with different advantages and disadvantages, options, limitations. How to start, how to grow, what are the pitfalls?
With this talk I’d first like to give a short overview of several cloud hosting alternatives such as plain VPS, AWS, EngineYard, Heroku, and provide some insights based on my experience with them – beyond just somehow getting it to run, but also how to handle continuous deployment, how to maintain and scale them.
While Rails already comes with many best practices build in, there are still plenty enough traps for you. We definitely had our fair share, and I’d like to share some of them for your entertainment and learning.
Serverless architectures let you build and deploy applications and services with infrastructure resources that require zero administration. In the past, you had to provision and scale servers to run your application code, install and operate distributed databases, and build and run custom software to handle API requests. Now, AWS provides a stack of scalable, fully-managed services that eliminates these operational complexities.
In this session, you will learn about the benefits of serverless architectures and the basics of the serverless stack AWS provides. We will also walk through how you can use serverless architectures for everything from data processing to mobile and web backends.
AWS DevDay San Francisco, June 21, 2016.
Presenter: Jeremy Edberg, Co-Founder, CloudNative, & AWS Community Hero
OSMC 2021 | Pipeline your Dashboards as CodeNETWAYS
Manage your Dashboards
Reproducible dashboards for the masses , as code,
Reproducible dashboards for the masses , in different environments,
Reproducible dashboards for the masses , reusable.
Years of (not) learning , from devops to devoopsKris Buytaert
This document discusses the history of devops from 2009 to the present. It began as a movement in 2009 in Ghent to improve software delivery using open source tools and has since grown globally with over 250 events held. While tools have evolved from things like Puppet and Jenkins to Docker and Kubernetes, the core challenges of culture change, continuous delivery, monitoring, and cloud infrastructure remain. The document cautions that tools alone will not solve problems and that the industry focuses too much on hype and certification over meaningful change. The key takeaway is that after over 10 years, many organizations still struggle with devops principles due to cultural barriers, and the work of bridging development and operations is ongoing.
Observability will not fix your Broken Monitoring ,IgniteKris Buytaert
This document summarizes a presentation about observability given by Kris Buytaert. The presentation discusses how adopting new observability tools alone will not fix underlying issues with broken monitoring. It provides an example of a large organization that spent a year moving to Prometheus but ended up managing two toolsets without achieving real observability. The presentation recommends first fixing existing monitoring, creating a single source of truth, automating configuration, improving alerts, and learning from metrics before adopting new observability tools. It emphasizes focusing on the goals for observability and involving relevant teams to understand real needs.
From devoops to devops 13 years of (not) learningKris Buytaert
Kris Buytaert discusses the history and evolution of DevOps over the past 13 years since its inception in 2009. Some key themes discussed include the rise and fall of different tools, the importance of culture over tools, and how the industry tends to over-hype and kill off promising approaches. The talk emphasizes that true change happens gradually through people, and that we still have a long way to go to solve problems like broken enterprise cultures and burnout.
Kris Buytaert discusses the problems with dashboard sprawl in Grafana and proposes managing dashboards as code. He introduces Dashboard Manager, a tool for fetching dashboards from a development Grafana instance, comparing them, and uploading them to a production instance. This allows end users to create dashboards in development and then promote them to production in a version controlled and reproducible manner.
Most people will claim that this never happens, others hope it never happens, but it happened on March 10, 2021, and it was not just the 1 datacenter that got impacted, but the whole campus of the provider that got powered down. This talk will explain how our customers survived this outage, how our culture, opensource tooling and automation saved the da(y,ta). A talk about disaster recovery, business continuity plans and building cloud agnostic stacks that survive disasters.
Kris Buytaert argues that while devops tools and technologies will continue to change, the core principles of collaboration between development and operations teams are essential for software delivery. He discusses challenges with adopting devops practices in large organizations and resistance to change from those promoting outdated methods. Buytaert believes the role of devops professionals going forward is to teach others, remain open to learning, and build bridges between different parts of organizations to facilitate cooperation.
10 years of #devopsdays, but what have we really learned ? Kris Buytaert
Kris Buytaert has been involved in DevOps for 10 years, organizing 250 DevOps events across the world. While tools have evolved from things like Puppet and Chef to Docker and Kubernetes, the most important lessons are about culture change and people. Many organizations have paid lip service to DevOps without truly changing culture and processes, and resistance to change remains a major barrier. The future of DevOps is about continual learning and helping others change.
This document discusses continuous infrastructure and delivery. It describes how automation of build, deployment, and testing processes through improved collaboration between developers, operations, and testers allows delivery teams to release changes in hours or even minutes regardless of project size or code complexity. The document also discusses how treating infrastructure as code through configuration management tools like Puppet, Chef, and Ansible supports continuous delivery.
Kris Buytaert discusses the past, present, and future of DevOps. He notes that while tools and technologies will continue to evolve, collaboration between development and operations remains a key requirement. DevOps adoption also faces challenges like broken certification processes, resistance to change from large organizations, and burnout. Ultimately, DevOps is still a work in progress with many organizations just starting their journeys, and its future will depend on continued education and bridging cultural divides between teams.
This document summarizes Kris Buytaert's involvement with DevOps over the last 10 years, including starting DevOpsDays conferences in 2013, organizing over 250 events worldwide with 900+ organizers and 70+ events planned for 2019, as the conference celebrates its 10th anniversary.
ADDO 2019: Looking back at over 10 years of DevopsKris Buytaert
Over the past 10 years of the devops movement:
- DevopsDays global conferences have grown from a single event in 2009 to over 250 events in 2019.
- Topic discussions have evolved from early automation tools to modern topics like containers, cloud platforms, and continuous delivery pipelines.
- While tools are helpful, the speaker emphasizes that culture and collaboration between developers and operations are ultimately more important for organizational success than any specific technology. Adopting devops practices requires change that can be challenging for large enterprises with established cultures.
This document discusses the evolution of devops concepts and tools over the past 10 years since the devops movement began. It notes that early topics focused on culture, automation and monitoring tools. Over time, tooling became more advanced but also more complex. Culture remains important but large enterprises still struggle with devops adoption due to broken cultures. New technologies like containers have created new challenges. Ultimately, devops is about change and people, not just tools. While progress has been made, there is still work to be done to fully implement devops principles and fix issues around tool hype, broken cultures and burnout.
Continuous Infrastructure First Ignite EditionKris Buytaert
This document discusses different approaches to implementing continuous infrastructure and collaboration between development and operations teams. It argues that starting with operations automating their own workflows first allows them to understand the tools and processes before enforcing them on developers, prevents technical debt, and enables delivery and provisioning from the start. Having dedicated operations resources focus on automation leads to improved collaboration and quality over having "devops" teams dictate tools to operations.
Kris Buytaert discusses his transition from developer to operations engineer to consultant. He advocates for starting DevOps transformations with operations skills and involvement to improve success rates and adoption. Buytaert outlines four common transition cases for startups and multinationals, highlighting the importance of cultural and skills alignment between development and operations.
Kris Buytaert gave a talk on open source monitoring tools. He discussed how monitoring used to be an afterthought but new tools now focus on automation and integration. Popular modern tools like Prometheus focus on metrics collection and short-term storage while shipping long-term data to systems like Graphite. Prometheus excels at containerized environments through scraping but can also monitor other systems. Visualization and alerting have many options like Grafana, Icinga, and AlertManager. The landscape continues evolving towards full observability of applications and services.
Devops aims to break down silos between development and operations teams through culture, automation, and continuous integration/delivery. It emphasizes collaboration and automation to allow code to be deployed safely and quickly. Security should be integrated into the devops pipeline through practices like automated security testing on each code change and configuration management to standardize security across environments. Adopting devops and continuous delivery helps improve security by reducing risk through faster issue remediation and increased visibility into systems.
This document discusses the future of DevOps and some challenges it faces. It notes that while DevOps started as a grassroots movement, it has now been commercialized by many vendors. This risks ruining the original ideas by over-emphasizing tools and certifications. Adoption in large enterprises also faces challenges like change resistance. However, DevOps still has a future if the focus remains on culture change rather than just tools. Continuous education is needed to teach its principles to new people and help organizations embrace new technologies over the long multi-year journey of transformation.
Looking back at 5 years of #cfgmgmtcampKris Buytaert
Kris Buytaert has organized Config Management Camp annually since 2014 to bring together practitioners of configuration management tools like Puppet, Chef, Ansible, and others. Over the past 5 years, the event has expanded from a single Puppet Camp to a multi-day event featuring talks, workshops, and collaboration across various communities. Config Management Camp helps advance practices in the field and allows different communities to learn from each other's experiences, as enterprises gradually adopt new approaches to infrastructure automation and management.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
2. • I used to be a developer
• Then I became an Ops person
• Chief Trolling/Travel/Technical Officer @ Inuits.eu
• Chief Yak Shaver @ o11y.eu
• Organiser of #devopsdays, #cfgmgmtcamp, #loadays, ...
• Everything is a Freaking DNS Problem
• Cofounder of all of the above
• DNS : devops needs sushi
• @krisbuytaert on twitter/github
Who am I ?
@krisbuytaert
4. A global movement to improve the quality of software delivery leveraging Open
Source experiences , started in Gent in 2009
Devops definition
@krisbuytaert
10. • Manually Crafted Snowflake
• Copied and modified
• Copied and modified
• Impossible to trace origin
• Impossible to reproduce
• Patching / Security nightmare
Image Sprawling & Golden Images vs JeOS
@krisbuytaert
11. FROM ubuntu
RUN apt-get update
RUN apt-get install -y git
RUN git clone git@github.com:prometheus/prometheus.git
RUN make install
What's wrong with this GW-Basic code ?
@krisbuytaert
13. • Treat configuration automation as Code
• Model your infrastructure
• Development best practices
• Model your infrastructure
• Pipeline your Code
• Test your Code
Infrastructure as Code
@krisbuytaert
14. • Reproducable Environments
• You never deploy 1x
• Local Test environments
• Development / User Acceptance / Testing / Shadow / Production / DR
• HA <- Keep cluster configuration in sync
• Prevent Configuration drift
• Cheap Disaster recovery
• ...
Infrastructure as Code Goals
@krisbuytaert
15. 3 types of tools needed
• Provisioning
• Desired state
• Orchestration
2022 IaC Requirements
@krisbuytaert
16. • Create me an instance of application X
• Container instance
• VM instance
• Service X configuration via API
e.g Terraform , Pulumi
Provisioning
@krisbuytaert
17. • Ensure that this file present / service is running
• With these permissions
• Always / Verified
e.g Chef, Puppet, Salt
Desired state
@krisbuytaert
18. • Non frequent
• Trigger action X on resource Y based on characteristics A,B and or C
• First do X here then do Y there
• One off actions
e.g Ansible, Salt, Puppet Bolt
Orchestration
@krisbuytaert
19. • In computing, an idempotent operation is one that has no additional effect if it is called
more than once with the same input parameters.
• Not idempotent :
echo “root=disabled” >> /etc/someconfigfile
Idempodency
@krisbuytaert
20. Frequent enforcing desired state with reporting =
Automated population of a CMDB (Single source of truth) , with up to date data
Side Effect :
Having a single source from where to generate dynamic configuration
eg. reverse proxy , firewall rules, monitoring configuration, backup configuration
IaC & CMDB
@krisbuytaert
21. • Do you want a reproducible infrastructure ?
• Do you want to reduce manual error ?
• Do you want to achieve desired state ?
• Do you want to have automated configuration for monitoring, metrics, backups,
security etc ?
• Do you want to trivially spin up different identical environments (dev/uat/prod/dr)
• Do you want to be able to detect and prevent config drift ?
• Do you want to prevent image sprawl ?
Questions to ask :
@krisbuytaert
23. • Code is not in source control
• Bolt / Ansible / Terraform is triggered from the admin's local machine
• Works for individual admin
• Doesn't Scale
• Prevents Collaboration
Pattern: It works from my homedir
@krisbuytaert
24. Improvement over $prev, but still doesn't Scale
Collaboration has been improved.
Pattern: It works from my workstation but its in git
@krisbuytaert
25. • Just the operating System
• Maybe some basic services
• Application is untouched
• Partial source of maybes
• Not suitable for derived configuration
• Kill your Silos
Pattern: We only automate the OS
@krisbuytaert
26. • Operating System
• Middle Ware
• Application
Pattern: We automate all the things
@krisbuytaert
31. • Ops use Chef but Devs use Java templating tool
or
• Terraform but Manual changes from UI.
Variants:
• Non centralized code base,
people run code from local forks undoing changes made by colleagues
• Templating tool is not idempotent (ruby sort ? / XML)
• Bonus points if the tool restarts a service on a change
Pattern: Multiple tools overwrite changes
@krisbuytaert
32. • Code is checked into a git repository
• The only way to apply is by central user
Pattern: Centralised apply , from source control
@krisbuytaert
33. • Tool is run once at deploy time then yolo
• manual changes afterwards are not identified or reversed
• State is not enforced, people are afraid to rerun playbooks
• Now we don't dare to update anymore
Orchestraition only mode, no desired state
AKA Yolo or Integrator mode
Pattern: We haven't run it for 6 months
@krisbuytaert
34. • Reporting says it's broken, we are not going to fix it
• Its been disabled for weeks, local modifications break it
• See Config Drift
Pattern: It's broken anyhow .
@krisbuytaert
35. • X < 120
• Periodically we run ensure the state of our Infrastructure
• We prevent config Drift
• We actively monitor broken runs
• We actively monitor change frequency
We have achieved desired state of our infra.
Pattern: We run it every X minutes
@krisbuytaert
36. • We setup everything, it worked for a while
• Then we broke service A ,
• Then something unrelated broke service B
• Automation got blamed
• We are not allowed to enable it again
• Team X doesn't trust automation,
• Often Team X = Security
• We manually make the changes now , but we have visibility on drift.
• We have semi desired state
Pattern: We run it in nooop now
@krisbuytaert
38. What is an Environment , a stack, a platform ?
A logically split of set of servers that together offer a service,
Typically existing in dev/uat/prod flavours
Environments
@krisbuytaert
39. • Limiting Blast radius
• Easy to spin up multiple variants
• Feature flagged code introduction
• And promotion of features
• Clear line of ownership (team bound)
• Same code , different config per environment
• Easier release management
Pattern : Using Environments
@krisbuytaert
40. • Huge blast radius
• Potential Scaling issues
• Difficult to "promote" changes
• Upgrade everthing or write host based if then case spaghetti
• Code duplication :
role_app_dev, role_app_uat, role_app_prod
Pattern : Not using environments
@krisbuytaert
41. • Typically with no environments
• Environment specific config is hardcoded
• See Config drift
Pattern: Config is hardcoded in the code
@krisbuytaert
42. • The same codebase is used
• Only the config data differs
• Multiple Environments possible
Pattern: Config Data defines config per environment
@krisbuytaert
43. • Code is run
• We will see the errors when they happen
• Code is not tested
Pattern: It we don't test
@krisbuytaert
44. • Every config run
• Collect information of the run,
• Store that information
• Be able to query a central source with live, correctly, machine generated data
• Reconfigure services based on changes in that data
• Full lifecycle
• Decomission instance => Automatically Clean out the data
Pattern: Single source of truth
@krisbuytaert
46. • Our Ansible playbook does a git commit to a config repo
• That repo gets checked out on the monitoring server
• Humans also modify this config
• Information is scattered over different tools
• you can't leverage the real power of automation , no dynamic reconfiguration of
resources
therefore configuration is often done manually , but through a tool
Pattern: No single source of truth
@krisbuytaert
47. We have one repo with all
• code
• passwords
• software binaries
Pattern: One repo for all the things
@krisbuytaert
48. "Blue printing"
Building a UI on top of a provisioning framework is typically an intermediate
step before people realize they either need to build in all AAA functionality and
buy a bloated tool.
Or realize git + Terraform solves these problems in a better way.
Pattern: Provisioning from a UI
@krisbuytaert
49. • We have written all code in house ?
• What do you mean there are modules on github to manage apache ?
• We spent about 3 months building our own
Pattern: we ignore the existing codebase group
@krisbuytaert
50. • Aka We do NOT understand Continuous Integration
• We have mapped our environments to git branches
• Obviously they are long running
• We are cherry picking changes from uat to prod
• We don't test those combinations
• We are in merge hell now
Puppet r10k is an antipattern.
So is running your gitops from multiple branches.
Pattern: We love Branching
@krisbuytaert
52. • All of these people say they are doing infrastructure as Code
• Some with 0 real benefit
• Find the patterns you like / dislike
• Implement or remove the ones you please
• My preferences might not fit your use case
Lessons Learned
@krisbuytaert