OpenShift is great! Developers can quickly start development on a new project. Just log into the web console, create a new application, select a gear and start coding. When you are done implementing a feature you push to OpenShift and after a few seconds you can admire and share your work with the whole world.
But there is more to consider when working with OpenShift. What if you develop in teams? Usually applications are not directly deployed into production. How can I implement a staging process harnessing the OpenShift Infrastructure? How do I know if my changes passed an Acceptance Test or failed it? How does a test team know which features have been implemented?
The answer to these questions are usually not easy, and every company has implemented their own set of processes to address these problems. Although some Organizations have automated some of their IT Infrastructure, there are still a lot of manual processes and changes involved when it comes down to taking a particular software release from development into production. On the other hand, the business stakeholders have a high interest into a fast and efficient Release process, because every day that my feature is not in production and available to my users, is lowering my ROI. Continue reading →
Like many organizations, Red Hat Consulting constantly seeks ways to eliminate organizational inefficiencies in our business operations. These inefficiencies typically deal with how our consultants are trained on cutting edge technologies, how our sales force demonstrates product capabilities to our customers and prospects, and how our technical groups request operational environments (virtual machines, platforms, etc.)
To attack this problem, a team of architects and consultants set out to design, implement, and operationalize a system that will reduce these inefficiencies. This system is called the Red Hat Innovation Center (RHIC). Its vision is twofold:
1. To demonstrate Red Hat products’ features and capabilities through a solutions-oriented approach based on real world use cases.
2. To enable our consultants to quickly and efficiently learn our technologies by lowering the barriers to entry to internal training. Continue reading →
The post below originally appeared here on November 22, 2012.
A comparison between enterprise IT and public cloud computing dramatically highlights the benefits of moving to cloud.
Application deployment times can shrink from weeks in the traditional data centre to minutes in a cloud data centre; new application development time accelerates from years to weeks (or months at most); cost per virtual machine plummets from dollars to cents; server administrator ratios can explode from 20:1 to 300:1; while efficiency increases, with resource utilisation soaring from 20% to 75%.
With measurable benefits like these, it’s no wonder that IDC expects that by 2015 the majority of the enterprise market will require integrated hybrid cloud management capabilities (Source: IDC Cloud Management Study, 2011 Survey). Continue reading →
It’s a truism that adopting open source software (OSS) reduces costs, but that’s not all. Let’s make a deeper dive into the business value of adopting OSS and uncover how the adoption provides immense value at multiple levels of an organization. The value proposition for OSS can be attributed to three groups within an organization – Technical Buyers, Business Buyers, and Economic Buyers.
Technical buyers can be best described as the line managers who are operating under stringent budgets to do more with fewer resources. As a result they aim to reduce costs and increase efficiencies within their operating units. In a bid to increase their resources utilizations, the technical buyers seek to increase reliability and flexibility in their operations. To achieve these goals they use systems that are reliable, adhere to standard specifications, and low in cost.
The high level of collaboration and contribution within the OSS development model accelerates the number of features that typical open source software provides. Availability of source code allows the adopters to make custom changes and tailor the software for specific needs. The ability to reuse software components across the organization (develop once and use within multiple systems) reduces the unit cost of development. These virtues of OSS mesh well with the goals of technical buyers and make OSS a viable option when making technology decisions. Continue reading →