Project

General

Profile

Actions
Copy link

Feature #25532

closed

Foreman/Cockpit integration

Added by Marius Vollmer over 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marius Vollmer
Category:
-
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

It would be nice to integrate Foreman and Cockpit so that there is a "Web Console" button on the page for a host (next to "Schedule Remote Job") and clicking that button will "seamlessly" open a Cockpit session for the host.

"Seamlessly" means:

- No additional login into Cockpit should be required if the Foreman session can execute remote jobs on the host
- The browser should not need to have direct access to the host, even if remote execution must go through a Smart Proxy
- No additional TLS certificates should need to be accepted and not additional network ports should need to be opened anywhere

Discussion with progress reports: https://community.theforeman.org/t/seamless-cockpit-and-foreman/9846

Related issues 4 (0 open — 4 closed)

Related to Foreman Remote Execution - Feature #25534: Foreman/Cockpit integration - REX partClosedIvan NecasActions
Related to Foreman Remote Execution - Feature #26109: Foreman/Cockpit integration - Web Console button "OAuth"ClosedActions
Related to Foreman Remote Execution - Feature #26110: Foreman/Cockpit integration - Interactive SSH sessions via the SmartPRoxyClosedActions
Related to Foreman Remote Execution - Feature #26116: Foreman/Cockpit integration - Add foreman-cockpit-session toolClosedActions
Actions
Copy link
 #1

Updated by Marius Vollmer over 5 years ago

REX part: https://projects.theforeman.org/issues/25534

The plan for Foreman itself is that

- Foreman sets up a specially configured Cockpit instance that uses a new session starter
- Foreman responds to a new URL path to do the redirection that Cockpit uses to get a session token
- Foreman gets a new button that links to this Cockpit instance
- the Cockpit instance is put behind Apache in a production setup

Actions
Copy link
 #2

Updated by Lukas Zapletal over 5 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #3

Updated by Marius Vollmer about 5 years ago

  • Related to Feature #25534: Foreman/Cockpit integration - REX part added
Actions
Copy link
 #4

Updated by Marius Vollmer about 5 years ago

  • Related to Feature #26109: Foreman/Cockpit integration - Web Console button "OAuth" added
Actions
Copy link
 #5

Updated by Marius Vollmer about 5 years ago

  • Related to Feature #26110: Foreman/Cockpit integration - Interactive SSH sessions via the SmartPRoxy added
Actions
Copy link
 #6

Updated by Marius Vollmer about 5 years ago

  • Related to Feature #26115: Foreman/Cockpit integration - Add foreman-cockpit-session tool added
Actions
Copy link
 #7

Updated by Marius Vollmer about 5 years ago

  • Related to deleted (Feature #26115: Foreman/Cockpit integration - Add foreman-cockpit-session tool)
Actions
Copy link
 #8

Updated by Marius Vollmer about 5 years ago

  • Related to Feature #26116: Foreman/Cockpit integration - Add foreman-cockpit-session tool added
Actions
Copy link
 #9

Updated by Lukas Zapletal over 4 years ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF