Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tools: Split out cockpit-ssh into its own subpackage #5338

Closed
wants to merge 2 commits into from

Conversation

stefwalter
Copy link
Contributor

@stefwalter stefwalter commented Nov 10, 2016

Both the dashboard and cockpit-ssh process go into this subpackage: cockpit-dashboard

Note that until we have a stable interface between cockpit-ws and its authentication processes, we need to require identical versions between cockpit-ws and cockpit-dashboard.

In addition for the time being we have cockpit-ws unconditionally require cockpit-dashboard.

  • Update packaging
  • Decide on a good name: cockpit-dashboard

Depends on:

@stefwalter stefwalter added blocked Don't land until something else happens first (see task list) bot needswork labels Nov 10, 2016
@stefwalter stefwalter force-pushed the package-ssh branch 3 times, most recently from 7d407e0 to c2bcf9a Compare November 10, 2016 09:51
@stefwalter stefwalter removed the blocked Don't land until something else happens first (see task list) label Nov 17, 2016
@stefwalter stefwalter self-assigned this Dec 1, 2016
@stefwalter stefwalter changed the title WIP: tools: Split out cockpit-ssh into its own subpackage tools: Split out cockpit-ssh into its own subpackage Dec 19, 2016
@petervo
Copy link
Contributor

petervo commented Dec 20, 2016

This breaks the kubernetes container where we want cockpit-ws and nothing else.

Long term i don't think we want cockpit-ws depending on cockpit-dashboard, but that's blocking on removing the secondary machines logic from cockpit-ws. Is there a reason to do this before that work is done?

If we do then we can work around the installation issues in the container scripts.

@stefwalter
Copy link
Contributor Author

Okay, so I've reversed the dependency now that we have #5658 and the LoginTo option.

@stefwalter
Copy link
Contributor Author

Added a commit to return "not-supported" when cockpit-ssh is not present.

@petervo
Copy link
Contributor

petervo commented Jan 9, 2017

The kubernetes container needs cockpit-ssh. For the node tests.

Right now we only install cockpit-ws into the cockpit/ws container (https://github.com/cockpit-project/cockpit/blob/master/test/images/scripts/lib/atomic.install#L171). We need to install cockpit-ssh in there as well.

@stefwalter stefwalter added release-blocker Targetted for next release and removed needswork labels Jan 10, 2017
@stefwalter
Copy link
Contributor Author

Priority, part of today's sprint deadline.

@petervo
Copy link
Contributor

petervo commented Jan 10, 2017

Disabling most of the multi machine tests on atomic worries me a little. We've found a lot of OS bugs by running those. I realize we can't install cockpit-dashboard on atomic while it's bundled with cockpit-ssh. Is this a good enough reason to just make the cockpit-ssh package now?

@stefwalter
Copy link
Contributor Author

Disabling most of the multi machine tests on atomic worries me a little. We've found a lot of OS bugs by running those. I realize we can't install cockpit-dashboard on atomic while it's bundled with cockpit-ssh. Is this a good enough reason to just make the cockpit-ssh package now?

Aren't we going to end up in exactly this situation anyway long term, where cockpit-dashboard/cockpit-ssh won't be available on Atomic? If we work around this now we're just delaying inevitable.

Both the dashboard and cockpit-ssh process go into this
subpackage: cockpit-dashboard

Note that until we have a stable interface between cockpit-ws
and its authentication processes, we need to require identical
versions between cockpit-ws and cockpit-dashboard.

In addition for the time being we have cockpit-ws unconditionally
require cockpit-dashboard.

Closes cockpit-project#5338
@petervo
Copy link
Contributor

petervo commented Jan 11, 2017

Yeah good point, though I think it's worth working towards getting it back in at some point. Something something modularity something something containers.

@petervo petervo closed this in fef9d7c Jan 11, 2017
@stefwalter stefwalter deleted the package-ssh branch January 12, 2017 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker Targetted for next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants