 Hi everybody, I'm Thierry Chomron from CloudWatt and We have a Foucault de Bonneville. I am a Foucault de Bonneville product owner at CloudWatt We are going to present to you how to scale SDN and the choices we've made in CloudWatt First of all, I would like to introduce a story about who is CloudWatt So the key question with the cloud is who will take care of my digital data Those digital data, they can be financial, industrial, personal Patrimonial, health data or that could be data related to email So who? And the paradigm is What is the affordability of getting privacy, security and durability? There are two curves. There is the curves of privacy, security and Durability assurance and there is the curve of the TCO Which is the cost. Whether you believe in yourself, I do it myself. Yes, I can Sure, it's possible, but the cost of doing it can be pretty expensive You can do it via private cloud and depending on the private cloud choice. You see these little bumps It's more like expensive. It can be Do it yourself Depending on what you do then they are very attractive multiple public clouds available and They are cheap, low price However, the question there is what is the level of security, privacy and Durability I'm getting It varies depending on the supplier and there is so-called sovereign public cloud Our sole goal is to deliver privacy, security and durability of your data at the low cost of public cloud So to ensure privacy, security, durability of your digital data at the low cost of ownership of a public cloud Is our mission This is Claude Watt and we are in France and with the sovereign cloud provider in France for doing this How do I get managed services in a public cloud? So in Claude Watt, we offer YAS object store, Hadoop as a service But all the layer of managed services is offered through partners So if you want to use Claude Watt services, you will go through partners and Here you see a subset of the partners working with us For which use case will you use Claude Watt and public cloud services? It can be dev and test It can be production grade hybrid cloud It can be big data Hadoop as a service It can be high traffic web hosting. It can be Claude for media or It can be SAS applications So how does SDN and network serve these use cases Here you see a panel of Rating all important is the network and SDN for a given use case So in column you see the use cases like Claude for media, high traffic website hybrid dev and test, YAS for SAS, Hadoop and health and In line you see the different services that you get from your SDN and network Hey It's not exactly in front, but The first one is subnet and V-routers and what you want to get is flexibility in designing your network Designing a subnet V-routers. You want no limit in the number of routers You use and in the number of subnet you design With open control what we use there is a complete transparent integration within notron And we have soon source not coming with the version 1.10 Hey The second side is the bandwidth So bandwidth We've used open V-switch in the past at the beginning and we were able to reach about 900 megabit per second at bound of a VM With open control we are exceeding 7 gigabits At bound of a VM so that we've already seen that live in our network And we have no explicit limitation egress of a tenant So we can have multiple tens of gigabits outside of a tenant. There is no limitation like because of a router Bond with limitation latency Latency is very important. I think this thing gets a little bit crowded probably because of the apple and latency is very important and In France we get minimal latency Thanks to our network and tends to our location in France So we're a French cloud provider and it's very important that we reach French enterprises and Customer as well as European so you can go on select sees us our cloud screener to see the benchmark of latencies and will you will see that We're number one in latency minimal latency on object store we offer end-to-end direct connection and also One thing which is very interesting is end-to-end private MPLS vs. R from subnetwork in the cloud up to the intranet of the customer so that you have a single addressing plan and everything is private and Now I suggest live demo for the new features Okay, so as Jerry said we are French cloud provider and our stack is mainly is based on a Open stack and open control Does some people around who knows about open control, okay cool So The thing is that When we started with open control, it was fleshly open sourced and We needed to Get quickly up to speed and We needed a performance overlay and another open source of early, but there was a couple of feature missing the two main features that We wanted to have quickly was sourced net meaning when you plug a network to To a router and this router to internet you want that your VM get access gain access to internet automatically This feature was developed by some guys of cloud what with working with the open control team and And I want to that's the demo I want to do But I would like my Screen to be more viewable Getting better More more more You want more? Okay Okay, so I prepared a series of Common line to show you I think most of you are aware of how network works in in open stack What I want to do I want to create Something like that Meaning just the right side so a virtual network with two servers The router and the internet so I just want to prove that the The virtual machine can configure dance themselves download the web server and host a very small page with just the server ID inside and Then if I have time I will I just want to bootstrap a load balancer as a service instance and Add these two servers to the load balancer Present this those balancer to the outside network and show you that we can reach and that will advance on the VM For that I need to Clean up my stack so I I have created already created the the network and the subnet associated and I am going to Launch these two servers with the metadata's that Will tell to server one to as the web server server one My key and the network I want them to connect to okay, so I get my two VMs started and I get them back here in the meantime. I can start to Prepare my load balancer I'm going to create the New pool with two members so I know the IP my VMs are going to gain but that's something you can configure dynamically in first release and with and with the heat and Then I'm going to create the VIP For my load balancer for the two VMs So let's see where Vmr, okay, so VMs are not yet configured with the web server That shouldn't be long So I get my pool and I get my VIP here So my VIP is on the 20 to 20 to 20 to address and What I can do is I can associate this VIP with floating IP which Which allow us to reach the VM from the outside, so I just have to Pick a floating IP floating IP associate so that's my Board my floating IP ID So now my floating IP is associated to my VIP from my load balancer, and I hope my VM finally are configured Okay, so I get my plan B my plan B is a already configured Stack if I can okay my demo So that's the same stack in another tenant That should be Okay, I got four minutes left That was my floating IP on the other one and so we get the same design on this stack With my two servers my VIP inside in the 20 network attached to the floating IP which is the 85 and as we Can see there. We had the Server name that's changing meaning that each request is Going to a different server Okay, sorry for the demo Yeah, you want to conclude yeah, I just wanted to say it's the first time in the world I think We get to such a demo with this feature with this overlay and with the ice ice release We're working very hard to get this In our production platform very very soon, so our clients will meet the Level of of quality that's meeting the reference implementation of neutron and open stack so that's it so thank you Foucault and So you've seen the first live demo of a load balancer on open control Just to say what's behind the scene of Claude Watts is We are Whoops We are using open source from head to feet and This is open stack open control and adoop for adoop as a service and I would like to say big thanks to the open source communities Certainly we contribute, but we get more than what we contribute So thank you. Oh, yeah, we yeah, we can remind just the the the project DNA of Claude Watts is And why we choose open control? It's The cloud is 100% open source On 99.99% open source We didn't want any vendor looking on our production platform And we want to use standard protocols like BGP like MPLS and like GRE and that's What we get with open control and the the four points I picked from open controls Architecture strength is that we have a fully distributed vrouter meaning that the L3 L3 agents are hosted on each compute node which makes no single point of transit of the traffic Mostly the North South to North traffic we get a full slash registry general routing Meaning that every IP is announced inside the network and if a floating IP is not used inside the overlay It's not announced outside. So you can stop the traffic destination to these IPs on the border, which is really great that Control plane and data plane are fully independent And analytics also so you can have one component You can have your data plane working while the rest is down and We have a very Very very nice feature that's all the LBAS demo that I did and the source net demo that I did are fully available because natively in the system we can Spun two instances of each and It just failovers automatically So Thank you for your time and attention So that was a quite, you know, first demo of LBAS on open control and so you can Join our public cloud at www.cloudwater.com. We have free resource deals There and you can meet us at our booths if you have a question As well, Cloudwater is hiring so You're welcome to If you're interested. Thank you