Interop 2008: Wednesday keynotes liveblog

| No Comments | No TrackBacks

Part 1: IBM and Web 2.0 / collaborative technologies. Presenter was using Lotus Symphony to present his slides; claims it's free to download and at least looks to be on par with Powerpoint.

Current iteration of Notes is slick and is incorporating the technologies that we are trying to smash together--directory services, blogs, wikis, social networking (Face/Space, Twitter), IM, the whole works. Still looks a bit like a clunky IBM product.

Look for a beta of their new Web 2.0 product, Bluehouse. Demo wasn't clear whether this was the name of the suite or a component.

Part 2: Cisco and virtualization. Why virtualize? (We're talking about virtual presence, and virtual servers/VM.) Costs, large campuses, multiple locations, globalization.

Speaker is promoting virtualization as a way to multitask more efficiently (argh!). Need to upgrade human brain first.

Now getting into a real issue about virtualization: IT silos and individual resource pools make it tough to get buy-in. Q: Would PSU be able to bring computing resources together out of the individual departments/silos? PSU Cloud in the future?

In many virtual server setups the weakest link is the hypervisor. Admins leave big security holes here. Beware!

Virtualization shifts mindset from server-centric to services-centric. A good shift.

No TrackBacks

TrackBack URL: https://blogs.psu.edu/mt4/mt-tb.cgi/17611

Leave a comment

March 2009

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        

Contact Me


AIM: TNS BillS

View William Simon's profile on LinkedIn

Donate

Make a gift
Like this blog? Support education and research at Penn State by donating any amount to an area of your choice.

Subscribe

Blogroll

Disclaimer

We are Penn State, but I am not. Opinions expressed on this blog are those of the author and do not represent the opinions of The Pennsylvania State University or any division therein, including but not limited to the author's workgroup, department, administrative unit, or campus. Technologies and ideas discussed on this blog do not describe a production service unless noted.