-
Notifications
You must be signed in to change notification settings - Fork 0
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
Run SUSE service as user _rmt and group nginx #18
Conversation
@joelgordon this can only be merged if the user |
@joelgordon I'm not merging this prior your approval :) |
_rmt is not currently allowed to write to /var/lib/registry |
If it is not already, we would like to make this path configurable. In the short term we would like the path on our servers to be /var/lib/rmt/public/repo/registry so that we do not have to create a new disk or symlink. Later when we are forced to add a new disk, we would like to be able to change the path. |
@joelgordon The path to the registry is already configurable. At the moment you see among others in the systemd service file the following option setting:
if you change the registry location this setting needs to be changed to e.g
Please note cgyle does not offer migration code from one path to another. So the copy of data from former-path to new-path is not a responsibility of cgyle. If you start empty at the new path a full caching procedure will be the result |
The SUSE cgyle service is expected to run as user _rmt
@joelgordon I pushed a commit here to change the registry path to /var/lib/rmt/public/repo/registry |
@joelgordon I'll keep this PR open until you approve. Thanks |
LGTM, you can merge whenever you would like. |
@joelgordon Thanks for the review. I did a test of the change on the test RMT server and found a couple of issues. I sent you details on my findings in a private chat on slack. As a summary to make cgyle work on our RMT servers under the
|
I added a link to the steps into the release plan. We will capture the initial step into a SALT state. We will also need to go back and decide how to handle this on new deployments. We could just add the salt state to the highstate and call it a day, or we could build it into the configuration python steps(My least favorite option here), or we could and it to the image build. @renu-saini @joelgordon |
The SUSE cgyle service is expected to run as user _rmt