Do you wonder how to make use of T-Systems’ Public Cloud (IaaS - Infrastructure as a Service) offering Open Telekom Cloud (OTC) for your future workloads? Do you wonder as well how you could migrate your existing workloads from another infrastructure like AWS to Open Telekom Cloud?
This blog post is just the first of a series and will explain you the general basics and advantages of scale-out cloud infrastructures. You will also learn more about the key differentiators (like SLAs) from traditional physical or virtual (“legacy on premise” or "Enterprise Cloud") infrastructures. Further specific challenges to get virtual machines and services working well in Open Telekom Cloud are addressed next along with some considerations on security and deployment automation.
Since I mentioned that this is just the first pitch of a series you maybe ask yourself now what’s next? Just get back to our blog here on a weekly base and you’ll find the continuation:
- Next time I tell you more about how you could make VMs work well in Open Telekom Cloud
- In part 3 I tell you more about the usage of Open Telekom Cloud for test and development environments
- Part 4 will bring some light to you on how to implement a web presence on Open Telekom Cloud
- Last but not least (for a start) part 5 is going to explain you how migrations of applications from another scale-out cloud platforms could be successfully executed.
With this series of posts I do explicitly focus on the general technical considerations to make applications work well on Open Telekom Cloud and take advantage of its benefits. Every cloud adoption project will involve several other phases and implications like analyzing business requirements, efforts to adopt an application that it works well on a Public Cloud, organizational changes and of course cost. All these aspects can be individual and complex and thus will not be touched be me in this blog.