140 likes | 231 Views
Enterprise Application Stores. Tuesday, February 21, 2012. Primary use cases. On boarding Migrate existing applications to cloud Fastest, most cost effective, systematic way to get on a cloud Hybrid/Federated Continuous and incremental “On boarding ” Cloud bursting No lock-in
E N D
Enterprise Application Stores Tuesday, February 21, 2012
Primary use cases On boarding Migrate existing applications to cloud Fastest, most cost effective, systematic way to get on a cloud Hybrid/Federated Continuous and incremental “On boarding” Cloud bursting No lock-in Cloud protection: instance, region, vendor Enterprise App Store Dynamic catalog image assembly Linear vs. exponential image management ISV distribution Pre-installed, pre-configured software distribution Fastest time to deployment Reusable demo/poc, pre-configured implementations
Enterprise App Stores Dynamic catalog image assembly VMsprawl is a bigger problem than server sprawl Cloud scale is all about automation Self service is a foundational theme
What’s the root problem an EAS is addressing? The cloud industry’s current approach to ecosystem mgmt adds no value to published components and lacks the concept of “bundles” Large scrolling list of 800+ images is overwhelming AND …. customers don’t use single components - they build complete stacks
OS A 32bit OS A 64bit OS B 32bit OS B 64bit Partner A Partner B Partner C Partner D Image Sprawl • Imagine a simple, early, ecosystem use-case • 2 Certified Operating Systems • 1 Foundational element say JBoss • 3 partner offerings, which a customer might use on their own or integrated into a WebSphere stack • Operating System • Need to cover 32 and 64 bit • Only 1 release at the moment, what happens when new release of OS? • Partner Products • Customers might want up to 12 different combinations of these items • What happens as the number of partners grows?
OS A 32bit OS A 64bit OS B 32bit OS B 64bit Partner A Partner B Partner C Partner D Sprawl the result of pre-built images?
OS A 32bit OS A 64bit OS B 32bit OS B 64bit Partner A Partner B Partner C Partner D Our example requires 48 images What about different version, hypervisor, cloud vectors
Image Catalog Presentation Monitoring App Server Windows App logic Security Messaging Linux Data Tables Storage Database Workflow Solaris Backup Process Workload Owner : App Dev, DBA Middleware Owner : Infrastructure, DBA Base Owner : Infrastructure OS Owner : Sys Admin Deployment Biz Logic UI Database
Frictionless dynamic composition Dynamic composition None
How the enterprise consumes applications • Use cases: • Cloud catalog - Dynamic composition OS+Mgmt+Srvs+App • Telcos services offering for SMB or Public • Apps operations offering for company function – F&A, Dev, Sales • Streamlined ISV delivery • Flexible, loosely coupled set of components: • Purpose fronted – Store canvas or front end • Repository/Catalog – Where images/apps are stored • Provisioning engine – Life cycle manager • Operational stacks – Where the apps run i.e. Cloud
Enterprise App Store (EAS) Automation Operational Stacks
Enterprise App Store (EAS) Dynamic catalog image assembly • CloudSprawl is a bigger problem than server sprawl or VMsprawl • Simplified mage selection • Self-service, on-demand provisioning of server apps • No cloud lock-in • Operational efficiency at cloud scale • Standardize and automate configurations • Easy add-in model
Demo: Migrating Apps to the Cloud Windows Server My Enterprise App Store The Cloud