We are back at Walmart searching for the new 25th anniversary blisters, which are basically legend of blue eyes and all those different awesome 25th anniversary reprint sets have been put into blisters. According to a message I got, we're going to see if we can find any in our currently stocked Walmart. You know, this Walmart is always having stuff. So we're going to see if that continues today. And if they've gotten any of the blisters, let's head inside. Wow, it is way too hot to be outside today. I don't know about you guys, but it is cooking here. So hopefully the poles will be cooking later in this video. Yeah. Oh, here we are. The worst items of all time. Okay. I might be grabbing these for a video. Worst Walmart items you can ever buy, but let's see if they've gotten better. Maybe they will buy these mystery cubes. Anybody? No, thank you. Duel's from the deep. Hey, new duelist thing coming out like two weeks. So we'll be better than this. Hopefully. All right. I think we're just going to buy all of these so nobody ever buys these. I'm going to save everyone who is in my local Walmart from wasting their money on these. Well guys, so much for the fire pulls that we were hoping for because I ended up having to pivot. We didn't have any 25th anniversary blisters like I was hoping. Seems like they put them out in some Walmart's and not ours yet. So it looks like we're going to have to do something else, which is open the worst Walmart blisters ever made. So we have done a video on these before. They're about $5 each and you basically get nothing, or at least the times I've opened them. So I bought all of them like six or seven of them for $5 each so that no kid or no other person comes through and buys them thinking that they're going to be good. That way we can rid them from the Walmart and save any potential future buyers from that terribleness of the experience of opening those and getting complete bulk for $5. But we also have hope that maybe today's the day we pull a star. All right guys, we are back with the absolute worst blister packs you could ever buy in Yu-Gi-Oh. I bought six of them. That was all they had. I saved many, many people by buying these. I mean, six people could have bought these. It would have been severely disappointed. So shout out to those six people. You're welcome. But before we get into it, we have a giveaway. I'll be giving away these three cards. We have the Alpha, the Magnaware, the Valkyrie, the Magnaware, and then Jynzo secret rare from the 10. The 10. So just like the video, be subscribed to notifications. Let me know down below. Is there a worse Yu-Gi-Oh product than this? Or is this the worst of all time? Fortunately for you guys, I did buy some extra blister packs, one which I thought was battles of legend monsters revenge. And it was wild survivors. I just am dumb. I completely forgot and just bought this. So we're going to be opening for the Hungry Burger again, I guess. But hey, this is going to be more exciting than opening those. Yeah, there's other ones.  Let's see if they've improved at all. I highly doubt it. But this maybe will be decent. We have a lost world. OK, that's a Ruxen special right to the cartway. Do we have a? I thought we had a crimp for a second. Super rare. OK, we got the baby Sarasaurus. So starting off with the dud. That's perfect for this video. I guess I'll go back and forth. So we'll start off with our very first includes 20 cards, blister pack, one guaranteed rare card or a rare card. So cool. Just like a booster pack, guaranteed rare card. Oh, yeah, awesome. Except you get an extra 19 cards that are all bulk. Very exciting. Let's see what it says. The collectible product in this package has been purchased directly from the manufacturer purchased from secondary market and repackaged for retail sale by M.J. Holden Company, our favorite company. M.J. Holden Company LLC is not affiliated with the individual manufacturers or trading card companies contained within this product. All related trademarks and logos are trademarks of their respective owners. At copyright 2022 M.J. Holden LLC, which is in Illinois. So we can thank Illinois for this. If you're from Illinois, it's your fault. Will we get a single one with like a super in it? I think we might get a super if it's like a super that's like a guaranteed newer super. So it's basically a rare. So it's going to be a rare or that is what I'm guessing. If we get anything better than that, we're doing great on these because these are honestly going to be 19 commons and then probably one rare. And most likely it's going to be a rare that's in a set that where the rares are basically commons. Kind of like how we just opened a, this is perfect for wild survivors. We just opened a wild survivors pack and that's six rares and one super. So rare is essentially a common. That'll be the rare we get unless I'm wrong and there's a starlight rare in here. Hey, pot of greed. It is a regular rare, but hey, pot of greed. That's probably the best rare you can ask for. Unless, well, probably if it comes off the ban list, probably be insane, but we have a pot of greed. So honestly, that might actually be worth a dollar. We're going to see how much money we can make back. We spent six of these times five plus tax. So it's like whatever that is, like 635 or no, 632.50, something like that. So we're going to see what we can get. We'll put it at 32 bucks for fun. We might have made back $1. That's a good start. All right, our commons are Gernia, which is the champion pack two ultra rare. So pretty interesting to see that malevolent. These are actually kind of old. These just started deck though. Yellow belly Doni. Shinra Nui Samurai. Ghostrick Yeti. I wonder if any of these are money. Wait, is that the same card? We got two of the same card. What is this? Come on and give us some real cards here. Ghostrick Skeleton. We have Vampire Grace for the vampires. Chubo. What is this from? Return the duelist Chubo. And I don't remember that card. Patricia updarking his first deck from a start. This is an old starter deck actually. Infernity Doom Archfiend. We get a Synchro. Malfi Pony. That's a real new card. Rampaging Smash Tank. Dogmatica. Gogi Powerload Ogre. Dark Lord Uprising. Soldier Gaia. We have Fury of Kaishin. Curse of Dragon. The Curse Dragon, very nice. And it's not the, not the Dark Magician we're looking for, but it's probably half of it. And then AI Shadow. So okay, I mean, honestly, that's probably the best one we're ever gonna get. So good start I guess. Now it's time for a little duelist Nexus. Look, we never pulled the Magician of Dart Souls of Chaos. The Chaos Souls Magician. The Magician of Souls and Unity. There we go. We have Duelist Nexus. Let's go. We believe that we can do this. Today is the day.  One, two, so four. I think it's just four, right? We have the, oh! The Cuckoo Commandant to Crune. A good comment. Let's go. Bedou, the Greed Jar. Not a lot of greed and a lot of jar today. Well, technically not, I guess it was greed as a pot though. Jurassic Power. We have Million Century Ice Prison. The Valence Wave and, okay, Kymer Refusion. Justice Super. We did not get anything crazy in that pack. Okay. Second pack of whatever you can call this. Come on. Okay, the rare is at the, we gotta do this so we don't spoil the rare because that's the exciting part. The rare. This is gonna be incredible. So we're gonna go like this. We're gonna open it like that. We're gonna put that to the back. All right. We have a That is a Portuguese. That is not in Spanish accent though. Sorry, Portuguese fans. Okay. Skilled Brown Magician. Dynamorphia Diplos. Dartron. The Mechanical Monstrosity. Ghostrick Retreat. Ghostrick Siren. We're getting any good cards. Great Double Cast and Caster. Dynamorphia Shell. Submarine Tour Ride. Doll Monster. Bear Bear. Silver Vine. Cynry. As for Lapswell. We have the Dynamorphia Sonic. Myutin Mutant. We have the Smile Potion. Wow, we have the Groza. Epsilon the Magnetware head. It goes along with the giveaway. Cool. We have a Tribe Drive. And it is a regular rare. And it is out of Kings Court. Just like I said, the rare is out of the, they're basically comments because they're from a collector rare set. All right, so we got scammed on that one. Next up, technically not scammed. Okay, don't take that. Because sometimes I say that as a joke and people think I'm being serious. Not technically scammed. Not technically scammed. Just really bad, really bad value. Wild Survivors. Here we go.  I don't know if it's worse than that Mystery Cube. The Mystery Cube where it's 10 bucks. These are only five. The Mystery Cube could be worse. I think there's like 40 cards. So it's basically two of these. So I guess it's like the same. You get five rares. So, okay, we have another rare. Another rare. Okay, a common. Super sewing, Frosaurus. Oh, an advancing soul. Pluton, HG, Super Rare. Oh, eradicator epidemic virus. Because it's this version, it's probably not worth a dollar, but it could be. That was a big card for a while. Next one, we got four more of these bad boys. Oh, I didn't spoil it. I might have spoiled it, but I'll cover it up on the edit. So you guys don't see it. I don't know what it was, but I have an idea. We have a, oh, wait, wait, wait. Charo de Captura de Dragois. Dragois. Laundry trap. Laundry Zentukan. Penguin Cleric. Giant Starfall. Magic Key Battle. Reptilian. Ice Shade Acti. Heritage of the Light. Abyss Keeper. That is a super rucks and special. Sign up, Cascade. Rebuild Deer. We have the Aerosonic. Reptilian, Niamh. Cascade. Heritage. Magical Cylinders. Brave Drive. Ice Shade Tanola.  Oh, for a second, it had like a, it looked like it had texture. And I was like, is this a collector rare? No. Shrooking Lithogym, The Disaster. And it is from Tune Chaos. So get another rare that's really a common. All right, Duelist Nexus. You can turn this thing around. Yet look, this is supposed to be a terrible opening if we pulled the magicians of Bonds and Unity in this. That would definitely make up for it. That'd be hilarious. It would be a little confusing, but it would be great. Let's go. We have a Veda Calanta. Altergeist Revitalization. The Continuing Epic of Charles. Doomstar Oka. Magic Key Deity. Unchained Soul of Charvara. Synchro World. Beta Evolution Pill. And you are finished. That is us, we're finished. We have no chance. All right, all right, it's fun. One guaranteed rare card though. All right, don't spoil this. Last time I got a little too excited, it went right in and I spoiled it. So let's see if I can not do that this time. Like going like this. Yeah, here we go. Now that is it. There's a Starlight at the front of this pack. Just keep that in mind guys. A Starlight Rare in these five dollar packs is going to be a steal. We have Rogue of Indimion. Fuma Wave. Fire Antascatour. We have a Ruxen Special. Evil Hero Infernal Prodigy. Actually a good card. Got a repair recently, so probably not worth a dollar, but still pretty decent. Heritage of Light. Mewtrooper Assault Roller. Giant Starfall. The Gemini's Lord Gold Knight. Rebuild Deer. Reptilian Codel. Laundry Trap. Ice Jade. These are the same cards. Magic Key Locking. What are these from? Okay, Burst of Destiny. Okay, so Burst of Destiny. We have Threshold. We have Knight of Armor. The Ancient Warrior Saga. Armor Dragon Ritual. Reinforcement of the Army's Troops. The Retrain. Fabled Abonk. Okay, and a Hypnosister. We got a super. It is from Pendulum Evolution. One of the worst sets ever, and it's guaranteed supers. So yeah, another super. That's basically a comment. Okay, one more Wild Survivors pack. Let's see what we can get. Will we get a burger or something? I mean, I bought the wrong packs. Feels bad. All right, I don't even need anything in this set. Well yeah, I mean, I would take a burger though. I'd be okay with that. We have Candle. We have Pre-Preparation of Rights. M-Cantation, Talisman, Draup. Very creepy looking. Like, what is that guy? Is that Stinky Pea right there? The stinky Pokemon? Xenomedioris. Okay, super. Those were all duds, unfortunately. All duds. But these, I've been, no, they've been terrible. They've been duds as well. All right, let's see what we can get. Come on, two more. We got two more of these. We got one more Duelist Nexus pack. We can turn this around. We can get something crazy out of these. No spoilers, because there's a Starlight at the beginning. All right, swap it around. We have Lapti Driver, Driver with the left. We have Death Spot 003. Machina Defense Perimeter. Digital Bug Web Soldier. The Doppelganger. What is this from? That's from Crossroads of Chaos. We have Space Insulator. Rockstar Special. The Beaver Warrior from L.O.B. Are probably our best card yet, Beaver Warrior. We have the Subterra Behemoth. Shiny Black Sea Squatter. The Ice Jade. Brave Drive. Ersonic Drytron. Starry Knights. Threshold Boar. The Penguin Squire. Sword Soul Assessment. Giant Starfall. Cyanet Crosswipe. Break the Destiny. And it's a Bear Blocker. And that one is from Tactical Masters, another collector rare set. Final Duelist Nexus Pack. This is really, there are really only a chance to pull something good here. Final Duelist Nexus Pack. We haven't even gotten a foil out of these. Like it's just been like guaranteed stuff. This is it. We can do it. We have a Greed Jar. Epic. Click and Echo. Small Scuffle. We have the Kwee Belt. The Belay Dragon. Signs of the Tistina. The Adada. Grinsaurus Gigacannon. Makanko. And a Super Rare Mirror Knight. All right, final chance. If you guys have enjoyed the worst opening of all time, which we did a pretty bad opening recently. And I think this one is worse because the Pot of Reed has been our best pull. And that was our very first pull. And it literally was the first back. So yeah, it's been pretty bad. We might be at $1 out of $32 or whatever it was. Let's open this thing up. Let's see what we can get. If you've enjoyed it, make sure to subscribe to the channel for more horrible content at this rate. Horrible, horrible content. We have, oh, a Presa de Prata Silver Fang in Portuguese. Gamble, we're gambling right now. Like a terrible gamble. It's like you got a one in a million chance. Like buying a lottery ticket.  We have Soprano. We have the Soul Buster. Oh, how could it end like this? The body buddies? No!  Then the Dragon Balls. What a weird pack. They'll send you. We got Artifacts. Oh man. The only thing you can get worse is if the creepy Kony is in here, which hopefully that will not happen. Zero extra link. Keep it volley. Cluster. I don't think it's going to be in here. Thank goodness. And, okay, Rookie Heel Ogre. Gokie. And a Cynet Kodak. This is also a, yeah, it's a tuned chaos card. So, yeah. Pretty good way to end. If you guys enjoyed the video, don't forget to subscribe to the channel and hopefully we will never have to do this again. Shout out to Tom Fosho, Daxer, JT Show, Puffins of Doom, Ernesto, Diana, America Doidster, Supreme Sage 21, CJ, Leo Guine 62, another Thai show, Ian Moosa, Junior Barney, Mimic Gecko, and Robert Epp. Thank you guys for supporting the channel. I'll see you guys in the next video. Peace.


He saps me Isn't a step for I'm getting a really cheap shop. Yes appears the shield in it and this for everything you can't earn in here, but you Is there? It's whatever done. He vanished the stuff Dispelled shield of priests running a priest Sure Damage on roof. I can't get this but it's not bad part Yeah You might try and step off I'm gonna line. I'm gonna line him.  I've got stone for you Just use the kidney for that. I'm fine Rogue is out of ashes Wardling to you getting the shield. Got it. Hey, buddy priest. Rogue is in trouble. Never mind gouch Good but Spelling room. Okay. Big damage. There's My best stunning priest. I've come priest act longer. He blinds me. I want to sit this you can keep her I'll try. Yeah, but do Now I have to drink you defensive I don't want to eat Now it's getting Yeah Yep, I believe He's that's Okay, I need the innovating I'm coming back to you. Okay. I'm okay. I'm very Getting priests up on priest. Sorry. Okay. It's gonna be I should be able to get the fit nice to drink it They're on me. I don't want to drink at this. It's not dance Oh Maybe don't need to Precise him I can bash I'm gonna blinds Dancing Precise trying to drink as long as we don't let him drink. I'll still Drinking I'm priest. Yeah drink up. I have skin. I'm totally okay During me here. They're watching us in nothing. That's what We should finish off now. They have that Gage me. I am gonna have to remove Phil probably and I see doesn't get a man for it Precise fit I should just the silver. I got the field. I didn't get wrapped your problem. Huge Yeah, gage that's gonna be so out. Maybe I should come It's belly. I love you as well I'm not priest Vanish I'm gonna respect gonna get sat Swapping to regen for That media. He wants to be able to Increase yeah, I'm getting a bit head by should be okay You've shot our shoulder. He has done smithing During word, you get it. It's huge.  You're friend priest. No trinket. He think I'm okay. I'm okay. I'm okay. I won't die Even though he fiended me. I'm still fine Nice, I can use a ruse. Yeah, you can feed me here. Okay. Do I I don't get a problem. I just charge the priest. I just charge for it.  When increase the shields are undispellable man. I saw a good boy. Nice Get them priests from yeah I'll keep her and I recently egg down on red I'll go rickson. Maybe I was a quick priest get the gauge


What is going on guys welcome back to the channel critical overload here So this will be a spoiler-free review for immaculate immaculate is directed by Michael Mohan It is written by Andrew Lobel or Lobel and it is starring Sydney Sweeney David Burner David Burned Jonathan DeVino Teddy schwarzen schwarzen and Michael Heimer Now this film is revolving around Cecilia played by Sydney Sweeney and American None of Devote Faith who embarks on a new journey in a remote convent in the picturesque Italian countryside Cecilia's warm welcome quickly devolves into a nightmare as it becomes clear Her new home harbors a sinister secret and unspeakable horror Now immaculate I would have to say is a very visceral Religious horror film that may stumble at times towards its finish line But this film managed to restore my faith in 2024 releases Horror has truly been a disappointment so far this year and I needed this movie to deliver and it did that and then some So this is on the list of W's joining late night with the devil, which is the only W I have on the horror genre this year and Dune which isn't horror, but you get me I don't want to give it too much praise just to avoid over hyping it But hats off to every person who had a hand in making this movie I had a love-hate relationship with this screenplay I want to say our protagonist Cecilia survived a near-death experience Sometime ago and has decided to leave her life in America after this convent recruits her Lobo doesn't really spend too much time exploring Cecilia outside of that But the characters surrounding her are so suss shady or unreliable that it's enough to get you invested in her as a Character the way everyone is so fixated on her makes everything uncomfortable Unsettling and it's just a constant feeling you have while watching Thanks to the way the characters are written granted. They are underutilized There's still something about them that kept the story and the ongoing events very disturbing her decision-making Cecilia that being I do want to say this the decision-making from her throughout the film keeps her likeable as a Protagonist there might be a few dumb decisions here and there But immaculate seem to rely mostly on a character being aware of their surroundings Trusting their instincts and then acting accordingly like the viewers like ourselves watching would that was a breath of fresh air to see Not that you haven't seen smart people in horror films in the past but you know, there's the Cliche around horror films that there's just stupid people in them making dumb decisions And I felt like Cecilia was a very smart Protagonist to follow speaking of characters though most are underutilized and underdeveloped as I was mentioning earlier Which is unfortunate because without the shady antics that characters do and their off-putting fixation on Cecilia None of them would have been remotely interesting What this screenplay excels at is exploring how religion can be exploited or used against us by corrupt individuals and Building intrigue around figuring out what this secret is is being kept from Cecilia or what the secret is being kept from Cecilia However, it didn't dig as deep as it could have when it relates to those themes of exploitation with religion I'll blame the runtime for that one because we could have had another 40 minutes added on to this runtime I appreciate the fact that the conflict in the screenplay isn't being laid out in the most obvious fashion Only for the film to then spend five to ten minutes dumping it all on me as if I'm a blithering idiot It literally has clues that are sprinkled throughout it But not in a spill the beans early when we still have an hour left to go Sort of way the main the way movies like the nun do when the mystery is solved during an opening sequence But now let's wait for everyone else to figure it out too for another hour or so I'm as lost and unsettled as Cecilia is and I'm eager to figure out what's happening Immaculate even lets me interpret certain aspects of the story, which I also love I wasn't being spoon-fed everything The dialogue wasn't unbelievable Every word was fitting for how people likely would talk to one another the scares were Annoying though at times because Immaculate does lean on jump scares more than three times Which is getting on my nerves But then it balances it out with this unsettling imagery and a consistent unease that swells as the film is progressing If Sidney Sweeney wanted to convince us that she is ready to become the next screen queen She didn't have to go this hard y'all. She really didn't the lady is delivering Some of her best work yet in this role Cecilia's disgust pain sorrow everything she's experiencing I was experiencing it as well because of how brilliant Sidney Sweeney was as Cecilia Michael Mohan's direction I would say was phenomenal. I couldn't look away from anything on the screen, especially Sidney Sweeney's performance Most of the performances were superb and make up for how underdevelop every character not named Cecilia is Absolutely fantastic cinematography lots of white shots. They kept me on edge. Thanks to the surroundings being appearing very dreadful One particular shot in a field with Cecilia running made me anxious There was just a lot of stunning camera work in this film. They kept the tension high at all times now that finale And if you've seen the movie, you know what I'm talking about This is easily my favorite one take shot of the year so far and again if you've seen the movie You know exactly what I'm talking about. It gets very disturbing Sidney Sweeney is putting her all into that sequence I would say it did go on for a little bit too long at points when she is screaming like that And if you know what I'm talking about again, you know what I'm talking about Immaculate I again don't want to over-hype it, but this is a very solid horror movie for the religious horror genre or that subgenre of the horror horror genre It was very good had a lot of good performances Specifically by Sidney Sweeney who's carrying the bulk of this the pacing I didn't take too much issue with granted I do think that the third act kind of was here One second and then gone I would have preferred certain things to have gotten a little bit more fleshed out We allowed certain things to breathe a little bit longer, but for the most part I have To give immaculate a seven out of ten I do think it is better than late night with the devil late night with the devil's issue just comes down to me Not really being able to connect with a lot of the characters unless the movie was dumping things at me Whereas with immaculate, I'm not really being dumped a whole lot I'm just being allowed to experience the film. It's building intrigue around things like certain characters and their motivations Dialogue is dumped to keep you intrigued like one character saying it should have been me And I'm like, what are you talking about? And then I find out what it is later on in the movie of what this person is talking about I loved all of that. They really keep the mystery mysterious Despite the characters can be underdeveloped There's that love-hate relationship that again I have with the screenplay because while it gets so many things not so many but some things wrong It also gets so much right that I love and adore about the screenplay and again, Sydney Sweeney Phenomenal job. This is her best role yet. I would say I'm gonna go out on record and say that Let me know what y'all think about this down the comment section below. Have you seen the immaculate? Did you enjoy it? Did you not enjoy it? Why or why not? Let me know all of that down below if you haven't already, of course Make sure you subscribe turn on post notifications so that you never miss a video in the description I'll have links to all of my social media accounts. I'm on Facebook, Twitter and Instagram You can message me there of course to let me know if there any movies news or views Let me to cover in the future and with all that in mind guys. I will see you in the next video


Okay. Hello, everybody. Can you hear me? Good. Thank you very much. Welcome to our presentation. I'm really excited to see that many people here. And our presentation is about the integration of OpenContrail and Open Daylight with OpenStack. We want to talk today about the pain, the gain and the lessons learned while integrating. So the contents of the presentation will start with general description of what to expect. Then we'll introduce ourselves and give credits to people who were very kind to help us with this presentation. We're going to talk about what SDN is and discuss the benefits of SDN in modern networks and touch on popular SDN controllers, which is in our presentation will be OpenContrail and Open Daylight. And we'll discuss the industry trends with regards to those SDN controllers. And we have a lab demo that will be used during the presentation to demonstrate different things we're talking about. So this is a tutorial style presentation mixed with some architectural descriptions. So we want you to have a recipe that works. And this was the goal of our presentation. There will be no focus on specific features of any particular SDN controller. And we are focusing on integration with DevStack today. We're assuming that everyone in this audience has basic understanding of OpenStack. And there will be no vendor-specific discussions. We do not go deep into protocol discussion. We're not going to talk about OpenFlow, SSMPP and stuff. And we'll avoid discussions about which SDN controller is the best, or which one should be and should not be used. It's not the point. We're here as we work for Ericsson. And we're here also as enthusiastic members of OpenStack community. And we strongly believe in open source collaboration and development in open source framework. So let me introduce myself. My name is Konstantin Kamaristi. I work for Ericsson. I'm in telecom industry more than 20 years. I worked on different projects with different products. And time came to get more familiar with software-defined networking. Hence we started working on this. And let me present my colleague, Syed. He's also a telecom veteran. He has vast experience in network equipment, network projects related and many other things. And would like to say special thanks to our colleagues from Ericsson, Team Inrich and François Limarchand, who have helped us a lot, inspired us, and shared their vast knowledge on the subject. The SDN is defined by Open Networking Forum. It's a long definition. You can read. But I would like to focus on the highlighted keywords. It's a dynamic solution. It's manageable solution and cost effective. This is very important and adoptable. If it's not cost effective, it's not going to be adopted. The solution should decouple the network control and forwarding functions. And it should allow direct programmability of networking devices. So this is in brief what SDN is. SDN comes to solve certain problems with traditional networks. We know that there are certain things that traditional networks are suffering from. I've listed a few points here. The traditional networks are mostly hardware oriented and static in nature. So any changes that needs to be done will require manual configuration. And sometimes it's difficult to achieve within short times. Maintenance windows required. And errors are possible. So the town times are possible. The distributed control plain-leg scaling. What does it mean is that the control decisions are distributed across the networks in different devices. So it's hard to synchronize that and keep everything under control. More than that, management plain sometimes uses proprietary implementations. So they're not always compatible and interoperability is not always great. So these are the shortcomings of traditional networking. So here's a great slide. It depicts two use cases on the top where something like cloud is. It's like a wide array network east to west with lots of routers and some networking equipment. Let's say if we need to introduce some changes or reconfiguration in the network. This requires work on all of those devices. And like I said before, it's going to cost a lot of time, effort, sometimes manual labor, and actually can lead to errors and town times. Or on the bottom part of this slide, there is a data-centric use case. For example, if we need to create another web server and provide a VPN tunnel for this server to be accessible from outside.  So the SDN is supposed to bring changes that will make life better in this respect. So the centralized management and control planes, that means that the control function that was previously divided between control and management plane now can be centralized in one controller, one system. Another benefit is that control and data plan, plane can scale independently. So you don't need to scale control plane just to be able to scale the data plan and the other ways. The interoperability is improved. That's the promise of SDN. The networking devices can be programmed automatically. And this is making operations cheaper and more efficient. It's possible to start using commodity hardware, also making operations more efficient. And the adoption of SDN would facilitate migration to software-based networking. Think of a paradigm shift that happens in the last decade in virtualization in computing domain. So the same thing is about or happening already in the networking domain. Finally, the wider adoption of SDN will enable also adoption of scalable and dynamic applications. So that's the next thing that's coming. There are many SDN controllers on the market. There's a long history behind it. We have put a link to some exhaustive list of SDN controllers available. You are very familiar with one of them, which is Neutron. And today, we're going to discuss open control and open daylight. In order to demonstrate this integration that we're going to talk about today, we have built a small lab. The purpose of this lab was exactly to show that this can be done in a very small environment, fairly easy, and it's easily reproducible and gives ability to experiment with SDN concepts in a small and cheap environment without big expense. So as you see, there is a Nuke Intel little box with 4 CPUs, 16 RAM, a gigabyte SSD, and 250 gigabyte SSD. So we put latest Ubuntu image on it and activated the nested virtualization. This is important. Most of the cookbooks miss to mention that step. Maybe everybody knows, but some don't know. So this is a nasty surprise when you deploy everything and you cannot run the VM on top of VM. So you need to enable it from the base up. Here's one of the views on architecture of open control. So I'll take over and we'll go over the architecture of open control. But before we do that, a word of caution. If you're trying to explore the integration of SDN controllers with OpenStack, and if you do it for two weeks, this is what you get. And by that, I mean gray here, and a little bit less here as well. So we'll try to make that pain easy for you. So the end result is not like this. Still bright and handsome, but black here. So let's maybe understand a bit about the architecture because what we want to do is we want to make it easy for you when you integrate the components and when it fails, where do you find the problem? I think that's one of the biggest challenges of open source and OpenStack and the integration. So let's take a familiar view and we start with the neutron.  So if you don't have SDN at all, you still got neutron. So we've got the neutron which actually talks to the REST API in the management layer of the open control system. I was trying to move the mouse on my screen, but actually we don't see that there. So let's see if we can break it down. Okay. So the view is slightly smaller, but I think it will help us explain it a little better. So you've got neutron on the top left corner and you have your applications, OSS, BSS, GUI, etc. These are the ones that will actually want to create those dynamic networks, the virtualized networks. So they push in the request towards the REST API for your controller. Within the controller, you have three different main sub components. You've got the configuration node, the analytics node, and then the control node. The configuration node is responsible for receiving the request and doing a high level to a low level translation. Analytics is responsible for continuously monitoring and analyzing the current deployments and seeing what's going on in your forwarding plane. And the control plane is responsible for pushing the request. Another way to look at the same is to look at the flow control. So here we are trying to show that OpenStack sends the request towards Neutron server. Neutron servers talks to the control configuration node. Configuration node wants to make sure that whatever request has been sent is persistent. So it needs to store it in the database. Once that is done, it also pushes down to the control node and the control node is responsible for pushing it onto your forwarding plane. One last view about this and I promise I'm not going to drag this any further and we'll go directly into the installation. But this I find really interesting because here you can see the setup. So traditionally speaking, we come from the ODL family and ODL came more naturally to us because we worked with OVS for a long time. So the first thing we noticed when we were trying to deploy OpenContrail is where is my OVS? And there is no OVS. So you have these kernel modules which were built in and they're part of a kernel. So instead of the OVS agents, you have the Vrouter agent which replaces the OVS agent. And then instead of the data plane that you find in OVS, you have the V kernel module which does a forwarding part. The rest of the setup is very, very similar and this picture I think is a good depiction of what to expect when you're trying to analyze the call flow. So as a next step, we'll take you into the details of installation and Konstantin has a lot to talk to you about the pains, gains and what we've learned. Okay. Now it's not so a lot, so it's shorter. So we have installed a virtual machine on top of our KVM host. It's important to use exactly this version of Ubuntu 14.04.4. Most of the cookbooks that you can find, many of them on the internet, do not mention the last digit and this is the one that is in the details. The compatibility of libraries and image are very important and so far this is the only configuration that has worked for me and believe me, I tried a lot. So we've used this size, like a 15 gig of RAM and 4 CPUs, 70 gig of hard drive for the VM and we'll create two VMs basically on this host, one for OpenContrail and DevStack integration, the other one for ODL and DevStack, but we create them with the same size of the virtual machine and we can run them at the same time in parallel, so kind of over committing, but it's not a problem because there is no load in this environment, so they can coexist peacefully, which we'll show later. So again, we need to not to forget to configure nested KVM Intel nested feature. You need to edit the grab file, update grab reboot and verify that it is in place. So follow the steps as it's shown. To have more control of the installation, I usually disable resolveconf and the HCP components. So in the middle of installation, sometimes I've seen that resolveconf defines something different as a gateway or some other DNS servers and then the installation may fail. So I just delete that. And we need to install Git. We clone the JuniperContrailInstaller project. I recommend to clone at the same time OpenStack DevStack project. So we're pulling the master branch from Juniper OpenContrailInstaller and we're putting stable Mitaka branch from DevStack. You should create the two environmental variables, ContrailDeer and DevStackDeer for it somewhere. So it's always there when the user logs in. And now we're coming to configuration. We should have a local RC file which can be copied from samples. And I recommend to uncomment the line ContrailRepoProto equals HTTPS. So in this case, the getting of the packages that are needed during the installation will be done over HTTPS. So you would not need to configure SSH key. I recommend to change the number of jobs to maximum number of CPUs available on your KVM host or available to the VM. This is to make the build and installation a bit faster because it takes a long time. So we'll let four CPUs work at full speed. And something that I found during the installation, they need to enable multi-tendency in this file. Otherwise, the installation will fail because the some network for certain tenant ID cannot be created and the installation will fail. So this has to be done in two places. I'll show the later, I'll show the other one where it has to be done. So the steps to build OpenContrail are simple. So there is a file, the script Contrail.sh. So we need to build first. This takes the longest time, one hour, 12 minutes for my setup. And then we install. That's another half an hour. The other two steps are fast. As a result, if these two environmental variables were defined before and the DevStack GitHub project has been cloned already, then we will be able to run the OpenContrail status verification script. So you should see all the components in active state. And this is a good state. You should see that. Then we go into the next step, which is building DevStack. So we go into DevStack folder and copying the glue file that is provided with the Contrail installer project. We're copying it into DevStack Lib Neutron plugins folder. Then we create the local RC configuration file. And we need to change a little bit the configuration to match the environment. And disable this optional, but I recommend to disable Cinder service. So we don't need to change the volume at this time. And it's going to make things easier and faster. So when we run this StackSH script, it's always coming to an error very quickly because of unmet dependencies. Actually, the error prints out the recommendation how to fix that by forcing the installation. So I just chosen that method. And then we run the Stack.sh. After 20 minutes, we get another error. And this error is showing up in most of the cookbooks available on the internet. You will see that this is a popular fix. So it's also in this cookbook. Then I recommend to run the Unstack and rerun the Stack again. And yet we get another error after half an hour, which we can work around by restarting the whole system and rerunning the Stack again. So this takes another eight minutes for the Stack to start. And it's important to mention, I don't know if I can highlight it. No, I cannot. Before building the Stack, okay, one second. I wanted to highlight this section. Okay, so now can you switch back? Please. I found that if this is not done, then you would not be able to open the VNC consoles to the instances that you're running. Actually, you will be able to open the VNC consoles, but you cannot type anything there. It will get some keyboard errors. So this is a workaround to make it work. As a result, you get the functional environment with the Stack dashboard and OpenContrail GUI. And that is the working system. And now we can experiment with that. So now we're switching to ODEAL. I just wanted to highlight a few things quickly before we move on, because a lot of us overlook these things. First of all, why Nuke and why DevStack? We are lucky to be working for a company where if we want to do a project, we can get a lot of servers, but not everyone has that luxury. So we wanted to create a cookbook that can be used and deployed for anyone and set up the environment on their lab. So when your manager comes and asks you to evaluate these technologies, you don't have to rent out or get the equipment, a lot of service. The other thing that Constantine figured out, there's a lot of recipes that tell you how to deploy OpenContrail and ODEAL. And they tell you, okay, you need to use Linux or Ubuntu 14.04. But the amount of variation when you go from 14.04.1 to 14.04.2 to 14.04.3, all the way up to different stuff, it changes things beyond your imagination. So if someone comes and tells you that OpenContrail and integration of OpenStack was so 2014, you tell them to talk to us and we'll show them the logs that we actually produced trying to make it work on different integrations. So apparently it's very easy to do, but don't take it for granted. So we try to put in as many details as we can.  Also, it's worth it to mention that since we are taking the code directly from the repo, and repo is changing constantly. So whatever worked for you yesterday, it won't work for you tomorrow. These are the challenges that you need to be aware of. And that's why you see, so luckily the light is not that much. So you don't see the gray in my hair, but you would definitely see it next time if you're still doing this. And let's go into ODL. ODL was a little more natural to us because we've had a chance to work with it for a while. So apparently there's a lot more information that was easily available to us for ODL. It seems it's well documented. So perhaps a recommendation from us, from open source enthusiasts to open control community, please start producing the documentation that will attract more people to open control as well if you want it to be successful. Just like what ODL has done. So let's start without going into too much details of that, let's go into ODL. So the architecture of ODL is based on microservices. That gives you the ability and flexibility to add and remove services on the runtime. You don't need to reinstall, recompile and things like that. You want to add BGP. That's a component.  I love that aspect of it. Platform independent. I was having a conversation with Konstantin about it. And of course we say that ODL is platform independent because it's run as a JVM. And then we got into a different discussion of, well, okay, that can be argued. But this is the information that we found on the ODL.org. So we've decided to do a little bit of research on that. And I think it works pretty well. The other important thing is that it's at parity with reference to Neutron. A lot of us here because we are talking about open stack. So we are open stack centric. So when we start exploring SDN, we are more familiar with Neutron. So anything that claims and works actually and we've tested it, if it's at parity with what Neutron is, it's naturally more easy for us. Now let's get into the scary part of ODL. If you're trying to understand the architecture of ODL, and this is a diagram that you see, it might look a little overwhelming for you at the start, but we've tried to break it down. And I'll try to explain it in a way that I can explain it to my five-year-old nephew and he kind of understood. So if he can understand it, I'm sure you guys can understand it too. So let's take a top-to-bottom approach. You've got the northbound interface. The northbound interface is where you'll receive the request from OpenStack. You'll receive the request from OSSBSS. And that's where you can actually deploy the application to ask ODL to do what you want it to do. On the center there, you've got the control part. So this whole part, this is where you deploy your, this is the modular MD-SAL architecture. And you have the microservices running here. So you receive the request, and then depending on what the request is, you forward that request to that particular module. That module does what it needs to do and converts that onto the hardware equipment or virtualized equipment that you're working with. So if you're working with the typical hardware deployed, Junipers or Cisco or Sianas, and you have a plug-in for those using protocols like XMPB, actually OVSTB, OpenFlow, BGP and things like that, then it will get translated here and it will get pushed down towards the southbound interface. One last thing about this architecture before we go and see how we've done it in our lab. So this is the diagram that you actually see. These are the different connections between different services. I will talk only about the OpenStack aspect because I think that makes more sense instead of talking about other things. So here you see that the OpenStack is sending a request towards the Neutron API. Neutron API sends a request to OpenStack Neutron services running in the Open Daylight Controller platform. Now here you have the option of using VTN, which is a new feature, and that sends a request down to your OVSTB. OVSTB is responsible for talking to your different OVST or host servers and pushing the configuration and the flows with OpenFlow onto your hosts. And if you're looking for the plugin architecture, this basically shows you the plugin architecture where you have the Neutron. We've eliminated NOVA and Cinder, et cetera, et cetera. It makes life easier. It makes it easier to understand as well. And then you have the ODEAL controller in the center. And we see that everything actually is going through the MD cell data center. So you receive the request, and then this is the controller for the OpenStack services, and then you have the OVSTB and the OpenFlow talking to your compute host. So now let's go ahead and look at the installation that we have in the lab, and Konstantin will walk you through that. Thank you. The five-year-old nephew that understands the concept of Northbound Interface is a little bit scary, but... You have the genes in the family. Okay. So the OpenDay Lite and DevStack integration is also running as a virtual machine. We've used the Ubuntu 17.04, and the size of the VM, the same size as the OpenContrail VM. Same trick is used for controlling the IP environment, no resolve conf, no DHCP components. We're installing Git, and we're creating a special user that will be needed for building and running OpenDay Lite and DevStack. So the user is called Stack. So you will find these instructions in absolutely every cookbook that you can find on the Internet and in the official ODEAL documentation. So we clone the OpenStack DevStack and proceed with configuring the installation with local confile. I have found the very detailed instructions in the link provided on top of the slide, and I advise you to read through and try to understand all of the options available. You probably don't need all of them, but it's good to understand what they are before spending hours in reinstalling the system and finding that you're missing something that was important. But for your convenience, I've compiled a list of parameters that you should configure in order to get a working installation. So on the top, we configured the IP connectivity. And on the middle of the slide, there's lines starting with ODEAL underscore. We specifically want to install the Boron SR3 release. And these features that are listed below and these are the features that will be available in the deluxe GUI. And by default, the ODEAL deluxe core is installed. And that will not let you see all the possibilities in the deluxe GUI. So I recommend to put ODEAL deluxe all during the installation. And also, we've added ODEAL layer 2 switch all. So just use that and that should work. And there is a bunch of services that we need to enable and disable for just to fit them on one slide, I've listed them in a line format. But in the configuration file, each parameter needs to be in a separate line. So these are the configurations. Running stack.sh takes approximately 20 minutes. At the end, you will get the URL for dashboard and credentials. And also, I've added this boxed text at the bottom of the slide. This is the URL to log into deluxe GUI and credentials. So as a result, you have dashboard and the deluxe GUI. So if the parameters were not correctly set in the configuration file, you will end up only with the topology view. And the rest of the views will be missing. So if you use the configuration as specified on the slides before, you will get these views in the GUI. So there is a nodes view and Yang UI, which I understand is kind of SDK with the possibility to send rest API requests to different services and parameterize them. And it's interesting to experiment with that. And there is also a young visualizer which helps to visualize the data models and objects created in the configuration. So as a result, we have this environment with a host running two virtual machines. We've noticed that running side by side, the OpenContrail virtual machine consumes more CPU than the ODEAL without any load in idle state. So it's something interesting. We don't know. We never tested yet the system under any kind of load, not in this environment for sure, but this is interesting to get these metrics in future exploration. And now we're getting to the end of the presentation. And we'd like to discuss the industry trends in terms of adoption of SDN controllers discussed today. We have a list of operators and vendors on this page that are using OpenContrail. And they are listed on the OpenContrail website. And these are big companies. And we have a list of operators and vendors that are involved with Open Daylight. It's interesting to see that AT&T and Juniper are also involved in this project. So it's not an indication of good and bad. It's an indication of specific need, use case, scenario. And so it's good to understand the difference. So also I would like to say that on this summit, there are many very knowledgeable people presenting the SDN controllers. Do you want to say? No, no, go for it. So we've seen the Juniper booth. And it would be interesting to talk to engineers from Juniper about this. And you can ask them more questions. And for sure they will give you more details. And add something exactly. Thank you. And yes, I'll give the mic to Mike. So yeah, we've tried to be, as we were explaining before, we want to be vendor neutral. We are not here to compare one with the other. So Konstantin here is telling you guys to go and talk to the guys in Juniper. I'm here representing Ericsson and ODL side of it. So make sure to drop by the Ericsson booth as well. We've got some really fantastic people who know a lot more about ODL than ourselves. So this is something I promised the marketing guy, so that is taken care of. I forgot to mention that Ericsson is actively involved with Open Daylight project and makes a lot of code contributions upstreaming into Open Daylight project. So this is important to mention. So we have, I think we started a bit late because of the setup. So we have an option to, or actually we could have shown you the lab setup, but I think we should give time for the next presentation presenters to come in. Can I ask a quick question? Sure. Actually, two. One is, did you do Apple to Apple comparison in terms of the performance? Absolutely not. So that was the whole idea. We're not here to talk about the advanced Apple to Apple comparison. We are here for the people who actually want to start the exploration of SDN with OpenStack. Next question, please. And let's make it quick, please. Okay. So in terms, you showed ML2 path, the Neutron path as well as the monolithic ODL. Correct. So the backend is exactly identical or are there any differences? So the thing is architecture is changing from one release to the other. For example, ODL last time had a rev one for the ML2 side and they realized that somebody in Japan was doing testing and they found out that it can actually cause an event where you have parallel threads that can try to register the same network in the database. Now, in order to resolve that, they had to change the architecture and now there's a rev two available. So as we move forward, we are actually trying to analyze different paths of what is the optimal way. So it's not a set architecture. It will not be final. It will continue to evolve. Guys, thank you very much. Thank you very much for your attention. Thank you very much.


This is one of my ranting videos. Remember, it's going to rant about something so if you don't wanna hear me rant about something? Don't watch this video. Today, I'm gonna talk about JavaScript a little bit and scripting language is in general, but definitely JavaScript. In the last rant video, I talked about HTML and how it's not a programming language, but how much I still love it. Well, a lot of people talk bad about JavaScript and about how slow it is, which is just an over-exaggeration and how bad it is for some reason. I love JavaScript. I use it for a lot of things. Now, in the last video, I talked about how I used HTML for GUI for a lot of my programming languages and it's true, even when I have a lot of shell scripts that I use HTML as the interface for. And yes, I can use a shell script and generate the HTML directly and that'd be fine, but really, you're not getting the full benefits of HTML if you're not incorporating some JavaScript in there. And that's not a bad thing. Now, some people complain about how JavaScript is slow. It is not the fastest programming language. It's a scripting language. Scripting languages generally are slower than compiled languages. So yeah, JavaScript's gonna be slower than something like C. Some people, I'm looking at you, Ryan Lunduk, have said, well, the reason JavaScript is bad, one argument for that is if I came to you and said, I rewrote the Linux kernel in JavaScript, you would be like, well, that's great, it's gonna be so much better now. Yeah, that's a valid point, but it's still a bad argument because if you came to me and said, I rewrote the Linux kernel in Bash or I rewrote the Linux kernel in Python or Perl or any scripting language, I would not think that's a great thing. I would be amazed if you did that. But it's a not a valid argument because all those languages are good. I love Python, I love Bash. I think JavaScript is great as well, but I wouldn't write the Linux kernel in or any kernel. Some programming languages are more focused on other things and something lower level like kernel needs a lower level language like C. That being said, doesn't make JavaScript bad. Another argument, again, I'm looking at you, Brian Lunduk, who is kind of the way you constantly complain about JavaScript kind of prompted this video. You complain about websites and how poor a lot of them run and how you click on a tab on a web page and it supposedly uses a gig of RAM to load up the drop down menu or you're scrolling through a page and it's not because you're using JavaScript. It's because they're bad programmers because a lot of web designers are just that. They're web designers, they're not programmers. They don't know how to program properly and they try to jam all these things there and all of that, but they put in ads in the pages which are going to cause problems because they're pulling these from all different places and they're trying to pop out in front of you. It's not because they're using JavaScript, it's because they're rich. They're rich. They're rich. They're rich. They're rich. They're rich. They're rich. Because they're written poorly and I think a lot of times when people complain about different languages, their complaints are invalid because they're complaining about the language and really it's the developers.  I will say for one, I am not the best programmer in the world but I test my software. I go, when I put something on my website, I go to Walmart or Target or wherever they have computers and phones and stuff and I'll go to the cheapest, smallest phone, you know, this $50 or $100 phone or tablet and I check it on there and see how well it runs. And yeah, if I'm making a video game, it's probably not going to run very well on there and maybe if I did write it in some other language, it might run a little bit better on there but chances are $100 phone isn't going to run a 3D, a first-person shooter very well. And but yes, using a faster language would help in those cases. But on my website, for example, there is some JavaScript in there that loads the video search and you can start typing and it starts filtering out the videos. And I can say for sure, it works pretty good. Even though my code is not the best and not even the JavaScript but my server-side software isn't the best in that example because I'm not using a database because I designed that years ago and it's just pulling from a flat plain text file that once a day I have a cron job, pull my newest videos and dump them into this text file and add to the text file. And then I have either a PHP or a Bashcript. I can't remember what I wrote it in because it was so long ago. You know, basically just grep through it and output based on your search. But it still works great. In fact, I pulled out a pretty old computer, two pretty old computers I have today. One that has a half a gig of RAM, a little netbook and another one that only has 750 megabytes of RAM. It's a little more than a half a gig. And you know what? It took two or three seconds for it to search the videos and display the icons. But that's not bad for an old machine like that when you're searching through a couple thousand videos, grabbing the thumbnails from YouTube, so from an external site and loading them up there. And it's doing the search every key you press. So I think that's pretty good. And again, it could be written better. That being said, JavaScript is not the problem. I think it would be a lot worse if I had a plain text, plain HTML that you had to do the search and then hit submit in the whole page reloads. And you need JavaScript if you're going to do those real time searches and stuff like that. So JavaScript is not bad. It's better than just using plain HTML. No, no, you might be saying, I like using the shell when I'm web browsing. JavaScript is just horrible for that. I agree. There aren't really any shell web browsers that support JavaScript. If the page is written properly, there's going to be some sort of API. If you were to look at the page in a GUI browser, you will be able to see the network requests. And if the page is not trying to hide it from you, you should very easily be able to pull that information. So basically, you open up my website in Firefox or Chrome and you open up the developers tab. Start typing. You'll see that it's calling a PHP code. Well, now you can call that from your shell and you can pull that same information without even going into a browser just using Wget or Curl. But I've got a step further and it doesn't take much to add the shell functionalities to your website. If you go to my website with Wget or Curl, it will automatically give you instructions on how to use the website using Wget and Curl. And then you took it even a step further. There's a link on my website that says shell that you could actually, if you were to go there in a text browser such as W3M or links, you can use the page that way where it actually gives you a search field. But you can use my page just using Wget. Even if I didn't add those features in there, you could figure it out. But I put that there for you and I'll probably do a video on that. But I just wanted to point out JavaScript is not as bad as you think. The problem is bad programmers. If you have a good programmer, you can make any programming language, even ones that are crappy, do some decent stuff.


I am not the face of a heart attack. I'm healthy, I'm active, I hike, I ski, I love to be outdoors. And I had a heart attack. When the pain first started in my chest, I remember thinking to myself like, this might be a heart attack. When I got to the emergency room, the doctor came in and told me that there was trauma in my heart and now we need to admit you, then things got real. I did tell her this because of her age that we might find this entity known as SCAD. It stands for spontaneous coronary artery dissection, so meaning a tear in the coronary artery. It's an issue that mostly affects women who are below the age of 50. SCAD is not a regular heart attack. It can do damage to the heart, but it's not the traditional risk factors such as smoking, diabetes, high blood pressure, high cholesterol, or family history. After I had the angiogram, Dr. Rivera came in and showed us a still image of my artery where they could see the tear. What is helpful here at Kaiser Permanente is I also have an interventionist, someone who is even more of an expert in the coronary arteries, to take a look if I have concerns Everybody comes together as a team, including our nurses, our lab, follow-up, our clinical specialists and pharmacists, our mental health care. All of that is available without having to have a second referral outside the system. My experience with Kaiser Permanente's cardiac care was phenomenal. Dr. Rivera and everybody that I worked with was really attentive to me. I remember each one of them coming in and really connecting with me and looking me in the eye. Linda took it all in stride. I love seeing a patient walk back into my clinic after I've seen them in the hospital and they are back to living their life to their fullest. Now that I've recovered, I think every day about loving my people and my kids and the people that mean the most to me and making sure that they know I'm going to be around for a long time.


Welcome, or welcome back if you're a graduating student. It's wonderful to see you all here, although actually having said that, it's very hard to see you in the audience at our first graduation ceremony of 2012. My name's Paul Webley, I'm the director of SIAS. Now I've been an academic for 33 years now and I've attended dozens of degree ceremonies, but they still bring a lump to my throat and sometimes tears to my eyes. It really is a great experience to stand here and see the Logan Hall shimmering with pride. I've been a parent of a graduating student twice and I hope in three years to be one again. The last time was in 2007 and I can still remember the details of every graduation and it wasn't until I was a parent that I really appreciated what graduation ceremonies were about. You're here for your parents, you're going to have a wonderful time, so thank you. I'm delighted that we can share this special day with the family members and friends of graduating students across the world who are unable to make it today. The ceremony is being streamed live on the internet, so please don't pull any funny faces because the camera might be roaming around the audience. I'd just like to begin by introducing Dr Tim Miller, the chairman of the SIAS Governing Body. He's going to preside over today's ceremony. Tim has been a wonderful chairman of SIAS for the past four years. He's been incredibly generous, engaged, supportive and critical when needed. He's really wonderful. We're very delighted that he's agreed to continue as chairman for the next four years. I'm just going to pass over to him, over to you.


card number eight kill them all let God sort them out look at this delightful dude Thomas Posey Thomas Posey who's this guy a nice looking guy kill them all let God sort them out lovely lovely card number eight mercenary soldier Thomas Posey in July of 1983 Alabama grocer Thomas V Posey an ex-marine founded the civilian military assistance CMA project in December Posey and had organized a group of retired military personnel and Alabama National Guardsmen for the purpose of sending paramilitary teams to train equip and participate in military field operations against the Nicaraguan Sandinistas the CMA received surplus military equipment from the 20th Special Forces Unit of the US Army in Alabama a group whose participation in CIA covert actions goes back to the Bay of Pigs invasion of Cuba in 1961 the CMA also received use of surplus aircraft which were used to transport equipment and to stage terrorist raids against Nicaragua Nicaragua by May of 1984 Posey had sent three training teams into Honduras when two CMA recruits were shot down during a raid on a military school in northern Nicaragua it became clear to the media that the training teams were actually in mercenary commando units Posey also provided security services for John Singlobs World Anti-communist League and US Council for World Freedom through Singlobs he came to know all over North and at North request he sent his troops to the Contras Contras Southern Front headquartered at John Hall's Costa Rica Ranch C card number 12 because it is illegal to send mercenaries into other nations Posey is currently under indictment indictment indictment for violation of the security act I wonder what happened to this guy look at this lovely dude