 All right, so good afternoon and for everybody. Thanks for stopping by We don't have a lot of time to you know for for this particular Talk, but hope what I'm gonna present to you is of some benefit for all of you guys that are new or getting your feet wet And open stack or those who are just recently started Then we get it just hands up how many of you guys are completely new to open stack who are just Okay, awesome I'm gonna take that the rest of the other guys are already well delved into the magic that makes open stack What it is and just to let you guys know it is going to be a very Beginner-centric type of presentation. So what I'm gonna be showing here is necessarily going to be groundbreaking But at least who provide you with some of information as to how to get to explore your open stack Infrastructure using the Python open stack client to give you a little bit of an idea about myself. I'm a Support engineer at rack space private cloud We you know support out a large number of open stack customers of all various sizes Not only from the open stack consumption model, but as well as to managing their infrastructure from them as well I've been doing this for about roughly two years and Over community of the over the period of ten years having experience in Linux network and of course virtualization technologies Open stack. However, it's been one of those that one of those Technology or technology fields where I feel like every single aspect that I've learned over a period of time I've been constantly put to test Now you don't necessarily have to have a lot of experience in working with open stack directly Obviously and strong knowledge of the Linux Operating system as well as some solid networking background or some networking concepts is useful And as well as some strong familiarity with command line Interface clients. However, you know, it can be a little bit intimidating once you start looking into the moving parts And especially when you're a new guy Learning about every single project that's out there but again in contrary to what the presentation title states you can take a deep breath as I hope that your managers is not Going to land you into a full open stack deployment single-handedly or just by yourself without any experience One assumption as well is that if your organization itself follows Multi-cloud strategy chances is that you're using open stack have heard about it or are currently in the process of implementing it On the other hand if you're attending here in your company sent you here Likely is that you're using it or we'll be using it in the future now as you guys heard on the keynote this morning, right? There's a 44. What's it two-thirds of the? two-thirds of the Implementations of open stack are being used in production and the user data that I gathered Before I heard that this morning is between 2015 and 2016 based on the user surveys There was approximately a 16% increase in production workloads So chances are that with the growth of these production workloads So is the need to manage this you know or have people capable of managing this type of environments now There is a point to consider when dealing with open stack as an infrastructure as well as an infrastructure as well as an open stack consumer as Open stack infrastructure manager, you know You'll be involved constantly with the users of the cloud itself a lot of the times you have to deal with Silent failures meaning everything shows up monitoring system shows up you look at all your systems are Working but a specific user Project or tenant are reporting an issue and after you dig into it a little bit deeper You do notice that there is an issue another another challenge and within managing an open stack infrastructure itself is that while the goal itself is to move the Infrastructure as a flow reverse platform while you're up meaning you are abstracting You know yourself from the users and the user are be able to consume the infrastructure directly There's Yeah, this is the users who when you do the platform was trying to get familiar They have to rely on your expertise. So you have to be very well-prepared into learn, you know learn Do you reason not familiar with the answer or fish answer together my apologies In addition to having to familiarize yourself with this complex environments with a vast number of software components Which are mostly entered interdependent of each other is a bleed simplified When you're equipped with the route right tools now before talking at taking a look at the unified open stack client one Smart note to consider is that there is a number of open stack projects There I put 46 on the slides. It's actually a whole lot more than that Issues specific project does have a set on set of software development kits language specific bindings as well as clients the Open stack client itself at one point In the what it solves is the need for you to having to install multiple command line client tools and it's unifying All of the core projects into the same Into the same tool now, let me go ahead and show you the This in action and this again, it's not a comprehensive Walk the rest to how to install the client. It's just mostly has to showing you top five commands that you can use to identify your infrastructure So if you excuse me here Sorry, I'm not by screens mirrored All right. So the first thing that we have to make sure is understanding the What services are enabled in your cloud right so in this particular case and this live environment that I have configured this Consist of networking the image service The identity and the compute service the placement service at this point We're not going to worry about it because it's a new feature that's been implemented starting in Okada, but in this particular case. We're testing that the Keystone or the authentication service is working In order for you to enable this endpoints or this endpoints that you can see here the services have to be defined Without this endpoints being defined and without those endpoints being bound to a service You will not be able to interact so you can say that before you can have anything running in your infrastructure You need to have the Keystone service fully running and implemented the next example that we're going to show you here is the Service list that is running by Nova Nova or or the compute service as you can see one column you have the number of the program or the binary that provides services The host words running as well as the status in the state now what that tells us there is the Nova compute Which provides instant services to it's running on two different hosts and then the Nova? Control plane services such as a noble scheduler console as well as a conductor are all running on different number of hosts This particular environment are you deployed it using OpenStack Ansible, which does utilize containers to Containerize a lot of the compute plane services. So that's essentially what is shows here Another caveat to understand is that not all of the services do support not all of the projects either through Using its native command line interface tools was using the Python unified client will support statuses like this To give an example the glam service itself There's no way for you say a chat glance show me what the statuses of your service in this particular case Of course, you know, it's returning a number of the instances that or images that the service is providing However, it doesn't give you any status if you want to familiarize yourself more My suggestion is again when starting just look at the endpoints and all of us and all of the different endpoints That are there are likely going to be low-balance. So there's going to have multiple members behind it So if again, this is taken into consideration that you have absolutely zero knowledge of the infrastructure You're pretty much sort of like reverse engineering your way into like, hey I want to see what my infrastructure looks like without zero documentation Another example that I have here is the networking service. So if for this in particular scenario, we have Linux bridge-based environment with a number of agents that are running for neutron and Of course, very similar to the command output that we saw for the compute service list You were going to have the agent type the host where it's running as well as that it's it's state and where it's at And of course, there is a whole lot other again This just went meant to showcase The environment as it was set up in the lab There is I can get in a lot of other services or many other services that are not yet supported by the OpenStack client But you can say that the core projects are supported including cinder orchestration heat as well as all you know as was a variety of other projects See that's pretty much all we have for now You know, yeah open for any questions or or anything against just a very brief walk through as to what you can do with the OpenStack client itself All right, then sit. Thank you guys