welcome to the it exchange february 22, 2011. announcements
Post on 19-Dec-2015
216 views
TRANSCRIPT
Agenda• MSU’s Institutional Data Policy– Don Ries, Enterprise Information
Stewardship• Future MSU Course Management System– Brendan Guenther, Virtual University
Design and Technology• Videoconferencing– Laurence Bates, College of Education
• Virtualization– JJ Streiff, Health Information Technologies
New PolicyInstitutional Data Policy
(IDP)• The IDP became effective January 1, 2011• Any questions?• Support/training going forward?• Securing Institutional Data website:
http://eis.msu.edu/sid
Institutional Data PolicyWhat and Who
• Defines Institutional Data and Confidential Data
• Sets minimum expectations for protecting the security and integrity of institutional data
• All faculty, staff and students are individually responsible
• Units responsible for implementing training and oversight procedures
Moodle Preview & Limited Field Trial
February 22, 2011
Brendan GuentherDirector vuDAT
On behalf of LC&T Moodle Implementation Team
LMS Futures• Running ANGEL since 2003• Planning to run 7.4 until at least 2014– Contract allows us to continue to run ANGEL
7.4 past 2014– Limiting factor will be browser compatibility
• Expect to have two systems for a few years– Allow people time to move on their terms
• Currently looking at Moodle 2.0 • Considering also looking at Instructure Canvas
• Already considered BB9, D2L, & LON-CAPA 3
How We Got Here
“LMS Futures” committee• Led by Byron Brown• Core members from VP-LCT’s units
Tom Davis, Sev Grabski, Brendan Guenther, Matt Kolb, Ryan Yang
Met with Faculty representatives from each college
Brown Bag Presentations, ICTC, Other Venues
Summer Limited Field Trial• Will run a controlled
pilot during US11• Selected several
courses• Each has an
alternative LMS with content already implemented there (for safety)
• Tried to represent diversity of offerings
• GEO 221 Weisenborn• CEP 820 Wolf• NUR 426 Cook• ORCBS Winslow et al• ACC 230 Jacobs• SW Stutzky
Preview System• Allows for
experimentation• NO “live” courses• Unsure if content can be
exported• Interested in feedback• IT staff welcome• …and anyone else in your
unit can join you
• Request access through DLS
• Online form will be available soon
• vuDAT blog will have an announcement when this is ready for you to use.
• Should be ready by Spring Break (+/-)
Questions for IT People• Do you want to be able to run you own Moodle?
– For a department?– For an individual course?
• Who are the important audiences for service?• If you want to innovate on the main system
– How should we handle enhancement requests?– How fast/often do you expect Moodle to change?– What transparency do you expect?– What input would you like to have?
• What data integrations are important?
Questions / News
• Subscribe to feed at blog.vudat.msu.edu
Transformation of HIT datacenterJJ StrieffManager of Network Infrastructure Health Information Technology
Transformation of HIT Datacenter
• 1997• 2 servers + 1 mainframe • 300 desktops• Single 5 ton AC unit• 10MB network via coax• Absolutely NO redundancy
Transformation of HIT Datacenter• 1997 - 2010• 100 physical servers (mostly Dell 1 & 2U
systems)• Almost 3000 desktops• 20+ individual UPS • 20 Ton AC unit with dual condensers • 1GB Ethernet network (from datacenter to
desktop)• Generator backup• Some redundancy but several remaining
gaps
Transformation of HIT Datacenter
• Jan 2010• Proof of concept with VMWare• Both Servers and Desktops• POC returns favorable results• July 2010 RFP released for virtualization
initiative• Jan 2011 all hardware, software and
professional services acquired.
Transformation of HIT Datacenter
• 2011• VMWare• EMC NS960 All Fibre Channel Storage• 15 HP C7000 Blades
Dual 6 core Intel Processors192GB RAM
• Liebert 14KVA UPS• Redundant 10GB fabric inside the datacenter
with redundant 10GB feeds to the campus network.
Transformation of HIT Datacenter• Overall Goals• Consolidate as many physical servers as
possible– 75%
• Convert as many as 1800 desktops to virtual– Student Labs and Clinics first– Repurposing the existing desktop– Replacing existing desktops in the future with thin
clients– Utilizing Linked-Clones as much as possible– RTO for roaming profiles