Closed Bug 496376 Opened 15 years ago Closed 15 years ago

new nfs share on 10.2.71.136

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bhearsum, Assigned: aravind)

References

Details

I'd like to be able to mount /exports/buildlogs/puppet-files from staging-puppet.build.mozilla.org. I know /exports/buildlogs is already exported, but can we have another export for only the puppet-files directory, and let staging-puppet.b.m.o and test-mgmt.b.m.o mount it, please?
Assignee: server-ops → aravind
Can you give moz2-linux-slave03, 04, and 17 access to the share, too?
While not necessary, it might be beneficial down the road to mount this share as read-only on the slaves.. Keep it read-write on staging-puppet where you will add files from. This will protect from anything on the slaves clobbering the dist files. Highly unlikely, but it would be a good practice to be safe.
whats preventing those servers from just mounting the sub-directory? Or is this bug about making that mount point read-only for those two servers?
I didn't know you could do that - neat. I also thought there was a permissions problem or something that disallowed them from mounting it. I just tried again from moz2-linux-slave04 and it worked fine. Long story short: nothing to do here, sorry for the noise.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.