Some time ago I set about creating an Android application that could emulate some of the features of Knife from the convenience of your phone. The biggest hurdle was authenticating with the AP.
From time to time I’m working with new recruits and bringing them up to speed in operations. The first thing I emphasize is care with destructive commands.
If you’re building a community project that’s aimed at developers, then throw the content on GitHub. In my case I have the entire site on there too but I think that’s secondary.
This is a guest post I wrote in the Puppetlabs blog for their Module of the Week program about the MaestroDev/maven module we created.
If you haven’t started looking at DevOps in your organization, I highly recommend you do. Not only will it keep you competitive, but it may be the key factor to differentiating your organization from the rest of the market.
I recently created a rubygem console utility to get focused information about your Go Continuous Delivery pipeline easily; no more switching again to browsers. It's called ci-go-nfo.
If you are throwing release parties, or just relieved every time the release doesn’t go wrong, it’s probably time to look into DevOps techniques and automating your releases. It’s not like the business is going to want to slow down the pace.
wWhen discussing the challenges of continious deployment for B2B services with SLAs, we got side tracked discussing using Selenium and Nagios in production. I would recommend that anyone else give this strategy a try.
Hands-On Visual Studio is a great website that will provide videos, labs and many other things with multi-lingual support, I believe it will become one of the primary resources for developers all over the world in the next years, stay close and tuned there will be update everyday…..
The status quo seems to favour bundler on the development side, but RPMs on the production side (if you judge these decisions based on what developers and ops folk prefer, generally).
Everyone is scaling horizontally and everyone needs a repeatable, automated process to set up instances, deploy software, and perform tasks that were previously manual. This trend is called Devops, and in this article I’m going to talk about where Nexus should fit into your automation effort.
Technical Debt in programming is a topic for the ages. It tends to permeate round table conversations and almost pre-dates physical development. Although its accumulation has no discernible pattern, time and money are common factors.
A new version of Go, the Continuous Delivery managment tool by ThoughtWorks Studios, is up for grabs today with a feature that is going to help package the right versions of your components and eliminate spurious builds.
What happens when “sometime in the future” is now? How much debt is too much to carry? When do you have to pay if off?
It’s a little-known fact that Phusion Passenger, the awesome Rack webserver module, can also competently talk WSGI as well as fit into the Rack ecosystem. This means that not only can you run your Rack and Rails applications through it, but also your WSGI-compliant Python applications.
Oftentimes we find users struggle with figuring out where to start when reviewing their log data, and what they should be looking out for. A common question we get is: "So I’ve a bunch of linux boxes, I’m running a LAMP stack, what should I be looking out for in my logs”.
We all know that protocols are an essential building block of our craft. So why not apply the ‘protocol’ idea to Devops? Let’s try and see how the idea of protocols can help us improve the adoption of a Devops culture.
IT people often try and justify new technology with technology reasoning. It's analogous to answering a question with another question.
Monitoring configuration is complicated, and the depths that you can configure alerts and tests seems endless. It may seem like a waste of time to invest in some options, but others can really help you eliminate states that send hundreds of alerts.
Learn abourt using Vagrant, Puppet, and Puppet modules to manage Maven dependencies, PostgreSQL, Tomcat, and apache as examples.
Learn some key Cloud DevOps patterns from a master in the IT space - John Willis
Recently I had a challenge of getting capistrano deployments working from jenkins installed on a RHEL box. The problem seemed to be down to the fact that ssh-agent isn’t running for the daemon process that jenkins runs as for whatever reason and it is needed to do ssh agent forwarding (which is what I do so I can use the ssh key on the jenkins server to check code out from github on remote servers).
We’re using logstash to collect all the logs across the different machines that we use in various environments and had noticed that on some of the nodes log files which we’d told the logstash-client to track weren’t being collected.
Recently I discovered the power of Vagrant and Puppet. They allow me to automate all the steps I used to manually make before. Here I test drive the process of automatically configuring a Hadoop cluster in virtual machines for a fully distributed mode.
Today, there are two broad categories of provisioning and deployment automation. The first are convergent tools such as Puppet and Chef. The second are directed automation tools.