Current session guides through Vagrant. Shows some tips and tricks and targeted to software developers.
Practical activities can be found here: https://github.com/akranga/devops-hackathon-1
DevOps hackathon Session 2: Basics of ChefAntons Kranga
The document discusses infrastructure provisioning using Chef. It explains that Chef uses a declarative approach where you describe the desired state rather than how to achieve it. Cookbooks contain recipes that describe resources to bring a VM to the specified state. Cookbooks are repeatable, testable units that can install packages, configure services, create users and templates. Vagrant and Chef are often used together, with Vagrant managing VMs and triggering Chef provisioning to install software inside VMs.
This document summarizes a presentation on using Vagrant for development. The presentation covers motivation for using Vagrant, basic Vagrant usage, provisioning Vagrant machines with Chef cookbooks, and creating custom base images with Packer. The agenda includes an introduction to Vagrant, demonstrating common Vagrant commands, modifying Vagrantfiles to configure VMs, provisioning VMs with Chef recipes, and using Packer to build reusable base images.
The document discusses automating software deployment using Ansible. It provides an overview of Ansible's basic concepts like inventory files to define hosts, playbooks to execute tasks on hosts, and roles to bundle related tasks. It then discusses using Ansible roles to automate deployments, including the ansistrano roles which can deploy applications by copying files, managing releases, and supporting deployment hooks. Overall the document presents Ansible as a way to easily automate and standardize software deployment processes.
Vagrant can be used to create consistent development environments that match production. This allows developers to develop locally yet still have access to all production dependencies. The presenter recommends using Vagrant to provision local development environments that match the OS used in production AWS environments. Developers can then use the same configuration management tools and processes locally and in production. Code is deployed from Vagrant environments to AWS, ensuring development and production remain consistent. A demo is provided to stand up identical local and AWS environments and deploy code between them.
Vagrant is a well-known tool for creating development environments in a simple and consistent way. Since we adopted in our organization we experienced several benefits: lower project setup times, better shared knowledge among team members, less wtf moments ;-)
In this session I'd like to share our experience, including but not limited to:
- advanced vagrantfile configuration
- vm configuration tips for dev environment: performance, debug, tuning
- our wtf moments
- puphet/phansilbe: hot or not?
- tips for sharing a box
Infrastructure as code is an approach to managing servers where their configuration is defined using code and version control rather than manual shell commands. Ansible is a tool that allows defining servers' desired state in YAML files checked into version control. It can automatically install software, configure systems, and ensure consistency across multiple servers using SSH without requiring an agent. Playbooks declare tasks to run that are idempotent, allowing Ansible to safely deploy changes. This approach improves on manual configuration by enabling testing, collaboration, and rolling back changes if needed.
The document outlines an 90 minute introduction to Ansible using Docker. It discusses setting up the environment with Docker, using ad-hoc commands and playbooks to automate tasks like installing Apache and configuring variables. Exercises demonstrate inventory management, templating configurations with Jinja2, and other core Ansible concepts. The document provides an overview but does not cover more advanced topics like dynamic inventory, roles, writing custom modules, or Ansible Tower.
Mukta Aphale presented at ChefConf 2015. She discussed her background transitioning from developer to DevOps architect. She contributed to Chef development and created several Chef knife plugins. Aphale also discussed using Docker and Chef together to automate container management and deployment. She showed how to build a Docker image using Chef recipes and push it to a registry for deployment using Chef push jobs.
With Vagrant 1.1, you can use the same configuration and workflow to spin up and provision machines in VirtualBox, VMware, AWS, RackSpace, and more. You get all the benefits of Vagrant with the power of working in whatever environment you need to.
In this talk, you’ll learn how to use the new multi-provider features of Vagrant to more effectively develop and test Chef cookbooks.
This document discusses testing principles and tools for infrastructure as code using Chef. It covers test-driven development (TDD) principles like writing tests first to define desired behavior. Chef testing tools covered include ChefSpec for unit testing cookbooks, ServerSpec for integration/black-box testing, and Foodcritic for linting cookbooks. It also discusses Test Kitchen for testing cookbooks across platforms and continuous integration (CI) using these tools.
This document discusses using Chef configuration management with Docker containers. It begins with examples of incrementally building a Docker tutorial using Chef, starting with a "hello world" container and moving on to more advanced containers for an echo server and web application. It then discusses using the kitchen-dokken plugin to test Chef recipes using Docker instead of virtual machines. The examples demonstrate how to version and tag releases as new features and patches are added.
The document discusses two serverless computing platforms that support Swift - OpenWhisk and Fn.
OpenWhisk is an open source system that is event-driven, containerized, and allows chaining of actions. It is hosted on Bluemix but can be difficult to deploy elsewhere. Fn is container-native and deploys functions as containers communicating via standard input/output. Both allow simple Swift functions to be deployed and called remotely with REST APIs or command line tools. The document provides examples of writing, deploying and calling functions on each platform.
Continuous Infrastructure: Modern Puppet for the Jenkins Project - PuppetConf...Puppet
This document summarizes Tyler Croy's presentation on managing the Jenkins infrastructure using Puppet. It describes how the infrastructure evolved from an unmanaged setup at Sun/Oracle to using masterless Puppet and eventually Puppet Enterprise. Key aspects covered include managing services, hardware, code layout, testing, and deployment process. Special thanks are given to Puppet Labs for their support of the project.
This document discusses using Chef to automate IT infrastructure. It covers installing the Chef client and server, creating cookbooks with recipes to configure nodes, uploading cookbooks to the server, managing nodes with run lists and roles, and using community cookbooks. Key steps include generating a starter kit, writing recipes with resources, uploading and applying cookbooks, bootstrapping nodes, and managing configurations through attributes, templates, and metadata.
Capistrano is an open source tool for running scripts on multiple servers. It’s primary use is for easily deploying applications. While it was built specifically for deploying Rails apps, it’s pretty simple to customize it to deploy other types of applications.
capifony is a deployment recipes collection that works with both symfony and Symfony2 applications.
From Ansible's website: "Ansible is a radically simple IT automation engine that automates cloud provisioning, configuration management, application deployment, intra-service orchestration, and many other IT needs."
This introduction is based on ansible official docs, capturing most important information to make it easy to understand Ansible main concepts.
This document provides an overview of using Vagrant to automate the setup of a development environment. It describes how Vagrant can be used to create and configure a virtual machine (VM) that contains all the necessary tools and files for a project, allowing new team members to get set up and running quickly by running a single script. The document outlines the steps to install Vagrant and VirtualBox, add a Ubuntu box, initialize a Vagrantfile, provision the VM with common tools like Apache and PHP, and set up a sample Drupal project.
This document discusses best practices for using Ansible for automation and configuration management. It recommends writing reusable roles with atomic and well-parameterized configuration, keeping roles in separate Git repositories, and using defaults instead of variables where possible. It also presents three patterns for using Ansible: a single playbook with hierarchical variables, configuration encoders to support multiple file formats, and using an Android repo script to manage multiple environments and versions of roles continuously.
The document discusses using Ansible to deploy PHP applications. It provides an overview of Ansible concepts like inventory, modules, playbooks and roles. It also covers common Ansible patterns like managing dependencies, accessing remote servers, deploying code from version control and implementing blue-green deployments. Examples are given for tasks like installing packages, copying files, templating configuration and automating full application deployments using third-party roles.
Vagrant allows users to define and configure lightweight virtual development environments. It uses VirtualBox to run virtual machines from a Vagrantfile configuration. The document discusses how Vagrant abstracts hardware, allows multiple operating systems to run concurrently on virtual hardware, and is limited by physical resources. It also outlines how in 3 lines users can download a base box, initialize a new Vagrant project, and boot the virtual machine. Key benefits of Vagrant include quick setup for new team members, ability to version control server configurations, and easy switching between projects.
It Works On My Machine: Vagrant for Software DevelopmentCarlos Perez
Vagrant is a command-line interface for simplifying the use of virtual machines (VM's). Vagrant allows teams to standardize their software development workflows by offering a uniform and portable interface to provision and run VM's on different operating platforms such as Mac OS X, Windows, and Linux and achieve identical results. It supports all the major virtualization solutions such as VirtualBox, VMWare, and Hyper-V and supports configuration tools that range from simple shell scripts to powerful Chef and Puppet recipes. Developers simply invoke “vagrant up” and immediately enjoy a standard, consistent, and reproducible VM for software development and testing.
Deploying an application with Chef and DockerDaniel Ku
Docker 캐주얼 토크 #1 (2014-10-15)에서 발표하기 위해 만든 자료.
원래 'Docker 실서비스 도입기'를 발표하려고 했으나, 아직 도입이 마무리되지 못한 관계로 그 과정에서 의미 있는 부분을 찾아보았다.
그래서 Chef와 Docker가 도입되면 StudyGPS에서 어플리케이션을 업데이트하는 기존의 방식이 어떻게 변화하는지에 대해 설명하고, 그 변화의 의미에 대해서 생각해보고 정리하였다.
Satellite 6 introduces new features for automation including improved support for Puppet. Puppet allows for recipe-style configuration management and drift management. The presentation demonstrates installing and configuring Puppet on a server and client, writing Puppet code to manage files and directories, and using the Puppet dashboard. Considerations for using Puppet with Satellite 6 include keeping Puppet modules modular and mapping modules to Satellite host groups.
Vagrant is a well-known tool for creating development environments in a simple and consistent way. Since we adopted in our organization we experienced several benefits: lower project setup times, better shared knowledge among team members, less wtf moments ;-)
In this session I'd like to share our experience, including but not limited to:
- advanced vagrantfile configuration
- vm configuration tips for dev environment: performance, debug, tuning
- our wtf moments
- puphet/phansilbe: hot or not?
- tips for sharing a box
Chef is an open-source automation platform that treats infrastructure as code. It allows users to automate how infrastructure is configured, deployed and managed across any environment using a powerful DSL written in Ruby. Key features of Chef include server provisioning, automation of infrastructure changes, and management of configurations through recipes and cookbooks which are shared through an online community. Linecook is presented as an alternative to Chef for server automation that uses shell scripts instead of Ruby code and relies on established tools like SSH, VirtualBox, and bash instead of requiring installation of the Chef platform.
Orchestration? You Don't Need Orchestration. What You Want is Choreography.Julian Dunn
This document discusses the differences between orchestration and choreography in configuration management. Orchestration involves a central orchestrator executing ordered operations on independent machines, while choreography involves autonomous actors that make and verify promises to each other to achieve a desired state. The document argues that choreography is preferable because it avoids single points of failure, enables more autonomy between systems, and allows for better coordination across a fleet with less reliance on external real-time state systems.
The document discusses Python virtual environments (virtualenv) and the pip package manager. It introduces virtualenv and pip, explains why they are useful tools for isolating Python environments and managing packages, and provides exercises for creating virtual environments, using pip to install/uninstall packages, creating your own pip packages, and sharing packages on PyPI. The goal is to help users understand and learn to use these tools in 90 minutes.
This document provides an overview of Ansible, an IT automation tool. It discusses Ansible's features such as being agentless, using SSH, and being idempotent. It also covers installing Ansible, using Ansible modules, writing playbooks in YAML format, managing inventory, and using ad-hoc commands and roles for automation.
DevOps Days Tel Aviv - Serverless ArchitectureAntons Kranga
Slides from Serverless Architecture with AWS workshop that has been delivered in Tel Aviv at December 2016 and XP Days in Kyiv at November. We go in details about AWS Lambda and give few implementation blueprints targeted to web applications
The document provides 5 entrepreneurial strategies for making money: 1) Learn how to sell your product or service effectively, 2) Pursue your passion for your business, 3) Believe in the value of your product and don't be afraid to charge accordingly, 4) Track key performance indicators to understand your business success, and 5) Adopt a mindset of failing fast and often to quickly learn and improve through iteration. It also offers 6 months of free business coaching to help readers implement these strategies and increase their cash flow.
With Vagrant 1.1, you can use the same configuration and workflow to spin up and provision machines in VirtualBox, VMware, AWS, RackSpace, and more. You get all the benefits of Vagrant with the power of working in whatever environment you need to.
In this talk, you’ll learn how to use the new multi-provider features of Vagrant to more effectively develop and test Chef cookbooks.
This document discusses testing principles and tools for infrastructure as code using Chef. It covers test-driven development (TDD) principles like writing tests first to define desired behavior. Chef testing tools covered include ChefSpec for unit testing cookbooks, ServerSpec for integration/black-box testing, and Foodcritic for linting cookbooks. It also discusses Test Kitchen for testing cookbooks across platforms and continuous integration (CI) using these tools.
This document discusses using Chef configuration management with Docker containers. It begins with examples of incrementally building a Docker tutorial using Chef, starting with a "hello world" container and moving on to more advanced containers for an echo server and web application. It then discusses using the kitchen-dokken plugin to test Chef recipes using Docker instead of virtual machines. The examples demonstrate how to version and tag releases as new features and patches are added.
The document discusses two serverless computing platforms that support Swift - OpenWhisk and Fn.
OpenWhisk is an open source system that is event-driven, containerized, and allows chaining of actions. It is hosted on Bluemix but can be difficult to deploy elsewhere. Fn is container-native and deploys functions as containers communicating via standard input/output. Both allow simple Swift functions to be deployed and called remotely with REST APIs or command line tools. The document provides examples of writing, deploying and calling functions on each platform.
Continuous Infrastructure: Modern Puppet for the Jenkins Project - PuppetConf...Puppet
This document summarizes Tyler Croy's presentation on managing the Jenkins infrastructure using Puppet. It describes how the infrastructure evolved from an unmanaged setup at Sun/Oracle to using masterless Puppet and eventually Puppet Enterprise. Key aspects covered include managing services, hardware, code layout, testing, and deployment process. Special thanks are given to Puppet Labs for their support of the project.
This document discusses using Chef to automate IT infrastructure. It covers installing the Chef client and server, creating cookbooks with recipes to configure nodes, uploading cookbooks to the server, managing nodes with run lists and roles, and using community cookbooks. Key steps include generating a starter kit, writing recipes with resources, uploading and applying cookbooks, bootstrapping nodes, and managing configurations through attributes, templates, and metadata.
Capistrano is an open source tool for running scripts on multiple servers. It’s primary use is for easily deploying applications. While it was built specifically for deploying Rails apps, it’s pretty simple to customize it to deploy other types of applications.
capifony is a deployment recipes collection that works with both symfony and Symfony2 applications.
From Ansible's website: "Ansible is a radically simple IT automation engine that automates cloud provisioning, configuration management, application deployment, intra-service orchestration, and many other IT needs."
This introduction is based on ansible official docs, capturing most important information to make it easy to understand Ansible main concepts.
This document provides an overview of using Vagrant to automate the setup of a development environment. It describes how Vagrant can be used to create and configure a virtual machine (VM) that contains all the necessary tools and files for a project, allowing new team members to get set up and running quickly by running a single script. The document outlines the steps to install Vagrant and VirtualBox, add a Ubuntu box, initialize a Vagrantfile, provision the VM with common tools like Apache and PHP, and set up a sample Drupal project.
This document discusses best practices for using Ansible for automation and configuration management. It recommends writing reusable roles with atomic and well-parameterized configuration, keeping roles in separate Git repositories, and using defaults instead of variables where possible. It also presents three patterns for using Ansible: a single playbook with hierarchical variables, configuration encoders to support multiple file formats, and using an Android repo script to manage multiple environments and versions of roles continuously.
The document discusses using Ansible to deploy PHP applications. It provides an overview of Ansible concepts like inventory, modules, playbooks and roles. It also covers common Ansible patterns like managing dependencies, accessing remote servers, deploying code from version control and implementing blue-green deployments. Examples are given for tasks like installing packages, copying files, templating configuration and automating full application deployments using third-party roles.
Vagrant allows users to define and configure lightweight virtual development environments. It uses VirtualBox to run virtual machines from a Vagrantfile configuration. The document discusses how Vagrant abstracts hardware, allows multiple operating systems to run concurrently on virtual hardware, and is limited by physical resources. It also outlines how in 3 lines users can download a base box, initialize a new Vagrant project, and boot the virtual machine. Key benefits of Vagrant include quick setup for new team members, ability to version control server configurations, and easy switching between projects.
It Works On My Machine: Vagrant for Software DevelopmentCarlos Perez
Vagrant is a command-line interface for simplifying the use of virtual machines (VM's). Vagrant allows teams to standardize their software development workflows by offering a uniform and portable interface to provision and run VM's on different operating platforms such as Mac OS X, Windows, and Linux and achieve identical results. It supports all the major virtualization solutions such as VirtualBox, VMWare, and Hyper-V and supports configuration tools that range from simple shell scripts to powerful Chef and Puppet recipes. Developers simply invoke “vagrant up” and immediately enjoy a standard, consistent, and reproducible VM for software development and testing.
Deploying an application with Chef and DockerDaniel Ku
Docker 캐주얼 토크 #1 (2014-10-15)에서 발표하기 위해 만든 자료.
원래 'Docker 실서비스 도입기'를 발표하려고 했으나, 아직 도입이 마무리되지 못한 관계로 그 과정에서 의미 있는 부분을 찾아보았다.
그래서 Chef와 Docker가 도입되면 StudyGPS에서 어플리케이션을 업데이트하는 기존의 방식이 어떻게 변화하는지에 대해 설명하고, 그 변화의 의미에 대해서 생각해보고 정리하였다.
Satellite 6 introduces new features for automation including improved support for Puppet. Puppet allows for recipe-style configuration management and drift management. The presentation demonstrates installing and configuring Puppet on a server and client, writing Puppet code to manage files and directories, and using the Puppet dashboard. Considerations for using Puppet with Satellite 6 include keeping Puppet modules modular and mapping modules to Satellite host groups.
Vagrant is a well-known tool for creating development environments in a simple and consistent way. Since we adopted in our organization we experienced several benefits: lower project setup times, better shared knowledge among team members, less wtf moments ;-)
In this session I'd like to share our experience, including but not limited to:
- advanced vagrantfile configuration
- vm configuration tips for dev environment: performance, debug, tuning
- our wtf moments
- puphet/phansilbe: hot or not?
- tips for sharing a box
Chef is an open-source automation platform that treats infrastructure as code. It allows users to automate how infrastructure is configured, deployed and managed across any environment using a powerful DSL written in Ruby. Key features of Chef include server provisioning, automation of infrastructure changes, and management of configurations through recipes and cookbooks which are shared through an online community. Linecook is presented as an alternative to Chef for server automation that uses shell scripts instead of Ruby code and relies on established tools like SSH, VirtualBox, and bash instead of requiring installation of the Chef platform.
Orchestration? You Don't Need Orchestration. What You Want is Choreography.Julian Dunn
This document discusses the differences between orchestration and choreography in configuration management. Orchestration involves a central orchestrator executing ordered operations on independent machines, while choreography involves autonomous actors that make and verify promises to each other to achieve a desired state. The document argues that choreography is preferable because it avoids single points of failure, enables more autonomy between systems, and allows for better coordination across a fleet with less reliance on external real-time state systems.
The document discusses Python virtual environments (virtualenv) and the pip package manager. It introduces virtualenv and pip, explains why they are useful tools for isolating Python environments and managing packages, and provides exercises for creating virtual environments, using pip to install/uninstall packages, creating your own pip packages, and sharing packages on PyPI. The goal is to help users understand and learn to use these tools in 90 minutes.
This document provides an overview of Ansible, an IT automation tool. It discusses Ansible's features such as being agentless, using SSH, and being idempotent. It also covers installing Ansible, using Ansible modules, writing playbooks in YAML format, managing inventory, and using ad-hoc commands and roles for automation.
DevOps Days Tel Aviv - Serverless ArchitectureAntons Kranga
Slides from Serverless Architecture with AWS workshop that has been delivered in Tel Aviv at December 2016 and XP Days in Kyiv at November. We go in details about AWS Lambda and give few implementation blueprints targeted to web applications
The document provides 5 entrepreneurial strategies for making money: 1) Learn how to sell your product or service effectively, 2) Pursue your passion for your business, 3) Believe in the value of your product and don't be afraid to charge accordingly, 4) Track key performance indicators to understand your business success, and 5) Adopt a mindset of failing fast and often to quickly learn and improve through iteration. It also offers 6 months of free business coaching to help readers implement these strategies and increase their cash flow.
My last talk at DevTernity conference. It was about anti patterns captured consulting several projects on their DevOps adoption. There are few common pitfalls we can see repeating again and again over DevOps culture discovery. This talk is my experience summary there
Antons Kranga Building Agile InfrastructuresAntons Kranga
This document provides an overview of a presentation on building agile infrastructures. It introduces the presenter, Antons Kranga, and his background. It then outlines the goals of DevOps in bringing developers and operations teams together through practices like Agile and ITIL. The presentation will discuss strategies for adopting a DevOps model, including provisioning continuous integration, automating infrastructure testing, and provisioning QA and production environments using tools like Chef, Vagrant, Jenkins, Nexus, and Test Kitchen. It will also cover techniques for automating infrastructure like configuration management with Chef recipes and testing infrastructure with tools like Chaos Monkey.
Java Day Kharkiv - Next-gen engineering with Docker and KubernetesAntons Kranga
My presentation in JavaDay conf Kharkiv (Ukraine). It has been targeted mainly to Java developers to demonstrate how modern containerisation tools can improve developers agility and productivity.
This presentations contains link to he Workshop that has been delivered in OpenSlava 2015
My presentation about Serverless Architectures in JavaDay Lviv, June 2016. It covers AWS Lambda and related AWS Services. LiveDemo have got terraform and apex.
Riga dev day: Lambda architecture at AWSAntons Kranga
My recent talk at Riga DevDay about Lambda architect at AWS. It illustrates few design simplifications that we can get when we implement Lambda Architecture in Cloud Native way
DevOps Hackathon: Session 3 - Test Driven InfrastructureAntons Kranga
We will assume that you already familiar with Vagrant and Chef fundamentals described in session 1 and 2. Today we will go through TestKitchen and ServerSpec. While chef-dk is not stable, this is most reliable path.
Practical activities can be found here:
https://github.com/akranga/devops-hackathon-3
CloudFoundry is a mature and production-ready opensource Platform-as-a-Service. That can serve as standard app deployment and hosting platform for enterprise. This talk will focus around CloudFoundry capabilities as private-PaaS
Last update to the DevOps anti-patterns talk that IMO deserves separate upload. It was about anti patterns captured consulting several projects on their DevOps adoption. There are few common pitfalls we can see repeating again and again over DevOps culture discovery. This talk is my experience summary there
Vagrant allows users to easily create and configure virtual development environments. The document outlines a 5 step process to get started with Vagrant: 1) select a virtualization provider like VirtualBox, 2) install Vagrant, 3) download a virtual machine image or "box", 4) initialize and start the VM with Vagrant commands, and 5) log into the VM via SSH. It also discusses additional features like version controlling Vagrant files, customizing the VM, using multiple VMs, and provisioning VMs with tools like Puppet, Chef, or Ansible.
Get started with Vagrant! This basic intro assumes no prior knowledge of the platform, and it is universally applicable regardless of the Provider (hypervisor\cloud platform) that you are using.
We also delve briefly into provisioners (ex: Shell, Puppet, Chef) to unlock the true power of Vagrant: quick & easy templates of production systems.
Create Development and Production Environments with VagrantBrian Hogan
Need a Linux box to test a Wordpress site or a Windows VM to test a web site on IE 10? Creating a virtual machine to test or deploy your software doesn’t have to be a manual process. Bring one up in seconds with Vagrant, software for creating and managing virtual machines. With Vagrant, you can bring up a new virtual machine with the software you need, share directories, copy files, and configure networking using a friendly DSL. You can even use shell scripts or more powerful provisioning tools to set up your software and install your apps. Whether you need a Windows machine for testing an app, or a full-blown production environment for your apps, Vagrant has you covered.
In this talk you’ll learn to script the creation of multiple local virtual machines. Then you’ll use the same strategy to provision production servers in the cloud.
I work with Vagrant, Terraform, Docker, and other provisioning systems daily and am excited to show others how to bring this into their own workflows.
Puppet is automation software that helps system administrators manage infrastructure by automating provisioning, configuration, and other repetitive tasks. It ensures consistency and stability. Puppet consists of a Puppet Master and Puppet Agents. Vagrant provides a way to easily create and configure virtual development environments using configuration files and automation (e.g. Puppet). It uses Oracle VirtualBox and allows specifying and provisioning resources. Benefits include consistent environments for development, testing, and teams.
Chef Workshop: Setup Environment with Chef,Vagrant, and BerkshelfJun Sakata
The document provides an introduction and agenda for a Chef developers' workshop. It outlines the prerequisites including VirtualBox, Vagrant, and Chef. It then covers two parts: 1) getting started with Chef using Vagrant including creating a cookbook and recipes, and 2) exploring the structure of Chef including cookbooks, recipes, attributes and resources. The objectives are to learn the basics of Chef, be able to use Chef to create infrastructure code, and build one's own cookbook.
Vagrant allows developers to quickly set up uniform development environments for Node.js projects. It uses configuration files to define and provision virtual machines with all necessary tools and libraries. Chef is used for configuration management, ensuring environments are identical. Vagrant provides portability and abstraction, allowing environments to run on different providers like VirtualBox or cloud services.
Create Disposable Test Environments with Vagrant and Puppet Coveros, Inc.
As the pace of development increases, testing has more to do and less time in which to do it. Software testing must evolve to meet delivery goals while continuing to meet quality objectives. Gene Gotimer explores how tools like Vagrant and Puppet work together to provide on-demand, disposable test environments that are delivered quickly, in a known state, with pre-populated test data and automated test fixture provisioning. With a single command, Vagrant provisions one or more virtual machines on a local box, in a private or public cloud. Puppet then takes over to install and configure software, setup test data, and get the system or systems ready for testing. Since the process is automated, anyone on the team can use the same Vagrant and Puppet scripts to get his own virtual environment for testing. When you are finished with it, Vagrant tears it back down and restores it to the same original state.
Create Disposable Test Environments with Vagrant and PuppetGene Gotimer
As the pace of development increases, testing has more to do and less time in which to do it. Software testing must evolve to meet delivery goals while continuing to meet quality objectives. Gene Gotimer explores how tools like Vagrant and Puppet work together to provide on-demand, disposable test environments that are delivered quickly, in a known state, with pre-populated test data and automated test fixture provisioning. With a single command, Vagrant provisions one or more virtual machines on a local box, in a private or public cloud. Puppet then takes over to install and configure software, setup test data, and get the system or systems ready for testing. Since the process is automated, anyone on the team can use the same Vagrant and Puppet scripts to get his own virtual environment for testing. When you are finished with it, Vagrant tears it back down and restores it to the same original state.
Preparation study for Docker Event
Mulodo Open Study Group (MOSG) @Ho chi minh, Vietnam
http://www.meetup.com/Open-Study-Group-Saigon/events/229781420/
Code testing and Continuous Integration are just the first step in a source code to production process. Combined with infrastructure-as-code tools such as Puppet the whole process can be automated, and tested!
Vagrant is an open source tool that allows users to create and manage virtual machine environments. It works by using a file called a Vagrantfile to configure virtual machines from templates called boxes. Vagrant provides features like provisioning, synced folders, networking, and multiple providers to automate the setup of a development environment and make it portable.
Quick & Easy Dev Environments with VagrantJoe Ferguson
Vagrant is a tool that allows users to easily create and configure virtual development environments and ensures that everyone is working with the same target environment. The document demonstrates how to install Vagrant and VirtualBox, acquire a virtual machine box, set up a basic LAMP stack environment, configure port forwarding and shared folders, and introduce some common Vagrant commands.
Vagrant - Version control your dev environmentbocribbz
Vagrant facilitates the creation and configuration of lightweight, reproducible, and portable development environments.
It is currently in use at companies like Disqus, BBC, Mozilla, Nokia, and O'Reilly Media. More information about Vagrant is available at: http://www.vagrantup.com/
Links:
Boxes: https://github.com/opscode/bento
Cookbooks: http://community.opscode.com/
LAMP demo: https://github.com/bocribbz/cookbook-lampdemo
How To Set a Vagrant Development SystemPaul Bearne
This document provides instructions on how to set up a Vagrant development environment. Vagrant allows developers to run development environments that match production by creating virtual machines. Key points:
- Vagrant uses VirtualBox to run virtual machines and configure project isolation and version control.
- The basic workflow involves initializing a Vagrantfile configuration, running "vagrant up" to launch the virtual machine, and "vagrant destroy" to wipe it out.
- Additional commands like "vagrant suspend" pause the virtual machine. The document demonstrates configuring ports, shared folders, and provisioning scripts.
- Benefits of Vagrant include no need to install web servers locally, matching production
Oracle Developers APAC Meetup #1 - Working with Wercker WorksheetsDarrel Chia
Oracle Developers APAC Meetup #1 - Working with Wercker
This is the hands-on work exercise example used for the Oracle APAC Developers Meetup #1 held in Singapore on 7th February 2018.
The worksheets are intended to be used in conjunction with the slides.
You can find the slides at :
https://www.slideshare.net/DarrelChia1/oracle-apac-developers-meetup-1-working-with-wercker-slides
Meetup Site:
https://www.meetup.com/Oracle-Developers-APAC/events/247111220/
Vagrant is a tool that allows users to create and configure lightweight, reproducible, and portable development environments. It works by allowing users to define and provision virtual development environments using configuration files. Vagrant provides users with a standardized way to manage virtual machines across different operating systems and virtualization platforms.
The document discusses using Vagrant and Puppet to create virtual machine environments for development. Vagrant allows defining and provisioning VMs through a Vagrantfile, while Puppet can further configure the VMs by installing software and configuring settings. Benefits include keeping development environments isolated, easy setup for new developers, and ability to deploy VMs to cloud providers like AWS. The key steps are downloading Vagrant and VirtualBox, defining the Vagrantfile, writing Puppet manifests, and running vagrant up to launch and provision the VM.
Setup a Dev environment that feels like $HOME on Windows 10Stefan Scherer
Windows 10 allows you to run native Linux binaries with the WSL. Let's see how we can use a good development environment for Vagrant and Docker using VMware Workstation on Enterprise notebooks.
RICS Membership-(The Royal Institution of Chartered Surveyors).pdfMohamedAbdelkader115
Glad to be one of only 14 members inside Kuwait to hold this credential.
Please check the members inside kuwait from this link:
https://www.rics.org/networking/find-a-member.html?firstname=&lastname=&town=&country=Kuwait&member_grade=(AssocRICS)&expert_witness=&accrediation=&page=1
In tube drawing process, a tube is pulled out through a die and a plug to reduce its diameter and thickness as per the requirement. Dimensional accuracy of cold drawn tubes plays a vital role in the further quality of end products and controlling rejection in manufacturing processes of these end products. Springback phenomenon is the elastic strain recovery after removal of forming loads, causes geometrical inaccuracies in drawn tubes. Further, this leads to difficulty in achieving close dimensional tolerances. In the present work springback of EN 8 D tube material is studied for various cold drawing parameters. The process parameters in this work include die semi-angle, land width and drawing speed. The experimentation is done using Taguchi’s L36 orthogonal array, and then optimization is done in data analysis software Minitab 17. The results of ANOVA shows that 15 degrees die semi-angle,5 mm land width and 6 m/min drawing speed yields least springback. Furthermore, optimization algorithms named Particle Swarm Optimization (PSO), Simulated Annealing (SA) and Genetic Algorithm (GA) are applied which shows that 15 degrees die semi-angle, 10 mm land width and 8 m/min drawing speed results in minimal springback with almost 10.5 % improvement. Finally, the results of experimentation are validated with Finite Element Analysis technique using ANSYS.
Sorting Order and Stability in Sorting.
Concept of Internal and External Sorting.
Bubble Sort,
Insertion Sort,
Selection Sort,
Quick Sort and
Merge Sort,
Radix Sort, and
Shell Sort,
External Sorting, Time complexity analysis of Sorting Algorithms.
ELectronics Boards & Product Testing_Shiju.pdfShiju Jacob
This presentation provides a high level insight about DFT analysis and test coverage calculation, finalizing test strategy, and types of tests at different levels of the product.
Raish Khanji GTU 8th sem Internship Report.pdfRaishKhanji
This report details the practical experiences gained during an internship at Indo German Tool
Room, Ahmedabad. The internship provided hands-on training in various manufacturing technologies, encompassing both conventional and advanced techniques. Significant emphasis was placed on machining processes, including operation and fundamental
understanding of lathe and milling machines. Furthermore, the internship incorporated
modern welding technology, notably through the application of an Augmented Reality (AR)
simulator, offering a safe and effective environment for skill development. Exposure to
industrial automation was achieved through practical exercises in Programmable Logic Controllers (PLCs) using Siemens TIA software and direct operation of industrial robots
utilizing teach pendants. The principles and practical aspects of Computer Numerical Control
(CNC) technology were also explored. Complementing these manufacturing processes, the
internship included extensive application of SolidWorks software for design and modeling tasks. This comprehensive practical training has provided a foundational understanding of
key aspects of modern manufacturing and design, enhancing the technical proficiency and readiness for future engineering endeavors.
Fluid mechanics is the branch of physics concerned with the mechanics of fluids (liquids, gases, and plasmas) and the forces on them. Originally applied to water (hydromechanics), it found applications in a wide range of disciplines, including mechanical, aerospace, civil, chemical, and biomedical engineering, as well as geophysics, oceanography, meteorology, astrophysics, and biology.
It can be divided into fluid statics, the study of various fluids at rest, and fluid dynamics.
Fluid statics, also known as hydrostatics, is the study of fluids at rest, specifically when there's no relative motion between fluid particles. It focuses on the conditions under which fluids are in stable equilibrium and doesn't involve fluid motion.
Fluid kinematics is the branch of fluid mechanics that focuses on describing and analyzing the motion of fluids, such as liquids and gases, without considering the forces that cause the motion. It deals with the geometrical and temporal aspects of fluid flow, including velocity and acceleration. Fluid dynamics, on the other hand, considers the forces acting on the fluid.
Fluid dynamics is the study of the effect of forces on fluid motion. It is a branch of continuum mechanics, a subject which models matter without using the information that it is made out of atoms; that is, it models matter from a macroscopic viewpoint rather than from microscopic.
Fluid mechanics, especially fluid dynamics, is an active field of research, typically mathematically complex. Many problems are partly or wholly unsolved and are best addressed by numerical methods, typically using computers. A modern discipline, called computational fluid dynamics (CFD), is devoted to this approach. Particle image velocimetry, an experimental method for visualizing and analyzing fluid flow, also takes advantage of the highly visual nature of fluid flow.
Fundamentally, every fluid mechanical system is assumed to obey the basic laws :
Conservation of mass
Conservation of energy
Conservation of momentum
The continuum assumption
For example, the assumption that mass is conserved means that for any fixed control volume (for example, a spherical volume)—enclosed by a control surface—the rate of change of the mass contained in that volume is equal to the rate at which mass is passing through the surface from outside to inside, minus the rate at which mass is passing from inside to outside. This can be expressed as an equation in integral form over the control volume.
The continuum assumption is an idealization of continuum mechanics under which fluids can be treated as continuous, even though, on a microscopic scale, they are composed of molecules. Under the continuum assumption, macroscopic (observed/measurable) properties such as density, pressure, temperature, and bulk velocity are taken to be well-defined at "infinitesimal" volume elements—small in comparison to the characteristic length scale of the system, but large in comparison to molecular length scale
☁️ GDG Cloud Munich: Build With AI Workshop - Introduction to Vertex AI! ☁️
Join us for an exciting #BuildWithAi workshop on the 28th of April, 2025 at the Google Office in Munich!
Dive into the world of AI with our "Introduction to Vertex AI" session, presented by Google Cloud expert Randy Gupta.
The role of the lexical analyzer
Specification of tokens
Finite state machines
From a regular expressions to an NFA
Convert NFA to DFA
Transforming grammars and regular expressions
Transforming automata to grammars
Language for specifying lexical analyzers
Lidar for Autonomous Driving, LiDAR Mapping for Driverless Cars.pptxRishavKumar530754
LiDAR-Based System for Autonomous Cars
Autonomous Driving with LiDAR Tech
LiDAR Integration in Self-Driving Cars
Self-Driving Vehicles Using LiDAR
LiDAR Mapping for Driverless Cars
"Boiler Feed Pump (BFP): Working, Applications, Advantages, and Limitations E...Infopitaara
A Boiler Feed Pump (BFP) is a critical component in thermal power plants. It supplies high-pressure water (feedwater) to the boiler, ensuring continuous steam generation.
⚙️ How a Boiler Feed Pump Works
Water Collection:
Feedwater is collected from the deaerator or feedwater tank.
Pressurization:
The pump increases water pressure using multiple impellers/stages in centrifugal types.
Discharge to Boiler:
Pressurized water is then supplied to the boiler drum or economizer section, depending on design.
🌀 Types of Boiler Feed Pumps
Centrifugal Pumps (most common):
Multistage for higher pressure.
Used in large thermal power stations.
Positive Displacement Pumps (less common):
For smaller or specific applications.
Precise flow control but less efficient for large volumes.
🛠️ Key Operations and Controls
Recirculation Line: Protects the pump from overheating at low flow.
Throttle Valve: Regulates flow based on boiler demand.
Control System: Often automated via DCS/PLC for variable load conditions.
Sealing & Cooling Systems: Prevent leakage and maintain pump health.
⚠️ Common BFP Issues
Cavitation due to low NPSH (Net Positive Suction Head).
Seal or bearing failure.
Overheating from improper flow or recirculation.
its all about Artificial Intelligence(Ai) and Machine Learning and not on advanced level you can study before the exam or can check for some information on Ai for project
2. Vagrant
- Vagrant will mange VM for you
- Describe VM in configuration file
- Can put configuration in Source Control
- You can allow other to contribute
- You have full control on VM
3. Vagrant
- Ruby powered command line interface to
VM hosted in your Computer
- Supports multiple VM providers
(VirtualBox by default)
- Allows to create reproducible and
portable environments
4. Vagrant
- Supports run of Multi-VM environments
- Allows to create/restore snapshots of VM
- Allows package environment
- Environment configuration stored in file
(you can put it in git)
5. Installing Vagrant
- Download and install latest VirtualBox for your OS:
https://www.virtualbox.org/wiki/Downloads
- Download and install latest vagrant for your OS:
http://www.vagrantup.com/downloads.html
- Update PATH Environment System Variable. Add entries:
- VirtualBox location
- C:Program FilesOracleVirtualBox
- Vagrant location
- C:DevOpsvagrantbin
- Might require extra directories
- C:DevOpsvagrantembeddedbin
- C:DevOpsvagrantembeddedmingwbin
- C:DevOpsvagrantembeddedgemsbin
7. Command Line Interface
Vagrant basic operating model through CLI vagrant command
Running any vagrant subcommand with --help or –h prints context help
$ vagrant init
$ vagrant up
$ vagrant halt
$ vagrant reload
$ vagrant provision
$ vagrant destroy
$ vagrant ssh
$ vagrant ssh-config
Create initial Vagrant configuratoin
Start or create VM if not exists
Power down VM
Restart VM (useful when you change config)
Run Chef or Puppet scripts
Destroy VM as it never existed
Connect to VM if it is running
Prints SSH configuration
8. Command Line Interface
shell
$ vagrant box list
$ vagrant box add
$ vagrant box remove
$ vagrant box repackage
$ vagrant box outdated
$ vagrant box update
List all vagrant environments on your PC
Add basebox record to vagrant registry
Remove basebox (doesn’t terminate VM)
Make a snapshot of your VM
Deprecates the VM
Checks and updates a VM if it is out-dated
Additional commands to manage your vagrant environments
9. Vagrantfile
All VM configuration stored in Ruby DSL file. This file can be placed in git.
When you run vagrant up. Vagrant will check following directories.
./Vagrantfile
/home/mitchellh/projects/foo/Vagrantfile
/home/mitchellh/projects/Vagrantfile
/home/mitchellh/Vagrantfile
/home/Vagrantfile
/Vagrantfile
VAGRANT_CWD to change directory where Vagrant is looking for configuration
10. Boxes
Vagrantfile
Vagrant.configure "2" do |config|
config.vm.box = “my-vm"
config.vm.box_url = “box-url"
end
Minimal Vagrantfile looks like this
Vagrant file contains API versioning.
11. Vagrantfile (cont)
Vagrantfile
Vagrant.configure "2" do |config|
config.vm.box = “my-vm"
config.vm.box_url = “box-url“
(1..3).each do |i|
config.vm.define "slave-#{i}" do |slave|
slave.vm.provision "shell",
inline: "echo hello from slave #{i}"
end
end
end
How many machines will
run this file?
12. Modifying scripts
config.vm – to mange VM parameters
Vagrantfile
config.vm.box
config.vm.check_update
config.vm.box_url
config.vm.box_version
config.vm.box.hostname
config.vm.provider
cofnig.vm.synced_folder
Name to be associated with box
By default true. Can disable update checks
URL of the VM to download
Version of the basebox file
Hostname of the VM
By default VirtualBox. Can be other
By default current host dir mounted as
/Vagrant. Can map additional directory
inside VM
13. Modifying scripts
config.ssh – to customize SSH behavior
Vagrantfile
config.ssh.username
config.ssh.password
config.ssh.private_key_path
config.ssh.insert_key
config.ssh.shell
By default vagrant
No pass by default
Path to your SSH key. By default
/home/.vagrant.d/insecure_private_key
By default true. Can disable to use pass
Shell to open when ssh. By default bash -l
14. Boxes
To create a VM Vagrant needs a basebox file which is typically
Just Enough Operating System.
Baseboxes can be downloaded from Community websites
www.vagrantbox.es Offsite for Vagrant boxes
http://opscode.github.io/bento/ Vagrant boxes optimized for Chef
You can create your own box using
- Packer (http://packer.io)
- Packer templates for Chef optimized boxes can be found:
https://github.com/opscode/bento
15. Synced Folder
To enable Vagrant to sync files at your Host and Guest machine
By default mapped directory: /vagrant
Permissions: all files in synced folder are 0777
16. Vagrant Plugins
Vagrant is extremely pluggable.
You can add/costomize almost everything in Vagrant (such as add
VMWare, AWS or Docker providers), Chef or Puppet provisioning etc.
Vagrant has tons of plugins. Official hosted here:
https://github.com/mitchellh/vagrant/tree/master/plugins
Dog Food: API for Vagrant plugins:
http://en.wikipedia.org/wiki/Eating_your_own_dog_food
Most useful Plugins:
- vagrant-omnibus: Chef for Vagrant VMs
- vagrant-cachier: Cache for packages (can be reused across VMs)
- vagrant-berkshelf: Enable Chef cookbook dependency mechanism
17. Vagrant plugins command
CLI to manage vagrant plugins.
Will be installed in /home/.vagrant.d/gems
Shell
$ vagrant plugin install
$ vagrant plugin list
$ vagrant plugin uninstall
$ vagrant plugin update
Install vagrant plugin
List of installed plugins
Erase plugin
Check plugin and update with newer version
19. Activity 1
Go to /activity1 directory
1. Create a vagrant box file:
$ vagrant init vagrant-hackaton http://opscode-vm-
bento.s3.amazonaws.com/vagrant/vmware/opscode_ubuntu-14.04_chef-
provisionerless.box
2. Run command:
This will create a Vagrant configuration which is pointed to URL.
This is a good manner to specify Valid URL so vagrant config can be
repeatable out of box
$ vagrant up
This will start download image from Internet. Please spare our bandwidth
and terminate this process (CTRL+C). We will add image from our local disk
20. Activity 1
3. Check if nothing installed
$ vagrant box list
5. Spin up VM:
Vagrant should return no images. Otherwise we might overwrite one with
this activity. Or you might want to change name of VM by modifying
Vagrantfile
4. Add box manually with link to local file
$ vagrant box add vagrant-hackaton PATH-TO-BOX/opscode_ubuntu-
14.04_chef-provisionerless.box
$ vagrant up
6. Connect via SSH
$ vagrant ssh
21. Activity 1
7. Type command
$ vagrant destroy
8. Destroy VM
in VM
$ uptime
$ exit
23. Activity 2
Go to /activity2 directory
1. Run command
$ vagrant up
This will bring VM to life. Vagrant will reuse basebox from local file because
activity2 VM has same name as VM from activty1
2. In the VM run command
You should get some HTML text on console. Before exiting SSH sesion
in VM
$ sudo apt-get install –y apache2 curl
$ http://localhost
$ exit
24. Activity 2
3. Modify Vagrantfile
This will instruct Vagrant to use cache on your Host machine all software
installed inside VM (vagrant requires plugin vagrant-cachier)
4. Modify Vagrantfile as per instructions
Vagrantfile: TODO2
config.vm.network :forwarded_port, guest: XXXXX, host: YYYYY
Vagrantfile: TODO1
config.cache.auto_detect = true
Vagrantfile: TODO3
config.vm.synced_folder "webapp/", "/var/www"
5. Modify Vagrantfile as per instructions
25. Activity 2
5. after Vagrantfile changes we need to raload VM
$ vagrant reload
6. With your browser open: http://localhost:80801
You will get something like this (on the right)
This is allright. We need to create a HTML
7. Create file webapp/index.html
webapp/index.html
<html>
<head><title>Hello World!</title><head>
<body><h1>Hello Vagrant!</h1></body
</html>
26. Activity 2
No needs to reload VM (directory will be synced automagically )
8. Refresh your browser at: http://localhost:80801
You will get something like this (on the right)
7. Destroy VM
$ vagrant destroy
28. Activity 3
Go to /activity3 directory
1. Run command
$ vagrant up
Vagrant will fail with
Vagrant:
* Unknown configuration section 'berkshelf'.
* Unknown configuration section 'omnibus'.
2. You need to install additional plugins
$ vagrant plugin install vagrant-berkshelf
$ vagrant plugin install vagrant-omnibus
$ vagrant up
29. Activity 3
Go to /activity3 directory
1. Run command
$ vagrant up
Vagrantfile has extra configuration that says it will use Chef (Omnibus
packaged) and Berkshelf to download cookbooks. But it doesn’t have plugins
and it will fail:
Vagrant:
* Unknown configuration section 'berkshelf'.
* Unknown configuration section 'omnibus'.
2. Check if plugins installed and install plugins
$ vagrant plugin list
$ vagrant plugin install vagrant-berkshelf
$ vagrant plugin install vagrant-omnibus
$ vagrant up
30. Activity 3
Go to /activity3 directory
1. Run command
$ vagrant up
Vagrantfile has extra configuration that says it will use Chef (Omnibus
packaged) and Berkshelf to download cookbooks. But it doesn’t have plugins
and it will fail:
Vagrant:
* Unknown configuration section 'berkshelf'.
* Unknown configuration section 'omnibus'.
2. Check if plugins installed and install plugins
$ vagrant plugin list
$ vagrant plugin install vagrant-berkshelf
$ vagrant plugin install vagrant-omnibus
$ vagrant up
32. How many VMs will this file run?
Vagrantfile
Vagrant.configure "2" do |config|
config.vm.box = “my-vm"
config.vm.box_url = “box-url“
(1..3).each do |i|
config.vm.define "slave-#{i}" do |slave|
slave.vm.provision "shell",
inline: "echo hello from slave #{i}"
end
end
end
33. Synced folder tricks
Vagrantfile
require 'rbconfig'
is_windows = (RbConfig::CONFIG['host_os'] =~ /mswin|mingw|cygwin/)
Vagrant.configure "2" do |config|
config.vm.box = “my-vm"
config.vm.box_url = “box-url“
config.vm.synced_folder
"webapp/",
"/var/www/html",
nfs: is_windows
end
Synced folder in windows synchronizes in one direction. To enable it to
synchronize in both directions we need to say that host system is
Windows by setting parameter nfs to true
34. Synced folder tricks
Vagrantfile
require 'rbconfig'
is_windows = (RbConfig::CONFIG['host_os'] =~ /mswin|mingw|cygwin/)
Vagrant.configure "2" do |config|
config.vm.box = “my-vm"
config.vm.box_url = “box-url“
config.vm.synced_folder
"webapp/",
"/var/www/html",
nfs: is_windows
end
Synced folder in windows synchronizes in one direction. To enable it to
synchronize in both directions we need to say that host system is
Windows by setting parameter nfs to true
35. Synced folder tricks
If Windows host machine you cannot create symlinks in synced directory
However there is a workaround.
1. Add vm customization parameter to Vagrantfile
Vagrantfile
config.vm.customize ["setextradata", :id,
"VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root", "1"] if
is_windows
2. Run vagrant up as user Administrator
36. Shell
$ git clone https://github.com/opscode/bento.git
$ cd bento/packer
bento/packer $ packer build ubuntu-13.10-amd64.json
Creating VM from scratch
37. Shell
bento/packer $ packer build
-only=virtualbox
-var-file=variables.json
ubuntu-13.10-amd64.json
Packer with extra params
variables.json
{
"chef_version": "latest",
"mirror": "../builds/iso/"
}