BMC Communities Banner
1 2 Previous Next

Cloud Computing

25 Posts


If you're interested in learning more about BMC's Cloud Computing vision, offerings, partnerships, and customers, I'd encourage you to attend one of these two upcoming events.

  • If you're in the Boston area, please join us for a free half-day Cloud Computing seminar, on Feb 3. For details and registration, click here

 

 

  • For those of you in the Public Sector, BMC is hosting a forum specificially for you, with a heavy emphasis on Cloud Computing. This free event is Feb 4 in Washington DC -- for details and registration, click here

 

We hope to see you there, and look forward to speaking with you about Cloud!

| More
0 Comments Permalink

Previously in this thread, we’ve discussed the different styles of cloud computing, mostly from an Enterprise IT perspective (Private Cloud management, Public Cloud usage, and Hybrid Cloud management).  Going beyond these simple labels, an Enterprise’s cloud computing operations are typically a mixture of cloud services of different types, operated in a common fashion.  That is, customers are telling us that, no matter the mixture of cloud service types they’ve chosen to offer, they want an internally (privately) run IT management platform, that’s uniform and consistent across physical, virtual, and cloud service types, independent of whether these services are hosted locally or remotely.


For all types of services, IT (and the business) must also carefully consider which IT services make sense to expose as a cloud service.  Given the general nature of cloud services – codified and exposed in a service catalog, and automatically provisioned and de-provisioned – there are several attributes that would make a service more likely to be viable as a cloud service:

  • Multi-Instance Services
  • Varied workload and scope
  • Easily-Templatized
  • Highly Parallelizable
  • Short lifespan
  • Frequently-requested

 

Examples of such services include

  • Basic OS’s for Development and Testing (the classic infrastructure as a service scenario)
  • Compute-Intensive Activities, such as scientific computation
  • Large-Scale environment for short-term testing, such as scale testing a new web application

 

Conversely, service attributes that wouldn’t make much sense to expose as cloud services include:

  • Single-Instance Services
  • Static systems with stable loads
  • Services requiring a lot of customization
  • Services with a long lifespan

Examples include ERP systems, directory services, and complex applications that require heavy customization unique to each instance.

 

What types of IT or business services are you considering moving to a cloud environment? Why? What attributes do they have that drive you to turn them into Cloud services?

| More
0 Comments Permalink

 

Ah, Lego®: a toy that has captivated kids of all ages, and across generations.  With its assortment of colors, sizes and fun accessories like windows and people, there was no limit to what one could do with a bucket of Lego® pieces and an aptitude for mechanical engineering.

 

 

I personally loved building houses, complete with rooms and furniture, with mine.  One of the coolest things about these blocks, I thought, was that, regardless of the function of each piece, they all snapped onto one another by adhering to a standard design on top and bottom.  Additionally wonderful was that, any time I needed one of those really long pieces but had run out, I could easily use a couple of shorter ones to achieve the same effect.  In the end, multiple combinations could achieve the same result – a beautiful example of fine Lego® architecture.

 

 

So, what does this have to do with the cloud?  Well, like the Lego® product, in an ideal cloud you will be able to easily fit its pieces together.  Whether dropping in monitoring and alerts, or provisioning and deploy, each piece should have a common way of fitting in with the others.  A solution like BMC BSM for Cloud Computing™ is a great example of component parts coming together easily and seamlessly.

 

 

Also, think of the managed services within the cloud.  Much like sitting ten kids in a room and asking each one to build a Lego® house, the details of a service such as “New Production Server” could look completely different from one enterprise to another, one business unit to another, even one administrator to another.  But the flexibility to use the equivalent of any length, color or type of building block to deliver the service should also exist in a cloud solution.

 

 

And of course – let’s now consider Phurnace, a very exciting acquisition and a really cool product.  Where do they fit in?  Requirements for Java application deploy exist across every organization, but few products on the market can manage the automation and administration of this process, and Phurnace is one that does it superbly.  In the world of Lego®, this is more than just a simple building block.  This is akin to when they added electricity to their sets.  Suddenly, cars drove, trains steamed, and – voila! – lights turned on in the houses.

 

 

With a strong cloud management solution already in place, BMC is capable of delivering even more powerful products with the Phurnace acquisition.  We’ll electrify the cloud!

 

 

In the meantime, as for myself…I’m going to Legoland®. 

| More
0 Comments Permalink

 

In many cases, true integrated and process driven release management has been ignored and disguised as change management. However, release management is not change management. ITIL® Release management, centers on the tasks and processes involved in releasing new/modified software to the live environment, whereas change management is an overall process that controls and validates the business case of all changes to the IT infrastructure. The release management process includes quality control, roll-out planning, distribution and installation, communicating and managing user expectations regarding the release. A software release is categorized as a major, minor or emergency release.

As you can tell release management is a fairly complex process. Made worse by the DNA of an application which could be a mishmash of distributed web services, operating elements, data and presentation layers. Throw in to the mix rolling development processes such as Agile and it is no wonder that in any environment, including a virtualized one, application deployment errors can cause
subsequent loss of quality of service to the business affecting the end users. Maybe this complexity is what has led to so many organizations struggling with how to resolve the problem and some have attempted to Band-Aid the problem with manual processes and scripting which is hardly an effective solution. It is a significant problem and one that can now be addressed through effective Data Center Automation.

 

This week BMC Software announced it has acquired privately held Phurnace Software, a leading developer of automation software that significantly reduces the cost, complexity and risk to deploy and configure Java-based applications on physical, virtual and cloud environments.

 

As BMC BladeLogic Application Release Automation, BMC’s solution will fully automate the application deployment process to streamline implementations, reduce the risk of errors and help customers avoid downtime and outages traditionally associated with manual or script-based processes. This will provide rapid full-stack provisioning and compliance of all infrastructure layers, including the operating system, patches, middleware and applications significantly increasing the ability of rapid application development deployment release cycles often seen from Agile development.

 

Ronni Colville, vice president and distinguished analyst at Gartner, Inc. said, “The increased frequency and criticality of application deployments and changes make it difficult and costly for IT organizations to rely on manual change and deployment processes. Organizations need to embrace an automated application release solution to ensure efficient, repeatable, accurate and reliable application deployments.

 

With applications now increasingly transparent and mobile between multiple delivery platforms including the Cloud, a more robust, integrated, and automated solution for Application Release Management must be sought and blended with the ITIL process of release management. Doing so will go a long way to improve business continuity.

 

By adopting a strong release management process, and ensuring that BMC BladeLogic Application Release Automation is part of the overall solution, the application layer as the next frontier in data center automation is finally conquered.

| More
0 Comments Permalink

 

At 3:30 this morning, as I fed my ten-day-old son and dreamt of lost sleep, it occurred to me that managing a cloud can be compared to managing an infant.  Mind you, I’m not making a direct link between infantile behavior and those who work in a data center, but having experienced firsthand what it takes to roll out a private cloud, the process is much like the care of a new child. 

 

 

With newborns, the life of parents can be bewildering and even a bit cruel on the psyche.  There are a lot of requirements streaming in and, for the uninitiated, a big learning curve.  And if you fail to satisfy the demands of your progeny, a lot of screaming and general fussing ensues.  But, after some time goes by, parents learn enough about the needs and moods of their child to begin to anticipate those needs and moods.  And, by using this quintessentially human capability, we can begin to take steps to minimize the crying and sleepless nights.

 

 

But, in a cloud environment, it is software and not always people who must learn the personality of their charges – servers, applications, storage, and so on.  The raising of a cloud requires IT solutions to mimic the anticipatory function of man, and to translate this into an action or a resolution that makes sense for the environment. 

 

 

So, why is this important?  Imagine an environment with a distributed application that periodically dips in performance or even causes a crash due to heavy load.  Without analytics, your cloud is like a thermostat, responding to events that have already occurred like a dip in temperature prompts the heat to turn on.  You don’t actually avoid the performance hit.  Now consider what you could achieve if your system were proactive instead of reactive?  What if it could look at environmental data over time and begin to predict that the resource overload would happen at particular times of the day, or in particular components of the application, and then take steps to provide more capacity at those specific points to preempt the problem?

 

 

The ideal cloud is self-governing and efficiently automated, which is not possible without anticipation.  In fact, managing a cloud is a lot like managing many other things for which anticipation is a key ingredient for success.  Like an excellent butler, or iTunes Genius, or even Furby – that chattering relic of toys gone by – a cloud management solution must learn from its surroundings and become smarter over time so that its capability for anticipating the needs of the cloud environment is real-time.

 

 

Any cloud management solution, therefore, should include strong analytics with ability to correlate historical data with future events.  If you’re working toward true autonomy in the cloud, predictive, or anticipatory, capability of such a tool will soothe even the most fussy of clouds.

 

| More
0 Comments Permalink

As you may have seen, today BMC announced the acquisition of Phurnace Software.  I won’t duplicate the press release details here, but I do want to publicly welcome Phurnace to BMC, and to express my enthusiasm for this new addition to the BMC portfolio.


Using the Phurnace product, enterprises can dramatically improve the speed, quality, and reliability of their Java EE application deployments. With the integration of these capabilities into the BMC family, organizations will be able to deploy a full-stack service – OS, middleware, and applications – in an automated fashion, driven and constrained by IT policies. As it turns out (completely coincidentally, I must say!), these are exactly the capabilities that organizations need to dynamically provision their services (applications) onto the cloud.


Stay tuned here, as we continue to explain and explore dynamic application provisioning, and how it’s an important attribute of effectively using a Cloud.  And Happy New Year.

| More
0 Comments Permalink

 

Now we have turned the corner to a new decade are we finally going to see increased evaluation and subsequent adoption of cloud computing? I think so. I firmly believe that this will be the year that the CIO will become the Cloud entrepreneur as he or she finally gets to grip with the fundamental technologies and business cases, and to address the outstanding challenges that have held them back from cloud implementations for the last 24 months. From what was thought of as being overhyped and even had some naysayers even calling it a fad, cloud computing is now being taken quite seriously and certainly going to prevail as the next evolution in IT computing.

 

We have seen a number of enterprise IT organizations start with limited evaluation and small deployments of both cloud use cases and the technologies required to manage and deploy them. Several key items are still outstanding and require resolutions before mainstream adoption will be garnished. Specifically the majority of these relate to the Public cloud type and centers around security, sizing, chargeback, application performance, software licensing and a few others. Overtime, as with any challenge, these will be overcome.

 

But for many enterprises, safety today comes from building out their own Private cloud type which is still transforming internal IT  with its automating and dynamic provisioning of catalogued and scalable end-user services. This will help transform an IT department into more service-centric and service-enabled organization. Building internal (Private) clouds will help companies obtain highly virtualized, on-demand services delivered in a seamless way. One where the customer, not IT, places the business need and priority decision.

Whatever unfolds for the CIO in 2010 it will mark an exciting and interesting time as they continue to balance a fragile budget, a bruised business from the economic situation, the stabilization and management of IT and the embracing of Cloud Computing to create an entrepreneurial atmosphere within IT to either do more with less, or to do more with the right strategic investments. During our lingering economic challenge, visionary CIO’s will rise to the top as they adopt a Cloud focus. After that, it won't be long before CIOs are serving as cloud computing entrepreneurs to their business.

 

Is this the year of the CIO Entrepreneur in the Cloud? What do you think?

| More
0 Comments Permalink

We, as an industry, have appeared to have reached consensus on a generally accepted classification scheme for public cloud offerings – namely Infrastructure-as-a-Service (Iaas), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS).  (Note how we avoided the unfortunate acronym that would have resulted from Application-as-a-Service!)

 

I won’t define these terms here, as there are many, many resources on the web that do so, and we can safely assume an at least basic familiarity with them. But I will briefly explore how these can relate to an internal cloud environment. First, let’s consider IaaS – in this scenario,  the provider delivers “just an Operating System” to the customer.  The customer is responsible for configuring, installing, patching, and managing the OS. In many (but clearly not all) respects, this is no different from remotely logging in to a physical server down the halls (which is precisely the point).

 

For PaaS, customers see a much more abstracted view – essentially just a runtime container into which they can deploy their applications. Without direct access to the OS, their control (read: ability to cause problems) is much more limited – they can do what they need to do, to deploy and configure their application, but no more.

 

Then, of course, there is SaaS, which is simply an application remotely hosted, and delivered over the web --  Salesforce.com and gmail are two examples of this type of service. Note that we can consider many services that have traditionally been locally hosted  by an organization’s IT dept as SaaS – for example, webmail or collaboration software such as Sharepoint.

 

I’m exploring these here in order to spark a conversation about how they might be applied to our internal IT environments.  Specifically,  as we think about the types of cloud services that we should offer to our internal customers, these three classifications are useful.  What types of services do we offer, and which category do they fall into?  More importantly, are we delivering services in the wrong way? That is, is there an opportunity for us to move up this stack, and deliver more value to our customers?


For example, consider a QA team that uses our IT resources to provision Linux VMs, on which they then install JBoss, for testing of an internally developed application.  Why not, rather than provisioning them just a plain vanilla Linux OS, instead define a consistent template that combines a preconfigured Linux OS with a preinstalled JBoss web app server? This can help IT ensure consistency, reduce the number of moving parts, and in fact make the QA team more productive.  Using this approach will also help improve communication between IT and the apps team, since the OS and app server template will be jointly defined and tweaked – ensuring consistency through QA, staging, and production.


Think about this as you design your service portfolio, deciding which services to offer to your internal customers of your cloud environment, and at which level they could be best exposed.

| More
0 Comments Permalink

·       

·        

·       

·        

·        

·        

·        

 

 

 

 

 

| More
0 Comments Permalink

The Origins of Cloud?

Posted by Meghan Stabler Dec 8, 2009

I've been asked many times whether Cloud is a new technology. Rather than 'new' I feel that it is a coupling factor of several areas (not all listed here):

 

  • basic advancement in technology (think Moore's law)
  • evolution in grid, virtualization, networking, storage, telecommunication
  • the massive globalization of the internet
  • current economic challenges to reduce cost (OpEx and CapEx)
  • required agility of IT to real-time deliver services
  • maturity of processes, automation and integration
  • evolution of dynamic resource delivery, consumption and pricing

 

Yet it is also more than that. If we go back to the 70's and 80's, and I can date myself here, even then we were virtualizing resources with OS/VS1, MVS/SP and IBM VM operating systems. We were using one physical "blue iron" mainframe, but running multiple 'virtual' operating systems to provide services to our respective lines of business. Go even further back to the 60's and 70's and we (well others as I was a tad young back then) had something called 'Timesharing'. It was the same basic idea, large scale computers professionally  managed and operated, accessed via cheap devices over telecommunications.

 

Then last week, while on a flight to the west coast, (using WiFi at 35,000 ft - thank you American Airlines), I was reading Nick Carr's 'Rough Type' blog (http://www.roughtype.com/archives/2009/11/cloud_computing_1.php) and specifically an article where he references the supposed first  published evidence of the concept of cloud computing, http://www.governmentattic.org/2docs/WesternUnionStrategicPlans_1965.pdf dated March 30, 1965 which outlines a  Western Union executive's ambitious plan to create "a nationwide information  utility, which will enable subscribers to obtain, economically, efficiently,  immediately, the required information flow to facilitate the conduct of business  and other affairs." Western Union invented cloud computing. One small snippet within the document states, "Just as a number of local or regional  companies provide both electricity and gas, independent telephone companies  would be encouraged to provide both telephone and information utility services  in their respective territories".

 

The idea of a "computing utility" was much discussed in the 1960s, but this  document nonetheless provides an interesting historical optic of what we now call  cloud computing. However, it was a vision with a yet to be invented set of IT technologies that we have available to us now. Much like visions that man would one day walk on the moon, it was only when advancements and the evolution of technology matured and collided did we end up with the set of capabilities that cloud computing is offering us today.

 

I am sure that I am missing a number of other major observations in the history of computing that has advanced us to where we are today with the cloud. If you have them, please share them here!

| More
0 Comments Permalink

Recall in our previous posting, we introduced the notion of an Enterprise Cloud, comprised of a combination of private, public, and hybrid cloud services.  Many enterprises will want to exclusively offer private services (meaning they are operating, by definition, a “private cloud”) for a variety of reasons (a topic of a future posting in this series).  However, more realistically, and more commonly  moving forward, IT will need to manage all three types of services.

 

Thus, the question is that of how IT wants to approach the design and management of the mixture of cloud services in its environment – whether the service types are blended together in a single cloud offering, or separated.  There is no single right answer to this, as it’s entirely dependent on the organization’s priorities, infrastructure, needs, and context.  Nonetheless, it’s clear to me that there’s a need and a demand for an overall management  platform that can handle all three variety of services in a unified fashion.

 

For example,  imagine that you’re a developer who needs a server OS temporarily provisioned for some development work. You make the request, and a few minutes later you have a new VM, which you access across the network via some sort of remote login. Does it *really* matter where that VM physically resides?  Much of the time, it doesn’t…it can just as easily and productively be in a remote cloud as in the server room down the hall.  That is, the policies and factors that determine where this particular VM is provisioned should be embedded in and executed by the management platform, which can make the best placement decision at the time of request.  There would need to be a compelling reason to instead have the requester make this decision, by explicitly choosing which cloud platform to use.

 

A related question, applicable to organizations operating only private cloud services, is whether to manage one cloud environment, or have distinct cloud infrastructures to serve different purposes. The answer is that there is no single answer…people will need to balance their technical and business needs with the financial, technical, and organizational constraints, and make an informed decision that’s right for them.  Nevertheless, I think that many organizations will want the option of managing disparate service types, as well as all their clouds, from a common management platform.  Even if an organization is running multiple, distinct private clouds, it makes sense to embrace a common management platform, to leverage shared policies, processes, and people.

 

Our next topic in this series – using external Cloud Service Provider offering definitions as a model for internal cloud service types.

| More
0 Comments Permalink

A Bad Cloud, eh?  What in the world is a Bad Cloud?  How can I avoid one, if they even exist?  And for that matter, that brings me back to the original question – Is there such a thing as a Bad Cloud?

 

In a nutshell?  Yes.

 

But before we answer the other questions as to what is a Bad Cloud and how to avoid one, let’s give some background behind how a Bad Cloud forms.

 

Cloud often means different things to different companies.  However, most commonly across progressive organizations, the term describes a visible and executive-sponsored initiative.  If a project is part of a cloud initiative, then it probably also has a better chance of being funded than other projects in the IT realm.  Sure, this isn’t always true, but the point I’m making here is that the positive power of cloud is significant. 

 

Part of the reason that cloud projects are so popular is simply because buyers are ready to implement clouds, and therefore to build or buy cloud-focused products.  The strong support for cloud is also influenced by the sheer hype around the topic that exists in the industry.  Yet another factor is because it is the most commonly understood concept that unifies many of the solutions that companies have been developing across the Enterprise for years.  And, the list goes on…

 

Cloud is exciting. Cloud is the Cool Nerd in a teen movie. Cloud reeks of innovation and the cutting edge. But the cloud boost factor (the appeal attributed to cloud for the aforementioned reasons) sometimes causes otherwise intelligent decision makers to make poor choices, and that’s when a Bad Cloud rolls in.

 

A Bad Cloud can be the result of something as simple as rushing to implement a private cloud without understanding the proper controls of that environment. For example, no change management or tracking of virtual machine provisioning can cause the underlying virtual infrastructure to grow unchecked (commonly known as sprawl).

 

Luckily, such a situation can be easily remedied with the proper tools and processes put into place. However, a Bad Cloud can also be represented by a poorly formed cloud strategy that encourages employees to use public clouds for any short-term projects and/or to aggressively try new ideas in the public cloud. Such unbridled enthusiasm without foresight can unintentionally cause placement of confidential data – like customer credit card numbers or employee Social Security numbers – into a public cloud.

 

So, what can you do to avoid a Bad Cloud?  Like with all major decisions, use common sense – think through what are your core needs and stick to addressing those first. Use industry leaders and market sources to help you understand where are the pitfalls. And purchase the right products and solutions – ones that will not only add automated execution to your cloud environment, but also the right governance and controls to keep your good cloud from going bad.

| More
0 Comments Permalink

Living in New England, we are blessed with a large variety of ice cream shops, offering a sometimes bewildering selection of flavors – regional selections such as Moose Tracks and Cranberry Bog, or, if we’re at Christina’s in Cambridge, more interesting flavors such as Ginger, Corn, or Kaffir Lime.  But, the old standbys of vanilla, chocolate, and strawberry still outsell all others. Faced with the difficult choice between these three flavors, Neapolitan ice cream was invented in the late 1800’s – a single container with sections of vanilla, chocolate, and strawberry.  Properly dispensed, each serving contains a portion of each flavor. Delicious!

 

Speaking about Cloud with so many different people from different organizations, backgrounds, and perspectives, I often discuss the different styles of cloud computing, and categorize them as Private, Public, and Hybrid.  But, much like our ice cream, we shouldn’t necessarily think of this an either/or choice.  When an organization envisions what sort of services it wants to run in a cloud, and how they want to manage it, it turns out that reality is complex.  A given enterprise’s cloud is likely to have a wide variety of services, and these services will be private, hybrid, or public.  That is,  we need to think about these as private cloud services, hybrid cloud services, and public cloud services – all of which are services offered by IT within an enterprise’s cloud, with different characteristics.
That is:

  • A private cloud service is a service that runs entirely on the organization’s own infrastructure
  • A hybrid cloud service is a service that runs partially on the organization’s own infrastructure, and partially on an external service provider – typically for handling peak “overflow” work loads
  • A public cloud service is a service running entirely on an external service provider

 

(An interesting sidebar is that these distinctions, while highly important for IT, should actually be transparent to the internal customer. If I obtain a service from IT, it shouldn’t really matter to me where it runs, as long as it works, and meets the SLAs).

 

Typically, IT wants to expose all these styles of services through a single, common request management interface, with standard and common policies, processes, and tools.   That is, a single management layer operating multiple service infrastructures, acting as a single platform with all three service flavors deployed together.  Implemented properly, this can be as appealing to the organization as a dish of the aforementioned Neapolitan ice cream (although not quite as refreshing).

 

Note that I say IT typically wants a single, common management platform, because there are valid considerations and situations where IT would want or need to run operate multiple clouds, separate and distinct from one another. That discussion, One Cloud or Many, is the topic of my next posting in this series.

| More
0 Comments Permalink

In the years that I have focused specifically on Product Management for virtualization management in the data center, I have seen a distinct shift in how our customers speak about their needs with regard to virtualization.  Three years ago, during product strategy discussions or development validation meetings, we talked about things like whether to implement VMware technology, how to execute technical administration in a UNIX virtualization environment and about the joie de vivre gained from successfully automating the management of basic virtualized resources.

 

Our customers still talk about the components that they manage – the data center elements and building blocks of virtualization technology.  And, just as at the beginning of the Virtualization Boom, these components are still directly within the IT department’s control, as well as serve as the foundation for our own automation products.  When I am called upon to whiteboard a particular product or solution, I often draw this relationship as a neatly-boxed layer labeled “Virtualized Infrastructure in the Data Center” sitting underneath a group of stick figures labeled “IT Department.”  A bit generalized, to be sure, but – 1) the simplicity helps audiences at all levels to quickly get on the same page and 2) I’ve always been a terrible artist.

 

However, the push toward cloud and self-service in virtualized environments has influenced the Data Center Automation Zeitgeist.  Today, the spirit has changed such that the IT users with whom I speak are no longer just sitting atop a rectangle of data center infrastructure.  Cloud has added a layer overhead (pun not intended, but it’s a nice bonus).

 

That layer contains the components of the business, or Business Services.  These are the elements that end users* within an organization understand and to which they have direct access, whether or not they ultimately control the resources behind those Business Services.  In the new version of the aforementioned drawing, the IT team is now sandwiched between the data center elements below them and the Business Services above them.  So today, when I speak with our customers about automating their virtualized world, we do not focus solely on the technical language of their IT domain; rather; we also speak in the end user language of Business Services.

 

IT departments have become, in effect, bilingual.

 

That’s why, as the discussion with our customers has taken on another tongue, so too have BMC’s products evolved to speak both Data Center and Business Services languages.  Forget about “Que Será, Será.”  The future is ours to see, and implementing a solution that does not handle the translation between business and data center will place a heavier onus on the IT department to serve in additional capacity as a dictionary, which can often take time and focus away from both efficiently administering the infrastructure and delivering useable services to the business – in distinct opposition to what cloud represents.

 

* I was tempted to label the end users as, “Vox populi,” but that would just be a shameless attempt to squeeze in yet another foreign language.

| More
0 Comments Permalink

Organizations around the world and in every industry are using BMC’s BSM unified platform to reduce the cost of running IT, increase business impact, improve quality of service, manage risk, and provide transparency to business stakeholders.

 

Since launching the first comprehensive vision of BSM, BMC has been a driving force in the adoption of today’s IT management standard. Last week BMC took the next big step forward in the future of enterprise IT management with the introduction of Dynamic BSM. Dynamic BSM is the next evolution of BMC's management architecture where the goal is to not only address the core requirements of IT management but also support the on-demand provisioning and management of services that leverage new computing platforms, such as virtualization and cloud computing infrastructures.

 

Consequently, Dynamic BSM leverages the strengths in BMC's BSM platform while enabling customers to deploy and manage a more agile, responsive and efficient IT computing environment. As Forrester research recently noted, BMC has successfully positioned itself as the thought leader in IT management software. It was also stated that our alliances with firms such as Cisco, Dell, and VMWare position BMC as the most valuable player in IT management software.

 

One of the keys to our ESM strategy and to our success is our continued ability to anticipate changes in the technology landscape and to capitalize on areas of higher growth potential. This includes extending our BSM offerings to virtualization and cloud computing environments.

 

While customers will aggressively explore these new computing paradigms, it is important to understand that they will retain significant parts of their existing computing environment. As a result, BMC's distinct competitive advantage is to provide customers the ability to seamlessly manage their heterogeneous physical, virtual, and cloud computing environments with one comprehensive management platform.

 

Large organizations that are considering moving applications and infrastructure to a cloud environment must first implement and address the management challenges of highly virtualized IT infrastructures. In a highly virtualized environment, the management challenge is exacerbated on two fronts -- one, there is a dramatic increase in the rate of change for both applications and the underlying infrastructure, and two, there is far more complexity associated with the configurations of those virtualized infrastructures.

 

BMC’s BSM platform delivers a proven and service-centric approach to the deployment and ongoing management of virtualization technology. With new capabilities that address virtual life cycle management, essentially the ability to manage the creation, ongoing use, and decommissioning of virtual machines, as well as performance and compliance management of virtual machines, our customers can rapidly take control of their virtual infrastructures.

 

BMC's BSM for Cloud Computing™ and BSM for Virtualization™ help customers enable cloud computing environments and harness the power of virtualization and at their own pace. With capabilities that address virtual life cycle, performance and compliance management, BMC customers can rapidly take control of their virtualized infrastructures.

 

The attraction to cloud computing, including both private, hybrid and public cloud environments is powerful, particularly in today’s cost-sensitive, service-oriented IT organization. BMC is already helping enterprise customers and service providers realize this potential.

| More
1 Comments Permalink
1 2 Previous Next