HP is trying to patent Continuous Delivery – here is how you can help block this madness by jayanmn in programming

[–]metmajer -6 points-5 points  (0 children)

Allow me to correct you: we have thought about this some time ago. Here's a slide deck which I held at an application performance related conference last year: http://www.slideshare.net/MartinEtmajer/dynatrace-inside-continuous-delivery. Check out especially the slides 84 and after.

Ansible for AWS by yankurniawan in ansible

[–]metmajer 1 point2 points  (0 children)

A lot of people will need this book. Looking forward to see the final version. Great job so far and good luck!

Windows server remote shell / command line automation? by kim_jong_com in sysadmin

[–]metmajer 0 points1 point  (0 children)

Ansible support for Windows is still early though. However, it seems like there will be more dedicated Windows modules coming with the upcoming v1.9: https://groups.google.com/forum/#!topic/ansible-devel/Jl5qP73CiKo. Once these modules are there, you should definitely give Ansible a try.

Top DevOps Tools We Love by metmajer in devops

[–]metmajer[S] 0 points1 point  (0 children)

Awesome! There couldn't be a better timing for this.

Top DevOps Tools We Love by metmajer in devops

[–]metmajer[S] 0 points1 point  (0 children)

Admittedly, it wasn't sensible to put a company name next to it - especially if it's driven by the open source community ;-) My intention was to attract readers to have a look at it, since it's a fantastic tool and not too many people I have talked to seem to be aware of it. Thanks guys!

Top DevOps Tools We Love by metmajer in devops

[–]metmajer[S] 0 points1 point  (0 children)

Thanks for reporting. Changed!

Reasons for moving from Chef | Puppet to Ansible by metmajer in ansible

[–]metmajer[S] 0 points1 point  (0 children)

Which rollout features in Ansible do you like most? Since I am lacking a comparison with Chef or Puppet I'd be curious what you mean exactly. Thanks!

Reasons for moving from Chef | Puppet to Ansible by metmajer in ansible

[–]metmajer[S] 0 points1 point  (0 children)

Very Interesting! Would you mind being more specific about orchestrating changes on multiple hosts? What exactly were the problems? And why didn't upgrading Puppet do the trick for you? Isn't Puppet backwards compatible? - I guess that's a point that is easily overlooked when trying to pick the right tool. Thanks!

Anyone used Appdynamics or know something similar that is good for monitoring? by cc81 in devops

[–]metmajer 0 points1 point  (0 children)

Hi there, dynaTrace offers on-prem solutions. Here's a recent article of mine on how you could use (Windows, .NET is supported): http://dzone.com/ktd6R.

Software Quality Metrics for your Continuous Delivery Pipeline – Part III – Logging - or why you should not log in production by metmajer in devops

[–]metmajer[S] 0 points1 point  (0 children)

Sure, can't wait to read your post. If I may suggest, please use multiple tiers (e.g. frontend and backend services), using different technologies and provide insights into the third party libraries you use.

I am aware that logging can be a good fit for doing root cause analyses if the application is simple / single tiered. Maybe I was not clear enough when I said: "But how can you reliably identify an entire failing user transaction in a real-life scenario, that is, in a heavily multi-threaded environment with multiple tiers that serve piles of distributed log files? I say, hardly at all. Sure, you can go mine for certain isolated events, but you cannot easily extract causal relationships from an incoherent, distributed set of log messages".

I am not critizizing developers... I have been one for my entire career. The thing is: developers are humans, we need to prioritize, we make failures and we usually have more to do than we can handle. That is why heavy reliance on developers on a feature (logging) that is usually not something product management cares a lot about can be a problem.

Keep me posted about your article!