Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

github.com

Post reply on HN
Print view View original

11–20 of 37 posts

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#11

Post by TheBengaluruGuy »

anonme4ever wrote: post #9
TheBengaluruGuy wrote: post #6

Earlier quoted context omitted.

This is quite an interesting evaluation, thanks for sharing. We are piloting with a large enterprise (100+ SREs). Before us, they started implementing Jupyter Notebooks in a similar direction. Writing one playbook in Jupyter is easy but creating a framework to enable their 100+ product teams to self-serve and create playbooks has been so intensive for them, they even started working on their internal SDK for it. It w…

You should check out Nurtch[0] with Rubix integration[1]. Gitlab have some docs on how to use it[2]. Your project seems nice! I'll give it a try ;-) Only thing, the Jupiter-like part is not clear enough. 0: https://www.nurtch.com/ 1: https://docs.nurtch.com/en/latest/rubix-library/index.html 2: https://docs.gitlab.com/ee/user/project/clusters/runbooks/

Thanks for sharing about Nurtch & Rubix, I have come across it before in the Gitlab Runbooks.

The Jupyter part is reference to the cellular execution of tasks as per the preference of the users + being able to get execution / code next to each other. Both have been design principles for us from the get-go.

Just like how variables can be reused across cells in Jupyter, we plan to shortly introduce rules / conditionals creating interdependencies between variables in the PlayBooks steps.

Edit: Adding the a sample Playbook link here for reference -- https://sandbox.drdroid.io/playbooks/14

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#12

Post by lcfcjs6 »

This is awesome, i've seen so many static runbooks (like confluence) and SREs will scan it once, not find what they need and then go wake up a senior dev. Pre-programmed scripts could go a long way in giving the SRE the ability to go that extra step, which could be vital to solving the problem faster.

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#14

Post by debarshri »

Reminds me of Rundeck and the time we were trying to build something similar. There are more modern take like fiberplane and moment.dev. Not sure about their adoption.

At one point, we were building something like this on top of kubernetes. I think tech is the easy part here. Getting people to leave their existing workflows and use your product is hard.

Secondly, difficult part of our journey was integrations. Until you have integrated all the tools an org uses, product is useless.

Thirdly, it is great that there are building blocks, but users understand use cases. So, expecting end users to build playbooks themselves is tricky. There has to be an intrinsic motivation within the platform.

Fourthly, it is super competitive space if you see it from an internal tool building perspective. There are lot of internal tool builders like appsmith, retool, tooljet, django admin you are competing with where you could run bash scripts, sql queries etc.

Best of luck, with you journey.

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#16

Post by samuelstros »

delano wrote: post #15

If it works like Jupyter, as a file that can be version controlled, and like Deepnote where multiple people can be viewing/working on it at the same time, my mind would be blown.

here, be blown away https://github.com/opral/monorepo/tree/main/lix

solving version control for files like jupyter notebooks brings collaboration to those files without the need to give up files in favor of the cloud. playbooks could leverage lix in 1-2 years to build a file-based version of their tool

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#17

Post by mcintyre1994 »

delano wrote: post #15

If it works like Jupyter, as a file that can be version controlled, and like Deepnote where multiple people can be viewing/working on it at the same time, my mind would be blown.

You might also like Elixir Livebook! :) https://livebook.dev/

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#19

Post by TheBengaluruGuy »

delano wrote: post #15

If it works like Jupyter, as a file that can be version controlled, and like Deepnote where multiple people can be viewing/working on it at the same time, my mind would be blown.

Thanks for your feedback.

> as a file that can be version controlled

PlayBooks are created using a UI and all state changes are tracked but we currently don't support moving back to a previous version of the PlayBook.

> where multiple people can be viewing/working on it at the same time

This is currently picked wherein we will be creating sessions for each time PlayBooks are run and sessions will have the data persistent in each cell for everyone with the link to see.

Re: Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents

#20

Post by TheBengaluruGuy »

samuelstros wrote: post #16
delano wrote: post #15

If it works like Jupyter, as a file that can be version controlled, and like Deepnote where multiple people can be viewing/working on it at the same time, my mind would be blown.

here, be blown away https://github.com/opral/monorepo/tree/main/lix solving version control for files like jupyter notebooks brings collaboration to those files without the need to give up files in favor of the cloud. playbooks could leverage lix in 1-2 years to build a file-based version of their tool

this is quite interesting. I'll surely keep it in mind while we build out deeper collaborative features.!
Post reply on HN