In the age of automated infrastructure our monitoring tools need to be capable of being automated , we need to be able to deploy new services and hosts and know that they are monitored. Puppet can obviously help us here.
But in the age of the chaos monkey our puppet infra needs to be monitored too. So how do you monitor Puppet and its friends itselve ?
This talk will give you some ideas on monitoring a puppetmaster with it's friends , PuppetDB, etc ..
Package all the things, from #ihatepackaging to #packagingloveKris Buytaert
Slides as presented at LinuxCon 2014 in Dusseldorf
Automated Software Delivery on Linux,
Continuous Delivery of software on Linux ,
As operations persons we like to have software installed from apt or yum repositories in clean packages.
We want to be able to trace the origin of a file and have smooth upgrade paths.
But distributions make it hard on us, then languages reinvent the wheel, then developers want to ship software in different ways ..
fpm, fpmcookery, omnibus, specfiles to the rescue, or chaos and hairpulls.
This talk will guid you trough the maze of how to deploy software, from different sources in a sane way.
How and when to use different packaging tools that will make your life easier, and how this approach will help you in growing towards a #devops approach
My DrupalCon 2014 Amsterdam talk, introducing the audience to #devops and the current state of #devops and Drupal based on the 2014 Drupal and Devops Survey
In the age of automated infrastructure our monitoring tools need to be capable of being automated , we need to be able to deploy new services and hosts and know that they are monitored. Puppet can obviously help us here.
But in the age of the chaos monkey our puppet infra needs to be monitored too. So how do you monitor Puppet and its friends itselve ?
This talk will give you some ideas on monitoring a puppetmaster with it's friends , PuppetDB, etc ..
Package all the things, from #ihatepackaging to #packagingloveKris Buytaert
Slides as presented at LinuxCon 2014 in Dusseldorf
Automated Software Delivery on Linux,
Continuous Delivery of software on Linux ,
As operations persons we like to have software installed from apt or yum repositories in clean packages.
We want to be able to trace the origin of a file and have smooth upgrade paths.
But distributions make it hard on us, then languages reinvent the wheel, then developers want to ship software in different ways ..
fpm, fpmcookery, omnibus, specfiles to the rescue, or chaos and hairpulls.
This talk will guid you trough the maze of how to deploy software, from different sources in a sane way.
How and when to use different packaging tools that will make your life easier, and how this approach will help you in growing towards a #devops approach
My DrupalCon 2014 Amsterdam talk, introducing the audience to #devops and the current state of #devops and Drupal based on the 2014 Drupal and Devops Survey
This presentation provides guidelines for testing effectively, writing good alternative-answer, multiple-choice, short-answer, matching, and long-answer questions, ways to reduce student frustration ...
QA online training offered by Quontra Solutions with special features having Extensive Training will be in both QA Online Training and Placement. We help you in resume preparation and conducting Mock Interviews.
Emphasis is given on important topics that were required and mostly used in real time projects. Quontra Solutions is an Online Training Leader when it comes to high-end effective and efficient IT Training. We have always been and still are focusing on the key aspect which is providing utmost effective and competent training to both students and professionals who are eager to enrich their technical skills.
A Primer into Android - An NSLUG Tech Talkjoelmaxuel
As part of the Linux ecosystem, Android has been getting much fanfare. This tech talk will dive into the basics (and not-so basics with an NSLUG spin) of running, and administering an Android device.
Teaching & Learning English under difficult circumstancesGraham Stanley
Workshop given 16th Sep 17:45 in Buenos Aires:
- Dirección Operativa de Lenguas Extranjeras, Ministerio de Educación, CABA
- British Council
- I.E.S. en Lenguas Vivas “Juan Ramón Fernández”
"Many English teachers find themselves teaching in difficult circumstances. Large classes, multiple levels, and demotivated students are just three realities that can make language learning and teaching a challenge. The idea behind this interactive workshop is to examine these difficult circumstances and others, and to use our shared experience as teachers to help each other with classroom strategies and ideas to overcome the challenges we face on a daily basis.."
http://t.co/hfQ9U98Hzr
Continuous Delivery of Puppet ManifestsKris Buytaert
This document discusses lessons learned from implementing continuous delivery of Puppet code. It describes starting with manual hacking directly on production servers, then using basic version control with Git. Improved approaches involved running Git on Puppet masters with automated pulls, using modules, and package management. The optimal solution uses a Jenkins pipeline for continuous integration testing and deployment, including syntax, style, testing, packaging, repository uploads, and deploying to test environments. Metrics are sent after deployment to close the feedback loop for continuous improvement.
This presentation provides guidelines for testing effectively, writing good alternative-answer, multiple-choice, short-answer, matching, and long-answer questions, ways to reduce student frustration ...
QA online training offered by Quontra Solutions with special features having Extensive Training will be in both QA Online Training and Placement. We help you in resume preparation and conducting Mock Interviews.
Emphasis is given on important topics that were required and mostly used in real time projects. Quontra Solutions is an Online Training Leader when it comes to high-end effective and efficient IT Training. We have always been and still are focusing on the key aspect which is providing utmost effective and competent training to both students and professionals who are eager to enrich their technical skills.
A Primer into Android - An NSLUG Tech Talkjoelmaxuel
As part of the Linux ecosystem, Android has been getting much fanfare. This tech talk will dive into the basics (and not-so basics with an NSLUG spin) of running, and administering an Android device.
Teaching & Learning English under difficult circumstancesGraham Stanley
Workshop given 16th Sep 17:45 in Buenos Aires:
- Dirección Operativa de Lenguas Extranjeras, Ministerio de Educación, CABA
- British Council
- I.E.S. en Lenguas Vivas “Juan Ramón Fernández”
"Many English teachers find themselves teaching in difficult circumstances. Large classes, multiple levels, and demotivated students are just three realities that can make language learning and teaching a challenge. The idea behind this interactive workshop is to examine these difficult circumstances and others, and to use our shared experience as teachers to help each other with classroom strategies and ideas to overcome the challenges we face on a daily basis.."
http://t.co/hfQ9U98Hzr
Continuous Delivery of Puppet ManifestsKris Buytaert
This document discusses lessons learned from implementing continuous delivery of Puppet code. It describes starting with manual hacking directly on production servers, then using basic version control with Git. Improved approaches involved running Git on Puppet masters with automated pulls, using modules, and package management. The optimal solution uses a Jenkins pipeline for continuous integration testing and deployment, including syntax, style, testing, packaging, repository uploads, and deploying to test environments. Metrics are sent after deployment to close the feedback loop for continuous improvement.
Looking back at 6.5 years of #devopsdaysKris Buytaert
Kris Buytaert reflected on 6.5 years of organizing DevOpsDays conferences. The first conferences in 2009 had no manifesto and focused on culture change. Over 100 events have since been held worldwide, with nearly 300 organizers. While vendors initially struggled to see value, sub-communities around monitoring and configuration management emerged. Enterprise adoption of DevOps principles has grown beyond startups. The future includes more collaboration and a return to emphasizing empathy and common sense.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
The document discusses how system administration has changed over time and will continue to change in the future. Some of the key points made include:
- Infrastructure used to be deployed manually but now utilizes infrastructure as code approaches like Chef, Puppet, and Ansible for automated deployments.
- Virtualization has largely replaced physical servers and made infrastructure more flexible and cost-effective.
- Continuous delivery practices from software development are being applied to infrastructure to allow for reliable, tested changes.
- Monitoring has improved from early tools to current approaches that leverage metrics, machine learning, and aim to provide actionable information.
- Emerging technologies like containers, orchestration, and software-defined infrastructure will further transform system
Kris Buytaert reflects on 7 years of organizing DevOpsDays conferences. He started as a developer and became an operations person. DevOpsDays began in 2009 with conferences in Gent and Hamburg that had no manifesto. The conference format then spread to over a dozen cities worldwide. Definitions of devops evolved to focus on culture and job performance. Critics argued devops only works for startups, but the roots are in enterprise systems not startups. Vendors struggled to sell "devops" as it is hard to sell culture and change. Related submovements in devops emerged like DOD, Monitorama, and CfgMgmtCamp. The future includes over 130 events in many cities and starting your
This document provides an overview of DevOps. It begins with definitions of DevOps, noting that it is a cultural and professional movement, not a new role or team. It discusses how DevOps aims to break down barriers between development and operations teams to improve collaboration. The document outlines some common DevOps practices like automating infrastructure, implementing continuous delivery, measuring metrics, and encouraging sharing of knowledge. It provides examples of how organizations have benefited from DevOps approaches like faster delivery and more stable systems. Overall, the summary emphasizes that DevOps is focused on changing culture and ways of working, not just tools or processes.
The document summarizes the changes that have occurred in system administration over time. It discusses how software delivery has shifted from CDs/DVDs to online and continuous delivery. Infrastructure deployment has evolved from manual installations to tools enabling reproducible deployments. Virtualization became common in the 2000s. Infrastructure as code principles including treating infrastructure configuration as code, versioning, and testing best practices are discussed. Monitoring has shifted from tools like BigBrother to Nagios and newer solutions. Emerging technologies like Docker, Packer, orchestration tools, and metrics/monitoring are also summarized.
From Config Management Sucks to #cfgmgmtlove Kris Buytaert
This document summarizes Kris Buytaert's talk on the evolution of config management from the 1990s to present day. It discusses early approaches like manual installations and system imaging tools. It then covers the rise of infrastructure as code using tools like Puppet, Chef, and Docker. The talk addresses challenges like getting operations teams to adopt new methods and complexities that can arise from dependencies and modules. It promotes treating infrastructure like code with development practices for versioning, testing, and continuous integration/deployment.
Kris Buytaert discusses the evolution of monitoring tools from #MonitoringSucks to #MonitoringLove. He describes how early monitoring tools like Nagios and Zenoss were difficult to configure and maintain. Newer tools like Icinga, Sensu, Graphite, Grafana, and Riemann provide modular components that are easier to automate and integrate. Logs can now be monitored alongside metrics using tools like Graylog and ELK. Packetbeat allows monitoring application performance. The monitoring landscape continues improving with better automation, integration, and reduced alert fatigue.
Closing the gap between Distros(devs) and their Users(ops)Kris Buytaert
Kris Buytaert discusses the gap between software developers (devs) and operations teams (ops) when using Linux distributions. There is often a lack of communication and different priorities, with devs focused on getting the latest code quickly and ops concerned with stability, security and deployability at scale. Buytaert provides examples of issues, such as packages containing PHP code directly in /etc, and distributions packaging outdated or broken upstream software. He advocates for better collaboration between distributions, upstream projects and power users through activities like meetups, user advisory boards, and tools to more easily build and test packages. The goal is to improve culture, automation, measurement and sharing between all parties.
This document discusses the concepts of DevOps, SecOps, and DevSecOps. It describes how the traditional divisions between development, operations, and security can lead to problems, and how adopting a DevOps culture and practices like continuous integration, infrastructure as code, and automation can help break down silos. It emphasizes that DevSecOps is about collaboration, culture change, and bringing security practices into the development lifecycle from the beginning.
This document discusses using the ELK stack (Elasticsearch, Logstash, Kibana) for log collection, aggregation, and visualization. It describes how to use Logstash to collect logs from various sources, apply filters like Grok to parse logs into structured data, and output to Elasticsearch for analysis and long-term storage. Metrics can also be sent to Graphite for long-term storage and visualization. The ELK stack provides a way for both developers and operations teams to analyze logs.
Adopting Devops , Stories from the trenchesKris Buytaert
As presented at Baltic Devops in Talllinn ,
Starting with devops is either the most trivial, or the hardest thing to do.
This talk will teach you a number of tricks on how to make life easier for your team. How to work together with your management and how to convince them devops is a relevant thing
From MonitoringSucks to Monitoring Love , 2016 EditionKris Buytaert
The document discusses open source monitoring tools and trends from 2008 to 2016. It begins by providing background on the speaker and their experience transitioning from a developer to operations role. It then outlines reasons why traditional monitoring was disliked (#monitoringsucks), before the rise of tools enabling more automated, metrics-based monitoring brought renewed interest (#monitoringlove). The rest of the document summarizes popular open source monitoring tools for collecting, storing, analyzing, and visualizing metrics and logs at different stages of the monitoring pipeline. It concludes by noting an improved ability to reduce false alarms compared to earlier approaches.
Skill development for assessing cognitive impairment in elderly 24 nov15Dr. Rakesh Tripathi
Skills required for cognitive assessment of an elderly is highlighted with some cognitive screening and detailed assessment tool. It may be useful for Psychologist, clinical Psychologist, psychiatrist and for trained professional in the field.
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 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.
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.