 Good morning. Thank you so much for having us. It's a pleasure to represent Swisscom And it's it's always better to have customers telling the story I brought Christian Bach from SwissV with me and he will join a conversation after I give some introductions So my personal cloud story at Swisscom started roughly five years ago And there was a meeting with a company called Pivotal I've never heard before and then there was something they were talking about cloud foundry And I learned only afterwards in our workshop in Ementale what it really means and Being a software engineer by heart and education, of course, I was enthusiastic about it But I could never imagine what we were able to do During this last past five years So we have created a solid cloud foundation at Swisscom so that we are able to run every kind of workloads Whether you want the deployment that runs on Swisscom premises as a virtual private environment or you have Things you would like to run even in public clouds Our vision is to provide managed services and typical outsourcing capabilities for all these environments and Of course, we did a huge investment in what we call the enterprise application cloud where We have cloud foundry as the core of it and recently and some of you might know We moved also the infrastructure layer towards the Elements from our core partner Dell technology So we have hardware and software from those guys and I would like to take the chance to Thank the Swisscom team for Enduring and bringing up all these fantastic capabilities on both sides the guys building the infrastructure and I met some also today in the morning The ones that are building applications on top So we do lots of eat your own dog food in that environment And so we are proud to see the progress So we have customers leveraging these infrastructures as well as we leveraged them at Swisscom and I remember our cloud foundry initiative around the application cloud started as a grassroots initiative and Nobody in management did ever imagine that we wouldn't end up where we are Nowadays we have geo redundant Deployments already since quite some time and we are running mission critical workloads that every Swisscom customer uses on a daily basis on this infrastructure and of course as we are on Such an event we have to announce something new We are building on our solid grounds filling the gap That is they are between infrastructures a service with the more heavyweight VMs and the platform as a service capabilities that sometimes lack capabilities and I think with the container capabilities we built on top of the infrastructure From people to I think this brings our offering to the next level so that we have really a more complete environment bringing a lightweight capabilities to do massive scale out But I think Christian is really much better suited to tell you what he is going to do with his team And I think you guys already started general availability of all these capabilities. We will have beginning of next year. Thank you So hi from my side. My name is Christian Bach and I'm chief application architect with Swiss re Swiss re is a wholesale provider of reinsurance insurance and other forms of risk transfer as a global financial Services company we're subject to very many different local jurisdictions and regulations and therefore on many different clouds We are faced with a multi-cloud world In this context the rise of containers to becoming first-class citizens of Deployments to us might simply be the best thing since sliced bread both in terms of deployments and in business continuity terms But let me tell you all about our container journey at the podium with a few slides of mine So we have no demo. There's nothing gonna break beside me. Maybe All right, so it's all my fault then Multi-cloud wasn't the original cause for us getting into docker and containers in the first place our original motivation stemmed from an engineering desire To leverage the paradigm of cloud native computing to a bigger extent than what 12-factor apps on cloud foundry And it's time in being specific here the cloud foundry application runtime allowed for We were confronted with services that were not stateless, but stateful With service instances hosting a dedicated partition of an overall state space that needed a stable network Identity and oftentimes an associated dedicated persistent volume Services typically being part of architectures where events need to be routed to self-contained service instances implementing reactive event processors Respecting local orderings and with event processing semantics depending on aggregated state From previous events having reached the respective partition That's for the first bullet We were confronted with services that were exposing multiple endpoints not exclusively restful if at all based on HTTP or Then various flavors of services that were in a cloud foundry application runtime world being considered backing services like distributed commit locks message queues or databases So these services were asking for more They were in desperate need of a home outside of the application runtime Enter Kubernetes So as you can read on the slide we started looking for solid grounds Similar to what cloud foundry offered but for just about any sort of cloud native payload Initially we explored solutions ranging from Docker swarm and custom Kubernetes installations Which led us to the discovery of the advantages of real container runtimes? We came to appreciate the control we gained in running containers Beginning being it in isolating them by means of overlay networking Being able to scale instances up and down in container replication Spanning software defined networks of which you see a little sketch of mine on the right-hand side Between them and getting strict governance in restricting any other communication paths and Even further having a say on lowest level operating system security policies in Container execution down to the individual kernel module access level For us in particular the possibility of limiting a container's connectivity perimeter Was key in getting green lights in running third-party containers Not only in protecting other enterprise services from let's be positive and just call them noisy neighbors But in days of ubiquitous internet connectivity Also in strictly governing any sort of hosting platform internal network egress as One fundamental measure in preventing from data breaches to external parties After running our experimental clusters for a while on the Swiss com yas We realized that us taking care of Kubernetes Both in installation and operation was not really what we want or would be expected to be doing as A non-platform provider that we are what we really wanted was a cast to be operated by Swiss com So not quite like the past the Swiss com app cloud on the right-hand side and not like the yas on the left-hand side Where we manage the biggest share of the stack ourselves we were looking for the middle ground Swiss com managing a container orchestrator a container execution engine for us a platform on which we could not only bring our own run times and Stateful services, but also run middleware components of our choosing or use components from Swiss com services offering We were striving for a platform Allowing for autonomy on solid grounds Gaining freedom from what a pass allows while not having to face the chores of installation from plain vanilla virtual machines And not having to operate the solid grounds ourselves So what did we do? We approached our long-term partner with which we present today Swiss com on those accounts and came to find fertile grounds Swiss com as we heard just a few minutes ago was contemplating and investigating the cloud foundry container on time and thinking about a managed cubanitas offering Themselves and had even started evaluating the pivotal container service already as Used to with Swiss com we could not only count on a knowledgeable partner ready to help us write yet another chapter in our cloud journey But we got readily Accommodated with our big enterprise Special some might call it legacy Demands like the hosting of corba IOP based enterprise Java beans demanding for unusual cubanitas stack features like the direct address ability of pods in That spirit. Thank you Swiss com Thank you, and thank you all for having me. It's great to have customers like this