Admin Tasks

From Van Essen Lab

Revision as of 16:34, 23 February 2012 by Jschindl (Talk | contribs)
Jump to: navigation, search
  1. Remove warning when accessing brainvis through SSL/https.
  2. Upgrade Brainvis to latest LTS release (10.04)
    • Upgrade mail server to support encrypted files for extra security
    • Upgrade mail server to support mail dir (which should help improve performance)
    • Set up a single sign on system (LDAP) for all machines to make it easier to keep accounts and passwords in sync across all machines
    • Migrate wiki pages to new wiki on brain vis
  3. Upgrade brainvis hardware, either by purchasing a machine from a well-known vendor or building a machine
  4. Upgrade NFS shares to version 3 at minimum, and make sure permissions are set up so that all users can access files with appropriate permissions
  5. Continue to update and maintain build systems, as needed
  6. Migrate build servers to myelin2 (our secondary file server), running under virtual box (see both Tim and Jon for details)
  7. Migrate sumsdev to latest LTS release of ubuntu
  8. Create and/or support development environment releases for 3rd party developers
  9. Create and maintain git servers, actively support granting access to outside developers where appropriate
  10. Maintain, and possibly upgrade the linux machines that are used by our rotating graduate students
  11. Perform an inventory of all back up procedures and come up with a sensible back up policy that will ensure that all important files and data are backed up regularly
  12. Perform an inventory of all equipment and machines. Attempt to standardize on certain versions linux/OSX/Windows where appropriate to make our systems easier to maintain
  13. Perform an inventory of our installed software. Ensure that all software is licensed properly. Also, manage site license programs, such as vmware's academic alliance, MSDN, and any other programs that require an administrative point of contact.
  14. As you perform an inventory of the hardware and software above, document all possible security threats or situations that could cause catastrophic failure (e.g. data loss, hardware failure, etc.). After coming up with this list, come up with strategies for tackling these issues and meet with the rest of the lab to discuss them.
  15. Document all procedures, inventories, and policies on the wiki, as necessary. Where policies are ambiguous (the rule, not the exception), meet with the rest of the tech and admin staff to develop sensible policies and procedures for usage of equipment.
Personal tools
Sums Database