This document provides an overview of learning Chef infrastructure automation. It discusses that after taking the course, students will understand DevOps and Chef's role in infrastructure automation. The course teaches how to deploy and automate node configurations using recipes and cookbooks. It also covers the Chef workflow and how to use Chef to automate infrastructure deployment.
Introduction to Chef: Automate Your Infrastructure by Modeling It In CodeJosh Padnick
Presentation by Josh Padnick given at Desert Code Camp on April 5, 2014. Introduces OpsCode Chef with a special emphasis on learning the key Chef concepts. Also includes tips & tricks and references to best practices.
Introduction to Chef: Automate Your Infrastructure by Modeling It In CodeJosh Padnick
Presentation by Josh Padnick given at Desert Code Camp on April 5, 2014. Introduces OpsCode Chef with a special emphasis on learning the key Chef concepts. Also includes tips & tricks and references to best practices.
Short presentation about Docker and some usage scenarios for Web Developement, Operations and Continuous Delivery. This talk was held at the TYPO3 Camp Stuttgart in 2015.
This presentation was held at the DevOps Meetup Frankfurt on 2014/12/08. It describes some tools and practices for testing your infrastructure provisioned with Chef.
Chef Tutorial | Chef Tutorial For Beginners | DevOps Chef Tutorial | DevOps T...Simplilearn
This presentation on Chef will help you understand why Chef is needed, what is Chef, what is configuration management, infrastructure as code, components of Chef, Chef architecture & how it works, and you will also see a demo on Chef. Chef is an open source tool developed by Opscode. It is written in Ruby and Erlang. It automates the configuration and maintenance of multiple servers. Configuration management is a collection of engineering practices that provides a systematic way to manage entities for efficient deployment. These entities include code, infrastructure and people. Now let us get started and understand Chef in detail.
Below topics are explained in this Chef presentation:
1. Why Chef?
2. What is Chef?
3. Configuration management
4. Infrastructure as code
5. Components of Chef
6. Chef architecture
7. Flavors of Chef
8. Chef demo
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at: https://www.simplilearn.com/
This presentation gives a short introduction to Vagrant and Chef for automation of configuration management. You will get a first overview of the stack of technology used to set up your own Vagrant Boxes and how they help the to build reliable development environments right on your own local laptop. We will scratch topics like DevOps and Continuous Integration and how they link to Configuration Management and Chef and Vagrant.
If you like these slides, make sure to check out http://de.slideshare.net/Sebobo/continuous-delivery-with-open-source-tools as well!
Codecoon is the next generation hosting portal from the punkt.de GmbH. In this talk we explain how we implemented the portal and its components using TYPO3 Flow, Opscode Chef, Vagrant and Sinatra. We give a detailed insight in why we used which technologies and which developer itches we want to tackle.
Introduction to Chef - Techsuperwomen SummitJennifer Davis
Interested in speeding up time to production when developing an application? Want to understand how to minimize risk associated with changes? Come learn about infrastructure automation with Chef. In this beginner level workshop, I will teach you the core set of skills needed to implement Chef in your environment whether for work or personal projects. I will cover the basic architecture of Chef and the associated tools that will help you improve your application workflow from design to production.
Community Cookbooks & further resources - Fundamentals Webinar Series Part 6Chef
Part 6 of a 6 part series introducing you to the fundamentals of Chef.
This session includes an introducing Community Cookbooks and some additional resources.
After viewing this webinar you will be able to:
- Find, preview, and download cookbooks from the Chef Community site
- Use knife to work with the Community Site API
- Download, extract, examine and implement cookbooks from the Community site
Video of this webinar can be found at the following URL
https://www.youtube.com/watch?v=ovTIeS3kx4g&list=PL11cZfNdwNyPnZA9D1MbVqldGuOWqbumZ
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20Michael Lihs
Presentation about open source tools to set up continuous integration and continuous deployment. Covers Git, Gitlab, Chef, Vagrant, Jenkins, Gatling, Dashing, TYPO3 Surf and some other tools. Shows some best practices for testing with Behat and Functional Testing.
At Rackspace, sysadmins have taken responsiblilty for what was a "developers problem" only a few years ago. What started as a way to solve an image build problem turned into a socially collaborative DevOps community. Come see what Chef started.
When most people talk about automating infrastructure, they focus on things like consistency, scalability, and flexibility. While fine goals, we recently converted several projects to Chef for both systems AND application deployment, and found that, with a little work, these tools could also help you enable better software quality assurance, load modeling, and even improve resource allocation.
By sharing cookbooks across projects, we were able to standardize practices and eliminate arbitrary differences, while using parameterization to perfectly isolate the special needs of each project. This allowed us to transfer knowledge among staff much more quickly. Pulling in and parameterizing application state – database contents, website assets, uploaded content – allowed us to spin up new environments with as much or as little state as needed. Integrating with Vagrant and Jenkins, we were then able to use chef to treat the entire image – system and application – as a test fixture. As each engineer (ops or dev) has visibility into the whole stack, we can more easily move people between dev and ops, or 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.
EC2 AMI Factory with Chef, Berkshelf, and PackerGeorge Miranda
Presentation accompanying a Live Demo at the AWS Pop-Up Loft in San Francisco on using Chef + Berks + Packer to create an AWS EC2 AMI Factory.
Demo Repo available here -- https://github.com/gmiranda23/chef-ami-factory
Short presentation about Docker and some usage scenarios for Web Developement, Operations and Continuous Delivery. This talk was held at the TYPO3 Camp Stuttgart in 2015.
This presentation was held at the DevOps Meetup Frankfurt on 2014/12/08. It describes some tools and practices for testing your infrastructure provisioned with Chef.
Chef Tutorial | Chef Tutorial For Beginners | DevOps Chef Tutorial | DevOps T...Simplilearn
This presentation on Chef will help you understand why Chef is needed, what is Chef, what is configuration management, infrastructure as code, components of Chef, Chef architecture & how it works, and you will also see a demo on Chef. Chef is an open source tool developed by Opscode. It is written in Ruby and Erlang. It automates the configuration and maintenance of multiple servers. Configuration management is a collection of engineering practices that provides a systematic way to manage entities for efficient deployment. These entities include code, infrastructure and people. Now let us get started and understand Chef in detail.
Below topics are explained in this Chef presentation:
1. Why Chef?
2. What is Chef?
3. Configuration management
4. Infrastructure as code
5. Components of Chef
6. Chef architecture
7. Flavors of Chef
8. Chef demo
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at: https://www.simplilearn.com/
This presentation gives a short introduction to Vagrant and Chef for automation of configuration management. You will get a first overview of the stack of technology used to set up your own Vagrant Boxes and how they help the to build reliable development environments right on your own local laptop. We will scratch topics like DevOps and Continuous Integration and how they link to Configuration Management and Chef and Vagrant.
If you like these slides, make sure to check out http://de.slideshare.net/Sebobo/continuous-delivery-with-open-source-tools as well!
Codecoon is the next generation hosting portal from the punkt.de GmbH. In this talk we explain how we implemented the portal and its components using TYPO3 Flow, Opscode Chef, Vagrant and Sinatra. We give a detailed insight in why we used which technologies and which developer itches we want to tackle.
Introduction to Chef - Techsuperwomen SummitJennifer Davis
Interested in speeding up time to production when developing an application? Want to understand how to minimize risk associated with changes? Come learn about infrastructure automation with Chef. In this beginner level workshop, I will teach you the core set of skills needed to implement Chef in your environment whether for work or personal projects. I will cover the basic architecture of Chef and the associated tools that will help you improve your application workflow from design to production.
Community Cookbooks & further resources - Fundamentals Webinar Series Part 6Chef
Part 6 of a 6 part series introducing you to the fundamentals of Chef.
This session includes an introducing Community Cookbooks and some additional resources.
After viewing this webinar you will be able to:
- Find, preview, and download cookbooks from the Chef Community site
- Use knife to work with the Community Site API
- Download, extract, examine and implement cookbooks from the Community site
Video of this webinar can be found at the following URL
https://www.youtube.com/watch?v=ovTIeS3kx4g&list=PL11cZfNdwNyPnZA9D1MbVqldGuOWqbumZ
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20Michael Lihs
Presentation about open source tools to set up continuous integration and continuous deployment. Covers Git, Gitlab, Chef, Vagrant, Jenkins, Gatling, Dashing, TYPO3 Surf and some other tools. Shows some best practices for testing with Behat and Functional Testing.
At Rackspace, sysadmins have taken responsiblilty for what was a "developers problem" only a few years ago. What started as a way to solve an image build problem turned into a socially collaborative DevOps community. Come see what Chef started.
When most people talk about automating infrastructure, they focus on things like consistency, scalability, and flexibility. While fine goals, we recently converted several projects to Chef for both systems AND application deployment, and found that, with a little work, these tools could also help you enable better software quality assurance, load modeling, and even improve resource allocation.
By sharing cookbooks across projects, we were able to standardize practices and eliminate arbitrary differences, while using parameterization to perfectly isolate the special needs of each project. This allowed us to transfer knowledge among staff much more quickly. Pulling in and parameterizing application state – database contents, website assets, uploaded content – allowed us to spin up new environments with as much or as little state as needed. Integrating with Vagrant and Jenkins, we were then able to use chef to treat the entire image – system and application – as a test fixture. As each engineer (ops or dev) has visibility into the whole stack, we can more easily move people between dev and ops, or 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.
EC2 AMI Factory with Chef, Berkshelf, and PackerGeorge Miranda
Presentation accompanying a Live Demo at the AWS Pop-Up Loft in San Francisco on using Chef + Berks + Packer to create an AWS EC2 AMI Factory.
Demo Repo available here -- https://github.com/gmiranda23/chef-ami-factory
CIRCUIT 2015 - AEM Infrastructure Automation with Chef CookbooksICF CIRCUIT
Drew Glass - Hero Digital
Push button deployments can automate AEM infrastructure to reduce costs and defects. Chef is a platform that enables this by transforming infrastructure into code using DevOps practices. AEM Author, Publish and Dispatcher instances can be fully configured and deployed as code with Chef. In this talk we will discuss how the open source AEM Chef Cookbook can be used to automate the deployment of AEM instances with Chef features like recipes, attributes, providers and resources. Out of the box, the AEM Chef Cookbook supports:
- Unattended installation of AEM Author, Publish, and Dispatcher nodes.
- Automatic search for and configuration of AEM cluster members using Chef searches.
- Configuration for replication agents using the replicator provider.
- Configurations for Dispatcher farms with the farm provider.
- Deploying and removing AEM packages with the package provider.
We will also discuss how AEM can be automated to supported different SSO and deployment scenarios like cold standby. Finally, we will cover how to extend the Cookbook to support your project specific needs.
This slide deck Introduces Chef and its role in DevOps. The agenda of the deck is as follows:
- A Review of DevOps
- BMs Continuous Delivery solution
- Introduction to Chef
- Chef and Continuous Delivery
Read more on DevOps: http://sdarchitect.wordpress.com/understanding-devops/
(DVO314) USA Today Uses Chef & AWS for Infrastructure StandardizationAmazon Web Services
What happens when you move from using a large, unstructured Amazon EC2 pool to an automated, secure, and auditable cloud computing strategy? Learn how Gannett went from a chaotic pool of hand-crafted Heroku instances to a culture of automation and continuous delivery with Chef. By creating a DevOps team, Gannett empowered developers to automate the full stack, monitor comprehensively, and deploy code frequently. Hear how this approach allows the entire team (Security, Finance, IT, Engineering) to buy into creating the ability to push deployments whenever necessary.
AWS re:Invent 2016: Hybrid Architectures: Bridging the Gap to the Cloud( ARC2...Amazon Web Services
AWS provides many services to assist customers with their journey to the cloud. Hybrid solutions offer customers a way to continue leveraging existing investments on-premises, while expanding their footprint into the public cloud. This session covers the different technologies available to support hybrid architectures on AWS. We discuss common patterns and anti-patterns for solving enterprise workloads across a hybrid environment.
AWS re:Invent 2016: Getting Started with the Hybrid Cloud: Enterprise Backup ...Amazon Web Services
This sessions is for architects and storage admins seeking simple and non-disruptive ways to adopt cloud platforms in their organizations. You will learn how to deliver lower costs and greater scale with nearly seamless integration into your existing Backup ad Recovery processes to achieve fast, simple wins that demonstrate the scale and flexibility of cloud services for storage. Services mentioned: S3, Glacier, Snowball, 3rd party partners, Storage Gateway, and cloud data migration services.
Are you still using FTP to deploy your code? Are you still manually performing the same steps of deploying a feature, again and again? How many hours have you spent on ssh-ing into the server, pulling the repo, migrating the database, reloading the web server and so on, for each deployment?? Ever wondered if there is a process as simple as a single click to perform all these steps for you?
Automated Deployment does exactly these things for you. It takes the burden of remembering all the steps required in each deployment process and execute it smoothly.
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.
AWS re:Invent 2016: Hybrid Architecture Design: Connecting Your On-Premises W...Amazon Web Services
You’re trying to minimize your time to deploy applications, reduce capital expenditure, and take advantage of the economies of scale made possible by using Amazon Web Services; however, you have existing on-premises applications that are not quite ready for complete migration. Hybrid architecture design can help! In this session, we discuss the fundamentals that any architect needs to consider when building a hybrid design from the ground up. Attendees get exposure to Amazon VPC, VPNs, Amazon Direct Connect, on-premises routing and connectivity, application discovery and definition, and how to tie all of these components together into a successful hybrid architecture.
Vagrant is an excellent tool for quickly setup a development environment in a reproducible manner. However it is also a DecOps tool. In this talk the idea is to introduce audience how they can use Vagrant for DevOps
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
Understand benefits and pain points of cloud, local and vagrant based development
Describe a development flow that combines vagrant and AWS to create a:
consistent environments for all developers
consistent environment from development to production
help organizations move fast – if they are not already doing this
integrate nearly flawlessly with AWS
Ease Development <-> Production Software Deployment
Ansible 2.0 - How to use Ansible to automate your applications in AWS.Idan Tohami
- How to use Ansible to automate your applications in AWS.
- What is Ansible and why is it different?
- How to control cloud deployments securely
- How to control AWS resources using dynamic inventory and tags.
AWS CloudFormation is a comprehensive templating language that enables you to create managed 'stacks' of AWS resources, with a growing library of templates available for you to use. But how do you create one from scratch? This presentation will take you through building an AWS CloudFormation template from the ground up, so you can see all the essential template constructs in action.
Watch a recording of the webinar based on this presentation on YouTube here: http://youtu.be/6R44BADNJA8
Check out other upcoming webinars in the Masterclass Series here: http://aws.amazon.com/campaigns/emea/masterclass/
CI/CD on AWS: Deploy Everything All the Time | AWS Public Sector Summit 2016Amazon Web Services
Why does DevOps matter? How can you use continuous integration to build your product faster, make it more highly available, and be able to recover from bugs quickly? Let one of our solutions architects walk you through continuous integration and continuous delivery on AWS. This session includes live demos of our tools AWS CodeCommit, AWS CodePipeline, and AWS CodeDeploy.
The guide helps you understand how Chef works. It will also demonstrate about the primary usage and getting started with installing Chef-Solo over your workstations.
However, it will also help you to figure out how to configure Chef Server, Knife and Chef-Client at your stack making it possible to let them all communicate together.
AWS re:Invent 2016: Configuration Management in the Cloud (DEV305)Amazon Web Services
To ensure that your application operates in a predictable manner in both your test and production environments, you must vigilantly maintain the configuration of your resources. By leveraging configuration management solutions, Dev and Ops engineers can define the state of their resources across their entire lifecycle. In this session, we will show you how to use AWS OpsWorks, AWS CodeDeploy, and AWS CodePipeline to build a reliable and consistent development pipeline that assures your production workloads behave in a predictable manner.
Configuration Management with AWS OpsWorks for Chef AutomateAmazon Web Services
AWS OpsWorks for Chef Automate provides a fully managed Chef server and suite of automation tools that give you workflow automation for continuous deployment, automated testing for compliance and security, and a user interface that gives you visibility into your nodes and their status. The Chef server gives you full stack automation by handling operational tasks such as software and operating system configurations, package installations, database setups, and more. The Chef server centrally stores your configuration tasks and provides them to each node in your compute environment at any scale, from a few nodes to thousands of nodes. OpsWorks for Chef Automate is completely compatible with tooling and cookbooks from the Chef community and automatically registers new nodes with your Chef server.
Announcing AWS OpsWorks for Chef Automate - January 2017 AWS Online Tech TalksAmazon Web Services
AWS OpsWorks for Chef Automate provides a fully managed Chef server and suite of automation tools that give you workflow automation for continuous deployment, automated testing for compliance and security, and a user interface that gives you visibility into your nodes and their status.
Learning Objectives:
• Learn about the capabilities, features and benefits of AWS OpsWorks for Chef Automate
• Learn how you can automate configuration management using AWS OpsWorks for Chef Automate
• Learn how to get started using AWS OpsWorks for Chef Automate
chef is an automation tool that describe your infrastructure with code. The purpose of cookbook is automation the system configuration. Cookbook created on the workstation and uploaded to the chef server. Then testing the cookbook by using opennebula. Test kitchen is test hardness tool o execute your configured code on one or more platforms in isolation. Then install the test kitchen and opennebula driver.finally run the cookbook.
Introduction To Continuous Compliance & RemediationNicole Johnson
Success with DevOps can be measured with a number of different metrics. How frequently are systems audited for compliance to various policies? How long does it take to remediate a failing control or vulnerability? This workshop provide an introduction to practice of continuous compliance and remediation. The workshop uses InSpec and Chef for compliance and remediation, respectively. InSpec is an open-source testing framework for infrastructure with a human-readable language for specifying compliance, security and other policy requirements. Chef is an open-source framework for infrastructure automation. Easily integrate automated tests that check for adherence to policy into any stage of your deployment pipeline.
During this session, participants will:
Run InSpec locally on a machine
Run InSpec on a remote machine
Use InSpec in the Chef cookbook development process for integration testing
By the end of this class participants will be able to:
Execute an InSpec test on a local machine
Execute an InSpec test on a remote machine
Generate an InSpec profile
Add InSpec-based integration test to a Chef cookbook
Run InSpec-based integrations tests during Chef cookbook development
Prerequisites
Participants should bring a wifi-enabled laptop to the workshop. Participants will be given a remote workstation with all prerequisites installed. The only thing required to access these workstations will be an SSH client (PuTTY on Windows) and familiarity with a interactive text editor (Vi/Vim, Emacs, or Nano).
It’s best that participants of this workshop have some familiarity and comfort with the following:
Writing code (of just about any flavor) in a text editor
Working on the command line
Basic system administration – installing packages, configuring those packages, starting service
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...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.
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.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
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!
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
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.
2. Learning Chef
A#er
this
course
you
will
be
able
to:
§ Understand
DevOps
and
what
Chef
is
§ Know
the
role
of
worksta>ons,
nodes,
and
Chef
server
§ Deploy
and
automate
configura>ons
of
nodes
§ Understanding
of
wri>ng
Recipes
and
Cookbooks
§ Understand
the
Chef
work
flow
§ Use
Chef
to
automate
the
deployment
your
infrastructure
3. Learning Chef
How
this
course
is
laid
out:
§ Will
learn
Chef
by
working
with
single
nodes
to
start
§ Learning
to
build
cookbooks
will
follow
a
theme
such
as
installing
LAMP
§ Addi>onal
exercises
will
be
found
at
the
end
of
the
course
§ Need
access
to
LinuxAcademy.com
lab
servers
or
your
own
VM
environment
§ VirtualBox
§ VMWare
worksta>on
§ Parallels
§ Have
at
least
one
“node”
(server)
available
to
connect
to
4. Learning Chef
How
this
course
is
laid
out:
§ Will
learn
Chef
by
working
with
single
nodes
to
start
§ Need
access
to
LinuxAcademy.com
lab
servers
or
your
own
VM
environment
§ VirtualBox
§ VMWare
worksta>on
§ Parallels
§ Have
at
least
one
“node”
(server)
available
to
connect
to
6. Learning Chef
What
is
DevOps?
§ DevOps
is
about
“How
well
people
work
together
and
how
streamlined
our
Opera6ons
really
are”
–
Adam
Jacob
§ The
applica>on
and
infrastructure
that
runs
on
it
are
not
treated
as
separate
en>>es
to
each
other
and
neither
are
the
teams
that
manage
each
§ DevOps
is
part
of
con>nuous
delivery
where
all
aspects
of
the
deployment
process
are
automated
§ DevOps
is
infrastructure
as
code
8. Learning Chef
What
is
Chef?
“Chef
turns
infrastructure
into
code.
With
Chef,
you
can
automate
how
you
build,
deploy,
and
manage
your
infrastructure.
Your
infrastructure
becomes
as
versionable,
testable,
and
repeatable
as
applica6on
code.
Chef
relies
on
reusable
defini6ons
known
as
recipes
to
automate
infrastructure
tasks.
Examples
of
recipes
are
instruc6ons
for
configuring
web
servers,
databases
and
load
balancers.
Together,
recipes
describe
what
your
infrastructure
consists
of
and
how
each
part
of
your
infrastructure
should
be
deployed,
configured
and
managed.”
Getchef.com
9. Learning Chef
What
is
Chef?
§ Recipes
are
created
using
the
Ruby
language
and
while
learning
Chef
we
will
learn
a
lot
of
the
Ruby
language
§ Recipes
rely
primarily
on
resources,
resources
described
a
desired
state
of
an
element
in
the
infrastructure.
§ Packages
to
be
installed
§ Files
to
be
created
§ Directories
to
be
created
§ Services
to
be
started
§ Config
files
to
be
updated
§ Commands
to
be
executed
§ Essen>ally
anything
we
need
to
do
on
our
Linux
nodes
10. Learning Chef
What
is
Chef?
§ Chef
relies
on
either
OpenSource
Chef
server
or
Chef
enterprise
to
host
configura>on
recipes,
cookbooks,
and
node
authen>ca>on
for
your
infrastructure
§ Nodes
when
performing
a
convergence
will
check
in
with
the
Chef
server,
download
the
required
configura>on,
then
execu>on
the
recipe
instruc>ons
13. Learning Chef
Common
Chef
Terminology
Recipes:
Fundamental
configura>on
element
within
an
organiza>on
Cookbook:
Defines
a
scenario
and
is
the
fundamental
unit
of
configura>on
and
policy
distribu>on
Chef-‐Client:
Agent
that
runs
locally
on
the
node
that
is
registered
with
the
chef
server
Convergence:
Occurs
when
chef-‐client
configures
the
system/node
based
off
the
informa>on
collected
from
chef-‐
server
Configura9on
Dri;:
Occurs
when
the
node
state
does
not
reflect
the
updated
state
of
polices/configura>ons
on
the
chef
server
Resources:
A
statement
of
configura>on
policy
within
a
recipe
Describes
the
desired
state
of
an
element
in
the
infrastructure
and
steps
needed
to
configure
14. Learning Chef
Common
Chef
Terminology
Provider:
Defines
the
steps
that
are
needed
to
bring
the
piece
of
the
system
from
its
current
state
to
the
desired
state
A?ributes:
Specific
details
about
the
node,
used
by
chef-‐client
to
understand
current
state
of
the
node,
the
state
of
the
node
on
the
previous
chef-‐client
run,
and
the
state
of
the
node
at
the
end
of
the
client
run
Data-‐bags:
A
global
variables
stored
as
JSON
data
and
is
accessible
from
the
Chef
server
Worksta9on:
A
computer
configured
with
Knife
and
used
to
synchronize
with
chef-‐repo
and
interact
with
chef
server
Chef
Server:
Chef
server
is
the
hub
for
all
configura>on
data,
stores
cookbooks,
and
the
policies
applied
to
the
node
Knife:
Command
line
tool
which
provides
an
interface
between
the
local
chef-‐repo
and
chef-‐server
client.rb:
Configura>on
file
for
chef-‐client
located
at
/etc/chef/client.rb
on
each
node
Ohai:
Tool
used
to
detect
a_ributes
on
a
node
and
then
provide
a_ributes
to
chef-‐client
at
the
start
of
every
chef-‐client
run
15. Learning Chef
Common
Chef
Terminology
Node
Object:
Consists
of
run-‐list
and
node
a_ributes
that
describe
states
of
the
node
Chef-‐Repo:
Located
on
the
worksta>on
and
installed
with
the
starter
kit,
should
be
synchronized
with
a
version
control
system
and
stores
Cookbooks,
roles,
data
bags,
environments,
and
configura>on
files
Organiza9on:
Used
in
chef
enterprise
server
to
restrict
access
to
objects,
nodes
environments,
roles,
data-‐bags
etc
Environments:
Used
to
organize
environments
(Prod/Staging/Dev/QA)
generally
used
with
cookbook
versions
Idempotence:
Means
a
recipe
can
run
mul>ple
>mes
on
the
same
system
and
the
results
will
always
be
iden>cal
17. Learning Chef
Chef
Server
Two
types
of
Chef-‐server:
1. OpenSource
Chef-‐server
§ Free
version
of
Chef
§ Each
instance
of
the
server
must
be
configured
and
managed
locally
(includes
all
aspects
of
managing
the
server,
updates,
migra>ons,
scalability,
etc.
2. Chef-‐server
enterprise
(hosted)
§ Scalable
by
design
§ Available
organiza>ons
§ Always
available
§ Resource-‐based
access
control
3. Chef-‐server
enterprise
(on-‐premise)
§ Scalable
by
design
§ Available
organiza>ons
§ Hosted
on-‐premise
behind
your
firewall
§ Managed
yourself
18. Learning Chef
Chef
Server:
Enterprise
§ Allows
crea>on
of
organiza>ons
§ Organiza>ons
separate
the
infrastructure,
policies,
and
cookbooks
§ Nodes
are
registered
in
organiza>ons
§ Nothing
can
be
shared
between
organiza>ons
§ Enterprise
chef
server
can
contain
many
different
organiza>ons
§ OpenSource
chef
the
local
individual
server
acts
as
an
organiza>on
and
does
not
allow
crea>on
of
organiza>ons
§ Organiza>ons
can
represent
different
companies,
department,
infrastructures,
applica>ons,
and
so
forth
§ For
each
organiza>on
in
order
to
start
bootstrapping
nodes
you
need
to
download
the
starter
kit
§ Starter
kit
provides
security
creden>als
(valida>on.pem
keys)
to
authen>cate
each
node
to
the
chef
server
§ Chef
enterprise
scales
by
design
to
handle
thousands
of
nodes
and
different
organiza>ons
19. Learning Chef
Chef
Server:
Role
of
the
server
§ Stores
system
configura>on
informa>on
(policies
for
nodes)
§ Authen>cates
worksta>ons
and
nodes
§ Delivers
configura>ons
to
nodes
§ Chef
server
holds
the
configura>on
and
the
node
checks-‐in
to
receive
instruc>ons
on
its
desired
state
§ The
node
downloads
configura>on
instruc>ons
from
the
server
and
does
all
of
the
work
21. Learning Chef
Chef
Worksta>on
§ Developing
cookbooks
and
recipes
§ Synchronizing
chef-‐repo
with
git/svn
(source
control)
§ Using
knife
to
upload
and
manage
node
and
chef
server
configura>ons
and
policies
§ Organiza>ons
§ Nodes
§ Environments
§ Data
bags
22. Learning Chef
Chef
Worksta>on:
Organiza>on
Starter
Kit
§ Each
organiza>on
has
a
starter
kit
which
provides
the
chef-‐repo
as
well
as
security
creden>als
for
communica>ng
with
the
server
§ Knife.rb
configura>on
file
is
located
in
the
chef-‐repo
(starter
kit)
§ Starter
kit
can
be
re-‐downloaded
from
the
chef-‐server
23. Learning Chef
Chef
Worksta>on:
Organiza>on
Starter
Kit
§ Each
>me
you
download
a
new
starter
kit
the
security
keys
for
that
repo
to
the
server
are
reset
§
As
a
result
you
have
to
redistribute
the
security
keys
to
other
team
members
if
a
new
starter
kit
for
the
organiza>on
is
downloaded
§ During
bootstrap
oragniza>on-‐validator.pem
is
copied
to
the
node
as
valida>on.pem
§ During
the
first
chef-‐client
run
the
valida>on.pem
signs
the
client.pem
key
which
is
used
to
authen>cate
the
node
against
the
chef
server
24. Learning Chef
Chef
Worksta>on:
Organiza>on
Starter
Kit
§ Security
considera>ons
for
valida>on.pem
§ It
should
be
removed
first
when
the
chef-‐client
convergence
runs
§ If
chef-‐client
locks
then
key
is
located
on
node
if
node
is
compromised
then
your
en>re
infrastructure
is
§ Chef-‐client
(super
market
cookbook)
provides
this
func>onality
§ Can
always
write
your
own
recipe
to
remove
valida>on.pem
and
run
it
first
in
the
run_list
§ file
"/etc/chef/valida>on.pem"
do
§
ac>on
:delete
§ End
25. Learning Chef
Chef
Worksta>on:
Knife
Knife
is
the
command
line
tool
used
to
provide
an
interface
between
your
local
chef-‐repo
and
the
chef-‐server
§ Crea>ng
cookbooks
§ Uploading
cookbooks
to
chef
server
§ Managing
roles
and
run_lists
§ Searching
chef-‐server
node
object
data
§ Bootstrapping
nodes
§ Essen>ally
everything
we
need
to
do
as
a
DevOps
admin
26. Learning Chef
Chef
Worksta>on:
Knife
Chef
and
knife
interface
can
be
installed
to
OSX
and
Linux:
curl
–L
h_ps://www.opscode.com/chef/install.sh
|
sudo
bash
Download
and
install
Chef
manually
for
windows:
h_p://www.getchef.com/chef/install/
This
course
will
use
a
Linux
CentOS
6.5
Image
as
the
worksta>on
27. Learning Chef
Chef
Worksta>on:
Knife
configura>on
file
(knife.rb)
§ Is
found
inside
the
chef-‐repo
which
is
available
inside
the
starter
kit
of
an
organiza>on
§ Configure
proxy
selngs
here
if
worksta>on
is
behind
a
proxy
28. Learning Chef
Chef
Worksta>on:
Using
knife
to
bootstrap
a
node
Bootstrapping
connects
the
worksta>on
to
the
node
to
install:
§ Installs
knife
§ Ohai:
Used
to
detect
a_ributes
on
a
node
and
report
them
to
chef-‐client
at
the
start
of
every
client
run
it
is
required
for
chef-‐client
to
work
and
it
builds
the
node
object
§ Ruby
§ Chef-‐client
§ A
few
other
addi>onal
items
29. Learning Chef
Chef
Worksta>on:
Using
knife
to
bootstrap
a
node
Knife
bootstrap
<address>
-‐x
user
–P
password
–N
nodename
§ For
star>ng
in
this
course
we
will
define
a
node
name
§ In
produc>on
it
is
best
prac>ce
not
to
define
–N
and
let
the
FQDN
work
as
the
node
name
Note:
For
linuxacademy.com
lab
servers
when
bootstrapping
use
your
public
hostname
31. Learning Chef
Chef
Server
&
Nodes
A
node
can
be
anything
that
can
run
the
chef-‐client
agent
• Smart
phones
• Switches
• APIs
• FreeBSD
servers
• Unix
Servers
• Windows
Servers
• Linux
Servers
• Etc.
32. Learning Chef
Chef
Server
&
Nodes
Chef
server
stores
all
policy
and
configura>on
informa>on
for
nodes
The
node
uses
the
client.pem
file
(created
by
validator.pem)
during
the
chef-‐
client
run
in
order
to
authen>cate
against
the
chef
server
Chef-‐client
run:
• Authen>cate
against
the
chef-‐server
using
client.pem
• Builds
the
node
object
and
runs
ohai
• Syncronizes
with
the
chef-‐server
(sends
node
object
informa>on
and
receives
cookbooks/policies)
• Executes/compiles
the
desired
policies
• Runs
the
node
object
• Completes
34. Learning Chef
Chef
Configura>on
Concepts
Policy:
§ A
collec>on
of
system
configura>ons
that
you
define
(roles/data
bags/
environments)
§ The
policy
states
the
state
that
each
resources
should
be
in
but
not
how
to
get
there
§ Chef-‐client
will
pull
the
policy
and
configure
the
node
so
that
it
matches
the
state
of
the
policy
§ Policy
concept
examples:
§ If
it
should
be
installed
§ If
it
is
not
installed
then
install
it
§ If
it
is
already
installed
then
do
nothing
§ A
file
should
exist
if
not
create
it
§ If
a
file
exists
but
does
not
have
correct
content
35. Learning Chef
Chef
Configura>on
Concepts
Resources:
Defines
the
desired
state
for
a
single
configura9on
item
present
on
a
node
that
is
under
management
by
Chef
§ Does
the
configura>on
on
a
node
and
maps
to
providers
§ Recipes
are
stored
in
cookbooks
§ Represent
a
piece
of
the
system
and
its
desired
state
§ Building
blocks
of
Chef
configura>on
§ When
chef-‐client
is
run
on
a
node
the
resource
is
executed
by
the
provider
which
is
handled
by
Chef
and
the
OS
itself
§ Informa>on
as
to
what
provider
to
use
(ie
what
package
manager
to
use)
is
populated
when
ohai
is
run
at
the
start
of
each
chef-‐client
run
36. Learning Chef
Chef
Configura>on
Concepts
Most
common
resources
in
configura>on
management
Package:
Used
to
manage
packages
such
as
installing
a
required
package
Template:
Used
to
manage
the
contents
of
a
Ruby
template
in
the
cookbook
Service:
Manage
system
services
What
run-‐levels
to
start
the
service
in
Current
state
of
the
service
(running/stopped/etc)
37. Learning Chef
Chef-‐client
nodes
concepts
§ Nodes
can
be
configured
to
automa>cally
running
chef-‐client
in
intervals
§ When
convergence
occurs
the
node
can
put
itself
back
into
compliance
(desired
state
and
how
to
get
there)
§ Chef
server
does
not
know
the
status
of
a
node
un>l
a
convergence
is
run
§ Something
could
happen
to
cause
the
node
to
get
out
of
compliance
but
a
convergence
will
check
policies/configura>on
and
put
the
node
back
into
compliance
based
off
your
defined
configura>ons
38. Learning Chef
Key
concepts:
Recipes
are
made
up
of
a
collec>on
of
resources
Cookbooks
are
made
up
of
a
collec>on
of
recipes
Nodes
receive
their
policy
based
off
of
roles
and
individual
node
configura>ons
A
run
list
defines
the
order
in
which
you
want
your
recipes
to
run
during
convergence
Configura>on
dri#
occurs
when
the
desired
state
of
the
node
does
not
match
the
desired
state
as
defined
in
the
policies
on
the
chef
server
Configura>on
dri#
can
be
resolved
by
automa>ng/running
the
chef-‐client
agent
40. Learning Chef
Key
concepts:
A_ributes
are
specific
details
about
a
node
A_ributes
describe:
• The
current
state
of
the
node
• What
the
sate
of
the
node
was
at
the
end
of
the
previous
chef-‐client
run
• What
the
state
of
the
node
should
be
at
the
end
of
the
current
chef-‐client
run
A_ributes
can
be
defined
by:
• The
state
of
the
node
(ohai)
• Cookbooks
(Our
a_ribute
files)
• Roles
• Environments
41. Learning Chef
A_ribute
Precedence
A#er
the
node
object
is
rebuilt
in
the
chef
run,
all
a_ributes
loaded
in
the
chef-‐client
are
then
compared.
The
node
is
updated
based
on
a_ribute
precedence
and
at
the
very
end
of
the
convergence
(chef-‐client)
the
node
object
is
uploaded
to
the
chef
server
Node
object
defines
the
current
state
of
the
node
(made
up
of
a_ributes)
Node
object
is
stored
on
the
chef
server
so
that
it
can
be
searched
Node
object
is
updated
at
each
convergence
If
there
are
a_ributes
with
the
same
names
then
a_ribute
precedence
determines
which
a_ribute
is
applied
to
the
node
and
the
node
object.
42. Learning Chef
A_ribute
Precedence:
Levels
of
precedence
default:
Automa>cally
reset
at
the
start
of
every
chef
client
run
is
the
lowest
level
of
precedence
force_default:
Used
in
a
cookbook
or
recipe
to
override
an
exis>ng
“default”
a_ribute
Normal:
A
selng
that
persists
in
the
node
object
Override:
Automa>cally
reset
at
the
start
of
every
chef-‐client
most
o#en
should
be
used
only
when
required
force_override:
used
to
ensure
that
an
a_ribute
defined
in
a
cookbook
(by
an
a_ribute
file
or
by
a
recipe)
takes
precedence
over
an
override
a_ribute
set
by
a
role
or
an
environment
Automa9c:
Contains
data
populated
by
Ohai
at
the
beginning
of
every
chef-‐client
run
and
cannot
be
modified
and
always
has
the
highest
a_ribute
precedence
43. Learning Chef
A_ribute
Precedence:
Levels
of
precedence
45. Learning Chef
Node
Object
Node
object
is
made
up
of
the
run
lists
which
define
what
recipes
to
run
during
a
chef-‐client
as
well
as
the
aMributes
that
define
informa6on
about
the
node
A_ributes
are
built
during
the
chef-‐client
run
process:
§ Data
about
the
node
is
collected
by
Ohai
§ The
node
object
previously
saved
during
the
last
chef-‐client
run
§ The
rebuilt
node
object
from
the
current
chef-‐client
run
Once
the
node
object
is
rebuilt
all
a_ributes
are
compared
and
then
updated
based
on
a_ribute
precedence
At
the
end
of
every
chef-‐client
run
the
node
object
that
defines
the
current
state
of
the
node
is
uploaded
to
the
chef
server
to
be
searched.
47. Learning Chef
Environments:
What
are
environments?
“An
environment
is
a
way
to
map
an
organiza6ons
real-‐life
workflow
to
what
can
be
configured
and
managed
using
the
Chef
server”
Apply
different
cookbook
versions
to
specific
environments
(dev/prod/staging/qa/)
Define
Environment
level
a_ributes
Environments
allow
sharing
of
cookbooks
within
an
organiza>on
48. Learning Chef
Environments:
Crea>ng
environments
• Environment
informa>on
can
be
stored
in
JSON
files
or
.rb
files
• Environments
will
be
located
in
chef-‐repo/environments
• Example
dev.rb
(development
environment
file)
name
"dev"
descrip>on
”Development
environment”
cookbook
"security",
"=
0.1.0”
cookbook
”motd",
"=
0.2.0"
cookbook
"apache",
"=
0.2.0"
override_a_ributes({
“author"
=>
{
“name"
=>
true
}
})
49. Learning Chef
Environments:
A_ributes
Two
types
of
a_ribute
precedence
can
be
set
on
the
environment
level
• default
a
default
a_ribute
defined
in
the
environment
will
take
precedence
over
a
default
a_ribute
defined
in
a
cookbook
a_ribute
file.
• Override
has
higher
precedence
than
default,
force_default,
and
normal
50. Learning Chef
Environments:
Methods
of
assigning
a
node
to
an
environment
• Modify
the
client.rb
file
with
an
environment
variable
• Knife-‐flip
to
do
it
from
the
worksta>on
• Assign
it
manually
on
the
node
51. Learning Chef
Environments:
Lab
goals
ü Configure
two
environments:
Dev/Produc>on
ü Modify
Apache
cookbooks
with
newer
versions
ü Set
newer
versions
to
dev
and
older
versions
to
produc>on
ü Configure
Client.rb
to
look
at
proper
environment
53. Learning Chef
Search:
Chef
search
allows
queries
to
be
made
for
any
type
of
data
that
is
indexed
by
the
chef
server.
Search
queries
the
chef
server
for
stored
informa6on.
Can
Search:
§ Data
bags
§ Environments
§ Roles
§ Nodes
54. Learning Chef
Search:
Methods
of
search
Search
with
Knife:
Syntax:
knife
search
node
“key:pa_ern”
–a
(a_ribute)
§ Search
nested
a_ributes
§ “memory_total:*”
–a
memory.total
§ Can
use
basic
“wild
cards”
in
the
pa_ern
“ipaddress:192.168.*”
§ Can
search
based
off
ranges
“ipaddress:[192.168.*
TO
192.172.*]”
Search
inside
of
recipes
Example:
Use
Ruby
recipe
to
search
all
nodes
that
are
running
an
outdated
package
56. Learning Chef
Data
Bags
A
data
bag
is
a
global
variable
that
is
stored
in
JSON
data
and
accessible
from
the
chef
server.
A
data
bag
is
indexed
for
searching
and
can
be
loaded
by
a
recipe
or
accessed
during
search.
Types
of
data
stored
in
a
data
bag:
ü Users
to
be
added
to
a
system
ü Admins
to
be
added
to
sudo
ü API/DB
Creden>als
(More
secure
and
be_er
than
environment
a_ributes
for
creden>als)
ü Much
more
59. Learning Chef
Roles
“A
role
is
a
way
to
define
certain
paMerns
and
processes
that
exist
across
nodes
in
an
organiza6on
as
belonging
to
a
single
job
func6on”
§ Up
un>l
this
point
we
have
assigned
recipes
to
be
run
for
each
node
§ Instead
of
upda>ng
run_lists
for
a
node
all
we
have
to
do
is
update
a
role
on
the
server
§ Prevents
us
from
having
to
manually
touch
all
nodes
that
need
the
change
§ A
role
is
essen>ally
a
lis>ng
of
recipes
and
a_ributes
that
are
to
be
executed
on
a
node
§ Instead
of
assigning
a
run
list
for
each
node
we
assign
the
node
a
role
§ A
base
role
can
be
assigned
inside
of
a
roles
run_list
60. Learning Chef
Roles:
Role
management
with
knife
§ Knife
role
create
role_name
§ Chef-‐repo/roles/rolename.rb
§ Knife
role
from
file
chef-‐repo/roles/rolename.rb
§ Knife
role
list
–w
(views
a
list
of
roles
on
the
chef
server)
§ Knife
role
delete
role_name
61. Learning Chef
Roles:
Produc>on
How
can
we
spin
up
new
nodes
(like
auto
scaling)
without
having
to
manually
modify
run_lists
in
a
node?
§ Pass
in
cloud-‐init
informa>on
about
the
node
§ Create
Virtual
Machine
Images
a#er
a
node
has
been
bootstrapped
§ Do
not
name
the
node
but
instead
let
it
use
the
FQDN
as
the
node
name
§ Modify
/etc/chef/first-‐boot.json
to
include
the
“role”
of
the
node
63. Learning Chef
Knife
Plugins
Knife
can
be
extended
with
the
use
of
plugins
§ Knife-‐flip:
Manage
environments
for
nodes
§ Cloud
plazorms:
azure,
ec2,
google,
linode,
openstack,
rackspace,
etc
§ Custom
plugins
65. Learning Chef
Work
Flow:
§ Nodes
should
be
bootstrapped
and
managed
from
the
worksta>on
§ Nodes
should
be
assigned
roles
and
environments
§ A_ributes
specific
to
roles/environments
should
be
configured
accordingly
§ For
auto
scaling
environments
such
as
AWS
“una_ended”
bootstrapping
should
be
used
66. Learning Chef
Work
Flow:
Una_ended
Bootstrapping
In
order
to
have
an
una_ended
install
the
node
when
first
created
must
meet
the
following
criteria:
§ Must
be
able
to
authen>cate
to
the
chef
server
§ Must
be
able
to
configure
a
run_list
§ Must
be
able
to
access
the
chef-‐validator.pem
so
that
it
may
create
a
new
client.pem
and
iden>ty
on
the
chef
server
§ Must
have
a
unique
node
name
§ Client.rb
file
must
have
proper
configura>on
so
that
it
knows
what
server
to
communicate
with
§ Modify
the
file.json
in
/etc/chef
to
include
the
run_list
for
the
node
§ This
will
ideally
include
a
way
to
automate
the
running
of
chef-‐client
67. AWS CSA
Certification
Example:
Simple code that when
run will create an S3
bucket.
Version control your infrastructure!
{
"Descrip>on"
:
"This
template
will
create
an
s3bucket",
"Resources"
:
{
"S3Bucket"
:
{
"Type"
:
"AWS::S3::Bucket",
"Proper>es"
:
{
"AccessControl"
:
"PublicRead",
"BucketName"
:
"gigitygumdrops"
}
}
},
"Outputs"
:
{
"BucketName"
:
{
"Value"
:
{
"Ref"
:
"S3Bucket"
},
"Descrip>on"
:
"Created
bucket
for
storing
websites"
}
}
}
68. PRESENTATION
TITLE
List Title:
Lorem ipsum dolor sit amet,
consectetur adipiscing elit.
Aenean pellentesque facilisis
felis. Suspendisse ipsum erat,
facilisis at euismod vel,
consequat vitae nulla. Curabitur
fringilla, ligula a sagittis
venenatis, odio velit ornare
ligula, non semper ligula eros
eget neque. Ut sagittis vulputate
est, in mollis libero varius eget.
Cras felis felis, feugiat a sem a,
pharetra elementum arcu.
In odio lectus, placerat ut felis
vitae, ullamcorper facilisis elit.
Nam posuere metus et velit
commodo tincidunt.
" Linux List Item Number 1
" Linux List Item Number 2
" Linux List Item Number 3
" Linux List Item Number 4
" AWS List Item Number 1
" AWS List Item Number 2
" AWS List Item Number 3
" AWS List Item Number 4
69. PRESENTATION
TITLE
Image Title:Content area for image description or caption. Even regular content simply
associated with the image. Content area for image description or caption. Even
regular content simply associated with the image.
70. PRESENTATION
TITLEChart Title: Lorem ipsum dolor sit amet,
consectetur adipiscing elit.
Aenean pellentesque facilisis
felis. Suspendisse ipsum
erat, facilisis at euismod vel,
consequat vitae nulla.
Lorem
Ipsum
Dolor