Adding 'compute1' and 'compute10' leads to problems

[Ian Wells]

Firstly, site.pp.example uses regexps for nodes:

node /compute10/ { ... matches compute10 }
node /compute1/ { ... matches compute1, 10, 11, 12, ...}

Secondly, the cobbler commands to add a node don't always run:

if cobbler system list | grep compute1;
 # doesn't run if compute10 has previously been installed

[Mark T. Voelker (mvoelker)]

That line is intended to be changed by the user anyway, so it seems to me we could quite easily add a couple of comments to tell them they have the option to not use a regex and/or change the line so that it doesn't do so off the bat:

node 'compute10.cisco.com' {

And/or we could cuse use anchors:

node /^compute1$/

I think the original intent of using regexp's in the first place was probably to avoid having to deal with FQDN's for multihomed hosts.

[Michael Chapman (michaeltchapman)]

This was to support testing multiple clusters on a single machine, which renames boxes to eg. compute-server-$DATE

[Mark T. Voelker (mvoelker)]

Pull request:
https://github.com/CiscoSystems/grizzly-manifests/pull/60