In our environment we want to use Foreman to build our OCP hardware. It was working well except that the installation would repeatedly PXE boot to reinstall because Foreman would not know that the PXE portion was complete. The standard notification code below was failing for some reason. 1 2 %post --interpreter=busybox --ignorefailure=true wget -O /dev/null <%= foreman_url %> After running the unattended install in a Fusion VM so I could have console access I reviewed the install log and a misleading message from wget about the URL being bad.

I often see/hear comments from people whose common sense approach to availability design includes eliminating a single point of failure. This is a great goal when required, but care must be take that the “common sense” approach is actually achieving what is required. I have found that using a fault tree approach to evaluating design decisions can be insightful. The last instance of this is a book, while otherwise great, gave the advice of separating a database from the application function onto separate servers because there was a single point of failure.

Launch the command prompt via: Start | Programs | ADAM | ADAM Tools Command Prompt dsdiag.exe /s:localhost:389 repadmin.exe /viewlist * /homeserver:localhost:389 repadmin.exe /replsummary * /homeserver:localhost:389 repadmin.exe * /repsto /homeserver:localhost:389 repadmin.exe /showconn * /homeserver:localhost:389

Understanding Microsoft Virtualization Solutions (Second Edition) http://blogs.msdn.com/b/microsoft_press/archive/2010/02/16/free-ebook-understanding-microsoft-virtualization-r2-solutions.aspx