ERSUG teleconference March 17
Francesca Verdier
March 17, 1999 ERSUG teleconference
9:30 AM Pacific Time.
To connect: dial 1-888-476-3757
enter code 109938
LBNL attendees: We'll almost certainly meet in the directorate suite, but I
don't have a room yet.
Agenda so far:
* user feedback on http://home.nersc.gov/
Francesca is interested in your comments: things that are better/worse; any
changes needed?
* April teleconferences
Scheduled topics are:
+ C90 to J90 Conversion and J90 Performance Coding
+ J90 vs. T3E Code Design Principles
+ Fortran 77 vs. the Fortran 90 Programming Model
So far only a couple of signups.
* cf90 update procedures and status of the compiler
PPPL would have liked an advance notification of changes.
We'll publish release notes in the future; for the latest update see:
http://home.nersc.gov/software/prgenv/cray/prgenv3.2.html
current problem report status: 63 reported to Cray/SGI; 16 still open.
The latest release fixed 6 SPRs and our overall sense is that it helped
users.
* J90 update
J90 batch and interactive performance; batch scheduling changes
* T3E update (scheduling)
* NERSC-3 (probably still can't say anything)
* April ERSUG meeting agenda
* Finalize account management procedures:
Summary of ERSUG feedback on account mgt procedures:
+ the use of any NERSC machine should count as active status (i.e. don't
disable on a per machine basis)
+ ANL uses 6 months of inactivity
+ username removal is a drastic step
+ contact inactive PIs by phone
+ migrating files is OK; removal should be at the discretion of the PI
especially as part of the ERCAP process
+ PIs and account managers should not be disabled in an automated fashion
+ 90 days too short for disabling; try 120 or 180 days
+ 90 days too short for disabling; try 6 months
+ send email1 week before disabling to user and PI and account managers;
response to Support needed to prevent this.
+ 150 or 180 days OK for removal but need to send email to user and PI and
account managers; response needed to Support to prevent this.
Resolution:
It makes sense to disable inactive accounts for security reasons. We want
users to be responsible for monitoring usage on their accounts. Therefore,
disabling due to lack of activity has to be on a per-machine basis.
It makes sense to free up online disk space of inactive users so that active
users can use this resource.
NERSC proposes to meet these two goals as follows:
Check for inactivity per machine on the first business day of every month.
For usernames that have been inactive for 120 days: send the user, the PI and
the account managers an email saying that the user will be disabled in one
week unless someone contacts Support to ask that this not happen. As part of
the disabling process the user's online files are archived into a cpio
archive, which will be automatically migrated (so long as it is over the
migration filesize threshold). At this time the PI or account manager may
request that the username be removed. There will be no username deletion
except on request of a PI or account manager.
For the complete text (STILL DRAFT) of the proposed policy see
http://home.nersc.gov/accounts/accounts.html
--
Francesca Verdier email: ver...@nersc.gov
Group Leader, NERSC User Services phone: (510) 486-7193
Lawrence Berkeley Lab fax: (510) 486-7891