[msherman64]

Adds Container.console(), which opens an interactive shell in a CHI@Edge container inside a notebook cell. Until now the only way to get a shell was to run openstack appcontainer exec --interactive in a separate terminal.

container.get_container("my-container").console()   # or .console("bash")

The kernel holds the exec session, through python-zunclient's execute_interactive(), recv(), send() and resize(). The cell shows the session with xterm.js, as an anywidget. It doesn't use the openstack CLI or Jupyter's terminals, so it works in JupyterLab and in VS Code notebooks. When the command exits, the cell shows its exit status.

Needs a python-zunclient with those methods. They're in mike-personal-org/python-zunclient#20 and aren't in ChameleonCloud/python-zunclient yet. It also needs anywidget in the Jupyter image.

Note: the shell has a tty, so stderr arrives mixed into stdout, as in a terminal.

Not handled yet, most harmful first:

• In a VS Code notebook, an early prototype received each key five times, so Enter ran a command five times. The cause isn't known yet.
• You can't type in the console while another cell is running. The kernel handles keys only when it's idle.
• With an older python-zunclient, console() fails with an AttributeError, not a clear message.
• xterm.js loads from cdn.jsdelivr.net, so the console doesn't work where that's blocked.
• Closing the browser tab leaves the shell running until the kernel stops.
• Nothing keeps a quiet session alive. HAProxy may cut it after an hour (not checked).

🤖 Generated with Claude Code