This is Adele's Brain on ITS
November 4, 2005

1. Accounts Management
Open
and Blocked tickets in the ITS Accounts Group
ITS Accounts Brain Cells
1.1. Accounts Deletions
Terminations clearances, EPANs, and bulk account culling are
three major components of accounts deletions at ITS. The public pages describing
our processes and policies are at:
I handle EPAN account culling monthly as user requests come in.
Termclear and EPAN tickets currently blocked: I've unassigned myself from
the tickets which are currently blocked. Some of them will unblock when they
are ready to be goneshed, others are already goneshed and will unblock when
they're ready to be morgued.
Termclear and EPAN tickets currently open: I'm going through them during the
week of October 24th, and if they need action which I no longer have privs
to do, I'm unassigning myself. If the action needed does not require additional
privs other than my T-Reqs status, I'm doing what is needed and then blocking
and unassigning myself from the ticket.
All of my files I've used over the years aside from the tools in /ccovol/admin/bin
and /ccovol/admin/scripts and tools that Roger has made for me live in /home/adele/accounts/
.
RSI account culling in progress (when this culling is finished, the RSI group
in NIS and ldap-auth should be retired)
Tickets currently blocked: I've unassigned myself from the tickets which
are currently blocked. These will unblock on November 2nd, when they are
ready to be goneshed.
Tickets currently open: There are a couple RSI students who have accounts
in the recruit group who also have accounts in the ug group... they need
to be transitioned to only have one account, and the username they should
keep needs to be the username they have in the ATC/Oracle side. Patrick Lam
in ATC may be able to assist if username changes are needed on the ATC/Oracle
side. Note that the second account username needs to be made into an attached
alias, since both addresses may be in various campus databases as ways to
contact the student.
Summer account culling - do the summer accounts culling at the end
of September every year.
Tickets currently blocked: I've unassigned myself from the tickets which
are currently blocked. These will unblock on November 2nd, when they are
ready to be goneshed.
Tickets currently open: I'm going through them during the week of October
24th, and if they need action which I no longer have privs to do, I'm unassigning
myself. If the action needed does not require additional privs other than
my T-Reqs status, I'm doing what is needed and then blocking and unassigning
myself from the ticket.
ug and grads account culling - do this in October every year.
guest, club, class account culling - do this in November/December
every year.
For guest accounts, https://www.its.caltech.edu/its/operations/guestaccts.html
is out of date (it was written pre-ldap-auth) but the philosophy hadn't changed
as
of
October
2005.
citstaff, visitor, postdoc account culling - do this in January/February/March
every year.
faculty culling - do this in April/May every year.
I mentioned that accounts deletions were challenging, right?
1.1.4. manage the Unix-side morgue
1.2. Accounts Creations
The public pages describing our processes and policies are at:
Note that there is special information All
About Computer Access for Volunteers, Guests, Library Users and Conference
Attendees.
Also, I was on the approved list to sign key request forms for the south entrance
of Steele Building. Bob would know who can now sign those forms, since Dan
and I used to be the primaries on that and we're now both gone.
1.2.1. Single account creation
I was a secondary walk-in
and fax-in individual account creator (Dan was primary, and Mike, Jack,
Kimo, Jason and Alex could all fill in as well).
I was on the distribution list for the new account created logging,
and that's now been set to go to the acctmgmt account, into a procmail filtered
folder. Kimo took care of setting that up, and can answer further questions.
I had wanted to add an alert for when new accounts were created in bulk similar
to this single-wise account creations log, but we didn't get to it.
1.2.2. Bulk account creation
I created accounts in bulk for the inbound undergraduate and
graduate students each fall. This includes collecting username preferences
from the inbound students, as well as making sure that the Admissions Office,
Dean's Office, Graduate Office, Registrar's Office, International Students
Office and the Minority Students Office had correct information about ITS to
provide
to
their
students.
Note that the information sent to fall-inbound students needs
to be to the Dean's Office and the Graduate Office by late February or early
March to be in time for their mailings.
I created accounts in bulk for the inbound summer students (SFP,
FSI, Physics summer students, etc) This included collecting username preference
information from from those summer students who are also inbound Caltech students,
and also making sure that the SFP Office, the Minority Students Office, and
the program coordinators of any Caltech summer program had correct information
about ITS to provide to their students.
The incoming@its account has an autoresponder, and that's how
username preferences came in. I had hoped to set up a webpage with an automated
script to handle these, but never had the time.
I had wanted to add an alert for when new accounts were created
in bulk similar to the single-wise account creations log described above in
2.1., but we didn't get to it.
There's a Brain page about bulk creates but it is slightly out
of date, and another which together, should allow any UCO sysadmin to figure
out this process. Roger is an invaluable resource if you run into trouble.
Go to https://www.its.caltech.edu/its/operations/newunixaccounts.html and
see the section titled "To create lots of accounts at once, in bulk, a
UCO
admin needs to do the following: (updated June 2004)"
Also read Adding
New ITS Unix Cluster Accounts in Bulk
carefully, and see all of the files living in /home/mangler/.
1.3. Accounts Data Synchronization with Other Campus Groups
and Databases
- Use the command-line
tools and utils.its.caltech.edu to
keep ITS account records up to date as needed ("account maintainer" privs
needed on Utils to do this)
- Exchange
2003 transitions (I've trained Kimo on this now)
- Username synchronization with ATC, including sorting out the new process
which should be used for the new account creations
- ATC-related account creations from the daily parking report (developing
this process turned up some huge messy issues which I did not have time to
resolve - I'm handing what I have off to uco-staff and Glenn)
- Figure out a distribution method for the ~950 Oracle/ATC/Techmart account
sheets and P-53s (they are currently in a large red accordion file on my
desk in Steele)
- Get the list of the Oracle users who already have ITS accounts from Patrick
Lam, and sort through their free-floating aliases
- Solve the account deletions issues stemming from the ATC userspace
synchronization (ITS recycles usernames, ATC does not, for one, so what happens
when we morgue a user over here if they're still in ATC's systems for whatever
reason?)
- Accounts deletion integration across Mark's new Exchange 2003 service and
the new for-pay file storage service, ldap-auth, AD and the Unix Cluster
(handed
off in a ticket to unix-admins #652754 and emails
to Mark of our meeting notes)
- legacy mail server retirement issues (there are still a large number of
users on legacy-smtp-server.its.caltech.edu (the only reasons they should
need to be there are that they use really old non-IMAP-compatible unix mail
clients or very, very complicated procmail filtering schemes like Phillipe
Brieu does) out of sheer iniertia, and there is an additional issue... users
set to keep a copy and forward mail
on to
other
addresses
who also
have the legacy server bit set to yes have spam piling up infinitely on chamber).
We need to comprehensively go through the accounts still set to have any
mail go to the legacy server and transition them so that chamber can eventually
be retired. Erich and I had a vague plan for this but then he left and by
the time the UCO group recovered from that void in our personnel, we had
too many machine room move issues to deal with to get to this project.
- Helping retire
non-ITS mail servers for dependent groups on campus, and configuring our
mail systems to answer as them for specific users.
- send informational email to all of the citnp# email forwards with dates
for shutoff (see open tickets about this)
- making sure created ITS account email addresses for students are in all
the appropriate databases on campus (Elena and Cynthia in Directory Services;
Patrick Lam in ATC Security for ATC/Oracle; Debi Tuttle/Rosana Gatti/Gloria
Brewster for the Registrar's Office/REGIS; Natalie Gilmore in the Graduate
Office, and someone in the Housing Office.) I provide the data in Excel format
to each office each late-summer/early-fall.
1.4. Welcome Orientations and Tabling
Passing out new undergrad accounts
We get a table every year at the Undergrad Housing Checkin. Contact the Dean's
Office and/or the Registrar's Office during June/July to reserve table space.
We also pass out new accounts in the Steele Lab (after that closes, having
the accordion file of new accounts at the Helpdesk is probably the best idea.
Passing out new grad student accounts
We get a table every year at the Graduate Student Registration. Contact the
Graduate Office during July to reserve table space. We also pass out new accounts
in the Steele Lab (after that closes, having the accordion file of new accounts
at the Helpdesk is probably the best idea. Many of the graduate students arrive
before the Registration and want to walk in and get their accounts.
SFP Orientation
Things I talked about include:
- ITS accounts handouts in SFP office
- webmail.its.caltech.edu
- forwarding via utils.its.caltech.edu
- changing passwords via utils.its.caltech.edu
- resetting passwords (ID needed or phone caller ID)
- ITS Helpdesk, 312 Center for Student Services, building 86-87 on campus
maps
- www.its.caltech.edu
- wireless networking on campus
- registering MAC addresses
- printing in the Steele Lab from laptops
- logging into the library computers with ITS accounts
- computer labs in the student houses
- Security!!!
- Keeping my computer and my ITS account secure helps protect other systems
and users on the Caltech network. Components of good computer security
include:
- Using well-chosen password for my ITS account and my own computer login,
never telling it to anyone, and using different ones on different systems,
- Keeping my computer's operating system up to date with the latest updates/patches/security
fixes,
- Installing a good anti-virus program on my computer and configuring that
program to use the latest virus definitions and to run both real-time protection
and
regularly scheduled scans,
- Turning on a firewall on my computer to help prevent network-based attacks,
and
- Thinking carefully about the implications of programs which are running
on my computer, since Caltech's network connection to the internet is fast
and
high-profile.
FSI Orientation
FSI is the Freshman Summer Institute (used to be called the Bridge Program).
Inbound undergrads arrive about a month early, and the Minority Student Programs
Office usually asks for a special orientation for them.
International Student Orientation
The International Students arrive for a special orientation a week or two
before the rest of the inbound students, and many of them do not have their
own computers, so I gave the same general overview stuff as the Undergrad Orientation,
but also how to use the Steele Lab computers and printers. We walked these
students through logging into Utils and Webmail to be sure they could access
their accounts.
It's helpful to have a representative from the Registrar's Office there to
help with walking them through their REGIS logins!!
Undergrad Orientation
Things I talked about this past year include:
- where to get help (student house reps, ITS Steele Lab, Helpdesk, ITS website)
- webmail.its.caltech.edu
- forwarding via utils.its.caltech.edu
- changing passwords via utils.its.caltech.edu
- resetting passwords (ID needed or phone caller ID)
- wireless networking on campus
- registering MAC addresses
- printing in the Steele Lab from laptops
- logging into the library computers with ITS accounts
- computer labs in the student houses
- Security!!!
- Keeping my computer and my ITS account secure helps protect other systems
and users on the Caltech network. Components of good computer security
include:
- Using well-chosen password for my ITS account and my own computer login,
never telling it to anyone, and using different ones on different systems,
- Keeping my computer's operating system up to date with the latest updates/patches/security
fixes,
- Installing a good anti-virus program on my computer and configuring that
program to use the latest virus definitions and to run both real-time protection
and
regularly scheduled scans,
- Turning on a firewall on my computer to help prevent network-based attacks,
and
- Thinking carefully about the implications of programs which are running
on my computer, since Caltech's network connection to the internet is fast
and
high-profile.
It's helpful to have a representative from the Registrar's Office there to
help with walking them through their REGIS logins!!
2. Aliases Management
- backing up Mike on new alias creations
- backing up Mike on Mailman mailing list creation and maintenance
- cull
nonlocal forwarding aliases (handed off to Bob during summer 2005)
- match up free-floating aliases which can be made into attached aliases
- UID matching between accounts and free-floating aliases that cannot be
combined because they go to different destinations for the same person
- untangling multidepartmental snarls in the Global Address List
3. T-Reqs Issues
- Train new ITSI employees on how to use it, and assist existing ones with
advanced features
- Back up Kimo and Jack on adding
new T-Reqs experts and groups
- Back up Kimo and Jack about the emergency ticket system
- Be the archivist of history of the project, since I wrote the requirements and
specifications and rollout plan with Erich.
- remove "password change" link in T-Reqs if it's still lingering
(handed off to Jack)
- fix the T-Reqs custom submit help file to be more clear about multi-line
fields - they should be presented in a bulleted list, like the single-line
fields. (on hold indefinitely until IMSS decides which ticket system to use)
- Be sure Jack's recent changes are documented where new ITS users can easily
find them
4. Web services
4.1. The ITS public website
- Structure
and requirements doc for the ITS website circa 2001 (the current
white-backgrounded right-sidebar site)
- All
About the ITS Website (as current
as I can make it today, November 4, 2005) including how to add new sections
and pages, the website table of contents, the include files, and contacting
Cynthia about putting new sections into our Google collection for the search
instance.
- updating news on Utils front page at /local/stow/webconf/etc/webconf/homepage.html.std
(Kimo and Jack can do this)
- Utils stylesheet update (Jack knows some of this)
- assist with fixes to Webmail project (I think this was Mike's project,
with backup from Kimo and Jack and I)
- current ITS website changes as ITS staff requests come in via tickets in
the ITS Web group via itsweb@its.caltech.edu
- ITS website components
I was trying to find time to work on
- debug the dynamic feed from T-Reqs (doublecheck Gharib and Roth groups,
among others) onto the Help Contacts webpage
- ftp section
- security section
- web services section (in progress)
- wireless section (in progress)
- new pages for Joe for the cablemodem section because Charter can't
keep accurate records of who they've refunded of their Caltech users
- VPN request, VPN3000 request, and cablemodem request should all have
email address a required field - doublecheck this!
- desktop support/config guides section for Ciro
- redo IMAP pages
- redo POP pages
- debugging email page
- figure out status of "connecting to ITS servers from Windows
computers in non-ITS domains" document (this is not Dan; who is
working on this?)
- XSL for search results page (trying to make our search results page
look like the rest of the ITS site blue/black/white scheme rather than
the Caltech main site's orange scheme)
- its-announce - retire or doublecheck security permissions and start
using it!
- expand outreach section
- Services for Sysadmin section
- Director's Bulletins and Overviews - Caltech only
- Document MSDN developer stuff (talk to... is it Dimitris now?)
- lab section (retiring now?)
- Unix cluster section
- update Helpdesk section
- NNTP Usenet news section
- House Labs section
- Finally finish cleaning out the old CCO and Info webpages (there
is still good information buried in there that the "new" ITS site is
missing, thanks to the 1997-8 redesign by Aure).
4.2. The ITS Brain website
- I had hoped to enhance the structure of ITS
Brain site, making it easier for people to find things, and easier
to self-submit things. At one point I asked for a Wiki to be set up, but
ITSI did not have a spare server to roll out at that point, and putting
it on one of our production systems was enough of a security concern that
we decided against it at the time.
- Adding
ITS Operations Runbook (Give Me The Brain!) Webpages
- The following were Brain pages I knew needed to be written, or needed additions:
- new
T-Reqs group creation process (awaiting additional info from Kimo/Jack/Erich
about initial multiple experts; do sleuthing about auto-nag for group
descriptions etc.)
- new T-Reqs expert creation process (awaiting data from Mike/Jack/Kimo)
- T-Reqs expert retirement process (partial data from Kimo, but awaiting
more)
- all of the rest of Erich's notes in /home/erich (handed off to Jack
now)
- all of the emails Kimo has sent me to Brainify (currently in a folder
in my adele account's IMAP called "brainify")
- Netapp disk capacity equation philosophy (Roger knows this)
- 800 billing if it isn't there already (Mike does this)
- how to set up an administrative self for a new ITS staff member (Kimo
and Jack know this)
- checklist
for new ITS hires (exists, needs expansion)
- checklist for people leaving ITS (awaiting information from all sorts
of staff and managers)
- library
service and dependencies (Kimo knows this)
- username change process and policy, and why it is what it is
- UCO
tasks and project doc (yes, again... it's gone out of date)
- accessing systems in the new machine room (Jack and Kimo know how to
do this)
- what
are we backing up and for how long doc (awaiting a final doublecheck
from Mike)
- logs and security page (Kimo knows this)
- private net access stuff (Jack knows this)
- jumpstart servers (Kimo knows this)
- revisit the "stop A thing" and make sure it's Brainified
somewhere (Kimo and Jack know this)
- update what services ITS really offers page
(awaiting information from management)
- IP to MAC database (if not already documented... I don't know where
it lives)
4.3 Web Advocacy
I help users figure out which webservers on campus meet their needs. Usually
this is phone calls, drop ins, and tickets to itsweb or to help@its which are
handed off to itsweb.
See also http://www.its.caltech.edu/its/services/internetapps/web/servers.shtml
and Marionne Epalle knows more. Bradley Cain knows about the hosted server
service thing that ITSS offers, but hasn't sent me information for the webpages;
that's partially why the ITS Web Services website section isn't completely
revamped... I had it partially done but was waiting for more information.
4.4 Answering user questions about serving webpages on www.its.caltech.edu
and managing virtual hosts
- web services webpages section update (see 4.3 above)
- talk with Marionne about documentation for the credit card transactions
vendor
- backing up Jack, Kimo and Mike on virtual host creations
- virtual host culling (Roger knows what I was doing on this, since it also
involves hostmaster changes)
- httpuser
mail (handed off to Dimitris now)
- spec out requirements for web statistics service offering, roll out website
statistics package
(on hold indefinitely now)
- investigate offering blogging services since we get requests every year
(on hold indefinitely now)
5. Unix Cluster Operations
- mindterm rollout (internal and user documentation I was supposed to make
more user friendly; handed back to Kimo now)
- decommission
old hardware as needed
- I was the archivist and UCO project lead for the machine room move (the
move plan documents have details of what our servers do and many of their dependencies)
- I was trying to write "All About [Server]" Brain pages for each of our
servers from the machine room move notes and the Systems
Overview page (the UCO
admins update
ITS Unix Systems Overview page to reflect new hardware
upgrades, sparing, services and tripwiring
- budget brainstorm coordination (I handed off all my notes and historical
info to Kimo now)
- authentication by more granular ITS groups for remote/out-of-band access
to machines in the new machine room - NIS or LDAP roles for ITSI, ITSS, Network,
others?
- Help make sure all of the current ITS staffers; accounts are its-staff-ified,
and that former ITS staffers' accounts are de-its-ified and/or removed. (handed
off to Jack now)
- monitor loginwatch, mailwatch, auth-failures-report, jingmai-stats, uco-staff
- be the backup for the Helpdesk and other ITSI Win and Unix admins on password
resets
- be the backup for the other UCO admins on Cleaning
up Processes on inky, blinky, clyde and sue (handed off in late 2004 to
them)
Other pages which might be useful as references: