Quickstart

erikwb> i've successfully built it on RHEL6
erikwb> via multipkg
erikwb> you need libcrange, mod_ranged both installed
erikwb> and then edit /etc/libcrange.conf to be something sane
erikwb> for yaml files, [ebourget@ela4-admin02 ~]$ cat /etc/libcrange.conf
erikwb> loadmodule yamlfile
erikwb> that's it
erikwb> then put *.yaml in /etc/range/
erikwb> yaml files are:
erikwb> [ebourget@host range]$ cat cluster-name.yaml 
erikwb> ALL:
erikwb> - hostname1
erikwb> - hostnam2
erikwb> CLUSTER:
erikwb> - hostname1
erikwb> - hostname2
erikwb> CONFIG: app-config-version-1.2.3
erikwb> CONTAINER: appname
erikwb> CONTEXTPATH:
erikwb> etc
nrh> builds fine on osx
nrh> s/libtoolize/glibtoolize/
nrh> how different is the yaml/range specification stuff than the rolesdb stuff i'm used to?
eam> in terms of parsing?
nrh> in terms of specification
nrh> like:
nrh> ALL:\n- foo4-10.bar.com
nrh> is that 4..10?
eam> depend if you have - or .. as the expansion dealie
eam> I think e switched it
nrh> yeah i saw
eam> so - does nothing now
nrh> heh
nrh> but .. would, got it
eam> but foo4..10.bar.com would be 4..10 yes
eam> no enclosing {} necessary
erikwb> - does set diff
nrh> and i guess i'm confused about the difference between the definitions like ALL: and how i'm used to using role-names.  is 'ALL' in this case a rolename?
erikwb> (a,b) - b ==> a
eam> erikwb: with spaces right
eam> yeah
erikwb> uh
erikwb> ALL is a metadata key
erikwb> if you have foo.yaml
erikwb> with ALL: bar
erikwb> then
eam> nrh: so, the *file* represents a cluster (role)
erikwb> %foo:ALL == bar
eam> and
eam> every cluster/role is actually a dictionary/hash
erikwb> there's only one magic key
erikwb> called CLUSTER
erikwb> where if you just say %foo
erikwb> it means %foo:CLUSTER
erikwb> everything else is just whatever you feel like calling it
eam> so from a roles perspective
eam> there are two magic clusters, HOSTS and GROUPS
nrh> ahhh
nrh> ok
eam> and %GROUPS:FOO has a shorthand syntax of @FOO
eam> and this is what rolesdb implemented
eam> but the actual underlying cluster labels can have multiple definitions of host lists
eam> with arbitary names
eam> and as e said there's one that's magic: %foo:CLUSTER, and a few that are by convention like :ALL
nrh> i'll try to distil this into some actual documentation at some point
nrh> needs QUICKSTART
eam> ya
eam> and %GROUPS:FOO has a shorthand syntax of @FOO
erikwb> not with yamlfile
erikwb> fyi
erikwb> yamlfile just doesn't do @
erikwb> cause it's not needed in a post-gemstone world
erikwb> would be ez to add though.
eam> ah
eam> yeah it seems fine to drop