gorillas in the mist
TRANSCRIPT
Gorillas in the mist
Enterprise Workloads on OpenStack
Gerd Prüßmann
Cloud Architect Deutsche Telekom [email protected]@telekom.de
Sriram Subramanian
Founder & Principal Cloud SpecialistCLOUDDON@[email protected]
AgendaBrief HistoryToolboxLessons LearntDeutsche Telekom OverviewOverview of WorkloadsWorkload #1Workload #2Lessons LearntNext Steps
Brief History
● Compute Intensive○ E Commerce○ Research○ Service Provider○ Streaming
● Large Storage○ Media
● Compute + Storage○ Bio Informatics○ Analytics
Toolbox
● Cloud Native Applications Unicorns● Port● Rewrite/ Partial Rewrite● Smart Packaging● Backoff :)
Lessons Learnt
● Start from Workloads● No One Rule Fits All● Wrapping in VM != Cloud● It’s OK to leave some out
• Business Market Place (BMP)
• https://portal.telekomcloud.com/
• SaaS offering - applications from Software Partners (ISVs) and DT offered to SME end customers
• Cloud platform based on Open Source technologies only (OpenStack, CEPH, Ubuntu)
• Project started early 2012 with OpenStack Essex, CEPH
• 1st OpenStack platform in production since Q1/2013
• complements other platforms: Enterprise clouds based on i.e. VMware / SAP Hana, OpenStack based Cisco “Intercloud”, OS platforms for NFV, research, IaaS
Deutsche Telekom Overview
OVERVIEW OF WORKLOADS
• Enterprise Social Network• Enterprise Cloud Storage TeamDisk• Payroll Management Sage• Enterprise Resource Planning SilvERP• Customer Relationship Management• Invoice Management Fastbill• Knowledge Management• Enterprise Content Management Lexmark Enterprise Software, EasySyS• Project Management Projecterus,
Teamlike, weclapp• Contract Management • Document Management Mobile Devices PadCloud
all applications are completely different w.r.t.
• technologies used• tenant size / resource usage• scalability / elasticity• business case• number of users / target groups• operational maintenance efforts• level of cloud awareness
OVERVIEW OF WORKLOADS
SERVICE MODELS
• Two models: Managed model vs. Hosting model
• Cloud resourcesOS Tenant, instances, storage (RAM, persistent Volumes / S3)
• Reference and production tenants
• PaaS services / supportVPN, load balancer, proxy server, email gateways, diff. databases, mirror, puppet master, DNS, NTP, backup, monitoring
• Individual integration / onboard support
WORKLOAD - BUSINESS CLOUD STORAGE
• Application developed by DT
• Enterprise secure online storage for documents, images etc.
• web app, mobile app, PC SyncClient available
• Petabyte storage cluster (CEPH)
• integrated in some other applications on BMP (easily exchange documents between apps)
• bundled with every business users mobile phone contract
WORKLOAD - BUSINESS CLOUD STORAGE
Application consists of
• Apache web servers (memcached)
• JAVA application servers
• ActiveMQ servers
• Transcoders (image processing)
• MongoDB servers
• Load balancers
WORKLOAD - BUSINESS CLOUD STORAGE
Before onboarding: Non-dynamically scalable installation on physical servers
• Traditional 3-tier deploymentweb-, application-, database servers (master-slave),
• DRBD replication
• Deployed on multiple huge servers in DC
• Expensive storage appliances (NFS)
• no configuration management / automated installation
WORKLOAD - BUSINESS CLOUD STORAGE
After onboarding: dynamically scalable tenant on OpenStack
• Load balancers in front of each layer (web service / application server / API)
• Deployed on multiple standard KVM VMs on OpenStack
• Multiple MongoDB database servers
• all persistent volumes on CEPH RBD
• NFS replaced by object storage (CEPH S3)
• configuration managed by Puppet
WORKLOAD - BUSINESS CLOUD STORAGETOOLBOX
• small partial rewrite (cloud S3 storage backend, MongoDB)
• smart deployment (Load balancers)
• configuration management (puppetized) / automatic installation introduced
• scalable and highly available storage backend introduced (CEPH, RBD/S3)
Result: Scalable enterprise application on cloud
WORKLOAD - ENTERPRISE SOCIAL NETWORK
• ISV’s enterprise social network application for private cloud offering
• originally “on premise” solution
• huge customer specific modifications
• multiple Single-Instances for private cloud customers (just one VM for every App Tenant)
• “tenant VM” contains application and services
• every new “customer tenant” gets a single, new VM
WORKLOAD - ENTERPRISE SOCIAL NETWORK
onboarding actions:
• ISV implemented / replaced storage backend with S3 (CEPH)
• configuration management (puppetized) introduced
• “cloud manager” service introduced by the ISV to provision, reboot VMs (single “customer tenants”)First user login starts the instance - last logout closes down VM
• “cloud manager” portable to any cloud platform!
WORKLOAD - ENTERPRISE SOCIAL NETWORKTOOLBOX
• partial rewrite - adoption of cloud S3 storage backend
• additional development - cloud manager
• smart deployment with “containerized” VMs to prevent heavy changes on a pet / on premise app
• accepted limitations of scalability and availability (VM reboots <1min)
LESSONS LEARNT
• Enterprise apps: no cattles - only pets
• Enterprise apps / sector software: specific target groups / limited number of users / not millions of users worldwide
• “Cloud native” from ISVs point of view:rewrite app - huge investments - no business case - no ROI
• Majority of enterprise apps are not well prepared for cloud (Legacy, stateful, not cloud aware, no DevOps technologies)
LESSONS LEARNT
• Initially increased integration efforts on cloud or OpenStack
• Good toolset to ease the migration to cloud:
Partial app rewrite (to integrate cloud technologies)changed deployment and distribution architectureconfiguration managementchange processes
• Adjust installation, maintenance processes of the apps
Next Steps
● App Ecosystem Work Group● Win the Enterprise Workgroup● OpenStack User Stories - SuperUser● Cloud Native Applications Whitepaper
Gerd Prüßmann
Cloud Architect Deutsche Telekom [email protected]@telekom.de
Sriram Subramanian
Founder & Principal Cloud SpecialistCLOUDDON@[email protected]