On 6/12/2011 8:52 AM, Derek J. Balling wrote:
On Jun 12, 2011, at 2:48 PM, [email protected] <mailto:[email protected]> wrote:
I'm on a new mail client and accidentally responded to just Derek.
Heh, then ignore my "direct to you" reply. :-)
while a good pxe setup is great, and really, the only reasonable way
to manage a fleet once it gets beyond a certain size, I think it's silly
to call it "the cloud" because that sort of thing has been the way it's
done at larger places for most of my career.
Well, we can have that whole discussion about the word "DevOps", too,
no? It's just a new name for the same flavor.
On a side note, my parent company set up a new dev wiki. It's a great
thing, with a good opportunity to share programming stuff between teams
and sister companies which is something we've probably not really done
as much of as we should have. Part of the wiki describes the teams
there which is great because we've had little transparency there for a
while. Amongst them is a new DevOps team. The page starts with the
usual rationale for a devops team, all stuff that makes sense,
especially given the nature and size of the operation. It's a choice
I'd agree with, we could do with a team that spans both dev and ops but
across all the teams there. Except the team does just three main
things: Deploys, Monitors and Supports. No Dev, other than arguably
scripting stuff for monitoring. We looked at it, compared it to the job
spec for the sysadmin jr we hired and rather tongue-in-cheek started
discussing a possible job title change for him.
Paul
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
