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

(node/rucio01.ls.lsst.org) deploy rucio #1488

Open
wants to merge 5 commits into
base: production
Choose a base branch
from

Conversation

dtapiacl
Copy link
Contributor

@dtapiacl dtapiacl commented Oct 4, 2024

Requirements per ticket information on IT-5509:

• Install the following rpms, xrootd, xrootd-selinux, xrootd-libs, xrootd-client, xrootd-client-libs, xrootd-server-libs, xrootd-server
• modify the /lib/systemd/system/[email protected] and /lib/systemd/system/[email protected] and change the User and Group inside these two unit files to saluser and it group (current it is user xrootd)
• Change the owner of directory /etc/xrootd, /var/{log, run, spool}/xrootd to saluser (this probably need to be done every time there is an update of the xrootd rpms)
• Allow user bwhite and wyang to do a) sudo su - saluser and b) sudo systemctl restart xrootd@summit. We will add Sajid Ali to this list of users once he has an account
• Place VM in BTS-LHN network.
• Mount the filesystems KT mentioned.

@dtapiacl dtapiacl self-assigned this Oct 4, 2024
@dtapiacl dtapiacl force-pushed the IT-5489_rucio_puppet_2 branch 2 times, most recently from 0f0bedc to ecb9a51 Compare October 4, 2024 16:11
@dtapiacl dtapiacl added the enhancement New feature or request label Oct 4, 2024
@dtapiacl dtapiacl force-pushed the IT-5489_rucio_puppet_2 branch 6 times, most recently from 57112a3 to 84f370e Compare October 4, 2024 17:51
hieradata/role/rucio.yaml Show resolved Hide resolved
site/profile/manifests/core/rucio.pp Show resolved Hide resolved
]:
ensure => file,
mode => '0644',
owner => 'saluser',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is saluser being used as the role user? This isn't a tssw related service and it doesn't interact with sal/dds.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They want to use saluser as a service account to manage the xrootd related services.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the ownership of these files to saluser does not allow the saluser to start or stop those services. Nor does it grant saluser the ability to trigger systemd to re-read those files after they have changed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also object to role accounts editing service units. Changes should be made via puppet.

@dtapiacl dtapiacl force-pushed the IT-5489_rucio_puppet_2 branch 3 times, most recently from b2eda09 to 02fb506 Compare October 7, 2024 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants