Use ssh controller proxy #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asbalderson
suggested changes
Sep 25, 2023
Sponge-Bas
force-pushed
the
ssh_proxy
branch
from
f196e3e
to
9bfec73
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since recently, workloads on OpenStack controllers do not get a public IP. In order to still get the crashdumps for workloads on OpenStack we need to use the
--proxyoption when usingjuju scporjuju ssh. We need to make a proxy jump through the juju controllers for vanilla ssh commands. This requires slightly different ssh-key handling, which is assisted by thessh-agent-setuppackage.The unittests are updated from nose to pytest and the formatter
blackis run against all .py files.