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