Blip

About this episode

This presentation deals with how to achieve an agile, flexible and automated IT environment based on an example implementation of a private openQRM Cloud for a developer team. Implementing new features and fixing bugs are the two most important tasks for a developer team. While implementing new features always requires adaption to different operating system versions and system architectures also the second work area of fixing bugs needs lots of testing with various custom setups. Lots of time in the development process is misspend just to prepare and provide a powerful testing environment for the developer team. The performance of the test-bed is actually proportional to the quality and robustness of the developed software. The presentation focus on the different aspects of private Cloud Computing with openQRM and how system administrators and especially developers can take advantages of that. Speed up and automate custom provisioning via a private openQRM Cloud keeping a versioned history of specific server-images The openQRM Cloud provides a standardized, flexible and extensible "request system" mechanism to the development and QA teams so they can simple and fast get systems according their needs. Those systems can be fresh and clean, known-to-work testing systems but openQRM provides also the capability to easily exchange snapshots of development-, QA-, or even production-servers during runtime without affecting the origin service. This means e.g. the development and the QA team can deploy a 1-to-1 copy of the production environment as their test-bed and even exchange snapshots of specific servers for sanity checks. Server snapshots in openQRM are also useful for keeping a versioned history of specific server-images to e.g. compare application performance between different versions. Automate Configuration Management fully automated and integrated with existing business processes. The Puppet integration as an additional plugin in openQRM allows further to fully automate the deployment process of the application stack on the requested Cloud Appliances. This programmable configuration layer allows system-administrators, QA and developers to "develop" their IT infra-structure via the well defined puppet-language. Via the openQRM Cloud WebService and SOAP API Aspect 1) can be fully automated and integrated with existing business processes. Furthermore openQRM is designed with a fully plug-able architecture so any third-party component can be integrated easily. you do not need to be a sysadmin to integrate a third-party component you do not need to be a developer to integrate a third-party component ... but it is good to be a bit of both

• Release Date

  Dec 28, 2009

• Runtime

  47:51