Welcome to this session. I am Priyanka Bidla and today we are going to discuss about block diagram fundamentals and reduction rules. These are the learning outcomes of this video lecture. At the end of the session students will be able to represent the block diagram with transfer function and second outcome will be to apply the rules for reducing the block diagram. These are the contents of this video lecture. Basically block diagram is a pictorial representation of the cause and effect relationship between input and output of a system. It is very difficult to analyze the entire system as it is without breaking into small parts. So, to analyze such system block diagrams are used. This is the simplest form of block diagram. Here it is a single block with one input that is x and the one output that is y. A mathematical operation performed by that system and output is produced according to the input. The arrow indicates the direction of flow of signal from one block to another block. Now recall what is the transfer function of system. Now pause the video for a while and you have to recall the transfer function of a system transfer function. The system parameters are designed and their values are selected as per the requirement of input. Therefore, the performance of system parameters are expressed in terms of their output. So, we can write down system parameters are nothing but that is a gain. So, gain is equal to output upon input or Laplace transform of output to the Laplace transform of input. So, we can write down output is equal to gain into input. So, gain is nothing but performance of the system parameters. Then we consider here the components of block diagram. There are the four basic components. So, we see one by one the first is the signals. So, here this is the R of s and this is the C of s. R of s is nothing but reference signal and C of s is the controlled signal. So, R of s is the reference input that is a Laplace transform of the R of t and C of s is the controlled output. This is the Laplace transform of C of t. Second component transfer function of components shown inside the block diagram. Here G of s is nothing but transfer function of system input is nothing but R of s and this is the output is nothing but C of s. So, this is the representation of system. Then summing point here this is summing point one or more than one elements can added or subtracted at the summing point. Here R 1 of s and R 2 of s are added directly. So, here we get C of s is equal to R 1 of s plus R 2 of s. Suppose here the sign is negative then we can write here R 1 of s minus R 2 of s. By default if there is no sign then it will be considered as a plus. Then the next four component fourth component that is takeoff point this is a takeoff point. The point from which signal is taken for the feedback purpose R of s R of s R of s. So, these signals are taken from this point for the feedback purpose. Then we see the advantages of block diagram that the four advantages. So, first is the very simple to construct for complicated system. Then second we can write down the individual elements from the block diagram. Then third individual as well as the overall performance of the system can be studied using the transfer functions. And then the fourth is you can calculate the closed loop transfer function of a system directly by using the block diagram reduction rules. So, there are the total 10 rules. In this video lecture we will see the first three rules. Then these advantages of block diagram. Block diagram does not involve any information about the system. Then second energy source is not shown in the block diagram. And third one is nothing but it can be applied only for the linear time invariant systems. Then here we can calculate the simple form of closed loop system. For that we have to calculate the transfer function. All these signals are Laplace transform of the particular signals. So, R of s is nothing but reference signal Laplace of R of t. E of s is the Laplace of error signal that is E of t. Then B of s is here we can write minus and plus. It may be minus or it may be negative or it may be positive. The meaning of this is the feedback signal. So, feedback may be negative or positive. It is a Laplace transform of B of t. Then G of s is nothing but it is a forward path transfer function. And H of s is the feedback path transfer function. Feedback path means here the path indicates the flow of direction from output to input. So, this is feedback path and the forward means it is from input to output direction. Then C of s is the control output that is a Laplace transform of C of t. Here G of s and H of s can be obtained by reducing the complicated block diagram. So, from that diagram we can write these equations. So, E of s is equal to reference signal minus plus B of signal. Then B of s is equal to is the product of C of s and H of s. Then C of s is the product of E of s and G of s. From this you can write down E of s is equal to C of s divided by G of s. Then here that is B of s is equal to C of s H of s. So, put the value of equation 2 in the equation 1. So, we get E of s is equal to R of s minus plus C of s into H of s. Now, compare the equation 4 and 5. Here left hand side E of s and E of s are equal. So, right hand side are equal. So, we can write down this equation. After solving these equations we get the transfer function that is C of s divided by R of s is equal to G of s upon 1 plus or minus G of s into H of s. Transfer function is nothing, but output upon input. So, C of s divided by R of s we get this equation. So, this is the transfer function of closed loop system. And remember if there is a plus sign then this is a negative feedback. If there is negative sign then this is a positive feedback. Then we see the rules for the block diagram reduction. There are three rules for reduction of the block diagram. So, first is what any complicated system is brought into the simpler form. First we have to reduce the block diagram. Then second using proper logic of the system and value of the feedback should not get disturbed. And third we will now analyze some common topologies for interconnecting subsystem. Some common topologies are used for the reduction of the block diagram. So, we see the rules. So, rule 1 is associative law. Here this is the cascade connection of the summing parts. Here R 1 is given to this first summing point and R 2 and R 3 are given respectively. So, here this is a minus sign. So, R 1 minus R 2 and then this output is given to the next summing point.  This is the final output of this summing points. Now, in this figure you have to consider exchange of summing points. So, here we have to exchange the summing points. So, instead of R 2 here R 3 is there and instead of R 3 here R 2 is there.   So, after exchanging the position of the summing points then also we get the same output. This is associative law. Second blocks in series or cascade. The transfer function of the blocks which are connected in series get multiplied with each other. If the blocks are in series then we can get multiplied directly. If n blocks are there and the transfer function of respective blocks g 1 to g n then take the product of these blocks. So, it is represented by this equation. Consider example R of s is given to g 1 and here we get R of s into g 1 and this is applied to next block. So, here we get R of s into g 1 into g 2. This is the before reduction. After reduction in this case g 1 and g 2 are in series. So, directly take a product and we get the output R of s g 1, g 2 blocks in parallel. If the blocks are in parallel then directly added these blocks. Consider the sign. If there is negative sign then you have to consider the negative sign. Now consider an example here g 1, g 2 and g 3 these blocks are connected in parallel. So, directly added to at this summing point.  So, we can multiply with R of s and how to reduce this block? If the blocks are in parallel then added directly. So, here this is the equivalent transfer function of the parallel subsystem. Remaining rules we will see in the next video lecture. These are the references. Thank you.


Tonight's spectacle was made possible by Skillshare. The first thousand people to go to the link in the description will get two weeks of Skillshare premium free. Hello and welcome to Polyphonic's house of musical wonder and mystery. Come in, have a seat, and I'll give you a reading. Tonight's reading is one you may have heard before, or perhaps one you've even done yourself. For in rock and roll circles it's a rite of passage. It's the story of a conflicted hero, a tragic death, and a glorious rebirth. It's the story of one man putting it all on the line to be true to himself.  Tonight, my friends, we will be doing a close reading into Bohemian Rhapsody, a magic trick. With just two seconds of sound, I will make you sing. Unfortunately, that sound will be all of the song that I can play tonight. But please, listen along at home as we read into Bohemian Rhapsody. On the off chance, you're not familiar with Queen, and that sample didn't stir you into song. You should know that Bohemian Rhapsody represents perhaps the apex of the 1970s rock experiment. In a mind-bending feat, it somehow manages to take the transformative structure of progressive rock and shove it into a form that could be a radio rock staple and sell out arenas worldwide. Along the way, we get an operatic breakdown, a legendary guitar solo, and iconic lyrics that perfectly walk the line between grounded and cryptic. Over the years, those lyrics have remained a riddle. Guitarist Brian May has repeatedly refused to comment on the song, preferring to let fans find their own interpretations. But on the Queen video greatest hits DVD, he did provide some insight into the song. He said, I think that Freddie was certainly battling with problems in his personal life, which he might have decided to put into the song himself. He was certainly looking at recreating himself. Another musician close to Mercury, Tim Rice, was more straightforward with his own interpretation of the song. Speaking with Leslie Ann Jones, Tim Rice said, It's worth noting that the topic of Freddie Mercury's specific sexual orientation is not as simple as it might seem. It's well known today that Freddie Mercury wasn't heterosexual, but how open he was about that is unclear, and it's also unclear whether he identified as gay or bisexual. Personally, I don't think it's my place to speculate, so throughout this video I will mostly be referring to Mercury's sexual identity as queer. And now back to the main show. I don't think that by any means the only way to understand Bohemian Rhapsody is as a coming out story, but that's the reading that's in the cards tonight. Bohemian Rhapsody opens on a scene of a man confused, weighed down by the expectations of society. Is this the real life? Is this just fantasy, caught in a landslide, no escape from reality? To any who have struggled with feelings of queerness, of otherness, this is a sentiment that will no doubt resonate. It can be disorienting, and you can feel that the expectations of the world are weighing you down, pushing you around. But rather than living under the weight of that landslide, Freddie Mercury sings to open your eyes, look up to the skies and see. For Mercury, redemption can be found by opening himself up to the truth, by embracing his identity. In the next lines we see Mercury characterizing himself.  This speaks to the innocence and helplessness that Mercury feels in a world that he's unfamiliar with. And if we choose to read bisexuality into the song, we can also read this line as Freddie embracing that identity. The introduction ends on a reiteration of Mercury's helplessness in the world. Any way the wind blows doesn't really matter to me. The second movement of Bohemian Rhapsody was the first part that Mercury wrote. As far back as the late 1960s, half a decade before Bohemian Rhapsody would be released, Mercury was chipping away at a piece that he called the Cowboy Song. It's a fitting name given that the lyrics of this section play out with all the melodrama and tragedy of a classic western film. And it's worth noting that the archetype of the cowboy is one that has resonated with queer men for a long time. The cowboy represents a model of masculinity that isn't based around sexuality. It allows room for queerness. However, the life of the cowboy is also hard and isolating.  The verses that sprung out of the cowboy song are the most grounded of Bohemian Rhapsody.   The hero tells his mother to be strong as he prepares to face his fate, exile or a noose. Here we get a thread connected to the intro, the character's nihilism when facing the winds of fate. If I'm not back again this time tomorrow, carry on, carry on, as if nothing really matters. As with everything in the song, this verse is filled with potential double meanings. The idea of killing a man, putting a gun against his head, could also represent sleeping with somebody, especially given the phallic imagery of guns.  Coming out can feel like a fatalistic act, especially to those with families that might not accept them.  In the next verse, our protagonist is racked with guilt and fear for his impending mortality. He has shivers down his spine, his body is aching all the time, but he knows what he must do. Goodbye everybody, I've got to go. Got to leave you all behind and face the truth. With one more farewell to his mother, Mercury steps out to face his fate, gripped by fear of the consequences. I don't want to die. I sometimes wish I'd never been born at all. On those lines we launch into Brian May's iconic guitar solo, a musical passage that seems to represent a transition from one state of being to another and leaves us in the song's most famous movement, The Operatic Break. At first glance, this section might seem like a pile of nonsense, and Mercury has called it such before. But Freddie Mercury was also a keen opera fan, and with a close reading, many of his references begin to seem more deliberate. If we pull the pieces together, The Operatic Break seems like a kind of judgment before the hero is set off to the afterlife, or to be reborn. We open on a little silhouette of a man, perhaps identified in the next line as Scaramouche. The character of Scaramouche comes from Commedia dell'arte, a form of Italian theatre that developed in the 16th century. Commedia dell'arte consisted of whimsical, witty scenes containing a cast of stock characters that the audience would be familiar with. Scaramouche was a boastful clown and trickster, often partnering or quarreling with another character called Harlequin.  Harlequin is one of the most iconic Commedia dell'arte roles, and has endured long past the forms heyday. He is most often seen dressed in a checkerboard pattern, an outfit that Mercury himself would begin to dawn on the stage in 1977. To me, I think these two characters represent Mercury before and after he has reckoned with his identity. One of Scaramouche's defining traits is cowardice, something reflected in the operatic breakdown, thunderbolt and lightning very, very frightening me. The cowardly trickster of Scaramouche is Mercury's imposter syndrome. It's his old self trying to convince him to look away from queerness out of fear for the consequences. For Mercury and many other queer people, the consequences are tied up in religion. This is where we might find meaning in the repetitions of Galileo's name. Due to his scientific discoveries, Galileo was persecuted by the Catholic Church, a fate met by many queer people as well. Later in the section, we get repetitions of Bismillah, an Arabic phrase meaning in the name of God. This is spoken in response to Mercury's pleas of easy come, easy go, will you let me go. Mercury is begging for his life and his eternal soul. The operatic section ends with this fear stated plainly. Bealzebub has a devil put aside for me. In killing his old self and acknowledging his queerness, Mercury fears that he'll be damned forever, that he'll be shunned from society. It's a religious fear, and a fear that comes from living in a world that has systemically disenfranchised queer communities for centuries. Like Scaramouche and Harlequin, Freddie's inner selves are dueling with each other on a backdrop of fear and anxiety. But in the end, Mercury triumphs. He and his bandmates come through with explosive instrumentals. Freddie Mercury embraces his true identity and we enter the rock section. Mercury has realized that the issue is not his queerness, it's the society that rejects his queerness. Instead of cowering from that society, he faces it head on with rage and defiance. So you think you can stone me and spit in my eye.  When we read Mercury's queerness into the song, the line about stoning becomes particularly powerful. Stoning has been a favorite punishment of Abrahamic religions for centuries. But in the end, Freddie decides to stand defiant of any and all expectations that a hateful society might have of him. He chose to embrace his true self, and he became an icon for it. The last movement of the song ends where we began. Freddie Mercury sings, Nothing really matters to me. And while the words are the same, the meaning is different. In the intro, the sentiment brings fear and pressure. But in the outro, it's a statement of peace and freedom. Mercury has realized that in the end, people's minds are not going to change. And his own identity isn't going to change. So there's no use hanging on in fear. Armed with this knowledge, Freddie Mercury completes his magnificent transformation and ascends to rock godhood. And with that, good friends, we finish our reading. I hope that it has been enlightening for you. And I hope that perhaps you may have seen yourself in the cards. I know that I did. If you were entertained by this evening's spectacle, please subscribe to get word of the next show. And if you weren't, if the reading didn't resonate with you, well isn't that the beauty of a great song? After all, it's not what's printed on the cards, it's what the dealer makes of it. If you were enthralled by tonight's show and found yourself wanting to learn your own tricks, may I recommend you try out Skillshare. Skillshare is an online learning community with thousands of courses on all sorts of topics. If you want to learn to do what I do, a great place to start is Jake Bartlett's Animating with Ease and After Effects. That course taught me how to properly ease my keyframes and really help me step up the quality of my videos. Or perhaps it's not the technical side of things that you need help with, but the personal. If that's the case, you should check out Emma Gannon's Unlocking Your Potential, Five Exercises to Build Creative Confidence. That course will teach you to create structure, find confidence and overcome your hurdles in any kind of creative pursuit. If any of this sounds interesting to you, you can try it out absolutely free by heading on over to the link in the description. The first thousand people to follow that link will get two weeks of Skillshare free, and after that it's less than $10 a month. I've personally learned a lot from Skillshare and I know that you can as well. So why not go give it a shot and learn something new while also helping support my channel? Thank you all so much for watching.


Good morning everyone. Good morning. Good morning. Good morning. Thank you for being here bright and early and on time. It's good to see everyone. Anyone go to the party last night? Anybody go to the Rackspace party last night? How was it? I missed it. It was great. I know the venue looked really nice. We were here having a good time. We had a party amongst ourselves. All right. So yeah, great time here.  That's the course you're in. All right. Hands-on, which means hopefully you have something to put your hands on. Hopefully you bought a laptop, a machine of some sort because we're going to dive in and actually get to use Nova and get to experience that. Quick survey before we jump in. How many of you all have actually used Nova before? You've had hands-on experience with Nova. So what do you guys do? Come here to teach the class? All right. Okay. So we expect each of every one of you. You've been knighted as tutors. So we expect you to help your neighbors for those who may not have used it before. So feel free to move around and help folks who are using this. All right. So before we get started, did want to do a few introductions. Just so you know the folks in the room that are going to be here to kind of help you out and walk you through this stuff. Okay. I'm going to start here with the gentleman to my left here. This is not this left all the way to the left. This is Mr. Byron McCollum. Say hello to the people. Hello. That's his speech. All right. This is Byron McCollum. He's one of our senior instructors at Rackspace. His job is to fly all over the world and teach people about OpenStack. So we're very happy to have him here today. He is the wizard behind most of what you're going to be seeing here today. So if stuff goes really, really well, he did it. If stuff goes really, really bad, he's going to blame the rest of us. All right. So there you go. That's Byron McCollum. Also over here I have Mr. Phil Hopkins. Phil Hopkins is also one of our senior instructors. Like Byron, he flies all over the world, teaches this stuff to folks. Say hello to the folks. Hello, everybody. He had at least four words. All right. Good job. All right. Phil Hopkins teaches our OpenStack Fundamentals course as this Byron. Phil also teaches our networking course. So our course on Neutron. Phil created that course and teaches that course. So if you want to hit him with hard questions around Neutron, he's more than willing to take those questions. All right. He's also got just about every red hat certification there is. So if you have any red hat questions, unless you work for red hat, you can talk to him too. All right. And then also we have over here Mr. John McKenzie. John McKenzie is another one of our senior instructors. Hello, everyone. It's good to be here. Yes. They're getting longer and longer. These guys do talk.  All right. He's one of our seniors instructors also teaches fundamentals and the building cloudy apps course that we have. So he has a software development background. Sony software developers interested in APIs, how to make apps cloud aware. You can ping him with questions as well. Okay. And then I'm Tony Campbell. I keep the trainers happy. That's my job. So I just try to make sure they are on the road teaching and are happy. And so the four of us together here from Rack Space. You're going to help with the hands on Nova session. But before we go too much further, I wanted to introduce some dear, dear friends of ours who are joining us in this venture. And actually none of this would be possible without this team that I'm going to introduce in the back of the room, acting like he's. Yeah, there he is in the back of the room acting like he's working hard. Mr. Young say song in the back. He's from AMD C micro. All right. We also have Vince Gonzalez right up here in the front. All right. And then I'm going to turn it over to Pete. Let me get it right. You must be young man. I'm sake, man. I'm weak. This is Pete. Pete's also from AMD C micro. And we want to give Pete a chance to kind of greet you all and share some things with you about our session today. So thank you all. And that's yours. Thank you, Tony. And just real quick before you guys get started here, we want to let you know what made this possible. What's your training running on? It's running in a data center. Where is that data center that data center is in the back of the room? Wave young say he's if there's any problems, if you file a ticket, hardware needs to be replaced, young says there to do that for you. So we've worked with Rackspace to put this together. Essentially, our box is a data center in a box. You can run all of open stack in the box. What is the system? It's a 10 R U chassis that has 64 to 256 power efficient servers. It's got network up a link cards, a shared storage controller. You could expand that storage to over five petabytes and we've got a high performance fabric tying it all together. And that's what makes this open stack deployment possible. I won't spend a lot of time telling everybody about that.  But if you're interested to learn more about our chassis, come and see us. Vince and young say and myself will be here after the after the training to answer any questions. Please go to the back of the room, take a look at the box, see what you've been running your training on. And if you want even more details, come and see us later today. We're sponsoring the developer lounge. If you're an active technical contributor, you'll be able to come into the lounge. You'll be able to talk to us. You'll be able to touch it and we'd be happy to answer any questions. Thank you guys. OK, good deal. All right. So once again, thank you to AMDC Micro for helping us pull this thing off without them. It would not be possible. If you get a chance, I would recommend during the time, if you walk back there with young say and take a peek at what this thing is running on, it's pretty cool, pretty impressive device. So I'm trying to buy one, but my corporate card won't let me slide it. But we're working on that. All right. OK, gang, let's go and get started. All right, I'm going to give you some instructions. Here's where this is going to work. I'm going to give you some instructions on how to access our lab. OK, also how to log on to the data center back there into the cloud. And then we're going to give you some instructions that you can run and actually get Nova working. And then what we're going to do is we're just going to surf around the room and kind of help you work through these exercises. Every once in a while, we may jump up here and show you something on the screen to make sure everybody's on the same page.  If you have a question, if we're not coming to you quick enough, throw a shoe that usually gets us there quicker. And whatever you need, we're here to help and kind of get you that experience, hands on experience with Nova. All right, you want to do this part? All right, so I'm doing this part, but he should be doing this part. OK, here we go. You play Vanna. All right, so there's three things we need to we need to share with you before we get started. Three things we're going to tell you about the Wi-Fi in order to get on to our lab. I'm going to tell you about the credentials you need in order to log in to our OpenStack cluster and then instructions for executing different Nova commands out there. OK, so let's start with the Wi-Fi. All right, we have a Wi-Fi running under the SSID of Rackspace. Password is also Rackspace. So if you want to do this hands-on lab, you need to be on Rackspace, Rackspace, all right? This is different from the conference Wi-Fi. This is an internal closed Wi-Fi that's connected to our C-micro back there, all right? Rackspace, Rackspace. What's the SSID? All right, what's the password? All right, y'all are with me, good. OK, you are in luck. We prepared for about 120 people, all right? And we're a little shy, which means everybody can play, all right? So we got 120 accounts, so there's plenty for everyone. We were going to say feel free to share with a friend if we had more than 120 people, but if you want to take two, go ahead and take two. So there's plenty of space there, OK? So the team right now is handing out little slips that look kind of like the one you see on the screen up here, OK? Each of these slips will give you credentials to log into the cluster. You're going to notice your username in the gray box, and in this instance, sorry, on the camera, my username is right there, OK? And then the password, and your password will be right there. Use the one that's on your slip, though. Don't use what's on my screen. This is just an example. Use what's on your paper slip, all right? Did everybody get one? Got a couple more over here. If you need a slip, let us know, OK? You're going to use the IP address as well that you see on your slip, not the one on my screen, but the one that's on your slip, your IP address. And then once we get you logged in, if you want to actually hit Horizon on that server, you can use the IP address that is on your slip. So far so good? Wi-Fi trouble? Right here? OK. The Wi-Fi does not have an internet connection, so I know Windows likes to complain about there is no internet connection. It's a private network, OK? These guys are awesome here, see? Whoa. Now I can point. Sorry, I'm excited about it. I don't know if this is great. I don't have to run down there now. All right. Anybody else have problems getting onto the Wi-Fi or connecting to their server? Excellent. OK. So one last thing we need to share with you is the instructions for things that you can do on NOVA. All these instructions are going to be located at training.rackspace.local. Training.rackspace.local, there'll be a PDF there. And in that PDF, we will have the instructions for the rest of our session this morning. That's training.rackspace.local. That is available on the Wi-Fi network. You don't have to hop back on the internet, OK? Great point. Thank you, buddy. You're welcome. All right, let's roll. I'll put that back up just in case anybody missed it. Questions? Two questions here? Question? Yes. Rackspace. The Wi-Fi password? It should be on there. Yeah. Going to this IP address? You need help? So we'll do some of the exercises up on the projector in a minute. As soon as we kind of help everybody out. Be right there. If you are having problems resolving to training.rackspace.local, if you're having problems resolving to training.rackspace.local, try <IP_ADDRESS>. Anybody else having issues logging in? Yeah. Did you get a slip? Did you get a piece of paper? Yep. The one that says Horizon is going to be the dashboard. The other IP address is the one you'll SSH into to run the command line clients, OK? Oh, for this, <IP_ADDRESS>. Should they be able to SSH by now? Yes. Got one that's hanging. Were you SSH into .10? OK. Same thing. And you're on our Wi-Fi, right? But you all work for the same company, right? Yeah, I probably won't be able to back out the security on your machine. If you can see if you can get to Horizon, or if it's just the PDF that's blocking, it won't, Horizon doesn't work either. OK. Oh, you need one? OK, one second. Let me get that. <IP_ADDRESS>. Yeah, across there. We just want to make sure that that server's up. I think she's got a pretty quality of her laptop. Does anybody need login information? They not have one? Yeah. I don't know. I don't know. Right. Everybody will see it. Is that in your way, bro? Oh, no. You're still starting out. OK. Yeah. Everybody have login credentials for those who may have just walked in?  Yeah, so here's the way this works. For those who want to go at their own pace, you're more than welcome to get ahead of us and start to execute these exercises. But Byron's going to pull it up on the screen, too, if you want to follow along. So whatever you're most comfortable with, you can stay with us for a guided tour or you can go off on a journey on your own. For those who just walked in, you can go to the Wifi network. SSID that is broadcasting is Rackspace. The password is also Rackspace. Once you get on that Wifi network, you'll need a little slip of paper that has your login credentials. John McKenzie in the center of the room there has those. If you need one, just raise your hand. And those will allow you to log into our cluster. Once you've logged into our cluster, the instructions for using NOVA, this PDF you see right here, is at training.rackspace.local. Or you can use the IP address, which is <IP_ADDRESS>. And in just a moment, our tour guide, Byron McCollum, will give you a guided tour through these NOVA exercises. Okay, so let's go and dive in here. The first thing we're going to do is after you've connected to the Wifi is we're going to SSH into one of the nodes in the back of the room. So this is going to give you access to the OpenStack clients. So we're going to run through a lot of the command line tools first. And then we're going to also take a look at the dashboard. So let's go and start now. The first thing we need to do is you're going to pull up either a terminal, if you're on Mac or Linux, Windows, something like Putty, Secure CRT, some type of SSH client. Okay? And we're going to SSH in. If you have your little slip here, it's going to have your username and password. It'll also have an IP address. That's the IP address you're going to SSH into. That's the server. So for me, that's going to be <IP_ADDRESS>. You may be on .3 as well. You may be on some other node. So I am OpenStack 1 on .3. And we're logged in. We also have in your home directory a RC file, an OpenStack RC file. This has been created for you. All you need to do is source it, and then you can start using the OpenStack command line tools. So that file contains all of our credentials. It's going to prompt us for the password, but it has everything else in it. So if we just take a look at that, we can see we have our auth endpoint, our tenant name, and then it prompts us for our password. So I'll go ahead and source that. And then it's going to ask me for my password. All right. And then to just verify everything is working, I can run something like glance, image-list. And we should see one image already registered for us. Okay. Is everybody able to do this? Anybody have any issues logging in, sourcing their credentials, start using some of the command line clients? Explain a tenant. Sure. A tenant is a way inside of OpenStack to kind of compartmentalize or segregate resources. So some people like to think of them, they have several names. There's project, there's tenant, there's account. But basically what it is, it's a way to organize or segregate resources. So if you're different departments inside of a company, those may be separate tenants or projects. If you're in a template cloud or multi-tenant infrastructure, they may be different customers. Or you might use them for different environments or different teams within your company. Templates? It's not a template. It's just a way of organizing resources. You can think of them like groups. So if we go back and look at our exercises, we can go ahead and start kind of going through here. So we've already done our first one of all the images that are registered in Glance. We'd like to inspect one of those images, see a little more information about it. We can do a Glance image show. See if I can put this here in my pocket. That works. So Glance image show is going to take an image ID. And we can get that from the image list. I'm getting a lot of latency here. And it's going to tell us about that image. So Glance is a Cirrus image. It's a QCOW 2 format. It's a very small kind of Linux image. It's used a lot inside of OpenStack for testing. It boots up really quick. Has all the basic plumbing to test things like cloud in it and network connectivity and things like that. So one of the first things we need to do before we can really start up an instance of quantum. Formally known as quantum. In this case, the command line tools are still named quantum. So we'll be using those. But just know that quantum is the same thing as neutron. It just got renamed. So the first thing is a quantum net create. That's going to create us a private network. So this is a tenant network. It's isolated from any other tenant network. Right now what we've done is we've provisioned system users on all of the compute nodes. So everybody has somewhere to log into. Normally that's not something you would do in a public cloud environment or in any cloud environment. Usually your end users don't access to the infrastructure. Here, just for the training lab purposes, because we wanted a known environment with everything installed in it. So we may have some saturation on our network here. So if you're having problems connecting to the Wi-Fi, let us know. So I'm going to go ahead and create a network with a quantum net create. And then we can use a net list and a net show to kind of view those. You get to name it however you want. It's just a label. So I like to call this one private. I'm going to call it log-in credentials for horizon. Same as on the paper. It is the actual same one as the paper. SSH credentials are the same as the Keystone credentials. Thank you very much. So I've created my network here. I'm also going to create a subnet. So the subnet is basically going to be your block of IPs that you'd like on that private network. So we'll do a subnet create. And then you'll just tell it which network it should be a part of. And then also the actual network citer that defines the size of the network. It's a quantum L2 network. Neutron. Sorry. We're having some... Byron, may I do a quick commercial? For those who may have just stepped in, we have a Wi-Fi that we're trying to do at Rackspace. Is SSID? Password is Rackspace. It may be getting saturated a little bit. Once you log on to that, then you need a little paper slip that has your credentials, your username and your password on that slip. So I'm going to create my subnet here. Give it a name. Very creatively private subnet. I'm going to use the UUID from the network I previously created from the NetCreate command. And then the citer the size of the network that I'd like to create for that subnet. And there we go. So we can see some information. Whenever you create something in Nova or Quantum you usually get some feedback. A little bit of information. So we can see the allocation pools, the number of IPs available on that subnet. Whether we have DHCP enabled what the gateway is whether it's IPv4 or v6, things of that nature. So I've got my network and I've got my subnet. And we can boot our first instance now. So to do that we need two things. One of them is we're going to need an image. We need an image ID. We also need a flavor ID. If you're not familiar with what a flavor is basically it's a it's a predetermined collection or predetermined grouping of resources. Things like a certain set of amount of memory, a certain number of vCPUs, local storage, things like that. And we can see a list of all those flavors and images with just the Nova image list and Nova flavor list. So we've got our one image what we've seen before but we also have our flavors here. There's two different ones. We've got a tiny which is 512 megabytes and we have an extra small which is one gig. The disk doesn't it's unbounded so it doesn't have a fixed size. It'll be as big as our images so that's why it says zero. And so with those two items we can go ahead and boot our instance. So I'll do that right now. So we need the image ID and the flavor ID. So I'm going to do a extra small here which is one gig. So flavor ID seven and the name of our instance. So my instance. And then we're going to get a response here so Nova accepted our request and we see a little bit of information about it and in the background it's going through the process of actually spawning and building that instance. So we can do a Nova list here and we see our instance is active and we can see its IP address. And again we can always drill into any resource information about it with a show command. So Nova show and then the instance ID. So a couple of tools that are very handy. One of them is the console log. So this is the log the boot log if you will. Basically what you see on the screen whenever you boot a server and it goes through and there's a bunch of stuff that flies past the screen you can get access to that log. And to do that it's just the Nova console log. So what is a flavor ID? Or what is a flavor? Okay well a flavor is basically it's a predetermined set of resource combinations. So basically you can think of it a menu. It's a set menu. You can spawn servers of these various sizes. You know a certain amount of RAM, certain number of VCPUs, things of that nature. If you do a Nova flavor dash list it should be the far left column. So we're going to do a Nova console log here with the instance ID. Question, comment here Byron? Yes. You can use the name. Not every command will accept the name. Also there is no requirement that names are unique. So if you name two things the same name and you try to use the name to reference it, Nova or some of the other clients will actually say hey there's more than one thing with this name so you're going to have to go use the ID instead. You can use the names as long as they're unique. So we can see our console log here of our instance. You can get that from doing a Nova list. Or again you could use the name. So that's the console log. We can also pull up a VNC connection to our instance and that's a nova git-vnc-console and then the instance ID. And on the end of that we need to tell it what type of VNC it is. In this case we're configured for no VNC. So question Byron, is there a way to use the VNC console without using that ugly ID hash can I use the name? Yes. Simple answer right? It's a man of many words. Yes. In most of OpenStack you can use the names instead of the UUIDs if you make sure the names are unique. Otherwise it'll just come back and say there's too many things with this name so I don't know which one you were talking about. Okay, it kind of bails. I don't know what your password is. Oh yes, yes. Yes, the password for Cirrus. Cubs win. Smiley face. So we have our no VNC URL here and we can copy that and then open it up in a browser and that's going to be an in-browser VNC client. Now you'll need a relatively modern web browser to use this VNC client. It's built using HTML5 canvas. So all the drawing is done in the browser with canvas. It uses web sockets to communicate with the VNC proxy back on the server and all the client side is done in JavaScript so the VNC protocol is kind of impressive. So we'll just paste that in here. Nova boot dash dash image ID or the dash dash image? Is it dash dash image? Yeah, I'm having some serious latency problems now. I am pulling up the VNC that get VNC console. I'm going to let that run in the background. That's taking a while. Okay. So that's pretty much the basics. Pretty simple to boot up an instance. Just a nova boot. You're going to specify a flavor and an image and give it a name. It's not an extension. It's something that you install. So there's a nova no VNC proxy and there's a package called no VNC. Yep, it sets it all up. It's also integrated into the dashboard. So if you pull up an instance in the dashboard you can click on console and it'll pull up the no VNC console right inside of horizon. Okay. Let me attempt this one more time here. There we go. Was able to pull it up now. So we have our VNC access to our instance here and I can go ahead and log in. So the username is Cirrus C-I-R-R-O-S password is CubsWin Smiley face without a nose. CubsWin colon close parentheses Smiley face without the nose. It also says it on the console when you pull up VNC. So that's nova. We also have sender setup so we can attach some additional storage. So sender is the block storage project inside of OpenStack and the flavors come with a certain amount of storage, local storage to run the instances on but if you want additional attached storage that's where you would use something like sender and we can just do a sender create and specify how big of a volume we want to create in gigabytes and then we're going to give it a name. Apologies for the Wi-Fi folks. Yeah, it's hurting me too. And then we can do a sender list and see our instance or sorry, our volume here. We see the size whether it's attached to anything status so it's available right now it's not attached to anything. So let's go ahead and attach. To do that we actually need to use a nova command instead of a sender command. It's nova volume-attach and then we're going to need two things. We're going to need an instance ID so one of our running instances we'd like to attach it to as well as the actual volume ID. And then the last little bit is the device inside the guest you would like that volume to appear as. We've got KVM configured to just automatically assign that based off the next available one and use auto for that value. So quick commercial, if we've lost any of you all completely please let us know. We will come around and catch you up and probably do this a couple of times and make sure everybody gets through John right here. The volume name it's you can pick anything that says name is something that you get to name it. Okay? Yes. Right, you get to think of it as like a USB drive or a USB thumb drive it's not shared storage so we can't take it and attach it it's not multi-attach. So I can't hook it to multiple instances but I can unplug it from one and then plug it into another. So it's persistent storage. If we destroy the instance the volume data and everything on it persists. So yes. Hey Vince, can you do me a favor? I'm right here, he can't see me. Can you take a look at <IP_ADDRESS> tell me if she's alive. So what auto means is certain hypervisors let you specify the device name inside the guest so like in Linux, dev, you know, VDA, VDB, etc. If you do auto it takes the next available one so you don't have to actually know what's already in there and go specify it. Some hypervisors don't let you support specifying it. So in that case you just use auto. Alright. To create it, it shouldn't take very long. Yeah. How big did you do? Yeah, no, it should work. Alright, so at this point let's go ahead and let's try something different. So we're going to switch over to the dashboard. On your piece of paper you should have a URL for horizon and you can use the same credentials that are on here, the username and password to log into horizon. We'll see if we have a little bit better experience using that. Having a lot of latency issues using SSH. So inside of here, the first thing we get dropped onto is just the overview page. How many people just by show of hands have not really used horizon before? Okay, so a good number of people. Alright, first time. So I'll go and just kind of talk through this. Again, you're going to see the overview. We see a little bit of information about our quotas or how many resources then we've been granted or allowed to use in the system and how much of those we're actually consuming at this point in time. So for this demo we've set up for each of you the ability to spin up 10 instances 10 vCPUs 10 gigs of memory 10 volumes, 10 gigs of local storage or volume storage. And if we just kind of go down the left-hand side and see if I can make this we can see our instances here. So here's the instance I created from the command line. We see it's IP address and some information about it the flavor that was used. It's current state. We can click in on it. We've got some more details here. We can go into the log. So that's going to be that console log that we did from the command line. And then we can also pull up the no vNC or the vNC console. We can also go down here and see all of our volumes that are created. We want to create a new one. We can do that from here. A little bit easier in the dashboard. So here we just give it a name and the only required fields are name and size. So if I want to create another one we'll also get projections of our quota usage. So as I change the amount of gigabytes that this new volume will use we can see our quota start getting filled in. So the green is basically going to tell us new resources we're about to consume and if you go over a quota then it'll actually turn red. So here it's saying that we're trying to build something that's going to put us over our quota so it won't allow you to do that. The type is a way of just labeling volumes. So for instance when you provision a volume it's just going to be a raw block device, it's unformatted there's no partitions, no file system nothing on it. So types are a way to indicate, oh this is an EXT3 volume or NTFS or not NTFS, FAT32 whatever. So there's none in there. So there isn't a way in Horizon but you could do that from the command line. So there's a sender type create I think it is and you could create those. Yes. The build request will eventually time out and then it'll go to an error state and then you could submit a delete request to terminate. But I'm not sure if there's a way to kind of force it to say if you've got something that's out there being processed to just kill it and it does that. I'm going to jump down a little bit down to our network. So we created our network previously we can see that here our private network we can also see the subnet on it and if we click in on that network again we'll see those subnets we can create additional subnets on that network we can create additional networks and if we go down to the network topology there's a nice little graph here about kind of showing what we have here we can see our private network we have one instance attached to it. We can see the IP address, the name of the server things of that nature. But we also have another kind of special network out here which is called an external network basically it's a public network that gets us to outside the cloud environment. So this might be the internet it might be another network inside of your data center it might be one of those things of that nature. So what we can do is if we go to routers we can create a router and uplink our private network to that external network. So we'll go ahead and create a router give it a name and if we go into router click on its name we're going to add an interface because right now we have a router but it's not attached to anything it's just kind of floating out there and we're going to start plumbing things together. So we're going to add an interface to our router and we're going to see a list of our subnets so we can go ahead and pick one of those subnets. Now if you had different subnets on the same network normally they wouldn't be able to route between them. So we're on different subnets. By creating a quantum router and attaching interfaces for those two subnets we're able to route between them so we'll add our interface for our subnet and if we go back to our network topology we'll see we have a new router right here but again it's still really it's not doing anything for us what we want to do is take that router and hook it to our external network so our instances can get out so we'll do that go back to my router and from a router list there's a set gateway and that's going to ask us well which external network would you like to set the gateway for? We only have one which is our public network it's kind of a shared network I've already created so we'll say set gateway and there it is and when we go back to our network topology we can see now that our private network is now gateway has been set to the external network yes I set that up yeah slightly different process for creating that it's still a quantum net create but there's a couple extra things you tell it this is an external network that's basically shared by everybody that only routers can attach to it things like that also generally you're going to disable DHCP because you're not having anything using DHCP attached to that network directly so alright so now we've got our instance on our private network we've got a router the gateway is set to that external network so that instance should be able to get out to that external network so I'm going to attempt to pull up VNC again we'll see if it's behaving a little better okay so one other thing our instance is able to get out now so it has outbound access to that external network but it's still on that private network and we have no way for traffic to be able to get in to that instance so if we want to selectively allow that so the way you do that in OpenStack is what's called a floating IP these are generally going to be public IPs and the way it works is that I've created a pool of these IPs so I have a set of IPs that are available for public access and as a user you'll go in and say I would like one of those IP addresses to allocate one of them so it'll come out of the pool and the ownership will be transferred to you and then from there you can take that floating IP and say I would like to associate it with one of my running instances so what gets set up is effectively a NAT translation so any request, any that come into that floating IP will actually get forwarded to the private IP on the private network so we've effectively allowed those instances, that floating IP never gets configured on the instance it's just a NAT rule on the network node so to do that we will go into access and security maybe, I dropped off again wow what happened to the signal oh I'm up there, ok let's try this again the way floating IPs work, you know how we created a network and then we created a subnet and there is where we specify a cider or pool of IP addresses you do the exact same thing, as an administrator I'll go create an external network and I'll put a subnet on it the cider I specify is going to be the IP addresses that will be handed out as floating IPs yeah I'm having some connectivity issues here again yeah we're all hitting that we're hitting that wi-fi loveliness question here the issue is all the other high power wi-fi that's overpowering it, I think it's like running on every single channel there's nowhere to hide alright so I was able to pull this up under access and security there's going to be a tab here that says floating IPs and we're going to allocate an IP to my project or to my tenant so I'll click that, it's going to ask us which pool we would like that IP to come from in this case it's going to be that public network so I will say allocate IP and here it's handed me an IP address in this case it's 192.168. 3.4 and so right now I've basically just taken ownership of that IP address now I want to actually set up the connection between that public IP and the private IP of my instance so to do that we'll just say associate floating IP it's going to say which floating IP will I only have one and then we're going to select what is known as a port a quantum port a quantum port is basically a you could think of it as just a virtual interface it has a MAC address and therefore it has an associated IP address so we say which one we want in this case this is the instance I spun up earlier and I'll say associate and that's it so we would be able to get in to that instance from the external network the public network the one that's shown here the floating IP can you on the external side probably not because there's a lot of stuff that's set up in IP tables to route the traffic to the actual private IP address so if you're just handing out random IP addresses to things that are attaching to that external network the plumbing is not there to actually make it all work well it's going to take everybody offline I'd rather not apologies for the wifi there's a clear channel but then we have to boot everybody off yeah we're getting crushed for the volumes here this is that attachment so I showed creating attaching is just as easy so we'll find our volume we'll say edit attachments we're able to well my instance is rebooting right now but we'll be able to choose our instances any instance that's running and it would attach that volume we would still need to log in to the guest to the instance and mount it format it partition it things of that nature because it is just a raw block device except for all the connectivity issues anybody have any other problems I know that's a huge problem the wifi? no it's not rebooting 14 is not it's probably because it's the regulatory domain is United States but we're not in the US anymore so yeah I wanted to both of them up here for those who may have joined us late allow me to bring up the speed on a little bit about the hardware that we're running this on why Byron reboots our wifi routers so we're actually running this on an AMD micro device which is located in the back of the room can I open it then everybody listen everybody listening are you listening stand by 1, 2, 3 there's a data center back here basically that's been quiet this whole time so everything you guys are running on is running off this awesome AMD micro back here 10U chassis 64 servers in this puppy not the wifi not the wifi but the wifi the wifi didn't come from cmicro but when you get a chance if you want to come back and take a look at this before you leave you're more than welcome to do so vince up front is the master magician behind this thing so he's got questions oh is that what did it the vnc yeah that makes sense yeah so maybe I won't do that hey vince you're getting questions back here bro yeah oh you want to see it through the GUI yeah I'll show you that it's under access and security and then there's the security groups here so we can either edit the default group no we haven't done that yet yeah you can go ahead and do it if you want yeah it's ingress only seems to be running much faster now I can't take it alright so I've got my instance up and I've set up my security group rules so we're allowing ssh and ping through and I've associated my floating ip here to my instance so I should cross fingers be able to access my instance through its floating ip so I'm just going to open up a new tab here again this is on my mac not in the actually logged into the open stack server and of course time out your floating ip is working yeah dashboard did you attach it but you attached it right yeah yeah that was the nova volume attach and then inside of there you can do a sudo fdisk dash l oh it helps if I associate my floating ip yep instance port id you can get that by doing a quantum port list a port is a virtual interface so basically it represents a mac address and inside of quantum obviously a mac address is then associated with an ip address do you have a running instance it doesn't have a port then let me come see ah there we go so I'm able to get to my instance so it's floating ip just f2 f2 edd that one that's the one yep that's the port id except for some of the spotty wifi so basically what I've done here is I have my instance I'm going to pull up my network here we've got our instance which is 1002 and we've got our router that's connecting our private network to our external network so I took an ip address off of that external network that's our floating ip and I associated it with my instance and so now this is from my laptop not from the cmicro back there I'm able to ping that instance so I can ssh into it directly too so let me do that so now I'm logged into my running instance now we logged in through its floating ip but if we do an if config what do you expect to see one interface, two interfaces one there's going to be one and what's the ip address going to be there goes the wifi oh this is really painful who provides the floating ip that's going to be whoever's running the infrastructure so the private networks we created they're all virtual networks they don't exist they're not physical this side of quantum is kind of this virtual construct but it's actually attached to a physical network so the administrator will go create that network they will attach it to the physical interface the physical network and on that network you'll have a block of routed ip addresses that you would set aside for nova floating ip or quantum floating ip quantum does all that so quantum sets up all the net rules yep the traffic will come into the quantum network server and there will be a rule for that particular floating ip and how to route it back to the actual instance on its private network so quantum manages all of that there we go so we can see that the ip address is 10.002 yet i sshed into it through its floating ip okay we can also go out so let's see if i can do this so my max ip address is <IP_ADDRESS> okay so i'm inside of cirrus right now and let's see if i can get out now i sshed into my instance but now i'm coming back out from my instance back to my mac which is on that external network if you will so i could ssh oh that's right ssh off so we can see our instances can get out to that external network we can also get into an instance through its floating ip is anybody having any issues with the floating ip's are not able to set that up a couple of people what's that? bill's gonna help you out right here and the black and grey striped all of your computers your personal laptops are actually on that external network so if you just figure out whatever ip address your laptop has for your wifi connection from your instance you should be able to get to your personal computer no your router have the gateway set but you were able to get in to your instance right oh i thought you said you could get into your instance you had that working your floating ip are you trying to ssh to it do you have ssh server running yeah the ssh inside of cirrus it might be the busybox one it probably doesn't have full features so i've got my one instance here and i've created my volume and attached it and if we do a sudo fdisk-l we should be able to see vda is going to be our root disk so that's the one with the os on it that's what it boots from we also have a dev vdb which is the volume that i've attached to that instance so right now it's just a raw block device so we can either partition it or we can just go ahead and lay a file system directly on it and mount it so i'm going to go ahead and do that so you want to make a volume bigger one way of doing that is just making a volume snapshot so you can go into your volume uh... and then under images what you'll have to do first is detach it so you'll detach your volume and then you can take a snapshot of it and then you can provision new volumes from the volume snapshot when you do that you'll just specify the new size yeah it creates a new one from a snapshot then you reattach it yeah back to the instance you want yep that's the you can delete the old one then when you're done yeah and then can you pull up the console in there or sorry view log i just want to make sure it DHCPed correctly yeah and then security groups so if you go to just scroll down a little ah that's what you need so if you go to access and security yeah the security groups you know because you're just creating policies but you're not applying them to any instances so you'll need to go into the instance and say edit security group yep hey gang so we really appreciate y'all hanging out with us today and uh dealing with us through the wifi apologies for that um we're going to be here for a little while until we get kicked out for the next session so you can continue to play but i don't have a pocket like Byron thank you but did just want to share with you all real quick uh what we've done for you oh sorry what we've done for you right now and very rapid pace we're using the public or open stack public script um what we've done with you in a very rapid time is a quick glimpse of what you get for us in a live training class um which would usually take four days our fundamentals class which we gave you in an hour and a half over a four day period six hours per day um and if you want more information about any of those training classes you can find that information at training.rackspace.com um all the classes we offer are listed here open stack fundamentals for those who are just getting started but we also offer an open stack networking course allow you to deep dive into networking into neutron we have a Hadoop on open stack course so anybody who's using Hadoop want to use it with open stack we have a course that will walk you through that a security in the cloud course for software developers we also teach a swift class so there's a ton of classes that are available for you training.rackspace.com if you're interested um if you have any questions about training at all you can email us at training at rackspace.com that email goes to all of your instructors here and we'll be more than happy to answer any questions for you so thank you again to Vince and the rest of the team at AMD for that C-micro um next time we'll get somebody to sponsor our Wi-Fi that we bring in we appreciate it thanks guys hope you enjoyed it


The backrooms has millions of fans, well over 100 million, and every single individual enjoys a different aspect of the backrooms.  But what we can all agree on is our love for liminal horror. The ability to get lost in this never-ending scene of melancholic nostalgia forever. And since there are so many fans of that, over the last four years, several different canons and lore systems have popped up about the backrooms. From the Wikidots canons, to the fandoms canons, to the liminal archives, to whatever this is, today I'm gonna be embarking on a journey to explain every single backroom's canon and what I think their pros are, what I think their cons are, and everything about them. Super long, so if you enjoy it, I'll leave a like for my eyes, they're currently melting out of their sockets after reading this entire script. So firstly, we need to identify what a canon is as it relates to the backroom's lore. In this instance, a canon is a set of rules, lore, characters, designs, and other things that go along with each other to form a readable parameter of sorts. These are different people's interpretations on how the backroom was created and how it works. That's what a canon would be inside of the backroom's lore. Unlike most canons in other fan bases, backroom's canons tend to overlap and dip into each other, and all still work together in a weird twisted way. Which just, to me, adds to more of that confusion, and if the backroom's is anything, it is confusing. And that's why we all love it. Canons are not simply the backroom's wiki.website versus the fandom website versus the liminal archives website. Those are not canons in and of themselves, those are vessels where canons are created in. Wow, that sounded really smart. Cool. Anyways, first up, I want to go over these six or seven different canons from the backroom's wiki. The wiki.describes them as, quote, when wandering throughout the backrooms, some things may simply not make sense. A note from an unknown source documenting destruction. A level which feels too reminiscent of certain events. No matter what, it's impossible to deny the fact that stories exist. It's not that we don't acknowledge these stories in events, it's the fact that they dip into each other, shatter each other's tails, breaking away at what founded these stories in the first place. They break laws established early on, and they show no indication of stopping. So you get a pretty good idea that the canons really are not a strict set of rules, they're more just guidelines. But anyways, with all that blabbering done, let's get into the actual canons. Like I said, there are six or seven of them so far on the wiki.describes, and then there's a bunch more of the fandom, and there's some on the liminal archives. And I'm going to go over canpixels as well. I'll be describing their outlines, their high points, and some of their levels and other key entities and stuff. I cannot go over every single detail. Obviously, the video will be 10 hours long if I did. Some of you would probably enjoy. Anyways, without further ado, let's get it. The Desolation Cannon. The Desolation Cannon focuses on humanity's ability, or rather non-ability, to survive inside the infinite labyrinth of liminal spaces that we call the backrooms. Its lore only has a few levels inside, and even fewer entities and objects. Now probably I would venture to say this is the most popular cannon that you all have heard of, and you probably take part of this cannon. Even if you didn't know it, the levels that find themselves underneath this cannon's umbrella are level zero through 10. I'm going to try to stop saying cannon so much, but if you can tell me how many times I say cannon in the comments, I'll pin your comment. Anyways, level zero through 10 are here in this lore. Those are the main original ones. It also includes a sub-level of level four. You can't forget about that one. There are just two entities inside of this lore, and those are facelings and hounds. And as far as objects go, there's only one, the recordless player. As you can see, this lore really involves nostalgia and how it relates to the human psychology. It's pretty much just the original stuff. The main 11 levels, the OGs, whatever you want to call it. Now this one is actually a lot of people's favorites, and many believe this is the one true cannon. The main one, the only one that matters, and the only one that people should listen to. However, I think it's boring just to have 11 levels. Yes, I love these first 11, don't get me wrong, I love it, but I also love the infinite places and the never-ending aspect of the back rooms. Anyways, that was the Desolation Cannon. Pretty much if you just think that the first 11 levels are all that should be in the back rooms, this is the cannon for you. Next is the Industrialization Cannon. The following paragraph is how it describes itself. Humanity has settled into the back rooms, creating societies which echo the ones back home, for better and for worse. The horrors of creeping monsters and liminality crumble away as humanity finds its own horrors to replace them with. Alongside the monotony, a decades-long fight for superiority as Top Dog is shaken to its core as a mysterious company known as the Back Room's Robotics enters the fray and threatens not just the status quo, but the entirety of the back rooms as a whole. In the chaos, many hope to rise and truly bring the back rooms to peace once and for all, but peace in the wrong perspective may be more dangerous than anything seen before. So that's the gist of the cannon. It's about building a life inside of lifeless places existing where you shouldn't. It's specifically how hard it is to do that. The levels underneath the umbrella are level 566 and level 522. Both of these levels are buildings with a ton of gizmos and technology and industrialization put inside of them. They're relatively safe as well, and they're both really deep inside the lore. You know, they're both 500 levels, so I doubt many people could even get to them.  The entities along with this cannon are entity 82 and 120. Now, 82 is Coco, which is kind of a sentient AI system on a computer. And 120 is a AI robot type entity. So I like to think of this cannon as almost a steampunk version. It's the idea that humans and technology coexisting inside of a hellscape like the back rooms can't really happen. And like the description said, this cannon really focuses on the one group known as the back rooms robotics. If you want a video of me going over every single group or like group of people in the back rooms, let me know. I'm going to talk about some of them in this video. Not going to go into too much depth. There's too much lore. Might be another video. Like I said, tell me if you want that. But if you like the idea of steampunk meets the back rooms, then you're going to like the industrialization cannon. Onto the next, the Pantheon Cannon. Oh Lord, this is a big one. So let me summarize. This cannon is the idea that the back rooms at one time were home to a ton of very powerful beings. Each of these beings controlled a different part of reality.   And the humans didn't like it. And yadda yadda yadda. There was a rebellion. The humans overthrew this Pantheon of creatures, scattering them to different parts of the complex. And yeah. So the Pantheon is way more esoteric. It has this supernatural view of the back rooms, focusing mainly on its metaphysical and spiritual aspects and not necessarily the just liminal aspect. It really dives deep into the forces that created it There's simply so much lore in the Pantheon cannon that I simply cannot touch on all of this video. It'll be impossible. But the levels that go along with it are level 51, level 389, 216, 49.2, 979, the hub, and level help. All of these levels are very similar themes of otherworldly and supernatural atmospheres with strange effects and themes of abandonment and ruin. Many people also like this cannon because it makes the back room seem less humanized and more mystified. It makes it seem as if it's a place that's steeped in mythos and stories and not logic and reason. There are many, many gods and creators in this cannon. And as I said, there's too many to go over, but each of them play different roles in creating the back rooms and controlling it. The entities involved under this umbrella are ones like the Keymaster and Blanche, which as you already know, are both extremely powerful, ethereal, and otherworldly beings that have control over the physical atmosphere in the back rooms. Think of this cannon as the Greek mythology of the back rooms. If you like that, then you'll probably enjoy it in its lore. The Simulation Cannon. And even though you might think this cannon is saying that the back rooms is just a big simulation controlled by a Simmaster, you'd be wrong. Although that is what some people believe to be a true cannon, this is not what that is. This specific one is mainly about humanity and its survival in the back rooms over the last thousand plus years. Essentially, the evolution of humans and the back rooms simultaneously from the beginning of time. And it's described like this. Its pages are connected mainly through its themes of being mostly about humans and incorporating as much other back rooms riding as possible and generally feeling more grounded. The back rooms is a weird, wild place that can get as wacky as it wants, but the cannon will always follow humans, human-based issues and human-feeling narratives. In Sim, you won't usually get a character with powers or having extremely supernatural stuff happen. If it does, it usually happens for a narrative reason. Most people in the cannon are just people trying to get by. Anyone from a lone survivor to the leader of a dictatorship follows this rule. Besides its rigid timeline, that's basically as much identity as it has. I try to stick to it as religiously as I can, especially in the age of cannons such as the Pantheon. So as you can see, this is pretty much about people surviving the labyrinth of rooms and hallways with nothing too fancy or crazy added. The cannon also includes a pretty cool timeline of events as it's proposed that the back rooms existed, dating all the way back to 1000 BCE, all the way up to future societies thousands and thousands of years away. It relies on humanity's achievements and also those achievements as it relates to the back rooms and the history progressing in a linear line. Pretty much all that fancy stuff is to say it's literally like real life evolution but inside the back rooms. It also involves old civilizations like the lost civilization that are prominent in the descriptions of the lore here. I think it's pretty dang cool to be honest. Illegious shows of the back rooms and people have always been in contact and they grew together in a strange way. This cannon shows back rooms and its levels going from very simple scenes of wilderness and stone rooms and small towns with less liminality all the way up to what it is now with the infinite rooms and infinite complexes that we know today. So if you would like to read about the evolution of people and the physical spaces in the back rooms as they've grown over the last 1000 years, you can check out this cannon. It's really cool. I really like this one. I think it's such a dope idea. They like cavemen were once in the back rooms and humans evolved. While the back room space is evolved, I think it's super dope. Humans and back rooms progressing together. Who doesn't love that? Next cannon, please. The Terror Hotel Cannon. This one is based inside of back rooms. It is pretty based, but it's inside of back rooms of a five. So it's reach really isn't that broad and definitely not as broad as the Pantheon or simulation cannons, but the entities and objects inside of level five and its sub levels are all that are involved here. The logo of the cannon is a silhouette of an entity known as the Beast of level five, which if you don't know is just weird eldritch horror type creature that seems to have control over level five and its domains. So I venture to say that that entity is the center points of the cannon. Welcome, welcome. Please don't be so afraid. We are not many here, mind you. Our small group of dedicated workers maintain the hotel in the way which you see it before you at the present moment. And despite this place being infinite, we still try our best to make the experience of our customers one that is pleasant. Yes, pleasant. On the topic of our customers between you and me, you better have something going for you. We take our duties and obligations most seriously here at this hotel. And this includes making sure our visitors final resting place lies right here where they stand. But let's not get too far ahead of ourselves here. You're one of us now. And hopefully things will remain that way for a long, long time. This cannon is really full of sinister undertones. It's the idea that the outside safety of level five and its hotel rooms and hallways is a facade. It's a mask, a cover for the true powers that be. The article says that there are much more dark forces at work, forces beyond our comprehension. Entities like the housekeeper and the bellhopper and the comedian are in this level, as well as the beast level five and the concierge. Pretty much hotel themed entities are inside this cannon. The only level zero course are level five and a sub level, level 5.1. This cannon just really focuses on how dark level five in and of itself is. Even though the level gets overlooked constantly as just a hotel, this infinite, it has much more esoteric and dark meanings behind it. And that's what this cannon dives deep into. So if you like that, then you're gonna enjoy it. And finally for the wiki dot is the unmasked cannon. And this cannon follows the group known as the masked maidens. It follows them around the back rooms as they try to destroy every other group that we all know and love or hate, specifically Meg. They hate Meg. The maidens believe that Meg is very corrupt and they almost view them as a plague that's destroying the back rooms. So this cannon seeks to purify that and scourge them from view. Levels in this cannon really take on strange features and descriptions like level 67. It literally just serves human meat cakes to people that go there. And level 10.1 is literally a carnivorous lake that consumes anything that touches it. The cannon is very dark, very macabre, mainly focusing on the evil of people and their involvement inside of these limeral spaces and how they're ruining the back rooms. It treats people as a sickness, a virus that needs to be healed by any means necessary. The entities in this cannon are no different from that. They're actually really cool. Entity 126, Scarecrows, and Entity 182, the masked messengers. These entities watch and they wait and they hide in plain sight. They try to heal levels whenever they can by removing people. They topple entire groups and organizations by hiding in the shadows and waiting to attack. They're just the normal back room stuff, of course. The people in this cannon use objects like wall masks to spy and maidens ink to write letters and communicate secretly with each other. It's all very under the table and shady. So if you wanna join in with dismantling everything besides yourselves, and this cannon is for you. The masked maidens want to return the back rooms to its rightful place as an empty, carnivorous, liminal hellscape. Honestly, I don't blame them. People kinda suck.  But do we need to kill everybody? I don't really think so. Still a really cool cannon, though. Okay, finally, that is all of the cannons from the Wikidot. There are two more, but they have very little lore and info with them. Those are the Black Knights and the Decay Cannon. I'll link them below if you wanna read into them. I'm not gonna cover them at this moment, like I said. Not enough lore. They don't pass the lore check. But as you can see, these cannons are all vastly, vastly different. And they all really take different approaches to understanding the back rooms, just like us as fans do. Some people like the idea of people living in the back rooms forever. So they follow the simulation theory. Some hate that idea, and they wanna see all the groups and all the people out of it. So they follow the Masked Maidens Cannon. Others, like it's simple and liminal, so they follow the Desolation Cannon. There's literally something for everyone. And I think that's pretty cool. But oh no, we aren't even close to being done. And this video is probably like 20 minutes long already, but we're just gonna keep going. We still have two more Wikis and a YouTuber's cannon to cover. So buckle up, fellas. The fandom. This is another Wiki that chronologizes the back rooms and its lore. So of course, it has its own set of cannons and storylines. But surely, surely there can be too many of them, right? Okay. The first two cannons here have a bunch of lore, so I'm gonna go over them and then we'll do a little lightning round of cannons because the rest of them don't have as much lore. The antagonverse. This cannon describes itself as one that focuses on the middle of the interworkings of the back rooms. You know, you often hear about the line between reality and unreality when referring to the back rooms, how it's really blurry. This cannon is that blurry line. It's the embodiment of it. This cannon sees the back rooms as something way more than just a flesh and blood place and more of a manifestation of a bigger part of the universe. And thus, it follows the journey of two sets of twins, each of these sets of twins being from a different dimension but both finding themselves stuck inside the back rooms, forced to explore the liminality forever. The antagonverse really shows the reach of the back rooms and how not only people on earth are infected. So if you wanna see other alien type creatures and other different humans from different universes here, this is the cannon to read up on. The armiverse. This one is unique. The armiverse cannon focuses on the relationship between real life and the back rooms and how those two used to live in harmony until an unknown and powerful force called the void emerged itself and messed up that beautiful harmony and peace thing. The void would bring chaos and terror to earth and the back rooms alike, turning the back rooms from a safe place to a dangerous hellscape. Among the chaos of all this void stuff happening, three heroes would emerge and attempt to vanquish the void from the back rooms and all the bad that it brought with it. Pretty cool story actually. This cannon treats the back rooms like a place that's been infected by this dark void energy. And it says that the levels before the void came were safe and empty, but the void brought deadly levels and entities that are forced to exist here now and that the void is this dangerous thing, this tangible that's spreading itself over the infinity of the back rooms and infecting it. Again, pretty cool. If you like the idea of dark creatures crawling out of the void and this darkness overtaking back rooms levels and infecting it, then you're gonna like this cannon I bet. Now the rest of these 10 cannons are more simply understood by their names or short descriptions. So it's gonna be time for a cannon lightning round. That sounded cooler in the script, I'm sorry. The Atlas Archive is about doom and the idea that it's not worth even trying to survive in the back rooms because you're not going to escape anyways. The behavioral sweet cannon focuses on humans and their minds during their journey here in their stories and their mad thoughts and going insane and losing that sense of humanity while still being lost in the halls. Most of the articles in this cannon are cynical and cold, but some are very happy and whimsical which fits with how the back rooms changes humans' minds. Pretty much the cannon is very psychology based and it shows the impacts the back rooms has on the psyche of the people stuck there. The convergence cannon is an extension of the pantheon cannon, but it's focusing on those godlike creatures that control the back rooms. The levels here again are focused on fantasy and this grandiosity instead of the usual just liminal, empty humbuzz. It focuses more on the ethereal energy like pantheon. The imperian-verse cannon is the idea that one single godlike entity known as the Exalted One created the back rooms in its entirety. The cannon states the birth of the back rooms was eons ago and that it's much, much older than we all believe it to be. And the back rooms is kind of treated as this small speck in the huge expanse of cosmos in this cannon. The back rooms incursion cannon focuses mainly on the sci-fi and action parts of the back rooms. Instead of wandering around aimlessly with no hope of survival, in the incursion cannon, you actually explore the back rooms as if it's a game with a linear timeline. In this lore, the back rooms began during a great cataclysm that happened outside of a reality, but it was so big that it bled into our reality and drug people into the back rooms with it. Now people who fell into this back rooms reality place have banded together and have vowed to explore it and make sense of it and survive it. It's a futuristic themed cannon and it kind of reminds me of Starfall or Destin or something like that, but it's pretty neat. I've actually never seen this take before. I like it, it's pretty cool. The liminality cannon focuses on the nightmare of being in the back rooms itself. The dread of being stuck in the past because that's all you can think about when you're here. It follows one specific guy named Masui as he no-clips into the back rooms and explores the levels. Eventually, this guy finds friends to do it with and they discover something dark on their journey through the back rooms. This thing is known only as the entity and these people, they realize how big of a danger the entity is to everyone. And this cannon shows how these people work together to explore these empty rooms to find ways to save them from the entity and its destruction. Lim cosmology cannon focuses on the madness and hostility of the physical back rooms and it treats the back rooms as a predator seeking a meal almost. It pretty much shows the back rooms is actually trying to consume you as the wanderer. Most of the levels and things in this cannon are written pessimistically and everything has this nihilism undertone. Nothing matters, so why should you even try to survive the back rooms?  The surrealness and psychological horror is the main aspect of this cannon and the psychological part is more dangerous than entities or people. And finally is the cannon called Zeta. Now the cannon Zeta is just about one single group, a criminal group inside of the back rooms. This group started out helping Meg and other groups research entities and their behavior. But after doing that, they realized how powerful entities are specifically compared to humans. They also realized that humans would never be able to leave the back rooms or survive it. So Zeta somehow convinced other groups to rally to their cause. In turn, creating this really large network of people that just wanna turn every single person and human into an entity by any means necessary. You know, since they think that only entities can survive and people can't, they wanna turn everybody into an entity so you can survive. It's kinda like the whisperer's storyline from The Walking Dead. If you sing that, Zeta believes that you have to become an entity to survive the entities, if you know what I'm saying. Yeah, it's actually pretty neat. And that is almost every single cannon from the back rooms, Wikidot and Phantom. I only skipped over a couple because they were more repetitive or convoluted than they should have been, but those are all from the Wikidot and the Phantom. The last website's cannon that I wanna touch on is called the Liminal Archives. This website focuses mainly on, of course, the liminality in its most basic or its most advanced form. They describe the back rooms as, quote, the back room system is many things and individual levels can vary, but most can be characterized by many of the same elements, man-made architecture, in decay, and distorted beyond comfort. Digital creations extrapolated into physical form, lost media now found with new identity, each level existing as part of the whole, rarely isolated. These themes can be found in abundance. This website has less than 100 levels in entities and objects combined and they all focus on the deep and psychological liminality of the back rooms. The idea that you're alone forever with nothing but your thoughts. They have groups and they have entities as well. They're just much less commonplace. It's actually kind of similar to the Desolation Cannon from the Wikidot, where the Desolation Cannon thinks only levels zero through 10 are cannon. This website, the Liminal Archives, is kind of like a whole website just for that. As you can tell, there is quite literally something for everyone in one of these cannons. Now, the levels that I've gone over on this channel and the levels on each of these respective websites that I just talked about, they don't all have to be part of a cannon. There's no real rules about it. After all, why would there even be rules about a rule-less place, you know? But I'm sure each and every one of you can find one of these cannons that you like the most and you can read into its lore more if you're interested. Like I said, I physically cannot document every single detail about every cannon. They're simply just too much and I'm just a wee YouTuber. I hope that after this video, you really realize just how vast the backrooms is and why it is so popular among so many people because there really is something for everyone. These cannons are like the Cheesecake Factory menu, bro. It's like infinite possibilities and I love it. I love every single part of it. No matter what aspect of the backrooms and its concept that you enjoy, there is a cannon that backs it up. There's something for literally every person. I know I just said that five times, I don't even care. Anyways, the last cannon that I wanna touch on today is the Kane Pixels Cannon, which is not dissimilar from the other cannons I talked about today, but it is unique in the fact that it's shown in a completely different form, the found footage form. Kane's story arc begins in level zero. Well, this is gonna start, but as we get deeper and deeper, we see a few other levels and locations, like the pool rooms. We also see a sinister backstory brewing underneath that leads to a company that started it all, Async. This company, of course, tapped into the backrooms and is researching it for multiple uses, like waste disposal, object removal and so on, but they didn't expect for it to bite back the way it has. Kane's Cannon, no matter how you feel about it, has made this backrooms thing revolutionary for the creepypastas in general. It literally changed and revolutionized online internet horror. It skyrocketed the popularity of this niche for better and for worse, yes, but I think it's a pretty darn cool thing to watch. I love the found footages and adds such a real aspect to it and I really enjoy the psychological horror involved. Many people like Kane's Cannon and many people don't, it's very polarizing. I like it for what it is, I love the footage part of it, but if you like watching the backrooms Cannon with this corrupt government undertone, then the Async Cannon is probably for you. In conclusion, my voice is shot, I've been drinking water for two hours. I think I've said everything I need to say. The video is already longer than my forehead, but there is literally a cannon for everything inside the backrooms universe and it proves to everybody that the lore in the backrooms is the opposite of one dimensional. You know, some say that cannons ruin the backrooms. It may not have too much lore, expanded it too much, but I say there can never be too much lore because the backrooms has always been infinite from the beginning and if there's only like five levels, it's too boring. These cannons add an ability to look at the backrooms through a billion different lenses and see it and enjoy it and respect it for a billion different reasons. Anyways, that's it for the video. If you enjoyed this video, like I said, please leave a like, check out my Twitter and Instagram below. If you wanna see my personal existence for some reason, you don't have to, but it's free to follow me over there. Also check out my third channel, Spoogely, if you wanna see those kind of videos over there, I upload like video essays and stuff. It's again, pretty neat. I love and appreciate you all and make sure you tell somebody you love them. Life is too short not to. With all that said and done, I'll see you in the next video.