Skip to content
Browse files

Add first pass at bootstrapping post.

  • Loading branch information
KyleOndy committed Dec 12, 2019
1 parent 8a8d5d1 commit 8cf7ceca9b0c8c31bdc5fb5e532b30d51a07f324
Showing with 21 additions and 2 deletions.
  1. +1 −2 provider/posts/2019/home-lab-pt-1.markdown
  2. +20 −0 provider/posts/2019/home-lab-pt-2.markdown
@@ -35,7 +35,6 @@ The long term plan is to self host and expose these services via a DMZ next to m

This post will contain an up to date list of posts that go into more detail

- Physical setup
- Bootstrapping
- [Bootstrapping](/posts/home-lab-bootstrapping)
- Configuration Management
- Running Services
@@ -0,0 +1,20 @@
title: Home Lab - Bootstrapping
Tags: homelab
created: 2019-12-11T22:24:37Z
author: Kyle Ondy
subtitle: Working out the kinks.

One of the most common and insidious issues with systems is configuration drift.
In a home lab without the controls in place that an enterprise or real business demands this drift happens before you realize.
One of the best ways to ensure minimal drift is to minimize the effort needed to rebuild the system in question.

Applying your configuration management to a fresh image verifies that you are able to rebuild your environment as needed.
Using a combination of [pixiecore]( and [waitron]( I am able to choose if each board should have its OS reinstalled when it boots into the PXE environment.

The RaspberryPi setup was fairly straightforward following [the offical documentation](

The [ODRIOD-H2]( _should_ be able to follow the same workflow.
However, there seems to be a bug in the H2's BIOS.
I've made a post for further clarification on the [official forums](

0 comments on commit 8cf7cec

Please sign in to comment.
You can’t perform that action at this time.