By Damian Tommasino
The demand for Linux engineers today is growing rapidly with the increase of “cloud” services. More and more organizations want their data to be available everywhere they go with zero downtime to their applications. This kind of demand from organizations requires that engineers know their “stuff” cold. When a web server goes down or a disk fails, you don’t have time to Google for an answer while there is a service outage affecting all of your customers. Becoming Red Hat certified is just one way to set yourself apart when showing potential, or current, employers that you can rise to the challenge.
Red Hat has clearly recognized these types of challenges that engineers and administrators face today when they developed their exams. Instead of the normal Q & A you would expect, these exams are fully hands-on. This lab style exam format helps to set Red Hat apart from other vendors by showing that certified individuals are highly experienced in their roles. For me, having Linux experience is critical to my job and being certified (from multiple vendors) shows expertise to my clients and peers.
The two main Red Hat exams are the Red Hat Certified System Administrator (RHCSA) exam, and the Red Hat Certified Engineer (RHCE) exam. As previously mentioned, each exam is completely hands-on and requires a solid proficiency of Red Hat Enterprise Linux in order to pass. The RHCSA is two and half (2.5) hours long, while the RHCE is two (2) hours.
by Jurgen Hoffman (Red Hat)
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.
by Justin Hayes (Red Hat)
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.
by Malcolm Herbert (Red Hat)
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).