Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Puppet broke my Xen

DZone's Guide to

Puppet broke my Xen

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.

Actually it didn't , but now I got your attention. 
We just adopted the use of adding headers to all of our files that are managed by puppet so people will know not to touch it
    file {
    "/etc/xen/scripts/network-custom-vlan-bridges":
    owner => "root",
    group => "root",
    mode => "0755",
    content => template(
    "headers/header-hash.erb',
    "xen/co-mmx-network-custom-vlan-bridges.erb");
    }

All worked nice however upon bootstrapping our Xen host the bridges stopped working .. running the network-custom-vlan-bridges script manually solved everything and created the appropriate bridges. But at boottime it didn't..

I added some debug info to the script and figured it never got executed at boot time.

Turns out that when I removed the headers Xen actually does configure the bridges at boot time, Xen probably checks for a shebang at the beginning of the file.

Putting the header at the end of the file therefore solved the problem.

Source:  http://www.krisbuytaert.be/blog/puppet-broke-my-xen


Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}