Tag Archives: virtualization

Cisco Virtualized Unified Communications

Cisco now offers VMware ESXi as a platform for many of their Unified Communications products, including Communications Manager, Unity and Unity Connection, and Contact Center.

I attended Cisco’s TechTV webinar today to learn about it. Great stuff. As you can guess, there’s a catch–it runs on their own server offering, only. It makes sense. Cisco has always prescribed the hardware in order to ensure the environment is right for enterprise voice-over-IP. That is still the case. But the big deal here is that you can now get TAC-supported, VMware-platform Unified Communications products and the benefits of virtualization–more servers on less hardware, easier backups, management through vSphere tools, speedy deployment, and so on.

Will the VMware offering be restricted to Cisco server hardware forever? My guess is, probably not. But the environment would still need to be well-controlled, with strict hardware specifications and not loading other (non-Cisco) VMs into the environment.

Interop 2008 wrap-up

Aside from touring the expo floor, I attended a few more sessions Thursday and then again this morning, gravitating toward the virtualization sessions. As we’re now implementing virtual servers in our machine rooms, a lot of the material was review, but not all. I learned that Microsoft has a free hypervisor offering called Hyper-V. It doesn’t have feature parity yet with VMware but since they’re offering it for free, I would expect VMware to respond by lowering their prices on their infrastructure components. This would be very helpful for us. Having been psyched up by these virtualization sessions, I’m really looking forward to our group getting the first few servers moved to VM and machines turned off.

On the show floor I spent a little extra time talking to network monitoring/management companies and a DNS/DHCP/IP address management company. The latter gave me a blue hat with a cat logo. Guess who? We have honed our DNS and DHCP processes over the years with scripts and mastery of vi but there are better approaches.

I appreciated the breadth of the conference and being able to sample training in various areas. It was an exercise for my brain to be continually switching gears (going from session to session or booth to booth).

Interop 2008: Wednesday keynotes liveblog

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.

Greener IT through bicycling and VoIP

“It’s not easy being green.”

My blog, if you read it from the web page, is green. That’s entirely coincidental. Green happens to be a color I like; I’m not trying to make any particular statements with the color of my blog (except that PSU blue was getting a bit stale).

The focus of “green IT” is mostly on lowering the energy use and heat production of servers, through more efficient servers or a reduction in the amount of actual hardware. In the non-VoIP part of my group, we’re digging into a virtualization project that should reduce 50 pieces of server hardware down to about four if everything works out perfectly. Even a five-to-one reduction would be fine. I’m excited about this project for a number of reasons; one of them is that I won’t have to look at as much hardware in the server room. Fewer server problems should be diagnosed as hardware problems. And hardware problems won’t be so catastrophic–just use some VM magic to move a server from failing hardware to working hardware. This “greening” of IT first involves putting down a lot of green (money) before we see any environmental benefit, which will be secondary to all the system management benefits, the main reason we’re doing it all in the first place.

In a number of years, equipment rooms and power and cooling requirements will have shrunk but we’ll still be committing all kinds of environmental crimes through our still-growing IT staff: driving internal combustion engines at $10+/gallon of gasoline. Two losses of green there: the environment eats our exhaust and the gas stations eat our cash.

Several years ago, Penn State ITS bought a number of efficient departmental vehicles for the staff to use to travel around campus. These four-speed one-seaters are human-powered and the only emissions are from the driver. Sadly, the ITS bikes have been seen around campus turning to rust. Some have been reclaimed and are in active use; Telecom Building has one that gets regular use and I have heard rumor that 300 W College uses one now too. This program could use some fresh support. Biking around campus is pretty easy and you can take shortcuts; there’s no getting stuck in traffic or waiting for the shuttle.

I sit here writing a blog at 6 pm because I biked to work this morning, as I have done most mornings since early May. However, the weather (stormy at the moment) sometimes dictates my schedule. A worthwhile tradeoff, in my opinion: I’m saving money, getting into better shape, enjoying the outdoors, and not polluting. Several of my coworkers also ride to work. This is just one shade of a green IT department.

VoIP and close relative VCoIP (video conferencing over IP) come into play by allowing us to meet from wherever we may be. Phone calls are cheap, conference calling is easy, and video is available on every Mac laptop (and before long, on every laptop). Set up XMeeting on your Mac and participate in video conferencing, wherever you are. It even works through a VPN (somewhat lower quality but usable). Meeting face-to-face and handing out paper copies of documents is familiar and makes us feel like we’re doing business; the greener IT department can do the same thing using video conferencing with side content (whiteboards, Power Point, wikis, etc.). When the personal interaction is the main goal, Penn State’s videoconferencing services meet the need; for a meeting that needs a lot of electronic content delivery, Adobe Connect does a great job. We have the tools right at our fingertips.

Someday we’ll get the hang of telecommuting and people will be able to telecommute more easily. I know other organizations–non-edu, anyway–have already figured this out, but it’s still an awkward thing in higher ed. I heard an analyst say this at a VoIP conference last year, and she’s right. Telecommuting should not be a goal for a greener IT department, but we can all use the concepts and technologies that are part of the telecommuting method to be more environment-friendly and economical in our daily business.