You should see a more interesting post here today.
Tomorrow till friday I’ll be going to a cfengine3 class.
I’ve been so excited about this I’ve been counting down the days and such…
Unfortunately thanks to the OpenSSL nightmare of today I don’t even have time to think about tomorrow.
anyway. by next week I’ll have working knowledge of both Ansible and cfengine3.
This is what I consider a great toolset, or as I described to a friend as “having an excellent hammer for when I need a hammer”, and also having something to build whole cities with for when I need that.
Talking of cities:
One of my favorite books is “The city and the stars” by Arthur C. Clarke, which takes place in a city enduring aeons.
This is kinda what I’d love my servers to do, too. I think a good overall system should be able to keep running and running and running. It should be weathering disk failures, updates and power failures.
I think this does not just work by giving it a “immutability”, but by teaching it how to serve it’s actual purpose…
Cfengine, to me, feels closest to that goal.
(Notably, in that story the only only normal-thinking guy in that city is a rare occurance and really wants to get out)
Instead of a new years resolution* I’ve looked into what things to work on next. Call it milestones, achievements, whatever.
- I’ve already cleaned up my platform, based on Alpine Linux now.
- IPv6 switchover is going well but not a prime concern. Much stuff just works and other stuff is heavily broken, so it’s best to not rush into a wall.
- Bacula: I’ve invested a lot of time to into backup management routine again. This paid off and made clear it was stupid to decide per-system which VMs to backup and which not. If you want to have reliable backups, just backup everything and be done with it. Sidequests still available are splitting catalogs and wondering why there is no real operations manual. (rename a client? move clients backup catalogs? All this stuff is still at a level that I’d call grumpy retarded cleverness: “You can easily do that with a script” – yeah, but how comes that the prime opensource backup tool doesn’t bring along routine features that are elsewhere handled with ONE keypress (F2 to the rescue)
- cfengine: This will be my big thing over the next 3 weeks, at home and on holiday. Same goal, coming to grips real well. During the last years I’ve tried puppet, liked but not used Chef and glimpsed at SALT. Then I skipped all of them and decided that Ansible was good for the easy stuff and for the not easy stuff I want the BIG (F) GUN, aka cfengine.
- Ganeti & Job scheduling: In cleaning up the hosting platform I’ve seen I’ve missed a whole topic automation-wise. Ahead scheduling of VM migrations, Snapshots etc. A friend is pushing me towards ganeti and it sure fills a lot of gaps I currently see, but it doesn’t scale up to the larger goal (OpenNebula virtual datacenters). I’ll see if there is a reasonable way for picking pieces out of Ganeti. Still, the automation topic stays unresolved. There is still no powerful OSS scheduler – the existing ones are all aimed at HPC clusters which is very easy turf compared to enterprise scheduling. So it seems I’ll need to come up with something really basic that does the job.
- Confluence: That’s an easier topic, I’m working to complete my confluence foo so that I’ll be able to make my own templates and use it real fast.
What else…. oh well that was quite a bit already 😉
Otherwise I’ve been late (in deciding) for one project that would have been a lovable start and turned down two others because they were abroad. Being at the start of this new (selfemployed) career I’m feeling a reasonable amount of panic. Over the weekends it usually turns into a less reasonable one 😉
But yet also cheerful at being able to give a focus on building up my skills, and I also think it was the right decision. I went into the whole Unix line of work by accident but loved it since “if it doesn’t work you know it’s your fault” – a maybe stale, yet basically bug-less environment where you concentrate on issues that come up in interactions of large systems instead of bug after bug after bug. (See above at platform makeover – switching to alpine Linux has been so much fun for the same reason).
My website makeover is in progress and I’m happy to know I’ll visually arrive in this decade-2.0 with it soon.
Of course I’ve also run into some bugs in DTC while trying to auto-setup a WordPress setup. DTC is the reason for the last Debian system I’m keeping. Guess who is REALLY at risk of being deprecated now 😉
*not causing doomsday worked for 2012 though