-
So i promised i would speak english, in case, we don't know who's out there on the far reaches of the
-
galaxy.
-
so if that's ok with everyone, i'll continue in english.
-
so the subject of configuration management
-
is now pretty well known in the open source community and cfengine as a project has been around
-
since 1993 as petter said, and it's still going strong and we're not running out of ideas any time soon.
-
Not Synced
and so it's great to come here and actually summarize what's been going on in the last couple of years.
-
Not Synced
because the last couple of years of cfengine have probably been one of the most active develeopment periods
-
Not Synced
of cfengine as a whole.
-
Not Synced
as some of you probably know, a couple of years ago we started a company to develop and support the future
-
Not Synced
of cfengine,
-
Not Synced
and since then it's been more resources to carry the project forward.
-
Not Synced
so these are exciting times in terms of
-
Not Synced
development of configuration management.
-
Not Synced
So i thought i'd just start out by sketching out the problem
-
Not Synced
of configuration managament for anyone who might not be completely familiar with it, and then i'll go
-
Not Synced
into some of the history and explain some of the features of cfengine.
-
Not Synced
so the challenge that i realized i back in 1993, is that we needed to separate the design of systems
-
Not Synced
from the implementations of the systems.
-
Not Synced
in pretty much the same way that today we separate design and implementation in many other areas in software
-
Not Synced
design,
-
Not Synced
implementation in web design, we have style sheets that take care of the look and feel,
-
Not Synced
and then we have the implementation in terms of html.
-
Not Synced
we can think of cfengine and configuration management tools in some ways being like style sheets for o
-
Not Synced
perating systems somewhat, deciding how they should look.
-
Not Synced
And the reason to separate them is pretty obvious, it's the classic argument that humans are really good at thinking
-
Not Synced
and planning and designing.They're not really good at implementing stuff.
-
Not Synced
we try to be consisting in the implementating of one or two systems, maybe you're lucking. 100 machines,
-
Not Synced
forget it.
-
Not Synced
1000 machines, you're probably dead by then anyway.
-
Not Synced
machines are really good at doing consitant implementation and not very good at desiging or planning.
-
Not Synced
So separating of duties is a good state of affairs. So that's pretty much the idea.
-
Not Synced
and as i say, it's like stylesheets of the web, we're trying to separate how we want things to look and
-
Not Synced
from how we want things to be implemented.
-
Not Synced
The difference of course between stylesheets and systems is that your web pages aren't usually changing
-
Not Synced
behind your back.