 Okay, we're rolling. Good afternoon. My name is Steve Curry. I'm the founder and president of MetaCloud I'm Todd Cranston-Cuevas Todd, what are we going to demo today? Absolutely nothing We actually wanted to give this time back to the community and talk about things that we thought were important to OpenStack in general For example, celebrating our wins as a whole for all the companies here at the OpenStack Summit I'm gonna advance to the next slide. There we go So a lot of us have some tremendously amazing fantastic great wins In our space with our solutions that involve OpenStack The problem is is that a lot of those customers because they're very big. They don't always let us talk about who they are Yeah, and it's a bummer because everyone wants to know, you know, who's had wins and we've had analysts and articles and information dispersed that says that Potentially OpenStack is not fully ready for prime time or production but I think everyone here would agree that OpenStack is ready for production and as I've been to all of the OpenStack summits through the last couple of years I've seen this community get bigger and bigger. It's because we're winning and we're doing a great job at acquiring new customers and building great solutions that Customers need to make their business successful. So what I would like to suggest to everyone here today is That we find more creative ways to celebrate our wins and we can do that. Thanks to the OpenStack foundation If you look at the bottom there OpenStack has debuted a new page that will allow you to in some sense talk about your win without really getting into the legal issue of Attaching it to your company's name. So I think what's most important here is that OpenStack is recognized for wins within the enterprise. It's being adopted by the enterprise. It's very important So for example, we have a very large company that we had a massive win with they've been using our product for about a year We'd love to talk about them because we think it's important for the community to continue to continue the momentum of OpenStack But we can't because of a legal agreement that we won't mention their name But what they could do what we could suggest to them and what we will suggest to them now that we know about OpenStack and what they've done with their user stories page is ask them To talk about the fact that they use OpenStack in a generic sense At the OpenStack user stories page So for example, our customer could go there and talk about that they do use OpenStack How they use OpenStack it wouldn't necessarily be tied to MetaCloud in any sense Or your company for example with your customers, but it builds momentum It lets analysts know that OpenStack is getting traction That there's great wins out there and it lets everyone kind of know how OpenStack is being consumed and used To make large companies or companies big and small More successful more agile Etc. Yeah And again, it's it's one of those situations where you know if the community wins we all win So it behooves the fall to basically make sure that we're getting our clients to recognize That they're using OpenStack and and openly just generally let everybody know that they're driving their enterprises on OpenStack I don't know if we want it. Well, yeah, so I think We just want to promote the idea of thinking about a new way to talk about your wins And it's a bit washed out of maybe your your brand name or your or your logo But I think it's it's great for the momentum of OpenStack. I think it's a really important time for OpenStack and Companies that are built on OpenStack solutions to really celebrate their wins And it may not be in the sense that you would like to for them the maximum benefit that you would get for Connecting your brand name to that customer's name, but For the community and for OpenStack, we think it's very important So we would encourage everyone to go to OpenStack org slash user dash stories and talk to your customers the wins that you've had in your organization and and talk to them about submitting their use case On OpenStack org so that people can learn about those use cases and how that technology is being used within Enterprises etc So I think we can so we've actually got a two-part discussion here. We wanted to talk about companies letting everyone know about the wins they've got with an OpenStack via this OpenStack page and then we wanted to talk about Addressing the needs around the user of OpenStack So yeah, there's I think from my perspective just Looking at the documentation that exists in OpenStack org website and some of the other documentation I've seen it's it's not that the documentation is good It's exceptional. So please don't get me wrong I think that there's just been huge community involvement and just tremendous generation of documentation It's just we come into a little bit of an identity crisis of figuring out, you know how do we define a user and We were thinking about this a little bit in terms of we have people who are now consuming OpenStack as a product and much of the documentation that is there is aimed squarely at a lot of developers systems administrators operations people but the people are actually going to be Interfacing using the dashboard perhaps writing code Just basically deployed against OpenStack The documentation is a little bit more difficult to reach and find and then it's also an issue of just defining What a user is for the community the community does have a definition of a user in the community draft charter That includes a definition of roles organizational Affiliations market specializations geographic regions. I think today I'd really like to think more about the roles and especially those people who are going to be using it as a product so you know The roles that are defined by the charter if you just take a look I mean it covers just about everything you'd ever do with OpenStack I think really the first one the consumer is probably one of the target audiences that I think really needs to be addressed much of the documentation is not hitting that target right now and I think you could really brand the product much more effectively if you're hitting the consumer the other area is that um You know looking at those people who use it to get things done You can't really assume that they're also going to be the people anymore running the cloud You know early adopters were building their own clouds trying to build it on their own and then consuming the product But now look for us. We're a product provider. We provide clouds as a service. You have hosted solutions You can no longer assume that the person who's now going to be using the dashboard or horizon to build their stacks It really has any idea what's going on under the hood And again, how do we outreach to that class of user? Again consumer is a funny term It's a term that I think goes well with the definition from the charter The only thing is I'm not too sure how easy it is to understand from the consumer's perspective But nonetheless it is I think a viable term It does reflect the fact that you're going to be consuming the product and using it as opposed to developing it and maintaining it and operationally making sure it's functional and In terms of how we do we outreach for that subpopulation Some of the ways we reach out to groups right now would include, you know, kind of your your traditional Well, let's go past that I already discussed that you're kind of your traditional user groups. You got user groups community welcome guides pretty good I think it's very good actually The open-stack operational guide that just came out is I think a tremendous effort that five days sprint is amazing what they produced And then user stories as we had discussed I think of all of these it's the user stories that probably hits people right at the heart because they can really understand from a user perspective or a consumer perspective I Do think that there needs to be a way of designating consumers on a more Clear level so that we can have perhaps user groups or other organizations specifically for people who are IT operational folks people who are perhaps internal developers who will be given access to the dashboard to be able to On their own basically deploy systems for testing or for development And also for IT stakeholders and executive kind of decision-makers It's it's a little bit interesting I've been going to a lot of user groups lately and as you might expect they're typically 80-90% engineers Operations folks systems engineer and they are very interested in open-stack, but again very much from the low-level operational side Ultimately you do have to reach your consumers though because that's a good, you know, that's who's going to drive your product adoption So again, it's not so much like I necessarily have an answer But I do think it's something that as an organization there has to be a significant focus on Some really I think some highlights of the year are the gnome. They had women internship program Develop some really interesting good documentation that was exceptional Aimed I think squarely at this Consumer population relatively easy to understand gave a very good modular overview of how open-stack works and was accessible The only other thing I wanted to mention is it's interesting like horizon is a big part obviously of how you would interface as a consumer I as a test I kind of looked to see how hard it would be to find a dashboard page or even an image It took about 15 20 minutes to find it there was one quick image in the getting started guide and then the Rest the rest of the information you would need to use rise and is actually under the Administration guide for Nova But buried way deep in the interface section As a consumer you would never look that deep into Technical documentation to find essentially a user guide So again, I'm just thinking that there has to be a slight refocusing Now perfect, so I would just like to ask that everyone in the community consider giving back to OpenStack Foundation OpenStack consumers by potentially submitting documentation that it helps end users or consumers Understand how they can more easily access OpenStack I can more easily use it find the simple things that they need just to get started I think if we can drive adoption at the consumer level, you know, it helps us all win again and I think it's something that when we look at OpenStack and kind of Where some gaps might lie Enabling the user and the consumer at the horizon dashboard level or the API level Better understand how they can consume and and not be so frustrated when they get started initially so appreciate your time Thank you. Thank you very much