Stupid services, I’m moving on

October 12, 2005

I’m giving up on service management for a few days — I think I need to stew on it or something.

Instead I’m going to take a crack at handling overriding object values, along with maybe the value intersections I mentioned a couple days ago, which will need to involve parameter values as arrays.

Fortunately I should be able to keep them pretty separate. I’m first going to create an ‘implicit’ attribute, which will be set on all instances created through recursion (e.g., recursing through ‘/etc’ will result in the ‘implicit’ flag being set on all resulting files except ‘/etc’ itself). Any conflicts between implicit and explicit instances will always be entirely won by the explicit instance — that is, no intersection will be sought.

But implicitness cannot handle cases where two instances that are either both implicit or both explicit collide. So the next step will be to use intersections for handling these conflicts. That is, the values will be the shorter list of all values allowed by all specifications. The only problem with this method is that it could introduce ordering, since when it comes time to fix a problem, you have to pick the answer, and I was planning on using the value specified first, but whose first? For instance, take this configuration:

    file { "/etc/funtest": owner => [root, adm] }
    file { "/etc/funtest": owner => [adm, root] }

The value list is the same, but the order is different. How do I pick which value to set the owner to? It’s essentially unsolveable at this point, but I don’t have to worry about it until I’ve already got the implicit stuff working, thankfully.

Converting from BlogSpot

October 12, 2005

I’ll be converting from my BlogSpot account, so the first few posts will be duplicates of that.

Hello world!

October 5, 2005

Welcome to This is your first post. Edit or delete it and start blogging!