Re: what to do w/ hosts
Will Partain <partain <at> dcs.gla.ac.uk>
2002-03-11 11:19:07 GMT
Folks, another tiny rumination on the "hosts quandary"...
This is an issue of "ARK fundamentals", the "theoretical"
side of the Arusha Project. For those of you closer to
'user' than 'developer', it's nothing to worry about I
have tried to give enough background so it is understandable
to all, though.
One of our basic theses is that sysadmin needs some extra
thinking machinery. [Analogy: Newtonian mechanics really
needed calculus; you do could talk physics without calculus,
but life got a lot better with it.] ARK proposes a very
simple "object model" based on what some call "value
inheritance" as that extra machinery.
We call the objects "things", and the idea is that a
sysadmin can organize his/her world around the "things" that
make most sense -- users, packages, web sites, routers,
vendors, .. anything. These "things" can have "methods",
i.e. fields that *do* something, i.e. code gets run.
Fact: such code must be run on some host or hosts. At
present, we have "hosts" as ARK things, but they are a bit
of a hack because of their somehow-special role.
Jonathan Hogg is leading a charge (ARK TNG) based around the
elimination of the special pleading for hosts. I mused upon
an alternative, namely to make hosts *entirely* special,
i.e. not ARK things at all. Daniel Hagerty hinted at
support for the latter view and, when he gets time, he may