Alright, so it's Sunday. I have to remind myself when I'm live because I forget. It's bad. It's pretty bad. And so yeah, it's Sunday. So I'm here to art you guys. If you're new, welcome. Hi. I'm Erica with me as my co-star Bowie. Jeff's over yonder as is Moo. You'll hear him coughing a little bit later. AKA Louisa. And we're artists till death. We go live every day, usually at 6 p.m. Central. I'm really today. Whoops. Except for on Tuesdays. We do 2 p.m. Central. And it's usually resin art. Sometimes it's other kinds of art, but it's always art. And it's usually live so that I can interact with you guys and answer questions as we go. So if you have any questions about this medium or anything else, if I know the answer, then I'm happy to share it with you guys. So since you're here, please leave me your thumbs and subscribe. I'd love to have you as part of the fam. I'm trying to grow. So also, if you've got a moment, share our video. If you like it, if you don't like it, share it with someone you don't like. It's ruin their day. Hi Bowie. You want to get down?  So at the end of this, I'll show you guys how the bear piece turned out yesterday and also some of the other things that I'm working on, which is why I'm doing a short live today. So yeah, what's up Karen, Crystal, Susan, Shane, Lisa, Diane, T.G., Christine, Betty, Lynette, Nancy. No, I missed some at the top. Chris Karen Marine. Missed you yesterday. Sorry about that. Hi, Michelle. Um, we decided to take a day. And if we don't go live, I usually post in ATDs, Poor People, which is our Facebook group so that you guys know what goes on if we're not here. Oh, you guys are in lockdown in Australia. That's no bueno. I fear that that's probably in the future for the states as well. Hey Tiffany, how are you? I hope you had an awesome birthday. Joe, Stephanie, Lisa. So I went ahead and mixed the resin because of the projects and I'm going to show you guys in a little bit. Um, I got to kind of get there. Tammy Anderson, I heard there was beautiful, incredibly talented, amazingly kind hunk of ham live on youtube. So I came to say, hey girl, I am a kind hunk of ham. So what's up? Um, hey Jen Germs, if you haven't checked out Tammy's channel, she's an awesome acrylic poor artist. We're going to be doing some collabs soon. I still have one collab that I need. Well, it's not a collab. We just art it together that I need to edit. Hey Susan, is this named after our Judy? It sure is. This is named after Judy Sand, whose favorite color is purple. So we requested that color passion make. Um, a paint in her honor since she's done a whole whole lot to help our channel out and they were kind enough to oblige. So I went ahead and mixed my resin. It's a one-to-one resin and I used equal parts and now I'm pouring out too much resin because I really want a negative space situation. So I don't need that much color. This is a 12 inch cradleboard that I prepped with a very deep purple spray paint from Montana. If you happen to remember the name off the end, I don't either. So since I'm doing negative space very back to our swipe days, I'm going to swipe this one. Uh, I'm not making a lot of different colors. Nope. Yeah, I'm not making a lot of different colors and I'm not making a lot of each individual color because I really want it negative space and the more colored resin you make the less negative space will be represented. So that's why I only have like half an ounce in each of these little cups. Right, isn't it a nice purple? So not doing that color yet. I don't know what I'm doing. First color I'm going to mix up is this Judy shimmer, which I while it is open, I think Jeff reviewed it one time. I haven't used it and so I'm very excited to check it out. These pastes, the color passion paste are also base tints or base cell activators and what that means is that it's going to be the reason for my cells. So I'm going to do that and I'm not going to use these other two because they're also base cell or color passion paste. Any color passion paste will create really awesome cells assuming that the other variables in your artwork are also conducive to cell generation making cell making. We'll say cell making.  Let me like scrape some off of this.  Good wording. Thanks. Thanks. Good wording. Thanks. I have my moments of good wording. Most of the time words are hard. And it's evident. Angel white is good. Titanium from Just Resin is good. And also Snow white color obsession. Today I'm going to be using Titanium. I've also used mermaid trash white, which is pretty good. System three. I've gotten to work pretty well. It's pretty good. Casting craft will work as long as it's not too thin and it's a paste you should be good to go. Also assuming all your other variables will work. Okay, I'm also going to do some silver. For this silver, I'm using aluminum powder from Just Resin. I don't usually use a lot of powders, but since I don't usually use a lot of powders, I like to mix it in every once in a while just to showcase the different looks that a powder can give you. And the last color I'm going to mix up is carnation pink from Just Resin. It is apparently also the lid to my pink sherbet. So that's fun. This is a non-shimmer matte bubblegum pepto-y pink. I can't get this lid on. If I get words right, then I'm on a different struggle bus. Never fails. Something and then it's always going to be difficult. But that's fine. So let's mix these colors. So this is a Judy Shimmer base cell activator tint paste from Color Passion. It's got a beautiful like platinum periwinkle lavender pearlescent look to it. Super fun. The carnation pink. Oh, there's low wheezy. On cue. If you're new, I have a palm. He's an elder palm, 13. And he has a heart condition. Has nothing to do with resin. So save it. I've heard it. I've talked to his vet, not the case. This one is a black currant from Color Obsession. We'll start to see the purple now up on the... Here we go. It's like a deep violet-y indigo purple. And then titanium white from just resin. Oh, for sure, Tammy. I always... My general... Let me start again. Tammy says it's good to have some of that shimmer and some that don't in order to give the eye a place to rest and make the shimmer stand out so much more. And I agree. My standard palette or color theory when I do a piece is to have either a black or a white. Some form of a metallic. So in this case, it'll be silver. Usually it's a gold. And I like to have at least one shimmer and at least one flat. And in terms of the main color, I'll pick it. And then a secondary color that's opposite of the color wheel typically to accent the color. Because if you pull colors that are opposite on the color wheel, it'll make your main color that much more vibrant. I can go on and on and on about color theory, though. If you guys aren't going to do a video explicitly on color choice and why some colors work together and some don't, I'd be happy to do that for you guys. This is the aluminum powder from just resin. Except Kim Alpha. You had a dream about these colors last night on Dolls? Okay. That sounds creepy. All right, so for my next trick, I'm going to put a little bit of this bling it violet into my this. And this is going to be applied over the entire surface and it's going to act as my grease the pan. I'm going to do a thick clear all over the whole thing so that you can see through it and it'll give depth to the piece. It'll look like a two-layer piece essentially, but it's just one layer. So this is a sparkling interference. You can't really see it until the light catches it and then it's more evident. You'll more be able to see it once it's on the board that we've got here. So I've got some resin on my gloves from mixing the colors because all of my jars are always dirty. So I'm going to use my notch trowel stick that you can get from our website artistildeth.com to move my resin around. If I were to try to use my glove hand, which is fine, I still do that very often. I would end up transferring the color from my gloves and I could leave a streak, which would be not good since I want this to be a negative space piece with very open application, paint flow. There's a word. I haven't figured it out yet what word I'm going to use for that. You guys have suggestions? I'm going to spill this everywhere. Let's move the colors so I don't get resin in them that shouldn't be there. I like the notch stir stick because it's offset. So I don't run the risk of running my knuckles through the piece, which I have done before. It's not a good time. And then also it will distribute the resin. But see that pattern? It's leaving an eighth inch of resin there as well while we move the rest of it around. So you don't have to worry about scraping everything onto one side of the surface. Okay, so maybe you can kind of see that shimmer you can see it in the notch lines a little bit. Right. Let's heat this up. Hey, Clara. TG, this shimmer was blowing it violet from resin. So when I do a negative space, when I do swipes, I try not to have too much heat on the piece because the resin doesn't like it when you're trying to use a base tint or cell activator for your design. So the cell activator that I have is this Judy shimmer. I'm going to put it on first because it needs to be under my other colors. It's finished all by itself right there. So it needs to be under the other colors to work. I always have to repeat myself when I teach a class on this. Take your time when you swipe and don't put a whole bunch of color down if you want the negative space to show. I used to give the example or what's the word?  Get a small plate and don't put a lot in it. That's kind of the comparison to why I use small cups and then don't put a lot of resin in it. So I won't make so much therefore I won't be tempted to apply so much onto the surface thinking I have to use it all. Which waste is done? I mean waste is not good. So I understand that but if you want negative space you have to apply as little color as possible. That may cover up your negative space. Okay Ms. lay down. So this is a black currant. I typically put light colors next to dark colors because when I swipe them out they'll layer really nicely and you'll see a gradation I guess in between the colors. This one is a carnation pink by just resin. I'm going to put another line of the Judy shimmer through here. And I'm going to add some white. A lot of people especially if they come from an acrylic background think that the white is what causes cells which is very common with acrylic cores. But with resin it's a little bit different in that it's about what's in the paint as opposed to the weight of the paint which is kind of what creates cells a lot of the time in acrylic cores. What's that kiwi? So this is the aluminum I'm going to add now. I'm going to add just one more line of the black currant. And the reason why I'm doing that I usually wouldn't add this much paint over but when you swipe you want to put your swiping paper in any color that's not your base paste. Which in this instance is going to be the Judy shimmer. So I'm going to take a piece of paper. You can use any heavy weighted paper that you like. And I'm going to place it like I said a second ago in any color that's not the Judy shimmer. So that will be the black currant, the silver and the carnation for this white. You want to let it soak up a little bit of paint. And then take your time pulling it outward. That pink is just disappearing. You can already see some of the cells coming up. Okay I always like to heat up the first swipe that I do just so that I can see what it's going to do if I need to make any corrections with my pigments at all. I always like to trail off my swipes so you can see it is thicker on this side than it is on this side because I swipe down to one corner as I pull it out. Okay cells. And I really want more pink represented so I'm going to put a little bit of this carnation just right on our swiping paper. You should call this a ditch swipe. Now I'm going to lay that right in our resin. Take my time swiping that out. I'm going to continue down this line of color that I have. I am Susan, thank you. I appreciate your asking. So I think it's looking pretty amazing so far. So now I'm going to do the other side and I always recommend that people pick a direction to pull. Don't cross them because then it looks kind of busy and confusing for the average person that's just looking at it. It's no bueno so pick a flow pick direction and keep it consistent. Always pull towards you not away from you so you don't risk having a swiping paper that you pull out this way and then possibly dribble back on because it's I guess a reflex once you fully extended your arm to just come right back to you and you don't want that. Just if you pull away from you just drop the swiping paper or just don't swipe away from you. Then when you do the other side pro tip just turn your piece around.  Okay so now we're going to pull this way to my left as opposed to to the right a second ago so we're going to pull to the left so that everything's flowing in the same direction and it'll look more consistent. Let the paper soak up a little bit of resin a little slowly. Also something is going to be an important point but I forgot what I was saying. That's a pretty one and I haven't really added any heat to any part of this except for this area here that's already basically maxed out on cells. When I add heat to this other bit you'll see the same sort of thing happen. Now if you wanted to swipe out and not have the cells just don't put the base cell in that area. Well thank you Tammy. Do enjoy the swipes. I did well we did two tours in Australia and both times it was basically centered and concentrated on this technique. Negative swipe, swipe that's not words. Negative space swiping and restraint knowing when to quit etc. So let's hit it with some heat and see what we got. Now you don't want to add too much heat because your cell structure won't be good if you heat it too much because when you heat resin you thin it out and when resin's really thin it's going to want to flow more it's going to want to flow off the board more and the more it moves the less words the less defined your cell structure will be. So this is very lace very very hard lines but the more heat you add the more blurry it could get because it's just moving more so do yourself a favor practice restraint with the heat because not going to do yourself any febos with it. Hey Donna Parker it's been great I hope you have an amazing day. So I think I'm really okay with this I'm pretty happy with how the piece looks so I'm going to walk away from this one. Once it sets I'll be able to show you more in detail the depth from having such a thick under layer the flood that we did initially and let's keep moving and settling for the next couple hours so I'll be checking in on it making sure nothing's really changed. One second and take this to dust free and I'll be our bee. You look at my this looks like this. Thanks. You can hardly see what it actually looks like without the lights on dust free zone check. I'm just going to grab a couple posters because I have a little bit of resin left over and we don't waste resin. Left over resin means time to experiment for something new that you don't want to mix fresh resin for because don't want to waste it. Don't have any clear. I don't even know if I have enough for three posters but we're going to do our best here. Well thank you alpha. It's much time right. I appreciate that crystal core. You guys are so sweet thank you. I'm just doing a bunch of different color bases and I guess since I have the time I can show you guys what happens if your base paste happens to end up on top of your other colors because people ask me quite often I mean why does it have to be on the bottom can it just be anywhere and make the same results and the answer is not. It has to be on the bottom because of whatever magic is mixed into the color passion paste. It has to be under the other colors in order to make that dispersion happen to create the cells like that. Five dollar word I just used dispersion. Me and words are doing all right today. What's up tutor? Okay so we got our bases done. I'm going to show you the difference in a base pasting on top and on the bottom. So with this one this light purple the Judy purple is our base base so it's going to have to be under the other colors. So this is the one I'm going to show you what happens when it's under the other colors. So I'm just going to smush this around. My only concern was making sure that the other colors were on top of that Judy purple which we did. Now on this one I'm going to swipe this Judy purple over the other colors. Now let's get some heat. Let's see what happens. You can already see some cells popping up here right. I'm just going to move these aside so you can still see them while I'm doing this other coaster but I'm not going to do anything with them till they relax and make magic. Meow then we got this one down here. You can make this one a smush. I'm out of little cups so I'm just going to put it right there. Impressive word use. Thank you. Thank you. And some pink. Essentially all I'm doing on this one is applying a bunch of color so that I can smush it on top of this purple one. It essentially does not matter what this one that looks like. Leave which one? This one? The Judy shimmer one? You're saying I should let this one live? Answer quick. So we'll let this one live. Put it over yonder. Get a new cup. Would it be good to spray paint the coasters white or any color and then do the colors? Sure. The reason why I'm not really worried about that on these is because all of these colors are opaque. You technically won't be seeing through which is why you would really need to create a base painting. You need to make most of this one the Judy shimmer because that's what's going to give us all of our reaction. See, I'm just putting this on our raw MDF coasters and you can't see through it. Okay. Now the rest of this black current and white. Y'all just hear me out on this one, okay? I know it looks hot mess but we're going to smush it and see if we can make magic. Susan, are you talking about the just resin giveaway from last week? Sorry for that movement. I just hit the charging cord. Yes, I did pull winners. I can't remember who they were but I'll go grab the winners in a moment. Okay, I'm going to smush so that some of the filling comes out and give it a quarter turn like that. Now we're going to just easily just do this. This is going to be super cool looking. Just trying to wipe my hand off with one hand, not easy. That is pretty. I feel like if I try to do this on a larger scale, it wouldn't really work. I try to do it with the 12 by 12 and it, I thought it was going to take the jaws of life to separate the two. That he says my smush has never come out of school as yours. The trick to a good smush is to be very haphazard with your application. It's my favorite part right there. A little broken butterfly wing of cells right there. Oh yeah. All right, I'm going to take these bad boys to the DFZ right back and here's the results of our, this is why we put the base under the other colors. You can see here, it did a little bit of something, not really a lot. This one did all of the things. So I'm going to smush these because they don't really, as just sample pieces, they don't really look like they're doing anything. We're going to smush so that some resin comes out of all the sides. That way you're sure that there's no gaps or breaks in your resin. I'm going to give it a quarter turn, beam bomb boom. Say the magic words. Wipe my hands off. We'll hit it with heat and see what we got. I live haphazardly. Well then the smush should be no problem for you. Purple up to my elbows. So this is the one you guys wanted me to let live. It's doing some magic all on its own because this is the cell activator color. So it's kind of just trying to make it, make some action happen anyways. Yeah, they smoothed out. In fact, they're almost smooth now, but they'll continue to relax and do amazing things. This looks like clouds to me. This wispiness right here. Love it. We'll let that one live. This one looks like a spider web almost. I like smushes because you never really know how it's going to turn out. It's like a box of chocolates. A smush is like a box of chocolates, okay? And only a resin person will understand that. I'm going to pick up a couple of these cups. Calm down, Miss. And I'll show you the completed pieces from the last couple of days. All right, Miss.  Sorry. I just need to clean this up. Well, no more purple. Yes, I woke up like this and I'm sorry. I look like this. So what do we got? There's the panda. I'll do a true color video on this guy. I did this one yesterday, so if you're interested in seeing how it happened, it looks kind of like that new glitter we want, doesn't it? All right, Miss. Go lay down. Nothing's happening right now. You didn't miss anything. Okay, come here. Mooper wants to say hi. This is Luigi. And he just wants attention. He knows it's almost time for the end of the feed. And he likes to cough to get his way, even when he doesn't actually have to cough. I'll show you our big bean in a minute. Okay. And then this piece I'm working on as a sample piece for a client. I am creating a video, so don't get mad that I haven't done a video on it. Okay, Miss. Lay down. So yeah, this actual bad boy will be seven feet. Have a drink on me, girlfriend. Oh, Tammy, where's my, do you want me to make a pamping arrow sound? He could do so much better and he knows it. So working on that piece, that is layer one done. Now I'll show you the other piece that I'm working on. Wait for it, wait for it. Yes. Sorry, I look like this today. Pop art lip piece. I should get this done today. It's essentially finished, but I got to do some shading. Yes, Tammy, you're an actual real life doll. Also, I just got in some thing. Hey, there's you guys. I just got in some lures, and you guys will be getting an email about it. So if you've been wanting the Angel White or some of her other amazing colors, get to getting because Angel White sells out super fast. The lips are always the favorite. Well, thank you, Pamela. Hey, Bamp. Yes, Tammy is amazing as all of you guys are that join us. So yeah, we're working on piece seller replace and also something we got to go down to Austin. And sorry, on Wednesday. So we'll be down there. Well, that's rude. We'll be going down there to finish that countertop that we had to completely start over for the Austin place. Okay, Bowie. Bowie wants to say hi. So come with me. There he is. So yeah, yes, big boys. All right, you guys. Thank you so, so much for watching and seeing what we're up to today. I hope you learned something. We're entertained or I could educate you about something. Okay, okay. We'd love to having you. Please share a video. Please subscribe. Leave me your thumbs. And on yesterday's video, you can leave me a comment about what animal you think I should paint next. Okay, Moose, hold on. And if you I'll be doing a drawing on Monday. If you get drawn, then you get a shirt. Oh, sorry, Susan. I'm gonna pull the names for who won the last one. Coming to my shop. This is my shop. This is where all the paint magic lives. Okay, so the people that won are Ms. Earley, Melissa, and Leslie. And they have till Monday to get in touch with me to claim their prize. Otherwise, I'm gonna do another drawing. So yeah. Okay, Moose. That's enough. Hey. Hey, what do you, what are you gonna cough right now? You're okay. We're gonna go. Just hold on. See how he stops when I talk to him. He knows. He knows. All right, you guys. Have an awesome day. Thanks for coming in and seeing all up to today. You guys are amazing. We love you so much. Enter our giveaway and you'll look out for an email with a discount code for the LaRez restock. So for the shirt drawing, if you go into yesterday's video and comment what animal you think I should paint next, that'll enter you in the drawing. And then I'll draw names from those. He knows. And so anyways, you're awesome. Have an awesome day. We'll see you tomorrow. We love you guys. We kind of want another. We never know what someone's going through. So you don't have to. See you tomorrow. Bye. Great. Round off the cat. What do you think, Bowie? That's not yours. Silly boy. Miss. You're okay. Just calm down. We're going.


Good afternoon, OpenStackers. We are so glad to have you here this afternoon. It's very exciting that after four days of all things OpenStack, you have attended this intro to OpenStack basics. So our goal here today is for every single one of you to get to use their Horizon OpenStack control panel and also use the Python command line clients. If you have any questions, we have a number of our Rackers here, and at RackSpace, we are all about fanatical support, and so we are going to show you that today. I'd like for all of our helpers in the audience to stand up and show everybody who you are. So if you have any questions, please call them over, they will help you. Yes. See, there you go. Right now, I'm going to introduce our speakers today. I'm Angela Streeter. I'm with RackSpace. I'm with the OpenStack Cloud Training Team, and- I'm H.S. 80. I've been a contributor to OpenStack for two years. I used to work on Glantz and currently, I'm a contributor on Trove. Hi, everyone. I don't think this is on. Pass the handheld. Oh, no. Hi, everyone. My name is Agnes Sigler, and I'm a Principal Architect on the Prior Cloud Solutions Team at RackSpace, and I hope that after this session, everyone knows how to use OpenStack. I'm Dana Bauer. I work with the Developer Relations Group at RackSpace. We do a lot of outreach to developers, and we create the SDKs for the RackSpace Public Cloud and OpenStack. I teach a lot of workshops, and I love teaching beginners, so I'm excited about this big group here. Okay. Do you want to pull up the workshop? So everybody here has a credential worksheet or the access page. She's going to pull it up for us up here. The workshop materials will be on- Are you going to- Well, no, the browser? Workshop materials? There you go. It's kind of hard to see. So all the materials that we're going to be using during this workshop are available here, and then also when you go home, this will be available for at least a few days to a week. You're welcome to use it and log in. There's also a virtual box appliance that we have supplied. You do not have to use it right now, but you can download it later. There's instructions for using it. It's pretty simple, and we're going to give thanks to our instructor, Matt Dorn, who is over here, and he will also be helping out. He's the one who created this appliance. He can give you more information about it if you have questions. Also, so we're primarily going to work with the Horizon PDF up there in the initial part, and then when Agle is up here with the CLI stuff, we have these files over here. They're text files you can easily copy and paste the commands if you don't feel comfortable typing them in. If you have any questions about that, please, I will be down there as well. I'll be walking around and I will help you. Just a little bit of a background. The lab environment that you are working on is OpenStack on OpenStack. It's a set of 15 beefy VMs that we have. We have a controller, a network node, and several compute and storage nodes. Okay, so this is day four. Who here doesn't know what OpenStack is? Okay, you've paid to be at this conference and you spent four days here. So basically, OpenStack is an open-source software for building private clouds. So that's between in your company or in your system, or for building public clouds for consumptions by a multiple diverse set of people. This is like a more technical definition which says it helps us control pools of compute, storage, networking, present in a data center, either using a command line interface or using horizon, which is like a user interface. OpenStack has these three main components, like I was saying compute, networking, and storage. All these different components have a common thread tying them. You can access them using the dashboard, and they all have a set of common shared services which they use, like authentication and Keystone. We'll be talking a little more about that. This is the Havana architecture of OpenStack. So if you're not aware, an ice house project culture got integrated. So this doesn't include that. So this is a brief architecture diagram. I'm not going to go into too much detail because you've probably spent four days talking about OpenStack and you're already aware of most of these components. But just for the sake of completion, let's go through and look at them one by one. First is horizon. This is the user interface, which instead of if you're intimidated by using the command line, or you don't want to go into opening your tiny terminal and typing in every single command or SSH'ing into your box. Horizon pulls up a beautiful GUI up there for you to help you manage and perform all these operations. And that's what the first part of the workshop we'll be focusing on. So NOVA is the crux of OpenStack. It's like when OpenStack started, it started off with two main components. First was NOVA and second was the stored Swift component. So NOVA is the main cloud computing fabric controller. It talks to your hypervisors, helps you spin up virtual machines. So it's basically the heart of OpenStack. Most of the commands which you're going to be doing, like booting up instances or creating snapshots, all your calls after getting authenticated with Keystone are going to go to NOVA. And all your images have to reside somewhere, right? So once you've taken, say, a snapshot, which is create an image of the instance at a given point of time, you want it to reside somewhere. So Swift is the object stored which OpenStack uses for storing all these images. It has lots of features like it helps you store data cheaply, safely, efficiently. It's built for disaster recovery, clustering and all those inbuilt features for data storage are available in Swift. Now yes, I have all these images. How do I keep track of them, right? So glance is the image registry for OpenStack. It helps you keep track of here are the images I own. And here is the location in which they reside. And for example, this image Ubuntu image resides in this location in my Swift. Neutron, so initially when NOVA started, it had all these components. It had all the voluming work, it was doing all the networking work.  And slowly OpenStack decided that we should separate out these components into their own projects. And that's how Neutron was born. It provides network connectivity as a service.  And you want your two instances to talk to each other. Neutron can help you do that. So I went through like, so whenever you make a request, you make it through Horizon, which is your user interface dashboard. It goes through Keystone, which is your heart of authentication in OpenStack. Every single call you make, you want to make sure if your user's allowed to make that call or not, Keystone is used for authentication. Once it's authenticated with Keystone, it goes to the respective component to make those calls and do your respective actions. So that was the very brief overview. We didn't want to go into too much detail cuz this is a workshop and it's all gonna be hands on. And Angela, do you have any housekeeping instructions before we start off? Now good. So all of you are ready? Pumped up to start? Okay. Use my pack. Could you guys, the mic guys, could you leave the handheld on? Some of my co-presenters are gonna answer questions while I'm going through this. Thanks. All right, I'm gonna be sitting, it's a little awkward for me as a presenter. Next year, we should have standing desks up here. No, I know, but I wanna get the, okay, I'm the one. Great. Okay, so this is your home base for the workshop. How many of you have pulled this up? Looking at this. This is the great stuff that you get to take with you at the end of the workshop. We've passed around the USB drive as well. So you're able to pull all the information that way and you'll have it locally. But we'll leave this up for a while. Our goal here is to truly take people from zero. So we're not assuming anything about your experience or your background. We wanna get you playing around in Horizon. We wanna get you doing things on the command line. If you're doing that and it's not too painful and maybe you're having a little bit of fun, we'll consider this a success. All right, so I'm gonna be working primarily from that Horizon PDF. Please follow along. You probably wanna have it, have it locally. Let's go ahead and, yeah. Can you just reiterate, they don't need virtual blocks of clients right now. They can just look straight into Horizon. Sure, okay, so we're not really working with that virtual blocks of clients right now, that's something that you can take home and work with. Of course, you can right now if you want to. But I suggest using the logging into this remote system. And at the top of that Horizon handout, you should see the instructions for logging in. And I'm gonna go ahead and. Are most people able to log in into the Horizon? Yeah, is everyone seeing this? Raise your hand if you're seeing this. If you are not seeing this and you wanna be following along, grab one of our friendly TAs. TAs, wave your hands in the air one more time. These excellent people are here to help you. Please take advantage of them. Now raise your hand if you want to talk to one of them. Connecting. Okay, so this is our dashboard. Horizon is our OpenStack dashboard. And it's a great entry point for people who are new to OpenStack. It's friendly, it's a nice graphical interface. If you're interested, if you're a Python developer, it's a Django project. I kind of find that exciting. You're using all of the OpenStack APIs, but you're pushing buttons and you're getting to explore all of the different components in a really nice visual way. So we're going to explore just a few of the components of OpenStack right now. And then we'll really do a more thorough exploration when we get to the command line. Okay, so, who's ready to spin up a cloud server? Yeah, the lady. All right, I'll talk through this. You can also watch what I'm doing up here. You can follow along on the PDF, whatever works best for you. So we're going to click on the instances menu. Ooh, all right, conference internet. So I think you can click on home. I guess you first, please. Yeah, all right, here we go. I'm going to make this a little smaller just so you can see what I'm doing up here. All right, so this is our instance dashboard, launching an instance, getting started at least, it's as simple as clicking this button in the upper right that says launch instance. So who's seeing this pop-up window? You all with me? Okay, great. You can name your instance, anything you like. I'm going to go and call mine Selfie because this is my instance. There's some nice things that we've done for you as administrators. You're all users right now, and that's all we're really going to show you during this workshop, how to be an OpenStack user. Today, I happen to be the administrator of our private cloud. So I have all the power and control. That's why you might notice that my dashboard looks a little different from yours. But we've done some things already to help you get started. One thing that you need to do when you're going to launch an instance is you need to identify a boot source. We're going to boot from image. And then we've provided you with an image here, Seros. It's a very tiny Linux distribution. Okay, the next thing that you need to do before you can launch an instance is attach it to a network. And we have a public network here that's for our entire cloud. And you're going to drag that into selected networks, come on, there we go. All right, once you've done that, you can go ahead and launch it. All right, there we go, spawning, lovely, lovely word. So this is a building machine right now. And if I click on it, I'm going to switch over to the lines. All right, I'm assuming that this is just as slow for all of you here. Yeah. Okay, so this gives you an overview of what you've created here. Some specs for the machine that we've launched. You can see that it's attached to this public network. Security groups are like a firewall just for this cloud. And some information about the image name. You can also click on the log button here. It might be slow to load. Is anyone able to see the log? Yeah, there we go. All right, so our machine is up. It's alive. It provides us with some login information. We also have a console right here in Horizon. And we can log directly into the machine. And that might take a while to come up. We click on this other button here. Okay, this is a little slow on conference internet, but who has successfully launched Cloud Server? If you haven't, if you're hung up, if you're stuck, grab one of the TAs. Okay, give yourself a little round of applause. This is pretty exciting for a lot of folks who are new to OpenStack. Okay, so the next thing that we're going to do is, the next step in this exercise is to register and upload your own image into Glance. And here's what I'm going to suggest now. I'm going to suggest that you just watch me do this and then follow along later. Or try it yourself later. Or try it at the end of the workshop. Okay, so we're going to click on the image and snapshots button here. It is really terrible. All right, there we go. Create image. Again, I'm going to give it, I'll just be a little my image. In this particular case, we're going to identify a file that's local as our image source. And we gave you this image. It's another Sero's image on the USB. So you probably pulled it to your desktop or to some other place on your local machine. Right, so that workshop dashboard where all of the materials are, you can get the image there as well. Format QCAU2, QMU emulator. And we're going to leave the rest as a default. Sorry. Can someone get the question and repeat it? Do you want to take that one? QMU is a disk format supported by KVM. The QMU, the QCAU, stands for copy on write. So what that format does is that it's a very small disk format and only expands as you write to the disk image. The nice thing of it is it gives a very compressed disk size. So you can create a 40 gig disk drive. And initially it may only use one or two gig on your whole system until it grows. But that's just the format that that disk is in. It will support other disk formats like VMDK and other formats that can be used. But that's just a particular format we've used. It's a very efficient one for running under KVM. Virtual box. Here we go. Would you fresh make sure you're on? Yeah. Okay, so here's the image that I registered in Glance. And one additional thing that I could do here is I could launch an instance from that image that I just created. And I've selected my image. Oops, what did I forget to do? Yes. So you cannot launch an image without attaching it to a network. And here we'll use my public network. Okay. And that came up a little faster. Okay, so you see that I have the two images that I launched today. The first one from the image that we provided to you as administrators. The second one from an image that I created myself and registered in Glance. Sure. Angela, do you want to take the boot from volume question? So you can have an image saved on your volume and you can just boot from volume. I forget what your options were.  So if you select boot from volume, you probably won't be able to proceed very far. Click on it. And it says no volumes available. And that's the next step we're going to do. We'll show you how to create a volume. Correct. Yes. So let's go through the basic steps. And then if we have time, we can go over more advanced sections. And it's difficult. We want to make sure that everyone that is not familiar with OpenStack can get familiarized without going into all these other options. Okay. So let's go ahead and create a volume. On the left, you'll see in the dashboard, you'll see the volume menu. Here's one that I created earlier today. I'm going to go ahead and create another one. So if you hit create volume in the upper right, give it a name. These are drive types. SATA is the one I'm going to pick. One gigabyte. And right now we're just going to create an empty volume. There's no file structure. We'll hit create volume. So here it is. We can click on it. We can look at some of the detail about the particular volume that we created. And we can see down here that it's not attached to anything. Someone says, is this block storage? Yes. So this is the cinder component of OpenStack. What we're going to do is go back to our instances. So here on the left, okay, we'll go back. I'm just going to pick one here. I'll pick selfie one. Sorry. I'm going to go back to volume. And I'm going to attach it here. So under my second volume, edit attachments. And I'm going to select that instance that I want to attach it to. So in this case, I'll choose selfie one. I'm going to go ahead and attach the volume. Sure. Sure. Okay. Okay. So I led you astray for a few seconds. My apologies. I'll take you back to the right place. Okay. So to attach an instance or attach to a volume to an instance, you're going to click on that volume that you created. Or sorry. Click on edit attachment next to the volume that you created. Okay. So who has created a volume here? All right. And if you look at the volume dashboard, some people only have delete volume. Okay. Has anyone been able to attach a volume? Yes. Okay. So under edit attachments, right. So if for some reason you had a problem creating your volume, you might want to go back, delete it, do it again, and then attempt to attach it to an instance. So I'll do it another time here. In this pop-up window, I'm attaching it to this instance that I've created. So over here on my right, are you now seeing an option? Did you have to go back and recreate the volume? Okay. Okay. Great. Okay. Okay. Yes. So we're using one right here. Also, some of you may have seen that your volume had errored out. So just go ahead and create another one. Make sure to use size one, SATA. And don't worry about errors. This is a private cloud for training purposes. So things are not going to be perfect. If there's an error, kill it, recreate it. Okay. I'm going to move on. But please don't hesitate to grab the TAs if you're still working on creating and attaching volumes. Yes. Just one. Right. Yes. So this is also something that you can attach to an instance, detach from an instance, attach to another instance. It's like an external hard drive. It's like the USB drive that we handed around. What is the question? No. Just one. So this other volume here is something that I had created earlier that I attached to a different instance. But here. So let me do this. I'm going to go ahead and detach this volume from selfie 2. And it's telling here on the dashboard that it's detaching. I'm going to go ahead and detach this other instance that was hanging around in my project from my volume instance. So error. There we go. I'm going to try it again. So Agnes, right. This is really the perfect environment for you to play around without fear. And that's really, and you can see that I'm playing around without fear. I'm not afraid. Okay. So now we have these two volumes and they're not attached to anything. Okay. And we'll do it one more time. So my first volume. I'm going to go ahead and I'm going to attach this to my first instance. Yep. Yep. So if you, right? So I could take one volume, attach it to my first instance, detach it, take that same volume, then attach it to selfie, which is a separate instance, and then detach it. So, nope. So right now what Dana showed was just how to attach and detach. If you were actually, we're going to do something with that volume, you would have to log in into the instance itself and do some magic Linux commands to make it usable so it's being used and you can put some files in our solutions that are available on the class site. We actually list out all of the commands that you need to do and you're welcome to try that out. For the sake of time for the class, we're not going to go into it right now, but it's just Linux commands. So, no, it's, once you attach a volume, you need to log in into the VM that you attach the volume to and make the VM aware that you actually have a volume and that you want to use it and stuff like that. I'm sorry. I'm sorry. When you attach a volume does the VM get a hot plug event like you plugged in a hard drive and hardware and it... You attached a hard drive to the server and so just like when you attach a new hard drive, you would have to go in with the utility in this case, it's a Linux image, so fdisk or gparted or something like that, right? And you'd have to make a partition on it and all of that kind of stuff. We also had another really great question over here about, you know, why does my first volume, the more button disappeared and it's actually disappeared for a good reason because now that that volume is attached, there's a restricted set of things you can do with it so you don't do something bad and so that's why the more button disappeared on the volume that you've actually attached to an instance. There are some features in the dashboard that save you from yourself. Hopefully. Okay. All right, so let's take a look at creating a private network. Go Neutron. You've got a... Your scroll bars aren't disabled. So right now we're using one network that we've set up as administrators that's available to all of you. All of you are working with your own projects and what we're going to do now is we're going to create a private network that's just for your project. And that means that the other users in the room working on their own projects won't be able to see this network that you're creating. All right, so over on the left side, I'd like you to click on networks. Okay. And right now you should only see my public network. This is the one that we're all using here. I'd like you to go ahead and create network. We're going to call this one private. Under the subnet tab, we're going to give it the name private subnet. If you're following along with the PDF, you can see the network address that we've asked you to use here. <IP_ADDRESS>. Backslash 29. Okay. 29. All right. And then I'd like you to go ahead and create that. Who is able to create a private network from the dashboard? You are now all neutron experts. So this is going to be a just very, very, very, very short overview. This is about all we're going to do. Agle will get into it a little bit more, the command line. But we just wanted you to see what this looked like in the dashboard. Leave it blank. In the PDF, it actually says check it. Oh, it does? Yeah. Okay. Check it. Chris, can you take this one? Oh, sure. Actually, I'm not sure either. But we do have a neutron expert in the room, Phil. When you create a network and it's admin versus non-admin state, what does that mean if they're just users? So let's take them. Go ahead, Phil. It means that the... I think that that means that then you have to admin privileges to... I mean, you have to have admins... In this, you're going to have to have admin privileges, I think, to see the box. And then from then on, normal users can't fiddle with the network. But they're all users and they can... Okay. That's a good question. So let me just... In that case, I'm not certain what that... I'd have to go look at the database and see what that one's actually setting. I don't know what the Windows thing sets there, so... Let's stop one minute and just talk a little bit about some resources that you might look at if you were trying to get more of these in-depth answers. The OpenStack site is really fantastic. The Docs, the OpenStack Docs are great. Right now, we're just trying to expose you to Horizon and how you might go about creating some resources and playing around here. It's not likely that you would spend a lot of time in Horizon, and if you're a software developer, you probably wouldn't at all. But this is a great way for you to explore the OpenStack components. And this cloud that we've set up for you today is really just a sandbox. You can experiment with things, you can try things. Also, don't hesitate to grab one of the TAs to answer some of those questions at the end, too. Alright, so the last thing that we're going to do here in Horizon is clean up some of these resources that we've created during our exercises. So if you're looking at the PDF right now, you can start by deleting those volumes from the volume menu. And if you want to wipe everything out, it's just as easy as clicking this box right up here in the top left. Why is it not that one I can delete? Right. So this other one we want to detach it from our instance. There we go. Interesting. Okay. And then from this more menu, we're going to go ahead and delete it. We're not. Alright. And so then you can also go under the Instances menu and select the instances that you created. I'll leave one. And go ahead and terminate instances. You might also want to go in and create or delete rather the private network that you created, but leave the public network there. Leave that one in place. Right. Yes. So I did that briefly. Actually, that's one of the remaining exercise in that handout if you want to do that later. To go ahead and either launch a new instance using that private network that you created. Yes. Yeah. Okay. So we've explored Horizon. We've gone through. We've clicked some buttons. This is a really cursory overview of some of the functionality there and an exploration of those components. So how many of you are excited about trying some of this on the command line? Maybe that's more. Alright. Yes. Okay. Maybe I should have left. You should have gotten the hook out earlier so we can move along there. Alright. So that's the next step. I know that might be something that's a little advanced for some of our beginner beginners in the room, but please stay with us. Excuse me. Alright. Am I on a mic now? Yes. Alright. Excellent. So everybody created instances and volumes. Yes. Yes. Alright. Ready to be super users? Yes. Awesome. So what I'm going to be doing is, because this is a live workshop demo, I'll cheat a little bit. I will use copy, paste for some commands. However, everything that I am copying and pasting is available here where it says command line solutions. So you may want to just take a look. If you want to, you can type in. You can copy, paste whatever is more comfortable for you. So if I go too fast, please stop me. If I say something that you're not sure what I just did, please let me know. Previous page. Oh, yes. So if you scroll up and you can open this PDF, you may want to save it in a separate page. I'm sorry. So you can keep this open for yourself.  And you can just take a look at all of the different things you can do in each client. I'm not going to be using it right now. I am going to cheat off the actual solutions.  And I will see if I can make sure that people in the back can see this. I am going to SSH into the same instance that Dana was using. How many of you have used SSH before? All right. So almost everybody. That's good. We will deny the acrobat reader. It will pop up again. We'll deny it again. All right. If this is your first time SSHing to it, you will get the yes no question type yes. And then the passwords, you should have gotten them on your little sheets. And hopefully this works. No. Why not? All right. Doesn't want to let me in. Did someone change their password on me? All right. All right. Typing. If I could just interrupt for just a moment while you work on that. We had a question earlier about that admin state box in Neutron. Yes. Very, very odd name for the box. But what that basically does, admin state's default value is true. Removing the check out of that box obviously means false. When true, that network will forward packets externally. When false, it will not forward packets. So it's probably best labeled, enabled maybe, would be a better term for that box having this network enabled or not enabled. So pull requests are accepted for that labeling. Chris, I think we had a question. No? An additional question? No. All right. So I was able to log in by using the correct password. I was using the wrong password. So yeah, that's a user problem. So now that I am in the terminal, I should be able to do everything and more than Dana did. Now if you list, you will see a couple of directories available for you. Go into the credentials directory. The credentials have the information available for all, for two users. So I want to be a user. I don't want to be an admin user. And this is what that file contains. People in the back, should they make the screen the font bigger or not? White background. Is this color scheme okay? Great. Great. Change it. Blue is not readable. Doesn't change? I think I need to. Good question. So if I, all right. We have white.  And you will have your own user. I am using OpenStack 100. You will have your own. But I am logging into <IP_ADDRESS>. This is the private cloud that we had set up for this class. All right. So let's go back to the credentials directory. And I still have blue. I'm sorry. This is fine? Okay. All right. So I have a user file. This file is so that we do not have to type in username and password for every command that we do. Right now, if I typed nova list, which is just a basic nova command to list all of the available instances that have been created, it will tell me that I must provide the username and password. And this is not something you want to be typing in each time you're trying to do something. So this takes us back to Stone Age. Right. This takes us back to Keystone. And if you look at the Keystone solutions that is available on the class website, these are the commands that we'll be doing. So you can follow along. You can copy, paste, or you can type them in. So what I'm going to do is I'm going to do to source the file. For those of you that are not familiar, it's just going to put everything that is in the file in there. It's just going to execute it, I guess. All right. So source, file. What file do they have? And now, when I type nova list, it actually gives me something back. It no longer asks me for a username and password. So the user has been created for us by our lovely administrators, and we have been provided with username and password. That's what you use to log in into Horizon, however, on command line. Because you're using a nova client, the command line client, you will have to pass the credentials each and every time. Instead, you can set those as your environment variables, and you will no longer have to enter them each time. Yes. Yes. So this file, you would create yourself, hopefully whoever set it up for you will create the file for you, but normally you would want to create your own, and if you're running DevStack or something like that, you would do something similar, and it would usually have your username, your password, your tenant name, and the authentication URL. This is the URL of your Keystone instance. So region one is the default region. For our class, we have only one region, so we do not have to worry about. If there is a large open stack installation, they may have multiple regions. All right. So in Keystone, you can... If you want to see what's available, you can type Keystone Discover or Keystone Catalog. So Keystone Catalog gives a lot of information for all of the different services that are available, and if you are a developer, you may actually care about these URLs because that's what you would be making API calls against. Lucky for us, the command line clients already take care of it, so we don't have to do it. If you want to know more about any of the commands that we're doing, you can type Keystone Help and enter the command following. The same will be true for the Nova, Neutron, all of the other open stack clients. So it would say Keystone Help Catalog and Catalog is List Service Catalog, possibly filtered by service. Some of the commands will have a lot more help. All right. So this is just a basic Keystone commands. As a user, you really don't have to worry about it. Administrators usually stutter up, and it's one-time job, and you don't have to do it all the time. The only thing that you may need to do is to source a user file so you don't have to do it every time, or you could just have it so that it's sourced every time you logged in automatically for you. Everybody so far with me? All right. So Dana has shown you how to create instances in Horizon. We will do the same thing on command line. First, let's see what we have. So to see what instances you already have, type novelist, and it tells me that there's a selfie too, and you may or may not have deleted your instance. I think the limit for each user is two instances per account per user, so if you have more than two, you will have to delete at least one of them, potentially two. So to delete it, you either go in the Horizon and delete it, or you type novel, delete, and the instance name. All right. And I didn't just mistype anything, so let's see if we have. And that's it. I no longer have any instances running. All right. So what do we need to create an instance? And you did this in Horizon. You needed to provide an image and flavor. So we're going to do the same. To find out what images you have available, you will type nova image list. This will give you available images. And we have a lot of people who had created images, so we have a few of them. And you probably see only one or two. It depends on what you created. I think I see all of them because, well, I don't know. Maybe some of them are public. You see everything? Okay. I think because they are public. All right. So we're going to use the Syros image. We also need a flavor. So we will see what flavors are available. Right now, it gives me only one flavor. A default OpenStack installation will have five of them, and they're going to have IDs from one to five. Our administrator does not want us using those flavors, so they were deleted. So now we have image and a flavor. So now we can type out the command for creating it. And because I think I will mistype it, I am going to go ahead and just copy paste. And all right. So it says, I got an error saying that the flavor was invalid. So that's because I need to use flavor six. All right. I have multiple. So that's the idea of the flavor. Right. So if you see here, I have ID six. That is the ID of my flavor. And I also got an error saying that I have to specify network. So because we have not covered neutron, what you want to do is you want to go and delete the networks that you created through Horizon. Or on command line, you can type neutron net delete. And I think this will give me an error again. Oh, no, it didn't. Excellent. So make sure you have only one network. Otherwise, you have to specify what network to use. So now, if I go back and try to boot an image, if I didn't make any typos, it should work. Yes. Did you delete an image? Delete all of the images? We will go and create an image. All right. So tell me this. When you do image list, what do you get? Does everybody have at least one image? Yes. All right. Was everybody able to create AVM on command line? Yes. Anyone stuck? Stuck. Can we get a fanatical volunteer? Anyone else that could use some assistance? Delete network? So I use the neutron net-delete and the network name. I think it's dash dash nick. And then I think. Yes. So if you want to use specific network, in addition to the other ones, you have to specify dash dash nick and the net ID. Yes. Neutron net dash list. All right. So we created AVM on command line. And it shows that I have one running. And it has some details. To see the details in a little nicer format than this table, you do nova show and the instance name. And this is all of the information. You saw the same information in the horizon dashboard. And this is just another way to view it. Any questions about this part so far? All right. So we had, we listed the available images, available flavors. We viewed the details. Now let's take a look at the log for this VM. All right. And this is just the same log that you saw in the dashboard. And it provides the super secret credentials to log in. And let's see, how do we log in to the VMC if we're doing this on command line browser? Well, we need to get a URL for it. We'll do nova getVNC console command. And this provides us with the URL. So copy, paste this URL. If you have a VM running, you should be able to get this. Yes. Anyone in Putty know how to copy and paste out of there? Double click. Select it. Right click. It'll copy. Okay. Just select it to copy. All right. So copy the URL. And I'll just go to the browser and enter it.  It takes a while to bring up. But you would just be presented with a little terminal in your browser. And you would enter username and password and be able to access the VM. We'll let it spin a little bit and we'll see if it will come up eventually. But to delete an instance, I would type nova delete and the name. But because I am waiting to see if it's going to finally come up, I will not delete it this time. We'll delete it later. You are welcome to delete it right now. I'll keep it for a little bit. So, so far, we have covered basic keystone and nova commands. The next big project in OpenStack that we're going to go over is Swift. Now, this is a little bit of a jump because we've been working with instances and now we're doing Swift so that we don't run out of time. We'll go back to working with instances after Swift. I think Swift is super cool. And it's really easy to use if you just want to do some basic commands. First, let's see what we have available. So, if you just type Swift, you will get all of the commands. And you should definitely go over them and take a look at them. Let's see what is in our Swift cluster. Right now, it tells me that I have zero containers, zero objects, and zero bytes. The way Swift works is that you must create containers first and then you will load your files into those containers. And you can have multiple containers and you can have multiple files per container. I think you can have container and container. I haven't played with that too much. Correct me if I'm wrong, but nobody thinks I'm wrong. All right, let's create our first container. First, make sure I don't have any. Right, I don't have any containers. To create a container, Swift, Post, my container, what do we have now? All right, did everyone here create their first container? Yes? Cool. Now, now that we have container, we should put something in there. And I probably have some files, but you may not. So what I'm going to do, I am going to quickly create a very small file by typing echo, just some text, and direct it to a file. And if you're comfortable with command line, you can create the file whichever way you want. I am basically just putting that text into my file, that txt file. If I view it, it will say that I love from Xero to Nova. Let's upload this very nice file to our Swift container. And if you forgot what your Swift container was, you can do Swift list. To upload, I think it is Swift upload. And it will say my container and the file that you want to upload. Now, if we do Swift list and attach a container name, we should see what's there. And it says that I have a file in that container. Did everyone upload a file to their container? Yes? Is anyone stuck? Excellent. Now everyone is able to use Swift. That's really all you need to know. Just upload files and leave them there. I know, and it's like all of the commands are pre-intuitive. You can do statistics on a container. You can delete them. You can upload large files and chunks. I'm not going to do that, but we can download the file. And I think it's just Swift download, my container. You need to say what you're downloading or what and from where. And to output my file, to output the terminal, just dash o dash and it's going to output what's in that file and download it. Now to delete it, we will go ahead and delete my container. And if we do Swift stat, it should say that we no longer have anything. And all of the commands that I did are also available in the solutions guide on the website. So you should be able to upload as many containers as you like. Any questions about basic Swift usage? All right. Next up is Neutron. As a user, you will not be doing a lot of things with Neutron. It can get pretty advanced if you're an administrator. And all of the usage really depends on how your network is configured. So the basic commands that you should know is Neutron net dash show. Nope, that's not the one. List. And it will list available networks the same for subnet. And because these tables, they don't wrap very well and you want to view additional details, you can type Neutron subnet dash show or Neutron net dash show. And then a network name or a subnet name. Each network has to have a subnet if you want to use it. And here it tells me what my DNS name server is, the DHCP enabled, and the gateway that has been set up. Thank you, private cloud administrators. There is also a command here on how to create a new private network with a subnet. If you create a network, you will need to end want to boot a VM. You will need to provide which network to connect to. So I will skip this part. You can try this after we are done walking through all of the exercises. Now that we have covered Keystone, Nova, Swift, Neutron, we're going to move to Cinder. And you already are experts on Cinder in Horizon. And using it on a band line, it is not that much difficult. So let's see what we have right now. And it tells me they already have a Cinder volume that was created. And you may or may not have deleted it. So I don't know what our limits are for each user. You may want to delete it if you want to create additional ones. To create a volume, you will need to provide a type. So if you type Cinder type list, it will tell me that I have two types. If you are using this from the OVA, there is no type specified, then you don't have to specify this parameter. All right, let's create our first volume on the command line. Wait, what was the other one called? Is it going to be called the same? Yeah. So I don't want two of the same. So I am going to delete it. What I did here, I said I want to create a volume of name, my first volume. The number one that you see here is the size of the volume, and the volume type is Sara. And it automatically says that there's nothing attached. The status is still creating. If you're creating very big volumes, that may take a while depending on your cloud and your storage. So keep that in mind. And of course, for here, please do not create large ones. Because that will slow everybody down. Let's see if our volume is finally created. It errored out. Lovely. You have the same problem? Did someone create a very large volume? No, someone else. So sometimes, then there were errored out as some of the other open stack commands. It is still not perfect. So let's create another one. We will try to create a second volume. And this one also errored out. All right. So at this point, if you're having constant errors with your private cloud, you would call your administrator and say, hey, my cylinder keeps failing over and over again. And your administrator will say, well, that's because you are probably out of storage. Well, as administrator, I would look at the logs and tell you what is going on. Hopefully, there is a very useful error. If not, there's... They may have to do some detective work and see why it is failing. So it keeps failing and failing. So what I am going to do is create an SSD. You think that's going to work? Oh, excellent. We will try that. All right. So what Angela is saying is that I should become an administrator and show you what is out there. Because I have... Yes. There are probably half of them at errors. Some are available, some are still in use. Thank you, Angela. No. So the reason I am seeing all of these is because I became an admin by Sheer Magic. And I typed cinder list dash dash all dash tenants. As a regular user, you probably don't have access to this command or if you do, you will not list you all of the available volumes that have been created. Right now, I am acting as an administrator of this private cloud. It looks like everything looks like 5.0. I'm sorry? It looks like 5.4. Oh, yes. Has someone created size 500? No. All right. So we know who you are and we will delete them. I mean, as a user, that's what people will do. People always try to test the boundaries and see what's available. And if you administrate any sort of IT infrastructure, I'm sure you ran into this and seen this a lot of times. So if I wanted to see details of a particular volume, I would type cinder show and ID. And it's going to tell me who the tenant was, what type it was, status, and there's not a whole lot else available. Have you deleted? Can you delete all of them? Okay. While Angela is helping us out with the cinder, we're going to move on to glance because right now, you've seen the commands to create it. You have not seen how to attach it to an instance on command line, but we'll try to do that after everything is cleaned up. So Dana mentioned a little bit about glance, and glance is where all of the images are storage, the catalog, and you can create your own images and register and provide them to users. So you may or may not have a file. I think, Angela, they have files, right? The image files? Yes. All right. So if you go to the images directory on your terminal, you should be able to see some images, and all of them are hopefully very tiny. Okay. So you should have just one image. So to see what images are available, you can type glance image list. And where have we seen this output before? I typed glance image list. Have we seen this before? Nova image list, right? How is that possible? Well, both of them give you a list of images, except the glance command will give you more detail. And the same if we do glance image dash show and the image name, it will give you a little more information than when you did with Nova. So let's see what Nova would give us. So same commands or almost same commands for Nova and glance, except the glance one will give you more information about each image. To create an image, we're going to use the super long command that I encourage you to copy, because you have to provide all the information like name and disk format and whether it's public and where the file is. And this command has a lot more options. If you look at the help command, you will see all of the different options that are available. All right, no such file. Yes? All right, so we're already over time. I don't think there's anyone after us here. We will continue if you guys are interested. If not, make sure to take some handouts. Do at home at your hotel or in your free time. But yes, everything that we did is available on the class site. And the lab will stay available for at least a week. So you can try to do all of the exercises yourself. There is also PDFs with exercises and with solutions. So you're not stuck just looking and trying to guess. What is it that I have to do? Does anybody have any questions? I can go back and try to do more of the Cinder. Yes? I'm sorry? IPv6. Is it available in OpenStack? I believe so. No. Well, so you have to SSH into a server where OpenStack is installed. I think you could potentially install a Nova client and just source it and then connect through the Internet. So yes, you could potentially do that. Agla. For Glance, what's the difference between the disk format and the container format? Disk and container format. So I think right now, for OpenStack, you can just have the disk, the containers. I think that the Docker, are you talking about Docker containers? Glance. Oh, Glance. Okay. So we have a disk container and we have a disk image. The disk container, if you guys are familiar with OVFs, or something that actually, if you were to crack open a disk container, there's no data in it, right? It's just the information regarding the actual VM itself. Information like types of NICs, maybe perhaps a number of VCPUs. Typically in OpenStack, what we want to do is specify bear for that type of container. Another type of container would be like an AMI for Amazon compatibility. But in the case of OpenStack, what we want to do is specify bear. But in the case of OpenStack, typically we are going to specify bear for the OVF. The actual image itself is where the OS is. That's where the actual laid-down OS is. Bear just means generic. It means that it just, you just say bear. Typically an OpenStack. And also OVF is not currently compatible. OVF containers are not currently compatible with OpenStack. Okay. This vanilla OpenStack, regular openStack, you can't actually have it read an OVF file and apply those settings. Do we have any other questions? Do we have someone after us in this room? Yes? Yeah. Give yourselves a round of applause. Thank you so much. So the question was, can it be on day one of the next summit? Tweet at OpenStack and make that suggestion. I encourage all of you to tweet at OpenStack and make that suggestion. Seriously, it's a good suggestion. Anyone for coming? We'll keep the materials up. We will stay here and answer your questions for as long as there are any questions.


An astronomical object or celestial object is a naturally occurring physical entity or association or structure that exists in the observable universe. In astronomy, the terms object and body are often used interchangeably. However, an astronomical body or celestial body is a single, tightly bound, contiguous entity, while an astronomically or celestial object is a complex, less cohesively bound structure, which may consist of multiple bodies or even other objects with substructures. Examples of astronomical objects include planetary systems, star clusters, nebulae, and galaxies, while asteroids, moons, planets, and stars are astronomically bodies. A comet may be identified as both body and object, it is a body when referring to the frozen nucleus of ice and dust, and an object when describing the entire comet with its diffuse coma and tail.


Item number SCP-557 Object Class Euclid Special Containment Procedures As it is not possible to relocate SCP-557, research site 29 has been built surrounding it. Geographic and aerial surveys of the area have been altered to make it appear to be empty desert with no valuable archaeological or mineral features. On-site personnel have several tasks. To prevent unauthorized observation of, and access to, SCP-557. Despite its inhospitable location, several occult groups, including the... appear to be aware of SCP-557 and have shown an interest in it. Unauthorized personnel are to be taken into custody, interrogated, and dealt with appropriately. Anyone attempting to tunnel below level 5, or disturb the stone block in the floor of room 501, is to be terminated immediately. To continue to attempt translation of the records found in SCP-557. To monitor the area for SCP-557-1. SCP-557-1 should be assumed to be Keter Class, and is to be captured if possible, otherwise terminated. To monitor room 501, and serve as a strike team, should anything emerge from beneath it. Description. SCP-557 is an um-an-nar-era tomb, estimated to have been built circa 2400 BCE. On a gravel plain in the empty quarter of northwestern Oman. Investigation of the surrounding area indicates it may be part of the lost city of Ubar. SCP-557 was discovered in 1988, during an inquiry into the disappearance of a geological survey team in the area. Unlike similar structures, SCP-557 includes five underground levels, constructed primarily of sandstone, apparently used as an ancient prison and containment site. Although living quarters and weapons for approximately f***ing staff and guards exist on level one, the facility appears to have been slowly abandoned over the years, and empty since circa 300 CE. Only two skeletons were found on level one. A substantial library of records was found on level one, in a number of ancient languages. Only the records in Egyptian, and a final note left in Greek, have been translated. Levels two and three are stated in the records to be a prison for heretics and sorcerers, but appear not to have been used for up to 1,000 years before the site was abandoned. Level four is described as, a place for the abnormal. Skeletons resembling SCP-557 and SCP-557 have been discovered locked away in stone cells, confirming the intent of the structure. Level five consists of a 51.2 meter long hallway, filled with complex traps and deadfalls, leading to a single large, 21.3 meters by 19.7 meters by 5.4 meters, room, designated as 501. Although all of the traps appear to have been sprung or cleared, researchers should exercise caution. The door to room 501, anachronistically composed of ***, was found torn down from the inside. Based on the distribution of dust in this area, this event happened only approximately 20 years ago. In the center of the floor of room 501, is a partially buried 3.2 meter by 3.35 meter granite block, estimated to weigh 80,000 kilograms. The block is covered with untranslated runes. A similar, thinner block stands in the room and shows evidence that a living being, designated SCP-557-1, was chained to it, using chains from the same material as the door. No evidence of the continued presence of SCP-557-1 has been found. Translated records only refer to SCP-557-1 as the prisoner, with the exception of one reference in Egyptian 2, the bastard son of APEP. Addendum, translation of a note, found in the records room. I will write in Greek, so that any learned man who finds this place will understand. I am the last of the keepers, and I will be dead soon. The sands are taking this place, and perhaps it is for the best. The prisoner must not escape, and the gateway to the dark must never be opened. I do not think the gate can be moved, but who knows of the prisoner. Not even the gods could kill it, and it was only with their help that he was secured. Without the rituals, I do not know. Secure the door the best you can, and never move the stone. Item Number SCP-570 Object Class Safe Special Containment Procedures SCP-570 is to be contained within a reinforced steel containment locker. No personnel are permitted to wear SCP-570, and all subjects who have worn it during testing are to have it removed immediately afterwards. No personnel who have worn SCP-570 are to be given medical treatment for their hands, following removal. Description SCP-570 is a pair of cotton gloves. When worn, they will extend between 100 to 150 cotton fibers into the outer epidermal layer of the subject's hand. Removing SCP-570 after this point will cause extreme damage to the subject's epidermal and muscle tissue. Following initial exposure to SCP-570, these fibers will migrate throughout the subject's body, eventually establishing contiguous connections to 80% of the subject's muscle tissue. Subjects affected by SCP-570 are classified as SCP-571. Instances of SCP-571 are capable of controlling the actions of any living organism they have physically contacted, while wearing SCP-570. Subjects are connected to SCP-571 by several strings, which are produced from its fingers. These strings are not composed of the same material as SCP-570. Instead, they contain DNA and match the composition of the SCP-571's muscle tendons. With practice, instances of SCP-571 are capable of controlling up to 20 subjects at once, by extending multiple strings out to the affected subjects from their fingertips. Note that the SCP-571 instance controls the others by use of physical movement. Subjects will have to act carefully due to the potential of tangling SCP-570 strings when there is a large number of affected subjects. SCP-571 subjects appear to be endowed with some basic knowledge of puppeteering techniques. However, instances with a background in marionette use will be more able to utilize SCP-570. After bringing multiple subjects under their control, the SCP-571 instances and subjects will begin to seek out any gathering of prepubescent subjects and use the persons they have attached themselves in order to put on puppet shows. SCP-571 and its affected subjects will recreate any stories they know, which are easily understood by children, and usable with the number of persons they have under their control. These puppet shows may last from anywhere between one hour and several days, depending on the length of the story and the number of subjects involved. Following the completion of the show, all subjects will be released from SCP-571. Subjects who were under SCP-570's control will suffer no immediate side effects after being released, with the exception of a strong sense of longing. Because of this, many subjects will eventually try to take possession of SCP-570 and attempt to create shows of their own. Subjects will claim that they experienced extreme feelings of joy and belonging when performing and wish to give these feelings to others. This effect is not universal and will only manifest in subjects who previously displayed symptoms of depression and anxiety. SCP-570 was recovered from Uncle Papi's Magic Emporium, which was a magic trick in puppeteering business. The proprietor of the store had become an SCP-571 instance and used SCP-570 on the parents of children who came into his store. Following reports from local law enforcement officers after witnessing SCP-570, Foundation personnel were deployed and containment was enacted. As of 09-18, 1976, SCP-570 has been classified as safe. Addendum, Testing Log, 570 Test A, 609-19- Subject, SCP-571, 6D Class Subjects Procedure, SCP-571 was instructed to perform Cinderella using D-Class personnel. Results, Show was performed without incident, with overarching narration being provided by SCP-571. Analysis, Test was performed as a baseline for SCP-570's properties. Test B, 623-19- Subject, SCP-571, 6 Rabbits Procedure, SCP-571 was instructed to perform a reenactment of the book Watership Down. Results, SCP-571 used no dialogue in the play. When asked, it claimed that such an action would be unrealistic. Analysis, Test was performed to establish baseline for SCP-570's effect on animals. Test G, 819-19- Subject, SCP-571, 7 completely paralyzed D-Class personnel. Procedure, SCP-571 was instructed to use the D-Class personnel in a play of Peter Pan. Results, Play was performed by SCP-571 in the D-Class personnel, with SCP-571 providing all lines for the D-Class personnel, in addition to narration. SCP-571 was noted to have difficulty speaking following the test. Analysis, Later tests have shown that, once mute, SCP-571 will simply act out the motions of the performance without any dialogue. Test I, 19- Subject, SCP-570, 3 D-Class subjects. Procedure, Test was conducted for 6 days 7 hours. Results, SCP-571 and the D-Class personnel were provided with sustenance. However, all D-Class personnel were not able to eat while being controlled by SCP-571. Following 4 days of testing, all D-Class had expired due to malnutrition and exhaustion. SCP-571 continued using the cadavers in the performance, providing narration in a manner similar to Test G. After 5 days had passed, the tissue surrounding the strings began breaking down, and after 6 days and 7 hours, the flesh connecting the subjects to SCP-571 had decomposed and severed the connection. Analysis, N.A. Addendum 2, Notes on SCP-570 Fiber Composition Samples taken from the cotton fibers used by SCP-570 to link SCP-571 and its affected subjects have been shown to match the composition of initial samples taken from SCP-2991. Due to the possibility that this particular fiber composition may be partially responsible for the effects of both anomalies, anomalous materials analysis on samples from both objects is currently underway. Item Number SCP-592 Object Class Euclid Special Containment Procedures SCP-592 should be contained in Research Cell 1611e at all times, locked in a steel box in the middle of a frosted glass containment cubicle. Also in the cubicle are a table, two computers, a standard-sized computer scanner, an internal network connection port, and two pairs of visual distortion goggles, which must be worn upon entering the cubicle, so as to make SCP-592 illegible. The first computer serves as an analysis machine, the second as a custom firewall. All devices have been modified with specialized software and hardware, and the network port has been secured such that no device other than the firewall may use it. It is strictly necessary that the computers and scanner are turned off and unplugged after experimenting, and that they are only powered for the duration of the experiment. The front and back covers of SCP-592 are to be covered in black opaque tape at all times. The cell must be guarded continually to ensure that SCP-592 is not removed. Description SCP-592 is a large hardcover book which exhibits no external qualities that could be considered unusual, but which can cause delusions, psychosis, changes in physical health and appearance, or even severe wounding when read. It is titled Chronicle of the 20th Century, and consists of 450 all-color printed pages. It is reported that it has a printed cover, no dust jacket, with the title of the book, the publisher, and a selection of illustrations from within the text. The original cover is a deep blue. The spine contains the title and publisher name, and is left uncovered by tape. The cover page informs the reader that it was published by Interworld Press, 54th Street, Chicago, Illinois, in 1996. A company named Interworld Press has never been registered in the U.S., nor does the street list it exists. The text is a collection of newspaper clippings and short articles on major events, from January 1900 to December 1995. Much of the first half of the text agrees with recorded events, but at some point no later than the 15th of June 1956, a date researchers have termed the point of divergence, POD. The text begins to diverge from known history. These divergences become more common and acute the further away from the POD the text is. Subjects reading from the text before the POD report no ill effect, and generally comment that the text is well written and seems very accurately researched. Subjects reading from the book after the POD understand the passage read is accepted truth, and vehemently deny any suggestions that the text is in fact incorrect. The claims subjects make are often disturbing or shocking in nature. It also appears that a subject that has read passages from a certain year can recount events that are detailed in later sections of the book. It has been found that those born before the date which the test passage indicates and lived in or nearby the location of the event described may construct personal experiences built around the event and describe them as they would any other vivid memory. The subject will go to great measures to defend the reality of their story, often turning violent if under interrogation. Exposure to SCP-592 may alter physical characteristics of the subject and form with the events of the passage being read. This can vary from small changes in appearance or clothing to the infliction of severe wounds. For example, in one instance, a subject, D-94920, produced a scar during an interview stating that he picked it up during the data expunged. His widow, when presented with the scar, was surprised, stating she had not noticed the scar before. It has been found that once the subject discovers that the world is inconsistent with their acquired memories, they begin to feel that the present reality is an illusion, a dream, or a deceit, often stating malevolent or government forces are at work in maintaining the illusion. Subjects who reach this stage enter into a profound and chronic psychosis. All attempts to treat this delusion have failed. The exact effects vary. Date of passage read, before POD. Effects, no ill short or long term effects. Date of passage read, less than two months after POD. Effects, short term, confusion, no ill long term effects. Date of passage read, less than two years after POD. Effects, short term, confusion, long term, minor mental illness, development of ticks, nightmares, minor paranoia episodes, and panic attacks. Date of passage read, less than 10 years after POD. Effects, short term, confusion, violent episodes. Long term, deeply ingrained delusion formed, leading to debilitating paranoia, psychosis, and schizophrenia type disorders. Date of passage read, greater than 10 years after POD or earlier if subject forms a personal experience. Effects, short term, confusion, violent episodes. Long term, acute psychosis and delusions, crippling agnosia, becomes withdrawn, high chance of suicidal or homicidal behavior, severe risk of immediate but variable physical change in subject. SCP-592 was recovered during a narcotics raid in August 2006 on the property of Mr. White, the leader of a controversial religious group called the Church of the True History. Despite being in possession of SCP-592, Mr. White is believed to have started the church for financial gain rather than revelation. The owner may have only survived exposure from SCP-592 for almost two years because of his rampant drug use, which included methamphetamine, cocaine, and a host of opioids. Those psychedelics, especially DMT, are known to have been used and probably interacted with the effects of SCP-592 more than the others. He believed that his delusions came from his drug use, but noted that a year after exposure to SCP-592, he found himself turning to drugs more often to, quote, hide away from the truth, end quote. In custody and deprived of his usual chemical relief, the suspect became comatose and died a week later. The circumstances of the acquisition has led to proposals to test SCP-592 in combination with psychedelic drugs. Addendum 592A The chemical properties of SCP-592 have been studied by Dr. Grayson and the chemical forensics team. Dr. Grayson reports that samples were obtained by means of cutting small squares of paper from the book while wearing distortion goggles. The squares were small enough to contain no more than one word. Squares containing portions of illustrations were covered by black opaque tape as soon as extracted. Our results indicate that the chemical properties of SCP-592 differ very little from any other color publication. The paper primarily consists of cellulose from common woods, and the black and yellow inks are standard. It has been found, however, that some chemicals used in the cyan and magenta inks, while entirely known to science, are not normally used in the industry. An expert in inks and dyes has commented that the chemicals would be an inferior but acceptable substitute to those currently in use, if certain metal elements were much scarcer and therefore much more expensive than they are today. Testing Protocol SCP-592 is under no circumstances to be read by a human unless that person is a subject of an authorized test. SCP-592 is only to be analyzed by computer using the systems provided. The book is to be scanned on a per page basis using the scanner provided. The scanned image is then sent to the analysis machine. The scanner and other devices are modified such that they can be used while wearing the visual distortion goggles. Note, researchers must pass training course 305-S, intermediate Braille, and training course 10-E. Use of SCP imaging software before being approved to test SCP-592. The analysis machine is modified such that it contains and supports no non-volatile, permanent, writable storage devices, such that it never stores a copy of the scanned image that may persist beyond the analysis phase. The image is destroyed from the system RAM as soon as possible through standard secure memory flushing routines. The firewall is configured to study incoming packets for characteristics of properly processed output and destroys the packet if an insufficient amount of characteristics are discovered. This prevents the transmission of text or images that have not been sufficiently obfuscated. As SCP-592 is heavily illustrated, there are two analysis protocols. Analysis of Text The analysis machine uses industry standard optical character recognition, OCR, systems, to parse the text in the image and then destroys the image. The text file is then passed through a series of custom natural language processing, or NLP, routines, to summarize the text. The original text file is then destroyed and the summary is sent to the secure foundation Intranet. The NLP routines analyze the passage using statistical methods, incorporating databases of diverse English corpora, some details of other SCPs, a correct chronology of events extracted from various texts, and a severely limited referential network of other entries in SCP-592. Note, efforts to increase the degree in which analysis references other events resulted in an incident whereby data expunged, resulting in three researchers being euthanized. See document SCP-592... The summary is composed in such a way as to mitigate any possibility of exposure to the true material of the passage, but still provide useful analytical details about the event described. An example, SCP-592-SUMM-090777A. Note, lexical tokens from source databases are presented in all caps. Date, 7th of September, 1977. Location, Southern United States, 99% certainty. Type, newspaper clipping. Summary, the passage is describing human conflict. The human conflict is of an ideological or religious nature. The passage seems, 56%, to be lamenting in tone. The passage contains the numbers 2000, 1977, and 16. A relation to event SUMM-010777C and event R is likely, 78% certainty. It is certain, 98%, that the passage contains a reference to both SCP- and SCP- related incidents. Incident 592- loss of a limb following exposure to SCP-592 article on war. Analysis of images. SCP-592 contains around 200 illustrations. These are cropped from the scanned image as part of the OCR routine. The image is then subjected to a number of Fourier transforms and convolutions to obscure the resulting output from human recognition while simultaneously analyzing its structure and providing a summary of its contents by statistical analysis. Record of the original image is then destroyed. An example report, SCP-592-IMG-098. Date, 1st of April, 1963. Location, unknown bedroom with western furnishings. Type, full-color photograph.  With 100% certainty the persons in the image do not have facial features. Item number, SCP-627. Object class, safe. Special containment procedures. One class D personnel designated D-627 is to be assigned to SCP-627. This assignment is for life. As long as the class D is so assigned, he is rendered exempt from the monthly terminations. SCP-627 is to be kept in a stone basin approximately one meter across. Once daily, SCP-627 is to be removed from its basin so that lubrication may be applied to the basin. Once weekly, SCP-627 is to be removed so that the basin may be inspected for wear. The basin is to be replaced if it shows signs of wearing out. Testing on SCP-627 is currently denied to all researchers. Description, SCP-627 was brought into the foundation in December of 1932 by Senior Researcher AE, fleeing religious persecution in Germany. Senior Researcher E found SCP-627 during his work with the German government on their own SCP protocols and felt that it could be more useful with us. SCP-627 is a sphere made of unknown stone, flecked with blue of approximately three centimeters in height. When not in close, defined as skin contact or in clothing being worn, contact with a human being, SCP-627 rolls in a circle approximately one meter across. It will not avoid inanimate obstacles, instead rolling up and over any impediments. It will never attempt to go around impediments, and, if contained in a space smaller than one meter, will increase in speed until it has worn itself away out. When confined to a small space, SCP-627 is capable of breaking the speed of sound. When not confined, SCP-627 rolls at a speed of approximately six rotations a minute. Note, 1939. We need to figure this one out. If we can just understand how it does what it does, we could have an unlimited supply of energy. All the top researchers on it, stat, site supervisor JRO. Note, 1942. R, I figured it out. What to do with it? We simply, it'll work. Senior researcher AE. Note, 1942. We're moving forward with this project. As of now, good job, A. You've got a promotion coming. We'll be data expunged. Site supervisor JRO. Note, 1945. My God, what have we done? Site supervisor JRO.