Great video! One that's also very cool (and the one I'm coming from) is sshfs

Great talk on a real sore point!

Cool video. Gave me some nice ideas to make with FUSE. BTW how many babies did she kill in Gaza? How's the genocide going?

What role does incident management play in SRE?

excellent construct

Nice discussion of real life docker-networking usecase and how you solved it without inventing any new tool. ---Thank You

any chance to have an English subtitles?

The least boring, most informative SRE video I have personally seen.

well presented. good job Daniel

yes, pcapy is nice, but I order to install it, I have to use: apt install build-essential apt install python-pcapy apt install python3-dev apt install libpcap-dev pip3 install setuptools=60 pip3 install wheel pip3 install egg pip3 install pcapy (so basically setup a whole development environment) instead of tcpdump, which only requires: apt install tcpdump

pavel

In order to connect to source code repo, do you need the source code repo to be accessible via a public IP?

😂 'promo sm'

amazing backstage thanks

this is cool :D

Lie #4 (see the episodes in the talk) "We have microservices architecture". What follows is the truth: "we are trying to migrate to microservices". What is not talked about is the preceding question "do you need that" (it was talked about indirectly before the subject of microservices). I experienced this at companies where as far as I saw this architecture was not needed. A lot of time and money was lost before the preceding truth replaced the microservice belief and a monolith was bought or built. Not to forget: the desillusionment of those of the microservices belief who saw their work thrown in the recycle bin and their job lost. Or was the cooperation opportunism to begin with.

Thanks for posting it !! Very simplistic overview

Informative! Thank you!

*promo sm* 💖

מדהימה ❤️היתה הרצאה עם כל כך הרבה ערך ולמדתי ממך המון.

amazing talk @anton

One year and only one comment! This is golden stuff!

Very detailed explanation , David

👏

fun guy, one of the really informative, fun SRE presentations!

Really its well explained in a simple way. Good job!

w/a a teardown to your test? uploaded.clear()

finally a top notch SRE video :) ty!

text

Yes agree with Yishai, the major AGile metrics are good for management, but really do not look into the inside engineering team to measure the value added by the engineering team. The cycle time seems to be a very useful metric.

Great talk !

Very helpful. Thank you!

@shahar, This is amazing I'd love to see this grow. All the best

Thank you for filming and editing!

Honestly still learning how all this stuff works and how to actually get some financial freedom! ♥♥ ♥♥ 4:40

Done 😃 do done lo 👍

perfect explanation, thank you

Thanks 👍 wonderful presentation.

informative in deed

Great presentation, especially when he talked about his marriage. Haha, just kidding! Thanks, I have read the books also, highly recommended for SRE folks!

the best presentation i ever seen about the sre now i understand

Cool, I really like that this explanation is telling a story of an incoming packet from start to finish instead of the usual 'now let's discuss iptables'

I really enjoyed the conference - lots of great sessions! If you liked my one, I've got more material about "lessons from the lunar landings" in a blog series - flyingbarron.medium.com & ibm.biz/apollo-lessons

any example on apache log ?

every customer likes to think they are special cuz their mum told em, lol nice one nv tough crowd

You can see more of my lessons at ibm.biz/apollo-lessons

awesome speech !! It helps me to understand how docker network works.

Things came from RPO/RTO to say what CAP means. AP/CP is a kind of state not model, right?

6:18 - GPU vs CPU

(Predictably) I enjoyed this very much. The quote at 20:48 ("optimised for killing people and breaking things") is pure comedy gold 🤣 At 16:54 I was slightly surprised you didn't mention the technique of shared minute taking via a real-time collaborative editing platform such as etherpad or <evil>Google Docs</evil>, although knowing you, you probably already considered this and consciously decided not to. In using this for weekly team calls for the last few years, I found that this has huge value through a) increasing the chance of identifying areas of misunderstanding in real-time, b) avoiding skewed perspective in the minutes which is common when they are written by a single person, c) keeping people more engaged during the meeting, d) making it more obvious who is engaged even if they aren't talking, and e) sharing the burden of minute taking, so that there isn't a single person disadvantaged in their participation by virtue of having to furiously capture what everyone else is talking about. Expanding on a), on many occasions I've seen people interpret what they heard in a certain way, minute it, and then other people immediately spot that the minutes don't match *their* alternative interpretation of the same words, and the disconnect gets resolved within tens of seconds of it emerging. IMHO this is much better than having to resolve the disconnect hours or days later. Of course, this technique is equally valuable in face-to-face meetings, as we both well know from countless OpenStack events :-) Finally, when I imagine pinching any kind of water pipe, I would expect it to *increase* the pressure of the water coming out (recalling p = F/A from my GCSE physics), but I suspect that's not quite what you were going for with this metaphor ;-)