1. Stairway to the cloud or can we take the highway? Taivo Liik

2. Who Am I Taivo.Liik@Playtech.com

3. Current Situation 3000 physical servers 25 000 Virtual Machines Over 100 deployable application servers

4. Current Situation (2) Developments happen across the Globe New versions and fresh features every week How to scale them easily? How to cut down the cost?

5. Current Approach Moving more and more to micro services approach New micro services are developed constantly Needs to: – Be scalable – Be discoverable – Have connectivity to different locations – Be highly available – Be configured – Have ability to store the logs for troubleshooting – Have up to date middleware

6. Drawing a parallel

7. Platform as a Service Requirements – Easy deployment – Run and scale applications – Possibility to make fast application upgrades There are several cloud products to accomplice it. Do we need: – Open sourced? – Commercial? – Public? – Private?

8. Open sourced or commercial?

9. Public or private?

10. What did we choose? Open sourced Private

11. Cloud product We chose Cloud Foundry as our cloud platform

12. Drawing a parallel (2)

13. From VM to cloud No permanent storage in Cloud Foundry for applications One port opened for application to be accessed outside the cloud Flexible scaling – application lifecycle can be very small Application can connect to outside world over as many ports as needed

14. From VM to cloud (2) Where to store application start-up configuration? Where logs can be written? How application monitoring will work? How middleware is deployed? How application deployment changes? How to know how many application nodes are running? Do we need to know?

15. Application logs No permanent storage like in VM Solution needed due – We have more than 100 deployable application servers – It quite an hassle to read logs from different data sources

16. Push logs to Apache Kafka – Clustered for high availability Log solution

17. Camus jobs are pulling the logs from Kafka to Hadoop Distributed File System (HDFS) Reading the logs can be done in single place On top of Hadoop Hue with Hive and Oozie Log solution (2)

18. Keystores & Configuration Needs to be stored somewhere Can be packaged inside the application package Can be stored in some site central location

19. Keystores & Configuration (2) We are using Git

20. Keystores & Configuration (3) Keystores needs to be in a secure location They are different per site Needed for making trusted connection We are using Vault

21. Monitoring Status was pulled form apps One port – cannot be wasted Also having metrics running to the Graphite on top of Whisper database

23. Monitoring (2) Needs to be highly available Use Graphite with Influx database The switch gave us additional tools like Grafana Monitoring pulling service can pull status from Influx DB

24. The road so far

25. The road so far (2)

26. The road so far (3)

27. The road so far (4)

28. Service Discovery Information about nodes was in the database How it works with dynamic scaling?

29. Middleware In virtual machine we had middleware preinstalled Upgrades took time

30. Middleware (2) manifest.yml Cloud Foundry middleware in its blobstore Custom build packs are supported

31. Load balancer Past – Each VM needed to be in the LB pool – Each VM needed to have firewall hole opened – DNS records needed to be created Now – Define that the application is in the cloud – Cloud infrastructure makes the rest

32. Security Each application is – In specific org Inside specific space – Inside application container

33. Orgs Orgs can be used for different environments in single cloud: – Production – Staging – Integration – Testing – Development – Performance – Some other purpose

34. Did we take the stairway or highway? We needed to change: – VM based procedures – Middleware and application deployments – Modify existing automation – Keystore storing policy – Error troubleshootings – Network layout – Capacity calculations – Service discovery

35. Did we take the stairway or highway? (2) For single application it is HIGHWAY Cutting down the cost infrastructure dependencies Taking private cloud approach it is STAIRWAY

36. Sometimes the stairs have to be taken to get to the highway for faster developments and deployments. Questions?

37. Thank You