diff --git a/content/post/a-raspberry-pi-bmc.md b/content/post/a-raspberry-pi-bmc.md
index 9734ebf..a5daad6 100644
--- a/content/post/a-raspberry-pi-bmc.md
+++ b/content/post/a-raspberry-pi-bmc.md
@@ -9,6 +9,8 @@ draft = false
 
 +++
 
+NOTE 2017-03-21: This post is still a work in progress - check back for updates!
+
 IPMI BMCs are pretty ubiquitous in the datacenter and enterprise computing, because in a warehouse full of computers, finding and walking up to one just to reset it or check its console is quite daunting. The same goes for a home server: it may just be in my basement, but in a closed-up rack it becomes a huge hassle to manage a machine without IPMI. I try to get it on every motherboard I buy, but currently my Ceph nodes are running with motherboards that lack built-in IPMI. After an incident with one machine while I was on vacation, I finally decided that they needed remote management, and I decided to make my own BMC for them rather than waste money on replacement (IPMI-capable) motherboards.
 
 ## Enter the Raspberry Pi