 Hi, welcome to our presentation today talking about the edge use case that you've heard about in the keynotes this morning, enabling a secure industry 4.0 transition for the textile industry with OpenStack. So my name is Christoph, I'm CEO and founder of ScaleUp and with me I have... My name is Christian Behrendt, I'm the CEO of BetaCloud Solutions. Mario Archediakono from EarlyCon, I'm an architect and team lead for the product IT team. Okay, so let's get started. Now hand it over to Mario to talk a bit about the requirements and challenges in our solution. Scale and challenges. So as you've seen in the keynote probably and as you can see here we are operating on a quite massive scale with lots of single machines in one plant delivering lots and lots of data. This is an example plan, midsize to big example plan from India and this thing is producing 600 tons of yarn every day so 20 for 7 operations which equals to a train of 4 kilometers of length. So this is basically what happens there every day and you can imagine that to support all these operations we have to deliver lots of IT infrastructure let alone the control PCs that control the machines and the overall plant that has to be controlled and managed like all those little things to do shift management, all the reporting statistics and so on. We have lots of data and as I want to give you one example, this plan consists of what we call so-called positions which are those winders on the left corner here and in our speech our language 48 of those winders are called one machine. And at a maximum each of these machines so 48 winders can output 800,000 data points per second and this leads obviously leads to a big requirement in computing as lot as we can directly in the factory of the customer. And with this so short introduction to what we do, the scale and the challenge and now hand over to Christoph, thank you. Yeah, so let's talk a bit more about the challenges as Mario has already mentioned. So when EarlyCon approached us early this year, they came with quite different challenges actually which were to overcome. So one of the challenges or one of the tasks is actually to replace existing physical hardware in the factories. So for example, each machine in the factory today has still a workstation attached to it. And so one of the tasks is actually to further down the road replace all those physical machines and virtualize them to make management of the whole infrastructure in the factory more easy to do. Also some of those systems in the factory are like single server single computer systems. So another challenge was actually to make some of those systems redundant. Another challenge and this was mentioned in the keynote as well is actually to enhance the monitoring and operation and control of the machines in the factory. And for this, EarlyCon is running their own piece of software, the plant operation center. And so the challenge here was to have the compute power locally in the factory in order to do the data aggregation in the factory. And then analyze the data and send out only the already pre-processed data for remote analysis of the data. And at the same time because some of those machines are not fully redundant today, another task was to build in some more redundancy and increase availability of those systems. To continue on with the challenges, another thing which was requested was to make it more easy to bring new functionality into the factory, into the machines by enhancing some existing control systems, do machine learning as was mentioned earlier and just bring out new features which then the customer can use in the factory. And so one of the goals is to use more modern infrastructure to do this in the future. So some of those new features will be rolled out in Docker containers, for example. So there's some need for a true cloud infrastructure in the factory in order to easily roll out those containers. And at the same time there's still the need to have traditional virtualization technology in the factory in order to have some of those legacy systems which are running today and move them on to a more redundant and more scalable infrastructure. Okay, so this was all about the challenges. Now we talk about what we did to make that possible. So we decided to build an OpenStack solution with SEV. And as a first step we migrated the existing systems on the central side to a central OpenStack cloud, so that we now have in Germany in the data center a bigger OpenStack cloud running high HA OS controllers, running SEV as a shared storage using QBM as a virtualization backend. And on top of this controller OpenStack environment we run the central infrastructure for the software that we are running in the fabrics. So the next step now that we have a central infrastructure controlled by OpenStack is that we connect our machinery in the fabrics. So one of the issues is that the fabrics are in Vietnam or in Honduras or something like this. And so we need VPN, we need something robust so that we can have. So the machinery is not possible to shut down the systems. So the POC running on bare metal systems, we need to connect them to the central infrastructure by a so-called edge gateway or a central cloud connector system. And in the next step we make this cloud controller bigger. So in the first step we have a single node system only with QBM running some VPN gateway software. In the next step we build an HA controller with OpenStack with SEV integrated on a hyperconverged infrastructure. And then we migrate the existing bare metal POC systems to virtual HA POC systems. So that we now have an independent OpenStack environment on the fabric side that is connected to the central infrastructure on the German side. And in the final step we migrate everything to a central controller running in Germany that is controlling the SEV storage and the QBM systems in the fabric. So that we now have a fully edge cloud. So the stage two is the future at the moment. We are at stage one and yeah this is working fine on several sites. And here are some details about the two variants. So we have a one node. Why is it not there? Yeah so we have a one node variant. This is the edge gateway and the three node variant at the moment with an HA controller with SEV. So we are going to the next slide. So the concrete implementation. Yeah so to talk a bit more about the implementation. So when we sat down together earlier this year we talked about ways how we can actually support early con to actually tackle all those challenges, find the right solution. And what we in the end decided on is that at this point in time we form forces together with beta cloud solutions and scale up technologies. And so we help early con to first of all deploy those edge installations for the factories and also support the operation of OpenStack and those edge instances in the factories as well as the management of those OpenStack instances. So that's one part of the implementation. And in order to actually have this hyperconverged setup we use the solution from beta cloud. Which is the OpenStack infrastructure and services manager which is in essence a fully containerized deployment of OpenStack. Which makes it possible to have to in essence have a consistent setup regardless of the size of the deployment for the actual end customers. So the goal is actually to have a consistent setup for a small installation with only one physical server. Going over to a fully redundant, fully HA setup which is at least three nodes big. And then for larger customers potentially in China where the factories are bigger we will need more compute resources to run everything. And so we can easily take the three node setup and add additional nodes to that setup to have I don't know five, ten whatever sizes needed nodes setup for larger customers and larger factories. So when we first talked there was also discussion about having I don't know having a look at other technologies. But we decided to use something established and standardized. So this is why we settled on OpenStack to have a standardized API in order to make it possible to use something like containers, Kubernetes and more automation in the future. So we needed standardized APIs. Another benefit of the solution is actually that we can now have all the compute resources that we need locally in the factory. So for example in the factory in Vietnam we can have all the infrastructure necessary to run legacy systems, container based, container based solutions and potentially other third party systems. Without having the need to have a good connection to the public Internet. I mean there in most factories there is a connection to the Internet and we use that connection to send out data to the central instance. But the whole setup does not rely on it and that was one of the one of the tasks that we tackled with this solution as well as remote management. So all the OpenStack Clouds can be remotely managed. So Earlycon and Remscheid can actually connect to all those instances. We can support those instances. If something on the OpenStack side is not in order we can debug and find all those issues. And last but not least another benefit of the solution is to and we build some pieces on top of OpenStack in order to do that. To take existing legacy systems which are not meant to be run in an AHA highly available setup and actually make them more available by using OpenStack using some additional tooling to build in more redundancy and more AHA capabilities to do that. So as you had heard in the morning the first pilot customer for this solution is Sentry in Vietnam. And I'm sure do you want to maybe say a few words to that as well about Sentry and their specific role as a pilot in this project? Sentry is a long-standing customer with the Earlycon main made fiber for something around 20 years now. So for us it's a very important customer even if it's not our biggest customer. But they're very interesting for us because they have all kinds of machines from us, not only single machine type. And they are currently running four instances of our planned operation center in two factories. And what they are doing currently doing is they migrate workloads that are currently run in SAP for example and migrate them to shift them to our software. So automatically the requirements for the requirements for a very high availability are raised. And so we had to do something about this and could implement this on top of OpenStack with some custom programming. Even if our planned operation center now is a we call it legacy application that has grown over the last 10 to 15 years. So there's always a good solution utilizing OpenStack even for those older systems. And on the other hand we are now able to throw our VPN into some deployment tools to bring our new infrastructure, container based infrastructure to those factories. Without the need like in the past for our guys always traveling there because we are always on with them now or they're always on with us. And yeah it's a happy story for all of us and the CEO of Century especially is very happy with this and completely understood from the get go the benefits he can now have with this new infrastructure and software layer we provide. Okay so let's give an outlook into the future. Yes in the future we have to replace the full blown OpenStack environments on the factory sites and we will replace them with one central controller so that we have a real edge cloud and not only full deployed edge clouds on the edge. And yes this will be the next stage and the next step. Yeah and at the same time I mean the first pilot customer is online the next one is the cloud is already on the way and there's more to come so in the future there's also the challenge to streamline the whole deployment process in order to support 10, 50, 100 whatever number there is edge cloud instances out there. This is something that we have not fully solved yet but we're also looking for the community to actually find better ways in order to make that more easy in the future hopefully. Yeah with that we can wrap up here and if there's any further questions you can certainly grab us after the presentation or you can have our contact details here on the slide. Yes and you can come to our booth and their booth of course. Yes C22 and yours is. A28. Okay so just come by say hi. Yes thank you. Thank you.