We’ve hit the road and rounded up local industry leaders Heather Mickman, Bridget Kromhout, Andy Domeier, and Ben Overmyer for this incredible half-day event. These speakers, from Target, Pivotal, Minneapolis Star Tribune, and SPS Commerce, shared real-life DevOps implementation stories and suggestions to help you on your DevOps journey.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
DSC UTeM DevOps Session#1: Intro to DevOps Presentation SlidesDSC UTeM
DevOps has been such a buzzword in the IT field nowadays. If you look into job postings, you might be surprised to find terms like "work with DevOps team", "work in an agile team" etc.
What is DevOps? What is agile? And why all these? 樂
Join us on 24 May 2021, where we have a short session to explore on the events that led to the trend nowadays
We will be exploring on the current trends, tech stacks and the existence of DevOps itself! 朗
Mark this date on your calendar and we'll see you there!
* Note: This is an introductory "brief overview" session that gives you context on our upcoming events.
Slides by KwongTN.
The Path of DevOps Enlightenment for InfoSecJames Wickett
Presentation at All Day DevOps on the path for infosec and security engineers in the modern software development flow and their place in DevOps. The journey is important but the destination is critical.
Keeping The Auditor Away: DevOps Audit Compliance Case StudiesGene Kim
GenOrganizations and development teams are moving beyond waterfall models to those embracing a continuous delivery/DevOps-style set of processes. The deployment of doing tens, hundreds, or even thousands of deploys per day as 'normal' does not align to the SDLC, separation of duties, and common controls expected by auditors.
In this presentation, we will describe what auditors look for in a compliance audit, how to develop alternate control procedures that fulfill those reporting requirements, how to avoid “red flags” that indicate inadequate controls, and real world case studies and reporting artifacts.
Gene Kim has been studying high performing IT organizations since 1999 and helped develop the SOX scoping guidelines with the Institute of Internal Auditors in 2005. James DeLuccia IV is the leader for the Ernst & Young Americas Certification Services, James oversees all of the audits against common industry standards, and champions several global program implementation roll-outs. Developing and 'translating' the control environment behaviors of clients, such as Google, Amazon, Workday, and others is difficult. This discussion will bridge the needs of auditors with the community of developers by sharing examples, discussing the assurance expectations, and how to communicate to pass an audit.
The History of DevOps (and what you need to do about it)dev2ops
The document discusses the history and evolution of DevOps. It traces the origins of DevOps back to 2007 when the terms "DevOps" and "Agile Infrastructure" first emerged. It then summarizes the rise in DevOps conferences and communities from 2009 onward. The document also outlines key findings that DevOps adopters see significantly faster lead times, higher deployment frequencies, better change success rates, and faster recovery times compared to non-adopters. Additionally, DevOps teams are more likely to exceed goals for profitability, market share and productivity. The document argues that organizations should focus on fast feedback loops, continuous improvement and adopting an "Improvement System" like DevOps Kaizen in order to see these benefits as a
Jeff Gallimore, Gene Kim, and Tim Buntel discuss the tactics behind expanding DevOps in the enterprise, in this great presentation. Watch the on-demand webinar here: http://bit.ly/2xygVQ7
2013 Velocity DevOps Metrics -- It's Not Just For WebOps Any More!Gene Kim
The document summarizes key findings from a 2012 survey on DevOps practices conducted by Puppet Labs, Gene Kim, and Jez Humble. The survey had over 4000 responses and aimed to understand the link between DevOps behaviors and performance. Key findings included that high performing DevOps teams deployed code much more frequently (30x more), had significantly shorter lead times for changes (8000x shorter), and were more reliable with fewer failed changes and faster mean time to restore service. Technical practices like infrastructure automation and version control correlated strongly with better performance. Organizations that adopted DevOps practices over 12 months prior performed significantly better. The document also discusses challenges in measuring culture and psychographics in DevOps.
Innotech Austin 2017: The Path of DevOps Enlightenment for InfoSecJames Wickett
Innotech Austin 2017: The Path of DevOps Enlightenment for InfoSec
Security as we have known it has completely changed. Through challenges from the outside and from within there is a wholesale conversion happening across the industry where DevOps and Security are joining forces. This talk is a hybrid of inspiration and pragmatism for dealing with the new landscape.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
DSC UTeM DevOps Session#1: Intro to DevOps Presentation SlidesDSC UTeM
DevOps has been such a buzzword in the IT field nowadays. If you look into job postings, you might be surprised to find terms like "work with DevOps team", "work in an agile team" etc.
What is DevOps? What is agile? And why all these? 樂
Join us on 24 May 2021, where we have a short session to explore on the events that led to the trend nowadays
We will be exploring on the current trends, tech stacks and the existence of DevOps itself! 朗
Mark this date on your calendar and we'll see you there!
* Note: This is an introductory "brief overview" session that gives you context on our upcoming events.
Slides by KwongTN.
The Path of DevOps Enlightenment for InfoSecJames Wickett
Presentation at All Day DevOps on the path for infosec and security engineers in the modern software development flow and their place in DevOps. The journey is important but the destination is critical.
Keeping The Auditor Away: DevOps Audit Compliance Case StudiesGene Kim
GenOrganizations and development teams are moving beyond waterfall models to those embracing a continuous delivery/DevOps-style set of processes. The deployment of doing tens, hundreds, or even thousands of deploys per day as 'normal' does not align to the SDLC, separation of duties, and common controls expected by auditors.
In this presentation, we will describe what auditors look for in a compliance audit, how to develop alternate control procedures that fulfill those reporting requirements, how to avoid “red flags” that indicate inadequate controls, and real world case studies and reporting artifacts.
Gene Kim has been studying high performing IT organizations since 1999 and helped develop the SOX scoping guidelines with the Institute of Internal Auditors in 2005. James DeLuccia IV is the leader for the Ernst & Young Americas Certification Services, James oversees all of the audits against common industry standards, and champions several global program implementation roll-outs. Developing and 'translating' the control environment behaviors of clients, such as Google, Amazon, Workday, and others is difficult. This discussion will bridge the needs of auditors with the community of developers by sharing examples, discussing the assurance expectations, and how to communicate to pass an audit.
The History of DevOps (and what you need to do about it)dev2ops
The document discusses the history and evolution of DevOps. It traces the origins of DevOps back to 2007 when the terms "DevOps" and "Agile Infrastructure" first emerged. It then summarizes the rise in DevOps conferences and communities from 2009 onward. The document also outlines key findings that DevOps adopters see significantly faster lead times, higher deployment frequencies, better change success rates, and faster recovery times compared to non-adopters. Additionally, DevOps teams are more likely to exceed goals for profitability, market share and productivity. The document argues that organizations should focus on fast feedback loops, continuous improvement and adopting an "Improvement System" like DevOps Kaizen in order to see these benefits as a
Jeff Gallimore, Gene Kim, and Tim Buntel discuss the tactics behind expanding DevOps in the enterprise, in this great presentation. Watch the on-demand webinar here: http://bit.ly/2xygVQ7
2013 Velocity DevOps Metrics -- It's Not Just For WebOps Any More!Gene Kim
The document summarizes key findings from a 2012 survey on DevOps practices conducted by Puppet Labs, Gene Kim, and Jez Humble. The survey had over 4000 responses and aimed to understand the link between DevOps behaviors and performance. Key findings included that high performing DevOps teams deployed code much more frequently (30x more), had significantly shorter lead times for changes (8000x shorter), and were more reliable with fewer failed changes and faster mean time to restore service. Technical practices like infrastructure automation and version control correlated strongly with better performance. Organizations that adopted DevOps practices over 12 months prior performed significantly better. The document also discusses challenges in measuring culture and psychographics in DevOps.
Innotech Austin 2017: The Path of DevOps Enlightenment for InfoSecJames Wickett
Innotech Austin 2017: The Path of DevOps Enlightenment for InfoSec
Security as we have known it has completely changed. Through challenges from the outside and from within there is a wholesale conversion happening across the industry where DevOps and Security are joining forces. This talk is a hybrid of inspiration and pragmatism for dealing with the new landscape.
What the smartest brands know about CX ... and what they still aren't doing a...Dynatrace
Dr. Natalie Petouhoff and Steve Trimbo presented on optimizing customer experience through better digital experience management. They discussed how most companies have separate IT and customer experience teams that do not collaborate effectively. This leads to poor customer digital experiences despite investments in customer experience. They proposed assessing an organization's digital experience management maturity across five dimensions and collaborating across teams to improve digital performance and close the gap between customer experience and digital experience.
Two years ago at Devoxx UK we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The large scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important, but equally you must understand specific deployment technologies, security issues, operational reliability, and how to drive organisational transformation. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same. Join us to learn how you can apply this within your team and company.
Winnipeg ISACA Security is Dead, Rugged DevOpsGene Kim
This document summarizes a presentation given by Gene Kim on infosec and DevOps. It discusses research that found high performing IT organizations have fewer security issues and implement changes more successfully. The presentation introduces the concepts of Rugged software development and DevOps. It provides an overview of how to implement DevOps through systems thinking, amplifying feedback loops, and developing a culture of experimentation. Key aspects include integrating operations, security and development teams and processes. The goal is to reduce issues and improve flow to help the business.
I apologize, but I do not have enough context to understand the full meaning of your question. Could you please rephrase or provide some additional details?
Deck for the Global Scrum Gathering in Austin, TX on May 22, 2019.
Summary:
Sometimes organizations that are going through an agile transformation complain that they aren’t getting the benefits that they expected, especially as it’s related to quality and sustaining their pace of delivery. One of the possible reasons could be that insufficient attention has been given to performing the technical practices that support the agile values and principles. One of the big problems that I have seen is development teams not doing the engineering practices and managers de-emphasizing or “not allowing” developers do them. We need to renew the emphasis on agile engineering practices and embrace the ideas of software craftsmanship – without this, agility will suffer. Join in the session as we talk about the relationship of Agile development and code quality and how lack of technical excellence impacts maintainability and time to market. Then we’ll review some agile engineering practices and recommendations on how to get started.
Learning Objectives:
What is clean code Description of technical practices Why lack of technical excellence can negatively impact the team's ability to sustain their delivery pace.
Inextricably linked reproducibility and productivity in data science and ai ...source{d}
In this talk Mark Coleman presents his team's research comparing the evolution of Software Development & DevOps with that of Data Science & AI.
Because it is more complex and has far more moving parts, Data Science & AI is where Software Development was in 1999: people are emailing and Slacking notebooks to each other, due to a lack of appropriate tooling. There are few CI/CD pipelines and model health monitoring is scarce. A lot that could be automated is still manual. And teams are siloed. This causes problems both for productivity: it's hard to collaborate, and reproducibility: which impacts on governance and compliance.
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Matthew Skelton is co-founder of Skelton Thatcher Consulting / @matthewpskelton
GitHub Universe: 2019: Exemplars, Laggards, and Hoarders A Data-driven Look a...Gene Kim
This document discusses a study of the Java Maven ecosystem to analyze relationships between practices and security/update outcomes. It outlines hypotheses that projects releasing frequently and updating dependencies frequently will have better security. Data on 310,888 components was gathered on attributes like release frequency, dependencies, vulnerabilities. Preliminary findings show a correlation between faster updating and better security. The goals of further studies are outlined.
2019 12 Clojure/conj: Love Letter To Clojure, and A Datomic Experience ReportGene Kim
Talk video: https://www.youtube.com/watch?v=5mbp3SEha38&t=1652s
Blog post: https://itrevolution.com/love-letter-to-clojure-part-1
I will explain how learning the Clojure programming language three years ago changed my life. It led to a series of revelations about all the invisible structures that are required to enable developers to be productive. These concepts show up all over The Unicorn Project, but most prominently in the First Ideal of Locality and Simplicity, and how it can lead to the Second Ideal of Focus, Flow, and Joy.
Without doubt, Clojure was one of the most difficult things I’ve learned professionally, but it has also been one of the most rewarding. It brought the joy of programming back into my life. For the first time in my career, as I’m nearing fifty years old, I’m finally able to write programs that do what I want them to do, and am able to build upon them for years without them collapsing like a house of cards, as has been my normal experience.
The famous French philosopher Claude Lévi-Strauss would say of certain tools, “Is it good to think with?” For reasons that I will try to explain in this post, Clojure embraces a set of design principles and sensibilities that were new to me: functional programming, immutability, an astonishingly strong sense of conservative minimalism (e.g., hardly any breaking changes in ten years!), and much more…
Clojure introduced to me a far better set of tools to think with and to also build with. It’s also led to a set of aha moments that explain why for decades my code would eventually fall apart, becoming more and more difficult to change, as if collapsing under its own weight. Learning Clojure taught me how to prevent myself from constantly self-sabotaging my code in this way.
The document summarizes the key discussion points from an interactive webinar on common DevOps myths. It outlines 9 common DevOps myths that were discussed, including "DevOps or Die!", "DevOps is Developers Doing Operations!", and "It's Hard to 'Sell' DevOps to the Business!". For each myth, it provides the perspectives of experts on whether it is more of a myth or a fact, rating it on a scale of 1 to 4. It concludes by providing information on how to access resources from the webinar hosts, Atos and XebiaLabs.
This document summarizes Gene Kim's presentation on how organizations can adopt a DevOps approach. It outlines three ways to achieve DevOps: (1) use systems thinking to understand workflow and increase flow, (2) amplify feedback loops to improve quality and respond to needs, and (3) foster a culture of continual experimentation and learning. Specific practices are provided for each way, like defining work, embedding dev in ops, and breaking things early. The presentation warns that the status quo leads to a downward spiral but DevOps can help organizations overcome tensions and do more with less effort.
Bill is called by the CEO of Parts Unlimited and given an ultimatum - fix the massively over budget and late Phoenix Project IT initiative within 90 days or have his entire department outsourced. With the help of a board member, Bill starts implementing agile and DevOps practices like limiting work in progress, establishing consistent feedback loops, and creating a culture of continuous learning. This leads to breakthroughs like identifying too much reliance on one engineer, improving flow through development and operations, and bringing critical supplier resources in-house. The novel is used to effectively demonstrate these concepts through an entertaining narrative.
Kim IT Pro Forum Eugene: IT at Ludicrous Speeds - rugged dev opsGene Kim
This document summarizes a presentation by Gene Kim on DevOps practices. It discusses how high performing IT organizations excel at areas like security, change management and incident response compared to average organizations. The presentation explores how the relationship between development and operations can become strained, leading to a downward spiral. DevOps principles like automation, collaboration and shared goals between Dev and Ops are presented as a way to break this cycle by increasing speed and reliability. The concept of systems thinking is discussed as important for understanding how work flows through the entire system from business to customer.
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
The document discusses how the Sarbanes-Oxley Act of 2002 led to disproportionate focus on IT controls in SOX-404 compliance efforts. This created problems and challenges as there was no clear guidance on how to scope IT processes and controls to specific internal control objectives. The document proposes that defining new terms, similar to how terms like "force" and "mass" helped Newton formulate his laws of motion, could help address this problem. It suggests an approach taken in another document could help create equivalence for exceptions in IT controls.
The document discusses how to better sell DevOps practices to organizations. It begins by describing the downward spiral of tensions between IT operations and development teams as applications become more fragile and difficult to deploy. It then provides suggestions for framing the problems organizations face in a way that shows how DevOps practices can help address significant business issues. The document concludes by highlighting examples of organizations successfully implementing DevOps and offers additional resources for learning more.
The Path of DevOps Enlightenment for InfoSecJames Wickett
This document summarizes James Wickett's presentation at DevOps Days Kansas City. It discusses Wickett's journey in IT and his involvement with DevOps. It outlines some of his initial questions about DevOps culture and whether it has been distorted from its original goals. The presentation then contrasts the traditional "old path" of IT operations with a proposed "new path" that more fully incorporates DevOps and security best practices like feedback loops, non-blocking processes, and testing approaches like chaos engineering.
Inextricably linked: reproducibility and productivity in data science and AILuke Marsden
In this talk Luke presents his team’s research comparing the evolution of Software Development & DevOps with that of Data Science & AI.
Because it is more complex and has far more moving parts, Data Science & AI is where Software Development was in 1999: people are emailing and Slacking notebooks to each other, due to a lack of appropriate tooling. There are few CI/CD pipelines and model health monitoring is scarce. A lot that could be automated is still manual. And teams are siloed. This causes problems both for productivity: it’s hard to collaborate, and reproducibility: which impacts on governance and compliance.
Luke presents a proposal for an architecture and a set of open source tools to solve both the collaboration and the governance problem in Data Science & AI. With live demos!
Paris Devops - Monitoring And Feature Toggle Pattern With JMXCyrille Le Clerc
This document discusses using JMX (Java Management Extensions) for monitoring and feature toggling of applications. It describes how to use JMX to monitor custom business indicators by isolating monitoring logic. It also provides examples of accessing JMX data through tools like VisualVM and JSP pages. The document then covers using the feature toggle pattern to enable/disable features without redeploying, including coding patterns like using a dispatcher to hold the feature toggle state.
I am a Test Engineer: Why should I care about DevOps?Anand Deshpande
This document discusses how test engineers should embrace DevOps. It notes that born digital companies are innovating rapidly using DevOps to keep pace with business needs. DevOps helps improve efficiency, reduce costs and team sizes by shortening the cycle between development, testing and operations. The document advises that as a tester, one's future is best served by being part of a DevOps team through embracing a culture of collaboration without blame, automating processes, using lean principles and continuously measuring and improving. It suggests expanding testing skills to include automation, behavior driven development and chaos engineering approaches.
What the smartest brands know about CX ... and what they still aren't doing a...Dynatrace
Dr. Natalie Petouhoff and Steve Trimbo presented on optimizing customer experience through better digital experience management. They discussed how most companies have separate IT and customer experience teams that do not collaborate effectively. This leads to poor customer digital experiences despite investments in customer experience. They proposed assessing an organization's digital experience management maturity across five dimensions and collaborating across teams to improve digital performance and close the gap between customer experience and digital experience.
Two years ago at Devoxx UK we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The large scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important, but equally you must understand specific deployment technologies, security issues, operational reliability, and how to drive organisational transformation. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same. Join us to learn how you can apply this within your team and company.
Winnipeg ISACA Security is Dead, Rugged DevOpsGene Kim
This document summarizes a presentation given by Gene Kim on infosec and DevOps. It discusses research that found high performing IT organizations have fewer security issues and implement changes more successfully. The presentation introduces the concepts of Rugged software development and DevOps. It provides an overview of how to implement DevOps through systems thinking, amplifying feedback loops, and developing a culture of experimentation. Key aspects include integrating operations, security and development teams and processes. The goal is to reduce issues and improve flow to help the business.
I apologize, but I do not have enough context to understand the full meaning of your question. Could you please rephrase or provide some additional details?
Deck for the Global Scrum Gathering in Austin, TX on May 22, 2019.
Summary:
Sometimes organizations that are going through an agile transformation complain that they aren’t getting the benefits that they expected, especially as it’s related to quality and sustaining their pace of delivery. One of the possible reasons could be that insufficient attention has been given to performing the technical practices that support the agile values and principles. One of the big problems that I have seen is development teams not doing the engineering practices and managers de-emphasizing or “not allowing” developers do them. We need to renew the emphasis on agile engineering practices and embrace the ideas of software craftsmanship – without this, agility will suffer. Join in the session as we talk about the relationship of Agile development and code quality and how lack of technical excellence impacts maintainability and time to market. Then we’ll review some agile engineering practices and recommendations on how to get started.
Learning Objectives:
What is clean code Description of technical practices Why lack of technical excellence can negatively impact the team's ability to sustain their delivery pace.
Inextricably linked reproducibility and productivity in data science and ai ...source{d}
In this talk Mark Coleman presents his team's research comparing the evolution of Software Development & DevOps with that of Data Science & AI.
Because it is more complex and has far more moving parts, Data Science & AI is where Software Development was in 1999: people are emailing and Slacking notebooks to each other, due to a lack of appropriate tooling. There are few CI/CD pipelines and model health monitoring is scarce. A lot that could be automated is still manual. And teams are siloed. This causes problems both for productivity: it's hard to collaborate, and reproducibility: which impacts on governance and compliance.
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Matthew Skelton is co-founder of Skelton Thatcher Consulting / @matthewpskelton
GitHub Universe: 2019: Exemplars, Laggards, and Hoarders A Data-driven Look a...Gene Kim
This document discusses a study of the Java Maven ecosystem to analyze relationships between practices and security/update outcomes. It outlines hypotheses that projects releasing frequently and updating dependencies frequently will have better security. Data on 310,888 components was gathered on attributes like release frequency, dependencies, vulnerabilities. Preliminary findings show a correlation between faster updating and better security. The goals of further studies are outlined.
2019 12 Clojure/conj: Love Letter To Clojure, and A Datomic Experience ReportGene Kim
Talk video: https://www.youtube.com/watch?v=5mbp3SEha38&t=1652s
Blog post: https://itrevolution.com/love-letter-to-clojure-part-1
I will explain how learning the Clojure programming language three years ago changed my life. It led to a series of revelations about all the invisible structures that are required to enable developers to be productive. These concepts show up all over The Unicorn Project, but most prominently in the First Ideal of Locality and Simplicity, and how it can lead to the Second Ideal of Focus, Flow, and Joy.
Without doubt, Clojure was one of the most difficult things I’ve learned professionally, but it has also been one of the most rewarding. It brought the joy of programming back into my life. For the first time in my career, as I’m nearing fifty years old, I’m finally able to write programs that do what I want them to do, and am able to build upon them for years without them collapsing like a house of cards, as has been my normal experience.
The famous French philosopher Claude Lévi-Strauss would say of certain tools, “Is it good to think with?” For reasons that I will try to explain in this post, Clojure embraces a set of design principles and sensibilities that were new to me: functional programming, immutability, an astonishingly strong sense of conservative minimalism (e.g., hardly any breaking changes in ten years!), and much more…
Clojure introduced to me a far better set of tools to think with and to also build with. It’s also led to a set of aha moments that explain why for decades my code would eventually fall apart, becoming more and more difficult to change, as if collapsing under its own weight. Learning Clojure taught me how to prevent myself from constantly self-sabotaging my code in this way.
The document summarizes the key discussion points from an interactive webinar on common DevOps myths. It outlines 9 common DevOps myths that were discussed, including "DevOps or Die!", "DevOps is Developers Doing Operations!", and "It's Hard to 'Sell' DevOps to the Business!". For each myth, it provides the perspectives of experts on whether it is more of a myth or a fact, rating it on a scale of 1 to 4. It concludes by providing information on how to access resources from the webinar hosts, Atos and XebiaLabs.
This document summarizes Gene Kim's presentation on how organizations can adopt a DevOps approach. It outlines three ways to achieve DevOps: (1) use systems thinking to understand workflow and increase flow, (2) amplify feedback loops to improve quality and respond to needs, and (3) foster a culture of continual experimentation and learning. Specific practices are provided for each way, like defining work, embedding dev in ops, and breaking things early. The presentation warns that the status quo leads to a downward spiral but DevOps can help organizations overcome tensions and do more with less effort.
Bill is called by the CEO of Parts Unlimited and given an ultimatum - fix the massively over budget and late Phoenix Project IT initiative within 90 days or have his entire department outsourced. With the help of a board member, Bill starts implementing agile and DevOps practices like limiting work in progress, establishing consistent feedback loops, and creating a culture of continuous learning. This leads to breakthroughs like identifying too much reliance on one engineer, improving flow through development and operations, and bringing critical supplier resources in-house. The novel is used to effectively demonstrate these concepts through an entertaining narrative.
Kim IT Pro Forum Eugene: IT at Ludicrous Speeds - rugged dev opsGene Kim
This document summarizes a presentation by Gene Kim on DevOps practices. It discusses how high performing IT organizations excel at areas like security, change management and incident response compared to average organizations. The presentation explores how the relationship between development and operations can become strained, leading to a downward spiral. DevOps principles like automation, collaboration and shared goals between Dev and Ops are presented as a way to break this cycle by increasing speed and reliability. The concept of systems thinking is discussed as important for understanding how work flows through the entire system from business to customer.
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
The document discusses how the Sarbanes-Oxley Act of 2002 led to disproportionate focus on IT controls in SOX-404 compliance efforts. This created problems and challenges as there was no clear guidance on how to scope IT processes and controls to specific internal control objectives. The document proposes that defining new terms, similar to how terms like "force" and "mass" helped Newton formulate his laws of motion, could help address this problem. It suggests an approach taken in another document could help create equivalence for exceptions in IT controls.
The document discusses how to better sell DevOps practices to organizations. It begins by describing the downward spiral of tensions between IT operations and development teams as applications become more fragile and difficult to deploy. It then provides suggestions for framing the problems organizations face in a way that shows how DevOps practices can help address significant business issues. The document concludes by highlighting examples of organizations successfully implementing DevOps and offers additional resources for learning more.
The Path of DevOps Enlightenment for InfoSecJames Wickett
This document summarizes James Wickett's presentation at DevOps Days Kansas City. It discusses Wickett's journey in IT and his involvement with DevOps. It outlines some of his initial questions about DevOps culture and whether it has been distorted from its original goals. The presentation then contrasts the traditional "old path" of IT operations with a proposed "new path" that more fully incorporates DevOps and security best practices like feedback loops, non-blocking processes, and testing approaches like chaos engineering.
Inextricably linked: reproducibility and productivity in data science and AILuke Marsden
In this talk Luke presents his team’s research comparing the evolution of Software Development & DevOps with that of Data Science & AI.
Because it is more complex and has far more moving parts, Data Science & AI is where Software Development was in 1999: people are emailing and Slacking notebooks to each other, due to a lack of appropriate tooling. There are few CI/CD pipelines and model health monitoring is scarce. A lot that could be automated is still manual. And teams are siloed. This causes problems both for productivity: it’s hard to collaborate, and reproducibility: which impacts on governance and compliance.
Luke presents a proposal for an architecture and a set of open source tools to solve both the collaboration and the governance problem in Data Science & AI. With live demos!
Paris Devops - Monitoring And Feature Toggle Pattern With JMXCyrille Le Clerc
This document discusses using JMX (Java Management Extensions) for monitoring and feature toggling of applications. It describes how to use JMX to monitor custom business indicators by isolating monitoring logic. It also provides examples of accessing JMX data through tools like VisualVM and JSP pages. The document then covers using the feature toggle pattern to enable/disable features without redeploying, including coding patterns like using a dispatcher to hold the feature toggle state.
I am a Test Engineer: Why should I care about DevOps?Anand Deshpande
This document discusses how test engineers should embrace DevOps. It notes that born digital companies are innovating rapidly using DevOps to keep pace with business needs. DevOps helps improve efficiency, reduce costs and team sizes by shortening the cycle between development, testing and operations. The document advises that as a tester, one's future is best served by being part of a DevOps team through embracing a culture of collaboration without blame, automating processes, using lean principles and continuously measuring and improving. It suggests expanding testing skills to include automation, behavior driven development and chaos engineering approaches.
Turning the Heat up on DevOps: Providing a web-based editing experience aroun...Michael Elder
We’ll present a web-based editing experience around Heat Orchestration Templates. We have created a unified editing experience leveraging diagram and text-based metaphors into one seamless flow. We have also extended the Heat engine to support full-stack deployment by integrating application deployment capabilities from IBM UrbanCode Deploy. We’ll demonstrate creating ready to deploy HOT documents which capture Compute, Network, and Storage resources as well as our own extensions around software configuration and deployment resources.
We’ll describe how our solution supports three characteristics for Software Defined Environments:
- Organic: Support creating and updating environments in place as their purpose or architecture changes over time.
- Version-aware: We’ll show incorporating native scm solutions like git as part of the web-based interface to version and update templates across multiple environments.
- Fullstack Engineering: We’ll describe templates which capture cloud resources and software resources as part of a unified template which can then provision cloud resources and deploy software in one action.
Our extensions to Heat will be described along with our experiences in extending the engine as a vendor.
- The document discusses how full-stack DevOps can maximize developer productivity when implemented properly through automated processes. It emphasizes that DevOps works best when developers have dedicated time and resources for implementation.
- A full-stack solution called "The Ball" is presented which utilizes tools like JetBrains TeamCity, Xamarin, Visual Studio, and TestFairy to enable automated testing, deployment and issue tracking across mobile and web platforms.
- The tools are argued to simplify the DevOps process and enable even non-technical users to comply with version control requirements. With these tools, complex full-stack platforms can be developed and maintained with clear branching models and integration of builds, testing and feedback.
We all know that bringing devops practices to your organisation is hard and very labour intensive task. Despite the fact that for large organisations it is still a real challenge, for small startups and development teams devops practices can be adopted relatively easily.
In this talk Leonid will share his experience of bringing devops practices to small organisations, and prove that devops isn't something that you should postpone for a later growth stage, but something you can do (and relatively easy) now, at the first stages of your idea inception!
Survey on article extraction and comment monitoring techniquesAnunaya
The online News publisher publishes their news in the form of articles. Most of the online news websites provide the facility for their users to comment on the news article and as a result a lot of people comment on the news article. Hence news web page contains huge data in the form of article content and comments data, etc and have a good potential to be a resource for many Information Retrieval Systems and Data Mining Applications. The extraction of the main content (Article content) from a web page has always been a challenging task because a web page contains other information like advertisements and hyperlinks etc. which is not related to Article Text. In this survey, we review various techniques which are proposed by various researchers to extract the article content from a news web site. We also learn various techniques which monitor and analyze the comments for various applications like popularity prediction of articles and identification of discussions thread in the comments data.
DevOps at Obama for America(2012) and the DNC (DevOps Days NYC Jan 2013)John Schneider
1) DevOps practices were implemented at the Democratic National Committee between 2009-2011 to improve systems, including virtualization, documentation, version control, automation, and making everything highly available.
2) Early agile development practices and use of AWS services like EC2 and continuous integration helped scale applications for the DNC.
3) Lessons from 2010 were applied in 2012, including use of big data, evaluating hardware vs AWS costs and limitations, and developing analytics tools for various teams.
This document summarizes a presentation about how DevOps engineers at Datadog provide customer support. Some key points discussed include:
- Datadog got customers through word-of-mouth due to the quality of their product and support provided by DevOps engineers.
- Datadog treats customers like they treat themselves by answering all questions thoroughly and making sure issues are fully resolved.
- Engineers spend a week at a time helping with customer support to continuously learn.
- Datadog uses a variety of tools like IRC, email, in-app chat, and social media to engage with customers and share information.
- Metrics like response time, resolution time, and channel volume are analyzed monthly to improve support.
The document discusses practical monitoring techniques including current tools used like Collectd, Sensu, New Relic, Grafana, and PagerDuty. It covers increasing coverage by automatically collecting metrics and alerts for new instances. Other topics include on-call schedules, automatic self-healing, bots and alerts channels, an events dashboard, accessibility of monitoring tools, and best practices like automating monitoring, sharing responsibilities, and automating healing when possible.
This document discusses various metrics for measuring website availability and performance. It defines Failed Customer Interactions (FCI) as when a customer request does not receive the expected response from the application. Top Percentile (TP) measures the response time within which a certain percentage of requests are served. Real User Monitoring (RUM) measures actual page load times for real users rather than synthetic tests. RUM is important for Single Page Applications where most processing happens after page load. The document also describes using NewRelic's RUM tool to capture metrics and calculate a formula for Measured Availability.
Last update to the DevOps anti-patterns talk that IMO deserves separate upload. It was about anti patterns captured consulting several projects on their DevOps adoption. There are few common pitfalls we can see repeating again and again over DevOps culture discovery. This talk is my experience summary there
5 Ways ITSM can Support DevOps, an ITSM Academy WebinarITSM Academy, Inc.
Presenter: Jayne Groll, President, ITSM Academy
There is much debate about the relevancy of ITIL and ITSM in a new DevOps world. The truth is that DevOps does not negate the need for service management, it validates it – with some adaptation to be faster and more agile. This presentation will demonstrate five ways that ITSM processes can be adapted to and support emerging DevOps practices.
Motivated by the ideas presented? Print a Personal Action Plan to capture them.... https://www.itsmacademy.com/content/PAP-FOLD.pdf
AWS and Dynatrace: Moving your Cloud Strategy to the Next LevelDynatrace
AWS and Dynatrace: Moving your Cloud Strategy to the Next Level
On-Demand Webcast
AWS re:Invent was an exciting time for Dynatrace and we received a lot of “Wows” on our capabilities. We got to demonstrate the only AI-based, full-stack monitoring solution to thousands of AWS prospects and users. We announced our AWS Certified DevOps Competency partnership, and we introduced DAVIS, our natural-language voice interface, to thousands of attendees.
We know that many of you couldn’t attend the event in Las Vegas, so we wanted to share some of the key highlights from the show. And for those of you who were there, you may not have seen all of the benefits Dynatrace provides in the AWS ecosystem due to time constraints of sessions and the large tradeshow floor.
Listen to this 30 Minute webcast where Alois Reitbauer and Franz Karlsberger recap some of the highlights of the event, including:
How Dynatrace, as an AWS certified Migration Competency partner, uniquely supports enterprise migrations to AWS
How to achieve faster feedback and improved lead times with AWS CodePipeline and Dynatrace
An overview of the first ever VoiceOps and ChatOps interface via DAVIS, based on our AI approach to full-stack monitoring
A full-stack developer is someone who can take a project from conception to a finished product, handling both front-end and back-end development. They have a wide range of skills across the stack rather than deep expertise in one area. Full-stack developers are well-suited for small startups but may face more scaling challenges in larger companies with more specialized roles. The document discusses technologies used in full-stack development and tips for learning new skills like contributing to open source projects.
This document discusses the importance of monitoring in DevOps. It provides examples of metrics to monitor like response times, errors, user behavior etc. and how to collect and visualize this data. Open source tools like CollectD, Graphite, Logstash, Elasticsearch, Kibana, InfluxDB and Grafana are recommended for collection, storage and visualization of monitoring data. The document emphasizes making decisions based on facts obtained from monitoring and continuous improvement.
DevOps/Flow workshop for agile india 2015Yuval Yeret
This document discusses implementing DevOps flow by leveraging lean/agile practices across development, deployment, and operations. It emphasizes establishing continuous integration and delivery workflows to enable frequent, reliable releases through automation. Kanban techniques are presented as a way to visualize work and limit work-in-progress to improve collaboration between teams.
Think that DevOps is just for product? Think again.
In this webinar, ITSM expert John Custy shows you how to apply DevOps principles to your IT org. This event is for anyone involved in the support and development of IT systems and services. The keys to higher-performing services are so simple, they might surprise you.
Watch the full webinar here: http://atlassian.com/help-desk/how-to-run-it-support-devops-way
Brought to you by JIRA Service Desk. Learn more: http://atlassian.com/service-desk
Jelastic provides an advanced DevOps PaaS with Docker containers support, easy cloud management and flexible quotas system to help service providers to unleash the full potential of containers.
DevOpsRoadTrip San Francisco Final Speaking Deck VictorOps
Join well known industry thought leaders and experts from local San Francisco companies for a 1/2 day event focused on the latest and greatest in DevOps practices.
https://victorops.com/devops-roadtrip-sf/
How Dealertrack Optimizes the DevOps Toolchain, FutureStack17New Relic
Dealertrack explains how they optimize their DevOps toolchain at FutureStack17.
Be sure to subscribe and follow New Relic at:
https://twitter.com/NewRelic
https://www.facebook.com/NewRelic
https://www.youtube.com/NewRelicInc
This document provides an overview of DevOps for architects. It defines DevOps as developers and operations teams working collaboratively across the entire software development lifecycle. The document discusses that DevOps aims to help businesses by optimizing collaboration and value delivery through practices like automation, continuous integration and deployment, and emphasizing a culture of communication, shared responsibility, and learning. It also provides perspectives on DevOps from several experts and discusses how architects can approach their work in a DevOps environment.
Join well known industry thought leaders and experts from local New York companies for a 1/2 day event focused on the latest and greatest in DevOps practices.
How AI is transforming DevOps | Calidad InfotechCalidad Infotech
DevOps is a remarkable asset to start-ups. The growing technology over the last two decades has made it easier to build & scale all sizes of businesses & organizations. In this fast-paced growing technology world, DevOps has paved its way with its innovative & effective tools & practices that have turned out to be a… Continue reading.. https://calidadinfotech.com/devops-services
AIIM and Vamosa - Practical Cosniderations when Implementing ECMnicarcher
AIIM give a great overview of a recent survey on the motivators for implementing ECM in todays economy, and Vamosa talk about how to get the best out of your content through enterprise content governance
First debrief of the Outcomes of the Owasp Summit 2017 (with keynote slides and photos)
Full details at https://owaspsummit.org/
Outcomes at https://owaspsummit.org/Outcomes/
This document discusses trends in enterprise content management (ECM) and highlights key points from a Forrester presentation on the topic. It notes that ECM is evolving to support the digital enterprise and new content types. Migration challenges and lack of governance are cited as top issues. Emerging trends include a focus on user experience, mobility, automation and embedding analytics. ECM is being shaped by innovations in adjacent areas like file sharing and is driving improvements to customer experience and operational excellence.
AppSphere 15 - Transforming the Business: The Role of DevOpsAppDynamics
DevOps practices are being used by an increasing number of IT executives and teams across development, application support, and operations to increase the speed and quality of application deployments. Besides technology and process benefits, DevOps can drive significant business outcomes, and lead a bottoms up approach for transforming culture and organizational structures. This session will answer the following questions:
- How do DevOps practices increase IT performance?
- What metrics should I use to gauge success, and how should they be defined?
- What role can application performance and analytics play in DevOps, and delivering business value?
- How does DevOps transform the security, compliance, and audit conversation?
This deck was originally presented at AppSphere 2015.
AppDynamics the Missing Link to DevOps - AppSphere16AppDynamics
IHS is a premier provider of global market, industry, and technical expertise. Our industry is fast moving, and IT agility is key to IHS's success. A DevOps approach is vital, and factual application performance information centered on business outcomes is key to a true DevOps practice. However, the move to DevOps shouldn’t be seen as a door that opens easily, but a maze that must be navigated carefully.
In this session you will learn how IHS used fact-based application performance data, correlated by AppDynamics, to avoid cultural challenges, competing goals, and unclear strategies. Hear how partnering with AppDynamics Professional Services helped map people, processes, and technology to ensure goals and needs were met. Together, we mitigated risk to the business.
Key takeaways:
o Why the move to DevOps isn't easy
o Why discussions based on fact remove emotion and are the foundation of success
o Why culture can be either a barrier or a catalyst for the move to DevOps, but whatever you do, don't ignore it
o How AppDynamics Professional Services can accelerate the journey and help identify risk, fill gaps, and guide you to best practices
For more information, go to: www.appdynamics.com
Improving software quality for the future of connected vehiclesDevon Bleibtrey
In the highly regulated environment of automotive, software quality can be difficult but it doesn't need to be. ESG partners with software teams to improve their team's performance through developer operations. From culture to tool integrations, ESG takes a holistic approach to help teams measurably improve their software development lifecycle and the quality of its output.
If you don't know where you're going it doesn't matter how fast you get thereNicole Forsgren
The best-performing organizations have the highest quality, throughput, and reliability while also delivering value. They are able to achieve this by focusing on a few key measurement principles, which Nicole and Jez will outline in this talk. These include knowing your outcome measuring it, capturing metrics in tension, and collecting complementary measures… along with a few others. Nicole and Jez explain the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic, so you can course correct rapidly. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and stakeholders, and arms you for important conversations around targets such as SLOs. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to be great SREs and move performance in the right direction.
The document discusses the characteristics of thriving open source software projects. It identifies three types of projects - dead, surviving, and thriving. Thriving projects are described as having five key characteristics: 1) being easy to contribute to, 2) being scalable and maintainable, 3) having a growing community, 4) having a growing reputation, and 5) having a good leadership team. Various metrics for evaluating projects based on these characteristics are provided. A case study of the Weex project is also examined.
Accelerate Your Time to a Successful Deployment with DevOpsPerficient, Inc.
According to research firm IDC, 70% of Global Fortune 500 firms are expected to adopt DevOps by the end of 2017. With digital transformation strategies at the forefront of organizational priorities, IT is now under more pressure than ever to optimize innovation cycles while removing roadblocks.
In this IBM / Perficient DevOps SlideShare, we discuss topics including:
The differences between DevOps, Agile, and Waterfall methodologies
How automation can influence your development process, remove roadblocks to innovation, and increase visibility into your projects
Why the DevOps toolchain impacts your entire innovation cycle
DevOps best practices from industry leaders
10 steps to salvation: Creating digital governance that worksKate Thomas
For organisations to succeed in the digital age, they need to adopt new frameworks and ways of working. The key to doing this is to dust off and turn inside-out existing governance frameworks, reinvigorating them with more nimble ways of working. Governance is no longer a separate policy or individual decision maker. It is everyone working in digital. It is every digital touch point and policy. It is the digital strategy, the customer strategy, the media strategy, the KPI framework, analytics, and SEO.
Twenty-first century governance is the supportive mesh of digital success.
Presented 01 Oct 2014 at Confab Europe Barcelona
http://confabevents.com/events/europe/program/10-steps-to-salvation-creating-digital-governance-that-works
DevOps is everywhere, but too often, people think they can buy “DevOps in a box” and just sprinkle some tools and automation over your broken or slow (or even super-fast AWS) stack. But we all know that software delivery is still hard. So what is this crazy DevOps thing, and why and how does it make things better? In this session, Jez and Nicole talk about what they’ve found working with dozens of organizations and conducting the largest DevOps research studies to date, covering over 23,000 data points across 2,000 organizations around the world. We start with the outcomes that companies care about: organizational performance, software delivery performance, and software quality. We then define what DevOps is, how you measure it, and how the best, most innovative teams and organizations are using it to drive improvements in performance and quality.
Best Practices for Driving Software Quality through a Federated Application S...DevOps.com
For DevSecOps to become a reality there must be a fundamental shift in mindset and approach to application security (AppSec) – moving from ownership solely within corporate security to a federated, shared model of responsibility that spans both security and software engineering teams.
In this webinar, ZeroNorth’s Thaddeus Walsh and Joanne Godfrey will discuss some of the real-life challenges security teams face as they seek to implement a federated AppSec responsibility model and will offer some practical advice to help address these challenges.
This webinar will cover:
Why a centralized control model for AppSec no longer works in today’s software-defined world
The vision, core requirements and value of a federated responsibility model for AppSec
The challenges of implementing this model in real life
Architecting the model for a successful implementation
Best practice for empowering developers to implement security throughout the SDLC
Creating a friction free collaborative working relationship between security and engineering
This document summarizes a presentation given by Eric Raarup from Avtex and Mike Peterson from Microsoft on June 12th, 2013 about the intersection of technology and marketing. The presentation covered key trends impacting marketing like mobility, social media, cloud computing and data. It showcased Microsoft's technology landscape for marketers, including Dynamics CRM, ClickDimensions, and tools for social analytics, data visualization, and responsive design. The presentation discussed how these technologies can help with web-to-lead conversion, lead nurturing, gaining customer insights, delivering content to sales teams, and allocating marketing resources effectively.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
National Security Agency - NSA mobile device best practices
DevOps Roadtrip Minneapolis
1.
2. JASON HAND |
DevOps Evangelist
• Holds over 15 years of experience as a
developer, system administrator, and
support specialist
• Fully emerged into the world of agile
development and the DevOps
movement with Colorado tech
startups
#DevOpsRoadTrip
5. A little about VictorOps…
VictorOps is the real-time incident
management platform that combines the
power of people and data to embolden
DevOps pros to handle incidents as they
occur.
#DevOpsRoadTrip
19. “How Organizations Process Information”
Roy Westrum: A Typology of Organizational Cultures
2014 State of DevOps Report shows that in the context of IT, job satisfaction is the biggest predictor of
profitability, market share, and productivity. The biggest predictor of job satisfaction, in turn, is how
effectively organizations process information, as determined by a model created by sociologist Ron
Westrum, shown below. 1
1: https://continuousdelivery.com/implementing/culture/
20.
21.
22. Words are how we think – stories are how we link.
- Christina Baldwin
Oral narrative is and for a long time has been the
chief basis of culture itself.
- John D. Niles
Stories from the road
36. TimeToRepair(TTR)
Continuous Improvement Efforts
Reactive
(chaotic)
Tactical
(obvious)
Integrated
(complicated)
Strategic
(complex)
✓ No automation
✓ No operational stack
awareness
✓ Poor collaboration between
teams (Dev & Ops)
✓ Documentation not available
✓ No standardized
communication
✓ High focus on consistent
continuous learning
✓ Uses a NOC
✓ Some monitoring & alerting
instrumentation
✓ Collaboration in crisis
✓ "Mission critical" processes
are available
✓ Understood crisis
communication protocols
✓ Remediation data available to
IT Operations
✓ Team rotations, paging
policies, role hunting
✓ Continuous improvement of
key health indicators
✓ Technical collaboration across
all incidents
✓ Docs up to date and easily
accessible
✓ Consistent real-time
communication practices
✓ Automated docs and remediation
✓ Actionable Alerts with full context
✓ High collaboration among all
teams
✓ Documentation part of
remediation
✓ Targeted, proactive crisis comms
✓ High focus on continuous learning
Incident Management
Maturity
37. Reactive
(chaotic)
✓No automation
✓No operational stack awareness
✓Poor collaboration between teams (Dev & Ops)
✓Documentation not available
✓No standardized communication
✓High focus on consistent continuous learning
38. Tactical
(obvious)
✓Uses a NOC
✓Some monitoring & alerting instrumentation
✓Collaboration in crisis
✓"Mission critical" processes are available
✓Understood crisis communication protocols
✓Remediation data available to IT Operations
39. Integrated
(complicated)
✓Team rotations, paging policies, role hunting
✓Continuous improvement of key health indicators
✓Technical collaboration across all incidents
✓Docs up to date and easily accessible
✓Consistent real-time communication practices
40. Strategic
(complex)
✓Automated docs and remediation
✓Actionable Alerts with full context
✓High collaboration among all teams
✓Documentation part of remediation
✓Targeted, proactive crisis comms
✓High focus on continuous learning
41. “Six Trends Shape DevOps Adoption, Q1 2015”
Forrester report
• The Foundation For Success Is In Place . . . Mostly
• Fear Of Failure Will Hamper Advancement
• Monitoring And Analytics Strategies Must Make A Big Leap Forward
• The Focus On Customer Experience Is Not Second Nature . . . Yet
• Change And Release Processes Are Not Delivering Business Needs
• You Must Prioritize And Focus Sourcing Strategies
64. Bridget Kromhout | Pivotal - Cloud Foundry
Principal Technologist
• Bridget Kromhout is a Principal Technologist for Cloud Foundry at
Pivotal.
• After years as an operations engineer (most recently at DramaFever),
she traded in oncall for more travel.
• A frequent speaker at tech conferences, she helps organize tech
meetups at home in Minneapolis, serves on the program committee for
Velocity, and acts as a global core organizer for devopsdays.
• She podcasts at Arrested DevOps, occasionally blogs at
bridgetkromhout.com, and is active in a Twitterverse near you.
#DevOpsRoadTrip
72. @bridgetkromhout
“Almost every task run
under Borg contains a
built-in HTTP server that
publishes information
about the health of the
task and thousands of
performance metrics”
Large-scale cluster management at Google with Borg - Verma et al. 2015
“Almost every task run
under Borg contains a
built-in HTTP server that
publishes information
about the health of the
task and thousands of
performance metrics”
73. @bridgetkromhout
The Art of Monitoring (2016) — James Turnbull
Monitoring Maturity Model
artofmonitoring.com
74. @bridgetkromhout Image credit: Wikipedia
“Any organization that designs a system…
will produce a design
whose structure is a copy of
the organization's
communication
structure.”
Mel Conway
79. Andy Domeier | SPS Commerce
Director System Operations
• Andy has been in Technology Operations leadership with SPS
Commerce for the past 11 years.
• Andy spends many mental cycles collaborating to solve
effective patterns for monitoring and operating complex
changing systems.
• Andy’s also spends time solving for priority organization and
alignment and the organization of knowledge.
#DevOpsRoadTrip
109. Ben Overmyer | Star Tribune
Digital Manager, Operations
• Ben is the Digital Manager of Operations at the Minneapolis Star
Tribune.
• He has over a decade of experience as a back end software engineer,
two years of experience as a dedicated operations engineer, and great
enthusiasm for the DevOps culture.
• Besides the Star Tribune, he’s worked for an eclectic mix of
organizations, including the USGS, a game company in New Zealand,
and a beauty products marketing company.
• When not hacking on servers, apps, or people, he acts as art director
and author for a tabletop gaming company.
#DevOpsRoadTrip
111. IN THE BEGINNING
▸ Forwarded phone line
▸ An on-call list maintained in a wiki
▸ Every week, manually change to the next person on the list
▸ …and overrides or substitutions?
112. EARLY MONITORING
▸ Zabbix monitoring set up for a handful of causes
▸ Zabbix alerts sent via email to a distribution list
▸ Sometimes no one would see these alerts until hours or, in
rare cases, days later
113. THE PAIN POINTS
▸ Manual maintenance of the calling tree data
▸ Manual rotation of the support phone line forwarding
▸ Poor documentation of incident life cycles
▸ No sense of incident frequency beyond “this was a bad
couple weeks”
▸ If the on-call person didn’t respond, there was no
escalation process other than calling the head of Digital
115. ADOPTING VICTOROPS
▸ Automated rotations
▸ Multiple teams
▸ Automatic escalation processes
▸ Easy schedule overrides and changes
▸ APIs for programmatic incident interaction
116. THE NATURE OF ALERTS
▸ OK, we can set up programmatic alerts. Now what?
▸ Integrating Zabbix, New Relic, and CloudWatch
▸ Discovering alert floods
▸ Move to alerting on symptoms, not causes
▸ …but still monitoring causes
118. THE SPIDEY-SENSE FACTOR
▸ Humans are good at catching certain kinds of problems
▸ “This doesn’t feel right” and gaps in monitoring
▸ The evolution of the Sev incident system
119. THE STATUS SITE: MANUAL ALERTING FOR NON-TECH USERS
▸ Want to let certain non-tech users report Sev incidents
▸ Initially just a password-protected form
▸ Uses the VictorOps alert ingestion API for triggering alerts
▸ Uses the VictorOps public API for fetching information
▸ Each Sev alert is created with its own entity_id
▸ Lets admin users share status updates
120. MONTHLY INCIDENT REPORTING
▸ Monthly reports include a list of all Sev incidents, when
they started, when they ended, what the alert text was, and
what the resolution was
▸ Combine automated and chat messages in VictorOps with
data gathered from other sources
▸ Present this data as automatically as possible in the Status
Site
122. NEXT STEPS
▸ Integration of summarized data collected from Datadog/
CloudWatch/etc. into incident reporting
▸ Reports for users that shouldn’t have access to VictorOps
▸ Integration of the Status Site into Slack
126. Breakout Sessions
◻ ChatOps - Jason Hand
◻ Leveraging Data to Establish a Healthy Culture - Andy Domeier
◻ Monitoring and Microservices – Bridget Kromhout
◻ Blameless Culture – Heather Mickman
◻ Devs vs. Ops On-Call, How and Why to Get started – Ben Overmyer
#DevOpsRoadTrip
128. Breakout Sessions
◻ ChatOps - Jason Hand
◻ Leveraging Data to Establish a Healthy Culture - Andy Domeier
◻ Monitoring and Microservices – Bridget Kromhout
◻ Blameless Culture – Heather Mickman
◻ Devs vs. Ops On-Call, How and Why to Get started – Ben Overmyer
#DevOpsRoadTrip
130. Heather Mickman | Target
Senior Director of Platform Engineering
• Heather Mickman is the Senior Director of Platform Engineering at Target and a
DevOps enthusiast.
• Heather has 20+ years of IT experience in various roles and industries including
retail, transportation, and high tech manufacturing.
• She is currently working on building the platforms used by software engineers
at Target including a multi-provider cloud platform, API Gateway, telemetry
tooling, data stores, and messaging.
• She has a passion for technology, building high performing teams, driving a
culture of innovation, and having fun along the way. Heather lives in
Minneapolis with her 2 sons and mini dachshund.
#DevOpsRoadTrip
153. Unordered Ordered
Complicated
Obvious
Complex
Chaotic
Cause Effect Obvious
From Experience
Cause Effect Requires
Analysis
Cause Effect Only
Apparent in Hindsight
Cause & Effect Cannot
Be Related
Sense – Categorize - Respond
Sense – Analyze - RespondProbe – Sense - Respond
Act – Sense - Respond
154.
155. The systems we engineer, maintain, and improve are
Complicated
.. or ..
Known unknowns
156. The systems we engineer, maintain, and improve are
ComplexUnknown unknowns
162. TimeToRepair(TTR)
Continuous Improvement Efforts
Reactive
(chaotic)
Tactical
(obvious)
Integrated
(complicated)
Strategic
(complex)
✓ No automation
✓ No operational stack
awareness
✓ Poor collaboration between
teams (Dev & Ops)
✓ Documentation not available
✓ No standardized
communication
✓ High focus on consistent
continuous learning
✓ Uses a NOC
✓ Some monitoring & alerting
instrumentation
✓ Collaboration in crisis
✓ "Mission critical" processes
are available
✓ Understood crisis
communication protocols
✓ Remediation data available to
IT Operations
✓ Team rotations, paging
policies, role hunting
✓ Continuous improvement of
key health indicators
✓ Technical collaboration across
all incidents
✓ Docs up to date and easily
accessible
✓ Consistent real-time
communication practices
✓ Automated docs and remediation
✓ Actionable Alerts with full context
✓ High collaboration among all
teams
✓ Documentation part of
remediation
✓ Targeted, proactive crisis comms
✓ High focus on continuous learning
Incident Management
Maturity
163. Reactive
(chaotic)
✓No automation
✓No operational stack awareness
✓Poor collaboration between teams (Dev & Ops)
✓Documentation not available
✓No standardized communication
✓High focus on consistent continuous learning
164. Tactical
(obvious)
✓Uses a NOC
✓Some monitoring & alerting instrumentation
✓Collaboration in crisis
✓"Mission critical" processes are available
✓Understood crisis communication protocols
✓Remediation data available to IT Operations
165. Integrated
(complicated)
✓Team rotations, paging policies, role hunting
✓Continuous improvement of key health indicators
✓Technical collaboration across all incidents
✓Docs up to date and easily accessible
✓Consistent real-time communication practices
166. Strategic
(complex)
✓Automated docs and remediation
✓Actionable Alerts with full context
✓High collaboration among all teams
✓Documentation part of remediation
✓Targeted, proactive crisis comms
✓High focus on continuous learning
182. TimeToRepair(TTR)
Continuous Improvement Efforts
Reactive (0 – 4)
(chaotic)
Tactical (5 – 9)
(obvious)
Integrated (10 -14)
(complicated)
Strategic (15 – 18)
(complex)
✓ No automation
✓ No operational stack
awareness
✓ Poor collaboration between
teams (Dev & Ops)
✓ Documentation not available
✓ No standardized
communication
✓ High focus on consistent
continuous learning
✓ Uses a NOC
✓ Some monitoring & alerting
instrumentation
✓ Collaboration in crisis
✓ "Mission critical" processes are
available
✓ Understood crisis
communication protocols
✓ Remediation data available to
IT Operations
✓ Team rotations, paging
policies, role hunting
✓ Continuous improvement of
key health indicators
✓ Technical collaboration across
all incidents
✓ Docs up to date and easily
accessible
✓ Consistent real-time
communication practices
✓ Automated docs and remediation
✓ Actionable Alerts with full context
✓ High collaboration among all teams
✓ Documentation part of remediation
✓ Targeted, proactive crisis comms
✓ High focus on continuous learning
Incident Management
Maturity