CloudForms Martyn Taylor, Software Engineer
Overview Red Hat Cloud CloudForms ● Features ● Structure Product v Project ● Architecture ● Realising Features
Red Hat Cloud Offerings
CloudForms “Red Hat CloudForms creates, controls and monitors private and hybrid IaaS clouds, manages infrastructure resources and application life-cycles, all from one central management console.”
CloudForms Leverage Existing Infrastructure Portability Resource Pooling and Reporting Application Compliance Image Management Secured Self-Service
Leverage Existing Infrastructure Build on Existing Infrastructure Create, Manage Private/Hybrid Cloud Manage Public Clouds ● Use existing cloud images, accounts Supports range of technologies Gradual Migration
Portability Multiple Hypervisors Multiple Cloud Providers High Level Image Definition ● Environment ● Applications Build multi-format Images Central Point of Management
Resource Pooling and Reporting Share Resources Control Access Govern Consumption Define Application Deployment Environments Policies around Access and Geography Event Monitoring ● Charge Back ● Usage Analysis
Application Compliance Build, Define Application Environments Continuous Updates ● Content ● Configuration Align Applications and resources together Define multi-tier application deployments Integrate current images, application stacks
Image Management Import Define Templates ● OS, Middleware, Application, Content, Configuration Build multi-format Images Update at build time Multiple builds
Secured Self Service Self Service UI Role Based Access
CloudForms: Structure Cloud Engine ● Cloud Resource Management ● Resource Pools ● Policy ● Workflow ● Access Permissions ● Quotas ● QoS ● Self Service
CloudForms: Structure Application Engine ● Pre-boot ● Template Based Management ● Build, Configure Images ● Multi-tier applications ● Application Life Cycle Management ● Versioning System Engine ● Post-boot ● Continuous Compliance ● Monitor ● Update
Realising CloudForm Features Leverage Existing Infrastructure Portability Secured Self-Service Resource Pooling and Reporting Application Compliance Image Management
Leverage Existing Infrastructure 1.Build on Existing Infrastructure ● hyper-visor support, Image Build Targets ● DC, Factory 2.Create, Manage Private/Hybrids Cloud 3.Manage Public Clouds ● Cloud, hyper-visor Support ● Pools, Accounts, Providers, Image ● Conductor, Factory, DC 4.Use existing cloud images, accounts ● Image Imports ● Factory, Aeolus CLI 5.Evolutionary Migration ● Points 2. 3.
Portability 1.Multiple Hypervisors DC, Factory 2.Multiple Cloud Providers 1.DC, Factory 3.High Level Image Definition 1.Templates, Deployments 1.Katello, Factory 4.Build multi-format Images 1.Oz, Factory, Aeolus CLI 5.Central Point of Management 1.Conductor UI
Secured Self Service Self Service Portal ● Self Service UI, Conductor Control User Access ● Roles, Permissions, Pools ● Conductor
Resource Pooling and Reporting Share Resources ● Pools, Accounts, Providers, Permissions, ● Conductor Control Access ● Permissions, Conductor Govern Consumption ● Resource Quota, Conductor Define Application Deployment Environments ● Templates, Deployments, Katello, Factory, Oz Policies around Access and Geography ● Pools Event Monitoring ● Conductor Events
Application Compliance Build, Define Application Environments ● Katello, Factory Continuous Updates ● Content ● Configuration ● Katello Align Applications and resources together ● Katello, Factory Define multi-tier application deployments ● Katello, Factory, Conductor Integrate current images, application stacks ● Factory Imports
Image Management Import ● Factory Define Templates ● OS, Middleware, Application, Content, Configuration ● Katello Build multi-format Images ● Factory, Oz Update at build time ● Factory, Audrey Multiple builds ● Factory, CLI
Project Roles
Further Reading Build Clouds Without Limits White paper Architectural Overview
Questions?