Welcome once again to another edition of the Red Brunnen Williams real estate show. I'm Shannon Deskins along with Jennifer Brown Day and today we're going to be bringing listings from across many counties in eastern Kentucky. That is something Red Brunnen Williams is known for. You all have four different offices so let's talk about where those are. Okay, we do have four different offices. We have an office in Louisa, Panksville is where our main office is located, Pressensberg and then our office here in Parkville. And of course you guys can show anything listed all across eastern Kentucky so you can represent the buyer or the seller. Absolutely. The Eastern Kentucky Association of Relators covers about 16 counties and we can help you in any of those counties. Alright, now that being said there's a whole lot of listings but we're going to feature five of those today and the first one we're going to talk about is in Johnson County. This one is located on Denver Branch at Hager Hill. If you're familiar with that you're going to take the Riceville exit right off of 23 and then go down 825 to Denver Branch. Now this is popular for anyone who hikes or gets outdoors or rides their bicycle being that this is adjacent to the Dawkins Trail. And this is a really, really popular trail line, you know if people aren't familiar it's great for biking, walking, you know taking your dog on a walk, anything like that and it goes on and on for miles so this is going to be a great location if you like that. Yeah, this is great for the outdoorsy person but it's also good for just somebody who wants to be outside the hustle and bustle. This is on the north side of Paintsville. Right. But still you're close to Prestonburg or if you're looking north to Louisa this is a great area for that but you're getting the privacy. Yes, absolutely. This comes with about 50 acres of property and then this home is one of those that it's already set in a country setting and then they have it set up if you want to do gardens, they've got fenced areas for livestock, you would be great with horses and a barn and that kind of stuff. This house is set up for somebody who really wants that kind of lifestyle. And you know horseback riding is something that's very popular in our area so this gives you that pasture land. All of that to where if you wanted to do that you could and you wouldn't imagine being so close to US 23 and right off that you've got all of this but you've got 50 acres but the house is huge. It's four bedrooms, two bathrooms. It is and it's almost 2,500 square feet. It's a fairly new house, it was just built in 2002 so you know going in you know kind of what was put in the house when it was built. It has a large open rooms, hardwood flooring so you've got all those extras and then like we said that country setting. Right. Now I love that front porch because that is one of those that we talk about. A lot of people look at when they go to look at a house the outdoor space as well as what that indoor space is because that's always an extension. It's not counted in your square footage but you're going to spend time there as well. Absolutely and this has that really nice front porch, really great view and then in the back you also have some space for garden and some outdoor space as well. Well now this is out of the Paintsville office. This is Cliff Bennett's listing so let's give that Paintsville office number. Okay that number<PHONE_NUMBER>. Alright now moving along to the next one we're going to talk about. This one is also in Johnson County and another one of Cliff's listings. It is, this one is off Cannell Cole Gap. Don't say that too fast because you can't get it out. But that is going to be right off of 321. If you're going from Paintsville towards Prestonsburg you're going to stay in Johnson County and everybody kind of knows where the old industrial road is right there to your right. You're going across there and this is going to be back in that area. This is what people refer to as the old road going between Prestonsburg where the airport, where the Combs airport and things like that. This is on that road. This one is convenient to Prestonsburg and Paintsville but still not far from US 23 and convenient to a lot of things. It is and this one is the house sits on about a quarter of an acre but you still have that country feel with its location. So you don't have the large yard to take care of but you still have the mountains around you in that scenery. You've got 2,300 square feet. Just like the last listing this is a large home, 4 bedrooms, 2 bathrooms and like you said those large rooms which are great for family gatherings and just to sit and enjoy the evening. Exactly and this one is a ranch home. So it's a 4 bedroom, 2 bath ranch house which is a very popular layout because that means you don't have the stairs, you don't have any trouble accessing any part of the house. So this is going to be one that I think will be very popular. Like you said look at that yard we've got the picture that shows that front yard so you've got your yard space so to be on a quarter acre it looks like it is sitting in a good location to give you that feel of a much larger yard lot however maintenance wise it's manageable. Exactly very manageable and that's the great thing about it being a ranch too it also makes it a little bit more manageable on the inside so you have it on both sides. And then you've got the 2 car carport also to park your vehicles and things like that. Again this is another one of Cliff Bennett's listings so can you give Cliff's email in case somebody didn't want to call the paintsfield office it's easier for them just to shoot him an email. Absolutely his email is bennett at rbnw.com. Now the next one that we're going to talk about we'll move back into Pike County and this one is on the Long Fork Verge and this is one of your new realtors. It is. Beverly Newman is one of our new realtors and she has hit the ground running and got multiple listings we're going to go over today. This one is on Long Fork Verge. This is a two story house again a four bedroom house with two bathrooms and I think the part that makes it look so homey is that wraparound deck that you can see. Right and just like we talked about you know the outdoor living space is important to some people as that indoor space but this you're out in the country onto this one you're getting the privacy you're still only 15 to 20 minutes outside of Pikeville which is not very far at all but you get that feel of you are you're to yourself. Exactly. You sit on four acres of property so you have a little bit of that privacy and then this one has a large yard so you have almost an acre flat of usable yard space right now this one like you said four bedrooms two bathrooms I love that one picture that shows all the windows and the light come again that always makes that space feel larger and more inviting. Absolutely and it's like I said this one is going to be a two story home so you have the ability if you've got you know teenagers or you've got an in-law that lives with you you have that possibility of a little bit of separation and privacy. Right now this one once you get on Lone Fork this is only three-tenths of a mile and it's right next to the family dollar so this should be anybody that knows this area of course they can do a drive-by I'm sure there's a sign in the yard so this is one that you'll be able to see and look at before you decide if you want to take that next step. Absolutely and when you drive by you're going to notice that there is a huge 40 by 40 metal garage that comes with it. There's also a two-story storage building that comes along with it and then like I said that one acre lot that you're going to love the yard. The flooring is hardwood tile and carpet throughout so you've got that mix of different things so this is one I think you could definitely come into and a lot of people can see themselves living in this home. Definitely I think so and if they want to definitely give Beverly a call. Alright let's give that pintful office number the price on this one is $239 so for everything you're getting the four acres this is one that a lot of people may want to look at. We hope so. You can call<PHONE_NUMBER>. Alright the next listing is also one of Beverly's now this one is on Childers Road. Yes this one is in the same area as the last one in that Shelby Valley High School District area. Okay now this one you also go up Penny Road but you'll turn left at the end of Penny Road versus the last one right but like you said the same area so somebody could actually schedule both showings in one day. Absolutely and this one is a 1992 double wide it offers three bedrooms two bathrooms and right at 1400 square feet. That is large for a double wide so you're getting all that three bedrooms and two bathrooms but what I like the most about this one is how it sits on that little hill. You can imagine what the view is sitting out you know thinking about what we just mentioned winter can you imagine the snow or in the fall when the leaves are changing these are the kinds of houses that really get some attention. Absolutely and it's got that great front porch so you can enjoy all those views of whatever season we're in. Right and it's a covered front porch so no matter what the weather if you can stand the temperature you can sit out on this front porch and enjoy those views. Absolutely and then they've done some updates they've got newly installed carpet vinyl and laminate in several of the rooms has been replaced and then it has a gas log fireplace in it so again getting ready for that winter time. And just like the other one this one also has an outdoor storage building and then you've got garden space too so that's important we feature that a lot because you know so many times people maybe they've been in a townhouse and they're buying their first home with property and that seems like a lot of people say I really want to be able to garden and this one has got that garden space for that too. Absolutely and then it comes with a one car car port as well so again super convenient location especially if you're wanting to be in that Shelby Valley area. Okay so let's give Beverly's email address on this one as well. Her email is bnewman at rbnw.com. And of course she is out of the Pikeville office so call or email either one. Now we're going to end the show with a townhouse that's actually right inside close to downtown Pikeville. It is this one is going to be at Fields Way which if you're familiar with Cornerstone Church it sits right there off of Handley Boulevard. Fields Way sits directly behind it and this is going to be on the middle street of up there on Renee Drive and this is a three-bed room two-and-a-half bath townhouse. But this you can't really just say townhouse on this because there's so much more if you've ever been to Fields Way you've got more property than you normally do. And of course one of these pictures is showing that patio area so you're getting a large townhouse because all of these are very big the way that they're built but you're getting that outdoor space as well. Absolutely they do come with that outdoor space and this one like you said that patio picture that is absolutely gorgeous and that gives you all kinds of privacy so that's something that's going to make this unit very very unique with the other ones that are out there. And this one I mean I'm looking you've got the privacy fence so a lot of people would come in and say well I want to put that well this one already has that so this one is truly move-in ready. You've got the new appliances these are all new townhouses it's a fairly new area so but you don't get to say very often that a townhouse is over 1,900 square feet. Yes over 1,900 square feet and again that means your three bedrooms are going to be spacious bedrooms you're going to have a really nice layout to it. They also went in and did custom cherry cabinetry. It's got hardwood throughout the house so you don't have to worry about allergies or changing carpet or anything like that and then this offers a great room and you can see in the pictures how large that space is. Typically in a townhouse you don't think of big spacious rooms but you can see in the picture that this one does have it. So you're getting almost 2,000 square feet again built in 2009 so this one is as great as far as all your systems should be good to go but being in a townhouse your maintenance you don't have to maintain the big yard you don't have to take care of a lot of things so this is great for somebody with that on the go kind of lifestyle. Exactly and then all these units do have one car attached garages so you've got that garage space as well they have built-in closets in them so you really have a lot of storage in that 1,900 square feet. Yeah and just to reiterate with a townhouse you don't get to say almost 2,000 square feet with a garage, with a patio, with all this space so this is one of these and these don't come open very often. They do not. This is something that if you have an interest in a townhouse this is something I would move on quickly because they don't typically stay on the market very long and like you said this is Teresa's listing. She's out of Painesville you can call the Pikeville office or the Painesville office whatever is easiest for who's looking. Okay well let's give Teresa's email just that's an easier way to get a hold of her. Absolutely it's T. Preston at rbnw.com. Alright so we've given you five listings today that I think run the gamut of pricing but then it shows the different areas that you guys take care of and service so that is something that's always great to say about Red Bread and Williams is you've got the whole region covered. Exactly we try really hard to make sure that Eastern Kentucky is well taken care of. And something else let's give those five those four office numbers or not numbers but those four office locations again just to let people know where you are. Okay Louisa, Painesville, Pressensburg and Pikeville. And of course all of their listings and all of the contact information for all their realtors is on your website as well and that is rbnw.com. But I think you have some things for people who may not be looking to buy a house now but may be looking to buy a house later and that's coming up in the real estate minute. Preparing to buy a home can be a long process but you can start early by learning to be financially healthy. This can have many meanings. Start with a good credit score and very limited debt. I recommend setting a budget for yourself that is reasonable and sustainable for long term. This budget should include monthly bills, emergency funds and putting money into savings. Using this method you are financially stable and getting approved for a mortgage is a simple process. Once you know you are in a position to purchase your dream home, the realtors at rbnw would be honored to assist you. Thank you for watching another episode of the Rare Brown and Williams Real Estate Show. See you again soon.


For the last few months, the world has provided nothing but darkness and depressing news. I don't know about you, but I'm getting a little tired of talking about deadly viruses, horrifying economic collapse, police brutality, impending dystopias, murder hornets, but I have been talking about it. And the inevitable theme that's been running through a lot of our recent videos has been negativity and criticism. From power-hungry politicians and destructive lockdowns to out-of-control police, I realized that I've had a lot to say about what's going wrong with the world, and yet I've spent very little time talking about how to make it better. So at the risk of missing the mark with something completely out of sync with the news cycle, I want to take a break from the carnage of reality to talk about something positive for a change. My lifelong love for Superman as a character, what's made the man of steel an inspiring hero and symbol for over 80 years, and why it's time to stand up for truth, justice, and the American way now, more than ever. This is a video I've wanted to write for a while, and now with the Zack Snyder cut of Justice League in the Works, rumors of Henry Cavill returning to the DCEU, and let's be honest, not many other movies coming out, I think the time is finally right. Before we really get into this, you should know that there are going to be all kinds of spoilers for a bunch of TV shows, movies, and comic books going all the way back to the 1930s. You should also know that this is going to be way less of a history of Superman video, and more of a love letter to some of my favorite incarnations of the character, and the values and personality traits that have made him an enduring figure in global pop culture. There's a lot to cover, so suit up, hit that subscribe button, and join me for this heroic edition of Out of Frame. Since Jerry Siegel and Joe Schuster first started kicking around the idea in 1933, Superman has gone through a ton of different iterations. But we all know the mythology that stuck. The last child of a dying planet is placed in a rocket ship and sent to Earth. He's found by two wonderful adoptive parents, Jonathan and Martha Kent.  Clark Kent grows up to be a reporter at the Daily Planet in the thriving city of Metropolis, and he's also... Over the years, there have been countless variations, reinterpretations, and alternate takes on the characterizations of both Clark Kent and Superman, produced by dozens of different writers all trying to put their own spin on the universe. This is one of the greatest, and yet also worst, aspects of comics as an art form. On the one hand, a single character can span multiple eras and generations, and sometimes brilliant writers get to work with incredible artists to create something iconic and memorable. On the other hand, with so many different creators all participating in a kind of writer's relay race, a ton of plot holes and narrative conflicts get built up over time. And as a result, comic storylines periodically have to be reset, with big, event comics like Crisis on Infinite Earth, or hard reboots like DC's New 52 or Rebirth. There's really no way around it, but it makes it tough for people who aren't regular readers to keep up. It would take hours for me to even come close to explaining the decades worth of storylines and changes Superman has gone through, so I'm not going to do that. Instead, I'm going to focus on a few specific stories and scenes that I think represent the best of who Superman is and why he's important. There's a lot to unpack here, but we need to start with a little bit of psychology and character analysis. There are so many ways to understand the nature of this character and its role in our culture. A lot of people, possibly including his own creators, think of Superman as little more than an adolescent power fantasy. The idea of a power fantasy is that the protagonist of a story acts as a surrogate for the reader, allowing them to imagine themselves asserting dominance over situations that they would otherwise be incapable of dealing with in real life. I get it. Even the name Superman is a translation of Friedrich Nietzsche's ubermensch, a concept from his 1883 book, also Sprach Zarathustra. In the book, Nietzsche presented the ubermensch as a man who created new values born from love of life in defiance of nihilism, in a world where God is dead. Under this conception, the ubermensch, or Superman, creates meaning from nothingness. It's an aspirational idea and something for all people to achieve. Unfortunately, the term came to be associated with Hitler and the Nazis, who arrogantly believed that the ubermensch was something that could be attained by eugenics and racial purity. Nietzsche did not agree with that, by the way. But when Siegel and Schuster, who were both Jewish kids from Cleveland, started working on the first incarnations of the character, Superman was a villain with psychic mind control powers. He looked more like Lex Luthor than the hero we think of today. Instead of a power fantasy, he was more like a will to power nightmare. But fortunately for all of us, that version didn't pan out, and they quickly rebooted their character as a physically powerful hero. Siegel and Schuster pitched stories and comics to publishers for several years, until one of their strips caught the attention of Jack Liebowitz in 1938. Jack, along with Harry Donnenfeld, co-owned and published Detective Comics Incorporated. At the time, they were looking to start a new magazine called Action Comics, and Superman turned out to be the perfect fit. Siegel and Schuster sold their copyright to the character to DC, and the rest is history. Now, in the early days, it might be fair to think of Superman as just being about power and giving kids a way to vicariously assert control over their world. Back then, Superman was stronger than ordinary people, but not at all like we think of him today. He couldn't even fly. He mostly stood up to bullies and bad guys by punching them in the face. Over time, writers gave Superman more and more abilities. First, he could only run and jump. Then he could fly. At the beginning, he could lift a car or a truck. Then a tank, then an airplane. Eventually, he was strong enough to punch a planet out of orbit. He gained new powers, regeneration, heat, telescopic, microscopic, and x-ray vision. Freezing, hurricane-force breath, also fire breath, for some reason. Super hearing, super intelligence and memory. At one point, mind reading and telekinesis. Super ventriloquism. Not all of these stuck, but between the 1940s and the 1980s, Superman went from having powers and abilities far beyond that of mortal men to one of the most all-powerful characters ever created. Some artists and writers even started deliberately using religious symbolism that would invite comparisons between Superman and Jesus. He's also been used as propaganda. During World War II, Superman fought the Nazis and the Japanese. And after the war in 1946, Superman took on the KKK in his radio show. His whole role in pop culture was to easily beat up people that the rest of us couldn't. So obviously, just a power fantasy, right? Well, no. I don't actually think so. You see, back when Superman was little more than a strong man, socking bad guys on the jaw, every comic book hero was basically doing the same thing. If he was a power fantasy, then they all were, but it's certainly not what made him a unique or great character, nor is it why he survived as a singular icon of pop culture for all these years. What's actually special about Superman is not all of his fantastically absurd superpowers or his alien heritage. It's the fact that underneath all of that, he's just a humble farm boy from Kansas. What makes Superman great is his humanity, and the constant choice he makes not to use his powers to force people to do what he wants and dominate the world. The magic of Superman is Clark Kent. As clinical psychologist Jordan Peterson is fond of saying, a harmless man is not a good man. A good man is a very, very dangerous man who has that under voluntary control. This quote perfectly embodies the essence of what makes Clark Kent even more than Superman or Kal-El, the character worth looking up to. Now, for some of you, I'm sure this distinction seems silly. They're the same person, right? Of course. But like all good characters, he's complex, and this duality, or triplicity, is what makes him interesting. Dean Cain probably explained the distinction most succinctly in Lois and Clark, The New Adventures of Superman. This is important, and it also flips the classic idea of a secret identity on its head. Here are the Incredibles. Most superheroes use a mild-mannered secret identity to mask the truth about their more powerful, real personas. Superincredible and Elastigirl are the true characters. Bob and Helen Parr, at least in the beginning of those movies, are the fiction. But in a few important ways, the reverse is actually true for Superman. The cape and tights are the fiction that helped Clark Kent mask his gentle, middle-American reality. Back in 2013, screenwriter Max Landis explained this idea perfectly in a rant he posted to YouTube called Regarding Clark. What's special about Superman is that his parents didn't f***ing die. He's not a selfish, post-traumatic sissy who needed to have his parents shot to death in front of him to understand that maybe you should help people and that crime is wrong and murder is bad. He didn't get stranded on a desert island. He didn't have a ring forced upon him that brought him into an intergalactic police force. He wasn't raised by Amazons. He didn't go up on a ship and get irradiated. He's just a guy from Kansas who has the best superpowers. He's unstoppable.  You're looking at someone who's a superhero because being a superhero makes the most sense. Either try to save the world or you can take it over.  Clark Kent is the most dangerous man in the universe. And yet, he is good. Only a handful of writers have really understood how important this is to the character and as a result we've gotten a ton of stories like Man of Steel and Batman vs Superman, Injustice, Gods Among Us, and Frank Miller's The Dark Knight Returns where virtually all the drama is built around Superman's physical powers instead of his moral values. That's a shame because it really seems like the world needs to remember how to be more like Clark Kent right about now. Fortunately, there are some good stories to look at. In All-Star Superman, Grant Morrison and artist Frank Quitely gives us a look at the final moments of Superman's life. After saving research facility in outer space from a plot by Lex Luthor, our hero has absorbed too much solar energy. He's going to die.  He saves a rude man from falling debris as Clark. He saves the life of an enemy. He talks a girl out of suicide. He cures dying children he's been visiting in the hospital. He shows compassion for an insanely dangerous creature. He becomes friends with Bizarro. He even saves Lex Luthor. Twice. Meanwhile, he reveals the truth about himself to Lois and shows her what it's like to experience life the way he experiences it. Then he has a heart to heart with his father and plays one last game of fetch with Crypto. He's both super and human. And through all of that, he consistently demonstrates the values that make him a hero. In one important scene, he confronts a pair of conquering Kryptonians, Bar-El and Lilo. They mock him for failing to use his powers to dominate the people of Earth and build a new Krypton. His response is humble. That's not fair. What right do I have to impose my values on anyone? You can either try to save the world or you can take it over. Clark chooses to save it. And you know what? Even after he saves Metropolis from Bar-El and Lilo, when they become ill, Superman shows them compassion and helps alleviate their suffering. All-Star Superman is one of my favorite stories because it isn't really about Superman's physical strength at all. It's an exploration of his character. This is also the focus of Paul Dini and Alex Ross's Superman piece on Earth. There are aspects of this story that I really don't like, but its core is a valuable lesson about humility and the limits of power, even for the man of steel. It opens with Superman encountering a starving girl on the streets of Metropolis. As Clark, he follows up on her story and learns more about global hunger. He reflects on the lessons taught to him by his human father and decides that Superman should do something about it. But what? Although he knows it's not his place to set policy for mankind, he offers to transport food to starving nations. Volunteers step up to help, but as he begins to deliver shipping containers and entire container ships to hungry people around the world, he realizes that the problems are bigger than he fully understood. A one-day reprieve from starvation did not resolve the underlying causes of poverty. It did not stop repressive governments from terrorizing their people or stealing their land and resources. It did not change the fact that societies without decent institutions, markets, trade, and the free exchange of ideas, people would never be able to take care of themselves. Superman is forced to accept that for all his physical power, global hunger was a problem beyond his abilities. In the end, he chooses to teach young kids how to feed themselves. Not as Superman, but as the son of a Kansas farmer. And that brings me to one last story, Superman, American Alien. Written by Max Landis, American Alien is one of the best modern Superman books. It's a seven-part series of vignettes depicting critical moments of development in Clark Kent's life, from relying on his parents to help him navigate the horrifying shock of suddenly floating into the air or seeing through people's skin to learning how to manage his emotions when even the slightest outburst could level buildings and kill innocent people. Like All-Star and Peace on Earth, American Alien isn't really about Superman. It's about Clark and the values that make someone a hero. These values aren't instinctive or guaranteed in any of us. No one is born knowing how to be a good person or what moral principles are actually worth believing. These are things we have to learn. Superheroes, most of all, Clark Kent learns them from his human parents. In my favorite scene in the series, a young Clark is frustrated and embarrassed, hating himself for being different after failing to control his ability to fly at a drive-in movie. Hiding from the world, little Clark looks at himself in a mirror and sees a monster in the reflection. He lashes out, destroying both the mirror and the wall behind it. His dad picks him up at the theater to take him home. In the truck, they talk.  Clark is sad and scared. He just wants to be normal. The next day, Jonathan tries to help Clark learn to control his powers. After a while, they sit together on the front porch and Clark gets introspective and remorseful about his actions from the night before. His dad asks him, what are you thinking about? The mirror. I was thinking, somebody had to make it. Like, somebody at the factory took the time to make it. Then, somebody had to sell it to the movie theater. And then, other people had to fit it to the wall, which somebody else built before them. The gravity of his outburst becomes clear. And he goes on, when you break something, you're not just breaking the thing. You're like hurting everyone who made it what it was. Man, that is one of the most insightful realizations anyone could ever have about the world around them. And it was written in a comic book. These stories have survived for decades. They've been retold in dozens of languages, and they're known all over the world. They are mythology. And like all mythologies, they're ultimately about human values. They're how writers and artists convey their ideas and share lessons about character and morality with everyone else. But not every value anybody puts on screen or in a book is good. The ends don't justify the means. The collective isn't more important than the individual. Appealing to the greater good is often just an excuse for the abuse of power. Not every moral lesson anybody takes the time to write down is actually going to make the world a better place. So the stories we tell each other matter. That's why it's frustrating for me to see portrayals of Superman in Man of Steel or Batman versus Superman who have unbridled power and no clear moral compass. The heroes in some of these movies don't seem to care about anything. It's also frustrating to see writers who clearly hate Superman, like Frank Miller, depict him as a state worshipping goon or an inhuman alien god one bad day from becoming a brutal dictator. That's bad for business. I understand, sir. And although it's fun to imagine alternate versions, they can't all be evil. Certain people must die in order for the system to work. Wise words. If Superman's only role is to punch things really, really hard, there's nothing to look up to or be inspired by. That might be a power fantasy, but it doesn't help us understand how to use the power we have for good. And that's not what's great about the character or why it's worth telling stories about. He's so much better than that. And more and more, I think we need to start reminding each other that there are some values that are worth standing up for and some that really aren't. We need more truth, justice, and respect for individual freedom. We need fewer people trying to lie and mislead in order to impose their values on everyone else by force. We need more humility, compassion, and kindness. We need less anger and division. More calm, less noise. What I'm saying is we need actual heroes. On our recent episode about cop shows and police brutality, one point I made was that even though those stories tell us that everyone with a badge is a hero, all those characters go around acting like villains. A couple years ago, I said the same thing about Captain Marvel. The idea that it's cooler and more dramatic to make every character as dark and violent as possible has permeated pop culture for years. And now we live in a world where it's often impossible to tell the good guys and the bad guys apart. All Rangers, I need you to engage the targets. Guardian, this is batter zero one. What about the giant blue? I said engage all targets. Anti-hero stories work when they actually make sense for the character and the world being portrayed. But blurring that line when it comes to the characters that are supposed to represent the best of humanity has done a lot of damage to the way people think about what it means to be good. I think it's time for that trend to end. Looking around at what's been going on in our society, I can't help but feel that maybe we've lost our way. And I suspect that this is largely a result of bad ideas and nihilistic philosophies that have taken root in virtually everyone of our cultural institutions. But if we're going to hold on to all the things that have led to human progress, the enlightenment, science and the industrial revolution, division of labor and global trade, expanding individual liberty, civil rights and economic freedom, we can't lose the values that make those things possible. To do that, we need better heroes and good role models. And we need stories and mythology to help us share these values with everyone. And that is why we need Superman. Hey everybody, thanks for watching this episode of Out of Frame. As I said at the beginning, there's no way I could cover 82 years of comic history. So what are some of your favorite stories? Who are your favorite heroes? Let's talk about that in the comments. I'd also like to give a shout out to all of our patrons with an extra special thank you to our associate producers, to Matt Tabor, Dalin Case, Victoria Manshart and Laura Turner. Thank you. If you love the show and wanna help us keep making more episodes, check out the Patreon link in the description below. And for those of you who have been wondering where Common Sense Soapbox went, I have some news for you. We've created a brand new channel just for Common Sense Soapbox and Seamus is working on new episodes right now. If you're a fan of that series, click that link in the description and subscribe today. As always, don't forget to like this video and subscribe to this channel and follow us on all our social media at YouTube, Facebook, Twitter and Instagram. Thanks for watching.


Hey everyone, welcome back to Nintendo Prime. Yes, my fiance is doing well. She did have her gallbladder removed late last night for those that are keeping up with that story. Everything's going well. She's obviously sore and has some shoulder pain and some other stuff going on, but she'll be fine. She's doing good. She's upstairs resting right now. But today I want to talk to you about a few stories. We've got three things we're going to talk about in this video. So buckle up. It's going to be a bit maybe longer video than my recent ones that have been on the shorter side. That's because this is some really, really cool stuff, including a big event happening tomorrow. We got a new game, a leak that got confirmed officially as coming to Switch next month. And something really cool about Breath of the Wild that makes us just dream about the possibilities of a future Nintendo platform. But before we get into that, I want to remind you we are giving away a Switch OLED system. That's what we're giving away. The white one that to me is personally themed after Metroid Dread. I know that's not an official statement, but gosh, does it look like it is? And it releases on the same day as Metroid Dread. So I'm sort of out there. It kind of feels like it's a Metroid themed Switch. But that being said, we are giving away one of those. To enter, all you have to do is be subscribed. That's it. There's no other special requirements or anything. Just be subscribed. All right, folks, let's just hop right into it because this first story is something that we will be live streaming tomorrow. In case you haven't heard the news, a new indie world is coming tomorrow. Now, this is not surprising. They traditionally have done indie worlds usually in the month of August. And yeah, people that were saying we were going to get Nintendo Directs in September did say, and of course I'm talking about here, Samus Hunter by the way, said that we would get an indie world this month and get a Nintendo Direct next month. Well, here we are with an indie world. Now again, it's a rather safe prediction or safe statement because we traditionally get indie worlds in August and then get Nintendo Directs in September. Even last year that was true, although it was not like a normal standard Nintendo Direct. Either way, we have an indie world coming up and it's going to be 20 minutes long. So again, the indie world happens tomorrow and it's happening at 9 a.m. Pacific or for me, 11 a.m. Central. So I will be live streaming that for you guys. We'll have a nice run up to that stream but potential games you might see, there's a certain Teenage Mutant Ninja Turtle game I'm hoping shows up there. Obviously we keep holding out hope for the new Hollow Knight, the silk song game. We keep holding out hope we're finally gonna see that. But you know, it is what it is. We'll have to wait and see. And I'll come up with a list tomorrow in the pre-show to let you guys know my thoughts on that. So yeah, that's really cool and I'm super excited for that indie world. Lots of stuff we hope to see. Obviously there's always the potential No More Heroes 3 is there, although we've been getting a trickle of trailers and information about that game already. There'll obviously be some new announcements. Pretty much every indie world tends to contain a lot of really high quality indie games. Hence the whole purpose of having that showcase. So I really look forward to seeing what new stuff is coming to switch from the world of the small independent game developers. So next up we're talking about Breath of the Freakin' Wild. And why are we talking about Breath of the Wild? Oh yeah, you're talking about the sequel right now. No, no, no. I wish we had news on that to talk about. But I'm actually talking about the original Breath of the Wild because a modder has done something that we haven't really seen done successfully to date and now we know why we haven't seen it done successfully. And that is running Breath of the Wild in 8K 60 FPS with ray tracing. Now you might go, who really cares, right? They're obviously playing a ROM, they're using an emulator, all that jazz. And yeah, they need some pretty beefy hardware to do this. They're using an ASUS TUF RTX 3090, 32 gigabytes of RAM of Corsair Vengeance at 3200 megahertz, a Ryzen 9 3900X which is a 12 core, 24th read CPU running at 4.5 gigahertz on all cores using a two terabyte SSD, which I'm not sure the exact speed of the SSD. But the point is the SSD, I don't think as much to do is it's usually the CPU that has a lot to do with getting that consistent frame rates. But running this at 8K 60 FPS, which I'm not doing for this video. You're looking at it right now and all you're seeing is 4K 60 because I can't, I don't have an 8K monitor here. So no point in me putting 8K footage in the show. But yeah, you can go to the link down below I'll mark it in the source section in the description. So you guys can go check it out in 8K if you just happen to have an 8K capable device. I don't know too many people that have even 8K displays to take advantage of that, but it looks really, really good. Obviously we've seen Breath of the Wild with ray tracing before, but we just haven't seen that 8K 60 FPS. And it obviously makes you wonder about the future of Nintendo. And like this game, but in the way that this looks potentially looks better than Breath of the Wild 2. And it just makes you wonder for future Nintendo Switch hardware. Not so much the 8K aspect. I think we're a long ways away from 8K displays becoming standard like to be 20 years before it becomes standard. 4K is literally just becoming standard. And so 8K I still feel is a couple of decades away before we get to that being the standard panel out there and being affordable. But it is really, really cool. And I'm pretty excited about it. I think it looks great. I think this does make me dream of what future Nintendo hardware is capable of. Again, not so much the 8K, but obviously the 60 FPS. Obviously the potential for ray tracing on a new generation Switch. I think there's just some exciting prospects here. When you think about, hey, what about bringing Breath of the Wild or Breath of the Wild 2 or Mario Odyssey or some of these other games over to Nintendo's next-gen platform in a kind of souped up kind of way like we're seeing with Xbox Series X and PlayStation 5 what's happening. So it would be really cool if Nintendo decides to do that versus going, by the way, this would mean the next Switch or the next Nintendo platform is full backwards compatibility, which that's something we have to hope for first. But still, I think this is a really cool thing and I hope to see it expanded upon in the future. Again, you're seeing the footage for yourself. It looks great. And I'm just really excited for what this shows for the possibility of future hardware and Nintendo. Now, this last story is one that I am personally excited about. And that is Darksiders 3. So it was actually originally rumored over the weekend and sort of leaked out there, but the official Twitter account for Darksiders has come on and confirmed that Darksiders 3 is coming to Nintendo Switch next month on September 30th. So really soon. And it includes both DLCs currently available for the game in Keepers of the Void and the Crucible. So those will be packed in. I'm pretty sure it's gonna launch at 60 bucks. They didn't give us any pricing details. They didn't give us any technical details, 60 FPS, 30 FPS. Probably gonna run at 30 FPS because the game itself has struggled on even like base PlayStation 4s and Xboxes. Some people even had issues with it on PlayStation 4 Pro. So it's traditionally known as a rather demanding game. And if you're fans of the other Darksider games which are already available on Switch and were on Wii U, this obviously completes that trilogy. This game is more like Dark Souls than I'd say the previous two entries. But that's obviously just my personal take based on my experience with all three games. It does feel more like a Dark Souls game, but that doesn't make it a bad thing. Dark Souls is one of the most critically-acclaimed games out there. So Darksiders 3 is a lot of fun and I'm just glad to see third-party support continuing to come to Switch. Now again, this game's already available everywhere else. So if you don't want to wait for it and you have other hardware to play it on, I mean, go play it. It's just a reminder it's available, but it is coming to Switch. And that to me is always exciting to see third-party support come to Switch. Even if personally, I'm probably not that interested in this game on Switch because I've already beaten it. But it is cool that it's coming and I'm pretty happy for those of you guys that don't have it yet. Now for our last story, we're going to end with a little bit of an update, a sales update on this platform because there's actually been quite a few digital sales happening for Nintendo Switch, some rather big ones. I don't know if you guys have been on the eShop lately, but there has been a mountain of games discounted, including Nintendo first-party games. I think I even saw Breath of the Wild digitally available for $45 like last week. So there's been a lot of massive sales hitting the platform, which to me is good. I'm not going to put them on the level of say steam sales, but it's still really good to see some actual digital discounts on major games. And today we have the announcement of some brand new discounts that are beginning later this month. It's going to be available only in a period that's for, gosh, less than 24 hours. So you're going to have a very small period here. And that is discounts on Bethesda games on Switch. Now I've actually played, I think every single one of these games on Switch and all of them were really good. Some of them have various versions, but the point is that Bethesda's entire lineup on Switch is going to be on sale for roughly 15 hours. So let's go over the lineup. So Doom itself, the 2016 Doom is going to be on sale for $39.99 before this sale. Doom Eternal, just the base game is on sale for $29.99, which is half off its current price on the eShop of $59.99. Doom Eternal, the Ancient Gods expansion pack is going to be down to $22.49, which is down from its $29.99 original price point. Doom Eternal Deluxe Edition, which will include everything, is going to be $53.98, that was originally $89.99. The Elder Scrolls V Skyrim is finally on sale for $29.99, still listed at $59.99. I mean, imagine that game's been around. How many platforms? How many console decades? Wow. Wolfenstein Youngblood is going to be $5.99. That's right, just $6. That game is really good. If you like Wolfenstein and haven't played Youngblood yet, for six bucks, you better be picking this thing up. It is $19.99 right now on the eShop. Wolfenstein Youngblood Deluxe Edition is going to be $14.99 down from its $29.99 price point. And then Wolfenstein II, the new Colossus, is going to be $17.99 instead of the usual $59.99. That's the biggest discount of all of them, over 50% discount. This sale is going to be taking place starting on August 23rd at 11.59 p.m. Pacific time, or in my time that would be 1.59 p.m. Pacific time, and ending August 24th at 2.59 a.m., or in my case that would be 4.59 a.m., so basically 5 a.m. So again, it's about a 14, 15 hour sale that's happening during QuakeCon. Really, really cool, really, really good stuff. Makes me really excited to see what other companies are gonna start dropping major sales on Switch. Obviously, this is also a reminder that we might never get Bethesda games again on Switch, because now it's Microsoft-owned. One of the pitfalls of Microsoft's purchase of Xenomex Studios is that we probably are done getting these games, or maybe we're not, because Microsoft and Nintendo, I like BuddyBuddy, and they're gonna be like, yeah, no, we're gonna keep bringing those games over. We'll see what happens, but I'm really excited about the sale. I'm excited about this news in general today. Guys, we have an indie world tomorrow, and that's always great. It's not an Nintendo Direct, but indie games matter too. Seriously, I know I don't play enough of them, and I should be playing more indie games than I do, but for real, that's awesome, that's exciting stuff. We had a lot of big stories today. I hope you guys enjoy all that news, and I'm kind of a nice little four pack for you guys today. I am Nathan DeRobeljans from Nintendo Prime. Thank you so much, I hope you enjoyed this video. If you did, drop a like, drop a comment. That helps get the video spread out to more people, and I will catch each and every single one of you in the next video. For sure, we'll be live streaming tomorrow. We'll see if we end up live streaming again today. We also have the podcast tomorrow, so a lot of stuff to look forward to this week as we keep pushing forward and keep pushing onward into a new tomorrow.


All right, all right, come on, keep coming in. Well, thanks for coming, everyone. I appreciate it. My name is Dan Wenland. This is where I usually say I work at NYSERA, but now I say I work at VMware. Either email still works, so it's perfectly fine. I'm the OpenStack Quantum PTL, and I'll also, obviously, core developer. If you're interested in updates on Quantum, you can follow me on Twitter. First off, I know there's a Quantum design session that's going on right now, too, but are there any other Quantum core devs here that want to just raise their hands and identify themselves? That's good. Everyone's getting worked on, except for you, Edgar. Should be up in the design session, man. OK, well, I guess if you have questions, you can find Edgar afterward as well. Cool, so the theme of my talk is taking OpenStack networking to new heights. So there was one really well-known skydiving incident this weekend, but there's actually another one, too, which is the first, as I know, of team OpenStack Quantum freefall experience. So we celebrated the full some weeks. This is not actually me. I'm way too wimpy to do this, but two of the other core devs did it, so I figured I'd open with that. So what we'll talk about today, well, how many of you have seen a talk on Quantum before? Can you just raise your hands? OK, all right, so I'll actually go fairly slowly then, just to make sure people are on the same page. Then we'll talk a bit about project status, and then we won't really have time to dive into a lot of the different scenarios in detail. I'm just going to flash a bunch of diagrams in front of you that kind of lets you understand the different modes that we see people deploying Quantum in right now. Talk a bit about looking forward, and then hopefully have some time left over for questions. OK, so the main motivation for Quantum, they're two big things of why we created the Quantum project in the first place. The first is that real enterprise applications have very complex networking requirements. They require multiple tiers that are isolated with multiple subnets. Maybe you need firewalling policies and intrusion detection system, et cetera. But the reality is that most cloud platforms, things like Amazon, OpenStack with the basic NOVA networking, have a very, very limited model in terms of what someone could do to configure their network and map it to what their application was expecting. So the first of the two things that Quantum really introduces is a tenant-facing network API. And we'll go into details about this API later, but it lets the tenant, just like it can go, say, create server to NOVA, it can go to Quantum and say, create network. And not just create network, but use this subnet of IP addresses on top of it, because I want to take this application that I built in my data center and move it to the cloud. And I want the network topology to map exactly. You could also, for example, uplink these networks to the internet if they need external connectivity. You can insert advanced services, things like routers, firewalls, VPN, intrusion detection, et cetera. You can also do things like monitoring to detect uptime, packet statistics, et cetera. So if you think about things that most people would assume if they were deploying a rich application in their enterprise data center, we need to bring those same capabilities into networking with an OpenStack. So that's reason number one for Quantum. So you can actually use Quantum, for example, to build rich multi-tier applications with firewalls, all kinds of different policies. Second thing is that cloud really stresses a network, particularly if you're building a cloud at scale. And really, there's no other reason to build a cloud. So first off, you have really strong multi-tenancy requirements. You need very strong isolation. But traditional mechanisms for multi-tenancy are pretty limited. I don't have time to say everything that's wrong with using VLANs for multi-tenancy. But everyone knows that it's not just the numeric limits. It's also that switches tend to have much lower limits even than the numeric limit. VLANs are only valid within a particular layer, two segments, et cetera, et cetera, et cetera. So there's also the fact that traditional networking gear is designed around a model that's a lot about manual provisioning. Someone actually H's into a switch and enables some VLANs. Everything about cloud, the entire point of cloud is to be on demand. If you have a human in the loop when you're provisioning an application, you've already lost in the cloud world. Additionally, the idea of cloud is to let you build large pools of capacity and potentially use the compute capacity wherever it exists. And yet, that's actually not how networks work. Networks tend to give you an IP address that's actually according to whatever physical pod you're located in. That would mean that you wouldn't necessarily be able to migrate, for example, VM from one part of your data center to another part of your data center. So again, the point is that cloud really stressed networks in ways that they weren't traditionally built for. So what you want is some super new technology. Now we're not going to say what technology, because quantum's not about a particular technology. It's about a platform and a plug-in architecture that lets you plug in different back-end technologies. So I have my list of buzzwords up here. You can pick your favorite buzzword, find out what people tell you that buzzword means, but you can use those buzzwords or any combination of them, or whatever vendor, technology, et cetera. Open source, closed source, we'll talk about that later. And you can leverage them to expose those generic quantum APIs. Does that make sense at a high level? All right, let's keep moving. OK, so now we'll talk about what quantum is. So quantum is another independent service with an open stack, just like Nova, or Cinder, or whatever. And so the basic model of an open stack service is that you have a generic tenant API that can be spoken to directly with code via CLI, or via GUI like Horizon. And those hit generic logical APIs that aren't about how the resources are physically instantiated. They're just about how they're logically consumed. And the operator, the cloud operator, can select different back-ends. And so, for example, on compute you may choose KVM as end server. You may choose the OBS plug-in on the network. You may choose Ceph or any other storage technology on the back-end. So this is kind of going to be how you should think about every open stack service, and also quantum in particular. So first, we're going to talk about that first part, which is the API. So as I mentioned, Nova, we're all pretty familiar with it as abstractions of a virtual server. So you can make an API call, say create me a server with these properties. And in quantum, it's very similar. You can say create me a network with these properties. The networking quantum corresponds to essentially a logical VLAN, an isolated layer two segment, that you can then associate subnets with. Subnets represent the IP address ranges that VMs will be allocated IP addresses out of. They also represent associated configuration, DNS configuration, host routes, that sort of stuff. The important thing to think about is that these quantum networks are completely isolated and multi-tenant in the same way that it doesn't matter that two VMs are running on the same physical server. They're completely isolated. It's exactly the same thing that two quantum networks may share the same physical network substrate, but they're completely isolated, such that the tenet is this very simple, clean, logical model, where they can think they're the only person that matters in the world. And that they just have their network, and they can build their network topologies as if they actually own the data center resources themselves. So here's an example just to talk through of how some quantum API calls might go. So you can create a network, associate a subnet with it, create another network, associate a subnet with it. The important thing is quantum actually supports overlapping IP addresses. So two tenants, for example, that want to use the same set of internal IP addresses for their applications. For example, they were using RSC 1918 space in their own data center. They want to bring that application over. They can continue to use those IP addresses. They don't need to reconfigure all of their applications. This is actually something that's very important in practice. And then you can spin up VMs. And as you spin up VMs, you can define the set of nicks that are going to be on that VM and what network they attach to. So I could spin up one VM on this network, one VM on that one. They're going to get IP addresses allocated out of these subnets that are associated with those networks. I could even spin up a VM with two nicks, one on each network. And then we're even just starting to venture into this world of more advanced network services. We'll talk more about this later. But you could instantiate a router, which is an LV forwarding device, and plug that into networks as well. And the router, for example, may be applying SNAT or DNAT policies or some type of firewalling. One thing that's very important to think about is that nowhere in this did I tell you how I implemented any of these things. I didn't say that actually tenant A net one mapped to a VLAN, because it may map to a VLAN or it may map to something else based on the plugin. Similarly, the router. That could actually be a virtual machine running Linux and routing software. Or it could be something totally different. The quantum logical API is completely decoupled from the physical implementation underneath. Like all OpenStack services, we also have a notion of extensions. This is kind of the OpenStack way of handling the tussle between trying to provide uniformity despite different technical back ends and the ability to let people actually innovate and take advantage of new features. So in quantum, we use API extensions for two reasons. First, to kind of trial new functionality. So sometimes when you're designing API, you don't get the abstraction right the first time. And so what we don't want to do is we don't want to bake an abstraction in necessarily the first time. First, we release it as an extension. And then if that's proven to be valuable and proven to be sufficient, we'll move it into what we call the core API. The second thing is that in some cases there will be features implemented by one plugin that will never, ever be implemented by most other plugins. For example, it's a very vendor-specific technology, but that cloud operator has decided that they actually want to expose that technology to tenants. So it could be something that provides quality of service or SLA guarantees. Could be security filtering, net flow. You get the idea. Anything that you would have traditionally configured via kind of a manual access to a firewall box or a switch or a router, you can expose by this quantum API. And if it's not part of our core API, plug-in writers can create extensions to expose that. And the important thing to think about extensions is I like this because sometimes an OpenStack project has a risk of becoming vendors fighting against vendors. But ultimately, extensions that were really the deployers of OpenStack get to decide what extensions they want to expose. And I think over time, effectively what that does is it really lets the market decide in terms of what are the abstractions people really think are useful. Because otherwise, it's just one vendor trying to make the abstractions look more like their stuff than other vendors. And that's not a game I like to play, at least. So extensions kind of give that flexibility and kind of outsource the ultimate decision of what are the right abstractions to the cloud operators themselves. Extensions can also be used, as I mentioned earlier, to oh, it just happened there. Someone have a clicker? OK. It can also be used to expose entirely new services, things like the routers or whatever. So now that was the abstract API. That's going to be the same across different quantum deployments, modular of the extensions. What we'll talk about now is the plug-in architecture. This is a high-level logical diagram. As I mentioned, you have this uniform logical API for all clients that will include the core API, which are the basic CRUD operations on networks, ports, and subnets. You may have certain API extensions that are supported by that plug-in. And then you have external tools like tenant scripts, GUI, other orchestration code that calls this logical API. And these API calls essentially get passed into the plug-in. And the plug-in is really the person. The code, I think of people as code of people, that decides how to map these logical abstractions onto the physical world, depending on the technology and the strategy that plug-in has chosen. So a simple way to think about a plug-in in a completely generic sense is that it's going to go out. It's going to talk to the switching infrastructure that's adjacent to each, if you're just using NOVA, to each NOVA compute node. So it could be that it just talks to the virtual switch. It could be that it talks to the virtual switch and the physical switch. Or it could even be that it just talks to a physical switch if, for example, NOVA is using a technology like VAPR or VNTag that maps VMNICs directly to the physical network by passing a V-switch. And then each plug-in is actually going to make certain assumptions about the physical network. And this is actually a very important thing to understand when you're looking at one plug-in versus another, which is to say a simple plug-in might assume that all VLANs are trunked everywhere. But other plug-ins, for example, that use overlays may say, well, it doesn't really matter what the physical topology of your network is. You don't have to access your hardware. We'll overlay on top of it. So that can be one of the key differences between different plug-ins. So this is something I like to use to really emphasize how there could be any back-end implementation to quantum. Some are good, some are bad. The simplest one in my mind would be, get an API call. They jump that JSON into an email. It goes to your network guy or girl. That network guy or girl does what they've always done in the old world, the SSH into a switch. They set up VLANs, et cetera. And then they send an email back and the web request returns. Obviously, this is a terrible, terrible idea. But it gets to the point of quantum doesn't specify what is actually happening on the back-end. That's ultimately the plug-in. And you can think of different plug-ins as being different strategies for how to solve the problem of automatically provisioning these network topologies. So when you think about quantum plug-ins, there's all kinds of trade-offs to think about. Just like when you're buying a car, different features, different quality, different aesthetics, all kinds of things, scalability, forwarding performance, what hypervisors are compatible with, again, what assumptions they make about the physical hardware. Do they assume the hardware is from a particular vendor? Do they assume there's some physical topology in your network, what manageability and troubleshooting tools come with it, what advanced features they have that may be exposed by API extensions, testing HA, both from a data plane perspective and control plane perspective, open source free versus paid. If you look at the plug-ins that we have, they span the entire gambit. And ultimately, it's about giving cloud operators the flexibility to make those choices. So the plug-in ecosystem, as it exists today, there's two common open-source plug-ins, which is the Linux bridge in the open V-switch plug-in. There's also another one that's called Raiu, which is an open-source, open-flow controller. And there's a couple of vendors that are behind plug-ins as well. So the Cisco, NICER, and NEC plug-ins are merged into the main repo. So they're officially supported by the core team. There's a lot of other people who have announced additional plug-ins, either I'm not sure if they're released or not, or whether they're just kind of demos at this point. But they're all people who are kind of subscribing to this model of implementing a quantum plug-in. And I think it shows really good momentum for the community. OK, so project status. So before we actually talk about features or what was in the Folsom release, there's actually one thing that to me is actually the most exciting thing about quantum in the past six months, which is that we've really had extremely great growth in getting not just new people contributing code to the project, but new core developers. So I think NICER, Cisco, and Rackspace have been involved for quite a while at this point. But just in the past about six to eight months, we've had Red Hat, Dreamhost, IBM, NTT, NEC, Internet, and other players really step up and start contributing to the project. And this is really, to me, represents a move from quantum to more of a true community model, which is something I think is very exciting. So six months ago, if you were at the talk, we had just released Essex. And Essex was our first, what's called, an incubation release. So we weren't considered an open-stack project, but we are not what's called a core open-stack project, meaning the core team, the docs team, et cetera, did not officially support our stuff. We were on our way to becoming core. So six months ago, we had a V1 version of our API that was really just about defining Layer 2 connectivity and letting VMs plug into different L2 subnets. Not about, for example, IP address management or anything else. And the second thing is, we only really delivered on one of the two goals of quantum that I mentioned before. The first goal that I mentioned was the tenant-facing API. And V1 of the quantum API actually wasn't truly tenant-facing. It was that NOVA proxied calls on behalf of tenants. And so tenants really couldn't define their own rich network topologies. There's more a model that the administrator could define them on behalf of them. The benefit that we did have in the V1 version of quantum was that you could have the different pluggable backends. So most people that, this is in production at several early adopters. For the most part, their driving motivation for deploying Essex was about being able to plug in different network backends, to, for example, avoid limitations on VLANs, things like that. Now, with Folsom, we're really excited because this is our first core release. This means we're official, just like all the other projects, we're an officially core project. We released V2 of the API. There's actually a pretty substantial change to the API in that previously IP address management had been handled by NOVA. But we wanted to change that for two reasons. First off, there are things other than VMs that may be consuming IP addresses. For example, routers, load balancers, additional network services. So you needed IPAM to be pulled out of NOVA. The second thing is that NOVA actually had a very limited model for IPAM. They didn't allow overlapping IP addresses, even if they're on different layer two segments. So we actually pulled IP address management and the associated DHCP functionality to inject those IP addresses into VMs. And we moved that into Quantum in the Folsom release. We also integrated with Keystone. Thank you, Joe. So that was obviously a critical part of actually being able to expose an API to a tenant, not just to another OpenStack service. And we integrated with Horizon. Anyone on the Horizon team here? Thanks for the help. So they're really great about that. So what's that? Gabriel sent you one. OK. We also had, we updated the CLI. We added a lot of new functionality there. We also had two very important extensions. We had a good number of extensions, but two ones that I really want to highlight here because they correspond to things that people commonly did with NOVA networking. So the first was the L3 router API. So this is the idea that you can create a logical construct that connects multiple isolated layer two segments and provides basic routing between them and then can act as a NAT uplink to an external network. Along with that basic L3 forwarding in NAT, there's a notion of floating IPs in NOVA. And this is how Quantum ends up providing an equivalent functionality. So floating IP is a notion that you can have VMs that are on private addresses behind a router. So they're protected. And then you can allocate a public IP that's one-to-one mapped to a particular VM. So we have kind of the L3 in floating IP support that's equivalent to NOVA. It's also a notion, another extension of something we call provider networks. So in most cases, when a tenant wants to allocate a network, they're allocating it from a pool of possible networks that that tenant could use. Let's say you have a simple plug-in and you're using VLANs for isolation. So there's some range of VLANs that are valid in your physical network. And when a tenant asks for a new quantum network, you're going to allocate one of those VLANs and use that for them. But in some cases, particularly a cloud operator wants to create a quantum network that actually maps directly to a physical network. You use this, for example, let's say you want a quantum network that someone could plug into to just connect directly to your physical network infrastructure and go to the internet. This is a pretty common model that's used in a lot of the clouds that we deal with. So this is a way that if a particular VLAN or a particular physical network is meaningful to the provider, but they want to expose that to let tenants plug into that network, they can create a what's called a provider network that creates a logical network directly mapped to a particular physical network. There's also functionality around quotas, which I would say very important. You can't let someone create it. If you only have so many resources in your network, you can't let someone create an infinite number of networks and notifications as well. So this can be used for billing or basic monitoring. So the quotas and the notifications are kind of just things that are in most open stack services. And we felt like we needed to do that by the time that we were a core project. So here's a little I decided against a live demo. Probably a good idea in hindsight. But I wanted to kind of walk you through the flow a bit in Horizon, which is obviously the open stack GUI. So you'll notice something new that when you're running quantum is you get a networks tab. And you can click on that and you see a list of networks. Now these may be networks that were created on your behalf by an administrator, or they may be networks that you decided to create yourself. So you can create a new network. You can click on it. You can specify not just a network name, but you can specify the network address, whether it's V4 or V6. This actually doesn't even expose all of the options. You can configure, is it a gateway? Does it use DHCP, et cetera. And then you create those networks. And then when you launch an instance, you can choose what network to plug it into. So this is a subset of the quantum functionality, but it's kind of all we got around to exposing in Horizon right now. But this is really the core feature set of you being able to create multiple networks and create interesting network topologies and spin up VMs on different networks. Oh, actually I have another slide later. So one of the main questions we actually get with quantum becoming core is what happens with Nova Network? And I've spent a lot of time talking to Vish, who's the Ptl for Quantum, about this. And our general rule is no forklifts. So it's a critical time for the OpenStack community in terms of convincing people that we're not going to go just redesign them and tell them they have to rip their old stuff out and put new stuff in. So essentially what we've done is we've said we're going to freeze, from a new feature perspective, we're going to freeze Nova Network. So no new functionality goes into Nova Network. And then what we're going to do is we're going to make sure Quantum is updated to cover all the key use cases that Nova Network supports. There's still a couple of gaps that we need to handle in Grizzly before that's really, truly happened. And then even then, because we're being extra cautious, even in that in Grizzly, we're not going to get rid of the Nova Network stuff. What we'll likely do is deprecate it and target that for an H release. So number one takeaway is don't panic. Your existing deployments with Nova Network aren't going away or it's not going to be immediately deprecated. And to some degree, Nova will actually probably always keep some network functionality, at least enough to do the basic flat networking. The other main question I get is, should I start using Quantum? Oh, it's CoreNow. Should I start using it? And my usual thing, you probably expect me to say, yes, yes, yes, yes. My usual take, though, is actually a little more cautious, which is to say, you have to go back to the reason we created the project in the first place. Do you have demand for creating an API to create rich network topologies? Are you limited by that today? Or is the flat networking model for you perfectly fine in Nova? Same thing about, are you being constrained by physical network issues like the number of VLANs or the size of your layer 2 pods, those types of things? If you're running into those issues, I'd say go for it. Quantum's designed exactly to be tackling a lot of those issues. But I'm not going to tell you to go to Quantum just because I think it's cool and I spend all my time thinking about it. If Nova network is fine for you, you can feel free to stay on it, at least for a couple more releases. So if you want to take Quantum for a spin, we've got admin documentation up here. We've got Ubuntu and Red Hat deployments covered in the admin docs. I will kindly request that you please read the entire document. Some people tend to say, oh, I've read the docs, but they haven't really read the docs. So when you read the docs, always come back. We're very, very happy to get suggestions in terms of, oh, I was looking for this thing in this section, but it was way down in this section or something like that. Or you actually did miss this. Feedback on docs is super valuable. It's obviously as well as bug reports.  So you can just download dev stack. You can look at this page for exactly what you need to put in your local RC, and you can just go for it. So the other great way to get more familiar with Quantum is that we're actually, my team, the NYSERA team, is doing a hands-on Quantum deployment workshop Thursday, 9am to 10 30am. And I guess this is Manchester E, right? Sounds good. So what this will be is actually, so we actually have our own internal cloud that's running OpenStack and NBP, which is our technology. And then on top of that, we'll be deploying little mini labs that you guys can use to actually have your own isolated setup of two hypervisors, a network node, and all of the OpenStack services that you can then basically do a basic setup, play around with it, ask us questions about how you deploy a certain scenario. OK, so I'm going to go through this stuff pretty quickly. The idea here is more to kind of give you a general sense of how Quantum works when you're actually deploying it, and what are the different scenarios that you can deploy it in. So this is a basic physical network layout. You can tell this looks probably a lot like what you would do in a Nova network scenario where you're using the VLAN manager. So for example, on the right, you're going to have some kind of controller node. Just like you run all of the other Nova API stuff and all of that, you're going to run the Quantum server there. The Quantum server is both a generic API code and the base plugin code that gets those calls from the API and dispatches them and goes and talks to various switches. You're also going to have obviously a set of hypervisors that are running Nova Compute and potentially an agent that may be specific to your plugin. This depends on what plugin you're using. And then if you're using the layer 3 functionality in the DHCP, you'll likely have a separate node in the production deployment that would actually be running not just the plugin agent, but also something called the L3 agent and the DHCP agent. This is how we inject routers and DHCP into your Layer 2 networks. So the traffic between VMs would be flowing on your data network. Traffic between VMs in the router, for example, will be flowing on the data network from a compute node to the network node and then out onto the external network and into the physical world. And then obviously all of the nodes are connected via a management network. This is, for example, communication between the agents and the main quantum server process. So again, not answering all of your questions, just want to give you a high-level idea. So there's two main models that we see people deploying quantum in. One is to say that I actually only want the administrator to define network connectivity. But that administrator needs a lot more flexibility when building the network topologies for its tenants. And it needs more flexibility than what Nova gave it. Or they want to use a different back-end technology than what Nova has. So in this case, it's a kind of operationally speaking, it's a model similar to maybe what you've done with Nova Manage in that administrators are defining the networks and then tenants are deciding what networks to plug into. The other model is the true kind of self-service networking model where you're actually exposing the quantum API to tenants. Tenants can make the calls to create network, create subnets, et cetera. So those are two different models depending on what your strategy is for your cloud deployment. And obviously you can mix and match these. For example, a common thing to do is for admin providers to create a default setup on behalf of the tenant. So the tenant shows up and they already have a router with maybe one network behind it. And then the tenant can decide, oh, I actually have this application that needs three networks behind this router. I'm going to go add a network and use this subnet, et cetera. So I'm going to move through this stuff pretty quickly. But this model basically maps to exactly what the Nova Flat or Nova Flat DHCP manager does. The point of showing these diagrams is to show that you can do all of the topologies that Nova supported. And you can actually do a lot more in terms of kind of taking these base constructs of networks, ports, and routers, and matching them together. So you can do a single flat. You can do multiple flat, for example, if you have different classes of applications. But there's only a couple. So maybe you have your production here, your test and dev here, but you want those isolated. This is one we see as well, which is basically an extension of a service provider that originally just provided the flat model, but then wants to kind of ease their tenants into also being able to use private networks. So a VM might have an interface on the shared public network, but also have an interface on a back end network for back end communication. Or you could even, like the VM on the far right, you could even have VMs that are completely disconnected from the public network and just connected to private networks. So again, you get the idea all we're doing here is taking the core API constructs and kind of rearranging them. So this is one example now, once we're actually pulling the layer 3 router in. This maps to what Nova network does with VLAN manager, which is there's conceptually one router, each tenant gets their own network behind it. And then tenants can allocate floating IPs from the public address space and map them one to one to a virtual machine for public access. You can also have an even richer model where tenants can create their own layer 3 routers and have their own isolated networks. This is what, for example, lets tenants create networks with overlapping IP addresses that are still connected to the internet. This is a model that maps more closely to something like Amazon VPC or CloudStack's advanced networking model, if you're familiar with that. And I say per tenant, but really they could be per application, tenants can have multiple routers here. So a couple slides looking forward. So where are we going from here? As I mentioned, how I view the work the quantum team needs to do in Grizzly is kind of dividing the two different areas. First, we need to close some gaps. There's a couple things in terms of being able to play nicely and really replicate all of the existing Nova network functionality that we still need to tackle. In particular, security groups in the metadata service. Nova's model, as I said before, was that no IP addresses can ever, ever, ever overlap. Quantum actually supports overlapping IPs. So if you're trying to use Nova's security groups or the metadata service with overlapping IPs, they're actually incompatible. So right now we basically have an option to let you disallow overlapping IPs if you choose to use these services. But in Grizzly, we're obviously going to tackle that. There's also the notion of a multi-host, which is not to be confused with being able to have multiple compute nodes. This is something in Nova where you can actually run the DHCP and the basic NAT capabilities on the compute host itself. And this can be nice for smaller deployments, just in terms of a simpler HA and kind of scale up model, as opposed to having pushed traffic through a network node, which could be a single point of failure or a bottleneck. So the second half of what we're focusing on and what people are upstairs arguing about right now are more advanced services like low balancing, VPN. How do we start letting people not just create VMs that do these things and plug them into topologies, but how do we actually give people APIs so that they can orchestrate programmatically advanced network functionality? OK, so I want to tell you about a couple other talks. I think one of these might have gotten moved and is now done. I forget. But these are all people who are giving talks about their OpenStack deployments that had deployed quantum on SX. So I think to varying degrees, they'll be talking about quantum. I know the NICER talk and the eBay talk, in particular, will be pretty quantum focused. I expected to come up in the Rackspace and Dreamhost talks as well. And again, several of these deployments have actually been running for six months plus now in production with quantum. So again, that was kind of the bleeding edge people. Now we're to the point where it's the core release of quantum, and we expect the set of people running it in production to go up a lot. So last slide, just key takeaways. So again, quantum exists for two purposes, to bring advanced networking to OpenStack by first exposing rich network APIs to let tenants build complex networks and services that map to the services that they could have deployed in their own enterprise data center. The second thing is it has that plug-in architecture that lets you leverage different back-end technologies to solve. You get to pick whatever technology you think is going to best solve your cloud networking problem. So like I said, Folsom is the first release where we are considered a core OpenStack project. We're really excited about it. We've been hearing from a lot of people who are planning on putting quantum into production with Folsom. So that's really exciting. I think it's going to represent a really big jump for the project. And finally, if you're interested, if you're a developer, you're interested in networks, come talk to me. We're always looking for new people on the team. So thanks. And Ron Burgundy, I couldn't be in San Diego without making a reference. All right, I think I finished with some time for questions, because I talked really fast. So any questions? You're walking through the workshop tomorrow. Thursday. Thursday. Is that going to be open-v-switch-based? Yeah, it's the entire open-source stack. It's all based on open-v-switch. So right now, are you saying if there was a plug-in that used OpenFlow, potentially a vendor who just did hardware could just sell an OpenFlow switch? Yeah, so that is true. So most vendors actually write plugins that are specific to their technology at this point. There's definitely a scope in the plug-in mechanism for there to be more of a driver or other self-bound interfaces that are meaningful. I think OpenFlow would be one attempt to do that. But in practice, I think that's actually going to be somewhat challenging, in that the plug-in is going to have to make assumptions about what OpenFlow version you're using, what table sizes you have, et cetera. Yeah, so there's no actual rule that a plug-in has to be single-vendor. In fact, the Cisco plug-in right now actually is able to speak to multiple types of switches. So it will actually configure the UCS switch and open-v switch that's running on a hypervisor. So there's no plug-in is not necessarily one vendor. Think of plug-in more as a strategy for how you're going to map logical networks to actual packet forwarding. And so one example, so people have moved and no one's ever done this because I don't think it's actually that useful in practice. But people have said, well, what if I just have a plug-in that's the VLAN plug-in? And I can go talk to any vendor's physical switch and know how to configure a VLAN on it. That would actually work. That would be more of a driver model. The overall strategy for the plug-in is I'm going to use VLANs to isolate logical networks. But I could talk to different types of technology. So no, no, no. So if you query slash extensions in quantum, you'll get a list of the extensions that are supported by the plug-in that are currently running. Yeah, yeah. So yeah, it's something we've talked about with. Yeah, are there questions? All right, well, thanks. Happy to chat with you afterwards.


Hei, myfyrwyr a myfyrwyr. In this video I'm going to be talking about why the narcissist targeted you. Please like, comment, share and subscribe. Click the bell icon to receive notifications for my future videos. If you would like to donate, my Paypal link is in the video description. If you're interested in one-on-one coaching, you can email me at narksworldwyrcoaching at gmail.com We have a private reddit community where myfyrwyrs and myfyrwyrs can share their experiences and knowledge. If you are interested in being a part of this community, you can sign up for our Patreon page, the link is in the video description. Check out the Narc's 5 Emojdi store where you can purchase your own Narc's 5 Emojdi t-shirt or mug. We have a variety of designs and it is a great way to support the channel. The link to our Narc's 5 Emojdi store is in the video description. Why did the Narcys target you? Narcys are predators. They are always seeking targets who are likely to be influenced or harmed by their manipulation. Then they know in their minds. Yes, I will be able to change the behaviour or the perception of this person. I will be able to exploit them for my own needs. Narcys advance their own interests at the expense of their target. When they are first hooked in you, they want to see how much you are going to trust them. How much you are going to believe in what they are saying to you. The minds start talking about something that happened in a past relationship. Just to see how you react to it. Narcys are predators. They are always studying you. Always studying your reactions. They want to have the ability to predetermine your response for anything that might happen in the future. So they might orchestrate a fake situation and act as though they are hurt or emotionally distressed. Just to observe your reaction to it. They are testing you to predetermine how you might respond in the future. They want to see how much you care. Narcys usually only target people who care. They target good-hearted people who they believe are easier to manipulate and take advantage of. Easier to propagate emotional reaction from. They do not want a target that doesn't care. A cold heartless person. Although later in the relationship that's what they will make you think you are. When they would never have targeted that type of person. As they wouldn't care or wouldn't emotionally react as you do.   Narcys like this initially. It is very beneficial for them. You are there to provide them with the love and affection they need. You might have goods or services that are beneficial to them. But over time they get bored of your love or affection or your goods or services. It's not as satisfying or fulfilling as it was in the beginning. So in their minds you cannot satisfy or fulfil them. You are not good enough. Which is really just their own feelings of self-hatred, envy and low self-esteem. Which are then projected onto you. Sometimes it comes out in verbal abuse. Such as put-downs or back-handed compliments. Other narciss can be passive-aggressive or even physically abusive. And this relieves their frustration for a short time. But as you begin to start confronting them on their abuse or manipulation. Then in their minds you are no longer the good-hearted person they thought you were. And then they begin to resent you. You are supposed to let them abuse and manipulate you. Devalue and degrade, publicly humiliate and exploit you. As you start confronting them on what they are doing to you.  They do not self-reflect or acknowledge their own emotions. They do not consider any faults or mistakes that they have made. So anything that you confront them about. That's your fault and you deserve to be punished. When they targeted you. They saw your empathic qualities as a weakness or a vulnerability. They saw it as something to exploit or take advantage of. They may have married you who appealed to your own ideals in the beginning. You may have believed that they were empathic too. But over time you begin to realise that most of the time their words never match their actions. They may have complained about a certain experience in their lives. Where someone did something wrong to them or to someone else. As though it was such a big deal and that person needs to be held accountable or deserves to be punished. As though it's something that really means a lot to them. But when it comes to actually resolving the situation. They never do anything about it. It's never treated as anything of significance or importance. And that's when you begin to realise that they were using a situation as bait or as a distraction. To lure you in and then take advantage of everything you have to offer. They use certain situations as an excuse. Few to empathise with them as though they were victimised. And really they are predators. They never consistently act upon something which they claim to mean so much to them. They might say that it's something that hurt them or it's something they care about. But when they have the ability to correct a situation they never act on it.  They will use situations to justify their actions and behaviours. But they never do anything to correct or change it. This is to keep you in a place of acceptance. It causes you to link that actions and behaviours to a certain situation. But it's never the real reason why they do what they do. If it was, they would be busy attending to what should be more significant or important in their lives. Rather than engaging in these types of actions and behaviours. But they never do. Most of the time their words never match their actions. They never tell you the real reason why they do what they do. The real reason, the root of their narcissistic actions or behaviours is envy. That's the real reason why they do what they do. That's where their true desire or motive comes from. Rather than some other situation which they claim to care about so much. Yet never act upon to correct or resolve the root of their actions or behaviours is envy. They will claim as though they cannot do certain things for you or act a certain way. Because of a past situation which bothers them so much. It's designed to keep you around so they can extract as much of your time, effort and positive energy as they can. The longer you stay around them, the more you will get sucked into the illusion. Where you end up in this alternate reality or fake world. With distorted perceptions, alternative interpretations and made up stories. They will tell you things like you shouldn't have done this or you could have done this better. But none of that really matters. It doesn't matter if they say that you've done something you shouldn't have done or you could have done this right. Most of the time you are already doing exactly what they want you to do. Exactly what they want. You are more beneficial to them than they are to you. What they are telling you is the problem is really a distraction or a diversion from what the real issue is. A narcissist will almost never reveal the true desire or motive behind their actions or behaviours. What they are telling you is the issue is just a distraction or a diversion from the real issue. And that is something involving you which they are envious of. But they will never tell you the truth because they are too deeply ashamed to ever admit it. What drew them to you in the beginning soon becomes what they are envious of. When they realise it cannot be theirs. When they realise they cannot be you. And have the qualities, talents and traits that you have will experience the world in the way that you do. They specifically pick targets who are more likely to believe in their manipulation, lies and illusions. Good-hearted, loving, caring people. Empaths, just so they can exploit them and extract as much out of them as they can. And also project their self-hatred, low self-esteem and envy onto. Thank you for watching. I hope this video resonated with you. Please like, comment, share and subscribe. If you would like to donate, my PayPal link is in the video description. Coaching enquiries, you can email me at narxfiverrcoaching at gmail.com. Talk to you soon.