This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-12
Channels
- # ask-the-speaker-track-1 (136)
- # ask-the-speaker-track-2 (192)
- # ask-the-speaker-track-3 (82)
- # ask-the-speaker-track-4 (89)
- # bof-arch-engineering-ops (1)
- # bof-leadership-culture-learning (2)
- # bof-sec-audit-compliance-grc (3)
- # demos (1)
- # discussion-main (675)
- # discussion-more (9)
- # games (4)
- # games-self-tracker (1)
- # gather (1)
- # help (4)
- # hiring (5)
- # networking (2)
- # summit-info (41)
- # xpo-bmc-ami-devops (1)
- # xpo-cloudbees (4)
- # xpo-github-for-enterprises (1)
- # xpo-gitlab-the-one-devops-platform (7)
- # xpo-itrevolution (3)
- # xpo-launchdarkly (3)
- # xpo-lightstep-observability-incidentresponse (1)
- # xpo-linearb-automate-dev-team-improvement (4)
- # xpo-planview-tasktop (2)
- # xpo-snyk (3)
- # xpo-sonatype (1)
- # xpo-split (1)
- # xpo-synopsys-sig (3)
- # xpo-tricentis-continuous-testing (1)
Reminder: Get yourself in front of your browser and into #ask-the-speaker-plenary for the opening remarks. We’re kicking off the final day of the DevOps Enterprise Summit in 15 minutes at 10am BST! https://devopsenterprise.slack.com/files/UATE4LJ94/F01D34MC2KS/image.png
Reminder: Remember all those talks you attended the first two days of the Summit? Please submit your feedback for those! It’s so valuable for us and the speakers. And after all, feedback is a gift and sharing is caring! Enter your feedback for those talks here: https://members.itrevolution.com/live/schedule https://devopsenterprise.slack.com/files/UATE4LJ94/F03E48CJRF1/image.png
Reminder: The final day is starting now – opening remarks and then plenary talks! Join the conversation in #ask-the-speaker-plenary.
Reminder: The breakout sessions are starting in 5 minutes. Get in front of your browser and start navigating your way to whichever session you’re attending. https://devopsenterprise.slack.com/files/UATE4LJ94/F01D34MC2KS/image.png
🔆 Here to present, DevOps For 24 x 7 SaaS and Disaster Recovery, Know What It Takes Before You Leap Into It, is @amitpras, Software Architect, IBM India and @ssriva, Distinguished Engineer and Master Inventor, IBM 🔆
benefit of recorded session. You can be late by couple of secs for the session 🙂 Here now.
🌟 Let's welcome @stephan.stapel, Head of Customer Solutions, Hermes Germany GmbH, here to present, Nobody is Left Behind 🌟
Wouldn't backing up the ETCD database provide you the state of the cluster? What other components did you backup using Velero? What are the benefits of backing up those ? Does it backup the application data as well?
Hello @habibrahman.a when we use kubernetes as service we won't have access to etcd. and Yes we are backing application data too and that's where we are using volume snapshot. If application data is part of kube PVC/PV
We have GitOps implemented and all the components (including the namespaces required) are defined in the manifest file. So backing up the etcd db was sufficient for us. Obviously application data was backed up by the application teams. Would like to understand the capability of Velero and benefits it can bring
As I mentioned if you have access to ETCD you will end up backing up everything.
since you already have GitOps implemented, isn't in that case you don't need to back up entire ETCD but rather only transactiona kube objects created while application was running.
Velero help us back up only subset of kube objects based on labels and make sure to clean those up and ready to apply.
• 2nd benefits you get is to take backup of volumes either via restic or by snapshot (if storage class supports that)
Hi Stephan! Nice to see you here! We also struggle with the decision of who to help first, the ones that know they need help and are begging for it, or the ones that have no idea (yet) that they need help at all…
That's a good question and probably there is no right answer. It might also be worthwhile to consider the impact of the particular team. If there are many dependencies to others, it might be good to start there because the postive impact might be higher
@stephan.stapel: Shouldn’t pattern #3 used carefully only? Others write ‘your’ software and you need to maintain it later? And I guess it requires a lot of trust between team.
That is definitely true. We are also very cautious with this pattern. What surprises me as a leader of those teams is that this works very smoothly mosts of the time. Both teams agree on a way of working. Imho, pull requests, are a great technical detail to foster a appreciating collaboration/ culture.
This is excellent advice for organisations that have to run both a monolith and a number of modern micro-services.
Very interesting presentation! Liked it very much - addressing an important transformation topic: “don’t let the ‘legacy teams’ behind!
Reminder: The breakout sessions are starting again in 5 minutes. Get in front of your browser and start navigating your way to whichever session you’re attending. https://devopsenterprise.slack.com/files/UATE4LJ94/F01D34MC2KS/image.png
🌟 Let's welcome @dvidyara, Site Reliability Engineer at Cisco, here to present ISTIO with BookInfo Application 🌟
⚡ Please welcome, @rob947, Software Consultant and Author, here to present: If Development is a Game, How Do I Win? ⚡
winner of the best talk title award: If Development is a Game, How Do I Win?
this is a talk I’ve given a few times to straight-up devs - but I think it might be even more relevant to DevOps..?
Hi, @rob947 — your submission definitely caught our attention! We're excited that you could present!!!
(The notion of devs talking more routinely talking about all sorts of risk is a super concept!)
Totally, there's more risks than just functional or operational risk! :)
I LOVE TV TROPES! (I used it extensively to help write Unicorn Project)
a big obstacle i see in many organizations is an “unhealthy” relationship with risk.
My fave way to describe Unicorn Project to myself during writing process: A Team, Redshirts, Hogans Heroes, and the movie Brazil.
I don’t get to this in the presentation today, but Dependency Risk is one risk that keeps growing, due to things like the explosion of open-source libraries, and things like Log4Shell
@jeff.gallimore What I love about this is that giving things names is great — like naming cognitive biases help us be aware of them, and overcoming/mitigating them.
There was great conversation yesterday of someone who added multiple versions of multiple XML parsers to program, and never removed them. Because, why not? 😆
What case studies would you put forth as the best example of people using your philosophies/tools successfully? @rob947
As someone who trained as internal auditor, I totally love the idea of someone who thinks thru important lenses of risk, on domains such as financial reporting, compliance, operational. So I love the thesis: just wondering who's gravitated towards this, how they've used it, etc.
well, I don’t know if I can lay claim to this being my philosophy. This is applying risk management to software development. But, to answer your question - a lot of the development teams I’ve been on have gravitated to something like this, talking about risks rather than story points, say.
More generally (and famously) I would argue that SpaceX is building their rockets with risk management top-of-mind: they’re happy to lose the odd rocket, they’ve managed the risks on that. Each launch is a bet, where they’ve minimised the downside and hoped to learn something
yep. made out of wood 😀. not anymore, they’re all computerized so don’t try this now
I love the story that gaming machines in casino odds are at aggregate level, not machine level. (Best odds can be concentrated on a game in corner, as long as aggregate is "fair")
Meta-game: goal is to win! (Vs. completing features, not getting hacked, not having users think a 5 yo wrote it (haha!!))
(Auth0 outage story: dependency risk... albeit, a very good choice for most!)
"You want to place bets where there's maximal payoff" "Use oauth2 will increase dependency risk, but save person-months of effort"
Bets -> underscores need for options: w/no options, you can't bet. Sometimes best thing you can do it buy options, to buy the right to make decisions/bets again.
(Dr. @steve773 and I are presenting on this at end of the day!)
And in addition to manage down risks, make better bets to win (and hedge risks that you take on when you do the work)
@rob947 is there any tooling that facilitates risk assignment and betting?
When gambling to win, it helps to know the rules of the game, the odds, and the risks they need to hedge against.
Loved the talk thanks @rob947! Have been trying to argue along these lines in work It's more obvious for data scientists - most ideas they start exploring won't make it to production, so every day they gamble with their own time, losing most bets but winning in the aggregate -> apply similar thinking to other people's time & $ spend in the firm
Reminder: The final plenary sessions are starting in 5 minutes. Start making your way back to your browser and join us in #ask-the-speaker-plenary to interact live with the speakers and other attendees. https://devopsenterprise.slack.com/files/UATE4LJ94/F01D34MC2KS/image.png
Reminder: Please submit your feedback for the talks you attended. It’s so valuable for us and the speakers. And after all, feedback is a gift and sharing is caring! Enter your feedback for those talks here: https://members.itrevolution.com/live/schedule https://devopsenterprise.slack.com/files/UATE4LJ94/F03E48CJRF1/image.png