Monthly Archives: March 2016

  • -

Jenkins User Conference Israel 2016 Announced

Category : Tools

Reposted from the official event page:

Jenkins User Conference hits Israel fifth year in a row!

Come learn how to optimize Jenkins across the software delivery process!

With more than 100,000 active installations and more than 1,000 plugins Jenkins is no doubt a leader in the CI and CD domain. Our 2015 Jenkins User Conference in Israel drew more than 700 developers, and was so successful that this year we know it will be a blast!

JUC IL 2015

The Jenkins User Conference focuses on the use of Jenkins for continuous integration (CI) and continuous delivery (CD) as the fundamental best practice for enterprise software delivery. Our presenters are experienced Jenkins developers, build managers, QA, DevOps practitioners, IT managers/executives, architects and IT operations who are luminaries within the Jenkins community. They represent the many organizations around the world that are leveraging the use of Jenkins within the software delivery lifecycle.

We welcome you and other leading Jenkins developers, QA, DevOps and operations personnel to the Jenkins User Conference World Tour. As the organizing sponsor of the Jenkins User Conferences, CloudBees has helped the community grow the Jenkins User Conferences worldwide over the last four years. In 2015, the community saw a 70% increase in attendance over 2014.

In 2016, the World Tour will bring together the full strength of the Jenkins community—now over 100,000 installations strong—and the ever-expanding Jenkins partner ecosystem, allowing attendees to learn, explore, network face-to-face and to shape the next evolution of Jenkins development. Kohsuke Kawaguchi will kick off the event with a keynote address and lead us into the conference. Come get the knowledge you need to make your current and future Jenkins projects a success.

Call For Papers is Now Open>


  • -

DevConTlv update

Category : Tools

Just went to DevConTLV pre-conf speaker dinner. Had a lot of fun talking about tech, life and business with some of the finest minds in the industry.

Now – it figures I was wrong regarding the conference format. This one isn’t going to have beers and live music… But! It will have great speakers who are going to rock the stage with talks on cutting edge software development tools and metodologies. On my part I will do my best to keep the audience entertained. So if you want to be a ninja – make sure to attend.


  • -

Service-Oriented Collaboration

Category : Tools

We-are-happy-to-serve-you

This post is yet another take on how we should be creating software together. I’m now working on a book named “Coding Together” that will be reviewing all the challenges of collaborative software delivery and the ways of overcoming them for maximum creativity and efficiency. As I’m gathering materials – my understanding not only deepens but shifts – complex systems viewed holistically definitely cannot be analyzed as a sum of their parts.
Two years ago I gave a few talks and wrote about the importance of enabling self-service principle in a smart and secure way for smooth and effective value delivery in software engineering organisations. I still hold a strong belief in self-service builds, tests, deployments and infrastructure provisioning. All these can greatly enhance the rate of innovation and the quality of produced software.
If done correctly, that is…

But it can be quite disastrous when this self-service concept implementation isn’t designed and delivered with due attention. What’s more annoying and demotivating than being told that you can build, test and deploy with a click of a button but ending up with a failed process and a bunch of cryptic error messages?!
And then opening a ticket to the suporting team and waiting for hours because “they are busy developing the new self-service infrastructure”…

I’ve seen this happening too often in real life and that led me to understand that self-service is really worth nothing when the other most important ingredient is missing. And that is – human service consciousness. Not serving oneself but serving others should be the focus.

That’s easy to say, but how do you practically implement this? How should we structure our software development organization around service consciousness and how is this any different than what we used to have before continuious delivery and automation became common knowledge?

Microservice architectures are becoming the de-facto standard for building modern highly scalable and reliable software systems. In line with Conway’s law – small service teams based on consumer-driven contracts should become the foundation of a highly scalable, flexible and agile IT organisation. And it’s really less about the team size but more about being focused on serving the members of other teams – the consumers of your team’s api, the users of your self-service automation, the implementers of your feature requests or the developers you’re assigning bugs to. It’s about building a decentralized Team of Teams  where each unit takes pride in the level of service it provides and not in its special status in organisational hierarchy.

Advanced communication is what allows us humans to collaborate on massive scale. But communication can also ruin collaboration if what we transmit is a negative, elitist or egocentric attitude.

As Sabine Bendixen rightfully writes – a highly effective agile organization starts with effective communication.

Communication is always the first thing we at Otomato look at when performing a software delivery assessment for our clients. How are changes getting communicated? How is knowledge managed within the organization? How are decisions made? How do the members of different teams see themselves and their role in the value delivery stream?
Whenever there’s hostility, resentment and lack of motivation or transparency – we know we struck a bottleneck. And this is a great place to start. Start building trust and visibility, reviewing and streamlining the processes. But most important – start building collaboration around providing important services among teams. Around treating all the internal interactions as interactions with customers in which customers invariably come first and their experience is the utmost measure of our performance.

I like to call this ‘service-oriented collaboration’ and that’s the only type of collaboration that’s truly sustainable, adaptable and robust. This is the kind of collaboration that will allow your business to quickly change course when needed and keep engineers creative and motivated. And once you have this – self-service infrastructure will take you to the moon!

Now did you notice how this whole post didn’t mention DevOps even once?
Watch our follow-up posts to learn why.

Happy delivering!


  • -

Cloud-aware, provider-agnostic monitoring

Category : Tools

I’ve never had to deal so much with monitoring. I’ve established a few Nagios instances in earlier days, I’ve used Amazon CloudWatch, Pingdom and New Relic lately for cloud setups, but I don’t consider myself a monitoring expert. At Otomato we are currently mainly focused on software delivery processes, on how to get those bits from dev machines and into production in the most effective and agile manner without compromising quality. Monitoring, although an important part of running software and assuring successful value delivery (should I say an important part of DevOps?) , has been largely out of our scope.

But now we are working on a  new project where we had to deal with the full-full cycle – building, deploying and running. Moreover – the requirement was for cloud-provider-agnostic solutions as this is going to be a multicloud setup.

And with that came the most exciting part of any project – the research!

I didn’t want to go back to Nagios as my previous encounters with it left a bad aftertaste. Cumbersome setup, dated WebUI and no real support for ephemeral cloud servers. So I started reading up to understand  what are the newer tools on the market and if #monitoringsucks less now than it used to.

Here are the links to a few articles that really helped me in my research:

A series of posts on Florin’s blog: http://florin.myip.org/blog/monitoring-cloud-part-1-tools-and-techniques

All James Turnbull has to say about monitoring and his experience with Riemann: https://kartar.net/tags/monitoring/

This comparison of Nagios, Sensu and Icinga2 : http://phillbarber.blogspot.co.il/2015/03/nagios-vs-sensu-vs-icinga2.html

And this great post on Sensuhttp://roobert.github.io/2015/11/09/Sensu-What/

And there are more…

To sum things up – I really liked what Riemann has to offer, and I’d like to research it more for future project but currently we’ve decided to go with Sensu. Reasons: scalability, cloud-awareness and yes – a good-looking WebUI.

Needless to say – we’ve only touched the tip of the iceberg here – modern monitoring is a world of its own. Metrics collection, event handling, threshold definition, log analysis, anomaly detection – you name it. We promise to revisit all these in more depth but until then – please comment here with links and insights of  your own.

Happy delivering!

 

 

 


  • -

DevConTLV is only 2 days away!!!

Category : Tools

If you’ve never been to DevConTLV – you are seriously missing out!!! Running under the banners of “Server Side Development and Rock’n’Roll” this is the grooviest software conference in Middle East, (or maybe even in the whole world?!)

Great speakers, free beer and live music – what more can a geek ask for?

The one taking place on the 22nd of March is probably the largest, the most bombastic DevConTLV ever. Featuring speakers from all parts of the planet, a Terraform training day and no other than Otomato’s own Ant Weiss as the DevOps track MC.

There are only late bird ticket left now, they are a bit pricey, but you can use the ‘ANTWEISS‘ coupon to get a very nice discount.

Hoping to see you all!

P.S: and this is a sweet memory from the last year DevConTLV : Sputnik Hi-FI feat. Ant Weiss – Software is Eating the World!

 


  • -

Otomato – separating scopes.

Category : Tools

If you’ve been reading the posts on this blog  – you know that until now this was a mixed bag of professional articles, technical tips and personal impressions.

Now that Otomato is going to become a full-blown consulting firm I feel it’s time to separate the personal from the professional.

There still may be some shared context here and there, but starting today I’m moving my personal blogging to a Hugo-based site hosted on Github pages – http://antweiss.com


  • -

Going full time and looking for partners.

Category : Tools

Dear friends, colleagues and clients!
As some of you may know – I’ve decided to finally dedicate all of my working time to developing Otomato into the best in class DevOps and Software Delivery consultancy and training company.
Starting March 10th this will be the focus of my business activity and I’m now open for projects, collaborations and partnerships.

If you’re enthusiastic about DevOps and improving software delivery practices, if you need help with streamlining your workfows or enabling infrastructure automation – drop me a note and I’m sure we’ll find a way to do some great stuff together.

Ant Weiss
logo-with-red-circle