 My name is Jesse Keating. I work for Blue Box, an IBM company as the release lead for our OpenStack product. Hi, thanks for being here on SuperUserTV today. So at the Operator Summit over here at the Summit, what were the new burning issues? So we had a fun session on the new and interesting issues for the Liberty release and I think one of the most interesting things that came out of that was that there were very few operators who were here this week who are running any significant amount of Liberty in production. So the number of burning issues that they're aware of is very, very small. So that session typically generally turned into a session about what other issues we're having and a lot of those involve keeping the old releases going and building out new installs of the old release as we prepare to move up to the Liberty release. So can you please share any highlights from what you heard discussed in terms of best practices, tips and tricks for OpenStack operators? Yeah, so what seems to be really clear is that operators are employing a strategy of segregating their services so that we're not relying on a shared pile of operating system level dependencies to satisfy the needs of all of our products. Each service is getting its own environment, be it a Python virtual environment, a virtual machine, a Docker container, whatever the method they're being isolated and segregated so that each one can be treated individually and all the dependencies of that one are treated independently and can move independently of the others. So it gives us a lot of flexibility in when we make changes to those and confidence to know that a change in Nova isn't going to disrupt the functionality of our neutron bits as well. So how can people get involved and what's needed? So the best way to get involved is to join the OpenStack operators mailing list. There's a lot of good discussion that happens there. It's not a very noisy list so it's high value content. Developers show up there quite a lot to try and present new ideas to get operational feedback on the plans that they have for the future or changes that they want to make to their projects. It's also where new information about meetups happen, new data about things like the summit, the types of sessions we're going to have, the call from moderators, that sort of thing. And it's just a good communication hub for the greater operator community within OpenStack. And one of the most important things that we can do as operators is provide that feedback, that operational point of view of the OpenStack projects to those developer communities. Some of that's being done through a tagging initiative to try and provide operational tag data to apply to these projects, building up to the type of metrics that was shown at the summits here at Summit, the keystones here, the keynotes here at Summit. Great, well thank you so much for coming on Supervisor TV again and I hope you have a wonderful day. Thanks for having me.