Open-Future, making open source work for You
The increased industrialization has brought us more and more servers to manage, be it local, in the cloud, virtual or bare metal. And on the other hand, budgets are getting tighter to stay competitive. This has pushed us, sysadmins to search for tools to help us to automate system administration tasks. This gave birth to tools like the Puppet, Chef, CFengine, Saltstack and many more.. All of them started with the same goal in mind: "To make it easier to configure and maintain as many as thousands of servers". Even when you are a small company with as much as 10 servers, you will benefit using one of those tools.
Last week Johan from Open-Future talked about Collaboration at the Zarafa event “Life Beyond Email”, the yearly Zarafa event for the Belgium Zarafa Partners and Zarafa Customers. As the title of the event suggest, it is clear that Zarafa is moving from a groupware to a collaboration platform. It all started around e-mail, calendaring and adding 'teaming' facilities. But it isn't about email and sharing calenders anymore.
But what is collaboration anyway ?
Wikipedia says “Collaboration is working with each other to do a task and to achieve shared goals.”
And working together means a lot of communication between each other.
In the past we had peer to peer communication with for example a simple phone call, a conversation from person to person, IRL or using e-mail. But collaboration today is more focused on teaming. (well, we work together, don't we ?). So we extended e-mail, and created public folders, shared mailboxes and mail listings to make it possible to have access to the same information by multiple people at once. Add a calendar, a basic document management system and groupware is born.
First of all, I apologies for the bad choice I made for the color scheme for the code examples making it hard to see the code. The slides are on slideshare or you can download the pdf here.
The github repo of the openldap type, mentioned in the talk is located here The whole idea of giving this talk, is to show that TDD for Puppet code is something that can be done. Looking at the reactions from the people in the room, writing rspec unit tests is seen in most cases a waste of time. And I kind of follow this feeling. But on the other hand, this does not give you a reason to not write tests for your modules. And yes, in some cases, writing rspec test for your modules is still a valid way of testing them.
On the other hand, I tried to show that when dealing with pure ruby code, which we all will do sooner or later, when we need to extend puppet to make it fit our own environment much better. And for us sys-admins, the first time we do, will probably be when we write our first Custom Puppet Type and Provider.
And I hope I did show that for that kind of software, TDD fits much better.
And the talk just touches the top of the whole TDD process, just showed the very basics of writing your rspec file, run your tests and make just that piece of code to pass your test, to become Green.
During the Open Source Conference we will have business sessions for CIO’s, CxO’s, IT Managers, Business Managers and Team Leaders, as well as technical sessions for IT Architects, Developers, System Administrators, System Engineers, Developers, Integration Specialists and Consultants. Also when you are interested in creating business value from Open Source based solutions you are welcome to attend the OSC 2013.
The Open Source Conference welcomes guests from the Netherlands, Belgium and Luxembourg.