Puppet Camp Atlanta 2014: r10k Puppet WorkflowPuppet
The document discusses r10k, a Puppet workflow tool that helps manage Puppet code, modules, and data across different environments using Git and the Puppetfile. It recommends configuring r10k to store each environment as a Git branch, with a Puppetfile to define Forge modules and custom code and data in separate directories. r10k can then sync code and deploy changes to environments on the Puppet master automatically based on the Git configuration. This simplifies promotion of code, modules, and data through development, test, and production environments.
The document discusses the R10k tool and Puppet workflows. It describes how R10k is used to manage Puppet code modules from Git repositories. It shows the Puppet file and environments like production, testing, development. It demonstrates pushing new features to Git, and testing them on agents using the new_feature environment before deploying to production.
The document discusses continuously testing infrastructure by testing images, containers, and infrastructure as a service using tools like Packer, Serverspec, and Expect. It advocates applying test-driven development principles to infrastructure provisioning and management. Specifically, it suggests writing tests against an infrastructure API to define policies and desired functionality before provisioning resources. The document also describes testing based on data from PuppetDB to automatically generate and run configuration checks.
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.
PuppetConf 2014 Killer R10K Workflow With NotesPhil Zimmerman
R10K is a tool that automates the deployment of Puppet modules and environments. The presenter's organization previously used a single monolithic repository to manage all of their Puppet code and hiera data, which led to long test cycles, all-or-nothing deployments, and other issues. They transitioned to using R10K along with separate repositories for each module and hiera data. Now, changes can be tested and deployed independently for each module through a Sinatra-based Git hook that handles dynamic Puppetfile manipulation and environment deployment with R10K.
Continuous Delivery of Puppet-Based Infrastructure - PuppetConf 2014Puppet
The document discusses continuously deploying infrastructure with Puppet. It covers topics like deliverability, immutability, configuration as the heart of the build process, orchestration challenges, isolation, validation tools like rspec-puppet and Beaker, and deployment tools like Capistrano and r10k. The goal is to integrate infrastructure, validate configurations, and reliably deliver changes to production environments.
PuppetConf 2014 Killer R10K Workflow Without NotesPhil Zimmerman
The document describes the evolution of a workflow for managing thousands of Puppet modules using R10K and the Puppetfile. It started with all modules and code in a single monolithic repository, which led to long test cycles and all-or-nothing deployments. Introducing R10K and the Puppetfile allowed each module to be in its own repository and specify versions, enabling faster targeted testing and deployments. A post-receive hook was added for automated testing and deployment on code changes, improving the process.
This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
Puppet Camp Atlanta 2014: r10k Puppet WorkflowPuppet
The document discusses r10k, a Puppet workflow tool that helps manage Puppet code, modules, and data across different environments using Git and the Puppetfile. It recommends configuring r10k to store each environment as a Git branch, with a Puppetfile to define Forge modules and custom code and data in separate directories. r10k can then sync code and deploy changes to environments on the Puppet master automatically based on the Git configuration. This simplifies promotion of code, modules, and data through development, test, and production environments.
The document discusses the R10k tool and Puppet workflows. It describes how R10k is used to manage Puppet code modules from Git repositories. It shows the Puppet file and environments like production, testing, development. It demonstrates pushing new features to Git, and testing them on agents using the new_feature environment before deploying to production.
The document discusses continuously testing infrastructure by testing images, containers, and infrastructure as a service using tools like Packer, Serverspec, and Expect. It advocates applying test-driven development principles to infrastructure provisioning and management. Specifically, it suggests writing tests against an infrastructure API to define policies and desired functionality before provisioning resources. The document also describes testing based on data from PuppetDB to automatically generate and run configuration checks.
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.
PuppetConf 2014 Killer R10K Workflow With NotesPhil Zimmerman
R10K is a tool that automates the deployment of Puppet modules and environments. The presenter's organization previously used a single monolithic repository to manage all of their Puppet code and hiera data, which led to long test cycles, all-or-nothing deployments, and other issues. They transitioned to using R10K along with separate repositories for each module and hiera data. Now, changes can be tested and deployed independently for each module through a Sinatra-based Git hook that handles dynamic Puppetfile manipulation and environment deployment with R10K.
Continuous Delivery of Puppet-Based Infrastructure - PuppetConf 2014Puppet
The document discusses continuously deploying infrastructure with Puppet. It covers topics like deliverability, immutability, configuration as the heart of the build process, orchestration challenges, isolation, validation tools like rspec-puppet and Beaker, and deployment tools like Capistrano and r10k. The goal is to integrate infrastructure, validate configurations, and reliably deliver changes to production environments.
PuppetConf 2014 Killer R10K Workflow Without NotesPhil Zimmerman
The document describes the evolution of a workflow for managing thousands of Puppet modules using R10K and the Puppetfile. It started with all modules and code in a single monolithic repository, which led to long test cycles and all-or-nothing deployments. Introducing R10K and the Puppetfile allowed each module to be in its own repository and specify versions, enabling faster targeted testing and deployments. A post-receive hook was added for automated testing and deployment on code changes, improving the process.
This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
Курс Java-2016. Занятие 04 (часть 2). Git и GitHub7bits
This document discusses setting up and using Git and GitHub for version control of a Java project. It explains how to initialize a Git repository, add and commit files, configure user information, check status and history, ignore files, connect to a remote GitHub repository, authenticate with SSH keys, and push code to GitHub. The steps taken are initializing a Git repository, adding files, committing with a message, configuring user details, viewing status and log, ignoring files, connecting to a remote repository, generating and adding SSH keys, and pushing the local code to the remote GitHub repository.
Git Magic: Versioning Files like a Bosstmacwilliam
This document provides an overview of using Git for version control. It discusses setting up Git, making commits, branching, merging, resolving conflicts, reverting changes, collaborating remotely, and using hooks. Key aspects covered include distributed version control, non-linear development with branches, committing snapshots of a project's files, and resolving incompatible changes during merges.
#5 - Git - Contribuindo com um repositório remotoRodrigo Branas
This document discusses contributing to a remote Git repository. It explains how to push local commits to a remote repository using git push, and pull changes from the remote using git pull. It demonstrates cloning an existing remote repository locally, making changes, and pushing them back. It also shows how to fetch updates from the remote without merging using git fetch, and resolve differences using git diff and git merge.
This document discusses ChatOps, which is an approach to operations that uses chat platforms like Slack for communication around operational processes like infrastructure changes, code deploys, and monitoring. It describes how ChatOps integrates tools like Slack, Hubot, GitHub, Jenkins, and AWS Lambda to enable chat-based workflows for development and operations tasks. Key aspects of ChatOps mentioned include using chat for GitHub pull request management and Jenkins integration to enable chat-based code deploys and monitoring.
The document discusses Git branches and merging. It provides examples of creating branches, making commits on different branches, switching between branches, and merging branches using both fast-forward and recursive strategies. It also covers resolving merge conflicts that can occur when changes are made to the same file on different branches.
This document discusses the Python-based build tool Paver. It provides examples of using Paver to run tasks like checking out code from version control systems, executing shell commands, and passing command line arguments to tasks. Paver allows defining reusable tasks and dependencies between tasks to automate and script common software build processes.
GitGot: The Swiss Army Chainsaw of Git Repo ManagementJohn Anderson
GitGot is a Perl-based tool for batch management of collections of git repos. It has a number of interesting features and acts as a force multiplier when dealing with a large varied collection of repositories. My talk will cover why you would want to use GitGot as well as how to use it effectively.
LicensePlist - A license list generator of all your dependencies for iOS appl...将之 小野
The document discusses LicensePlist, an open source tool that generates a license list of all dependencies for iOS applications from CocoaPods, Carthage, and source code added manually. It describes how LicensePlist collects license information from these various sources and processes it to generate a property list file containing the licenses, which is displayed in the Settings app. The document also provides examples of similar existing tools and demonstrates LicensePlist's processing flow and use of parallel operations.
The document discusses Git and GitHub. It describes Git as a distributed version control system that allows multiple computers to work on versions of files simultaneously and merge changes. GitHub is a hosting service for Git repositories that allows for collaboration through features like forking repositories and creating pull requests. The document provides an overview of common Git commands and workflows, such as committing, branching, merging, and pushing changes to a remote repository.
This document provides an overview of several technologies: Git for version control, Python as a programming language, Django as a web framework built with Python, and Heroku as a platform for deploying Python/Django apps. It discusses basic Git commands and workflows. It also introduces Python concepts like shells, modules, and virtual environments. Django fundamentals like the MVT pattern and templates are covered. The document recommends Python 2.7 for Django projects and provides sample code.
This document provides an overview of using Git and GUI tools for Git. It discusses initializing and committing to a local repository, adding a remote repository, resolving conflicts, branching models like master/develop/feature branches, writing commit messages, generating SSH keys, ignoring files, and migrating from SVN to Git. Links are provided to resources on GitBook, branching models, SSH keys, writing commit messages, hosted version control services and more.
This document provides an overview of various Git commands, workflows, and best practices. It covers the basics of initializing repositories, committing, branching, merging, tagging, undoing changes, and working with remotes. It also summarizes several common Git workflows including centralized, feature branching, Gitflow, and forking models. Best practices around aliases, ignoring files, log formatting, and branching strategies are also outlined.
The document discusses a tool called Versions that checks for new releases of projects. It started as a hardcoded script but was refactored to use a YAML configuration file to make it more flexible and maintainable. The tool supports checking versions from many sites by parsing release notes with regex. While versioning schemes vary, the tool handles irregularities through configuration. Feedback from users helped improve the tool's capabilities and identify bugs.
tech node.js developer how to deploy apps to heroku, and how to quick setup heroku.
it is for all over platform, whatever your platform is, can follow steps to deploy to heroku.
Open Source Collaboration With Git And Git HubNick Quaranto
This document provides an overview of open source collaboration using Git and GitHub. It discusses the history and goals of Git, how it works internally with blobs, trees and commits, and how it supports distributed and multiple workflows like centralized, integration manager and benevolent dictator models. It also provides instructions on how to contribute to open source projects by forking repositories on GitHub, making changes locally, pushing to your fork and submitting a pull request.
The document discusses profiling Puppet performance, including profiling Facter facts, catalog compilation, and the agent run. It shows how to use tools like 'facter --timing', 'puppet apply --profile', and processing reports to identify slow areas. Specific optimizations discussed include caching external facts, avoiding repeated Hiera lookups, and profiling resources by type and time.
This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
Курс Java-2016. Занятие 04 (часть 2). Git и GitHub7bits
This document discusses setting up and using Git and GitHub for version control of a Java project. It explains how to initialize a Git repository, add and commit files, configure user information, check status and history, ignore files, connect to a remote GitHub repository, authenticate with SSH keys, and push code to GitHub. The steps taken are initializing a Git repository, adding files, committing with a message, configuring user details, viewing status and log, ignoring files, connecting to a remote repository, generating and adding SSH keys, and pushing the local code to the remote GitHub repository.
Git Magic: Versioning Files like a Bosstmacwilliam
This document provides an overview of using Git for version control. It discusses setting up Git, making commits, branching, merging, resolving conflicts, reverting changes, collaborating remotely, and using hooks. Key aspects covered include distributed version control, non-linear development with branches, committing snapshots of a project's files, and resolving incompatible changes during merges.
#5 - Git - Contribuindo com um repositório remotoRodrigo Branas
This document discusses contributing to a remote Git repository. It explains how to push local commits to a remote repository using git push, and pull changes from the remote using git pull. It demonstrates cloning an existing remote repository locally, making changes, and pushing them back. It also shows how to fetch updates from the remote without merging using git fetch, and resolve differences using git diff and git merge.
This document discusses ChatOps, which is an approach to operations that uses chat platforms like Slack for communication around operational processes like infrastructure changes, code deploys, and monitoring. It describes how ChatOps integrates tools like Slack, Hubot, GitHub, Jenkins, and AWS Lambda to enable chat-based workflows for development and operations tasks. Key aspects of ChatOps mentioned include using chat for GitHub pull request management and Jenkins integration to enable chat-based code deploys and monitoring.
The document discusses Git branches and merging. It provides examples of creating branches, making commits on different branches, switching between branches, and merging branches using both fast-forward and recursive strategies. It also covers resolving merge conflicts that can occur when changes are made to the same file on different branches.
This document discusses the Python-based build tool Paver. It provides examples of using Paver to run tasks like checking out code from version control systems, executing shell commands, and passing command line arguments to tasks. Paver allows defining reusable tasks and dependencies between tasks to automate and script common software build processes.
GitGot: The Swiss Army Chainsaw of Git Repo ManagementJohn Anderson
GitGot is a Perl-based tool for batch management of collections of git repos. It has a number of interesting features and acts as a force multiplier when dealing with a large varied collection of repositories. My talk will cover why you would want to use GitGot as well as how to use it effectively.
LicensePlist - A license list generator of all your dependencies for iOS appl...将之 小野
The document discusses LicensePlist, an open source tool that generates a license list of all dependencies for iOS applications from CocoaPods, Carthage, and source code added manually. It describes how LicensePlist collects license information from these various sources and processes it to generate a property list file containing the licenses, which is displayed in the Settings app. The document also provides examples of similar existing tools and demonstrates LicensePlist's processing flow and use of parallel operations.
The document discusses Git and GitHub. It describes Git as a distributed version control system that allows multiple computers to work on versions of files simultaneously and merge changes. GitHub is a hosting service for Git repositories that allows for collaboration through features like forking repositories and creating pull requests. The document provides an overview of common Git commands and workflows, such as committing, branching, merging, and pushing changes to a remote repository.
This document provides an overview of several technologies: Git for version control, Python as a programming language, Django as a web framework built with Python, and Heroku as a platform for deploying Python/Django apps. It discusses basic Git commands and workflows. It also introduces Python concepts like shells, modules, and virtual environments. Django fundamentals like the MVT pattern and templates are covered. The document recommends Python 2.7 for Django projects and provides sample code.
This document provides an overview of using Git and GUI tools for Git. It discusses initializing and committing to a local repository, adding a remote repository, resolving conflicts, branching models like master/develop/feature branches, writing commit messages, generating SSH keys, ignoring files, and migrating from SVN to Git. Links are provided to resources on GitBook, branching models, SSH keys, writing commit messages, hosted version control services and more.
This document provides an overview of various Git commands, workflows, and best practices. It covers the basics of initializing repositories, committing, branching, merging, tagging, undoing changes, and working with remotes. It also summarizes several common Git workflows including centralized, feature branching, Gitflow, and forking models. Best practices around aliases, ignoring files, log formatting, and branching strategies are also outlined.
The document discusses a tool called Versions that checks for new releases of projects. It started as a hardcoded script but was refactored to use a YAML configuration file to make it more flexible and maintainable. The tool supports checking versions from many sites by parsing release notes with regex. While versioning schemes vary, the tool handles irregularities through configuration. Feedback from users helped improve the tool's capabilities and identify bugs.
tech node.js developer how to deploy apps to heroku, and how to quick setup heroku.
it is for all over platform, whatever your platform is, can follow steps to deploy to heroku.
Open Source Collaboration With Git And Git HubNick Quaranto
This document provides an overview of open source collaboration using Git and GitHub. It discusses the history and goals of Git, how it works internally with blobs, trees and commits, and how it supports distributed and multiple workflows like centralized, integration manager and benevolent dictator models. It also provides instructions on how to contribute to open source projects by forking repositories on GitHub, making changes locally, pushing to your fork and submitting a pull request.
The document discusses profiling Puppet performance, including profiling Facter facts, catalog compilation, and the agent run. It shows how to use tools like 'facter --timing', 'puppet apply --profile', and processing reports to identify slow areas. Specific optimizations discussed include caching external facts, avoiding repeated Hiera lookups, and profiling resources by type and time.
This document discusses Mojolicious::Lite, a micro web application framework for Perl. It begins by introducing Mojolicious::Lite and positioning it as a framework for small, single-file web apps as opposed to production or complex applications. It then provides an example of a simple Mojolicious::Lite app and explains key aspects like routes, templates, and starting the app. Finally, it briefly mentions some similar Perl web frameworks and provides additional resources.
Drone is a Continuous Delivery platform built on Docker, written in Go
* Why I don’t choose Jenkins or GitLab CI?
* What is Drone CI?
* Drone Infrastructure
* How to install Drone in five minutes?
* Integrate your project
* Create your Drone plugin
* Try drone cli without drone server
Circus is a Python program that monitors and controls processes and sockets. It can be installed via pip or from source code. Circus uses a central daemon (circusd) that communicates with watchers, processes, and sockets via req/rep and pub/sub sockets. It has a web interface and command line tools for control and monitoring. Circus has advantages over similar programs like Supervisor such as its use of ZeroMQ for fast inter-process communication.
The document discusses setting up continuous integration for a JavaScript project using Jenkins. It describes configuring Jenkins to run unit tests with RhinoUnit after checking out the code from a GitHub repository. Jenkins fetches the latest code, runs the unit tests via an Ant target, and reports the results, allowing for continuous integration and automated testing of the JavaScript project.
The document discusses using Docker and SaltStack to build dynamic and highly available computing environments. It describes how to separate concerns between the host systems and application services through containerization with Docker. It also discusses how to implement the Twelve-Factor App methodology for building portable apps by defining factors like codebase, dependencies, configuration, backing services, scaling, and more. The document provides examples of building Docker images for services like Nginx and binding container ports, as well as using environment variables to configure application dependencies.
Golang 101 for IT-Pros - Cisco Live Orlando 2018 - DEVNET-1808Cisco DevNet
This session is an introduction to Golang - the Go programming language - for IT Professionals. We'll explain how to setup a GO development environment, create a simple HTTP/2 Web API, and embed our code into a Docker container. We'll also go through the reasons why the language is so popular to create network applications by showing how the language is expressive, concise, clean, and efficient. Join this session if you've started writing Python scripts that consume Web APIs, and you now want to go to the next stage by creating your own APIs to expose or store Enterprise Data.
DEVNET-1808
https://www.ciscolive.com/us/learn/sessions/session-catalog/?search=DEVNET-1808
The document discusses multiple approaches to managing Puppet modules, including keeping all modules in a single repo (which is not scalable), using a Puppetfile to track modules and dependencies, librarian-puppet and librarian-puppet-simple to install modules from a Puppetfile, and r10k to deploy modules from a git repo to environments. It recommends using separate repos for each module, a Puppetfile to track modules, and r10k to simplify development workflows.
The document discusses using Docker for continuous integration (CI) with tools like Drone and Gogs. It notes that CI setup can involve many tools, configurations, and challenges. Docker helps address these issues by providing containerization which Drone supports natively. Docker volumes also help with persistent storage challenges. The document provides an example Dockerfile and Drone pipeline configuration.
In an ideal world, you would write Python code and then it would work perfectly. But unfortunately, it doesn't work in this manner. In my talk, I'll cover how to efficiently debug your programs, especially in cloud environments or inside Kubernetes.
OSDC 2014: Ole Michaelis & Sönke Rümpler: Make it SOLID - Software Architectu...NETWAYS
Starting with Chef or Puppet as a System Administrator will lead you to a problem where you are not sure what’s the best solution of a problem in terms of software architecture.
We will give you a brief overview of general well known and battle tested software patterns, which also applies to infrastructure management code. In addition, we‘ll also show Antipatterns, and best practices.
The document discusses automated deployments using SaltStack and Docker containers. It describes how Docker can be used to build application environments in isolated containers with defined dependencies. This allows services to be easily started and stopped, and experiments with a low barrier for entry. The document outlines how to separate concerns between the host system and application services using Docker images. It also discusses Twelve-Factor App methodology for building applications and binding application ports, as well as using environment variables for configuration.
This document contains a list of tools, methodologies and resources for infrastructure automation including IDEs like Git and GitHub, version control best practices like Gitflow and SemVer, issue tracking with Jira, configuration management with Puppet and provisioning modules, and links to documentation, code repositories, and tools for tasks like encryption and timezone configuration.
Webinar: Building Embedded Applications from QtCreator with DockerBurkhard Stubert
This document discusses using Docker containers to build embedded apps from QtCreator more efficiently. It presents three solutions: 1) using virtual machines which is currently done but slow, 2) building apps in Docker containers on the local workstation which is faster, and 3) building apps in containers on remote workstations. The document then provides steps for setting up a development environment using Docker to build an app in QtCreator, including installing a Qt SDK in a container, configuring QtCreator, building the app using a Docker wrapper for CMake, and running the app on a Raspberry Pi device.
Build and run embedded apps faster from qt creator with dockerQt
This document discusses using Docker containers to build and run embedded Qt applications from QtCreator more efficiently. It proposes wrapping CMake calls in a Docker script to build apps in containers on the local workstation instead of virtual machines. The key steps are installing a Qt SDK in a container, configuring QtCreator kits to use the Docker wrapper script for builds, and setting up deployment to run the built apps on target devices via SSH. This allows reusing existing container builds on a powerful workstation for faster development compared to building each app version's SDK in a separate virtual machine.
This is a presentation give to the Vancouver Drupal users group about moving to GIT as a version control system for a small development team. The presentation details the workflow we settled on, and the git flow method for branch management. You can see a video of the presentation here - http://www.ustream.tv/recorded/13544036
Building your own RC Car with Raspberry PiJeff Prestes
In this presentation we talk about basic concepts of Internet of Things, Java for Embedded, Android, Raspberry Pi and a practical workshop how to create your own IoT RC Car - Brasilino - and rent it.
GitHub investierte sehr stark im Bereich Security und hat als weltweit grösste Open-Source-Plattform auch die ideale Basis, um Abhängigkeiten und Schwachstellen viel genutzter Bibliotheken zu analysieren und zu notifizieren. In öffentlichen wie auch in privaten Repositories in GitHub Enterprise Cloud und GitHub Enterprise Server stehen einem unter dem Betriff "GitHub Advanced Security" eine Vielzahl von Sicherheitsfunktionen zur Verfügung.
Dieser Vortrag zeigt die Funktionsweise der Features Code Scanning, Secret Scanning und Dependency Review auf. GitHub Actions und Pull Requests runden die Werkzeugkiste für einen erfolgreichen DevSecOps-Prozess ab.
Express is a popular Node.js framework that provides scaffolding for building web applications in an organized manner. It allows adding middleware functions and templating engines like Dust.js to add dynamic content. The document demonstrates how to use the Request module to call an external weather API, parse the JSON response, and render the data in a Dust template to present weather information for different cities. It concludes by discussing deploying the application to production platforms like Bluemix.
Similar to Webinar - Automated Puppet Code Deployment with R10K (20)
This document outlines strategies for optimizing AWS costs based on the lessons learned from Scrooge McDuck. It discusses using the right instance types, reserved instances, spot instances, monitoring usage, redesigning architecture, and removing idle and unnecessary resources. It provides examples of policies for automatically stopping and starting test environments outside of business hours to save on costs. Specifically, it shows policies for suspending auto scaling groups, stopping EC2 instances and RDS databases in test environments during off hours, and resuming them during on hours.
Slides from Walter Heck's presentation on 2 factor authentication presented during the AWS The Hague meetup on 15th of August 2018. https://www.meetup.com/aws-hague/events/llgwrpyxlbtb/
GitLab CI is a continuous integration service fully integrated with GitLab. It allows users to define build and test workflows directly in the GitLab repository using a .gitlab-ci.yml file. GitLab CI runs jobs defined in the YAML file on GitLab-hosted runners which can be Docker containers. It supports features like artifacts, dependencies between jobs, stages, and secret variables to securely pass credentials to builds.
Walter Heck presented on using Puppet to automate Icinga monitoring. He discussed what Puppet is and its typical architecture. He then showed how to set up the Icinga server and client using Puppet modules, including configuring MySQL/Postgres, setting up Icinga2 and Icingaweb2, and exporting host configurations from Puppet to populate Icinga's monitoring configuration. He concluded by discussing next steps like creating application-specific profiles and advertising upcoming Icinga training in Amsterdam.
Webinar - Auto-deploy Puppet Enterprise: Vagrant and OscarOlinData
To automatically deploy a virtualbox setup with Puppet Enterprise installed on a master and subsequent machines hooked up to that master with everything ready to go PuppetLabs maintains a vagrant plugin called Oscar. This webinar explains what we can do with Oscar and what the benefits are.
Webinar - High Availability and Distributed Monitoring with Icinga2OlinData
We will explore all the possible scenarios on how to scale Icinga setup for high availability and distributed monitoring. This involves creation of zones or clusters to provide us with a more powerful yet dynamic monitoring infrastructure.
Webinar - Windows Application Management with PuppetOlinData
This webinar will help you to understand how to install Windows application and services, We will also look into how to manage windows services related to the application.
Webinar - Continuous Integration with GitLabOlinData
The document is a presentation about continuous integration with GitLab. It discusses what continuous integration is, why it is important, and how to set up continuous integration builds using GitLab. Specifically, it defines continuous integration as integrating code regularly to prevent problems and identify issues early. It recommends gradually adopting continuous integration practices like writing test cases whenever bugs are fixed. The presentation also provides instructions on setting up a GitLab runner to enable continuous integration builds and adding a .gitlab-ci.yml file to configure builds.
Webinar - Centralising syslogs with the new beats, logstash and elasticsearchOlinData
This webinar will cover details on Centralising syslogs with the help of Beats, Logstash and Elasticsearch. This will help you to Centralise logs for monitoring and analysis.
The document describes how to configure an Icinga 2 monitoring setup using Puppet including:
1. Configuring Puppet modules for Icinga 2, Icinga Web 2, and MySQL
2. Defining Puppet classes and resources to install, configure, and manage the Icinga 2 application, database, and web interface
3. Describing how Puppet is used to define Icinga 2 objects, zones, hosts, and services that are collected by Icinga for monitoring
This webinar we will explore how project managements are generally done for devops and the tool taiga.io will provide us with all the necessary project management tools.
This document appears to be a presentation about the company OlinData and their use of Puppet for infrastructure automation. It discusses topics like silos in infrastructure, why the company chose Puppet, their initial plan and how reality differed, and managing frequent management changes. Images are included throughout to accompany various points. The presentation encourages asking the presenter if help is needed with Puppet or DevOps.
PuppetDB gives users fast, robust, centralized storage for Puppet-produced data. It caches data generated by Puppet, and gives you advanced features at awesome speed with a powerful API.
Learn new things with fun.
Webinar - Manage user, groups, packages in windows using puppetOlinData
The document is a presentation about managing users, groups, packages, and files in Windows using Puppet configuration management. It discusses installing the Puppet agent on Windows, the Puppet run process, supported Puppet resources for Windows including file, user, group, package, and service resources. It also covers Puppet profiles, roles, modules from the Puppet Forge, and upcoming Puppet training from OlinData.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program