<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>virtualbox on Otzarri.net</title>
    <link>https://otzarri.net/tags/virtualbox/</link>
    <description>Recent content in virtualbox on Otzarri.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2019 &lt;a href=&#34;https://creativecommons.org/licenses/by-sa/4.0/&#34;&gt;CC BY-SA&lt;/a&gt;</copyright>
    <lastBuildDate>Tue, 10 Sep 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://otzarri.net/tags/virtualbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chef client bootstrapping lab</title>
      <link>https://otzarri.net/chef-client-bootstrapping-lab/</link>
      <pubDate>Tue, 10 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://otzarri.net/chef-client-bootstrapping-lab/</guid>
      <description>Seems that I&amp;rsquo;ll work with Chef soon, so it&amp;rsquo;s time to review some lessons about it. After browsing the web for a while, I found that using Virtualbox to virtualize infrastructure and Vagrant to manage it as code is the easiest and fastest way to provision new lab environments for Chef.
The first step to start working is to create a baseline, a minimal workaround built with one server host and two nodes.</description>
    </item>
    
  </channel>
</rss>
