Comments on: Getting Started With DevOps http://www.thesimplelogic.com/2010/02/17/getting-started-with-devops/ Thu, 12 Aug 2010 15:03:08 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: The Simple Logic » Blog Archive » DevOps Documentation http://www.thesimplelogic.com/2010/02/17/getting-started-with-devops/comment-page-1/#comment-7 The Simple Logic » Blog Archive » DevOps Documentation Wed, 24 Feb 2010 03:42:21 +0000 http://www.thesimplelogic.com/?p=6#comment-7 [...] a previous entry I wrote that the key to removing the wall between developers and operations is communication. I [...] [...] a previous entry I wrote that the key to removing the wall between developers and operations is communication. I [...]

]]> By: Adam Fletcher http://www.thesimplelogic.com/2010/02/17/getting-started-with-devops/comment-page-1/#comment-6 Adam Fletcher Mon, 22 Feb 2010 20:04:09 +0000 http://www.thesimplelogic.com/?p=6#comment-6 Hi Geoffrey, I agree with you on having developers see into the support queue and to have the respond to support tickets (and I agree it doesn't scale). You may find that as the organization grows and the developers are put on work that is more "important" then answering support tickets you'll still want to rotate developers into handling some support tickets for a week at a time, or having a way for support personnel escalate some tickets to developers very quickly. That's an interesting problem that I haven't spent much time thinking about, but fits well with the core tenants of DevOps as I see them. Hi Geoffrey,

I agree with you on having developers see into the support queue and to have the respond to support tickets (and I agree it doesn’t scale). You may find that as the organization grows and the developers are put on work that is more “important” then answering support tickets you’ll still want to rotate developers into handling some support tickets for a week at a time, or having a way for support personnel escalate some tickets to developers very quickly. That’s an interesting problem that I haven’t spent much time thinking about, but fits well with the core tenants of DevOps as I see them.

]]> By: Geoffrey Thomas http://www.thesimplelogic.com/2010/02/17/getting-started-with-devops/comment-page-1/#comment-5 Geoffrey Thomas Mon, 22 Feb 2010 03:34:58 +0000 http://www.thesimplelogic.com/?p=6#comment-5 My experiences are different because my big projects are all for an all-volunteer student group, but I've always found the split between dev and ops to be rather weird, by which I think I mean that it's not a division that occurs to the unprejudiced mind. All of our projects' production servers are maintained by the core devs, and the development servers are accessible to the entire dev team, and they're kept in sync as to how they're run. The occasional time we need to interact with a separate ops team (e.g., when we need beefier hardware or VMs run by the school), it's actually kind of odd for us as developers not to be assumed to be running and installing the whole machine. If I'm going to run this service, I want either myself or one of the other developers to have made sure the machine is the way we want it. We also do what I guess you'd call DevOpsHelpdesk; the all service developers/maintainers receive e-mails to the support queue. This helps us be extremely responsive to users' questions and have a very good sense of what sorts of things our users would like to see and are using our stuff for, but it's pretty close to reaching the point where it doesn't scale. Still, I think it's good for developers and maintainers to be regularly watching the support queues; your help desk might just look at the system and think something isn't possible, where the developers might have had it as an easy feature all along that they haven't implemented because they didn't think there was demand for it. My experiences are different because my big projects are all for an all-volunteer student group, but I’ve always found the split between dev and ops to be rather weird, by which I think I mean that it’s not a division that occurs to the unprejudiced mind. All of our projects’ production servers are maintained by the core devs, and the development servers are accessible to the entire dev team, and they’re kept in sync as to how they’re run. The occasional time we need to interact with a separate ops team (e.g., when we need beefier hardware or VMs run by the school), it’s actually kind of odd for us as developers not to be assumed to be running and installing the whole machine. If I’m going to run this service, I want either myself or one of the other developers to have made sure the machine is the way we want it.

We also do what I guess you’d call DevOpsHelpdesk; the all service developers/maintainers receive e-mails to the support queue. This helps us be extremely responsive to users’ questions and have a very good sense of what sorts of things our users would like to see and are using our stuff for, but it’s pretty close to reaching the point where it doesn’t scale. Still, I think it’s good for developers and maintainers to be regularly watching the support queues; your help desk might just look at the system and think something isn’t possible, where the developers might have had it as an easy feature all along that they haven’t implemented because they didn’t think there was demand for it.

]]> By: What DevOps means to me… » Kartar.Net http://www.thesimplelogic.com/2010/02/17/getting-started-with-devops/comment-page-1/#comment-4 What DevOps means to me… » Kartar.Net Fri, 19 Feb 2010 03:56:43 +0000 http://www.thesimplelogic.com/?p=6#comment-4 [...] the last year or so a bunch of presumptuous European sysadmins and developers, joined by some of their American brethren and even a couple of us antipodeans (there are others too!) have been talking [...] [...] the last year or so a bunch of presumptuous European sysadmins and developers, joined by some of their American brethren and even a couple of us antipodeans (there are others too!) have been talking [...]

]]>