Anonymous-RO

Vmware Academic Program

Introduction

The VMware Academic Program (VMAP) is a comprehensive program designed specifically for the academic community. The program enables qualifying academic users at VMAP member organizations worldwide to gain easy access to cutting-edge virtualization technology and resources at no charge.

Availability

Faculty can use VMware software under specific program usage guidelines, free of charge, in a wide variety of areas of academic research and classroom instruction.

Students can use this software free of charge for one year with yearly renewals as part of qualified coursework or research projects. Students must be enrolled in an eligible class to gain access.

Acceptable use cases include:

  • The free single use licenses provided through The VMware Academic Program may be used for instruction and non-commercial research only. Please refer to the definitions of instructional and research use below
  • Lab licenses may only be installed in lab environments where the lab is primarily used for instructional and research purposes.
  • Program software installed in shared lab environments can be used across different courses offered by different faculty members.
  • Faculty members as well as staff directly involved in administering systems and providing support for program software may install the software on their personal computers
  • Students taking qualified courses or conducting research can access program software within lab machines or download programs software on their personal computers. Students receiving licenses through a qualifying course or research project may use the licenses after the course or project is concluded.
  • Multiple academic groups in an institution may join the Program if each group meets the eligibility requirements.
  • The designated Program Administrator (PA) must be an employee of the department or group and is responsible for administering, managing, and enforcing the guidelines set by the EULA for the VMware Academic and Research Program (“Academic EULA”)
  • Every copy of the software must be a true and complete copy and it must include all copyright and trademark notices. All software made available must include all of the files.

Unacceptable use cases include:

  • Students who are in an approved department but are not taking courses that lead to credit or a certificate or who are not involved in relevant research projects are not eligible to use the software.
  • Students, faculty members, or other parties that received a license under the program but no longer attend or are employed by the institution.
  • Staff members who are not directly involved with system administration related to the program, such as administrative assistants, may not install the software on their personal computers.
  • Software that is part of the program may not be shared with non-approved departments. However, it may be installed on shared labs if the approved department's students regularly use that lab.
  • The designated Program Administrator for the member approved may not be a teaching assistant or a student. However, teaching assistants or students may help the Program Administrator with the program.
  • The software provided by VMAP may not be sold, rented, leased, or transferred to any third party including contractors, consultants, other companies, and other department personnel.
  • Software cannot be used for infrastructure purposes. Licenses acquired through the VMware Academic Program are for instructional, research and personal use only.
  • The software provided by VMAP may not be used for any purpose outside of instructional, research and personal use. vSphere licenses provided under this program may not be used for desktop virtualization.

Use of free VMware software for instruction and research is governed by the specific program guidelines and the conditions described within the Academic EULA and the use of software for infrastructure purposes is governed by the VMware EULA for each of the products.

Definitions of Instructional, Research and Infrastructure Use

  • Instructional use is defined as conducting educational classes, labs, or related programs for teaching or learning concepts related to the products that are part of this program.
  • Research use is defined as conducting not-for-profit research projects.
  • Infrastructure use is defined as use of software as a part of the institution's or department's infrastructure that's not intended for specific classroom instruction or research project

Limitations

Once the serial key to a program has been registered, additional keys cannot be generated. Faculty can get yearly renewals on software packages. Students can only download the software once for 400 days. See http://www.vmware.com/partners/academic/faqs.html for more details.

Accessing Software

Unlike CSE's MSDNAA licensing, VMAP accounts are not generated automatically. Faculty wishing to use VMWare software for their class should contact cse-consult.

Students who are enrolled in a class requiring Vmware products will have their accounts created automatically when an instructor requests access. Students will then receive an email message with account information.

Researchers who wish to use Vmware products should have their adviser or faculty member make the request on the researcher's behalf.

Once an account is setup for you, your login name will be your UB email address, for example: ubitname.buffalo.edu.

You will receive an email message stating an account has been created for you. Follow the link to finish setting up your account (including password). Once you have setup your account you should be able to access and download VMware titles at http://e5.onthehub.com/WebStore/Welcome.aspx?vsro=8&ws=bcc13a83-ebc9-e01...

Download and Installation

Titles can be browsed at: http://e5.onthehub.com/WebStore/Welcome.aspx?vsro=8&ws=bcc13a83-ebc9-e01.... Once you have found the title you want to download/install, click the link.

  1. Click "Add to Cart". don't worry, you will not be charged!
  2. Enter your login credentials, your UB email address and the password you would have set when setting up your account
  3. Click "Check Out".
  4. Accept (or decline) the end-user license agreement
  5. Click "Proceed with Order"
  6. Save this page, print it out, or make a copy of the serial number provided. If during the excitement of the download experience you close this page, you should be able to access it again through a confirmation message sent to your UB address.
  7. On this same page click the "Start Download" Button. Depending on the software you will then begin the download or have to select a version of your OS and or specific files you want.
  8. Once the download is complete you can then launch the installer (and follow the prompts) or burn the disk ISO, etc... Different software packages will be delivered in a variety of ways.

References

  1. Help - http://e5.onthehub.com/d.ashx?s=crc38aqxt3
  2. Acceptable use guidelines - http://www.vmware.com/partners/academic/program-overview.html

Data Erasure

Introduction

Because the computer systems we dispose of could potentially hold large volumes of confidential data we must ensure all sensitive data is removed. This will prevent the possibility of data being stolen and compromised, leading to identity theft, loss of reputation, threats to regulatory compliance and financial impacts.

Simply reformatting a drive is not sufficient. Reformatting a drive only removes the file allocation or address tables. The data still remains on the drive.

Disks must be wiped or scrubbed in some way. This usually involves multiple passes of writing 0s and 1s to the drive. The number of passes varies and is determined by how much security is needed. In CSE we will do 6 passes of random characters and one pass of 0 bits.

Methods

shred

The shred program comes standard on most linux distributions including RHEL5.

[kpcleary@repulse /dev]$ sudo shred -n 6 -z -v /dev/sda
Password:
shred: /dev/sda: pass 1/7 (random)...
shred: /dev/sda: pass 1/7 (random)...460MiB/19GiB 2%
shred: /dev/sda: pass 1/7 (random)...461MiB/19GiB 2%
shred: /dev/sda: pass 1/7 (random)...936MiB/19GiB 4%
In the example above the drive was a 20Gb IDE drive connected through a USB to IDE adapter.

scrubdisk

This is a program written by Ken. The attached source code can be compiled on FreeBSD systems. Ken has CDs with scrubdisk added to what is within the "Live FS" support so you can boot a machine using the CD, enter into "Fixit" mode, and then run scrubdisk to wipe out the contents of all the hard drives on that machine (in Fixit mode the operating system is running off the contents of the CD, not relying on the hard drives for anything). There is also a FreeBSD machine named blackhole in the back corner of the Davis 339A machine room that has an IDE swappable hard drive canister and a 6-bay SCSI Multipack chassis attached to it that can be used to wipe IDE and SCA-interface SCSI disks.

Usage:


% scrubdisk -rvFZ -p4 -P1 /dev/disk(s)

Options:


'r' alone would do one random pass but -p4 says do 4 instead.
'v' means verify (read back and compare to what was written) the passes
'F' means do two passes first writing all 0xaa, then writing 0x55
    which flips all the bits
'Z' means end with writing all 0's and verifying
'P1' means only verify one of the four random passes

Physical Damage

If a disk we are getting rid of is still in working order, we will surplus the disk in case it can be used by other state agencies, but only after successfully wiping the disk as described above. If for any reason the disk could not be wiped (usually because the drive failed and is no longer operational, though sometimes drive interfaces are of a type that make putting it into a computer and wiping it as described above inconvenient or impossible) we send the drive to CIT instead of surplussing it. They have a machine that magnetically erases the disks, and then physically shreds it.

Notes

  1. Pay attention to whether the drive is set to cable select, master or slave in the case of IDE. I had to set an IDE drive to master to get it to play nicely with my USB adapter.
  2. Do drives to be shredded now need to go to Bean hall?

People

  1. Ken Smith, scrubdisk author.

References

  1. http://www.digitalissues.co.uk/html/os/misc/shred.html

Cyber Infrastructure OSG policies

Introduction

This document is meant to cover OSG and the Cyber Infrastructure research group usage policies and guidelines.

Processing

  • All access to CSE processing resources for other OSG VOs is provided on an opportunistic basis unless otherwise agreed upon
  • Non-CSE VOs have a hard limit of 48 hours of wall clock time.
    • If CSE staff are forced to kill running processes, we will attempt to provide warning to the affected VO.
    • Under normal running conditions we will attempt to give four hours notice.
    • During some running conditions we may be forced to remove processes without warning.
  • CSE requests that VOs submit using Condor Grid Monitor. VOs unable to submit through grid monitor will be limited in the number of active processes allowed.

Storage

  • CSE provides four storage areas: /home, /local, /scratch, and /projects.
    • /localis an area for software installation shared across all worker nodes.
    • /scratch is a read/write area for temporary files shared across all worker nodes. Files will be purged after 1 week.
    • /home is where user home directories reside. This space as 15 Gb per user quota.
    • /projects is an area for all Cyber Infrastructure specific storage.
  • Samba access for windows machines is available upon special request to cse-consult. Please be sure to mention what machine you will be accessing from.

References

  1. Memebers of the CI research group should see https://wiki.cse.buffalo.edu/services/content/cyberinfrastructure.

CSE Student Systems Fair Usage Policy

Introduction

CSE students are expected to follow the CSE department's computer system usage policies. These policies are in place to help keep the systems running well and to provide fair access and use to all students. These policies are not meant to be an exhaustive list of everything students should not do. Students should also use some "common sense" and "basic social graces".

Policies

Please abide by these policies when using CSE student computing systems.

  1. Out-of-Control Processes. In most cases, when we find a process running on an inappropriate system, we will warn the process's owner via e-mail that we are about to kill the process, then we will kill the process. We will kill a process immediately, without necessarily notifying its owner, if the process is adversely affecting other users or systems, or if it is a CPU-intensive process running on one of the CSE student servers.

CSE Room Access Policy

  1. Faculty and staff obtain access automatically based on their affiliation to UB to all CSE general purpose labs, research spaces, CSE conference rooms, mail room, copier room, and lounge.
  2. Graduate and Undergraduate students (taking CSE 241 and above) obtain access automatically to the Eberlien Memorial Student Lab (Bell 216) based on course registration each semester. They are also permitted access to other CSE labs, and the CSE conference rooms (Davis 310, 337 and 339A) when required by their TA/SA duties (on a per-semester basis). The professor of the class must e-mail cse-consult@buffalo.edu to request access to these rooms.
  3. Access to the copier room is provided at the request of the supervising faculty or staff member on a per-semester basis. Graduate students are not permitted access to the mail room off-hours (evenings and weekends) due to the risks involved with unsupervised access to faculty mailboxes and the fax machine; however, Ph.D students are permitted based on registration.

CSE Lab Usage Policy

Introduction

You are expected to follow the CSE department's computer system usage policies. These policies are in place to help keep the systems running well for everyone, provide fair access to everyone, and so on. These policies are not meant to be an exhaustive list of everything you should not do. You should also use some "common sense" and "basic social graces".

Lab Usage Policies

Most of the policies are in place because the departmental equipment needs to be shared by many people. Some policies are meant to provide everyone fair access to the equipment. Other policies are to address problems that have come up in the past.

  1. No food or drink is allowed in any of the public labs. Food and drink spills damage or ruin electronic equipment.
  2. Print only things you absolutely need to print. Paper and toner cost a lot of money and waste valuable natural resources.
  3. If you need to leave the lab for a short time (15 minutes or less), it is OK to "lock" the display. But if you will be gone more than 15 minutes, log off. Other users might be waiting to log in.
  4. It is OK to use the computers for "recreational" purposes as long as the lab is not full. But if the lab is close to being full, the computers should only be used for academic purposes. In the labs, academic work always trumps play.
  5. Unless otherwise noted, do not connect personal equipment to the departmental network. Personal equipment could introduce malware onto the network.
  6. Do not move, unplug, reboot, or reconfigure departmental equipment unless instructed to do so by cse-consult.