Here’s a discussion I was having with a coworker recently through email that I thought it’d be more appropriate if we have it here, so we can all chime in.
The goal would be to jump from Foreman to Cockpit on a machine
“seamlessly”, without having to log in again.
There is https://github.com/theforeman/foreman_cockpit already. Would
it make sense to improve this when the ultimate goal is to get Cockpit
integrated with Foreman?
That makes sense I would say. The gif in the README is quite outdated,
but I think in general it’d be tremendously nice to go to a machine and
be able to click on ‘Cockpit’ and automatically get to the UI.
Cool, I’ll look more closely at foreman_cockpit then and trust that we
can somehow reuse that.
Would you be willing with helping me to set up a devel environment for
Foreman and/or Satellite? That might save me a week or two of my
It should be a matter of going to https://github.com/theforeman/forklift
then ‘vagrant up centos7-devel’ - you definitely want Foreman and Katello
and Pulp to ensure maximum compatibility.
- Keep in mind Foreman does NOT necessarily have access to all machines
directly. Some of the machines can only be accessed through capsules
But Foreman still can execute things remotely, right? We need to run
cockpit-bridge on the target host and interactively communicate with its
stdin/stdout. Is that feasible via a capsule? Or more concretely, is
there a way to get a shell on the target host from the master without
having to type in any credentials? If it involves some complicated ssh
tunneling, that’s fine.
- For SSH authentication, the Remote Execution plugin sets up some SSH
keys in all hosts and proxies automatically which newly provisioned
hosts will have. I think it would make sense to use them with Cockpit
if possible. Ansible also reuses that.
Yes, that would be the idea.
I’ll keep on answering below