continuous delivery to open telekom cloud (otc) · saas apps cloud shift migrate modernize cloud...
TRANSCRIPT
Continuous delivery to open telekom cloud (OTC) Openstack Summit 2016, B. Folgmann, B. Rederlechner GDC Cloud Consulting & Transformation Services
t-systems Transforms whole landscapes to cloud The goal is „Cloud-only“ simpliCiTy, noT „one more environmenT“
Unlock Classic
Build Digital
&
PaaS
Mobile Apps/Devices
SaaS Apps
Cloud shift
Migrate
Modernize
Cloud Native
Levels of added value
Enable the cloud Operate the cloud
Cloudify
Cloudify
Cloudify
Cloudify
Take existing cloud approaches into account
Pursue a consistent cloud strategy
Transformation to T-Systems open cloud world
For E2E governance from appli- cation operation to end devices
Intercloud
vCLOUD
T-Systems Dynamic Services (DCP)
3
Open Telekom Cloud: What´s in?
4
OTC professional services
Calculation & Cases
Calculate optimal setup & pricing for a given solution
Calculate business scenarios
Based on OTC price lists
Easy Jumpstart
Coaching on OTC mechanisms
Installation/usage support
Easy Migration
Assement of existing apps
Migration strategy & roadmap („FMO sketch“)
Migrate industrialized with ATMF
Cloud Native
Help new apps to become „cloud-native“ on OTC installation
Jumpstart new development
Continuous integration
based on widespread cloud solution pattern
Modernisation & Hybrid
Help existing apps to modernize with a full modernization on OTC
help existing apps to modernize partly in hybrid scenarios with OTC
based on widespread cloud migration pattern
Level I: Shift to cloud
Address whole landscapes systematically
Level II: Modernization
Legacy, customer applications, CRM, dev/test, collaboration. web applications, big data, mobile, applications on PaaS.
Cloud-Native apps
Exploit Cloud API + CI/CD Pure virtualisation
Cloudified apps
Fully Industrialized factory approach
Unlock Classic
Build Digital
&
PaaS
Mobile Apps/Devices
SaaS Apps
Value step projects & pre-product integrations
Managed Evolution & capability-driven Modernisation „eaCh modernisaTion sTep ConTribuTes To business value“
6
horizontal scale Concern: Poor availability
„Pre-product“: finish line blueprint Cloud mechanisms
elastic loadbalancing
clustered DB
horizontal scale
burst-out to public
Concern: Seasonal bursts
auto-scaler
infrastructure as code
migration pattern: replacement with
cloud adaption
Concern: Inflexible customer database
SaaS
7
Pets vs. cattle
7
Maximum of care for your beloved pets
Cattle: one is like the other
Image Bakery Ephemeral Servers Rolling Updates using ansible and Jenkins in a real-world project
Image CentOS
Image Windows
Image SuSE
Public Images
Otc images
9
Image Cust1
Image Cust2
Image Cust3
Private Images ECS 1
System Disk
ECS 2
System Disk
Objectstore
Image bakery and Ephemeral servers
10
Production Staging & Testing
Base Image
Public Images
Image Cust v1
Private Images
ECS v1
System Disk
Image Cust v2
Image Cust v3
Update ECS v0 to v1
System Disk
UpdateECS v1 to v2
System Disk
ECS v2
System Disk
ECS v3
System Disk
Update ECS v2 to v3
System Disk
11 11
1. Creating basic structures https://console.otc.t-systems.com
2. Creating and installing Jump Host / Ansible Master
3. Adding the Jump Host as Jenkins Slave
4. Running the Image Bakery
5. Rolling Updates in Auto Scaling Group
13
Boris Folgmann Senior Multi-Cloud Architect
- GDC Cloud Consulting and Transformation Services -
Mail:
Bernd Rederlechner Lead Architect Enterprise & Cloud
- GDC Cloud Consulting and Transformation Services -
Mail:
Backup
T-SYSTEMS datacenter Campus BIERE