addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

February Chef & Vagrant workshop (Session 2/2)

Chef & Vagrant for Dev 'n' Ops - managing and infrastructure's lifecycle using Opscode Chef & Vagrant. We will cover Chef and how to use / implement it. Understand a software development lifecycle using vagrant.

Day 1 - Getting Started:

  • Introduction to Chef - understanding Chef components and concepts
  • Installing the tools for these two sessions - files will be available offline
  • A cookbook lifecycle :: Writing a cookbook  - hands on
  • A cookbook lifecycle :: Improving a cookbook  - hands on
  • Introduction to Vagrant
  • Testing our cookbook with Vagrant  - hands on

Workshop will have a lot of hands-on - bring your laptops !

 

Day 2 - Diving Deeper:

  • Recap day 1
  • The wrapper cookbook - hands on
  • Managing dependencies
  • Chef server vs. Chef solo
  • Chef solo route - configuring and using chef solo
  • The Vagrant (solo) way
  • Chef server route -> use vagrant to setup your chef server - hands on
  • Chef server route -> use vagrant to setup your chef workstation - hands on
  • Converging nodes with Chef server (and client ...) - hands on (Bootstrap & Converge)

Summarize + Open discussion / Q&A

 

PLEASE NOTE !

This workshop has two sessions on [masked] AND [masked] PLEASE RSVP TO THEM BOTH !

Join the online conversation at the Full Stack Developers Facebook group page.

 

Join or login to comment.

  • Doron M.

    Thank you Haggai, the meetup was very educating and informative. lots to practice moving forward.
    I'd appreciate a more concrete base for deciding whether to install a chef-server vs chef solo.

    thanks,
    Doron

    1 · February 23, 2014

    • Haggai Philip Z.

      Personally @ large scales I would use a chef server & at small scales chef-solo, nevertheless chef-solo will often be used for testing / development.

      February 24, 2014

  • Haggai Philip Z.

    Guys, in today's session we will be running our own Chef-Server (OSS) and bootstraps nodes to use it. In order to save time for today you can do the following:

    1. git clone [masked]:tikalk-cookbooks/ch­ef_workshop.git

    2. cd chef_workshop/chef_server_route/ch­ef-server

    3. Vagrant up in ~5 minuets you should have a server up and running 4. vagrant halt -> this will stop the machine.

    When you arrive to the workshop today you will already have a chef-server !

    you could to the same to the nodes under: chef_workshop/chef_server_route/ub­untu_node or centos_node [vagrant up && vagrant halt ]

    February 23, 2014

  • A former member
    A former member

    Chef / vagrant

    February 21, 2014

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy