CA Community






This Blog

November 2009 - Posts

The long road to virtualizing tier 1 applications

Published: November 23 2009, 09:41 AM | no comments
by Lakshmi Pedda

EMAPS7ZN24ZK 

How often have your heard this, "The Exchange admin vetoed the virtualization project; he felt it was too risky."?

The first wave of server virtualization focused on virtualizing applications primarily for server consolidation in test & development environments. The current phase is transforming infrastructure into one highly efficient pool of resources, enabling greater VM mobility in support of the business. We are seeing anywhere from 15%-20% of workloads virtualized in production today. Going forward, the most advanced customers are looking to standardize on private clouds, which will enable them to reach 100% virtualization in production.

The long road to this journey includes addressing several key questions.

  • Can I deploy it? What will the impact be on performance, will my ISV support it and will it really enable consolidation?
  • Why should I virtualize and what are its benefits? Here you will need to consider its impact on accelerating application lifecycle. How do I guarantee quality of service, and further, does it really cut my operational costs?

On the performance side, hypervisor vendors such as VMware, Citrix and Microsoft have made tremendous strides expanding their performance capabilities. Today, Virtual Machines can scale to run practically any application in the data center. Also, the top four ISVs provide support for these hypervisors, including MS, IBM, SAP and Oracle. Also, in most cases, virtualization actually lowers licensing costs.

Despite the unique challenges associated with large tier 1 applications, customers are already running applications such as SQL with success. Other applications that are seeing strong adoption include Exchange, SharePoint, and Oracle Database.  

On a final note, adoption in production environments is largely driven both by the economic climate, the need to reduce costs, and by the level of comfort that customers have.

Share this post:  EmailEmail

 

By: Lakshmi Pedda
Lakshmi is a senior principal product marketing manager, responsible for product marketing of the ‘CA Virtual’ portfolio – a key pillar of CA Technologies strategy. She is well versed in all aspects of marketing including evangelistic role for server virtualization, go-to-market plans, program execution...
Read More..

Don’t Knock the NOC

Published: November 20 2009, 09:40 AM | no comments
by Ramona Copeland

We all understand that the network is the backbone of the entire IT infrastructure, so vital to business survival.  Even if your applications, databases and physical and virtual systems are performing well, your users will never know it if there are network issues that negatively affect business services and the customer experience. On the other hand, if the network is performing well, but there are issues with applications, databases or systems, chances are someone will always assume it's a network problem.

So, when I recently took over product marketing for CA eHealth Performance Manager, it was no surprise to me to learn that the network team gets initially blamed for most of the issues that crop up; it seems to be an easy assumption for the other domain teams to make, especially when their performance tools say all is fine in their realm. 

Enterprise Management Associates conducted a survey in 2008 that I feel produced some great information:

  • When application-related problems occur, what are the primary ways in which IT most often finds out about the problem? The first answer was of course end users, but next in line? The NOC or monitoring center.
  • 89% of IT organizations use triage teams to solve service performance problems. Why? Because there is no high-level visibility across domains that would allow for quick identification of the underlying issue.
  • For these cross-domain triage teams, what types of personnel are most often included? Survey says... Network Personnel/Management 96% of the time!

As I've participated in customer calls recently, I've found it very interesting to note how the maturity level of the IT organization and how the organization maps IT to business services has a direct impact on how it views the evolving role of the NOC.  No longer just tasked with network performance management, the NOC is increasingly being asked to become the first line of support to determine within what domain an issue is rooted. The more mature the IT organization, the better tools in their NOC, and the more they rely on them.

What is the takeaway from this interesting information?  Don't Knock the NOC!  It just might end up being your best line of defense to remove you from the ever dreaded triage team!

Share this post:  EmailEmail

 

By: Ramona Copeland
Mona Copeland is the senior product marketing manager for CA eHealth Performance Manager and CA’s Distributed Database Management solutions. Her more than 20 years of sales and marketing experience includes Mainstar Corporation, Softek Storage Solutions, Fujitsu, Amdahl Software and McAfee. Earning her...
Read More..

Two cloud computing Rorschach tests: 'legacy clouds' and the lock-in lesson

Published: November 12 2009, 03:06 PM | no comments
by Jay Fry

This week's San Francisco Cloud Computing Club gathering was a great place to meet some of the movers and shakers in the cloud computing market (or at least the ones within a short drive of San Francisco). The event's concept was to spend some quality time talking through cloud computing issues with a crowd of people who spend all day thinking about the cloud and working on making it a reality.

James Watters (now at VMware) and crew invited an intriguing crowd of about 35 or so (here's a Twitter list of attendees). Gary Orenstein snapped some pics. John Furrier (from siliconANGLE) used some magical little device to record the entire multi-hour discussion for posterity. Hopefully the recording bit will turn out to be a good idea. There were a few pithy quotes, for sure.

Raising 2 key questions about cloud computing

 

As James Urquhart (CNET blogger from Cisco) guided the conversation, I heard two interesting points of contention that divided the room pretty dramatically. It struck me that each comment could actually serve as a Rorschach test of a person's view of how powerful and important the concept of cloud computing actually is.

One question was about where IT has been; the other helps define where we might be able to go. Both say a lot about the approach to cloud computing that you're likely to take.

#1: Is cloud computing compelling enough to change how IT runs existing apps?

I lobbed a question for the group to chew on that went something like this: we're hearing lots about new, pre-integrated stacks of hardware, software, storage, etc., that are intended to be used to create private clouds. These systems are interesting for new, greenfield applications. However, even if these sell like hotcakes, most of an end user organization's IT systems are going to still be using what already exists in their data centers.

The question: is it worth the pain and suffering to try to shift what's already running -- and contributing to your business -- to a private cloud? Should you create a "legacy cloud" from what already exists?

History -- and IT conventional wisdom -- say it's too hard to mess with things that work. If it ain't broke, don't fix it. The disruption of changing things adds IT operations risk, and the IT ops guys are not fans of that. Optimists, however, say that cloud computing (even if it's of the internal, private kind) is too compelling to pass up, and IT ops should make the leap.

One person in the Cloud Club discussion compared it to having to till the land to grow the wheat to make bread, versus suddenly having access to a supermarket that sells ready-made bread. You'd always choose the supermarket, right? Not so, if you're in IT operations.

I side with the optimists, but am realistic about how you'll need to get there. Customer feedback continues to say that a Big Bang approach (send everything to a cloud -- now!) certainly won't work in large companies. On the other hand, an incremental shift, app by app, is a lot more palatable by organizations with large, complex IT systems. And, in the end, there will be some apps that never move. (Last week's post mentioned John Treadway of Unisys -- he did a good presentation on a methodical, incremental approach at Cloud Computing Expo in Santa Clara.)

By the way, the answer to this question is not insignificant: it will determine how large the private cloud market will end up being. And, actually, how large the public cloud market will be as well. If end users are too timid, or unconvinced of cloud computing's benefits, this revolutionary change ends up being an uninteresting blip in the IT timeline.

However, my bet is that this process picks up steam bit by bit and is hard to stop.

#2: Has the industry learned its lesson about lock-in?

The second telling question about cloud computing I heard this week is as old as the industry itself, but with a new, cloudy twist. It's a follow-up to the previous questions in many ways. Tom Bittman of Gartner and many others have talked about the private cloud market as just the opening act for cloud computing. At Cloud Club, we talked about private clouds setting the stage for the ability to move some or all of your computing to an external cloud service somewhere. Making platforms slippery enough to be able to handle the shifting back and forth of workloads led to a discussion about how exactly that can come to be.

And the thing that might keep it from being: vendor lock-in.

One potential future tossed around at Cloud Club by James Urquhart, Rich Miller (of Replicate Technologies), and Tom Mornini (of Engine Yard) was that the eventual normal computing scenario will be one in which there are sets of interoperable clouds that customers will be able to choose from and move between, rapidly and easily. This Intercloud concept, as the Cisco folks call it, requires easy interoperability.

And, it requires that the industry (users and vendors alike) have learned the hard lessons about lock-in. The optimists and advanced technologists claim that we already have (Tom of Engine Yard certainly falls into that camp). If it's true, you'll have a slippery infrastructure supporting applications wherever it is that they need to run.

But skeptics didn't let that pass by without a fight. The concept seems too good to be true, and contradicts the way computing has progressed so far.

The economics of the vendors in many ways work against making it easy to move workloads around. Besides, big end user companies are used to making bets on technology stacks with only a few vendors. Is that no longer needed? Customers would certainly prefer the economics that result from making this possible. Will vendors cede control because they know lock-in is a losing proposition? Have we learned the lesson of lock-in at last?

You can see why this discussion needed comfy chairs, a moderator, and a healthy supply of beer and wine.

And the answer, please...

Obviously, there is no answer yet. There's not enough data one way or the other. The market, as we all know, is just getting going. But don't let that put you off. Why?

I think where you stand on this point is actually pretty intriguing: one position is a pragmatic read of what's come before; the other is an optimistic assessment of what's possible. This is a test of whether you see cloud computing as a fundamental shift or just a new buzzword to be exploited by those providing the old thing.

Of course, there is the possibility that cloud computing changes the game, but those who liked the old rules will continue to try to enforce them (read: making money from lock-in). The newcomers will try to undercut those rules and redefine the game. Innovator's Dilemma anyone?

So, my point in highlighting this subset of the Cloud Club conversations was this: keep an eye on these questions. They are some of more interesting things playing out in the cloud computing space.

And, for as much fun as it was to spend several hours in good-natured arguments over these and other topics in a penthouse in San Francisco, none of the answers will appear magically, nor overnight. We leave that to time, actual customers, and the market to decide.

(This post first appeared on the Data Center Dialog blog)

Share this post:  EmailEmail

 

By: Jay Fry
Jay Fry is vice president of marketing, Cloud Computing, at CA Technologies. He has over 20 years of experience in marketing and management for innovative enterprise software companies. Prior to CA, Jay was vice president of marketing at cloud computing start-up Cassatt and founded the marketing department...
Read More..

“Cloudy -- with a Chance of Meatballs”

Published: November 02 2009, 09:49 AM | no comments
by Bill Ahlstrom

This current kids' favorite features a zany inventor whose offbeat creations either end up on the junk pile or terrorize the neighborhood. Until he develops a machine that can turn water into food, so weather takes on a totally different meaning and transforms his hometown's economy, which was based on shipping canned sardines.

Transformation is also the theme of Cloud Computing.

Leveraging the underlying virtualization technologies which enable dramatic hardware consolidation, CapEX and OpEx reductions, and energy efficiency, Cloud offers new models for delivering IT services.

Arguably, Cloud computing will drive changes as extensive as IP did. Over-all, resources will be available just in time - instead of just in case. The promise is that over-provisioning in both networks and data centers will become a thing of the past.

That's what's driving the frenetic pace, as vendors, enterprises, service providers, consultants, analysts, investors all whirl around the cloud trying to define strategies, identify opportunities, and devise competitive advantage.

So what's really different here? The issues and problems are the same ones the industry has been grappling with for decades: Application or service availability and performance, quality of end-user experience, rapid reliable creation and deployment of new applications and services, reduced OpEx and CapEx, security of access and of data....everyone's familiar list.

When I was in college, mainframes were king and interactive computing was a gleam in a few people's eye. Batch jobs were delivered to the data center in racks of punched cards, and results were available a few hours later. Gradually, timesharing came into vogue, with companies like GE Information Systems shouldering the big iron costs and enabling leased-line-connected customers to access computing power they otherwise could never have afforded. Then came off-site payroll and other systems, such as ADP offered. And then, of course, the flood of departmental and individual computing enabled by networking, mini-computers and PCs.

Aren't we seeing a similar evolution?

The hulking mainframe in its air-conditioned, glass-walled sanctuary is now unlimited, invisible compute power somewhere "in the cloud", where thousands and eventually millions of virtualized devices will provide on-demand and pay-as-you-use computing power, storage, applications, and services to billions of devices ranging from handhelds to net-books and note-books, to wired homes and smart buildings, and even "smart cities". The "end-user" may be literally anywhere, perhaps a person, a collaboration group, a community of interest - or in even more billions another device or application, such as an On Star automatic notification that you have just been in an accident because the airbag in your car deployed, also relaying location from GPS. Or a smart power meter that advises appliances in your home to reduce or stop their power consumption because over-all demand has exceeded thresholds and the regional grid has automatically "ordered" cutbacks to avoid brownouts and blackouts. Similarly, the service or application may be anywhere, and may change dynamically as conditions change. Face-recognition software monitoring international arrivals through CCTV at London Heathrow may be overwhelmed when using CCTV scans of Piccadilly Circus on New Year's Eve unless expanded resources can be made available instantly.

A fascinating presentation by Google recently outlined its design goals: ~10(6) - 10(7) machines; ~10¹³ directories, ~10(18) bytes of storage, spread at 100s to 1000s of locations around the world, ~10(9) client machines and requires "automatic, dynamic world-wide placement of data and computation to minimize latency and/or cost" depending on constraints such as bandwidth, power, resource use etc. See: http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf

These are real differences of scale. But fundamentals remain: Deploying, monitoring, managing, securing -- and doing it all at affordable cost.

With such vastly increased scale and complexity, automation assumes new significance. Whether supporting the provisioning of a service chosen by a user at a self-service portal, dynamically moving applications among virtual machines based on demand and load, or provisioning additional capacity to meet flash crowds from successful marketing campaigns from, for example, an airline - automated processes are mandatory.

But to have a truly self-monitoring and self-adjusting cloud environment, which is required by the scale and scope of both services and users, automation must be based on as broad and deep collection and analysis of relevant information as possible.

Self-monitoring that feeds analysis and derives automated action to modify or recover. Again, fundamentals and evolutionary phases we have seen before.

So what's the message?

Easily accessible shared or cloud-based services and resources, available flexibly, on-demand, in a self-service and pay-as-you-use basis is a very attractive model for providers and users alike. As a Gartner analyst said at their recent Symposium: Cloud is the top tech trend and issue for 2010.

Certainly CA's customers and partners are among those working mightily to determine how best to respond, leverage, and capitalize on this fundamental shift toward the cloud model.

And let us all hope that we remember the lessons from previous transformational shifts, including IP networking and the web: Planning, experimentation and prototyping for fast learning, architecture and best practices will enable us to realize the promise of cloud.

We ignore them at our peril...and if we do, we will deserve to be pelted by - meatballs.

This post first appeared on the TM Forum Cloud Computing Blog.

Share this post:  EmailEmail

 

By: Bill Ahlstrom
Bill is a vice president in CA’s Infrastructure Management and Automation business unit. His CA focus includes international development, partners, network and systems management, service providers, and major customers. Prior to joining CA, he spent 14 years in Cisco’s network management groups, where...
Read More..

More Posts