Comments on: Three Aspects of DevOps: What’s in a word http://cuddletech.com/blog/?p=624&utm_source=rss&utm_medium=rss&utm_campaign=three-aspects-of-devops-whats-in-a-word The Blog of Ben Rockwood Tue, 21 May 2013 16:20:16 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Ремонт холодильников http://cuddletech.com/blog/?p=624#comment-25376 Ремонт холодильников Sun, 24 Jul 2011 11:23:03 +0000 http://cuddletech.com/blog/?p=624#comment-25376 Бесподобно это админ молодец что выложил :smile: --------------------------------- <a href="http://www.gorodservis.ru" rel="nofollow">ремонт холодильников</a> Бесподобно это админ молодец что выложил
:smile:

———————————
ремонт холодильников

]]> By: benr http://cuddletech.com/blog/?p=624#comment-25369 benr Fri, 22 Jul 2011 16:58:41 +0000 http://cuddletech.com/blog/?p=624#comment-25369 Exactly! The term "cloud" itself is SO ambiguous that NIST writes a separate Special Publication just to define it. Exactly! The term “cloud” itself is SO ambiguous that NIST writes a separate Special Publication just to define it.

]]> By: Svyatoslav Pidgorny http://cuddletech.com/blog/?p=624#comment-25351 Svyatoslav Pidgorny Sun, 17 Jul 2011 03:33:44 +0000 http://cuddletech.com/blog/?p=624#comment-25351 “What is Cloud?” NIST answers the question. The definition of cloud is http://csrc.nist.gov/publications/drafts/800-145/Draft-SP-800-145_cloud-definition.pdf. And it's quite unambiguous. “What is Cloud?” NIST answers the question. The definition of cloud is http://csrc.nist.gov/publications/drafts/800-145/Draft-SP-800-145_cloud-definition.pdf. And it’s quite unambiguous.

]]> By: benr http://cuddletech.com/blog/?p=624#comment-25234 benr Sun, 26 Jun 2011 22:10:58 +0000 http://cuddletech.com/blog/?p=624#comment-25234 Let me add the disclaimer here that this post is about separation of context. I use examples here only to help people understand the separation of contexts. WIthin the DevOps world these various areas are maturing at a newly accelerated pace and are changing quickly. Therefore, I am NOT trying to be prescriptive. In 6 months the list above will look very different, just as it would have looked different 6 months ago... however, the model of 3 Aspects as 3 phases of the DevOps Transformation is still true. Let me add the disclaimer here that this post is about separation of context. I use examples here only to help people understand the separation of contexts. WIthin the DevOps world these various areas are maturing at a newly accelerated pace and are changing quickly.

Therefore, I am NOT trying to be prescriptive. In 6 months the list above will look very different, just as it would have looked different 6 months ago… however, the model of 3 Aspects as 3 phases of the DevOps Transformation is still true.

]]> By: benr http://cuddletech.com/blog/?p=624#comment-25233 benr Sun, 26 Jun 2011 22:07:44 +0000 http://cuddletech.com/blog/?p=624#comment-25233 Again, really depends on the context. Ops teams are looking at using CI for testing config management and deployment methodology (Dev > Ops)... at the same time, dev is using CI is already being used in development teams where the concept really comes from, they are just doing more operational testing during CI (Dev < Ops). If we step back more broadly, the word "testing" is loaded with contextual interpretation. Ops does testing. Dev does testing. They are very different. The beauty of DevOps is those differing methods crossing teams en route to Phase 3. Thats the true beauty of DevOps, exploring differing definitions. "We do testing." "We do testing too." "Wait, your testing is really weird to me, can you explain how you test?" "Sure, lets see where we have commonality and differentiation and see what we can learn." "Sweeeeeeeeeeeet." DevOps at its finest. Again, really depends on the context. Ops teams are looking at using CI for testing config management and deployment methodology (Dev > Ops)… at the same time, dev is using CI is already being used in development teams where the concept really comes from, they are just doing more operational testing during CI (Dev < Ops).

If we step back more broadly, the word “testing” is loaded with contextual interpretation. Ops does testing. Dev does testing. They are very different. The beauty of DevOps is those differing methods crossing teams en route to Phase 3.

Thats the true beauty of DevOps, exploring differing definitions. “We do testing.” “We do testing too.” “Wait, your testing is really weird to me, can you explain how you test?” “Sure, lets see where we have commonality and differentiation and see what we can learn.” “Sweeeeeeeeeeeet.” DevOps at its finest.

]]> By: botchagalupe http://cuddletech.com/blog/?p=624#comment-25231 botchagalupe Sun, 26 Jun 2011 16:38:24 +0000 http://cuddletech.com/blog/?p=624#comment-25231 Would strongly argue testing is in phase II as well. I don't CI is CI w/o test... Would strongly argue testing is in phase II as well. I don’t CI is CI w/o test…

]]> By: benr http://cuddletech.com/blog/?p=624#comment-25230 benr Sun, 26 Jun 2011 15:10:03 +0000 http://cuddletech.com/blog/?p=624#comment-25230 Testing in which of the 3 context? In Dev > Ops the movement is to emulate test-driven-design with monitoring-driven-design, that is to create the monitoring alert before implementing the feature. In Dev < Ops the move is to supplement unit testing with continuous integration using tools like Hudson. In Dev Ops we're doing both and likely have peer review by both teams in addition to the above. My examples are just that, examples, not a complete list, hence "etc." You illustrate the point I'm trying to make perfectly. What does DevOps say about testing? It entirely depends on which of the 3 contexts your coming from. If you lack the context the question is confusing and incomplete. That confusion slows down the conversation and starts contention. Testing in which of the 3 context? In Dev > Ops the movement is to emulate test-driven-design with monitoring-driven-design, that is to create the monitoring alert before implementing the feature. In Dev < Ops the move is to supplement unit testing with continuous integration using tools like Hudson. In Dev Ops we’re doing both and likely have peer review by both teams in addition to the above.

My examples are just that, examples, not a complete list, hence “etc.”

You illustrate the point I’m trying to make perfectly. What does DevOps say about testing? It entirely depends on which of the 3 contexts your coming from. If you lack the context the question is confusing and incomplete. That confusion slows down the conversation and starts contention.

]]> By: Mark Tomlinson http://cuddletech.com/blog/?p=624#comment-25229 Mark Tomlinson Sun, 26 Jun 2011 13:33:27 +0000 http://cuddletech.com/blog/?p=624#comment-25229 So - what happened to testing? So – what happened to testing?

]]>