started formulating the term DevOps. Main consideration being increased feedback loops between business, software delivery and operations. • DevOps << Development IT Operations idea?
started formulating the term DevOps. Main consideration being increased feedback loops between business, software delivery and operations. • DevOps << Development IT Operations • CAMS : Culture, Automation, Measurement, Sharing soon became, CALMS ~ Lean CAMS Now even Wikipedia has a decent description ( after loads of revision ) around the Idea. Go read. Form your own opinion. idea? John Willis said Jez Humble added
retro ◦ one product one team ~ you build you run (amazon) ◦ trust your people or stop being agile • team ◦ mixed stand-ups ◦ devs rotation for tasks, collaborating all the time ◦ devs and ops, both on release call and alert panel
retro ◦ one product one team ~ you build you run (amazon) ◦ trust your people or stop being agile • team ◦ mixed stand-ups ◦ devs rotation for tasks, collaborating all the time ◦ devs and ops, both on release call and alert panel • personal ◦ broaden perspective beyond localhost ◦ find a common ground between change and stability ◦ automate and measure every aspect of ecosystem
them ◦ evaluate scalability over size, geo-location & time ◦ analyze current practices and the shift required • development ◦ repeatable and reliable ◦ reviewable and rapid ◦ resilient and robust
them ◦ evaluate scalability over size, geo-location & time ◦ analyze current practices and the shift required • development ◦ repeatable and reliable ◦ reviewable and rapid ◦ resilient and robust • delivery ◦ automate the automation ◦ secure the security ◦ pin the lynchpin, and get rolling
provide the entire product. $#!t happens Need to 'Monitor' every important aspect of product and product ambience. Place 'Alert' on events, that you can wiki-fy on how to handle.
Softwares live in varied environments like QA/Staging/Production. To understand how our product works, we need to notice its activities on environments. Log & Analyze
tasks) Platform • IaaS (no physical maintenance) Infras. • NaaS (seriously, you Dinosaurus) Null automate everything required for an auto- scaled environment on that NodeModel
requirements, less testing, bureaucracy, slow communication • Amplify Learning instead of adding to documentation or planning, try & learn • Decide as late as possible until they can be made on facts not assumptions. Set-based development flow allows better solutions. • Deliver as fast as possible, without speed decisions can't be delayed. • Empower the team, find capable people and let them use their capability. Enable their access to customer. • Build integrity in product quality, keep it flexible, maintainable, efficient & responsive. Solve requirements simultaneously as the information flows in both direction, not sequentially. • See the whole... larger the system, the more organizations &/or teams involved, greater the importance of having well defined relationship. A part of strong team is much more beneficial than minimum interaction departments.
abhishekkr
kenjikondobai
re_taro
amixedcolor
smt7174
tubone24
kitsuya0828
.jpeg){kind=avatar}
ostk0069
shujisado
emiki
takumiogawa
kakehashi
lycorp_recruit_jp
csswizardry
bluesmoon
erikaheidi
maltzj
panda_program
yeseniaperezcruz
brianwarren
bkeepers
kevinliebholz
ufuk
addyosmani
philnash
