Samba
Warning
This documentation is for internal use. It may be of interest to users who are curious about our internal processes and architecture, but should not be mistaken for describing services that we offer or stable infrastructure that end users should rely upon. If you find yourself submitting a ticket about something on this page, you are probably making a mistake.
How to grant Samba access on supported clusters¶
Currently, Samba is supported on Hive and Franklin.
Hive¶
Hive's Samba access is currently controlled through Puppet. At the top of data/nodes/samba.hive.hpc.ucdavis.edu.yaml
,
there is a hpccf::samba::users:
section with a list of Hive users that will have Samba passwords created for them by
Puppet.
-
Verify the user is on Hive and is in a group that has a Samba share.
-
As of this documentation publication, the only group is:
-
metabolomicsgrp
- Access IP:
128.120.208.42
- Access IP:
-
-
You can verify on
samba.hive
withgrep 'grp\]$' /etc/samba/smb.conf
:
-
-
Edit that file to add the new user's Login ID and ticket # number to the list under the appropriate group comment.
-
Commit the changes to git.
-
Push the changes to GitHub.
-
Run puppet on
puppet.hive
. -
verify
~{newuserhere}/samba-password
exists, update the ticket with wording like:INC wording
You have been added to Hive's Samba. Your password for this service can be found in "[code]<code>~/samba-password</code>[/code]" on Hive. The share is "[code]<code>metabolomicsgrp</code>[/code]" and the host IP is 128.120.208.42. Let me know if you have additional questions or run into any issues.
Note: the IP may depend on the group.
TODO: automate through Cheeto¶
This entire process should be moved into Cheeto with Puppet applying the changes. This requires Cheeto to support Quobyte, and probably additional development.
Franklin¶
TODO