3+ months is probably the biggest timeout I’ve taken from blogging in a while..
Not that I didn’t have anything to write ..but more that I was prioritizing writing different content over
over writing blogposts.
Blogging tech snippets and contributing documentation used to be one now all of that has evolved.
Anyhow ..
So to get things going here’s my preliminary Conference schedule for the next couple of months.
First up, in about one week (august 20-24) Ill be chairing the #devops track at [DrupalCon Munich](http://munich2012.drupal.org/)\ Next to talking there myselve explaining the [Drupal Crowd what devops is](http://munich2012.drupal.org/program/sessions/whats-devops-thing-anyhow)\ Plenty of interresting content there ranging from culture over to tooling and back. Im really looking forward to this one.
Devopsdays Mountainview sold out in a short 3 hours .. but there’s other events that will breath devops this summer.
DrupalCon in Munich will be one of them ..
Some of you might have noticed that I`m cochairing the devops track for DrupalCon Munich,
The CFP is open till the 11th of this month and we are still actively looking for speakers.
We’re trying to bridge the gap between drupal developers and the people that put their code to production, at scale.
But also enhancing the knowledge of infrastructure components Drupal developers depend on.
I’ve just finished presenting my talk on how I currently work on Puppet modules at Puppetcamp here in Edinburgh where I’ve been for the week talking on both FlossUK 2012 and Puppetcamp.
Honestly I was hoping for the audience to prove me wrong and I was expecting all of them to claim they were doing automated and repeatable deployments.
“An expert is a man who has made all the mistakes which can be made, in a narrow field.”
Niels Bohr
When I setup Logstash for the very first time I got bitten by an empty search, aparently no logs were indexed. Reading the log files indeed told me about\
1. WARN: org.elasticsearch.discovery.zen.ping.unicast: [Blaire, Allison] failed to send ping to [[#zen_unicast_1#][inet[/127.0.0.1:9300]]]
2. INFO | jvm 1 | 2012/02/06 22:45:55 | org.elasticsearch.transport.RemoteTransportException: [Page, Karen][inet[/127 .0.0.1:9300]][discovery/zen/unicast]
3. INFO | jvm 1 | 2012/02/06 22:45:55 | Caused by: java.io.EOFException
The above is the typical error when the ElasticSearch version you are using externally is not in sync with the one Logstash is using, yes those versions need to match.
Kent Skaar pinged me last week , asking for feedback on Lisa'11 and input for Lisa 2012.
Thought I should share my advise to him with the rest of the world
So If I were to host an event similar to Lisa I’d had either
Jordan Sissel or Mitchell Hashimoto give the keynote because over the past 24 months those people have written more relevant tools for me than anyone else :)
Earlier this week Inuits hosted a 2 day hackfest titled #MonitoringSucks. A good number of people with a variety of backgrounds showed up on monday morning. I don’t know why but people had high expectations for this event , did they really expect us to fix the #monitoringsucks problem in a mere 2 days ?
As announced earlier next monday and tuesday we’re opening up the Inuits offices for everybody working on monitoring problems.
There’s already a good number of people that have confirmed their presence and some people have asked
As for practical details .. the plan is simple.
I`m going to be at the place somewhere between 8:30 and 9:00 on monday. ( Hey .. it’s the day after Fosdem you know :))
The only thing I’ve planned is to do a get to know eachother round around 10:30 after that I`m expecting the hackathon to be self organising,
Given that @patrickdebois is working on improving data collection I thought it would be a good idea to describe the setup I currently have hacked together.
(Something which can be used as a starting point to improve stuff, and I have to write documentation anyhow)
I currently have 3 sources , and one target, which will eventually expand to at least another target and most probably more sources too.
If you are hacking on monitoring solutions, and want to talk to your peers solving the problem
Block the monday and tuesday after fosdem in your calendar !
That’s right on february 6 and 7 a bunch of people interrested to fix the problem will be meeting , discussing and hacking stuff together in Antwerp
In short a #monitoringsucks hackathon
Inuits is opening up their offices for everybody who wants to join the effort Please let us (@KrisBuytaert and @patrickdebois) know if you want to join us in Antwerp