This document discusses DevOps and continuous delivery. It defines DevOps as a cultural and professional movement to improve software delivery through automation, measurement, and collaboration between development and operations teams. The key aspects of DevOps discussed are adopting infrastructure as code practices, implementing continuous integration and deployment pipelines, and establishing a culture of automation, measurement, and sharing between teams. The overall goal is to enable software to be delivered safely and reliably in a matter of hours through establishing these collaborative practices.
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers, we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. In this talk, we'll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We'll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. We however spend very little time learning to understand and respond to outages.
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven’t nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
In this talk we ll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We ll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers, we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. In this talk, we'll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We'll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. We however spend very little time learning to understand and respond to outages.
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven’t nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
In this talk we ll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We ll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
Rise of the Machines: Can Artificial Intelligence Terminate Manual Testing?TechWell
The state of the art in automated software testing is far from being a replacement for human-guided testing. There is more to testing than setting up preconditions, applying inputs, verifying outputs, and logging the results. Testing requires significant planning, exploring, learning, modeling, inferencing, experimenting, and more. Therefore, before we can truly automate testing, we must bridge the gap between the testing capabilities of humans and machines. Tariq King says that breakthroughs in artificial intelligence (AI) and machine learning (ML) are challenging our thinking about the types of problems that machines can tackle. Can AI discoveries—a machine that masters a game like Go or autonomously drives an unmanned vehicle—help us find better solutions for automated oracles, test generation, system modeling, and defect discovery? Tariq believes they can and will share his vision of how. Drawing on his experiences working on, leading, and advising teams in the development of software that automatically tests software, Tariq walks us through recent advances in AI and ML. Join Tariq as he maps these advances to potential solutions for important software testing research problems.
Leveraging data visualization to improve the efficiency of large-scale test automation infrastructure.
Watch the full talk at: http://youtube.com/watch?v=oRIci6n566w
Applying principles of chaos engineering to Serverless (CodeMotion Berlin)Yan Cui
Chaos engineering is a discipline that focuses on improving system resilience through experiments that expose the inherent chaos and failure modes in our system, in a controlled fashion, before these failure modes manifest themselves like a wildfire in production and impact our users.
Netflix is undoubtedly the leader in this field, but much of the publicised tools and articles focus on killing EC2 instances, and the efforts in the serverless community has been largely limited to moving those tools into AWS Lambda functions.
But how can we apply the same principles of chaos to a serverless architecture built around AWS Lambda functions?
These serverless architectures have more inherent chaos and complexity than their serverful counterparts, and, we have less control over their runtime behaviour. In short, there are far more unknown unknowns with these systems.
Can we adapt existing practices to expose the inherent chaos in these systems? What are the limitations and new challenges that we need to consider?
TDD - Unit testing done right and programmer happinessErez Cohen
Test Driven Development has been around for a while but it has been dismissed by many as a superfluous and tedious way of developing software.
I have discovered through experience that it helps me create better quality code while turning the development into an even more enjoyable process.
In this talk I explain what makes it so great, tackle some of the criticism and share some tips regarding better unit testing.
Agile Development Practices - ProductivityAlex Moore
Lunch and Learn I did on some general Agile and other practices that can make developers more productive.
Most of the content was in the speech though unfortunately.
20 min sponsored talk presentation on Agile PT 2011 conference (http://2011.agilept.org/program/talk-tiago-pascoal).
Some slides are less than legible since they have animations. Apologies for that
Herman- Pieter Nijhof - Where Do Old Testers Go?TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Where Do Old Testers Go? by Herman- Pieter Nijhof. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
More Aim, Less Blame: How to use postmortems to turn failures into something ...Daniel Kanchev
Mistakes and failure are inevitable. Instead of being afraid of them, we should use them as lessons that help identify weak points in our organisations and systems. One way to do this is by writing blameless postmortems. Daniel details exactly how postmortems can help organizations and teams focus on improvement, and how that boosts work morale, makes products better, and strengthens your relationship with customers.
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013TEST Huddle
EuroSTAR Software Testing Conference 2013 presentation on Software Testing Secrets We Dare Not Tell by Graham Thomas.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
STARCANADA 2015: Lightning Strikes the KeynotesTechWell
Throughout the years, Lightning Talks have been a popular part of the STAR conferences. If you’re not familiar with the concept, Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period. Lightning Talks are the opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation. And now, lightning has struck the STAR keynotes. Some of the best-known experts in testing will step up to the podium and give you their best shot of lightning. Get multiple keynote presentations for the price of one—and have some fun at the same time.
Joy of Coding Conference 2019 slides - Alan RichardsonAlan Richardson
Adventures in Testing, Programming, Teaching, Automating and Marketing
When you already know how to code, it's easy to forget how hard some of that learning was... until you have to teach people. And if all you've ever built are applications, you don't know really know the nuances of writing code to automate them. And if you've written the code but never had to market the applications then you've not really experienced the full joy of coding.
In this presentation Alan will revisit many of his past projects to identify lessons learned. Lessons from: writing commercial and open source tools, multi-user adventure games, REST APIs, test automation, automating applications to make them do things they are not supposed to do, and coding for technical marketing.
Some lessons we will learn:
* The 'install' is the hardest part
* Writing frameworks is too much fun and should be banned
* Applications are just "code calling other libraries"
* Writing a Text Adventure s the most fun and educational thing you'll ever code
* The Dangers of knowing how to code
We will also learn the dangers of knowing how to code and discover how our coding skills can give us an edge, in business and online live in general, if we choose to harness our skills to improve our daily experiences.
Adopting Devops , Stories from the trenchesKris Buytaert
As presented at Baltic Devops in Talllinn ,
Starting with devops is either the most trivial, or the hardest thing to do.
This talk will teach you a number of tricks on how to make life easier for your team. How to work together with your management and how to convince them devops is a relevant thing
Rise of the Machines: Can Artificial Intelligence Terminate Manual Testing?TechWell
The state of the art in automated software testing is far from being a replacement for human-guided testing. There is more to testing than setting up preconditions, applying inputs, verifying outputs, and logging the results. Testing requires significant planning, exploring, learning, modeling, inferencing, experimenting, and more. Therefore, before we can truly automate testing, we must bridge the gap between the testing capabilities of humans and machines. Tariq King says that breakthroughs in artificial intelligence (AI) and machine learning (ML) are challenging our thinking about the types of problems that machines can tackle. Can AI discoveries—a machine that masters a game like Go or autonomously drives an unmanned vehicle—help us find better solutions for automated oracles, test generation, system modeling, and defect discovery? Tariq believes they can and will share his vision of how. Drawing on his experiences working on, leading, and advising teams in the development of software that automatically tests software, Tariq walks us through recent advances in AI and ML. Join Tariq as he maps these advances to potential solutions for important software testing research problems.
Leveraging data visualization to improve the efficiency of large-scale test automation infrastructure.
Watch the full talk at: http://youtube.com/watch?v=oRIci6n566w
Applying principles of chaos engineering to Serverless (CodeMotion Berlin)Yan Cui
Chaos engineering is a discipline that focuses on improving system resilience through experiments that expose the inherent chaos and failure modes in our system, in a controlled fashion, before these failure modes manifest themselves like a wildfire in production and impact our users.
Netflix is undoubtedly the leader in this field, but much of the publicised tools and articles focus on killing EC2 instances, and the efforts in the serverless community has been largely limited to moving those tools into AWS Lambda functions.
But how can we apply the same principles of chaos to a serverless architecture built around AWS Lambda functions?
These serverless architectures have more inherent chaos and complexity than their serverful counterparts, and, we have less control over their runtime behaviour. In short, there are far more unknown unknowns with these systems.
Can we adapt existing practices to expose the inherent chaos in these systems? What are the limitations and new challenges that we need to consider?
TDD - Unit testing done right and programmer happinessErez Cohen
Test Driven Development has been around for a while but it has been dismissed by many as a superfluous and tedious way of developing software.
I have discovered through experience that it helps me create better quality code while turning the development into an even more enjoyable process.
In this talk I explain what makes it so great, tackle some of the criticism and share some tips regarding better unit testing.
Agile Development Practices - ProductivityAlex Moore
Lunch and Learn I did on some general Agile and other practices that can make developers more productive.
Most of the content was in the speech though unfortunately.
20 min sponsored talk presentation on Agile PT 2011 conference (http://2011.agilept.org/program/talk-tiago-pascoal).
Some slides are less than legible since they have animations. Apologies for that
Herman- Pieter Nijhof - Where Do Old Testers Go?TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Where Do Old Testers Go? by Herman- Pieter Nijhof. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
More Aim, Less Blame: How to use postmortems to turn failures into something ...Daniel Kanchev
Mistakes and failure are inevitable. Instead of being afraid of them, we should use them as lessons that help identify weak points in our organisations and systems. One way to do this is by writing blameless postmortems. Daniel details exactly how postmortems can help organizations and teams focus on improvement, and how that boosts work morale, makes products better, and strengthens your relationship with customers.
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013TEST Huddle
EuroSTAR Software Testing Conference 2013 presentation on Software Testing Secrets We Dare Not Tell by Graham Thomas.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
STARCANADA 2015: Lightning Strikes the KeynotesTechWell
Throughout the years, Lightning Talks have been a popular part of the STAR conferences. If you’re not familiar with the concept, Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period. Lightning Talks are the opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation. And now, lightning has struck the STAR keynotes. Some of the best-known experts in testing will step up to the podium and give you their best shot of lightning. Get multiple keynote presentations for the price of one—and have some fun at the same time.
Joy of Coding Conference 2019 slides - Alan RichardsonAlan Richardson
Adventures in Testing, Programming, Teaching, Automating and Marketing
When you already know how to code, it's easy to forget how hard some of that learning was... until you have to teach people. And if all you've ever built are applications, you don't know really know the nuances of writing code to automate them. And if you've written the code but never had to market the applications then you've not really experienced the full joy of coding.
In this presentation Alan will revisit many of his past projects to identify lessons learned. Lessons from: writing commercial and open source tools, multi-user adventure games, REST APIs, test automation, automating applications to make them do things they are not supposed to do, and coding for technical marketing.
Some lessons we will learn:
* The 'install' is the hardest part
* Writing frameworks is too much fun and should be banned
* Applications are just "code calling other libraries"
* Writing a Text Adventure s the most fun and educational thing you'll ever code
* The Dangers of knowing how to code
We will also learn the dangers of knowing how to code and discover how our coding skills can give us an edge, in business and online live in general, if we choose to harness our skills to improve our daily experiences.
Adopting Devops , Stories from the trenchesKris Buytaert
As presented at Baltic Devops in Talllinn ,
Starting with devops is either the most trivial, or the hardest thing to do.
This talk will teach you a number of tricks on how to make life easier for your team. How to work together with your management and how to convince them devops is a relevant thing
Money, Process, and Culture- Tech 20/20 June, 2012Adrian Carr
A talk about Company Culture, Software, People, Lean Thinking, Agile Software.
This is the Powerpoint for a talk I gave at Tech2020, in Oak Ridge, Tennessee in June, 2012.
Cost reconciliation in a post CMDB worldBram Vogelaar
Back in the day in a IT company long ago, where the BOFHs roamed and the ITIL was strong. We used to keep long lists of CIs that used to enviably and hopelessly out of date. Because we either didnt care, know or bother keeping up to date. That was totally fine in a relatively static environment the IT company of long ago. We would have our yearly inventory day and forget about it again.
Of course we all use some form of infrastructure as code right now. Some of us might go as far that "if it isn't in code it doesnt exist", but can we truly say that whatever is in the OpenTofu state really is the only thing running? What about that recurring 1$ in that dormant AWS account, where is that coming from? How about the playground projects the CEO likes to play around with in his sparetime? or that one time the opentofu destroy didnt exit cleanly and some resources weren't cleaned during that timeout, did we really manually cleanup all resources?
Self scaling Multi cloud nomad workloadsBram Vogelaar
During this talk we will discuss the problems encountered and the solutions implemented while dealing with building out a multi-cloud strategy. We will start by taking our first steps building a multi-region, multi-cloud Nomad cluster and discussing some pitfalls we encountered, since not all cloud providers are built the same. We’ll finish our talk by diving into ingress patterns and Consul config to be able to survive pretty much any outage or price change. Maintaining these config can be quite cumbersome but they’re are also a prime target to automate using Consul watches.
We all know the wall of illegible wall of small graphs, that we like to present to (senior) management and auditors as proof that we do observability. It doesnt matter that the person ( and the associated knowledge) has long since left the company, nor that the dashboard doesnt autorefresh and still show the same data from when we turned on the monitoring PC.
In an ever changing IT landscape we deserve better than that. We shouldn't have to rely on the gut instinct of the senior engineer on deck about the general shape of the dashboard to know where to start fixing whatever it is that needs fixing.
We should aim to collect and present such information both from the it and business side that let a relatively inexperienced oncall engineer differentiate between a P1 incident and a major client/customer/continet going to bed.
We should be telling beautiful stories with data and dashboards in such a way that (even) management can pull up global dashboard and can determine business relevant information like "is our advertisement campaign having any impact". We should also not be afraid to have multiple dashboards that show different relevant information to stack holders (e.g sales figures for management and links to runbooks for engineers)
10 things i learned building nomad-packsBram Vogelaar
The nomad team has been working very hard on making templated deploys easy for this they have released the tech preview of nomad-pack. This talk discusses some of my observations while migrating nomad job files over to nomad-pack
10 things I learned building Nomad packsBram Vogelaar
The nomad team has been working very hard on making templated deploys easy for this they have released the tech preview of nomad-pack. This talk discusses some of my observations while migrating nomad job files over to nomad-pack
Easy Cloud Native Transformation with NomadBram Vogelaar
HashiCorp Nomad is a flexible and straightforward scheduler and orchestrator to deploy and manage containers and non-containerized applications across on-prem and clouds at scale.
Nomad can be seen as:
- an alternative to Kubernetes to deploy and scale containers without complexity
- a supplement to Kubernetes to implement a multi-orchestrator platform
On the other hand, this session will present how to ease the Cloud Native Transformation using Nomad.
The nomad team has been working hard to make sure that running Nomad is as easy as possible. For that they have introduced native service discovery and secret management and the ecosystem is picking up speed and tools like Traefik and Prometheus now support it out of the box. With the introduction of nomad-pack and the community registry it is now easier than ever to start nomad jobs. During this talk we ll discuss how to plumb all these together and why running Nomad has never been easier.
As engineers we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. We however spend very little time learning to understand and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
Plenty of people are jumping on the new hype, Observability, lots of them are replacing their “legacy” monitoring stack. Not all of them achieve the goals they set. But observability is not a tool — it is a property of a system. Moving from many small black boxes to a more holistic view of your system.
In this talk we ll talk about how to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems. We look at improving your monitoring by adapting your culture and then maybe your tooling. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior.
Furthermore we ll discuss the need for and the options of not only monitoring our platforms and it's envitable outages, but also their (potential) length and impact. We ll look at tools like at using Service Level Objects for ways to prepare teams to tweak their testing and monitoring setup and runbooks to quickly observe, react to and resolve problems.
Running Trusted Payload with Nomad and WaypointBram Vogelaar
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages.
With the the introduction of CI/CD best practices into our day to day workflows we protect ourselves for introducing "bad" code into production and exposing flaws to our (end-)users. But what about influences from bad actors in- and out-side our projects. This talk will focus on the additional steps we can add to our Waypoint build pipelines to also protect ourselves to so called supply chain attacks while running our jobs in Nomad. We ll discuss scanning for vulnerabilities in incoming code, packages and images and signing the content artefacts we trust before exposing them to our users.
Securing Prometheus exporters using HashiCorp VaultBram Vogelaar
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
This talk will focus on on creating a secure prometheus exporter ecosystem using HashiCorp Vault where we can we be sure that we are not leaking any business metrics from our observability stack. After which we ll investigate how to automatically rotate the certificates we created to do so.
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
This talk will focus on on setting up a CICD pipeline using Jenkins. We start by configuring Jenkins to use our Nomad platform to autoscale job runners. After which we ll look at using the newly released nomad-pack tool to convert, deploy and test and existing nomad job.
A gentle introduction to Observability and how to setup a highly available monitoring platform across multiple datacenters.
During this talk we will investigate how we can setup and monitor an monitoring setup across 2 DCs using Prometheus, Loki, Tempo, Alertmanager and Grafana. monitoring some services with some lessons learned along the way.
Running trusted payloads with Nomad and WaypointBram Vogelaar
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages.
With the the introduction of CI/CD best practices into our day to day workflows we protect ourselves for introducing "bad" code into production and exposing flaws to our (end-)users. But what about influences from bad actors in- and out-side our projects. This talk will focuss on the addtional steps we can add to our Waypoint build pipelines to also protect ourselves to so called supply chain attacks while running our jobs in Nomad. We ll discuss scanning for vulnerabilities in incoming code, packages and images and signing the content artifacts we trust before exposing them to our users.
We all love infrastructure as code, we automate everything ™ but how many
of us can really say we could destroy and recreate our core infrastructure
without human intervention. Can you be sure there isnt a DNS problem or
that all the things ™ are done in the right order This talk walks the
audience through a green fields exercise that sets up service discovery
using Consul, infrastructure as code using terraform, using images build
with packer and configured using puppet.
A gentle introduction to Observability and how to setup a highly available monitoring platform accros multiple datacenters.
During this talk we will investigate how we can setup and monitor an monitoring setup accross 2 DCs using Prometheus, Loki, Tempo, Alertmanager and Grafana. monitoring some services with some lessons learned along the way.
"Roles and Profiles" is now the ubiquitous design pattern to create your puppet code tree. In this talk we will discuss writing reusable and maintainable profiles. We ll start by introducing creating module structures and will move on to type hinting and setting appropriate defaults. Finally we ll discuss the importance and the enforcing of code style conventions that allows multiple teams or projects to inner-source profiless
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
We all love infrastructure as code, we automate everything ™. However making sure all of our infrastructure assets are monitored effectively can be slow and resource intensive multi stage process. During this talk we will investigate how we can setup nomad cluster that can automatically scale our infrastructure both horizontally as vertically to be able to cope with increased demand by users/
This talk will focus on making sure we on configuring Nomad and its new autoscaler component to be able to make data driven decisions about scaling nomad jobs in or out to fit current customers usage.
Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
We all love infrastructure as code, we automate everything ™. However making sure all of our infrastructure assets are monitored effectively can be slow and resource intensive multi stage process. During this talk we will investigate how we can setup and observe a service mesh platform using HashiCorp's Consul Connect by recording its metrics. logs and traces.
This talk will focus on configuring and analysing the metrics, logs and traces Consul Connect produces using Prometheus, Loki, Tempo and Grafana.
Testing your infrastructure with litmusBram Vogelaar
We have been able to test our puppet modules using rspec-puppet and
serverspec for a while now and the quality of our code is improving because
of it. This talk will introduce the new kid on the block litmus. This talk will show you how
to use litmus to test puppet modules and how to convert your existing modules to make use of litmus.
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.
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
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.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
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.
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
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
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.
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.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Essentials of Automations: Optimizing FME Workflows with Parameters
Devops its not about the tooling
1. Devops, it's not about
tooling
But tooling is so much fun !
05/12/2019
Bram Vogelaar
@attachmentgenie
2. ~$ whoami
●
I used to be a Molecular Biologist,I used to be a Molecular Biologist,
●
Then became a Dev,Then became a Dev,
●
Now an Ops.Now an Ops.
●
Open Source Consultant @inuits.euOpen Source Consultant @inuits.eu
3. What's this Devops thing really about ?What's this Devops thing really about ?
4. World , 200X-2009World , 200X-2009
Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzPatrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz
Humble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, andHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, and
lots of others ..lots of others ..
Gent , October 2009Gent , October 2009
Mountain View , June 2010Mountain View , June 2010
Hamburg , October 2010Hamburg , October 2010
Boston, March 2011Boston, March 2011
Mountain View, June 2011Mountain View, June 2011
........
6. ● Adopt the new philosophy. We are in a new economic age. Western managementAdopt the new philosophy. We are in a new economic age. Western management
must awaken to the challenge, must learn their responsibilities, and take onmust awaken to the challenge, must learn their responsibilities, and take on
leadership for change.leadership for change.
● Cease dependence on inspection to achieve quality. Eliminate the need for massiveCease dependence on inspection to achieve quality. Eliminate the need for massive
inspection by building quality into the product in the first place.inspection by building quality into the product in the first place.
● Improve constantly and forever the system of production and service, to improveImprove constantly and forever the system of production and service, to improve
quality and productivity, and thus constantly decrease costs.quality and productivity, and thus constantly decrease costs.
● Institute training on the job.Institute training on the job.
● Institute leadership The aim of supervision should be to help people and machinesInstitute leadership The aim of supervision should be to help people and machines
and gadgets do a better job.and gadgets do a better job.
● Drive out fear, so that everyone may work effectively for the company.Drive out fear, so that everyone may work effectively for the company.
● Break down barriers between departments. People in research, design, sales, andBreak down barriers between departments. People in research, design, sales, and
production must work as a team, in order to foresee problems of production andproduction must work as a team, in order to foresee problems of production and
usage that may be encountered with the product or service.usage that may be encountered with the product or service.
● Eliminate slogans, exhortations, and targets for the work force asking for zero defectsEliminate slogans, exhortations, and targets for the work force asking for zero defects
and new levels of productivity. Such exhortations only create adversarialand new levels of productivity. Such exhortations only create adversarial
relationships, as the bulk of the causes of low quality and low productivity belong torelationships, as the bulk of the causes of low quality and low productivity belong to
the system and thus lie beyond the power of the work force.the system and thus lie beyond the power of the work force.
•Eliminate management by objective. Eliminate management by numbers and numericalEliminate management by objective. Eliminate management by numbers and numerical
goals. Instead substitute with leadership.goals. Instead substitute with leadership.
•Remove barriers that rob the hourly worker of his right to pride of workmanship. TheRemove barriers that rob the hourly worker of his right to pride of workmanship. The
responsibility of supervisors must be changed from sheer numbers to quality.responsibility of supervisors must be changed from sheer numbers to quality.
•Remove barriers that rob people in management and in engineering of their right toRemove barriers that rob people in management and in engineering of their right to
pride of workmanship.pride of workmanship.
● Institute a vigorous program of education and self-improvement.Institute a vigorous program of education and self-improvement.
● Put everybody in the company to work to accomplish the transformation. ThePut everybody in the company to work to accomplish the transformation. The
transformation is everybody's job.transformation is everybody's job.
9. ““DevOps is a cultural andDevOps is a cultural and
professional movement”professional movement”
Adam JacobAdam Jacob
10. A global movement to improve the quality ofA global movement to improve the quality of
software delivery leveraging Open Sourcesoftware delivery leveraging Open Source
experience, started in Gent in 2009experience, started in Gent in 2009
11.
12. Whats in it for you ?Whats in it for you ?
● Faster time to marketFaster time to market
•
Features go live in hours vs yearsFeatures go live in hours vs years
● In a more safe (Secure)In a more safe (Secure)
● Reliable fashionReliable fashion
•
Fully automatedFully automated
● More happyMore happy {customers,developers,managers,investors}{customers,developers,managers,investors}
14. The Old DaysThe Old Days
● ““Put this Code Live, here's a tarball” NOW!Put this Code Live, here's a tarball” NOW!
● What dependencies ?What dependencies ?
● No machines available ?No machines available ?
● What database ?What database ?
● Security ?Security ?
● High Availability ?High Availability ?
● Scalability ?Scalability ?
● My computer can't install this ?My computer can't install this ?
19. Analyze ThisAnalyze This
● What are devs nagging aboutWhat are devs nagging about
•
Slow builds ?Slow builds ?
• No enviroments ?No enviroments ?
● What are ops nagging aboutWhat are ops nagging about
•
Bad artefacts ?Bad artefacts ?
•
No logs ?No logs ?
● What is mgmt nagging aboutWhat is mgmt nagging about
•
Quality / Feedback ?Quality / Feedback ?
20. Are you speaking the sameAre you speaking the same
language ?language ?
● Configuration management vs configurationConfiguration management vs configuration
managementmanagement
● What is Operations ?What is Operations ?
● What is #devops ?What is #devops ?
21. Crossfunctional TeamCrossfunctional Team
● Build a project team with skills from all overBuild a project team with skills from all over
•
DevelopmentDevelopment
•
Continuous IntegrationContinuous Integration
•
TestingTesting
•
Infrastructure (HA/ Scale/ Performance)Infrastructure (HA/ Scale/ Performance)
•
DeploymentDeployment
•
MeasurementMeasurement
● Seat them together !Seat them together !
● Goal = Help the businessGoal = Help the business
22. Shared BacklogShared Backlog
● CHALLENGE : Getting Non FunctionalCHALLENGE : Getting Non Functional
Requirements in the development backlogRequirements in the development backlog
•
On team levelOn team level
•
On management levelOn management level
•
On business user levelOn business user level
● Put the Product Owner on CallPut the Product Owner on Call
23. There's a tool for thatThere's a tool for that
● RedmineRedmine
● GitlabGitlab
● TracTrac
● Github.comGithub.com
● PhabricatorPhabricator
● TaigaTaiga
25. There's a tool for thatThere's a tool for that
● Good old Irc,Good old Irc,
● Xmpp (ejabberd,openfire, …),Xmpp (ejabberd,openfire, …),
● JitsiJitsi
● Mattermost , Rocketchat, Telegram, SlackMattermost , Rocketchat, Telegram, Slack
● ……..
26. Build TrustBuild Trust
● ExperimentExperiment
•
DevDev
• TestTest
● ProdProd
● Automate all theAutomate all the
thingsthings
● Measure successMeasure success
● Measure FailureMeasure Failure
27. With great power ...With great power ...
Your code will go to production..Your code will go to production..
You will be able to fix it ..You will be able to fix it ..
You will have access to the logsYou will have access to the logs
Access to the metrics...Access to the metrics...
28.
29. While we talk about animals..While we talk about animals..
32. BondBond
● Internal DevopsdaysInternal Devopsdays
● Internal Open Source DaysInternal Open Source Days
● Hack DaysHack Days
● Teach a collegue daysTeach a collegue days
● Ramdon Lunch meetupsRamdon Lunch meetups
● Eat CakeEat Cake
● Both inside and outside the officeBoth inside and outside the office
36. Automate all the thingsAutomate all the things
● BuildBuild
•
reproducable builds are undiscussablereproducable builds are undiscussable
● TestTest
•
testing reduces risktesting reduces risk
•
automate deployments of your test infraautomate deployments of your test infra
● DeployDeploy
•
Infrastructure as CodeInfrastructure as Code
•
100% automation100% automation
•
Can you rebuild your infrastructure ?Can you rebuild your infrastructure ?
37. NirvanaNirvana
An “ecosystem” that supports continuous delivery, fromAn “ecosystem” that supports continuous delivery, from
infrastructure, data and configuration management toinfrastructure, data and configuration management to
business.business.
Through automation of the build, deployment, and testingThrough automation of the build, deployment, and testing
process, and improved collaboration between developers,process, and improved collaboration between developers,
testers, and operations, delivery teams can get changestesters, and operations, delivery teams can get changes
released in a matter of hours — sometimes even minutes–noreleased in a matter of hours — sometimes even minutes–no
matter what the size of a project or the complexity of its codematter what the size of a project or the complexity of its code
base.base.
Continuous Delivery , Jez HumbleContinuous Delivery , Jez Humble
41. Continuous IntegrationContinuous Integration
● BuildsBuilds
● Nightly BuildsNightly Builds
● Builds with testsBuilds with tests
● Nightly Builds with testsNightly Builds with tests
● Frequent integrationFrequent integration
● Continuous IntegrationContinuous Integration
42. CI ToolsCI Tools
● HudsonHudson
● JenkinsJenkins
A zillion pluginsA zillion plugins
● Go (Cruise Control)Go (Cruise Control)
● TravisTravis
● GitlabCIGitlabCI
● Also test your (Puppet/Chef/CFengine)Also test your (Puppet/Chef/CFengine)
48. Can you Automate yourCan you Automate your
Pipeline Creation ?Pipeline Creation ?
● Puppetizing PipelinesPuppetizing Pipelines
● Templating PipelinesTemplating Pipelines
● Workflow PluginWorkflow Plugin
● JJBJJB
● ……
49. Can you Automate yourCan you Automate your
Pipeline Creation ?Pipeline Creation ?
● Pipeline as CodePipeline as Code
● Jenkins Job DSLJenkins Job DSL
● Pipeline PluginPipeline Plugin
52. How many times a day ?How many times a day ?
● 10 @ Flickr10 @ Flickr
● Deployments used to be painDeployments used to be pain
● Nobody dared to deploy a siteNobody dared to deploy a site
● Practice makes perfectPractice makes perfect
● Knowing you can vs constantly doing itKnowing you can vs constantly doing it
53. " Our job as engineers (and ops, dev-ops, QA," Our job as engineers (and ops, dev-ops, QA,
support, everyone in the company actually) is tosupport, everyone in the company actually) is to
enable the business goals. We strongly feel thatenable the business goals. We strongly feel that
in order to do that you must havein order to do that you must have the ability tothe ability to
deploy code quickly and safelydeploy code quickly and safely. Even if the. Even if the
business goals are to deploy strongly QA’d codebusiness goals are to deploy strongly QA’d code
once a month at 3am (it’s not for us, we push allonce a month at 3am (it’s not for us, we push all
the time), having a reliable and easythe time), having a reliable and easy
deployment should bedeployment should be non-negotiablenon-negotiable."."
Etsy Blog upon releasing DeployinatorEtsy Blog upon releasing Deployinator
http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/
54. Infrastructure as CodeInfrastructure as Code
● Treat configuration automation as codeTreat configuration automation as code
● Development best practicesDevelopment best practices
•
Model your infrastructureModel your infrastructure
•
Version your cookbooks / manifestsVersion your cookbooks / manifests
•
Test your cookbooks/ manifestsTest your cookbooks/ manifests
•
Dev/ test /uat / prod for your infraDev/ test /uat / prod for your infra
● Model your infrastructureModel your infrastructure
● A working service = automated ( Application Code +A working service = automated ( Application Code +
Infrastructure Code + Security + Monitoring )Infrastructure Code + Security + Monitoring )
● IAC -ne scriptingIAC -ne scripting
56. Pick your poisonPick your poison
● CfEngineCfEngine
● PuppetPuppet
● ChefChef
● AnsibleAnsible
● SaltSalt
•
Or combine themOr combine them
57. Infra Requirements:Infra Requirements:
● GitGit
● CI ToolCI Tool
● Test FrameworksTest Frameworks
● IAC FrameworkIAC Framework
•
Includes ReportingIncludes Reporting
•
Also requires the aboveAlso requires the above
58. Culture Hack:Culture Hack:
Set up CI / CD for your infrastructure first, IfSet up CI / CD for your infrastructure first, If
the people running your infra don't know howthe people running your infra don't know how
CI/CD works , how do you expect them toCI/CD works , how do you expect them to
support / teach your application teams ?support / teach your application teams ?
You also get them to learn about the toolingYou also get them to learn about the tooling
they will need to support and they will sharethey will need to support and they will share
the pain and the joy of the applicationthe pain and the joy of the application
developersdevelopers
59. Spinning up stacksSpinning up stacks
● ForemanForeman
● Terraform ..Terraform ..
● Pitfall :Pitfall :
•
Require a CI Tool to deployRequire a CI Tool to deploy
60. Why ops like to packageWhy ops like to package
● Packages give you featuresPackages give you features
•Consistency, security, dependenciesConsistency, security, dependencies
● Uniquely identify where files come fromUniquely identify where files come from
•Package or cfg-mgmtPackage or cfg-mgmt
● Source repo not always availableSource repo not always available
•Firewall / Cloud etc ..Firewall / Cloud etc ..
● Weird deployment locations , no easy accessWeird deployment locations , no easy access
● Little overhead when you automateLittle overhead when you automate
● CONFIG does not belong in a packageCONFIG does not belong in a package
61. #devopsdays 2010 Open#devopsdays 2010 Open
Space ConclusionsSpace Conclusions
● Always package software YOU deployAlways package software YOU deploy
•
Exceptions: code that changes faster thanExceptions: code that changes faster than
you can package it. (Very rare)you can package it. (Very rare)
● Do NOT package Config FILES ,Do NOT package Config FILES ,
•
Use a cfgmgmt tool for thisUse a cfgmgmt tool for this
● Languages are still reinventing the wheel :(Languages are still reinventing the wheel :(
70. The New DaysThe New Days
● ““Put this Code Live, here's Docker Container”Put this Code Live, here's Docker Container”
NOW!NOW!
● No machines available ?No machines available ?
● What database ?What database ?
● Security ? What distro is this even ?Security ? What distro is this even ?
● High Availability ?High Availability ?
● Scalability ?Scalability ?
● How do we monitor his ?How do we monitor his ?
● How did you build this ?How did you build this ?
71. If all you know is docker, every whale looks like aIf all you know is docker, every whale looks like a
private cloudprivate cloud
Image Build by devs,Image Build by devs,
maintained by nobodymaintained by nobody
72. Closing the gaps between dev and opsClosing the gaps between dev and ops
AgainAgain
● Who build this ?Who build this ?
● What about SecurityWhat about Security
● How do you even build a containerHow do you even build a container
● How do you build the hosts that run theHow do you build the hosts that run the
containers ?containers ?
● Infrastructure as code ++Infrastructure as code ++
74. Monitoring is usually anMonitoring is usually an
aftertoughtaftertought
ENOBUDGET, ENOTIMEENOBUDGET, ENOTIME
75. An 2008 OLS PaperAn 2008 OLS Paper
● We have bloated Java toolsWe have bloated Java tools
● Some open Core stuffSome open Core stuff
● DYI folks want traditional NagiosDYI folks want traditional Nagios
● DBA RequiredDBA Required
76. #monitoringsucks#monitoringsucks
● John Vincent (@lusis), june 2011John Vincent (@lusis), june 2011
● A sub #devops movementA sub #devops movement
● https://github.com/monitoringsucks/https://github.com/monitoringsucks/
77. Why #monitoringsucksWhy #monitoringsucks
● Manual config (gui)Manual config (gui)
● Not in sync with realityNot in sync with reality
● Hosts onlyHosts only
● Services sometimesServices sometimes
● Aplication neverAplication never
● Chaos or out of sync with realityChaos or out of sync with reality
● Alert FatigueAlert Fatigue
78. What we wantWhat we want
● Small , well suited componentsSmall , well suited components
•
CollectCollect
•
Transport / MangleTransport / Mangle
•
StoreStore
•
AnalyseAnalyse
•
Act / AlertAct / Alert
•
VisualizeVisualize
79. #monitoringlove#monitoringlove
•
•
Ulf Mansson #devopsdays Rome 2011Ulf Mansson #devopsdays Rome 2011
•
A new era of toolingA new era of tooling
• #monitoringlove hacksessions @inuits#monitoringlove hacksessions @inuits
•
#monitorama#monitorama
83. Automation gives , automated maintainedAutomation gives , automated maintained
monitoring of the services we define.monitoring of the services we define.
88. GraphiteGraphite
● Graphing at ScaleGraphing at Scale
● Graphing at EaseGraphing at Ease
● Any metric is a graphAny metric is a graph
● echo "somestring $somevalue $timestamp" |echo "somestring $somevalue $timestamp" |
nc <%= graphitehost %> 2003nc <%= graphitehost %> 2003
97. Logs and MetricsLogs and Metrics
● Graylog2Graylog2
● ELSA (Enterprise Log Search and Archive)ELSA (Enterprise Log Search and Archive)
● ELK StackELK Stack
98. ● Collect from anywhereCollect from anywhere
● FilterFilter
● Send anywhereSend anywhere
● QueingQueing
99.
100. Self Service MetricsSelf Service Metrics
● Being able to add new metricsBeing able to add new metrics
● Build your own dashboardsBuild your own dashboards
● Look at metrics / logs on all platformsLook at metrics / logs on all platforms
● Learn from the LogfilesLearn from the Logfiles
● Learn from the platformLearn from the platform
103. Visualize Business MetricsVisualize Business Metrics
● $revenue$revenue
● #sales#sales
● signupssignups
● conversionsconversions
● Api callsApi calls
● Application useApplication use
104. SharingSharing
● Open SpaceOpen Space
● Open SourceOpen Source
● GithubGithub
● Talk about ExperiencesTalk about Experiences
● Publish the codePublish the code