New Managed Paths to Private Cloud Deployments Allow for Swifter Adoption at Low Risk by More Enterprises

New Managed Paths to Private Cloud Deployments Allow for
Swifter Adoption at Low Risk by More Enterprises
Transcript of a sponsored BriefingsDirect podcast on the role of effective management in moving
enterprise applications to the cloud.
Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Download the transcript. Sponsor:
HP.
Dana Gardner: Hi. This is Dana Gardner, Principal Analyst at Interarbor Solutions, and you're
listening to BriefingsDirect. Today, we present a sponsored podcast discussion on
finding low-risk, high-reward paths to cloud computing.
Businesses are looking to cloud-computing models to foster agility and approve
time to market for new services. But, attaining cloud benefits can founder,
without higher levels of unified server, data, network, storage, and applications
management.
These typically disparate forms of management must now come together in new ways to
mutually support a variety of different cloud approaches -- public, private, and hybrid. Without
adoption of such business service automation (BSA) capabilities, those deploying applications on
private and hybrid clouds will almost certainly encounter increased complexity, higher risk, and
stubborn cost structures.
Using increased automation and proven reference models for cloud management, and by
breaking down traditional IT management silos, the progression toward cloud benefit will come
more quickly, at lower total cost, and with an ability to rapidly scale to even more applications
and data.
We're here with two executives from HP Software & Solutions to learn more about what BSA is
and why it's proving essential to managed and productive cloud computing adoption.
Please join me now in welcoming our guests. We're here with Mark Shoemaker. He's Executive
Program Manager for Cloud Computing in the Software & Solutions Group at HP. Welcome
Mark.
Mark Shoemaker: Hey. How are you Dana? Great to talk to you again.
Gardner: Good to be with you too. We are also here with Venkat Devraj. He is the Chief
Technology Officer for Application Automation, also in HP’s Software & Solutions Group.
Welcome Venkat.
Venkat Devraj: Thank you Dana. Good to speak with both of you.

Gardner: Mark, I know you've been out and about talking with a lot of folks about cloud
computing. It's a really hot topic around the world nowadays. What is driving the latest wave of
demand and interest in cloud? What's got people really excited?
Shoemaker: There are several things Dana, and it certainly is an exciting time for us. There is
hardly a place we go that we don’t end up talking to our customers about cloud.
Universally, it's the same things that have been driving a lot of the work that IT
has been doing over the last few years. They want to improve their productivity,
definitely get better utilization out of what they have already got. They want to
be your better partner in the business. What that means is to shorten the time
that the business has to wait for the services. It's all of those things, and there’s a
lot to do to get there.
Gardner: Now, we have talked about these different models, even software as a service (SaaS),
thrown in there from time to time. Is there any particular type of cloud approach that you see as
the first step or the early path to more types of cloud?
The private cloud
Shoemaker: Most of the enterprise customers we talk to are looking at private cloud, the
internal cloud solution that they own, that they then provide to their business partners, whether
that’s the development teams or other elements in their business. So, that’s the first step. Most of
them are looking to build on the virtualization work that they've already done.
Devraj: Mark is absolutely right. Coupled with that intention that IT has, there is also an
interesting micro trend that’s occurring. A lot of the application teams, end-user
business teams, are getting increasingly sophisticated. They're learning about
private cloud implementations. They're privy to the same articles and magazines
that IT is reading these days. Consequently, they're demanding levels of service
from IT that are difficult to provide without a private cloud.
For example, because of things like agile development methodologies, application
teams are doing a lot more application deployments and code releases than ever
before. It's not uncommon to see dozens of application releases for different applications
happening during the same day.
IT ops are just bombarded with these requirements, and requests, and they are just unable to keep
up based on yesterday’s processes, which are relatively static. A lot of these processes are based
on standards like ITIL and they have a certain level of static nature to them. They are there for
stability and predictability and they're not evolving to accommodate the kind of dynamism that’s
expected from IT ops.

Unfortunately, or fortunately, these application teams and business unit teams are quite
influential. They're even willing to fund specific initiatives to allow their teams to work in self-
service mode, and IT ops are finding themselves in reactive mode. They have to support them,
make their internal processes more fluid and dynamic, and leveraging technology that allows that
kind of dynamism.
Gardner: So, Mark, it sounds as if cloud isn’t just a new way of doing computing, it's really
changing the way IT is defined.
Shoemaker: Absolutely. Just to add to Venkat’s comment, we're seeing the business driving IT
and demanding that agility and that flexibility. We talk to a lot of our customers,
where their own coworkers have taken corporate credit cards and gone out into
the public cloud, procured space, and have begun developing outside of them.
IT really has to get in front of this. They have to manage all this.
Gardner: One of the things that’s been interesting for me in watching this
unfold is how, not that long ago, IT only had to compete with its past record. As long as they
were showing improvements, riding Moore's Law, getting higher productivity, then everyone was
pretty satisfied. Now, the competition for IT is not necessarily against its past track record, but
they are competing against these other cloud providers, whether it's for platform as a service
(PaaS) or spinning off into actual deployment.
Back to you, Venkat. IT really can't sit around and wait. They're now under the gun to accelerate
the way in which they go about change in terms of a private cloud type of a development and
deployment capability.
Devraj: That’s right. It's easy to say that, though, because when you look at this picture a little
more closely, you find that the third-party companies, the cloud providers, the pure-play server
enablers, have an unfair advantage. Because they were started relatively recently, in the last few
years, they have the advantage of standardized platforms and delivery units.
A lot to deliver
They can say, "Okay, I'm going to deliver only Linux-based platforms, Windows-based
platforms, or certain applications. When you look at the typical enterprise today, IT has a lot
more to deliver. There is a lot of prevailing heterogeneity in terms of multiple software platforms
and versions. There is a lack of standardization. It's very difficult to talk about cloud and delivery
within the enterprise in the same breath, when you look at these kinds of technical challenges.
As a result, IT is undergoing a lot of pressure, but they have to deliver given the kind of
challenges that they face. That’s going to require a lot of education and access to the right kind of
technology, training, and guidance. That’s where HP really comes into help.

Gardner: So this pressure on IT now can't necessarily lead them to leap before they look. This is
still something they need to do with a great deal of planning and foresight. The governance needs
to be in place.
Mark, tell me about what needs to come together in order for IT internally to progress towards
cloud models, but at low risk, and perhaps transform the way they manage things, so that the
services can be created swiftly, but without it being some sort of complexity at the same time.
Shoemaker: The one thing that’s different about cloud is that it really is a supply chain. It’s the
supply chain of IT technology that the business consumes. If you think about what a supply
chain is, it’s something that’s got to be repeatable. As you said, it has to be governed, to some
extent, and it provides a baseline or foundation and building blocks to build those services that
you can then customize on top of the business.
So, the farther up that you can go with your standard building blocks, the less difﬁcult it is to
manage and focus on the custom business-facing functions on the front-end.
To do this, cloud has helped us out in a lot of ways. One of the challenges IT has always had is to
get the business to consume standards. Because of a lot of hype in the market, the business
absolutely is convinced that they get it and they want the business beneﬁts that cloud offers.
To consume that, as you said, you have to start with standards. I'd wager that the majority of
technology inside of most of our data centers, as much as 70 percent, is the same every time. It's
the same hardware, a lot of the same software, and a lot of the same application packages.
You have to look at your total footprint and understand what those common elements are and
then start building those inside the cloud catalog or the inventory of what would be consumed
inside of the cloud. These can be OS images with applications, common applications, like SQL
Server or Apache Web Server, that then get loaded into the service catalog. That’s what the
developers or whoever the users are going to be get to select.
So, you control the base building blocks, and then they get consumed and can be developed on
top of. Does that make sense?
Gardner: It does. It sounds like it's really something that’s aligned with these multiple clouds
and sourcing options as well, whether it's hybrid, private, public, because if things align with that
service catalog, regardless of where the services originate, there is that opportunity to leverage
them, but in some sort of a managed fashion.
Shoemaker: You're right. One of the things you can't overlook is the fact that the business is the
same. We want cloud, and IT is not ready for it. Even if the business decides to go to a public
cloud, they still have to consume those elements in a standard fashion. There's no way out of
that.

Doesn't work like that
We got kind of spoiled with virtualization, because there is that big P2V button, where you
could take a physical server and basically pull it into a virtual image on another physical server.
The cloud doesn’t work like that. There is no P2C button inside a cloud. Cloud has to be
manageable, and to do that, you have to be able to set some standards and get those building
blocks together to be offered.
Devraj: One of the things I see, to add to Mark’s point, is that a lot of CIOs look at the
standardization part as something they need to solve before they embark on the cloud journey.
That's one way of doing it. Deﬁnitely, you try to get some standardization in place, applying the
70/30 rule, as Mark alluded to.
But, it is also important to remember that the cloud requires a different set of dynamics, a lot
more pragmatic approach, wherein CIOs need to look at standardization as a process that they
undertake as part of the journey towards the cloud, rather than trying to do it all upfront.
If they take one of their mission-critical applications, that's a natural starting point. They look at,
does this meet the requirement of being able to deliver value within a certain amount of time?
Does it meet the requirement of being very close to the business users, being in high demand,
and a lot of IT work goes into maintaining and managing that application stack. If that’s the right
candidate for moving to the cloud, then they have to decide how do they do that? Having P2V
like capabilities is one option.
The other option is that there are lots of application modernization capabilities that HP and
Stratavia have brought to the table. One of the examples that I'd like to talk about is a lift-and-
shift capability, where you can take a composite application running on a legacy environment
like Sybase, for example. Let's say that Sybase is not part of the cloud implementation. They can
choose to have that Sybase database converted in a fairly lights-out manner to a SQL Server or
an Oracle environment and then launch it into the cloud.
So, there is a little bit of standardization as part of the journey towards the cloud that IT
managers and stakeholders need to look at.
Gardner: You mentioned Stratavia, and for the beneﬁt of our listeners, HP has now acquired
Stratavia, and there was also quite a bit of product and service news on September 15 around
BSA.
Mark, why don’t you give us a recap, before we delve a little bit more into this methodology, and
the crawl, walk, run approach to this that Venkat is getting at. Let's get into the news and then
come to that strategic and technical discussion.
Shoemaker: Several things have happened in the last 30 days. Obviously, we just got back from
VMworld and we presented a cohesive strategy for infrastructure and even PaaS built on the

BladeSystem Matrix hardware platform that we have, Converged Infrastructure. We've combined
that with two other pieces and a piece of Cloud Service Automation (CSA) software.
The other pieces, and it goes back to what Venkat is talking about as the how-to, is a thing we
call CloudStart, which is a consulting and a professional services-led engagement, where we
come in and work with the customer to get that transformation process nailed, so we can quickly
get them moving into the cloud benefits.
On the back end of that, there is another piece that we announced called Cloud Maps, which is
really more knowledge, but in a different capacity, in that it offers downloadable templates,
preconfigured applications, and best practices for sizing.
Cloud is a solution
As you said, if you had an application that you wanted to shift, or lift and shift to cloud, it's our
best practices about sizing and other things around common applications like Outlook, SAP, and
some others, that we are constantly adding to. We see the Stratavia acquisition fueling that fire,
because in the end, cloud is a solution, and a solution needs content, and content wins. Content is
what the customer is able to consume and use day one, when the solution is in. So it's important.
We've done a lot there.
Obviously, the Stratavia acquisition was a huge, huge win for us, and puts us in a great position
to help our customers transform their infrastructure.
Gardner: Mark, you painted a big picture of where these announcements go, but what are some
of the constituent parts?
Shoemaker: We've been really busy over the last two months. We've had significant
announcements at VMworld around the BladeSystem Matrix, where we have now got Converged
Infrastructure and we have embedded the CSA software inside of it, combined that with the best
practices on the front-end, and what you need to get up and running, and then the templates and
the quick start pieces on the backend, to really let you establish a cloud offering quickly.
But, all that sits on a recently refreshed BSA portfolio, with significant enhancements and new
capabilities across network, automations, servers, and storage, that really makes all this happen.
It's really the brains and the heavy lifting of what goes on to manage infrastructure, whether it's
in a cloud or not.
On top of that, we've got a best-in-class content provider in Stratavia that’s come on board to
help round out the capabilities and add more into what the customer can get out of our solutions
in very quick order.
Gardner: Let's delve into that a bit. Venkat, you've come to HP Software & Solutions from
Stratavia. Tell me about Stratavia and what it brings to the table in terms of this larger equation
that Mark just described in terms of a progression towards cloud?

Devraj: Sure, Dana. As Mark mentioned, HP already has a very comprehensive set of
technology platforms within BSA, as well as consulting capacity and educational prowess.
However, the gap that existed was around specific domain knowledge and out-of-the-box content
to manage specific composite application software stacks within the cloud.
These include being able to enable provisioning config management of heterogeneous database
and middleware products, doing things such as code releases, performing maintenance work, and
other functions around these stacks, in self-service and lights-out mode.
At Stratavia, that was precisely the area of focus. We had built a patented technology to manage
and control varied software stacks, such as databases, web servers, application servers, and even
well-known packaged applications, including Microsoft Exchange, Oracle E-Business Suite, and
SAP.
The software used by these enterprises, which are common customers for both Stratavia and HP,
tends to be disparate, heterogeneous, and requires a lot of domain knowledge to be able to
manage them, resulting in significant delays and bottlenecks associated with service delivery.
Those processes just don’t scale in the cloud.
Different platforms
For example, just at the database layer, within the enterprise, it's very common to see four or
five different platforms in use, such as DB2, SQL Server, Oracle, and so on. By automating the
operations management lifecycle around these layers, Stratavia made it possible for the
enterprise to deliver and manage these assets as a service within the context of the cloud. As
more and more of HP’s and Stratavia’s joint customers started seeing value in that capability, HP
brought Stratavia into its BSA/Business Technology Optimization umbrella.
Gardner: Mark, let's pull this back into this notion of being able to get to cloud quickly. IT is
under pressure, and there are new kinds of competition, even competing against other companies
that have had more of a greenfield approach. A startup might be able to get into cloud benefits
much sooner, so there is another element of competition there.
But, to attain these cloud values without risk what is it about the announcements on the 15th that
you think really is sort of the lynchpin to that? I am thinking that CloudStart, being able to
manage as a service, coupled with whatever you have got on premises is part of that, but I would
like to hear what your thoughts are.
Shoemaker: It's really about taking our experience, dealing with numerous customers in this
area, and being able to apply into your IT. So we give them a running start at cloud, rather than
trying to figure out everything.
Face it, a lot of the CIOs are looking at a data center that’s packed full of applications that they
probably don’t feel as if they have got a good handle on. Now, cloud is coming into the picture,

and they've got two things to do here. Number one, they need to start applying those new
business methodologies to IT around providing cloud and the things that go with that, but also
they have got a transformation piece to go along. And that can be very daunting.
What we've done is looked at the experience of helping previous customers do that work and we
have applied that into the CloudStart and Cloud Maps, CloudStart being the planning and the
upfront work that you need to get done.
So, we're right there with you. You don’t have to read chapter one of the book. We can quickly
take the customer through the book of our experiences and best practices, help them get that
plan, start that transformation, and look at the applications that can be pulled over, what needs to
be modernized or what needs to be standardized.
Then, as we put the infrastructure in with CSA for Matrix in the frame, we're embedding some of
the CSA software inside of the Blade Matrix frame. So, you've got a way to build infrastructure
as a service (IaaS) and manage it through the platform throughout the lifecycle.
Then, on the back end of that, we've got the preconfigured application templates. If I need a SQL
Server image to put into the system, I can pull that from Cloud Maps, build it into a framework
and offer that very quickly. I don’t have to go and figure out how to size for this piece or what
golden template looks like for this application.
It's really about a running start into the cloud, and one that’s not going to leave you wanting in a
year or two. You have to be careful. Cloud is a great enablement technology and a lot of people
are looking at IaaS, but that’s the starting point for it, and then you have to manage everything
that you put inside of that as well.
Gardner: Venkat, a similar question to you. What do you feel is the most important aspect or
lynchpin to being able to get to cloud fast, but without it spinning out of control and/or being
able to scale, if in fact you are successful?
Key areas
Devraj: There are a couple of things that become key areas. Number one, you have to be able to
integrate with an existing ecosystem within the enterprise.
Companies have already spent millions and millions of dollars over the last several years on
things like monitoring systems, ticketing systems, metering systems, and service catalogs. So the
technology that they adopt for the cloud cannot be a radical redefinition of these existing assets.
They have to be able to leverage these assets, where it makes sense, and tie them all together.
Number two, the new value that the cloud brings in comes in through out-of-the-box content.
The out-of-the-box content needs to be able to manage and control all the layers of the cloud
stack. The one thing that the cloud doesn’t change dramatically is that in order to deliver IT

services, you still have to do it with network, storage, servers, databases, web servers, and
application servers.
These are the fundamental building blocks and they have to be brought together using out-of-the-
box content, automation content, as well as doing it in a manner where the application language
is presented through a service catalog to the end users. The application that drives the business
has to be the de-facto delivery unit for the cloud.
So both the out-of-the-box content and integration are the two main lynchpin areas in my
opinion.
Gardner: I guess it gives you that opportunity to keep the plane ﬂying while changing the
wings, as it were. So, you can go to a cloud model but you are really using the same technologies
and assets, you are just perhaps abstracting them a little bit.
Devraj: Precisely. The whole content that I talk about becomes an abstraction layer, where the
customer, the end user, the people who consume the services, see a very easy to understand
service catalog. They can click on it. They can choose some menu options, some values from a
drop-down box, and then specify exactly what they need, and have the response come back in
minutes and in hours, rather than days and weeks, as is traditionally the case.
Gardner: Mark, as Executive Program Manager for Cloud, you've been traveling around the
world quite a bit. We're talking about this in sort of a theoretical mode, but how about on the
street? Are there folks who are doing this now? What are their experiences? What sort of
paybacks are they getting, and is the business noticing?
Shoemaker: There's good news on all those fronts. Yes, we're talking with and helping a lot of
our customers start to move into the cloud and move down that path.
I'll be honest with you. A lot of people we talk to are looking at drawing that line in the sand and
creating those new standard services that the business can start to consume, but there are a
couple of things.
Number one, it buys them some breathing room. The business is putting pressure on them to
move into the cloud. The second part is that it lets them get experience on how things work and
how they are going to work inside the cloud, because then it lets them go back, look at their
legacy infrastructure and application portfolio, and try to ﬁgure out how that’s going to transform
over time.
Some things will stay
We've talked about it in previous conversations. Everything doesn’t move into the cloud. Some
things are going to stay in the physical elements. Some things will stay virtual, things that you've
already virtualized and that you really can't standardize.

Then you've got cloud. As Venkat said, everything from the physical, all the way up to the
application, whether it's in the physical infrastructure or the virtual or the cloud, still has to be
managed, every element that you perform today. Compliance, patching, all of the service level
management, being able to barebones provision servers, all of that is still going to occur in the
data center, and we really have to pay attention.
Taking that first step, creating those new services, and building on those for the new applications
that come in does a good job of pulling the rest of it, and lets the IT organization become more
familiar with what it takes and raises their success ratio.
Gardner: Venkat, a similar question to you. For those folks who have already been progressing
in this direction, doing this the proper way, what are some of the paybacks that they get and how
well does both IT and the business benefit?
Devraj: One of the things I am seeing, Dana, is that there is a lot of qualitative analysis being
done in this area. A lot of the customers that I work with are not sure yet what the baseline is for
success in the cloud, given the newness of it and the rapidly changing definition of the cloud. So,
not a lot of people are able to have publishable metrics that they can stand behind and say that
this is the value that they've got.
A lot of them are in a wait and watch, or pilot, mode, and they're doing what I call a micro-cloud
implementation, wherein they take a subset of their environment and do a pilot around a cloud
deployment.
This is the data point that we're seeing. Of course there is a lot more maturity in some retail
environments, for example, financial services, banking, insurance, etc., but a lot of it is wait and
watch and there is a lot of qualitative stuff that’s going around. I'd love to see them apply some
financial discipline and get some quantitative data around it, based on things like their ticketing
system.
In data warehousing, there is a saying that data never lies. That is true with cloud deployments as
well. Enterprises already have a wealth of data in their ticketing system, their incident
management systems, and their change management systems, regarding which applications and
environments are consuming the most IT admin time, which are violating the service level
requirements of end user business teams the most, and which require the most caring and
feeding.
One school of thought that will help them enable more quantitative analysis and measuring ROI
would be to start the deployment with an application that offers the biggest bang for the buck.
They could start reviewing and mining their ticketing system data and choose the environment
that cost the most to deploy and manage and maintain and has the toughest problems related to
service level agreements (SLAs) and get those guys into the cloud.

Another school of thought is all about being risk averse and safe. Start with your least strategic
system and get that into that cloud. If that works, fine. Then, you can start going to better, bigger,
and harder to solve problems.
Either way the data is there
Either way, whichever is the approach that companies can adopt, the data is already is there in
the ticketing systems and incident and change management systems. What is required is some
level of guidance and education for these companies to start tracking this data and approaching
this problem in a quantitative and easy-to-measure approach. Then, we should start seeing a lot
more success stories that come out of the market.
Gardner: That, of course, will build on itself, and we'll see adoption patterns emerge. We look
forward to charting that along the way.
Mark, how do folks get started? Any thoughts about where some resources are, how to educate
yourself and to recognize that this is comprehensive? This isn't necessarily a piece that you plug
in. You really have to think about the strategic and holistic view of doing this?
Shoemaker: This is similar to a lot of the things we have been talking about for the last few
years. Cloud is an evolutionary process for IT. We've been talking about service-oriented
architecture (SOA) and we have been talking a lot to our customers about data center automation
over the last few years. Cloud just builds on that.
A lot of the different methods, no matter what they are, are what we already know inside of IT,
and are what HP has been helping customers with. We've got significant experience and
significant mindshare in workshops that we can help with. From the point of view where, "I don’t
know what cloud is, but I know I need to do something," we've got one-day workshops that can
come in and help educate.
We've got longer engagements that come in and work with our customers to look at their
processes and their level of maturity, along with the complexity in their applications, and help
them build a set of steps that help them move into cloud.
Certainly, with what we've announced, with IaaS, with our rich legacy of data center automation,
which really is what CSA is built on, we have got a history of providing ROI for customers
around this. Cloud builds on that, but adds some challenges. There are a lot fewer human hands
in the middle of it. Cloud’s whole purpose is to run on its own.
You have to make sure you put in place a closed-loop process that’s going to allow you to be
successful without all those hands in the middle of it, because you're not going to be able to keep
up with it. Plus, the customer is your actuation point. They push the button to get this thing
going.

Leveraging the experience that we have, a great investment and the series of workshops we work
with our customers on, being able to pull in the Converged Infrastructure offering, the
transformation technology that we have, applying the cloud experience, and now bringing in the
content maturity that Stratavia brings to the table for us, really just makes this a one-stop shop
for what you need to do to transform.
Gardner: Venkat, last word to you. Given that automation is such a big part of this, what would
you say is sort of an important stepping stone or a bridge to being automated in this and not
stumbling in terms of sprawl or complexity? So, the question is how to be mindful about
automation, as you progress towards these cloud values?
Devraj: The key thing to be mindful of is what are the admins doing today that makes the
environment run like clockwork. If you look at most IT enterprises, most of the people working
there are very hardworking. They do a lot of good things. They do a lot of right things. And, they
do that because of a lot of tribal knowledge that they have in their heads.
So, when you approach automation, one has to be very cognizant of the value that these people
bring to the table. There is a level of education that’s required that tells them not to be threatened.
It's not about job loss when automation comes in, but it's about job improvement.
Big gap
When you talk about improvement, there's a big gap in IT today, which is IT/Ops Engineering
or IT/Ops Architecture. That’s a big missing silo within IT/Ops. And lot of the operators today
that rely on scripts, command-line stuff, and point-and-click tools need to evolve themselves to
more of an architect approach. They need more of taking stock of the big picture, and taking the
tribal knowledge that they have in their heads and looking at the out-of-the-box content that HP
provides and selecting the right content that corresponds to their tribal knowledge.
When they go into the cloud, the underlying management, things like compliance and
governance, are not out of whack. They're able to successfully take that knowledge, put it in
there, and then, in their new role as architects or engineering folks, they're able to watch,
measure, and make modiﬁcations as appropriate.
So, the role that people play, that key subject matter experts play, is very crucial as part of
walking before running with automation.
Gardner: Very good. We've been discussing ﬁnding the path to low-risk, but high-reward cloud-
computing adoption. We have been enjoying the thoughts and leadership from HP’s Software &
Solutions Group. I want to thank our panelists, Mark Shoemaker, Executive Program Manager
for Cloud Computing at the Software & Solutions Group at HP. Thank you, Mark.
Shoemaker: Great, Dana. Thanks so much. I appreciate your time.

Gardner: And also Venkat Devraj. He is the Chief Technology Officer for Application
Automation at HP Software & Solutions. Thank you so much.
Devraj: Dana, Mark, thank you very much. I enjoyed the discussion.
Gardner: This is Dana Gardner, Principal Analyst at Interarbor Solutions. You've been listening
to a sponsored BriefingsDirect podcast. Thanks for listening, and come back next time.
Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Download the transcript. Sponsor:
HP.
Transcript of a sponsored BriefingsDirect podcast on the role of effective management in moving
enterprise applications to the cloud. Copyright Interarbor Solutions, LLC, 2005-2010. All rights
reserved.
You may also be interested in:
• Shoemaker on how HP CSAAids Total Visibility in Services Management Lifecycle for
Cloud Computing
• HP Data Protector, a Case Study on Scale and Completeness for Total Enterprise Data
Backup and Recovery
• HP Shows Benefits from Successful Application Consolidation With Own Massive
Global Supply Chain Project

New Managed Paths to Private Cloud Deployments Allow for Swifter Adoption at Low Risk by More Enterprises

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to New Managed Paths to Private Cloud Deployments Allow for Swifter Adoption at Low Risk by More Enterprises (20)

New Managed Paths to Private Cloud Deployments Allow for Swifter Adoption at Low Risk by More Enterprises