The Art and Zen of Managing Nagios With PuppetMike Merideth
The document discusses using Puppet to manage Nagios configurations. It describes key Puppet features like exported resources, Hiera for separating code and data, and templates. It also discusses building Nagios configs using these features, provisioning new hosts, removing decommissioned hosts, and monitoring Puppet processes. The presenter then demonstrates these techniques in a Vagrant environment on GitHub.
Puppet Camp Portland: Nagios Management With Puppet (Beginner)Puppet
This document discusses managing Nagios monitoring with Puppet. It describes key Puppet features like exported resources, Hiera, templates and Facter that help avoid monitoring gaps, keep configs consistent, and learn Puppet. It provides examples of using these features to define Nagios hosts, services and configs dynamically based on variables. While existing Nagios modules exist, the author wanted one that automatically adds/removes hosts and uses host/service groups. The full implementation combines Hiera, templates, facts and exported resources to dynamically build configs.
Puppet Camp Denver 2015: Nagios Management With PuppetPuppet
This document discusses managing Nagios monitoring with Puppet. It explains why Puppet is useful for Nagios configuration, highlighting key Puppet features like exported resources, Hiera, templates and Facter. It provides examples of using these features with Nagios and discusses integrating different configuration sources. Overall, the document shows how Puppet can be used to automate and simplify Nagios monitoring in a consistent, reusable way.
This document discusses using Puppet to automate the configuration of Icinga, a fork of Nagios, for monitoring nodes. Key points include:
- Using Puppet's standard file and template types to configure Icinga servers and store configs in a database for sharing across nodes.
- Configuring hosts, services, commands, dependencies, and NRPE checks as Puppet resources for automatic configuration.
- Tips like using hostgroups, tags, targets, and an ENC to dynamically configure and export monitorable resources from Puppet to Icinga.
Continuous Deployment into the Unknown with Artifactory, Bintray, Docker and ...Gilad Garon
VMware’s Common SaaS Platform (CSP) is a brand new offering designed to enhance the productivity of developers and cloud providers by equipping them with a set of common and configurable capabilities (such as Identity, Telemetry, Account Management, Billing etc.), thus enabling them to focus on their core businesses.
But enough with the product pitch.
CSP is distributed to numerous cloud providers around the globe, used by developers and IT alike to empower their services and better answer the business need of their customers.
Please join us and witness how we take continuous delivery to the next step where sometimes the target environment is not on our control and still seamlessly manage and deliver our unique collection of capabilities, packaged as platform for ease of use, using the best and shiniest tools the frogs can provide.
The document discusses using the Grunt task runner to manage build and testing tools for Drupal projects. It introduces Grunt and explains how it can be used to build a Drupal site from a codebase, validate code quality, and test functionality with Behat. The presentation demonstrates setting up a sample project with Grunt Drupal Tasks and running commands to build, validate, and test the project. It encourages adopting these practices for consistent workflows and encourages contributing to the Grunt Drupal Tasks project.
PuppetConf 2016: Why Network Automation Matters, and What You Can Do About It...Puppet
Here are the slides from Rick Sherman's PuppetConf 2016 presentation called Why Network Automation Matters, and What You Can Do About It. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa
PyWPS is an open source Python implementation of the OGC Web Processing Service standard. It allows users to publish and discover geospatial processes that can be invoked remotely through a RESTful API. Some key points about PyWPS include that it supports all geospatial tools available in Python, uses standards like WFS and WCS, and allows processes to be run asynchronously and in isolated containers. The current version, PyWPS 4.0.0, features improvements like enhanced data validation, multiprocessing support, and an updated codebase to work with newer Python and geospatial technologies.
The Art and Zen of Managing Nagios With PuppetMike Merideth
The document discusses using Puppet to manage Nagios configurations. It describes key Puppet features like exported resources, Hiera for separating code and data, and templates. It also discusses building Nagios configs using these features, provisioning new hosts, removing decommissioned hosts, and monitoring Puppet processes. The presenter then demonstrates these techniques in a Vagrant environment on GitHub.
Puppet Camp Portland: Nagios Management With Puppet (Beginner)Puppet
This document discusses managing Nagios monitoring with Puppet. It describes key Puppet features like exported resources, Hiera, templates and Facter that help avoid monitoring gaps, keep configs consistent, and learn Puppet. It provides examples of using these features to define Nagios hosts, services and configs dynamically based on variables. While existing Nagios modules exist, the author wanted one that automatically adds/removes hosts and uses host/service groups. The full implementation combines Hiera, templates, facts and exported resources to dynamically build configs.
Puppet Camp Denver 2015: Nagios Management With PuppetPuppet
This document discusses managing Nagios monitoring with Puppet. It explains why Puppet is useful for Nagios configuration, highlighting key Puppet features like exported resources, Hiera, templates and Facter. It provides examples of using these features with Nagios and discusses integrating different configuration sources. Overall, the document shows how Puppet can be used to automate and simplify Nagios monitoring in a consistent, reusable way.
This document discusses using Puppet to automate the configuration of Icinga, a fork of Nagios, for monitoring nodes. Key points include:
- Using Puppet's standard file and template types to configure Icinga servers and store configs in a database for sharing across nodes.
- Configuring hosts, services, commands, dependencies, and NRPE checks as Puppet resources for automatic configuration.
- Tips like using hostgroups, tags, targets, and an ENC to dynamically configure and export monitorable resources from Puppet to Icinga.
Continuous Deployment into the Unknown with Artifactory, Bintray, Docker and ...Gilad Garon
VMware’s Common SaaS Platform (CSP) is a brand new offering designed to enhance the productivity of developers and cloud providers by equipping them with a set of common and configurable capabilities (such as Identity, Telemetry, Account Management, Billing etc.), thus enabling them to focus on their core businesses.
But enough with the product pitch.
CSP is distributed to numerous cloud providers around the globe, used by developers and IT alike to empower their services and better answer the business need of their customers.
Please join us and witness how we take continuous delivery to the next step where sometimes the target environment is not on our control and still seamlessly manage and deliver our unique collection of capabilities, packaged as platform for ease of use, using the best and shiniest tools the frogs can provide.
The document discusses using the Grunt task runner to manage build and testing tools for Drupal projects. It introduces Grunt and explains how it can be used to build a Drupal site from a codebase, validate code quality, and test functionality with Behat. The presentation demonstrates setting up a sample project with Grunt Drupal Tasks and running commands to build, validate, and test the project. It encourages adopting these practices for consistent workflows and encourages contributing to the Grunt Drupal Tasks project.
PuppetConf 2016: Why Network Automation Matters, and What You Can Do About It...Puppet
Here are the slides from Rick Sherman's PuppetConf 2016 presentation called Why Network Automation Matters, and What You Can Do About It. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa
PyWPS is an open source Python implementation of the OGC Web Processing Service standard. It allows users to publish and discover geospatial processes that can be invoked remotely through a RESTful API. Some key points about PyWPS include that it supports all geospatial tools available in Python, uses standards like WFS and WCS, and allows processes to be run asynchronously and in isolated containers. The current version, PyWPS 4.0.0, features improvements like enhanced data validation, multiprocessing support, and an updated codebase to work with newer Python and geospatial technologies.
JavaEdge 2008: Your next version control systemGilad Garon
The next generation of VCS has a clear target ahead of them: making branching and merging easier. Until recently, Subversion was dominating the world of Version Control Systems, but now, Distributed Version Control Systems are growing in popularity and everywhere you go you hear about Git or Mercurial, and how they make branching and merging a breeze. But the Subversion team isn't going down quietly, they have a new weapon: the 1.5 version. Learn about the next generation of Version Control Systems is planning to solve your problems.
Best Practices? That’s like asking how long is a piece of string! While every environment is different, there are however a number of configurations, tweaks and methods that can be of great benefit for your Nagios XI environment. This talk will cover a variety of Best Practice topics for Nagios XI ranging from flexible object configurations through to back end performance enhancements.
Get There meetup March 2018 - Microservices in action at the Dutch National P...Bert Jan Schrijver
The document discusses the Dutch National Police's adoption of a microservices architecture and DevOps practices. It describes their private cloud platform, use of 5 cross-functional teams to build applications, and event-driven microservices with technologies like Spring Boot and Kafka. It also covers their continuous delivery pipelines, automated deployments to OpenStack, and challenges of maintaining over 50 independent services.
Dublin JUG February 2018 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
The document discusses the Dutch National Police's adoption of a microservices architecture and DevOps practices. It describes their private cloud platform, use of 5 cross-functional teams to build applications, and event-driven microservices with technologies like Spring Boot and Kafka. It also covers their continuous delivery pipelines, automated deployments to OpenStack, and challenges of maintaining over 50 independent services.
Devoxx PL 2018 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
The document summarizes the Dutch National Police's transition to a microservices architecture. It discusses how they reorganized existing systems into independently deployable microservices running on a private cloud platform. It also covers their development methodology, including feature teams, continuous delivery, and emphasis on automation and monitoring in production. Overall challenges discussed include balancing autonomy and sharing, managing dependencies, and ensuring modularity across frontend and backend systems.
- The company uses microservices architecture with 50+ services running across 300+ containers orchestrated by Kubernetes. They have fully automated continuous integration and deployment.
- CoreOS is used as the lightweight OS which updates automatically and stores services in read-only containers. Kubernetes provides service discovery, auto-scaling, deployment, rollback and resource management for containers.
- The software development process follows a continuous delivery model where code changes are deployed through a pipeline to ensure the software can be reliably released at any time.
iSense Java Summit 2017 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
3 DevOps teams at the Dutch National Police are building big data applications in a private cloud using microservices architecture. They develop independently using short iterations and continuous delivery. Key aspects of their approach include developing in separate teams with their own backlogs, embracing change, and having minimal dependencies outside each team. They aim to have zero downtime deployments and are exploring ways to further split their frontend and adopt cross-functional product teams.
There is no doubt that security has been in the spotlight over the last few years, recent events have been responsible for the increased demand for better and more secure systems. Security was often treated as an afterthought or something that could be implemented ‘later’. In this session, we will go over some best practices, using existing tools and frameworks to help you set up a more secure environment and to get a grasp of what is happening in your environment. We will leverage your existing automation skills to secure and automate these workflows. Expect a session with a lot of demos and resources that can directly be implemented. What to do in order to access systems that would otherwise be inaccessible, we will go in depth on how to resolve this using PowerShell and additional methods.
Vert.x is a toolkit for building reactive applications on the JVM. It was awarded for 'Most Innovative Java Technology' at the JAX Innovation awards. Vert.x is event driven, non blocking and polyglot, which makes it an excellent platform for building microservices. In this talk, I’ll share experiences and real-world use cases from a Dutch company that started building reactive web applications with Vert.x about 4 years ago. You’ll learn the concepts behind Vert.x, why we chose Vert.x, how we’re using it and the challenges we faced. Topics include the anatomy of our projects, (micro)services architecture, deployment model and DevOps, scalability, the upgrade from Vert.x 2 to Vert.x 3 and cooperation with the team behind Vert.x. At the end of this session, you’ll know enough about Vert.x to get started yourself right away!
GeekOut 2017 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
Microservices? At the Police? Definitely!
At the Cloud, Big Data and Internet division of the Dutch National Police, 3 DevOps teams use the latest open source technology to build high tech, cloud native web applications in a private cloud. These applications are used to support various types of police work with data from open, online sources and are built using Spring Boot, Angular 4, Spark, Kafka and Jenkins 2.
In this session, I'll share our experiences and real-world use cases for microservices. I’ll explain our architecture, why we chose it, which challenges we face and what this all brings us. I’ll show how 3 teams work together on one product, loosely based on the models used by Spotify and Netflix, and I’ll talk about how we apply the principles of DevOps and Continuous Delivery. I’ll show how we handle security, build pipelines, test automation, performance tests, automated deployments and monitoring.
You’ll leave this session with an understanding of how this approach enables us to have the agility of a startup within the large Police organisation.
Network Infrastructure as Code with Chef and CiscoMatt Ray
Chef is an open source framework for managing infrastructure as code. It uses a declarative language and recipes to describe and configure systems to match a desired state. Chef works by having clients pull policies from a server and apply them locally, then reporting the state back. Cisco and Chef are working together to bring official Chef support to Cisco's NX-OS and IOS-XR platforms through Omnibus packages and a Cisco cookbook with resources for managing Cisco devices. This will allow network infrastructures to be managed as code through testing, versioning, and continuous delivery practices.
Git is a distributed revision control system that stores snapshots of files rather than tracking changes. It allows for cheap branching, works offline, and is fast. Common Git actions include checking the status of files, adding changes to the staging area, stashing changes, committing staged changes, and pushing commits to a remote repository. The basic Git workflow involves making changes, staging them, committing, and optionally pushing commits to a remote. Key differences from other version control systems are that everything in Git is local by default, it is very fast, and allows for cheap branching and offline work.
Salt Air 19 - Intro to SaltStack RAET (reliable asyncronous event transport)SaltStack
Thomas Hatch, SaltStack CTO, and Sam Smith, SaltStack director of product development, introduce SaltStack RAET as a new alternative transport medium developed specifically with SaltStack infrastructure automation and configuration management in mind. SaltStack built RAET for customers needing substantial speed and scale to automate management of massive data center infrastructure environments.
SaltStack RAET is primarily an async communication layer over truly async connections, defaulting to UDP. The SaltStack RAET system uses CurveCP encryption by default. SaltStack users can now leverage substantial flexibility via either Salt SSH, ØMQ, or RAET to best address numerous use cases.
OSDC 2013 | The OpenNebula Cloud Platform for Datacenter Virtualization by Co...NETWAYS
The presentation will describe the OpenNebula project for data center virtualization, with a focus on how to deploy OpenNebula-based private clouds and its unique features to tune and adapt it to any technology in the cloud and virtualization ecosystem.
The target audience are developers and IT administrators interested in deploying a private cloud solution, or in the integration of OpenNebula with other projects. The talk will be useful for both people with experience or without prior knowledge of OpenNebula, as it will start by introducing the project and its main features, along with a quick demonstration. Although this is not a hands-on tutorial, by the end of the presentation attendees will have a comprehensive idea of the integration and customization capabilities of OpenNebula in different areas, like user authentication, virtualization, storage, networking, etc.
Nagios Conference 2014 - Sam Lansing - Advanced Features of Nagios XINagios
Sam Lansing's presentation on Monitoring Financial Protocols With Nagios.
The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference
Nagios Conference 2014 - Mike Merideth - The Art and Zen of Managing Nagios w...Nagios
Mike Merideth's presentation on The Art and Zen of Managing Nagios with Puppet.
The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference
This document discusses the key initiatives, components, and features of Drupal 8. It focuses on the major architectural changes including adopting semantic versioning, including configuration management and Twig templates in the core, and using Composer for dependency management. It also outlines the major Symfony components integrated into Drupal 8 to improve the request-response lifecycle and several non-Symfony libraries added to core like Doctrine, Guzzle, and EasyRDF.
JavaEdge 2008: Your next version control systemGilad Garon
The next generation of VCS has a clear target ahead of them: making branching and merging easier. Until recently, Subversion was dominating the world of Version Control Systems, but now, Distributed Version Control Systems are growing in popularity and everywhere you go you hear about Git or Mercurial, and how they make branching and merging a breeze. But the Subversion team isn't going down quietly, they have a new weapon: the 1.5 version. Learn about the next generation of Version Control Systems is planning to solve your problems.
Best Practices? That’s like asking how long is a piece of string! While every environment is different, there are however a number of configurations, tweaks and methods that can be of great benefit for your Nagios XI environment. This talk will cover a variety of Best Practice topics for Nagios XI ranging from flexible object configurations through to back end performance enhancements.
Get There meetup March 2018 - Microservices in action at the Dutch National P...Bert Jan Schrijver
The document discusses the Dutch National Police's adoption of a microservices architecture and DevOps practices. It describes their private cloud platform, use of 5 cross-functional teams to build applications, and event-driven microservices with technologies like Spring Boot and Kafka. It also covers their continuous delivery pipelines, automated deployments to OpenStack, and challenges of maintaining over 50 independent services.
Dublin JUG February 2018 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
The document discusses the Dutch National Police's adoption of a microservices architecture and DevOps practices. It describes their private cloud platform, use of 5 cross-functional teams to build applications, and event-driven microservices with technologies like Spring Boot and Kafka. It also covers their continuous delivery pipelines, automated deployments to OpenStack, and challenges of maintaining over 50 independent services.
Devoxx PL 2018 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
The document summarizes the Dutch National Police's transition to a microservices architecture. It discusses how they reorganized existing systems into independently deployable microservices running on a private cloud platform. It also covers their development methodology, including feature teams, continuous delivery, and emphasis on automation and monitoring in production. Overall challenges discussed include balancing autonomy and sharing, managing dependencies, and ensuring modularity across frontend and backend systems.
- The company uses microservices architecture with 50+ services running across 300+ containers orchestrated by Kubernetes. They have fully automated continuous integration and deployment.
- CoreOS is used as the lightweight OS which updates automatically and stores services in read-only containers. Kubernetes provides service discovery, auto-scaling, deployment, rollback and resource management for containers.
- The software development process follows a continuous delivery model where code changes are deployed through a pipeline to ensure the software can be reliably released at any time.
iSense Java Summit 2017 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
3 DevOps teams at the Dutch National Police are building big data applications in a private cloud using microservices architecture. They develop independently using short iterations and continuous delivery. Key aspects of their approach include developing in separate teams with their own backlogs, embracing change, and having minimal dependencies outside each team. They aim to have zero downtime deployments and are exploring ways to further split their frontend and adopt cross-functional product teams.
There is no doubt that security has been in the spotlight over the last few years, recent events have been responsible for the increased demand for better and more secure systems. Security was often treated as an afterthought or something that could be implemented ‘later’. In this session, we will go over some best practices, using existing tools and frameworks to help you set up a more secure environment and to get a grasp of what is happening in your environment. We will leverage your existing automation skills to secure and automate these workflows. Expect a session with a lot of demos and resources that can directly be implemented. What to do in order to access systems that would otherwise be inaccessible, we will go in depth on how to resolve this using PowerShell and additional methods.
Vert.x is a toolkit for building reactive applications on the JVM. It was awarded for 'Most Innovative Java Technology' at the JAX Innovation awards. Vert.x is event driven, non blocking and polyglot, which makes it an excellent platform for building microservices. In this talk, I’ll share experiences and real-world use cases from a Dutch company that started building reactive web applications with Vert.x about 4 years ago. You’ll learn the concepts behind Vert.x, why we chose Vert.x, how we’re using it and the challenges we faced. Topics include the anatomy of our projects, (micro)services architecture, deployment model and DevOps, scalability, the upgrade from Vert.x 2 to Vert.x 3 and cooperation with the team behind Vert.x. At the end of this session, you’ll know enough about Vert.x to get started yourself right away!
GeekOut 2017 - Microservices in action at the Dutch National PoliceBert Jan Schrijver
Microservices? At the Police? Definitely!
At the Cloud, Big Data and Internet division of the Dutch National Police, 3 DevOps teams use the latest open source technology to build high tech, cloud native web applications in a private cloud. These applications are used to support various types of police work with data from open, online sources and are built using Spring Boot, Angular 4, Spark, Kafka and Jenkins 2.
In this session, I'll share our experiences and real-world use cases for microservices. I’ll explain our architecture, why we chose it, which challenges we face and what this all brings us. I’ll show how 3 teams work together on one product, loosely based on the models used by Spotify and Netflix, and I’ll talk about how we apply the principles of DevOps and Continuous Delivery. I’ll show how we handle security, build pipelines, test automation, performance tests, automated deployments and monitoring.
You’ll leave this session with an understanding of how this approach enables us to have the agility of a startup within the large Police organisation.
Network Infrastructure as Code with Chef and CiscoMatt Ray
Chef is an open source framework for managing infrastructure as code. It uses a declarative language and recipes to describe and configure systems to match a desired state. Chef works by having clients pull policies from a server and apply them locally, then reporting the state back. Cisco and Chef are working together to bring official Chef support to Cisco's NX-OS and IOS-XR platforms through Omnibus packages and a Cisco cookbook with resources for managing Cisco devices. This will allow network infrastructures to be managed as code through testing, versioning, and continuous delivery practices.
Git is a distributed revision control system that stores snapshots of files rather than tracking changes. It allows for cheap branching, works offline, and is fast. Common Git actions include checking the status of files, adding changes to the staging area, stashing changes, committing staged changes, and pushing commits to a remote repository. The basic Git workflow involves making changes, staging them, committing, and optionally pushing commits to a remote. Key differences from other version control systems are that everything in Git is local by default, it is very fast, and allows for cheap branching and offline work.
Salt Air 19 - Intro to SaltStack RAET (reliable asyncronous event transport)SaltStack
Thomas Hatch, SaltStack CTO, and Sam Smith, SaltStack director of product development, introduce SaltStack RAET as a new alternative transport medium developed specifically with SaltStack infrastructure automation and configuration management in mind. SaltStack built RAET for customers needing substantial speed and scale to automate management of massive data center infrastructure environments.
SaltStack RAET is primarily an async communication layer over truly async connections, defaulting to UDP. The SaltStack RAET system uses CurveCP encryption by default. SaltStack users can now leverage substantial flexibility via either Salt SSH, ØMQ, or RAET to best address numerous use cases.
OSDC 2013 | The OpenNebula Cloud Platform for Datacenter Virtualization by Co...NETWAYS
The presentation will describe the OpenNebula project for data center virtualization, with a focus on how to deploy OpenNebula-based private clouds and its unique features to tune and adapt it to any technology in the cloud and virtualization ecosystem.
The target audience are developers and IT administrators interested in deploying a private cloud solution, or in the integration of OpenNebula with other projects. The talk will be useful for both people with experience or without prior knowledge of OpenNebula, as it will start by introducing the project and its main features, along with a quick demonstration. Although this is not a hands-on tutorial, by the end of the presentation attendees will have a comprehensive idea of the integration and customization capabilities of OpenNebula in different areas, like user authentication, virtualization, storage, networking, etc.
Nagios Conference 2014 - Sam Lansing - Advanced Features of Nagios XINagios
Sam Lansing's presentation on Monitoring Financial Protocols With Nagios.
The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference
Nagios Conference 2014 - Mike Merideth - The Art and Zen of Managing Nagios w...Nagios
Mike Merideth's presentation on The Art and Zen of Managing Nagios with Puppet.
The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference
This document discusses the key initiatives, components, and features of Drupal 8. It focuses on the major architectural changes including adopting semantic versioning, including configuration management and Twig templates in the core, and using Composer for dependency management. It also outlines the major Symfony components integrated into Drupal 8 to improve the request-response lifecycle and several non-Symfony libraries added to core like Doctrine, Guzzle, and EasyRDF.
This document provides an introduction to using Git and version control. It explains the basic concepts and workflow of Git, including initializing and committing to a local repository, pushing changes to a remote repository, and using branches for features and releases. It also discusses how to manage Drupal configuration changes using features in Git.
This document discusses version control and a trunk-based approach using Visual Studio Team Services (VSTS). It begins with an overview of VSTS and its key functional areas. The document then covers topics like version control, Git, branching, merging, pull requests and code reviews. It proposes exercises for practicing these concepts using both command line Git and the Visual Studio IDE. The trunk-based approach is introduced as an alternative to feature branching where developers collaborate on a single branch.
OSGi is a modular system for Java that addresses issues with complex, monolithic systems by breaking them into interacting modules. Carbon is a middleware platform built using OSGi that consists of modular components providing core services. Each component is an OSGi bundle that can be independently installed, updated, and uninstalled. This allows Carbon to be extended through additional bundles and provides a dynamic and maintainable architecture for middleware.
This document describes eBay's use of Fluo for continuous integration and deployment using OpenStack. Fluo provides a single interface for configuring, building, testing, and deploying code changes. It provisions instances on OpenStack to run tasks defined in a configuration file like running tests, building packages, and deploying code. Fluo replicates code, packages, and configuration management code across regions and datacenters. It supports common workflows from code review through integration testing, releases, and periodic jobs. Fluo aims to provide a fully automated and scalable continuous delivery system to deploy code changes to eBay's global infrastructure on OpenStack.
PuppetConf 2017: Puppet Development Kit: A Seamless Workflow for Module Devel...Puppet
The Puppet Development Kit (PDK) provides tools to help developers easily create high-quality Puppet modules. It includes tools for testing, linting, and validating modules. Using the PDK improves the module development experience and helps ensure modules are configured correctly and ready to use. The PDK is designed for both new and experienced Puppet users and makes it easier to get started with best practices like testing and code quality checks.
This document summarizes an Ansible meetup presentation about what Ansible is, why it is useful, and how it works. Ansible is an open source automation tool that configures systems and deploys applications using human-readable YAML files called playbooks. It is agentless, using SSH to connect to servers. Playbooks define tasks to run on hosts in parallel using modules. Roles help organize tasks by server function. The presentation showed how Ansible simplified deployments by pulling code, installing dependencies, and restarting services across environments in an automated, consistent way.
Building a Modular Server Platform with OSGi - Harshana Eranga Martin, Dileep...mfrancis
OSGi is a modular system for Java that defines modules called bundles. Carbon is an open-source middleware platform based on OSGi that breaks complex systems into interacting bundles. Each SOA component in Carbon is represented by an OSGi bundle to provide modularity, dynamic loading, and loose coupling. Carbon uses OSGi services and features to compose middleware functionality from components and manage their lifecycles. This allows Carbon to be a flexible and extensible platform for building and running modular SOA applications.
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.
This document discusses tools and techniques for improving a developer's daily workflow, including using Vagrant for consistent development environments, Git for version control and collaboration, and design patterns for better code structure. It recommends Vagrant for matching local and production environments, Git and GitHub/Bitbucket for code changes, and following best practices like deleting code and embracing coding standards.
CT Software Developers Meetup: Using Docker and Vagrant Within A GitHub Pull ...E. Camden Fisher
This was a talk given at the second CT Software Developers Meetup (http://www.meetup.com/CT-Software-Developers-Meetup/). It covers how NorthPage is using Docker and Vagrant with a home grown Preview tool to increase the efficiency of the GitHub Pull Request Workflow.
В продолжение темы непрерывной интеграции, Макс расскажет о своем подходе организации непрерывной интеграции и деплоймента в Symfony проектах. Рассказ включает следующие темы:
- Управления зависимостями
- Процесс и инструменты для сборки
- Сервера непрерывной интеграции и в частности Jenkins, плагины к нему, jobs
- Процесс разработки в git
- Процесс выгрузки релиза
- Миграция БД
- Откат релиза
Symfony under control. Continuous Integration and Automated Deployments in Sy...Max Romanovsky
This document discusses continuous integration and automated deployments for Symfony projects. It covers setting up dependencies with Composer, building projects with Phing, implementing continuous integration with Jenkins CI, and deploying projects using Capifony. While many aspects are covered in detail, such as build targets, plugins, and rollback procedures, it notes that the full implementation is not yet available online and will be released to GitHub in 1-2 months.
In this talk, I will discuss our experiences at Mollie with setting up the Jenkins Continuous Integration server for all our PHP projects. The talk will be aimed at developers with little or no experience with CI.
BYOP: Custom Processor Development with Apache NiFiDataWorks Summit
Apache NiFi, a robust, scalable, and secure tool for data flow management, ships with over 212 processors to ingest, route, manipulate, and exfil data from a variety of sources and consumers. But many users turn to NiFi to meet unusual requirements — from proprietary protocol parsing, to running inside connected cars, to offloading massive hardware metrics from oil rigs in the most remote environments. Rather than posting a community request for custom development or offloading unusual demands to unnecessary external systems, there’s an answer in NiFi. Learn how NiFi allows you to quickly prototype custom processors in the scripting language of your choice against live production data without affecting your existing flows. Easily translate prototypes to full-fledged processors to optimize performance and leverage the full provenance reporting infrastructure. Discover how the framework provides conventions to streamline your development and minimize common boilerplate code, and the robust testing framework to make testing easy, and dare we say, fun.
Expected prior knowledge / intended audience: developers and data flow managers should have passing knowledge of Apache NiFi as a platform for routing, transforming, and delivering data through systems (a brief overview will be provided). The intended audience will have experience with programming in Groovy, Ruby, Jython, ECMAScript/Javascript, or Lua.
Takeaways: Attendees will gain an understanding in writing custom processors for Apache NiFi, including the component lifecycle, unit and integration testing, quick prototyping using a scripting language of their choice, and the artifact publishing and deployment process.
Using NuGet the way you should
Consuming NuGet packages, that’s what everyone does. Open source projects create NuGet packages and post them on NuGet.org. Meanwhile, all of us are still working with shared projects and fighting relative paths, versioning and so on. In this talk, we’ll use Visual Studio, NuGet and TeamCity to work with NuGet the way you should. Project references must die! Add Package Reference and good continuous integration is everything you will ever need.
August Webinar - Water Cooler Talks: A Look into a Developer's WorkbenchHoward Greenberg
The webinar covered tools and techniques used by several developers in their work with Domino and XPages. Howard Greenberg discussed using SourceTree and BitBucket for version control of XPages applications. Jesse Gallagher presented his toolchain including Eclipse, Maven, and Jenkins for plugin and application development. Serdar Basegmez outlined his development environment including configuring Eclipse to develop OSGi plugins for the Domino runtime. All emphasized the importance of source control, testing, and documentation in their processes.
This document outlines workflows and tools for managing Magento 2 development. It discusses challenges with scalable and complicated processes and assumptions of skill. Lessons learned include keeping developer freedom and code integrity while maintaining accountability. Recommended tools include Vagrant for simplified developer setups, PHPStorm for code completion and testing, Git for version control, and Composer for dependencies. The workflow uses separate modules in a Git repository structure with branches for different environments and deployment automation.
Similar to The Art & Zen of Managing Nagios with Puppet (20)
Failure as Success Devops Roadtrip Seattle 2016VictorOps
'Failure' as 'Success': The Mindset, Methods, and Landmines
J. Paul Reed
Release Engineering Approaches
Simply ship. Every time.
http://release-approaches.com/
DevOps involves development and operations engineers working together throughout the entire lifecycle of a service, from design to production support. This breaks down the traditional silos between development and operations teams. The document discusses DevOps practices like continuous integration, infrastructure as code, monitoring and metrics, and implementing processes to minimize the impact of disruptions and outages. It emphasizes adopting DevOps culture from the start and evolving practices over time in a way that makes sense for the business.
This document discusses lessons learned around crisis communication at VictorOps. It provides tips for establishing a cross-functional crisis communication process that includes agreeing on when and how often to communicate, what gets communicated, who manages the message, and where the message is shared. The goal is to control the messaging and build trust with users during times of crisis. An effective crisis communication process can help manage reputational impact and make communicating less burdensome when incidents occur.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
The document discusses the results of a study on the effects of exercise on memory and thinking abilities in older adults. The study found that regular exercise can help reduce the decline in thinking abilities that often occurs with age. Older adults who exercised regularly performed better on cognitive tests and brain scans showed they had greater activity in important areas for memory and learning compared to less active peers.
Dealing with an outage is so much more than just getting notified that a server is down. From alerting to resolution, learn more about the incident lifecycle and how each phase contributes to MTTR.
Jason Hand, DevOps Evangelist at VictorOps, and Michael Ansel, from Box, explain what ChatOps is, how it can help different teams in your organization, and where security comes into play. You'll learn tips to get started, tools needed and emerging best practices around the topic.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-call Report, most teams report that it take 10-30 minutes to resolve an incident on average, 5 people are needed to help with resolution.
But it doesn't have to be that way. Jason Hand presents best practices and tips for surviving every stage of the firefight - from when an alert comes in to pulling reports after its over.
Clusters are getting bigger and bigger and machines are getting more and more powerful and yet we continue to use architectures that worked for websites built during the 90’s internet scale. Microservices vs. Monoliths glosses over a key architectural distinction in the way we build concurrency into our applications. We’ll define terms like concurrency and parallelism and learn how the key question in an architecture is message passing vs. shared mutable state. We’ll also look at concepts like Actors and CSP for creating a holistic messaging passing architecture that will let you truly scale your architecture.
An Introduction to Rearview - Time Series Based MonitoringVictorOps
Jeff Simpson, senior software engineer at VictorOps, delivered this presentation at the Frontrange Alerting & Monitoring meetup...along with an awesome live demo.
Putting Devs On-Call: How to Empower Your TeamVictorOps
A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates.
We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.
Join DevOps Evangelist, Jason Hand, for a discussion on ChatOps and the movement to deploy, measure, and mitigate from a chat client.
With more and more teams implementing methods to trigger commands from within their favorite chat clients, the time it takes to perform specific and repetitive tasks has been dramatically reduced. In providing a real-time command history to others, we can share knowledge and learn from each other faster than ever before.
Everyone knows the importance of post-mortems but something seems to be keeping your team from actually doing them. Whether it’s a question of psychology or sociology, our guide provides six reasons why your post-mortem process might be failing. Read more to see how you can stop making these mistakes!
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
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.
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.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
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
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
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
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.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
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.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
1. The Art and Zen of Managing Nagios with Puppet
Michael Merideth - VictorOps
2. Puppet and Nagios
• Why use config management?
• Using Puppet with Nagios:
• Client-generated config
• Server-generated config
• Data separation
• Provisioning and de-provisioning
• Monitoring Puppet
• Demo Time!
3. Why Config Management?
The age of virtualization
• IT pros, even at startups, are managing hundreds
of nodes per person
• There are simply too many running OSes for most
shops to manage manually
• Config management solves the problems of drift
and inconsistency
• Config management becomes living documentation
4. DevOps and Config Management
DevOps from an IT
perspective:
• Infrastructure as code
• SCM as an IT workflow tool
• Continuous integration
• Unit testing
• Integration testing
• Letting the developers into the
sandbox
6. Key Puppet Features
Exported Resources:
• A resource gets defined on one host, and
implemented on another
• Requires the use of PuppetDB, which means a
Puppet Master
• Saves having to use shared storage or insecure file
transfers
• Keeps the number of config files low
7. Key Puppet Features
Hiera:
• Separate code from data
• Set defaults and provide overrides
• Encrypted back-ends mean security, even if
your source code is stolen
8. Key Puppet Features
Inline Templates:
• Not just for file content
• Allows the use of native Ruby code
within Puppet policy
9. Key Puppet Features
Facter:
• Variable values defined at
run-time, on the client
• Easily extensible
10. Key Puppet Features
Nagios Resource Types:
• Makes creating Nagios configs dead simple
• Enforces correct syntax
• Not suitable for every config in every file
• Warning: these will probably get deprecated and
moved to a PuppetForge module
11. Key Puppet Features
Puppet Forge:
• A public repository of Puppet modules
• Modules can be libraries, defined resource types,
or classes
• OMG CAUTION: 3rd party submissions are not
guaranteed by Puppet Labs
12. Why Not Use an Existing Module?
There are several user-submitted Nagios modules
in the Forge, but I wanted one that would:
• Automatically add new hosts
• Provision some services within other modules
• Automatically remove decommissioned hosts
• Make use of host and service groups
13. Putting It All Together
Hiera defines the variables
• Sane defaults for most values
• Environment-specific overrides (dev, staging,
production)
• Site-specific overrides for different datacenters
14. Putting It All Together
Clients build their own config:
• Each client figures out its own hostgroup
memberships
• Array is built with an inline template
• Other facts integrate into the host definition
• NRPE config built from a common template
15. Putting It All Together
Special service definitions get embedded
with the service module
• A change to a service means a change to how
you monitor it
• Manage that all in one place
16. Putting It All Together
Common service definitions are templatized
• Not everything needs to get built dynamically
• Some services are monitored on all hosts
• Less dynamic config means shorter catalog
compilation
• Templates can be easier to debug
17. Ugly Hack Alert
Dynamic files get built every
run, installed if there’s a diff
• Allows keeping backup directories
with previous versions of the configs
• Allows automatic removal of
decommissioned hosts
• Prevents excessive Nagios restarts
18. Sidebar: Monitoring Puppet
On the Puppet master:
• Apache and passenger processes
• PuppetDB processes
• Optionally puppet-dashboard or Foreman
processes
On the client:
• Watch file age on last_run_summary.yaml
19. The Demo Environment
Vagrant
• AWESOME way to test
Puppet code as you develop
Github repository
• Contains Vagrantfile and
complete Puppet policy
• github.com/victorops/puppet-nagios
21. The Demo Environment
github.com/victorops/puppet-nagios
• Check it out!
• Contribute!
• Or fork it! I don’t mind!
• Help work towards a Puppet Forge module:
• Cleaner Foreman provisioning
• More types of config resources
• Cross platform support
• Documentation