Page History
| Wiki Markup |
|---|
h3. Objective
This project will bring together 3 separate related projects across IS&T involving the deployment of virtual machines (VMs) to the community into one shared framework and base that can be leveraged for each need and supported and maintained effectively by IS&T.
h3. Background
Virtual machines provide a method for solving some difficult IT problems at MIT such as:
* How do we effectively provide access to certain Windows only applications to the Macintosh community?
* How can we effectively provide a consistent computing environment for students on their laptops across a wide variety or hardware and operating system choices?
* How can we provide a secure and reproducible base VM that departments, labs and centers (DLCs) can leverage for their own purposes and save the 4-8 hours of VM creation each time?
Three separate efforts/projects were started last fall in IS&T, one focused on the business application area, another focused on student computing and a third focused on the basic underlying steps. As we shared information about these various approaches, it quickly became apparent that we should work together to avoid duplication of effort and provide a better service that would be easier to support for the community, so we formed the Virtual Project Team.
h3. Team
* Jonathan Hunt - FSX in CSS (PM for Student VM Project)
* Lisa Robinson - Service Desk in CSS (Business App Project)
* Brian Bulmer - Departmental Services in CSS (Business App Project)
* Patrick McNeal - SWRT in ISDA (Base VM)
* Blake Skinner - SWRT in ISDA (Base VM)
h3. Deliverables - DRAFT
<!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 415 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1273709993; mso-list-type:hybrid; mso-list-template-ids:1337744866 80799400 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol; mso-fareast-font-family:Calibri; mso-bidi-font-family:"Times New Roman";} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l0:level3 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l0:level4 {mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level5 {mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level6 {mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level7 {mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level8 {mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level9 {mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} -->
· Discovery
o Recommendations for specific VMs that would be useful to the MIT community
o Maybe a minimal and ideal set
o Technical information on what’s involved in setting them up and refreshing them
o Recommended technical settings for the VMs around serialization and personalization after download
o Issues, caveats, etc.
o Security recommendations, if any
· Delivery plan
o Resources required to deliver a set of initial test VMs for the recommendations outlined above (who, time estimates, any special software required)
o Service recommendations/requirements for downloading such VMs; do we have something they could be download from? Would it require a new server? Estimate of cost of such a beast, etc.
o Stakeholders, testing requirements, any initial documentation, the usual
· Sustainability and Support plan
o In your estimation, what would be on-going, periodic effort needed to refresh each of these VMs?
o What would the appropriate refresh cycle be for each of them?
o Where is there “flex” in this plan and where isn’t there? (For example, if MATLAB needs to be refreshed every 12 months because the license will stop working, there is no flex. If we would like to refresh Office every 12 months to keep people happy but it will continue to work regardless, there is flex.)
· Business case
o Help us articulate a business case of why this is a good idea
§ How much time are we saving MIT by investing time and resources centrally?
§ How much might we save in support costs by having these available for users? |
Objective
This project will bring together 3 separate related projects across IS&T involving the deployment of virtual machines (VMs) to the community into one shared framework and base that can be leveraged for each need and supported and maintained effectively by IS&T.
Background
Virtual machines provide a method for solving some difficult IT problems at MIT such as:
- How do we effectively provide access to certain Windows only applications to the Macintosh community?
- How can we effectively provide a consistent computing environment for students on their laptops across a wide variety or hardware and operating system choices?
- How can we provide a secure and reproducible base VM that departments, labs and centers (DLCs) can leverage for their own purposes and save the 4-8 hours of VM creation each time?
Three separate efforts/projects were started last fall in IS&T, one focused on the business application area, another focused on student computing and a third focused on the basic underlying steps. As we shared information about these various approaches, it quickly became apparent that we should work together to avoid duplication of effort and provide a better service that would be easier to support for the community, so we formed the Virtual Project Team.
...
Overview
Content Tools
Activity