-
Notifications
You must be signed in to change notification settings - Fork 192
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
Simplified Proxy Onboarding #9703
base: master
Are you sure you want to change the base?
Simplified Proxy Onboarding #9703
Conversation
👋 Hello! Thanks for contributing to our project. If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
Suggested tests to cover this Pull Request
|
# Conflicts: # java/code/src/com/suse/manager/webui/services/SaltServerActionService.java
b57a121
to
14f73fb
Compare
Warning
This PR is a work in progress. While the core functionality is in place, there are still multiple scenarios to address and details to refine. This PR is intended to gather early feedback on the current implementation, considering the known issues (listed at the end).
Overview
This PR implements a new feature that aims to simplify the proxy onboarding process (following discussions at https://github.com/SUSE/spacewalk/issues/24680 and https://github.com/SUSE/spacewalk/issues/23714).
Currently, setting up a proxy involves the following steps: onboarding the minion, creating a proxy configuration file, installing Podman and mgrpxy (provided by uyuni tools), and finally running mgrpxy install.
For this initial feature iteration, our goal is to streamline the process by extending the existing web UI functionality (Container Based Proxy Configuration). Once the user fills in the necessary information in a form, the system will automatically set up the minion as a proxy with minimal manual intervention.
Pre-requisites
Note
Whether a minion can be converted to a proxy depends on the running manager:
Base Setup
If an onboarded minion meets the prerequisites to become a proxy, the first step is to go to the minion's Overview page. From there:
This action will make a new main tab, Proxy, visible.
Alternatively, the user can achieve the same result by clicking Convert to Proxy in the top-right corner of the Overview page.
The Proxy tab is intended to display data and provide operations related to the proxy. At this stage, it will only contain the form used to apply the proxy configurations to the minion.
WebUI Form
Note: All visible inputs are mandatory, except the Intermediate CAs.
Flow
Once the user fills in the form and it is valid, the "Apply" button will be enabled. Clicking it will trigger the following flow:
Known issues
Convert to Proxy button is not setting proxy entitlement;Applying a proxy configuration successfully isn't creating a proxy info (Convert to Proxy button is always visible);