by Christian Stankowic
My interest in Linux started in 2005 at the age of 15 when I discovered Ubuntu Linux. After being upset about my slow and always virus-attacked computer, I decided to try out something completely new.
I never had Linux on my computer before and wanted to have a look at it. After some first trials with OpenSuSE I got into Ubuntu and made my first experiences with the open operating system.
After exclusively using Ubuntu for almost two years I had a look at several other distros, including Debian, CentOS and Fedora. To learn more about Linux I built my own private “lab” using old spare computers. All these computers ran Linux, so I started to learn about network services including Apache, DHCP and Samba.
Continue reading “Guest Post: Journey to RHCE and beyond”
by David Kang (Red Hat)
Cloud is not software, cloud is not hardware, cloud is not virtualization, and cloud is certainly not a panacea for broken IT. Cloud is an architecture: a set of fundamental tenets that have different implications at different levels of IT, from network, to hardware, to applications, and to the IT process itself. To say you have a cloud is to say that you have a cohesive architecture, technology set, and most importantly processes, that work towards a defined goal under a set of well-understood principals. Building your cloud is as much about defining your goals and governing principals as it is about investing in technology.
Building your cloud and consuming cloud services
Step one is defining your governing principals. This is a crucial step before embarking on your cloud journey as the policies and principals you define will help you navigate your journey through the rapidly expanding cloud ecosystem. This is also an opportunity to ask tough questions and examine what your principals and processes are, and why you have them. Process is ultimately about managing risk, so consider what risks are acceptable under your governance policies and weigh them against the potential benefits cloud can offer. Both Facebook and Google have adopted “deploy to production” models that seem to fly in the face of process conventions such as ITIL or RUP, yet somehow they seem to survive. The penalty for not doing this exercise is ballooning adoption costs, or failed rollouts all together.
Continue reading “Cloud Sniff Test: Cutting through the jargon”