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

Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

github.com

Post reply on HN
Print view View original

21–28 of 28 posts

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#21

Post by import_awesome »

jarpineh wrote: post #20
import_awesome wrote: post #16

Earlier quoted context omitted.

Try it on Binder here: https://mybinder.org/v2/gh/ansible/ansible-jupyter-kernel/ma...

Hi, and thank you. It works well. Example play books already contain the basics I'd need for my playbooks. Could you perhaps elaborate how the kernel directs Ansible? Also, is there any difference between local and remote Ansible runs?

Ansible Kernel calls ansible-playbook on a specially constructed playbook. Ansible Kernel constructs a playbook with a two tasks in it: 1. wait for the kernel and 2. include tasks from a file that does not exist yet. When you enter a #task cell we write that included file and then tell the wait task to proceed. The included file contains the #task cell contents, a wait task, and another include task. This continues until you stop the kernel, the playbook dies on an error, or you enter a #play cell. On a #play cell ansible kernel throws away the old playbook and make a new one with the new arguments. The exported playbook just contains the content on the page (without the wait/include tasks) and should work with ansible-playbook normally.

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#22

Post by 1996 »

throwaway5752 wrote: post #14
1996 wrote: post #11

Earlier quoted context omitted.

I have more of an opinion there: Maybe programming should be more like data science. Prototypes are thrown away, but must exist at one point. They should be encouraged - like versionning, it is part of a core of good practices that admit few exceptions External dependencies, state etc will all be handled, once excution is ironed out

Sure, but that's not super different that series of commits along a feature branch. I think they accomplish the same goal. But am not dismissing notebooks as a way of doing that. I'm more familiar with ipython than jupyter, but particularly for more algorithmically complex programming tasks I think notebooks are a good tool. I disagree with you only that this might be a good way of prototyping for something like ansi…

I agree with you, ansible may not be the best showcase of the notebook (much is external) but I think it still remains practical for prototyping: I consider the notebook as a giant notepad, that shows you at the same time your code and the results of the code - in multiple versions, as many as tabs. Better than tabs, or terminals

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#23

Post by tejtm »

massaman_yams wrote: post #18
tejtm wrote: post #17

Until there is a meaningful `git diff` for jupyter notebooks I can't see them being a step in the right direction for anything but transient experiments (and of course what Jypyter is great at; communication, documentation, low barriers etc.)

This is effectively a solved problem, but it does require some tooling. Pre-commit hooks can strip things like execution count and/or outputs from the notebook: https://gist.github.com/minrk/6176788

Thanks will give this a try

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#24

Post by massaman_yams »

tejtm wrote: post #23
massaman_yams wrote: post #18

Earlier quoted context omitted.

This is effectively a solved problem, but it does require some tooling. Pre-commit hooks can strip things like execution count and/or outputs from the notebook: https://gist.github.com/minrk/6176788

Thanks will give this a try

caveat: I haven't tested this particular one, it was just the first thing I found in a quick search.

This post has more detail on a faster approach using jq: http://timstaley.co.uk/posts/making-git-and-jupyter-notebook...

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#25

Post by makmanalp »

massaman_yams wrote: post #18
tejtm wrote: post #17

Until there is a meaningful `git diff` for jupyter notebooks I can't see them being a step in the right direction for anything but transient experiments (and of course what Jypyter is great at; communication, documentation, low barriers etc.)

This is effectively a solved problem, but it does require some tooling. Pre-commit hooks can strip things like execution count and/or outputs from the notebook: https://gist.github.com/minrk/6176788

See also: nbdime to diff / merge notebooks https://github.com/jupyter/nbdime

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#26

Post by PurpleRamen »

tejtm wrote: post #17

Until there is a meaningful `git diff` for jupyter notebooks I can't see them being a step in the right direction for anything but transient experiments (and of course what Jypyter is great at; communication, documentation, low barriers etc.)

Something I always wondered about: why are Jupyter Notebooks JSON-Files and not directories where each cell and result has a coresponding single file? Would also make managing attatchments and versionscontrol per notebook quite easy.

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#27

Post by jarpineh »

import_awesome wrote: post #21
jarpineh wrote: post #20

Earlier quoted context omitted.

Hi, and thank you. It works well. Example play books already contain the basics I'd need for my playbooks. Could you perhaps elaborate how the kernel directs Ansible? Also, is there any difference between local and remote Ansible runs?

Ansible Kernel calls ansible-playbook on a specially constructed playbook. Ansible Kernel constructs a playbook with a two tasks in it: 1. wait for the kernel and 2. include tasks from a file that does not exist yet. When you enter a #task cell we write that included file and then tell the wait task to proceed. The included file contains the #task cell contents, a wait task, and another include task. This continues u…

This does sound like Ansible does not make it easy to control it from pure Python. It looks an ingenious way to get around it.

I came across this Python wrapper around Ansible yesterday: http://suitable.readthedocs.io/en/latest/ Official docs declare themselves deprecated...

Anyway, I'll have to start testing this soon. Thank you so much for making it!

Re: Show HN: Ansible Kernel – Run Ansible Tasks and Plays with Jupyter Notebook

#28

Post by import_awesome »

jarpineh wrote: post #27
import_awesome wrote: post #21

Earlier quoted context omitted.

Ansible Kernel calls ansible-playbook on a specially constructed playbook. Ansible Kernel constructs a playbook with a two tasks in it: 1. wait for the kernel and 2. include tasks from a file that does not exist yet. When you enter a #task cell we write that included file and then tell the wait task to proceed. The included file contains the #task cell contents, a wait task, and another include task. This continues u…

This does sound like Ansible does not make it easy to control it from pure Python. It looks an ingenious way to get around it. I came across this Python wrapper around Ansible yesterday: http://suitable.readthedocs.io/en/latest/ Official docs declare themselves deprecated... Anyway, I'll have to start testing this soon. Thank you so much for making it!

You're welcome. I hope that you find it useful.
Post reply on HN