Agile + DevOps Virtual 2020 - DevOps Practices
Wednesday, June 10
Threat Modeling Lessons Learned from Star Wars
PreviewEveryone knows you ought to perform threat modeling, but in practical reality, it turns out to be tricky. If past efforts to threat model haven't panned out, perhaps part of the problem is confusion over what works and how the various approaches conflict or align. Adam Shostack will give a basic introduction to threat modeling, taking you from uncertainty about how to do it well to understanding how to model threats effectively and avoid the traps that make it hard. Security professionals, developers, and systems managers alike will leave with threat modeling lessons from Star Wars...
DevOps Fireside Chat
You've got questions about DevOps, and we've got DJ Schleen to answer them for you. He won't really be sitting by the fire, but he will be on hand to talk about all things DevOps, mobile security, ethical hacking, and pen testing. He's also an expert in DevSecOps and development pipelines, breaking down silos in an organization, and digital transformations at some of the biggest companies out there. And he wants to talk to you about your DevSecOps hopes, dreams, fears, and nightmares. Alan Crouch will be moderating, so bring your questions and be ready for a lively, interactive discussion...
Overcoming Continuous Build and Other DevOps Anti-Patterns
Continuous build is an anti-pattern where a team will have what they call continuous integration (CI) in place, but it only builds the code—there are no unit tests or static analysis. Certainly, this is better than not building, but it leaves a lot of health-check information on the table that is considered part of CI. Without this information, you can never really gain confidence in your build. The whole goal of CI is to feel that your build is healthy, so no tests or analysis means you aren’t doing CI. Just like CI, other DevOps practices can be hard to understand, implement, and get...
Thursday, June 11
DataOps: Eliminating Data Friction in DevOps
The DevOps movement has led to the adoption of continuous integration (CI) and continuous delivery (CD) in the application delivery pipeline. The end goal of establishing a CI/CD pipeline is to achieve a continuous "flow" of releases as new features get built, integrated, tested, and deployed to production-like environments, and eventually to production. This flow depends on the continuous integration and delivery of small batches of code for database and environment changes. Data friction results from the inability to have the right data provisioned to the right environment when it is...
Changing Tires on a Moving Car: Our Journey to Zero-Downtime Deployments
Applications built over the years carry historical design assumptions, such as that a few hours of downtime for maintenance upgrades every six months is acceptable. Today, embracing continuous delivery practices means more frequent releases, which means more downtime. This is the problem Pierre Vincent faced and successfully overcame, going from monthly deployments with a couple of hours of downtime to zero-downtime deployments on demand. Pierre will show how, by mapping out a deployment process, it becomes possible to progressively reduce its impact on users. He will also give practical...
.jpg%3Fitok=lJJa-KTs&sc=dec602ae2443b1b5f89e8ef6fe3b045b)
The Road to Continuous Monitoring
DevOps culture has come a long way over the past decade. We have been able to automate almost every step of the delivery process—yet we still lack automated monitoring. The transition from the classic way of monitoring to continuous monitoring is difficult, not only because it demands strict approaches to the methodology and architecture, but mainly because our organizational culture is not ready for it. Join Pawel Piwosz as he attempts to create a common understanding of what continuous monitoring is, what foundations are needed to start building continuous monitoring, and what advantages...