 Was that our cue? Greetings team endurance four o'clock on day four of the open-stack summit and you guys are still here Or you fell asleep in your seats from the last session and nobody came and poked you. I'm not sure which Welcome thanks for joining us. We have a little bit of a play on you can have your cake and eat it, too My colleague and I are gonna talk about how you can build your open-stack and consume it, too Welcome everyone. My name is Valentina Larry and I work for plum grid Plum grid is a software-defined company that has a solution for open stack and I work on the product management product marketing side of the house My name is Brian Thompson. I lead product management for rack spaces open-stack private cloud portfolio Where we've partnered with plum grid as well for more advanced stn capabilities within our private clouds So one of the interesting challenges that we have that kind of sets the stage for this is really those Barriers to adoption for enterprises customers of open-stack itself. What are those kind of key challenges? Oftentimes when we talk to customers, we kind of have to rebaseline and come to that realization that open-stack is not a product Right. It is a collection of loosely coupled open-source projects My best analogy is like imagine this amazing sea of Legos that they can all be snapped together And you can choose different Legos and put them together in different combinations to make what your open-stack cloud looks like But holy cow. It's immensely Complex if you look at Nova alone, right? There are eight different Virtualization drivers depending on my platform and what I want to use. There are over 700 unique configurable attributes of just the compute service Now I multiply that across all the different projects that I can include as part of my private cloud and all the different permutations and External drivers and components that go into it It can be a little overwhelming one of the things that we see is That the market itself the cloud market is continuing to evolve and it's out of this complexity in this barrier to entry That we see opportunity to help customers kind of get through this process I might talk about how massively complex it is for many organizations They can certainly try to take that challenge on themselves But there are many others they're looking for maybe a managed experience that kind of goes through that To build on my Lego analogy There's this context of I could build my own car. I can source the parts myself. I can read manuals I can figure out how to put this together Maybe I have that expertise in house Maybe that is a core competency for me and that makes a lot of sense But for a lot of organizations Maybe it doesn't and this is really just those those cloud components that we talk about How can I solve that and give you the easy button the on-star experience where I have somebody else kind of paving that way Like I talk about the complexities and barriers to adoption within broader open stack kind of across all these projects It's that open stack is hard. It's very complex. There's a scarcity of talent up there But there's a whole underlying component of complexity around networking specifically that creates a huge challenge for enterprises to adopt it Yeah, and you know to dig deeper on the network side One of the things that I hear from the users I work with and I've been part of the open-stock community for a very large number of years Is you know is that they sometimes, you know see the networking as a barrier to the adoption of a cloud solution Versus an enabler, which is what it should really be right? And you know part of this is you know something that you know Brian also hinted at which is the Organizational challenges that they face internally of not being able to adjust to the models of operating In all the different components obviously including the network where everything tends to be more automated on-demand streamlined Versus the more traditional model of okay. I need you know some network functionality. I'm going to open a ticket I'm gonna wait for someone to go and you know provision this network component for me and make it available So that my end user application can then go and consume it And so you know by talking again to users This is an example of a real customer that we were working with which is you know They were opening a very large number of tickets every time they needed to bring up an environment for an application You know 78 tickets. It's a huge number and it was taking them You know a certain number of months to be able to bring up this environment And they're certainly not the only one out there And so their goal clearly is to see how they can take these impediments and make it an enabler Where they can you know not only achieve you know compute on-demand and storage on-demand but also make the networking component Fully programmable and fully you know able to be created in a matter of few seconds Now you know probably or you know most of you are familiar with the networking project within OpenSack That it's aiming at providing networks as a service which is Neutron You know just for those of you that are just approaching the OpenSack space Neutron was a project that was introduced a little after the creation of OpenSack It was introduced with the fall some remits and the main goal for Neutron was from the get-go to enable Two personas the cloud operator as well as the tenant to both have the ability to create networks as a service You know before Neutron there was some very basic networking functionality that was kind of baked into overall OpenSack within Nova But that lacked the control in terms of features and functionalities and configurations and more advanced applications needed and Especially as we start moving OpenSack into enterprise territory You want to be able to not just deploy new cloud applications, but also take existing applications and move them into this cloud environment So obviously the network plays a key Plays a key role there right where you want to be able to give Control to the user of the cloud where they can go and create their networks are routing their IP space There are security policies and also make sure that the cloud operator can still enforce any type of common rule and services across the different tenant environments So a lot of progress has been made obviously in the OpenSack Our community around the networking piece But if you were here for this past four days and you sign in some of the network related sessions There's certainly a lot of challenges there are still there are still present and and some of these reside around kind of the architectural choices that were made at the beginning of you know the design phase of the networking component and some of these come from trying to match Some of those design decisions with the large scale and the production requirements of you know customers and users in the OpenSack community You know you you probably are familiar with the fact that there is a mixed bag of distributed functionalities and centralized functionalities and some constructs of high availability that can be you know matched to some of the components down there But it's not necessarily the most homogeneous design So one of the things that you know we see when we work with users that are approaching OpenSack And especially from an enterprise perspective is to help them You know map the traditional constructs of networking and the solutions that are used to build to this You know new model that is certainly you know more distributed more software base and as Brandon was mentioning There is you know on the networking side as well There is a very large number of choices and options that users can go through So what we're going to go through next is you know to show you how we jointly bring a solution to our users That helps simplify some of these you know architectural choices as well as organizational boundaries And you know speed up the adoption of a technology like OpenSack and enable them to consume More advanced functions like network as a service within their solution We'll raise for the click So to start with kind of sitting the theme for this and this has really been from a rack space perspective our Mantra around how do we solve this for customers? It's really we're making OpenSack simple How do we make this where you can consume OpenSack as opposed to being worried about operating it? How do we deliver it to you in a way with a reliable and predictable? Scale and feature and performance and availability that you can then spend your efforts innovating on top of how do you consume these? Services as opposed to trying to build them yourself or manage them yourself So it's really trying to deliver that as a fully managed service The way we do that And part of that key value proposition of our partnership with plum grid being able to bring together our operational expertise And the capabilities of the plum grid on S platform is really around How do we provide you that single point of contact for all of your OpenSack operations? There's no longer this I'm going to call a vendor X for this and vendor Y for this and troubleshoot this and Look up in Google for this. How do we solve that for you? How do we simplify that and allow you to consume it and spend your efforts innovating on top of OpenSack rather than trying to operate it? We have a tight integration with the plum grid on S service So this isn't just a logo on a slide our teams work together The plum grid team makes the upstream contributions into the open stack ansible project that we use to consume and deploy Our prescribed deployments and build out and operate private clouds We work with them very closely on a constant testing validation and certification process So that we know with each release of the rack space private cloud and with the ONS platform These are working tightly together and working in a predictable scalable repeatable fashion We have an a massive amount of expertise between our two organizations rack space Of course as that foremost operator of OpenSack technologies between our public cloud and obviously the number of private clouds That we continue to build out and operate for our customers and then bring in the in-depth expertise that the plum grid Team brings as part of that cohesive solution for our customers. We're able to really meet those needs And then that one support number again It's not a decoupled experience as customers are operating this as they're working through these challenges There's one number to call and we as a collective team are responding to that both with the same focus on Delivering customer outcomes. It's not again a decoupled experience. It's very important to our overall relationship So Brian spoke a little bit about, you know, the business value and certainly this is, you know One of the major drivers it was one of the major drivers for us as two companies to come together and bring to the OpenSack community a joint solution that it's tightly integrated but You know, obviously, there's also a lot of you know, interesting technical reasons that you know play a very important role to our Users as they go through the selection process and you know the decision process on how to go about adopting OpenSack You know, so just to kind of help you Get some ideas and navigate maybe your decision here You know I wanted to highlight a little more the technical aspect of the integration So Brian mentioned, you know Ansible and you know, obviously This plays a critical role in how easy it is for someone to get a deployment up and running Right. So the fact that you have these two solutions being fully automated through the same framework You know really helps someone to get started in a matter of, you know, a few hours now Let's be realistic. It's probably not gonna be minutes But it's gonna be a matter of few hours as long as your physical infrastructure is in place The two components can quickly come together And this is something that it's quite important I know how many of you have tried the pulling open stack I tried, you know, I've been trying since Folsom, Grizzly, Yavan and all of that and certainly has been getting easier and easier and easier But it's still, you know, especially if you if you are in an enterprise environment Used to enterprise grade solutions It's not necessarily something it's always there. So we, you know, collectively put a lot of effort around making the deployment model and automation as Simple and seamless as possible so that you can, you know, be up and running in a very little time And the fact that we bring the teams there to help you through the process should, you know Hopefully speed up the whole The whole, you know, again deployment time The second aspect is, you know, what we refer to as an enterprise grade Architecture and there's two primary components there that I want to highlight. The first one is the concept of high availability You know, I spent a lot of time Educating customers as a product evangelist around open stack open stack networking and, you know What are some of the architectural decisions that they have to make from the get-go and, you know Very often someone asks me can I start with just, you know, trunk default open stack and my answer is always sure go for it You know anything that you pick out there is going to work for a small deployment Now it's a very different discussion when you start looking at what's going to happen when you want to run a production workload on top Of that environment and that's where, you know The architectural decision of looking for something that provides a very strong high availability model And this is true both for the overall, you know, open stack framework and in particular for what concerns me the networking layer, right Which is which is what provides the, you know, underlying connectivity between workloads and Storage and all the components that you have in the environment It's of paramount importance, right? If you cannot tolerate a failure If, you know, there's any component that it's hard to make, you know Highly available that can be an impediment to, you know, successfully rolling out a new business So, you know from an enterprise great architecture perspective having a strong high available Strongly high available solution. It's something that it's very critical The second aspect of things kind of goes back to what I was mentioning Which is if you have five nodes anything will do right, but if you start looking at, you know Kind of the typical size of a cell which is maybe, you know 250 nodes to 500 and then you want to start looking at multi-cell solution You certainly need to start selecting solutions there that can scale to those numbers Can you know seamlessly scale to those numbers that are not gonna just fall apart because you want to add more compute power to it And so, you know, what we do joint ways to Make sure that we, you know, harden the code obviously to make an enterprise grade But also the look at this key architectural Components and make sure that they're tightly integrating the solution Built-in so that when it comes to you as a user you get those benefits The third aspect which is critical for an enterprise environment is the you know security framework, right? And there's a lot to it and I'm not gonna have the time to go through all the aspect of this But the first aspect is obviously that you're most likely building a multi-tenant solution If you were to have just a single tenant solution You probably wouldn't be looking at open stack and all that comes with it, right? So by definition whenever you have multiple tenants that are sharing the same infrastructure You want to be able to have a common share infrastructure so you can get the best from a you know utilization and cost perspective and You know operation on cost perspective as well But you want to make sure to you know be able to tightly Isolate workloads that belong to different applications or different users or different line of businesses And you you know you want to be able to apply Security strict security policies right at the boundary of each of those tenant environments And so that's something that you know we jointly Bring to the table and you know especially from a networking perspective One of the key tenants of our solution is to provide is strong No micro segmentation and multi-tenancy solution The other aspect of you know being an enterprise and deploying open stack Is to be able to audit this environment have all the logs you need to be compliant to whatever Compliance you have in your environment right so that's something that you know We keep as one of the key requirements for for the deployments we enable The last bullet for you know, it's really important and we're gonna talk a lot more about you know How we enable users to build their business on top of of this kind of joint platform, right? But the whole idea is that you know We want to speed up your you know rolling out a new business And this is the number one driver most you know most often for you to go and look at open stack, right? You want to bring your business you want to roll it out faster? You want to generate more revenue and there's all sort of impediment to this The first one is you know We obviously want to bring you the greatest and latest features as fast as we possibly could right? So this is one of the you know key Enablers for for you to to bring more value to your line of business We also want to make it very simple to you know upgrade and migrate from one existing environment to to another environment We want to make sure that we can help you bridge anything that it's pre-existing into this new Cloud deployment that you have and we want to help you design applications on top of this So we'll talk a little more about kind of the design phase of a project for us But that's where we can help you take an application and figure out exactly how you know You map the requirements of this maybe traditional enterprise application and ported to a cloud environment So there's clearly a lot more details there You know customers ask me you know to things like the balance is a service and You know my cross implementation all sort of things that we can do for them technically in this environment But you know I just kind of wanted to give you kind of four key points from a technical perspective that you can bring home together With the four business values that Brian identified earlier to kind of look at the you know the overall value of this joint solution All right So if we start to talk about kind of the collective offerings that we're providing I Touched on this from a open-stack private cloud practice area within rack space and our focus again is how do we? Simplify the way in which you can consume open stack Going back to those two big barriers to adoption Just general based on the user survey and other analyst feedback is the complexity of open stack It's really the networking layer and then that lack of talent that's out there We really focus on this delivering open stack as a service if you want to think of in that context But it's really delivering it as a fully managed service offering We focus on delivering a high available reliable platform We actually stand behind the availability of the open stack apis with a four nines SLA That is our focus on being able to operate as part of a scalable highly available control plane as part of our reference architecture In the way in which we deploy and manage those services We take this practice anywhere our customers need to be we have the ability to deploy and operate private clouds In any of our data centers in any of our customer facilities or third-party data centers And we even recently announced the ability to actually provide hardware Into third-party facilities as well so for customers are looking for that fully managed experience from the floor tiles to the top of rack switches We can now provide those services again based on that operating expertise in the way in which we deliver these services That comes from rack spaces DNA and our involvement in open sex since the beginning we have more operational expertise Operating just deploying operating open stack clouds both private and public than anybody else in the space by Multiple factors factor many if you will and then looking at this single platform Context how do I deliver you a mechanism that you can deploy virtualized workloads bare metal capabilities cloud or a container? Technologies all as part of that service. That's really the cloud vision and what we're trying to enable our customers so that again by delivering it to you as a managed service you can focus your efforts and Innovation on top of those clouds and as opposed to trying to figure out how to run them If we look at just a quick touch base on what our technology offering is within the open stack private cloud area We recently released our Liberty series if you will or the first of that Liberty series of our RPC product This is a prescribed deployment of open stack We kind of opened our segment as we're talking about the Lego design and all these different pieces of open stack That goes to the overall breadth of the projects with an open stack Not all projects are created equally many are in different stages of maturity and Informing and how they grow and where are the sharp edges? We actually work very closely with our customers to make sure that we are deploying those components of open stack That are very mature that we can stand behind and operate with that high availability SLA that we stand behind and where we've Developed that operational experience that we can operate that Confidently for our customers this sphere of projects and capabilities and features does continue to expand with each release As we continue to be very active in contributing upstream to open stack and then pulling in the benefits of that to our customers As we can continue to mature and advance these different projects But we are very prescriptive as to how we deploy those the same is true on the networking side of things We've been very deliberate in our partnership with plum grid Identifying somebody that can bring to the table those advanced SDN capabilities To meet those security use cases I can't say it as fast or as elegantly as she does but the concept of micro segmentation and multi-tenancy say that five times fast in Daria These are the capabilities that this partnership can bring to us so we can deliver that full comprehensive solution to our customers And do so again in a confident highly available highly reliable way I want to talk about yeah, so this is what plum grid brings to the table and says I mentioned earlier We are an SDN solution and we have You know, it's we're software only we have an overlay based model And what we do is we bring a very comprehensive networking offering to You know through our joint partnership with with rack space There's a few you know key functionality that we bring to the table here that I you know want to highlight for for the audience and You know the first one is obviously the fact that you know We bring the ability to the end user to create very rich virtual networks And this is not true just for the end user. It's true also for the cloud operator There's certainly some you know some functionality that are exposed through opensack Networking but we'll give some ideas later of some of the even more advanced use cases that might not be you know Something you can map as is to the opensack abstractions that we can satisfy with with this platform here The other aspect of this is obviously what I was mentioning earlier around Security and so one of the key functionality that we bring to the table is the ability to you know have this Microsegmented environments. I don't have time to explain, you know how it exactly works But we have this concept of virtual domains Which was like you know a lot of bubbles that you can associate to a user or an application And within these virtual domains you can first of all define kind of security policies right at the boundaries of the virtual domain And you also have the ability to define any type of an arbitrary network functionality that an application or a user wants to consume within it This coupled with the fact that we have a very unique data plane technology Which is open source and it's called iOviser that lives inside each and every compute node Gives us the ability to bring this very advanced networking offering Coupled with analytics and visibility inside the compute layer without the need for any agent or central component like network nodes That really come in the way of scale out and high availability and all the things that we were discussing earlier The other thing that we bring to the table is the fact that again thanks to this distributed model that we have We have a lot of understanding of what happens in the environment We can kind of monitor, you know everything all the workloads their interaction with the network and expose these informations centrally so that you can then act upon it and Operationalize your environment and that's obviously something that jointly It's really important for us when we enable a user to not only deploy something and then be like oh bye Bye have fun with that right but you know to you know continue throughout the entire life cycle of a cloud project So key, you know operational tools that help you Monitor and troubleshoot and proactively find issues at the network layer or something that we have put into you know to the product solution and You know the last thing that I want to you know mention is the kind of scalable Architecture and I'll show you what it looks like in a in a picture here Which is the fact that as I mentioned earlier, we don't need to have agents or central components So what we have here is we have this distributed component that lives inside Each of our of the compute nodes in an open stack deployment and that's built on you know Iovizer as I mentioned earlier and this is how we bring all the features and functionality. So as I was mentioning earlier This is a key Architectural principle that will help you scale from five nodes to 50 nodes to you know 500 nodes in a very seamless way and You know that couple with you know the visibility that we bring to the table and all the operational tools It really help you with you know not just building a small initial environment But you know scaling out and rolling all type of interesting applications on top of this So this is you know what the what it looks like you know Behind the curtains right and we didn't want to just be like oh trust us This is how the platform kind of comes together right we want to give you an idea of you know the moving parts But what we want to do next is you know after we took you to the Challenges and we took you through the value of the joint solution and how it works behind the covers It's to actually show you how we you know in a very concrete and practical way help a user Through the journey of adopting An open-stack environment. So how do we help someone? Build a private cloud right and what are some of the steps that we you know to get or go through and you know I just want to highlight Something here because it's really important You might think that a lot of the challenges that an organization encounters in adopting open-stack are technical challenges And while that's perfectly through there's also a whole lot that has to do with the internal you know organization structure and readiness to consume new technology and products And this is true from you know the engineering group that you know necessarily might not be able to build a new solution from scratch all the way to the operational team that might not be able to Be proficient from day zero in operating this such environment, right? And in I'm a technologist. I'm really passionate about everything that's new and You know can change and transform the world But I'm also you know very much aware of the you know barrier to adoption of new technologies, right? How long it takes to learn to unlearn for example, how to do traditional networking and learn how to do software And I find networks and you know on learn how to do traditional You know compute management and learn how to do you know out the provision compute on demand through open-stack, right? So what we want to show you here is how through a series of steps we can help organizations Start get started on their journey to private clouds, right? So yeah, I think to build on that. I think one of the key themes that we see are why do open-stack projects or initiatives fail? There's certainly the early stage of we failed to get it up and running There's certainly the I failed to operate it at scale. I couldn't upgrade it. I couldn't keep it running But oftentimes even if you can get through those two barriers as Valentina mentioned There's the organizational adoption of it in many cases. This is a brand new technology I have to teach these people how to consume these services in order for them to really get value out of it Like what's the ROI on me building this cloud if nobody's going to be able to use it? So it really is a journey. It isn't a turnkey here I've built this amazing snowflake cloud for you go on your way There's a bigger part to that between our two organizations again with that joint focus on the customer outcome We believe there's a number of steps along that way We invest upfront in helping and walking through our customer walking our customers through a very involved design and discovery session How do we help to understand and profile your use cases the workloads that you'll be running on this and oftentimes customers? Don't know what that is. That's fine. We can help model for general ones, but how do we start with these? Informed decisions around sizing and how will this grow and how will this scale? How do we make sure that we're setting you up to be successful with that cloud early on? That then can roll into the initial deployment, but it can't stop there You didn't need to go into from a training perspective How do we enable the different personas within your organization that need to understand how to use this technology to be successful? Obviously focusing on the cloud user Those developers and others that will be consuming these cloud resources. How do you make it easier for them to do so? How do you help make them effective in doing so so that you actually start to get usage on us right away? How do you help train an operator capability so that those key? Architects and others within your organization that need to understand how open stack works can have that appropriate baseline of functionality and As you start to look at the more advanced capabilities that you can leverage from the SDN layer How do I start to be able to consume these services and architect applications and how I'm going to roll out these different workloads? To take advantage of the security capabilities and scalability capabilities all the things that I want to add to my Way in which I'm going to consume these clouds that becomes a very important part of that journey and that experience to continue to build on that We have within rack space as I thump my microphone As well as with our partnership we have the ability to bring in additional services to help customers as they get up and running in this cloud How do I start to focus on those things on top of the cloud our enablement services group? How do you think about? Re-architecting applications or moving there's a great keynote earlier I think Jonathan kind of talked about this classification of Applications or workloads that people are moving to open stack you have that cloud hosted experience How my fork lifting or trying to move across one of the design considerations? I need to do to move those pets and make them successful in an open stack world I have the cloud optimized What are the tooling and automation and other things I can start to take advantage of within an open stack? Platform to help me advance those applications and make them more effective And then of course how do I start to architect for the true cloud native type of stateless horizontally scalable applications? Bringing those Resources to help customers make those transitions learn and embrace these technologies is a key part of making them successful But again, it can't stop there the ongoing operational experience is another key part to making these customers successful It's not enough just to install a cloud once How are you scaling it? How are you upgrading it? How are you managing it? You're going to design self-healing applications that take advantage of the API is the elasticity of a cloud But if the cloud itself isn't there, it doesn't matter So there's a heavy focus on that that operational experience which goes back to the constant Testing validation certification that we do jointly to make sure that collectively we can provide that highly available cloud That doesn't just meet your needs today We can continue to grow with you and scale with you and make sure that the lights are on and things are running as you expect It in a predictable way Yeah, and just to give an idea of You know one of the results of this kind of joint design We wanted to you know give you something that will be very tangible is one of the first steps that we do You know together with our customers is to come up with kind of two designs one is more of a logical design and that means that we take your applications and we start looking at you know Your specific use cases and I'll give some ideas later on what some of those are And you know come up with okay What does the virtual network look like what type of advanced applications and functionalities we need there? But the other one it's also to come up with what does your environment your physical environment look like and this might seem like a Three-wheel step, but it's actually something that it's quite important to help Again getting started in adopting these technologies So one of the components of what we usually you know bring to the table. It's you know some very detailed reference architectures around the deployment model and you know we try to As much as we possibly can come together to standardize on you know how you go about deploying this solution And you know bring you something that it's you know a validated design that you can follow and you know leverage in your environment That includes kind of the basic functionality as well as some of the advanced use cases that you might have in mind for your specific environment So it's not just a matter of obviously bringing together two products But it's you know kind of coming up with the entire set of Tools that are needed to you know get started with a real production deployment So kind of to wrap it all together and then I want to certainly leave a little time for Q&A here You know we wanted to show you the kind of so what so now you talked about all this you know great solutions and soft You know offerings and services, but I'm getting started in my journey. What can I do with this? So we wanted to you know get your thinking and get some thoughts going there and show you some of these cases that we see Around you know the concept of cloud in general right and this can be you know your private cloud environment It can be you know more hybrid offerings you're building But you know we wanted to give you some ideas of what are our users looking at you know private cloud for and you know Obviously there is the traditional infrastructure as a service, which I haven't even quite mentioned there Which is simply the ability to start creating this you know environments and you know provision the Self-service on-demand control to the end user, but there's all sort of interesting applications past being one of those that And are being commonly deployed within open-stack and private cloud environments, which are certainly driving some of the Advanced requirements, you know from an underlying platform perspective that we went through earlier on in the flow Other very good use case That we see from joint customers is the e-commerce use case where we have You know businesses that are driving Revenue through a website right where I go and can you know purchase something and you know They're actually bringing in all sort of interesting requirements obviously upscale obviously of security right I'm making a Transaction with my credit card, so I need to make sure that the environment it's Isolated and it's auditable and all the things that I'm expecting from from an online platform Another great example, it's you know companies. They're looking at Streamlining functions like communication communication as a service moving from you know provisioning of physical equipment To provisioning something that can be consumed as a software model There's obviously a lot more that can be built on top of these environment right and by no means This is an exhaustive voice, but we wanted to you know kind of wrap it up and show you some of the potential use cases that you can Start thinking about once you have a ready to deploy managed solution for your private cloud environment And I think with this we wanted to thank you for coming here and open the floor for any question or comment or Additional thoughts we do have a few moments that there are microphones out if anybody has any questions We'd be happy to answer on All right. Thanks for coming. Oh You have a question, please RPC sure I saw the components that you deployed with our PC 12. How are you deploying? Swift are you doing on the controllers or can you also have it deployed on an HA proxy and separate sure? Yeah, so we kind of advanced through it and I didn't show kind of our full reference architecture But within RPC, which is our affection name for rack space private cloud We actually deploy all the open stack services in LXC containers on a control plane Our starting position is a four node control plane that run all the open stack services With Swift depending on the size or scale of the Swift cluster This is where that Modular capability of deploying those services in the containers can help us scale out to be very large We can run the Swift proxy services in containers on the existing control plane Or depending on the size or scale of that environment for a very large Swift cluster Typically, we will add additional infrastructure nodes and dedicate to the Swift proxy service So it's really just tuning for what are the expected input output type of workload in the scale that you're running But it's part of that control plane. We can scale it as big as we need it to be Yeah, for performance oftentimes we will break out the Swift proxy services onto dedicated nodes Correct. Yeah, we deployed the Swift proxy services into LXC containers Can you just come to the mic? Sorry. Otherwise, it's not gonna be in the record. I'm failing to restate the question Diversion RPC 11 did it use LXC containers? We've been using the LXC containers our deployment methodology since our ice house release RPC v9 Okay, and do you have are you working on the talk it right now? And do you have any idea when you might release I do yes and yes, so We obviously there's a component that comes to our release schedule right which is tied to as We can enable our support teams and kind of fully deliver that solution as we can continue the integration and certification of our partner plugins Such as the plum grid that kind of leads into that our team We recently announced our Liberty series that we released it came later in the calendar than we would have ideally done So but we've been working on a lot of other things as well Going forward with our mataka release and then as we get into a regular cadence following the community going forward will come much quicker So the mataka series or v-13 will be coming later this summer But you'll see us close the gap a little bit to where we've been as we also want to stay very close to the community from an overall vulnerabilities support and work that comes from that Please use the mic Thank you. So currently we use both rack space public cloud and private cloud So do you have any reference architectures spanning both these two with open stack? Ah, so It's a good scenario. So again to kind of restate the The hybrid experience if I'm kind of maybe jumping ahead the look for of something that's consuming both private cloud and public cloud capabilities so From a connectivity perspective rack space has a suite of products that allow you if you're running a private cloud within our data Centers to connect and extend to our public cloud. We call rack connect We are as an engineering team to kind of give you a little bit look underneath the covers within rack space We've actually brought our pride our private and public cloud engineering teams together They're now very focused on a lot of pure upstream development and how we actually bring those platforms even closer together So beyond the I have common API frameworks and there's certainly orchestration and tooling that can leverage across both So we've helped customers with kind of cloud bursting scenarios, and I don't mean the meteorological term Actual workload kind of bursting But you'll see over time as we bring these platforms even closer and closer together Our public cloud has kind of been an area where we can continue to advance and innovate and our private cloud where we've been bringing in those Hardened services that we can operate at scale for production workloads. You'll see those start to come even closer and closer together other questions Are we standing between you guys and beer? The question is are we the only company operating a public upside cloud? I don't believe that's true I believe there are several I Think even the keynote and I'm gonna fail to mention the names because I don't remember but there are a handful now Other questions Great. Well, Valentine. I will certainly be around if anybody else has any one-on-one questions, but we certainly appreciate your time Thank you. Thank you