 Hi, welcome to SuperAzure TV. Can you go ahead and introduce yourselves and how you participate in the OpenStack community? Hi, I'm Gal Sagi, working for a Huawei European Research Center. I'm working for a project career, a project Dragonflow, working on containers and networking in OpenStack. Hello, my name is Antoni Segura-Poimedon. I work for Midokura out of Barcelona. I'm one of the core contributors in Korea and I'm currently working on containers, Kubernetes integration that seems to draw a lot of attention and so on. Awesome, so what's the current state of career and how is it helping OpenStack users who are interested in container orchestration? To me, there is this new block, this new kid in the block containers and there's the OpenStack workloads and users and employers are trying to connect between OpenStack and what they are, the new orchestration engines and the new things that containers bring. And career mission is to basically make this very simple, to make one layer of orchestration and management for the operators and enhance their containers environment with policy and richness from OpenStack. Yeah, so the current state right now is that each of those orchestration engines are managing their own way and they have their own points of extensibility and what we're doing is try to work with each of those and first we brought the live network driver for Docker and now we're working on the Kubernetes one and the idea is that Mesos will be discussed and so on, if more spring up, so we'll have to deal with them. So what's a common request you hear about container orchestration as a lot of these new projects are coming about? What are some of the more common questions that you hear or requests that users have? So what I hear the most is probably about the seamless integration like I want to use the Kubernetes API, not necessarily use something like an abstract layer, even though some people do want that, and I want to get access to the OpenStack resources, network storage and so on in a way that I don't even notice that I'm using it, that if I want to specify something I will be able, but otherwise by default I just get it up and running and I don't need to do anything about it. I think one of the major things that I'm hearing is that people saying it's too complex right now. There are too many layers, people want to manage containers and OpenStack with one single pane of glass and I'm hearing a lot of problems about nested containers which we are also trying to solve in a career. Because the people use the bare metal infrastructure, they run VMs, they run containers on bare metal and then they want also to run containers on VMs and of course if you have three different sets of infrastructure and management for each of those it's going to be very costly. Definitely, so what do you think is next for containers with OpenStack? I think you both said some really great things that users are kind of asking you about. So what do you see as the next thing that's going to happen within the developer community to address those questions? So from my point of view what's going to happen is that we're going to make more and more OpenFact services available. So currently we have networking for Docker, then it's going to be networking for Kubernetes, Mesos and so on. Then storage is something that we're discussing now about having and Magnum is a very nice and important project of OpenStack that gives days of deploy and management that he was talking about. So the idea is that these efforts that we're doing, the two communities within OpenStack to convert and to make Magnum also leverage the effort that we're doing. Our mission in short is to simplify things for users and operators that want to run OpenStack and containers together. And my goal, our goal in career is to enhance the containers environments and I think we are on the right path. Awesome, thank you guys.