Many large organizations are implementing private clouds to enable on-demand network access to a shared pool of computing resources they can easily and quickly configure and provide. Although the main focus of cloud computing has been on the distributed infrastructure, organizations have learned that the zEnterprise also works well for implementing private cloud using Platform as a Service (PaaS).
Learn how your organization can benefit from implementing a development/test (dev/test) private cloud using PaaS with Linux on System z and why WebSphere Application Server (WAS) may be a perfect fit for a dev/test private cloud.
Private Cloud Initiatives
Customers have begun moving beyond the market hype of private clouds to pilot and mainstream deployments, and studies show that 2013 promises to be a year of many new private cloud production deployments.
Worldwide private IT cloud infrastructure investments will grow to $18.9 billion by 2015, with a Compound Annual Growth Rate (CAGR) of 25.7 percent, according to an IDC market analysis report (see www.marketresearch.com/IDC-v2477/Worldwide-Private-Public-Cloud-Infrastructure-6797018/).
A December 2012 Gartner poll shows that private cloud project deployments will increase significantly in 2013. Nearly 90 percent of customers are looking at private cloud implementation and are either in the planning or early deployment stages (see Figure 1).
In a recent CA survey, more than half of both U.S. and global respondents say they believe the mainframe is or will be a highly strategic platform in their cloud computing efforts (see www.ca.com/us/news/Press-Releases/na/2012/CA-Technologies-Survey-Finds-Mainframe-to-Drive-Innovation.aspx).
Why Consider a Dev/Test Private Cloud?
If your organization needs to cut IT costs and is looking for “self-service” for developers, then a dev/test private cloud could be the answer.
Setting up a new environment involves procuring and configuring hardware, installing the operating system, installing and configuring middleware and loading your applications on the system software stack. Given this complexity and long lead time, there’s a strong incentive to keep the old environments around just in case, rather than releasing resources when no longer in use. This type of usage model quickly consumes hardware resources, even though many application-serving environments aren’t being used actively. This usage model is inefficient and costly. Cloudtimes.org recently noted that 70 percent of the conventional IT budget is spent on keeping idle servers turned on (see http://cloudtimes.org/2012/10/18/private-cloud-funding-model-challenges/).
Using a dev/test private cloud with virtualization enables fast setup and consistent resource management. With this approach, developers can obtain IT resources on demand, releasing them when no longer in use. Since they no longer need to wait days or weeks to do the testing, productivity and time to market can be improved greatly while hardware and software charges are reduced.