diff options
| author | Franck Cuny <franckcuny@gmail.com> | 2016-07-02 20:06:31 -0700 |
|---|---|---|
| committer | Franck Cuny <franckcuny@gmail.com> | 2016-07-02 20:06:31 -0700 |
| commit | 4b8e43f75b394a4e6169884fbfb4c606865c6a22 (patch) | |
| tree | 48cae6b8e8f9b68cae29676d8a15cb3ddbfcccda /content/post/2012-12-16-about-devops.md | |
| parent | Stop using Jekyll. (diff) | |
| download | lumberjaph-4b8e43f75b394a4e6169884fbfb4c606865c6a22.tar.gz | |
Import migration from Jekyll to Hugo.
All the posts were converted, and the layout is created. This looks like
it works just fine.
Diffstat (limited to 'content/post/2012-12-16-about-devops.md')
| -rw-r--r-- | content/post/2012-12-16-about-devops.md | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/content/post/2012-12-16-about-devops.md b/content/post/2012-12-16-about-devops.md new file mode 100644 index 0000000..a292689 --- /dev/null +++ b/content/post/2012-12-16-about-devops.md @@ -0,0 +1,47 @@ +--- +date: 2012-12-16T00:00:00Z +title: About DevOps +--- + +There's a lot of talk about what is or what is not DevOps, and I'll +throw my opinion in the mix. + +Until a few weeks ago, at [work](http://saymedia.com), we had mostly +two teams: the engineering team and the ops team. Our workflow was +(to simplify) the following: + + * engineers develop services and applications + * they push their change to Jenkins + * a build pass and is pushed to CI + * a few times a week, engineers ask Ops to push the change to + production + +There's already a lot of articles about the kind of frictions created +by this (who owns what; engineers would blame ops when the push was +failing (or the other way around); it's hard for ops to know what's +wrong when something is broken in production; etc). + +A few weeks ago it was decided to create a new team to improve +engineers efficiency, and the team was named "DevOps". At first I was +not sure it was the right name for this team, but now I don't think it +matters. + +I was not sure the name was appropriate because of this +[article](http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/) +(and a few other to respond), explaining why you don't want a DevOps +team, but instead you want the whole organization to be DevOps. We +need engineers to own their applications, to be able to push when they +want, but also to monitor, know what's wrong or slow, etc. + +The **work** [hachi](https://github.com/hachi) and I will have to do is to +help engineers and ops to *be* the DevOps. Our team responsibility is +to choose, evaluate and integrate tools. We will also provide +libraries, documentation, training and support. *We* are not the +DevOps. Our **goals** are to create this culture, to give more +responsibilities to engineers, and to free Ops from the work of +pushing code. The **success** of this team will be measured by the +adoption of our work by engineers and ops. + +So yes, I agree that you don't want a dedicated DevOps team, but you +still need a team coming from different background (hachi is coming +from Ops and I'm an engineer) to build that culture. |