Open standards in the cloud benefit everyone and can dramatically reduce the
time it takes to move between public and private clouds, to deploy software and
to implement complex application topologies.
IBM is working with independent software vendors (ISVs) and the OASIS
Topology and Orchestration Specification for Cloud Applications (TOSCA) working group to define and deliver
standards for pattern definition. More information can be found here.
At IBM Pulse this year, we hosted the Open
Cloud Summit, where leaders in the cloud standards community from IBM and
other vendors presented on the importance of standards for successful cloud
deployments. The summit also featured a TOSCA demonstration that highlighted
TOSCA implementations by IBM, SAP and others. IBM also had a pedestal in the
solutions expo further promoting and informing attendees of the ongoing
standards work.
In the IBM PureApplication System we are already working with other
vendors like SAP to deliver on the promise of open standards and portability in
the cloud. Pattern definition standards benefit implementers and customers
alike. They allow customers to easily move from private clouds to public clouds,
and allow for a level of abstraction above the underlying deployment,
provisioning and orchestration technologies.
Taking complex distributed business applications and delivering deployment
patterns that are executable out of the box helps customers get immediate value
from their packaged software purchases. This IBM PureApplication System case
study cites a 47 percent reduction in labor costs for software deployment,
and in many cases steps are eliminated—freeing up resources who used to spend
time provisioning virtual servers, configuring monitoring and backup software,
installing and patching base operating systems, infrastructure and middleware
software, and installing application software.
It’s not just about money either. Take any application that needs a few
environments, such as production, test, development and so on. The traditional
deployment models have either been three separate installation processes, or
taking snapshots of images and re-configuring them. So either we have three
different installations or three versions of the same error—or by luck
everything works out perfectly. Taking into consideration a large application
like SAP, where runbooks can be hundreds of pages of manual steps, you can start
to understand how automation based on patterns developed by the experts who
wrote the application can deliver huge productivity improvements and ongoing
operational efficiencies.
There is no question that this is the future of software deployment, and all
organizations should be taking a close look at how much time and money they can
save in this type of environment. As standards evolve and more vendors adopt
them, customers will benefit from both efficiencies and portability across
public and private clouds, as well as solutions like the IBM PureApplication
System. All enterprise and infrastructure architects should be taking a close
look at these standards.
By:
Aucun commentaire:
Enregistrer un commentaire