Henderson : consul devops - Кабринский Эдуард
: 19 maja 2021, 10:32
Kabrinskiy Eduard - Devops blogspot - Кабринский Рдуард
<h1>Devops blogspot</h1>
<p>[youtube]</p>
Devops blogspot <a href="http://remmont.com">National news headlines</a> Devops blogspot
<h1>Express YourSelf !</h1>
<h3>Levels of DevOps Practice </h3>
<p>1. Values: <br />====== <br /><i><br /></i></b> <i>CAMS</i> </b> Culture Automation Measurement and Sharing</p>
<p>1.1 culture <br />1.2 automation, <br />1.3 measurement, <br /> <br />* MTTR <br />* cycle Time <br />* Costs <br />* Revenue <br />* Employee Satisfaction <br /> <br />1.4 sharing: Kizen <br /> <br />Later on, L for Lean is also added. <br /> <br /><i>CALMS</i> </b> Culture Automation Lean Measurement and Sharing <br /></p>
<p>2. Principles <br />======== <br /> <br />2.1 System thinking : Concept to Cash <br />2.2 Amplifying feedback loop <br />2.3 Continuous experiments and learning <br /> <br /> <br />3. Methods <br />======= <br /> <br />3.1 People (Who is responsible) , Process, Tools <br />3.2 Continuous Delivery <br />3.3 Lean Management <br />3.4 Change Control <br />3.5 Infrastructure as code <br /> <br />4. Practices <br />======== <br /> <br />4.1 Chaos Monkey <br />4.2 Blue / Green Deployment <br />4.3 Dependency Injection (Inversion of control) using service discovery <br />4.4 Andon Cord <br />4.5 Cloud : API driven way <br />4.6 Embedded Teams <br />4.7 Blameless Postmortem (industrial safety) should happen within 24 or 48 hours <br />4.8 Public Status Page is also about Transparent uptime <br />4.9 Developers on call <br />4.10 Incident Command System (Like fire department) <br /> <br />5. Tools <br />===== <br /> <br />Criteria for choosing tools</p>
<p>1. Tools should be programmable. Can invoke by API and CLI, not only GUI. <br />2. verifiable : events and matrix <br />3. well behave: deploy automatically, acceptance test case. it can be in form for .deb OR chef cookbook <br /> <br /><i><b>5.1 Code</b> </i>? code development and review, source code management tools, code merging <br /><b><i>5.2</i> </b><i><b>Build</b> </i>? continuous integration tools, build status <br /><b><i>5.3</i> </b><i><b>Test</b> </i>? continuous testing tools that provide feedback on business risks <br /><b><i>5.4</i> </b><i><b>Package</b> </i>? artifact repository, application pre-deployment staging <br /><b><i>5.5</i> </b><i><b>Release</b> </i>? change management, release approvals, release automation <br /><b><i>5.6</i> </b><i><b>Configure</b> </i>? infrastructure configuration and management, infrastructure as code tools (e.g. Ansible, Puppet, Chef) <br /><b><i>5.7</i> </b><i><b>Monitor</b> </i>? applications performance monitoring, end-user experience (e.g. NewRelic, Kibana, Datadog) <br /> <br /><b>Six Phases</b> of tool chain <br /> <br /><b><i>5.1 Version Control</i></b> : Git (Github OR Bigbucket) as SAS or enterprise version. Hands-on http://try.github.io/ <br /> <br /><b><i>5.2 CI systems</i></b> : Jenkins, commercial Jenkins from CloudBees, GoCD, Bamboo, Shippable, TeamCity. CI as Service : Travis CI, Circle CI <br /> <br /><b><i>5.3 Build</i> </b>: Make, Rake, Maven (Workflow approach), Gulp for front end, HashiCorp's Packer for infrastructure <br /> <br /><b><i>5.4 Test</i> </b>: Testing for developers before check in <br /> <br />5.4.1 Unit Test and code hygiene : JUnit, golint/gofmt, RuboCop, <br />Integration Testing : Robot, Protractor, Cucumber, Selenium (for UI testing), Sauce Labs from SAS for front end acceptance testing <br /> <br />5.4.2 Infrastructure Testing : Kitchen Chef <br /> <br />5.4.3 Performance Testing : Apache Bench, Meter, Apache JMeter <br /> <br />5.4.4 Security Testing : Brakeman, VeraCode, gauntlet <br />Vagrant, Otto, Docker Compose <br /> <br /><b><i>5.5 Artifact Repository</i></b> <br /> <br />Artifactory <br />Nexus <br />DockerHub <br />AWS S3 <br /> <br /><b><i>5.6</i> </b><i><b>Deployment</b></i> <br /> <br />RunDeck <br />UrbenCode <br />ThoughtWorks <br />Deployinator <br />Elastic Beanstalk <br />Octopus <br />Vamp <br />Saltstack <br />rerun <br /> <br />Most important tools are : Continuous Integration (e.g. Jenkins) and Infrastructure as a code (e.g. Puppet) <br /> <br /> <br />Containerization ? Docker, Rocket, Unik <br />Orchestration ? Kubernetes, Swarm, Mesos</p>
<p><b>Organisational culture</b> <br /> <br />1. Pathological (Power oriented) <br />2. Bureaucratic (rule oriented) <br />3. Generative (performance oriented) cooperation and inquiry <br /> <br />Processes are like training wheels: So go for minimal viable process <br /> <br />How to build Trust, Respect and eliminate blame and hostility ? <br /> <br />* Some people may introvert <br />* People think others job is easy to do <br />* bring transparency "chat ops" : Hip Chat, slack, ICR, Hubot, Lita, Cog, Err <br /> <br />Organisational boundary is also communication boundary.</p>
<h2>Devops blogspot</h2>
<h3>Devops blogspot</h3>
<p>[youtube]</p>
Devops blogspot <a href="http://remmont.com">Latest national news</a> Devops blogspot
<h4>Devops blogspot</h4>
Express YourSelf ! Levels of DevOps Practice 1. Values: ====== CAMS Culture Automation Measurement and Sharing 1.1 culture 1.2 automation, 1.3 measurement, * MTTR * cycle
<h5>Devops blogspot</h5>
Devops blogspot <a href="http://remmont.com">Devops blogspot</a> Devops blogspot
SOURCE: <h6>Devops blogspot</h6> <a href="https://dev-ops.engineer/">Devops blogspot</a> Devops blogspot
#tags#[replace: -,-Devops blogspot] Devops blogspot#tags#
Кабринский Эдуард
local news
<h1>Devops blogspot</h1>
<p>[youtube]</p>
Devops blogspot <a href="http://remmont.com">National news headlines</a> Devops blogspot
<h1>Express YourSelf !</h1>
<h3>Levels of DevOps Practice </h3>
<p>1. Values: <br />====== <br /><i><br /></i></b> <i>CAMS</i> </b> Culture Automation Measurement and Sharing</p>
<p>1.1 culture <br />1.2 automation, <br />1.3 measurement, <br /> <br />* MTTR <br />* cycle Time <br />* Costs <br />* Revenue <br />* Employee Satisfaction <br /> <br />1.4 sharing: Kizen <br /> <br />Later on, L for Lean is also added. <br /> <br /><i>CALMS</i> </b> Culture Automation Lean Measurement and Sharing <br /></p>
<p>2. Principles <br />======== <br /> <br />2.1 System thinking : Concept to Cash <br />2.2 Amplifying feedback loop <br />2.3 Continuous experiments and learning <br /> <br /> <br />3. Methods <br />======= <br /> <br />3.1 People (Who is responsible) , Process, Tools <br />3.2 Continuous Delivery <br />3.3 Lean Management <br />3.4 Change Control <br />3.5 Infrastructure as code <br /> <br />4. Practices <br />======== <br /> <br />4.1 Chaos Monkey <br />4.2 Blue / Green Deployment <br />4.3 Dependency Injection (Inversion of control) using service discovery <br />4.4 Andon Cord <br />4.5 Cloud : API driven way <br />4.6 Embedded Teams <br />4.7 Blameless Postmortem (industrial safety) should happen within 24 or 48 hours <br />4.8 Public Status Page is also about Transparent uptime <br />4.9 Developers on call <br />4.10 Incident Command System (Like fire department) <br /> <br />5. Tools <br />===== <br /> <br />Criteria for choosing tools</p>
<p>1. Tools should be programmable. Can invoke by API and CLI, not only GUI. <br />2. verifiable : events and matrix <br />3. well behave: deploy automatically, acceptance test case. it can be in form for .deb OR chef cookbook <br /> <br /><i><b>5.1 Code</b> </i>? code development and review, source code management tools, code merging <br /><b><i>5.2</i> </b><i><b>Build</b> </i>? continuous integration tools, build status <br /><b><i>5.3</i> </b><i><b>Test</b> </i>? continuous testing tools that provide feedback on business risks <br /><b><i>5.4</i> </b><i><b>Package</b> </i>? artifact repository, application pre-deployment staging <br /><b><i>5.5</i> </b><i><b>Release</b> </i>? change management, release approvals, release automation <br /><b><i>5.6</i> </b><i><b>Configure</b> </i>? infrastructure configuration and management, infrastructure as code tools (e.g. Ansible, Puppet, Chef) <br /><b><i>5.7</i> </b><i><b>Monitor</b> </i>? applications performance monitoring, end-user experience (e.g. NewRelic, Kibana, Datadog) <br /> <br /><b>Six Phases</b> of tool chain <br /> <br /><b><i>5.1 Version Control</i></b> : Git (Github OR Bigbucket) as SAS or enterprise version. Hands-on http://try.github.io/ <br /> <br /><b><i>5.2 CI systems</i></b> : Jenkins, commercial Jenkins from CloudBees, GoCD, Bamboo, Shippable, TeamCity. CI as Service : Travis CI, Circle CI <br /> <br /><b><i>5.3 Build</i> </b>: Make, Rake, Maven (Workflow approach), Gulp for front end, HashiCorp's Packer for infrastructure <br /> <br /><b><i>5.4 Test</i> </b>: Testing for developers before check in <br /> <br />5.4.1 Unit Test and code hygiene : JUnit, golint/gofmt, RuboCop, <br />Integration Testing : Robot, Protractor, Cucumber, Selenium (for UI testing), Sauce Labs from SAS for front end acceptance testing <br /> <br />5.4.2 Infrastructure Testing : Kitchen Chef <br /> <br />5.4.3 Performance Testing : Apache Bench, Meter, Apache JMeter <br /> <br />5.4.4 Security Testing : Brakeman, VeraCode, gauntlet <br />Vagrant, Otto, Docker Compose <br /> <br /><b><i>5.5 Artifact Repository</i></b> <br /> <br />Artifactory <br />Nexus <br />DockerHub <br />AWS S3 <br /> <br /><b><i>5.6</i> </b><i><b>Deployment</b></i> <br /> <br />RunDeck <br />UrbenCode <br />ThoughtWorks <br />Deployinator <br />Elastic Beanstalk <br />Octopus <br />Vamp <br />Saltstack <br />rerun <br /> <br />Most important tools are : Continuous Integration (e.g. Jenkins) and Infrastructure as a code (e.g. Puppet) <br /> <br /> <br />Containerization ? Docker, Rocket, Unik <br />Orchestration ? Kubernetes, Swarm, Mesos</p>
<p><b>Organisational culture</b> <br /> <br />1. Pathological (Power oriented) <br />2. Bureaucratic (rule oriented) <br />3. Generative (performance oriented) cooperation and inquiry <br /> <br />Processes are like training wheels: So go for minimal viable process <br /> <br />How to build Trust, Respect and eliminate blame and hostility ? <br /> <br />* Some people may introvert <br />* People think others job is easy to do <br />* bring transparency "chat ops" : Hip Chat, slack, ICR, Hubot, Lita, Cog, Err <br /> <br />Organisational boundary is also communication boundary.</p>
<h2>Devops blogspot</h2>
<h3>Devops blogspot</h3>
<p>[youtube]</p>
Devops blogspot <a href="http://remmont.com">Latest national news</a> Devops blogspot
<h4>Devops blogspot</h4>
Express YourSelf ! Levels of DevOps Practice 1. Values: ====== CAMS Culture Automation Measurement and Sharing 1.1 culture 1.2 automation, 1.3 measurement, * MTTR * cycle
<h5>Devops blogspot</h5>
Devops blogspot <a href="http://remmont.com">Devops blogspot</a> Devops blogspot
SOURCE: <h6>Devops blogspot</h6> <a href="https://dev-ops.engineer/">Devops blogspot</a> Devops blogspot
#tags#[replace: -,-Devops blogspot] Devops blogspot#tags#
Кабринский Эдуард
local news