I've finally gotten around to posting the last of my notes from Educause. I attended a session on server and storage virtualization at Seton Hall University. The folks at Seton Hall are doing some pretty interesting things in these areas. One interesting thing is that they have SANs from multiple vendors - IBM and Sun - but are still able to mirror data between the two platforms without any problems. They use IPStor from FalconStor to achieve this seamless data mirroring between platforms. This software allows mirroring and physical disk moves without any downtime. In addition, it allows for live snapshots to be taken. One thing that the gentleman cautioned against is trying to mirror the data during I/O peaks; even though there's no downtime, mirroring does have a noticeable impact on I/O. As such, it would probably be best to perform the mirroring during off-peak hours. The gentleman from Seton Hall also noted that clustering is an absolute must when it comes to storage virtualization. He also mentioned that the administration of their setup is so simple that they have no need to have a dedicated storage administrator. Based upon the salaries that these folks can command, this is a significant savings for Seton Hall.
Server virtualization is big at Seton Hall. They've signed an enterprise site license that gives them access to pretty much anything that VMWare offers. They use VMWare Virtual Infrastructure, ESX Server, VDI (for desktop virtualization), Lifecycle Management, and SRM (for disaster recovery). With regards to VMotion, they recommend using "like" platforms - e.g., Intel to Intel, AMD to AMD - for best results. In addition, each physical server should have a dedicated GigE NIC for VMotion for best results. They recommend adhering to VMWare's hardware compatibility list for the best experience. In addition, the presenter noted that Virtual Center can tie in to Active Directory for authentication.
They've chosen to look into VDI for desktop virtualization. In addition to the licensing, they went down this route because of small learning curve for their sys admins as well as the fact that it integrates with VMWare Virtual Center.
Wednesday, November 12, 2008
Saturday, November 8, 2008
New President and Sarah Palin
Finally, voters in the USA have selected an African American as president. In my opinion, this was long overdue in that African Americans have made significant contributions to this country yet have not held the highest office in the land. Now, I don't believe that someone should be elected to a position or hired solely based on the color of his/her skin. However, it is clear that African Americans have (and continue, to some extent) to be given short shrift in this country. The fact that Barack Obama - a man who, unlike other African Americans that ran for President such as Jesse Jackson and Al Sharpton, I feel is eminently qualified to hold the highest office in the land - was elected is an acknowledgement that we have made a lot of progress with regards to equality and civil rights in this country. Yes, we still have a long way to go. But one would have to have their head buried in the sand not to recognize the progress that has been made, particularly within the last 50 years.
With regards to Sarah Palin, the sniping that has been coming from anonymous members of the McCain campaign staff over the last few weeks has turned her into a sympathetic figure, in my opinion. A cynical person might suggest that this has been done on purpose in order to increase her popularity among Americans. However, I honestly believe that the McCain folks are simply bitter and, rather than blame their idiotic tactics for McCain's loss, they snipe at Sarah Palin in anonymity. While I thought that she is not prepared at this time to be vice president, I believe that come 2012, she will (or at least should) have gathered sufficient experience on the national political scene in order to be a viable player in presidential politics.
With regards to Sarah Palin, the sniping that has been coming from anonymous members of the McCain campaign staff over the last few weeks has turned her into a sympathetic figure, in my opinion. A cynical person might suggest that this has been done on purpose in order to increase her popularity among Americans. However, I honestly believe that the McCain folks are simply bitter and, rather than blame their idiotic tactics for McCain's loss, they snipe at Sarah Palin in anonymity. While I thought that she is not prepared at this time to be vice president, I believe that come 2012, she will (or at least should) have gathered sufficient experience on the national political scene in order to be a viable player in presidential politics.
Educause Notes
I have some more notes to post (from the last 2 sessions I attended). One of the is about data center infrastructure and the other one is about server and storage virtualization at Seton Hall University. I'll post them when I return to work and can access the laptop I took with me to Educause.
Wednesday, November 5, 2008
Educause Notes - Part V
I finally located my notes on the "Heroes, Silos and Small Boxes" session I attended at Educause last week. It was led by a project manager from Harvard Faculty of Arts and Science IT who discussed some of the processes they have in place over there. I particularly found it interesting that they have a very structured change management process in place. They have a committee that vets all change requests; everyone who proposes making systems or other types of changes has to be prepared to discuss their plans (which must also include backout plans) and to answer questions in front of the committee. On top of this, they also do a post-implementation review of all changes that take place. In addition, the presenter mentioned a very interesting statistic (one which caused our CIO to kind of nod in agreement when I mentioned it to him) - 80% of all unplanned downtime is self-inflicted.
Another thing that Harvard FAS has in place is strong project management. When a project is proposed, whether it is taken on or not depends on its priority, achievability and value to the business. In addition - and this ought to be a no-brainer for anyone who has ever worked on any type of project - the project intake is absolutely pivotal. Get it right, and you stand a decent chance of succeeding. Get it wrong, and you've added obstacles that can prove to be a project's death-knell.
Another take-away from this session is that organizations ought to reward people for being team players. This serves as a disincentive for hero-like behavior and helps minimize resentment - both on the part of the "hero" who can end up feeling overwhelmed as well as on the part of others who may resent the accolades that the "hero" receives. Also, I got the sense that encouraging hero-like behavior serves as a potential incentive for counter-productive behavior (counter-productive if you are a believer in proper teamwork).
With regards to project management, change management, and pretty much everything else, Harvard FAS IT utilises ITIL generously. Their motto for ITIL is "Just Do It". Also, management buy-in and support is crucial for ITIL initiatives to succeed.
What I ultimately took away from this session vis-a-vis our department is the following:
Finally, the gentleman recommended a few books:
Another thing that Harvard FAS has in place is strong project management. When a project is proposed, whether it is taken on or not depends on its priority, achievability and value to the business. In addition - and this ought to be a no-brainer for anyone who has ever worked on any type of project - the project intake is absolutely pivotal. Get it right, and you stand a decent chance of succeeding. Get it wrong, and you've added obstacles that can prove to be a project's death-knell.
Another take-away from this session is that organizations ought to reward people for being team players. This serves as a disincentive for hero-like behavior and helps minimize resentment - both on the part of the "hero" who can end up feeling overwhelmed as well as on the part of others who may resent the accolades that the "hero" receives. Also, I got the sense that encouraging hero-like behavior serves as a potential incentive for counter-productive behavior (counter-productive if you are a believer in proper teamwork).
With regards to project management, change management, and pretty much everything else, Harvard FAS IT utilises ITIL generously. Their motto for ITIL is "Just Do It". Also, management buy-in and support is crucial for ITIL initiatives to succeed.
What I ultimately took away from this session vis-a-vis our department is the following:
- We absolutely need to implement a formal change management process as soon as possible. Right now, we don't have a process and there really is very little, if any, peer review of proposed changes. It usually takes someone who is not directly involved with a project to spot problems that the project manager or team members may not notice.
- We should involve folks from outside our department where appropriate in terms of serving on governance committees. I realize that it may not be appropriate to involve non-IT folks in all situations, but there are definitely ones (e.g., change management, selection of new technologies) where such involvement is warranted. This provides transparency as to what the IT department is doing and what direction we're headed in. We currently have a technology steering committee that is fairly young; I'll reserve judgment until enough time has passed to allow the committee to get its legs under it.
- Common terminology - aka, ITIL terminology - is crucial. In order to get everyone on the same page, we need to begin using a common language in terms of processes and procedures. To achieve this end, we need to ensure that everyone in the department is properly trained/educated on this common language. Now, this doesn't necessarily mean that everyone should be sent out to training on this stuff. It could mean having those who are already familiar with frameworks like ITIL or CoBIT train others who are not familiar with these things.
Finally, the gentleman recommended a few books:
- "Leading Change" by John Kotter
- "Our Iceberg is Melting" by John Kotter
- "The Five Dysfunctions of a Team" by Patrick Lencioni
Monday, November 3, 2008
Educause Notes - Part IV
I'm trying to find my handwritten notes from the "Heros, Silos and Small Boxes" session I attended during last week's Educause conference. I found the session to be interesting and would like to post my notes/thoughts here (especially since some of my colleagues are waiting to receive my reports from the conference). This is just a reminder to myself to make sure that I locate those notes ASAP so that I can post them here.
Educause Notes - Part III
A third session that I went to dealt with Carnegie Mellon's 802.11n wireless roll-out. The folks at Carnegie Mellon started their roll-out in Fall 2007. They selected Xirrus and Aruba Networks as the respective vendors (I found it interesting that they decided to go with two different types of APs). One of the problems this presents is having two different management interfaces, though the folks at Carnegie Mellon don't find this to be as big a problem as gathering aggregate statistics. On top of this, they've implemented one flat subnet for their wireless network - which they admitted is not the best design. In addition, they do manual site surveys using AirMagnet and aim for -70dBm RSSI (received signal strength indicator - a measurement of the power present in a wireless signal). They're not big fans of the Aruba approach to wireless surveying - i.e., predictive surveying done by inputting information into the appropriate tool which then spits out its predictions as to the RF environment given the inputs. One of the problems they ran into ith site surveying was the fact that many tools out there - at least in their incarnation at the time they were doing the surveying - did not recognize 802.11n networks/adapters.
They recommend using the 5 GHz frequency wherever and whenever possible for 802.11n (and I agree with them on this point). The main reasons for this are that there is less interference from devices that operate on the 2.4 GHz frequency (e.g., microwaves, cordless phones, etc.) and that the use of channel bonding to increase throughput gives you only one non-overlapping channel (there are three if you forego channel bonding) whereas there are 12 non-overlapping channels (twenty-four if not using channel bonding) when using channel-bonding in the 5 GHz spectrum.
On the wired side of the wireless network, they run two Cat5e cables to each location (mostly for future expansion, it appears) and use 802.3af Power over Ethernet technologies. In addition, they use a centralized Aruba Networks wireless controller and have a 10G network core. The folks at Carnegie Mellon recommend having gigabit wired links for 802.11n access points due to the throughput that 802.11n offers.
Finally, they currently are using MAC-based authentication (which realistically is no real type of authentication given how trivial it is to spoof a MAC address). They have plans to look into 802.1x authentication in the next phase of the project. Other than this, their network is pretty open in that they're not using encryption or enforcing authentication (both of which we currently offer, though we only enforce mandatory authentication via a captive portal). One interesting finding that they revealed was that 36% of the students in the dorms using 802.11n - 58% of the dorm residents use 802.11g wireless adapters.
Overall, I found this session to be pretty interesting. There are a couple of things that the folks at Carnegie Mellon are doing that we probably should consider - e.g., gigabit connections to the access points, use of the 5 GHz spectrum where possible, use of AirMagnet, etc. There are also a couple things that I wouldn't do - namely, having one flat subnet for all wireless clients, using MAC-based authentication (although that's better than having no authentication/encryption), and going with APs from two different vendors. Although we are using wireless APs from Cisco and Aruba Networks, we are currently phasing out (slowly) the Cisco access poins while increasing our deployment of the Aruba equipment.
They recommend using the 5 GHz frequency wherever and whenever possible for 802.11n (and I agree with them on this point). The main reasons for this are that there is less interference from devices that operate on the 2.4 GHz frequency (e.g., microwaves, cordless phones, etc.) and that the use of channel bonding to increase throughput gives you only one non-overlapping channel (there are three if you forego channel bonding) whereas there are 12 non-overlapping channels (twenty-four if not using channel bonding) when using channel-bonding in the 5 GHz spectrum.
On the wired side of the wireless network, they run two Cat5e cables to each location (mostly for future expansion, it appears) and use 802.3af Power over Ethernet technologies. In addition, they use a centralized Aruba Networks wireless controller and have a 10G network core. The folks at Carnegie Mellon recommend having gigabit wired links for 802.11n access points due to the throughput that 802.11n offers.
Finally, they currently are using MAC-based authentication (which realistically is no real type of authentication given how trivial it is to spoof a MAC address). They have plans to look into 802.1x authentication in the next phase of the project. Other than this, their network is pretty open in that they're not using encryption or enforcing authentication (both of which we currently offer, though we only enforce mandatory authentication via a captive portal). One interesting finding that they revealed was that 36% of the students in the dorms using 802.11n - 58% of the dorm residents use 802.11g wireless adapters.
Overall, I found this session to be pretty interesting. There are a couple of things that the folks at Carnegie Mellon are doing that we probably should consider - e.g., gigabit connections to the access points, use of the 5 GHz spectrum where possible, use of AirMagnet, etc. There are also a couple things that I wouldn't do - namely, having one flat subnet for all wireless clients, using MAC-based authentication (although that's better than having no authentication/encryption), and going with APs from two different vendors. Although we are using wireless APs from Cisco and Aruba Networks, we are currently phasing out (slowly) the Cisco access poins while increasing our deployment of the Aruba equipment.
Saturday, November 1, 2008
Educause Notes - Part II
Another interesting session I attended was about student email - specifically, what other colleges were doing in terms of providing email for students. Based upon what I heard here as well as during the Zimbra advisory panel, it seems that many schools are or have been using the open-source Cyrus IMAP along with another open-source package - Horde - for webmail. During this session, representatives from Indiana University, Eastern Michigan University, Reed College and the University of Idaho discussed where they are in terms of student email.
Indiana University decided to allow students to choose which email service they preferred - Google or Microsoft. As of the time the data for this presentation was gathered, 65% of students preferred Google while the remaining 35% preferred Microsoft. In addition, only new students have a choice; existing students have a mailbox on the existing messaging system that they can opt to have migrated. Furthermore, IU's legal counsel examined the contract between Google and the university and concluded that it was only suitable for student mail, not for faculty and staff. Another issue that came up was FERPA - the Family Educational Rights and Privacy Act. New regulations are causing schools to re-evaluate contracts. One thing I found interesting when listening to the gentleman from IU was that IU students are indifferent when it comes to email. I suppose that on a larger level, students at the university where I work might have a similar outlook (note that I have no idea whether this is true or not; I'm just speculating). On a side note, I wonder what differences we might be discern in the attitude towards university/school IT services/systems amongst undergraduate students is versus graduate students. However, based upon my experiences in administering our email system, I am absolutely certain that students at our school do not feel this way. Email is an absolutely critical component in the communications toolkit of all of our constituencies and any extended outages or issues reflect poorly on our department and helps raise the ire of our students.
Someone from Reed College, a small, liberal arts college in Portland, Oregon, spoke about what approach they took to student mail. The only noteworthy thing that this gentleman mentioned was that after doing a cost-benefit analysis of migrating students to another service, they found that the relative costs of doing the migration were pretty low but also that the benefits that they would see would be marginal and because of these facts, they've decided to go with what they have in place (Cyrus IMAP). They are also working on unified communications at Reed, though nothing has been rolled out as yet. In addition, the powers that be at Reed College are open to outsourcing when outsourcing is the right approach for them to take. Finally, Reed College is another school whose legal counsel strongly prefers to keep employee mail in-house.
Eastern Michigan University has decided to go with hosted Zimbra (Zimbra is not doing the hosting though - Merit Networks, based in Michigan, is the hosting service). The choice was made by a committee that was convened for the purpose of choosing a new email system that was scalable, highly available, secure and full-featured. The committee - which was comprised of members of key constituencies across the Eastern Michigan campus - was given a lot of leeway to find solutions. They considered the following options:
1. Google Apps for Education
2. Microsoft Live@EDU
3. Microsoft Exchange
4. Zimbra Collaboration Suite
5. Groupwise
Zimbra was the unanimous selection of the committee. After choosing Zimbra and moving to it, they have found that members of the Eastern Michigan community have liked it very much.
The final presenter was the representative from the University of Idaho. They have a pretty restrictive policy on student mail - students are not allowed to forward their mail and the university has mandated that only the university's email system may be used for official communications. They decided to go with Microsoft Live@EDU since its roadmap met the university's needs for future integration with Exchange. They were able to migrate student accounts successfully with a few minor hiccups along the way. However, they also have some ongoing concerns which, in my opinion, sound pretty major. These include the following:
1. Password synchronization - students have two usernames and passwords for university systems and email
2. Integration with Exchange does not work as had been promoted
3. They've found that renaming accounts destroys mailboxes in some cases
4. Microsoft Premier support is not responsive to the university's needs
5. There are no reporting tools available
Overall, I found this to be an interesting session and found myself curious to find out what the student body at the University of Idaho thinks about the email system provided to them by the university. This is entirely speculative, but I would imagine that the university's email system for students isn't held in high regard. Of course, if the students at the University of Idaho share the same opinion of email as a communications tool with the students at Indiana University, then I suppose that the issues that IT has run into aren't that bad from their perspective. Finally, I thought that forming a committee and populating it with members of key constituencies at the university when making a major decision with respect to services that affect a large number of a university's community is a great decision and, in my opinion, ought to be a no-brainer. From my experience, however, this "no-brainer" is far from a "no-brainer" - I've witnessed situations where decisions that affect a large number of our users have been made with no input from the community when such input was warranted. I wonder how the external perception of our department fares when such decisions are made; I assume that we are not exactly held in the highest regard.
Indiana University decided to allow students to choose which email service they preferred - Google or Microsoft. As of the time the data for this presentation was gathered, 65% of students preferred Google while the remaining 35% preferred Microsoft. In addition, only new students have a choice; existing students have a mailbox on the existing messaging system that they can opt to have migrated. Furthermore, IU's legal counsel examined the contract between Google and the university and concluded that it was only suitable for student mail, not for faculty and staff. Another issue that came up was FERPA - the Family Educational Rights and Privacy Act. New regulations are causing schools to re-evaluate contracts. One thing I found interesting when listening to the gentleman from IU was that IU students are indifferent when it comes to email. I suppose that on a larger level, students at the university where I work might have a similar outlook (note that I have no idea whether this is true or not; I'm just speculating). On a side note, I wonder what differences we might be discern in the attitude towards university/school IT services/systems amongst undergraduate students is versus graduate students. However, based upon my experiences in administering our email system, I am absolutely certain that students at our school do not feel this way. Email is an absolutely critical component in the communications toolkit of all of our constituencies and any extended outages or issues reflect poorly on our department and helps raise the ire of our students.
Someone from Reed College, a small, liberal arts college in Portland, Oregon, spoke about what approach they took to student mail. The only noteworthy thing that this gentleman mentioned was that after doing a cost-benefit analysis of migrating students to another service, they found that the relative costs of doing the migration were pretty low but also that the benefits that they would see would be marginal and because of these facts, they've decided to go with what they have in place (Cyrus IMAP). They are also working on unified communications at Reed, though nothing has been rolled out as yet. In addition, the powers that be at Reed College are open to outsourcing when outsourcing is the right approach for them to take. Finally, Reed College is another school whose legal counsel strongly prefers to keep employee mail in-house.
Eastern Michigan University has decided to go with hosted Zimbra (Zimbra is not doing the hosting though - Merit Networks, based in Michigan, is the hosting service). The choice was made by a committee that was convened for the purpose of choosing a new email system that was scalable, highly available, secure and full-featured. The committee - which was comprised of members of key constituencies across the Eastern Michigan campus - was given a lot of leeway to find solutions. They considered the following options:
1. Google Apps for Education
2. Microsoft Live@EDU
3. Microsoft Exchange
4. Zimbra Collaboration Suite
5. Groupwise
Zimbra was the unanimous selection of the committee. After choosing Zimbra and moving to it, they have found that members of the Eastern Michigan community have liked it very much.
The final presenter was the representative from the University of Idaho. They have a pretty restrictive policy on student mail - students are not allowed to forward their mail and the university has mandated that only the university's email system may be used for official communications. They decided to go with Microsoft Live@EDU since its roadmap met the university's needs for future integration with Exchange. They were able to migrate student accounts successfully with a few minor hiccups along the way. However, they also have some ongoing concerns which, in my opinion, sound pretty major. These include the following:
1. Password synchronization - students have two usernames and passwords for university systems and email
2. Integration with Exchange does not work as had been promoted
3. They've found that renaming accounts destroys mailboxes in some cases
4. Microsoft Premier support is not responsive to the university's needs
5. There are no reporting tools available
Overall, I found this to be an interesting session and found myself curious to find out what the student body at the University of Idaho thinks about the email system provided to them by the university. This is entirely speculative, but I would imagine that the university's email system for students isn't held in high regard. Of course, if the students at the University of Idaho share the same opinion of email as a communications tool with the students at Indiana University, then I suppose that the issues that IT has run into aren't that bad from their perspective. Finally, I thought that forming a committee and populating it with members of key constituencies at the university when making a major decision with respect to services that affect a large number of a university's community is a great decision and, in my opinion, ought to be a no-brainer. From my experience, however, this "no-brainer" is far from a "no-brainer" - I've witnessed situations where decisions that affect a large number of our users have been made with no input from the community when such input was warranted. I wonder how the external perception of our department fares when such decisions are made; I assume that we are not exactly held in the highest regard.
Educause Notes - Part I
I've finally gotten around to posting some of the notes I took during this year's conference. Though I didn't get a chance to go to all of the sessions that I'd planned to, I still went to enough whereby I was able to glean a lot of useful information. The first session I attended was one about P2P war stories where folks from a couple of SUNY schools recounted their experience with the RIAA. Morrisville State College which, with a student population of 3,400, is a pretty small school has been in the top 25 of the RIAA's list of colleges with the highest rate of copyright infringement. They've installed Audible Magic to try and cut down on copyright infringement yet still continue to receive DMCA takedown notices. On top of this, the folks at Morrisville have the Ruckus music subscription service for students. The main complaint about Ruckus is that music downloaded through it don't play on iPods.
The University of Albany incorporates information about copyright infringement during student orientation and also has a Resnet ethics quiz for students every fall. On top of this, they make students pay to have their network connection re-established if it was disconnected due to a copyright violation. Unlike Morrisville, however, they have not and don't currently have plans to implement a music subscription service for students.
One interesting thing I learned during this session was that the next big thing in copyright infringement is textbook downloads. This is growing due to the high cost and low resale value (even after only one semester). For this reason, faculty who may not currently be bothered by the current incaranation of copyright infringement (i.e.,illegal music and movie downloads) may take notice in the next few years as their pockets are impacted by illegal downloading of textbooks that they've written.
The Higher Ed Act of 2008 has had significant impact on schools in this area. Schools are now required to certify that they have concrete plans to combat copyright infringement. In addition, they have to inform students about P2P use, particularly regarding to copyright infringement. In addition, institutions are encouraged to offer alternatives to illegal downloads.
The overall lesson that I took away from this session is that when there are things that impact students, it is very important to involve student affairs as well as public relations. On top of this, when it comes to copyright infringement and potential legal action, tread cautiously, involve your university's legal counsel, and don't take drastic action against students without verifying the offending activity (things that trigger DMCA takedown notices - i.e., merely making copyrighted materials available illegally should not be grounds for extreme actions such as suspension or expulsion), as there have been cases where takedown notices have been sent erroneously (one example mentioned was about a network printer).
The University of Albany incorporates information about copyright infringement during student orientation and also has a Resnet ethics quiz for students every fall. On top of this, they make students pay to have their network connection re-established if it was disconnected due to a copyright violation. Unlike Morrisville, however, they have not and don't currently have plans to implement a music subscription service for students.
One interesting thing I learned during this session was that the next big thing in copyright infringement is textbook downloads. This is growing due to the high cost and low resale value (even after only one semester). For this reason, faculty who may not currently be bothered by the current incaranation of copyright infringement (i.e.,illegal music and movie downloads) may take notice in the next few years as their pockets are impacted by illegal downloading of textbooks that they've written.
The Higher Ed Act of 2008 has had significant impact on schools in this area. Schools are now required to certify that they have concrete plans to combat copyright infringement. In addition, they have to inform students about P2P use, particularly regarding to copyright infringement. In addition, institutions are encouraged to offer alternatives to illegal downloads.
The overall lesson that I took away from this session is that when there are things that impact students, it is very important to involve student affairs as well as public relations. On top of this, when it comes to copyright infringement and potential legal action, tread cautiously, involve your university's legal counsel, and don't take drastic action against students without verifying the offending activity (things that trigger DMCA takedown notices - i.e., merely making copyrighted materials available illegally should not be grounds for extreme actions such as suspension or expulsion), as there have been cases where takedown notices have been sent erroneously (one example mentioned was about a network printer).
Subscribe to:
Posts (Atom)









