Damon Edwards, Alex Honor, Nathan Fluegel of Rundeck presentation from All Day DevOps on Oct 17, 2018
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Too often we model processes around the myth of Database Transactions, ofter forgetting what a transaction really means in the real world. This talk shows an easy and cheap approach to use together with EventStorming in order to include User Experience into process modelling
What makes software development complex isn't the code, it's the humans. The most effective way to improve our capabilities in software development is to better understand ourselves.
In this talk, I'll introduce a conceptual model for human interaction, identity, culture, communication, relationships, and learning based on the foundational model of Idea Flow. If you were to write a simulator to describe the interaction of humans, this talk would describe the architecture.
Learn how to understand the humans on your team and fix the bugs in communication, by thinking about your teammates like code!
Edit
Archive
Delete
I'm not a scientist or a psychologist. These ideas are based on a combination of personal experience, reading lots of cognitive science books, and a couple years of running experiments on developers. As I struggled through the challenges of getting a software concept from my head to another developer's head (interpersonal Idea Flow), I learned a whole lot about human interaction.
As software developers, we have to work together, think together, and solve problems together to do our jobs. Code? We get it. Humans? WTF?!
Fortunately, humans are predictably irrational, predictably emotional, and predictably judgmental creatures. Of course those pesky humans will always do a few unexpected things, but once we know the algorithm for peace and harmony among humans, we can start debugging the communication problems on our team.
There and back again (as presented at Agile 2012, Dallas, TX)Cecilia Fernandes
This was a rather short, yet very dense experience report that accompanies a paper, to tell the story of a team that evolved from textbook Scrum to something much alike Lean Software Development and then decided they needed iterations back.
DevOps Army of N - Recovering From Being A Human SPOFfunjon
You used to be a single point of failure. You were the solo engineer on a project, which came with some limited prestige, but it was incredibly stressful. Vacations were cancelled, dance recitals were missed, and sleep became a precious resource that you clutched tightly. You may also have developed a phantom buzzing in your phone pocket from all the late-night pages over the years. Survival was a struggle, but you kept soldiering on.
But no longer. Management opened and filled job reqs! New engineers have arrived, eager to learn and help, and the tunnel is suddenly much brighter! Except...
What do you do now?
Last November, I walked through my experiences as a human SPOF, and the strategies I used to survive. In the intervening months, our team has hired several new DevOps engineers, with more on the way. But now we need to get all that knowledge out of my brain, and into a palatable format for consumption by others. At devopsdays SV 2016, I shared some of the challenges encountered in getting new engineers up to speed, when all the knowledge exists solely in my head. Several difficulties exist, affecting both the individual and the team as a whole. Prioritizing projects is complicated, because so much depends on knowledge that exists only in one place. Knowledge transfer can often be disjointed and difficult to organize, because the information is frequently tied up in the chaos of solo operations. And as we've started exploring all the components in our environments, we've revisited the sins of our past - corners cut and shortcuts taken in the interests of getting it done now, versus getting it done cleanly. Many of the tools were designed out of desperation, not with flexibility and maintainability in mind. Now it's time to figure out how to complete that transition, and move toward a more maintainable, survivable environment.
This is a follow-up to my talk from devopsdays SV 2015, entitled DevOps Army of One - How to Survive When You're the SPoF. I really enjoyed giving that talk, and since then I've gained not only some much-needed help, but insight into the difficulties involved in bringing the new engineers online.
Too often we model processes around the myth of Database Transactions, ofter forgetting what a transaction really means in the real world. This talk shows an easy and cheap approach to use together with EventStorming in order to include User Experience into process modelling
What makes software development complex isn't the code, it's the humans. The most effective way to improve our capabilities in software development is to better understand ourselves.
In this talk, I'll introduce a conceptual model for human interaction, identity, culture, communication, relationships, and learning based on the foundational model of Idea Flow. If you were to write a simulator to describe the interaction of humans, this talk would describe the architecture.
Learn how to understand the humans on your team and fix the bugs in communication, by thinking about your teammates like code!
Edit
Archive
Delete
I'm not a scientist or a psychologist. These ideas are based on a combination of personal experience, reading lots of cognitive science books, and a couple years of running experiments on developers. As I struggled through the challenges of getting a software concept from my head to another developer's head (interpersonal Idea Flow), I learned a whole lot about human interaction.
As software developers, we have to work together, think together, and solve problems together to do our jobs. Code? We get it. Humans? WTF?!
Fortunately, humans are predictably irrational, predictably emotional, and predictably judgmental creatures. Of course those pesky humans will always do a few unexpected things, but once we know the algorithm for peace and harmony among humans, we can start debugging the communication problems on our team.
There and back again (as presented at Agile 2012, Dallas, TX)Cecilia Fernandes
This was a rather short, yet very dense experience report that accompanies a paper, to tell the story of a team that evolved from textbook Scrum to something much alike Lean Software Development and then decided they needed iterations back.
DevOps Army of N - Recovering From Being A Human SPOFfunjon
You used to be a single point of failure. You were the solo engineer on a project, which came with some limited prestige, but it was incredibly stressful. Vacations were cancelled, dance recitals were missed, and sleep became a precious resource that you clutched tightly. You may also have developed a phantom buzzing in your phone pocket from all the late-night pages over the years. Survival was a struggle, but you kept soldiering on.
But no longer. Management opened and filled job reqs! New engineers have arrived, eager to learn and help, and the tunnel is suddenly much brighter! Except...
What do you do now?
Last November, I walked through my experiences as a human SPOF, and the strategies I used to survive. In the intervening months, our team has hired several new DevOps engineers, with more on the way. But now we need to get all that knowledge out of my brain, and into a palatable format for consumption by others. At devopsdays SV 2016, I shared some of the challenges encountered in getting new engineers up to speed, when all the knowledge exists solely in my head. Several difficulties exist, affecting both the individual and the team as a whole. Prioritizing projects is complicated, because so much depends on knowledge that exists only in one place. Knowledge transfer can often be disjointed and difficult to organize, because the information is frequently tied up in the chaos of solo operations. And as we've started exploring all the components in our environments, we've revisited the sins of our past - corners cut and shortcuts taken in the interests of getting it done now, versus getting it done cleanly. Many of the tools were designed out of desperation, not with flexibility and maintainability in mind. Now it's time to figure out how to complete that transition, and move toward a more maintainable, survivable environment.
This is a follow-up to my talk from devopsdays SV 2015, entitled DevOps Army of One - How to Survive When You're the SPoF. I really enjoyed giving that talk, and since then I've gained not only some much-needed help, but insight into the difficulties involved in bringing the new engineers online.
Visualizing Work: If you can't see it, you can't manage itFernando Cuenca
Presentation delivered at Toronto Agile Conference - Oct 30, 2018
--
Unlike a factory, where we can see work literally moving around, piling up waiting, being worked on, or even deteriorating with time, knowledge workers have to deal with abstract constructs that are largely invisible. Suddenly, answering questions like "what are we working on?" or "how does work get done here" can become tricky.
The basic premise that the first step towards effectively managing knowledge work is to make it visible will not come as a surprise for anyone with some familiarity with Agile. That said, there's more to effective work visualization than a 3-column board showing "To Do | In Progress | Done" columns, and visualizing work items is only the first step.
This session will explore approaches for visualizing otherwise invisible aspects of work, such as commitments, process, rules and, of course, work items, and using them to enable more effective management and collaboration.
Every organisation pretends to be unique, but they mostly follow similar mechanics. Discover how your organisation too falls into common pitfalls and antipatterns and how you can leverage the situation to improve it.
Have you ever been the last to know something in your company? You were caught off guard when a few employees didn’t agree with your company’s direction, or you had no idea that a senior employee had put in her two weeks notice.
As a business owner, CEO or manager, you never want to be the last to know something in your company. In this talk, Claire will discuss how to avoid “being the last to know” as much as possible. You’ll learn a repeatable framework so you can get honest feedback from your employees. This way, you won’t be blind sided by unexpected problems, you can retain you best employees, and you can foster a healthy company culture to help your business win in the long-run.
You'll Never Look at Interactive the Same After this DeckDori Adar
Games and interactive systems are different from any other medium in that they require their users to constantly make decisions.
The decisions' type and the intensity of interaction define the global experience.
These two elements form the TIMT (The Interaction Mapping Tool). A tool that will help you quantify the user experience of any interactive activity and adjust it's variables properly to fit your users' state of mind.
Granted, you will not look at interactive media the same after this talk.
'10 Great but now Overlooked Tools' by Graham ThomasTEST Huddle
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
A dispute on probably the most controversial feature in ES2016 leads us back to age old questions at the base of the most common practices of the development universe.
Do the “sacred laws” still apply?
jsDay 2016 closing keynote (http://2016.jsday.it/talk/a-class-action/)
Joy Scharmen - The Virtuous Cycle: Getting Good Things Out of Bad FailuresJoy Scharmen
System failures happen. Hardware dies, software crashes, capacity gets exceeded, and any of these things can cause unexpected effects in the most carefully-architected systems.
At Heroku, we deal with complex systems failures. We’re running a platform as a service: our whole business model requires us to provide operations for our customers so they don’t have to do it themselves. We run over a million postgres databases, tens of thousands of redis, and hundreds of thousands of dynos on thousands of AWS instances.
What do we get out of these incidents? Pain and suffering? Yes, sometimes. We also get data about how our systems are actually working. We get ideas for making it work better. And sometimes we get ideas for whole new products.
In this talk, I’ll discuss how to take the bad of a system failure and turn it into good: better products, more reliable platforms, and less stressed engineers.
Retrospective Template: https://github.com/peculiaire/incident-lifecycle/blob/master/retrotemplate.md
How to Pitch Your Shareholders Like the Media (and get support for your ideas) Terri Trespicio
How do you get someone to listen to, let alone buy into, your ideas? Whether you're pitching external clients, internal clients, your boss, or your boss's boss, you need to understand how people listen (and why they tune out).
In this keynote address, given at Brand Experience Magazine's 2018 BXPLive event, branding pro Terri Trespicio, former editor at Martha Stewart and co-creator of Lights Camera Expert, gives you a new model and mindset for pitching your ideas.
Find out how to position your pitch and approach everyone from clients to the C-Suite using tools that experts and authors use to get media attention—so that you're in a better position to attract resources, recognition, and support for your efforts.
Presentation from October 4, 2015: Arts Midwest Orchestras 20/20: Context, Connection, Collaboration. An attempt to lay out the context of audience, competition, technology and strategy - then a set of practical steps to get things done.
Going Purple : From full time breaker to part time fixer: 1 year later Chris Gates
A little over a year ago I made the transition from external security consultant to internal offensive security engineer at Facebook. I went from a full time breaker to part time fixer. This talk is aimed at providing lessons learned and documenting the mindset changes I've made over the last year that I feel can be used by the industry as a whole. I've broken the lessons learned into three primary buckets; Red, Blue, and Purple and the talk will hopefully bring value to anyone working in their respective bucket or assist in their creation/continuing of purple teaming at their company.
You'll learn:
All the activities required for realistic design sprints
How to modify your agenda and activities for different timelines
How to incorporate quantitative and qualitative data into design sprints
Faster! Faster! Accelerate your business with blazing prototypesOSCON Byrum
Bring your ideas to life! Convince your boss to that open source development is faster and cheaper than the "safe" COTS solution they probably hate anyway. Let's investigate ways to get real-life, functional prototypes up with blazing speed. We'll look at and compare tools for truly rapid development including Python, Django, Flask, PHP, Amazon EC2 and Heroku.
Rundeck Community Office Hours: Using Variables with Job Steps Rundeck
Rundeck offers powerful runbook automation. Most Runbooks are complicated multi-step processes. We will show various examples of how to share data from one step to another through the use of Log Filters.
Come join this session to learn how to:
Use different types of Log Filters to gather variables from your Job Steps
Gather variables and use the values in other Job Steps
Use the Result Data feature to format your output in a consistent format regardless of the log output.
Visualizing Work: If you can't see it, you can't manage itFernando Cuenca
Presentation delivered at Toronto Agile Conference - Oct 30, 2018
--
Unlike a factory, where we can see work literally moving around, piling up waiting, being worked on, or even deteriorating with time, knowledge workers have to deal with abstract constructs that are largely invisible. Suddenly, answering questions like "what are we working on?" or "how does work get done here" can become tricky.
The basic premise that the first step towards effectively managing knowledge work is to make it visible will not come as a surprise for anyone with some familiarity with Agile. That said, there's more to effective work visualization than a 3-column board showing "To Do | In Progress | Done" columns, and visualizing work items is only the first step.
This session will explore approaches for visualizing otherwise invisible aspects of work, such as commitments, process, rules and, of course, work items, and using them to enable more effective management and collaboration.
Every organisation pretends to be unique, but they mostly follow similar mechanics. Discover how your organisation too falls into common pitfalls and antipatterns and how you can leverage the situation to improve it.
Have you ever been the last to know something in your company? You were caught off guard when a few employees didn’t agree with your company’s direction, or you had no idea that a senior employee had put in her two weeks notice.
As a business owner, CEO or manager, you never want to be the last to know something in your company. In this talk, Claire will discuss how to avoid “being the last to know” as much as possible. You’ll learn a repeatable framework so you can get honest feedback from your employees. This way, you won’t be blind sided by unexpected problems, you can retain you best employees, and you can foster a healthy company culture to help your business win in the long-run.
You'll Never Look at Interactive the Same After this DeckDori Adar
Games and interactive systems are different from any other medium in that they require their users to constantly make decisions.
The decisions' type and the intensity of interaction define the global experience.
These two elements form the TIMT (The Interaction Mapping Tool). A tool that will help you quantify the user experience of any interactive activity and adjust it's variables properly to fit your users' state of mind.
Granted, you will not look at interactive media the same after this talk.
'10 Great but now Overlooked Tools' by Graham ThomasTEST Huddle
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
A dispute on probably the most controversial feature in ES2016 leads us back to age old questions at the base of the most common practices of the development universe.
Do the “sacred laws” still apply?
jsDay 2016 closing keynote (http://2016.jsday.it/talk/a-class-action/)
Joy Scharmen - The Virtuous Cycle: Getting Good Things Out of Bad FailuresJoy Scharmen
System failures happen. Hardware dies, software crashes, capacity gets exceeded, and any of these things can cause unexpected effects in the most carefully-architected systems.
At Heroku, we deal with complex systems failures. We’re running a platform as a service: our whole business model requires us to provide operations for our customers so they don’t have to do it themselves. We run over a million postgres databases, tens of thousands of redis, and hundreds of thousands of dynos on thousands of AWS instances.
What do we get out of these incidents? Pain and suffering? Yes, sometimes. We also get data about how our systems are actually working. We get ideas for making it work better. And sometimes we get ideas for whole new products.
In this talk, I’ll discuss how to take the bad of a system failure and turn it into good: better products, more reliable platforms, and less stressed engineers.
Retrospective Template: https://github.com/peculiaire/incident-lifecycle/blob/master/retrotemplate.md
How to Pitch Your Shareholders Like the Media (and get support for your ideas) Terri Trespicio
How do you get someone to listen to, let alone buy into, your ideas? Whether you're pitching external clients, internal clients, your boss, or your boss's boss, you need to understand how people listen (and why they tune out).
In this keynote address, given at Brand Experience Magazine's 2018 BXPLive event, branding pro Terri Trespicio, former editor at Martha Stewart and co-creator of Lights Camera Expert, gives you a new model and mindset for pitching your ideas.
Find out how to position your pitch and approach everyone from clients to the C-Suite using tools that experts and authors use to get media attention—so that you're in a better position to attract resources, recognition, and support for your efforts.
Presentation from October 4, 2015: Arts Midwest Orchestras 20/20: Context, Connection, Collaboration. An attempt to lay out the context of audience, competition, technology and strategy - then a set of practical steps to get things done.
Going Purple : From full time breaker to part time fixer: 1 year later Chris Gates
A little over a year ago I made the transition from external security consultant to internal offensive security engineer at Facebook. I went from a full time breaker to part time fixer. This talk is aimed at providing lessons learned and documenting the mindset changes I've made over the last year that I feel can be used by the industry as a whole. I've broken the lessons learned into three primary buckets; Red, Blue, and Purple and the talk will hopefully bring value to anyone working in their respective bucket or assist in their creation/continuing of purple teaming at their company.
You'll learn:
All the activities required for realistic design sprints
How to modify your agenda and activities for different timelines
How to incorporate quantitative and qualitative data into design sprints
Faster! Faster! Accelerate your business with blazing prototypesOSCON Byrum
Bring your ideas to life! Convince your boss to that open source development is faster and cheaper than the "safe" COTS solution they probably hate anyway. Let's investigate ways to get real-life, functional prototypes up with blazing speed. We'll look at and compare tools for truly rapid development including Python, Django, Flask, PHP, Amazon EC2 and Heroku.
Similar to Tickets Make Ops Unnecessarily Miserable: The Journey to Self-Service (20)
Rundeck Community Office Hours: Using Variables with Job Steps Rundeck
Rundeck offers powerful runbook automation. Most Runbooks are complicated multi-step processes. We will show various examples of how to share data from one step to another through the use of Log Filters.
Come join this session to learn how to:
Use different types of Log Filters to gather variables from your Job Steps
Gather variables and use the values in other Job Steps
Use the Result Data feature to format your output in a consistent format regardless of the log output.
Most of what Rundeck does is via one of it’s plugins. There are already over 100+ plugins to perform various services including executing commands on nodes, performing step in a workflow, or sending notification about job status. There may be instances where you need to write your own plugin to perform a specific step or action. In this session, will walk through the steps for writing our own plugin.
In this session you'll learn:
Review the structure of plugin
How to use the structure and what information you need to include in other files to make your plugin work
How to write a simple plugin example using java
How to reply and use your plugin
Lunch and learn: Getting started with Rundeck & AnsibleRundeck
Operations teams depend on a mixture of tools to keep their systems running. One popular pairing for Rundeck users is integrating Ansible playbooks into Rundeck to orchestrate and schedule workflows across multiple tools.
Join us for this Lunch and Learn event to learn how you can use Rundeck to create runbooks that span your existing Ansible playbooks -- as well as any other scripts, tools, APIs, or systems commands, to respond to incidents or perform Operations tasks.
Join us to learn:
Benefits of using Rundeck and Ansible together
How to configure your Rundeck to use the Ansible plugin
Tips for getting started with the integration
And see a demo of the integration
This event is recommended for beginners.
Self Service Cloud Operations: Safely Delegate the Management of your Cloud ...Rundeck
Running Operations is not an easy job, especially these days. Ops teams have to ensure excellent user experiences, resolve incidents quickly and help developers stay productive. Yet at the same time, there is also the need to maintain systems security and keep downtime to a minimum.
While advances in cloud computing have helped address some of these challenges, many organizations find it difficult to leverage the cloud at scale because of bottlenecks that form around repetitive tasks, such as developers having to wait for provisioning infrastructure. Despite having access to abundant cloud resources, these speedbumps often make it difficult to achieve team objectives.
Join this talk to learn:
How to safely delegate the management of your cloud deployment (to developers and other end users) with self-service operations.
How to create powerful runbooks with guardrails that leverage existing scripting languages, infrastructure, and tools to remove bottlenecks that form around repetitive tasks.
Strategies for getting started with self-service.
Rundeck Office Hours: Best Practices Access Control PoliciesRundeck
Join us this month for an AMA discussion followed by a live Q&A led by technical experts from Rundeck’s engineering, product, and solution engineering teams. Experts are available to provide advice on your technical architecture, give recommendations for operational best practices, review current Github issues, or dive into the open source code itself.
Don’t miss the opportunity to learn Rundeck product best practices and ask experts your questions about Rundeck.
https://www.rundeck.com/rundeck-office-hours
Secure IT infrastructure is well protected by access keys, passwords, and other credentials. Admins need these secrets to gain access, as does any automation executed by Rundeck. Rundeck has rich support for secrets management with native key storage, as well as integrations with best-of-breed standardized solutions. In this webinar, we’ll cover best practices for working with Rundeck’s runbook automation platform in securing IT infrastructure. We’ll explore the secrets management options in Rundeck and we’ll highlight a new plugin with Thycotic Secret Server for Privileged Access Management.
In this webinar, we will demonstrate:
How Rundeck works with underlying secrets of the systems it manages
New Rundeck plugins that allow users to protect privileged accounts with enterprise-grade, privileged access management solutions
How you can use Rundeck plugins with HashiCorp Vault, Thycotic, and CyberArk as keys for jobs and other Rundeck configurations
In this session we will give a live walkthrough covering new capabilities released in Rundeck 3.4. Learn about security & compliance improvements we’ve made including the ability to organize secrets management by project -- so now each Runbook can access a different set of passwords and keys for its access control list (ACL). We also have a new plug-in for Thycotic users to manage secrets. Rundeck 3.4 now allows for queueing of jobs when those jobs must be run serially. Finally, we’ll discuss our vision for the future of Rundeck, and our primary development themes for the next year.
Automate Yourself Out of a Job: Safely Delegate the Management of your Azure...Rundeck
Running Operations is not an easy job, especially these days. Ops teams have to ensure excellent user experiences, resolve incidents quickly and help developers stay productive. Yet at the same time, there is also the need to maintain systems security and keep downtime to a minimum - goals which many struggle with at scale.
While advances in cloud computing have helped address some of these challenges, many organizations find it difficult to leverage the cloud at scale because of bottlenecks that form around repetitive tasks, such as developers having to wait for provisioning infrastructure. Despite having access to abundant cloud resources, these speedbumps often make it difficult or impossible to achieve team objectives.
Join this talk to learn:
-How to safely delegate the management of your Azure deployment (to developers and other colleagues) with self-service operations.
-How to create powerful runbooks with guardrails that leverage existing scripting languages (including PowerShell), infrastructure, and tools to remove the human from the bottleneck that forms around repetitive tasks.
-Strategies for getting started
-And how to create an Easy Button to handle the repetitive tasks that are interrupting your flow of work.
As presented by Jesse Houldsworth at PowerShell + DevOps Global Summit 2021
Super-Charge Your Site Reliability Practices with Runbook Automation Rundeck
On Demand Viewing: https://www.rundeck.com/super-charge-reliability
To win in today’s digital age, organizations need to balance product reliability and feature delivery with dynamic business needs and legacy and multi-cloud environments. Automation, as a main SRE practice, scales product reliability practices by reducing tedious tasks related to production operations, freeing up engineers to work on innovation.
Whether you are in a traditional operations organization or a “you build it, you run it” team, this webinar will explore strategies for increasing automation to improve your Operations so you can continue to create excellent experiences for your customers.
-How you can reduce MTTR and eliminate toil with Self-Service Operations
-Common workflow challenges and opportunities
-How you can use Runbook Automation to enable Self-Service Operations
-Ways to leverage existing assets and workflows by integrating Rundeck with existing toolsets
-See a demo of real world cases
https://youtu.be/4jAf6cbxsgo
As operators, it’s our job to monitor infrastructure, systems and applications and only wake up humans for tasks machines can’t fix on their own. Automated remediation pairs monitoring and runbook automation, giving you a monitoring system that can trigger operational actions with runbook automation to shorten incident response times and avoid alert fatigue.
Rundeck Director of Product Management Forrest Evans and Sensu Developer Advocate Todd Campbell discuss the key role automated remediation plays in the monitoring journey, with live demos of both the Rundeck and Sensu integrations. You’ll learn all about monitoring as code workflows with the Sensu Observability Pipeline and how to deliver runbook automation with Rundeck — and see how the two together can help you achieve automated remediation.
Failure is inevitable. But are you incurring more downtime and disruption than necessary? Legacy incident response techniques have difficulty keeping up with the increasing pace of change and skyrocketing complexity of today’s application environments.
During this webinar, you’ll learn about modern incident response techniques that can dramatically shorten incidents and reduce escalations. Join the experts from Rundeck and PagerDuty as they share:
*How a real-time operations platform intelligently manages alerts and on-call mobilization, delivering the right people the right information at the right time
*How runbook automation gives front-line response teams self-service access to run automated workflows – or runbooks – that diagnose and resolve incidents without escalating to an expert.
*How to automatically detect, diagnose, and resolve incidents without human intervention.
https://youtu.be/9yYwTPMRSOY
Nathan Fluegel, head of Customer Success at Rundeck, talks clustering and high availability. We'll show how to deploy Rundeck servers in a clustered configuration with Rundeck Enterprise.
https://youtu.be/PmBIGP3M9sI
Understand how to migrate your Rundeck environment from the community edition to Enterprise, including the pros and cons of each migratory approach.
In this webinar, you will learn how to:
-Determine which migration approach is most appropriate for your environment
-Shift from a single-server to clustered environment
-Migrate jobs and projects while keeping a clean install
Business Continuity for Humans: Keeping Your Business Running When Your Peopl...Rundeck
Damon Edwards (Rundeck) presentation from TechStrongConf on June 4, 2020.
Learn more: https://www.rundeck.com/business-continuity-for-digital-operations
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
6. Hello
Meet OpsHero
8 years experience
Last line of defense when
things go wrong
People turn to when things
need to get done
7. Hello
Meet OpsHero
8 years experience
Last line of defense when
things go wrong
People turn to when things
need to get done
Knows how things actually work
8. Hello
Meet OpsHero
Kick-ass scripter
(/home/opshero/bin is in
every co-worker’s $PATH)
8 years experience
Last line of defense when
things go wrong
People turn to when things
need to get done
Knows how things actually work
13. The interruptions…
Project A
···
Project B
···DUE: Yesterday! DUE: Tomorrow!
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
14. The interruptions…
Project A
···
Project B
···DUE: Yesterday! DUE: Tomorrow!
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Mmm, ya…
I’m gonna need
this and the other
stuff right away.
Boss
15. The interruptions…
Project A
···
Project B
···DUE: Yesterday! DUE: Tomorrow!
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Mmm, ya…
I’m gonna need
this and the other
stuff right away.
Boss
Colleague
What do you
know about…?
16. The interruptions…
Project A
···
Project B
···DUE: Yesterday! DUE: Tomorrow!
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Ticket
Mmm, ya…
I’m gonna need
this and the other
stuff right away.
Boss
Colleague
What do you
know about…?
Hey! Flair Service is
super slow.
Customer
20. The incidents…
Uh oh…
What changed?!
WAAH!! … the site is
slow … now it is down!
Is anybody working on
fixing this?
NOBODY TOUCH
ANYTHING ELSE!!
Oh no my fix
made it worse.
21. The Fear…
Is this next
outage the one
that ends our
careers?
It could all go wrong
at any minute!
This fix sure feels
shaky
We might drown in
all of this tech debt
22. The Slog…
Uh oh, I’ve got to
go into Prod… this is
going to hurt
Can you believe they said,
“where’s your TICKET?!”
This is the same
rigamarole as last
week!… Again!
I lost a whole day
working on that
emergency
All I’ll hear about later
is “why couldn’t it be
fixed quicker?”
23. I’m frustrated and tired.
Isn’t there a way to work smarter, not harder?
29. Silos are bad
Backlog Information
I need X
PrioritiesTools
Backlog
I do X
Requests
for X
Silo A
Information
Priorities
Silo B
Tools
30. Silos are bad
Backlog Information
I need X
PrioritiesTools
Backlog
I do X
Requests
for X
Silo A
Information
Priorities
Silo B
Tools
Context
Context
Process
Process
Tooling
Tooling
Capacity
Capacity
34. Queues are
expensive
Queues Create…
Longer Cycle Time
Increased Risk
More Variability
More Overhead
Lower Quality
Less Motivation
Adapted from Donald G. Reinertsen, The Principles of Product Development Flow: Second Generation Lean Product Development
We weren’t the only ones to realize that queues are expensive
35. Queues are
expensive
??
Silo A Silo B
Ticket
Queue
Queues encourage “snowflakes” (technically ok, but unreproducible and brittle)
36. Queues are
expensive
??
Silo A Silo B
Ticket
Queue
Queues encourage “snowflakes” (technically ok, but unreproducible and brittle)
38. We started by talking to
executives about re-organizing.
39. Big re-org!
Get rid of the silos!
Old Silo A Old Silo B Old Silo C Old Silo D
40. Big re-org!
DevOps product teams seemed like a great idea!
Old Silo A Old Silo B Old Silo C Old Silo D
Cross-Functional Team 1
Cross-Functional Team 2
Cross-Functional Team n
41. Big re-org!
DevOps product teams seemed like a great idea!
Old Silo A Old Silo B Old Silo C Old Silo D
Cross-Functional Team 1
Cross-Functional Team 2
Cross-Functional Team n
Key 1: get rid of as many
handoffs as possible
42. Big re-org!
DevOps product teams seemed like a great idea!
Old Silo A Old Silo B Old Silo C Old Silo D
Cross-Functional Team 1
Cross-Functional Team 2
Cross-Functional Team n
Key 2: “Horizontal”
shared responsibility, not
everyone do everything!
Key 1: get rid of as many
handoffs as possible
45. Same-org!
Dev to QA looks different, but Ops is still Ops!
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
46. So how do you get rid of the
interruptions and repetitive work
requests?
47. We took it upon ourselves to look at all
of the handoffs and ticket queues…
48. Self-Service
…and applied “Self-Service Operations” wherever we could.
Self-Service Operations
On
Demand
On
Demand
On
Demand
On
Demand
Ops
Capability
Ops
Capability
Ops
Capability
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
Ops
49. Self-Service
…and applied “Self-Service Operations” wherever we could.
Self-Service Operations
On
Demand
On
Demand
On
Demand
On
Demand
Ops
Capability
Ops
Capability
Ops
Capability
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
Pull-based
Ops
50. Self-Service
…and applied “Self-Service Operations” wherever we could.
Self-Service Operations
On
Demand
On
Demand
On
Demand
On
Demand
Ops
Capability
Ops
Capability
Ops
Capability
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
Pull-based
Bi-directional
Ops
51. Self-Service
…and applied “Self-Service Operations” wherever we could.
Self-Service Operations
On
Demand
On
Demand
On
Demand
On
Demand
Ops
Capability
Ops
Capability
Ops
Capability
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
Pull-based
Bi-directional
On-demand
Ops
52. Self-Service
…and applied “Self-Service Operations” wherever we could.
Self-Service Operations
On
Demand
On
Demand
On
Demand
On
Demand
Ops
Capability
Ops
Capability
Ops
Capability
Development Team 1
Development Team 2
Development Team n
Ops/SRE
Team
Pull-based
Bi-directional
On-demand
With security and guardrails
Ops
59. Not good…
… and there were lots of arguments about which language.
?
?
?
It’s got to be
Puppet.
Ruby? No way.
Python only!
Bash is what we
all know!
Ansible or bust.
We are stuck on
BladeLogic.
Powershell…
My team is
windows.
60. Oh, and both security and
compliance thought we were nuts.
61. Don’t worry my friend. I went
through the same growing
pains.
66. Attack the
“Do it.
Do it again.
And again.
And again.”
Anti-
Patterns
Done.
I need you to
do X
Later…
Ticket
Other
work
Done.
I need you to
do X
Later…
Ticket
Other
work
Sigh..Done.
I need you to
do X
Ticket
Other
work
Before
67. Attack the
“Do it.
Do it again.
And again.
And again.”
Anti-
Patterns
Done.
I need you to
do X
Later…
Ticket
Other
work
Done.
I need you to
do X
Later…
Ticket
Other
work
Sigh..Done.
I need you to
do X
Ticket
Other
work
Before
Do X
Later…
Other
work 1
Later…
Other
work 2
Other
work 3
Do X
Do X
Self-Service
Self-Service
Self-Service
After
69. Attack the
“I’m an Expert!
I don’t read the wiki”
Anti-
Patterns
Before
docs
Service has changed. Use this flag or
bad things will happen!
Pause monitoring first or
we all get woken up!
“restart -doit -now”
I’ve done this before.
I’ve got this…
Environment
docs
Later…
70. Attack the
“I’m an Expert!
I don’t read the wiki”
Anti-
Patterns
Before
docs
Service has changed. Use this flag or
bad things will happen!
Pause monitoring first or
we all get woken up!
“restart -doit -now”
I’ve done this before.
I’ve got this…
Environment
docs
Later…
Self-Service
Service has changed. This flag is now
required or bad things will happen!
Pause monitoring first or
we all get woken up!
“restart”
Environment
Later…
Update
Restart Job
✅
I’ve done this before.
I’ve got this.
Self-Service
After
72. Attack the
“I could fix it.
But I can’t access it.”
Anti-
Patterns
Before Environment
I could fix it if I
could get to it
73. Attack the
“I could fix it.
But I can’t access it.”
Anti-
Patterns
Before Environment
I could fix it if I
could get to it
After
Environment
I’ve got this!
Self-
Service
75. Attack the
“The Dog Pile”
Anti-
Patterns
Before
I think its a problem with
dbcluster07-store2.uswest.acme
dbcluster07-
store2.uswest.
acme
“$ top”
“$ top”
“$ top”
“$ top”
“$ top”
“$ top”“$ top”
76. Attack the
“The Dog Pile”
Anti-
Patterns
Before
I think its a problem with
dbcluster07-store2.uswest.acme
dbcluster07-
store2.uswest.
acme
“$ top”
“$ top”
“$ top”
“$ top”
“$ top”
“$ top”“$ top”
After I think its a problem with
dbcluster07-store2.uswest.acme
dbcluster07-
store2.uswest.
acme
“$ top”
“Healthcheck
store2 - all”
OaaSSelf-Service
77. As far as the automation language wars…
we decided to rethink it.
79. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
80. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
81. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
82. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
83. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
84. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
85. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
86. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
User input handling
87. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
User input handling
Infrastructure model
88. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
User input handling
Infrastructure model
UI, API, CLI
89. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
User input handling
Infrastructure model
UI, API, CLI
Scheduling
90. Start where
you are
#! Ȑ Ƙ
Scripts APIs Tools Cloud VMs Containers
>_
Web GUI API CLI
Self-Service Platform
Let people use the skills they already have.
Existing scripts and
tools
Workflow
Access control
Error handling
Notifications
User input handling
Infrastructure model
UI, API, CLI
Scheduling
91. Enable others
Once team’s are creating their own self-service, then build
out the platform.
Self-Service Operations Platform
Engineers get visibility
and controlled self-service
Secrets
Ops Procedures
“Status”
“Firewall Change”
"Restart"
deny
allow
Identity Audit Logs
Infrastructure view
Service health
System metrics
Ops Support use for
remediation procedures
Inventory and Health
Execute
+
Security and Ops manages
access, configuration, and compliance
/ Monitoring
92. Embrace
Make sure people can work through their SDLC
Self-Service Operations Platform
Engineers get visibility
and controlled self-service
Secrets
Ops Procedures
“Status”
“Firewall Change”
"Restart"
deny
allow
Identity Audit Logs
Infrastructure view
Service health
System metrics
Ops Support use for
remediation procedures
Inventory and Health
Execute
Source Code
Repo
if (($state==wait))
then
kill -9 $PID
fi
Change
Product Engineers
produce automated
procedures and health
checks.
RISKY
Automated Procedures
and Health Checks
FIX
Code review
+
Security and Ops manages
access, configuration, and compliance
/ Monitoring
DevOps
93. Leverage
Then integrate to your other enterprise systems
Service Desk
CustomersOps Support get
visibility and audit trail
updated by support tools
Service Ticket
Execute
Artifact and
Container
Management Ops integrate
with artifact
flow
Self-Service Operations Platform
Engineers get visibility
and controlled self-service
Secrets
Ops Procedures
“Status”
“Firewall Change”
"Restart"
deny
allow
Identity Audit Logs
Infrastructure view
Service health
System metrics
Ops Support use for
remediation procedures
Inventory and Health
Source Code
Repo
if (($state==wait))
then
kill -9 $PID
fi
Change
Product Engineers
produce automated
procedures and health
checks.
RISKY
Automated Procedures
and Health Checks
FIX
Code review
+
Security and Ops manages
access, configuration, and compliance
/ Monitoring
Investments
94. Improved
Once they see it in action, Compliance and Security will be big fans.
Service Desk
CustomersOps Support get
visibility and audit trail
updated by support tools
Service Ticket
Execute
Artifact and
Container
Management Ops integrate
with artifact
flow
Approval trail?
Self-Service Operations Platform
Engineers get visibility
and controlled self-service
Secrets
Ops Procedures
“Status”
“Firewall Change”
"Restart"
deny
allow
Identity Audit Logs
Infrastructure view
Service health
System metrics
Ops Support use for
remediation procedures
Inventory and Health
Source Code
Repo
if (($state==wait))
then
kill -9 $PID
fi
Change
Product Engineers
produce automated
procedures and health
checks.
RISKY
Automated Procedures
and Health Checks
FIX
Code review
+
Security and Ops manages
access, configuration, and compliance
/ Monitoring
Who reviewed it? Who ran it? When? Where?
Who created the procedure?
Who created the policy?Controls
95. Ah. I think I now see a path
forward. I’ll give it a try!
96. Ah. I think I now see a path
forward. I’ll give it a try!
Cheers!
99. I love Ops!
“Do X”
“Define Y
Procedure”
“Define X
Procedure”
“Do Y”
“Do X+Y”
Self-Service
Self-service is flourishing
Everyone is noticing the improvement
Fewer Interruptions
Less Waiting
Getting More Done
You are going
places.
100. Life is good!
My stature amongst my
colleagues is growing!
My work is way
more satisfying!
!!
So I’ve been
noticing…
And I’m getting a raise!
101. That is fantastic!!
You are working smarter (not harder) and
making life better for your colleagues!
103. So now… tell me about
this SRE thing…
We’re definitely going to
need more beers!
104. So now… tell me about
this SRE thing…
We’re definitely going to
need more beers!
But that is a story for next time!
105. The End
OpsHero ……………..…. Alex Honor
Mentor ..………..……….. Damon Edwards
Narrator………………….. Nathan Fluegel
Directed by ……………… Damon Edwards
Written by ………………. Alex Honor
Damon Edwards
Let’s talk ………………… @rundeck
www.rundeck.com