العف positions السلام عليكم رحمة الله باركاتو كيف حالكموا على حقام SOS The show that discusses duties and practices by His Eminence the Grand Idolid said Sadik Shirazi In this season Insha'Allah We will be discussing different types of Marajah and their opinions also in regards to Islamic duties Joining me is Sheikh Ali Maraj السلام عليكم شخara السلام عليكم رحمة الله Nice to have you again on the news set, Masha'Allah Thank you شيخنا ما فرس كورآن is in regards to the youth what is the opinion of the scholars on the Maraja about the youth and how they should be behaving and the attitude towards Fiqh and the holy traditions and rations we find that there are emphasis on the role of the youth in the society and the role of the youth in propagating and spreading the message of الله سمع تعالى and the message in which was delivered by prophets and many of them if not the majority or all of them were began their journey in the very early ages of their youth we come for example to yusuf عليه السلام when he was taken to Egypt and was sold as a slave he was in his youth a very young age and sent to Egypt and eventually he began his message towards الله سمع تعالى and guiding people and taking them out from the shirk to the belief in oneness of الله سمع تعالى and also in the holy Quran the word youth or the youth are mentioned in one or two verses in the holy Quran that I found the first verse was regard to ashabul khaf the people of khaf of the cave in which they were also youth who went to the cave to worship الله سمع تعالى and to stay away from that pagan society that the society in which worshiped other objects in other words the Quran says بسم الله الرحمن الرحيم إنهم فتية آمن بربهم was it now them they were a group of youths in which they believed in their lord and we added to them more guidance we guided them more and more so they were youths فتية youths in which they cared the message of الله سمع تعالى to the humanity also we have إبراهيم عليه السلام in other verse in which states that we've heard that a youth a young man with the name of إبراهيم with regard to the the statues in which إبراهيم عليه السلام he destroyed them so the holy verse mentions فتن youth so the journey of the prophets and the guides began in their early youth age in which in this age the one is able to move is able to provide guidance provide services to the humanity in overall because after that age or even before that age in childhood you can't do anything because you're a child and also if you're in your elderly age you're 70 80 it's difficult for you to be proactive and enjoy that strength and power in order to deliver the message of الله سمع تعالى لكما when we come and we see the علماء for example the great reformers the great even scientists for example they began in their early ages of youth they didn't start in their 70s or 60s so that's why we see the success comes initially one of the parts of the success comes from the one who starts education starts reading writing seeking knowledge in such early age so by the 40s and 50s he has reached a level of knowledge in which he can nurture students and teach others and guide others what about the question about the opinion for the علماء and scholars with youth affairs so let me begin with one of the علماء his Eminence Ayatollah Sistani where he advises the academics those youths who are studying in the colleges and universities advising them with a few of these important facts in which the one should take into consideration he says for example he's an obligation that the one should truly believe in الله سبحانه وتعالى and to believe in the hereafter so the first thing for this youth he must establish a profound belief in الله سمع تعالى and in the hereafter because without this belief the one can go to any direction and deviate from the right path and might end up with giving the services to the wrong sides to the sides of the enemies for example and he also gives the advice to possess a خلاق to possess a good morals again so after the belief in الله سمع تعالى is to have this خلاق great خلاق the morals in which the one should possess them at all levels and all the time and also he encourages for the youth to to learn a new profession or skills to have a career for the future and order for them so they won't waste their time they reach the age of 25 for example they must have a profession they must have some kind of ability to provide a service to the society they have a skill so they would get a job because otherwise they'd be unemployed and also he also encourages the youth again to have early family formation to get married as early as possible and also have children so important advice by the Sayyid that the one should look forward to get married as soon as possible the second مرجع which mentions also some advices to the youth is he says as well to pay close attention to the original religious and social culture in other words we go back to our original belief and عقيدة and culture so the one can immune himself from other cultures and beliefs and creeds in which might deviate and corrupt our youth of course that would benefit themselves their society their country that's the results of the one who sticks with his own beliefs and culture and doesn't import cultures from other sides the other مرجع is I told Allah the late Muhammad Ashirazi who also mentions this fact which is similar to other مرجع that one of the most important matter for the youth is the belief again عقيدة and because that protects the individual in all aspects of economics politics religious business social and so forth so the true عقيدة correct عقيدة and belief would protect the one from all deviations in any field you enter you want to work in politics and economics in trade in social services if you have good عقيدة and profound عقيدة you won't do wrong things and wrong doings basically you would provide the service that will please الله سمه تعالى and your Imam عليه السلام the next مرجع ايط الله شيخ واحد الخراساني he calls to revive the realities of the شيعة اسلام those profound realities in this great religion in the minds and the hearts of the youth so important because now many of the youth sadly some of them they have lost this realities they have lost this understanding the true meanings of being a muslim and being a believer in أهلبيت عليهم السلام they try to some of them try to find from you know to look for celebrities for example okay other personas so no we have to go back to our realities and our own beliefs and try to have the true role models who are محمد المحمد السلام عليهم أحسن شيخنا شيخنا what about the opinion of uh سمحت السيد صادق شراسي حفظ الله what does he have to say in regards to the the obligations of the youth towards islam and islamic سمحت السيد صادق شراسي حفظ الله he would mention that before we actually establish let's say an islamic government or islamic movement or organization or anything else the first thing we have to think about are the youths in other words before i establish an islamic um center or i have to think where do i uh accommodate the youth in this organization so important because um as the said says that they have in this age of youth they have the stamina they have the power they have the strength um they have the eagerness to serve their religion and community so we should take care of their um their needs in the society in the community and try to offer the best for them and employ them in these uh places and roles so they can provide the best for the community because at the end of the day um those who are elderly they can't do whatever um they they did in the past when they were young young and youth so now it's the role of the young generation to take over and help the elderly as well in running uh these centers and these movements and so forth احسان it's nice how you know all the maraja you know give time and dedication and recognizing importance of the youth and the involvement in islam and also how you know at that tender age you know there's so many questions there's so many issues and that to make sure that they can stay within the bounds and foes of islam and to focus on you know اقايد and فرق and then later on إن شاء الله to develop themselves into good muslim beings شرحان my next question is in regards to um the youth and the issues how can we address the issues of the youth well to address the issues of the youth is not just اثريتاق or just a verbal means of trying to deliver something to them or to their parents or to those who are related yes you can give advice you can talk which is great but we need more pragmatic steps more practical elements in this field so for example to get them انولت for example to educate them for example we need let's say provide them with libraries specific libraries for the youths and in their language if they are living the west for example whatever place they live they have to have their own books and at all levels in terms of the age levels and that's important otherwise how could you deliver the message of islam to the youth if they can't read the father's language for example they can't read their parents language and well they can speak it roughly but they can't really write and read the original i think there's a big issue in our community where we learn how to conversate in our mother tongue but we don't know how to academically use the language exactly so that's one of it is to basically provide for them reading material and make sure that information not least available in a language that they can understand because the original language for the islam is arabic yes and the main and the most sources are in arabic so in order to deliver the message of islam to this generation who now they live in the west they have to be educated according to the islamic teachings and education so they need to have access to these sources in their own language and understanding with regard to other fact in which some of the state mentions to the youth that sometimes the youth are in need of financial help so they can build their life so if they want to set up a business for example a project so we try to help them if we have the ability to take out loan or for example somebody who is a merchant or a trade man who can help them support them so you're actually offering also financial support you're offering not only just how can i say religious support also material support so معنا we both support for the youth so they won't run away from you that you only provide us with religious facts that's it no we try also help the others as the holy prophet صلى الله عليه واله and they helped people not only by guiding them telling them to come and pray and fast and go to Hajj but also they supported financially he gave that amount of money and wealth to certain people who were in need أهلبيت علميسان also used to support the poor for example support those who wanted to for example establish a trade or business the Imam would support them so we have to also support the youth in this field as well so religious and also financial aspect also say it mentions that we have to set up اوغانيزيشنز and associations in which provides for those who are still in education support so if they need the support as students we can support them also he mentions that we provide places of worship for them as well because the youth أهلبيت علميسان are more likely to have their own community as well so the kids have their own community their own gatherings and also the youth they would like to have their own gatherings and majlis especially if it's in different language as we have now in English for example so we have to open a specific locations or a space in the سنز or أسيانية or mosques in order for them so they can have own activities and they can provide the programs in their own notions and in which are in line with the Islamic teachings so we need to facilitate and accommodate for the youth these aspects and he also mentions that to set up also some bodies in which they can help in solving the problems within the society within the youth for example in all aspects as well I think in today's day and age a lot of the youth they have issues with you know where to study what to study should I go to university or not where to take my career path also there's also challenges in being a Muslim free mixing you know sometimes there's issues with you know drugs and alcohol so I guess it's very very important that each centre establishes some form of relationship as well as some sort of aid to help the youth exactly now we have thousands of organizations in the west in which they support the youth there are youth forums youth something you know support there are sets of all charitable organizations to support and help those youth who are abandoned or isolated from the society or those who are they fall into committing crimes and so forth so we have already these things in the west but Islamically or religiously we need to also have this as well to give them not only the financial support or other means of support but also to guide them you know they might need more support in terms of uh religiosity for example so we try to support them and also finish there as well and all other aspects أحسنث uh thank you very much say شكرا شكرا what about you know spreading awareness and to promote certain topics with the youth I mean how do we go about that how do we promote and spread awareness amongst the youth as I've just mentioned a few minutes ago that um the youth need advice and admonishment in all stages and levels especially when they reach that age of the teens and the age of after the puberty and the age of bulug which is very sensitive and crucial so they need support they need to be given advice by the elderly by the professionals if somebody's academic who can advise them which route to take for example some of them let's say are not interested in studying they just want to stop studying they want to work so you can guide them and tell them what are the best options so you bring somebody from the market for example a merchant a trade man for example if somebody wants to continue studying then you bring somebody from the university advice center for example or for for example somebody who wants to um basically gain skills in specific fields then also you bring a career advisor but also that could be done within the community the the religious community for example the muslim community we have all these advisors in all aspects and levels so they have to be uh I think they have to have a mentor somebody who can overlook their activities so we shouldn't leave them to make their own decisions because they might end up now and God forbid uh as a result of bad friends the bad society ending up in drugs and so forth and crimes and so forth thank you very much شكرا and thank you to all our viewers for joining us إن شاء الله join us on another episode of akam s o s we'll be discussing duties and practices for muslims by say صادق شرازي and also by other مراجع as well see you next time سلام عليكم رحمة الله وبركاته


RCA Victor, world leader in radio, first in recorded music, first in television, proudly presents... Douglas, production, champion, director, Mark Robson. Woodscreen directors present a symphony in fists. The motion picture drama Champion, starring Kirk Douglas in his original role of Midge Kelly with Frank Lovejoy as Tommy Haley. Never mind the winner. No one remembers who won that four-round pro-limin Kansas City that night years ago. No one knows who lost it, Midge Kelly, by a decision. He lost because he'd never been on a prize ring before. He was just fighting to eat. But he had heart. He had guts. And if he was willing to learn, I was willing to teach him how to fight. I'd talk to him about it later in the dressing room. He was a battered mess, but he grinned at me. Oh, no thanks. Not for me. What good is the big money if you don't live to spend it? All right. Forget it. But if you're ever in LA, you can find me in Brady's Gym. Yeah, sure, sure, LA. Brady's Gym. Yeah. Goodbye. He brushed me off like dandruff, and I thought I'd seen the last of him until one day in Brady's Gym in Los Angeles. Hello, Mr. Haley. Hmm? Oh, sure. Kansas City. Midge Kelly. Yeah, that's right. How are you, Kelly?  Oh, yeah. Yeah. But I'm retired now. Retired? You want some advice? You do the same.  You said you want to manage me. Well, that was then. This is now. I'm out of the fight business. It stinks. I'm kidding. Take a deep breath. Stinks in here, doesn't it?  I'm kidding. What do you mean, go home? I don't need you. You're not the only manager in the world. I'll find somebody else. I'll show you. What's the matter with you? What's the matter with me, says? Look, you ever been poor?  Look, Midge here. What's that? Five bucks. Pay me back when you get a job. Keep it. Sure. Get a job. I've had jobs.  Fry cook. Busboy. Ditch digger. Nice, clean, healthy work. Big money. Well, I'm tired of being nobody. I'm going to get someplace. Look at it this way. Wait a minute. You see that fellow sitting over there on that bench with a cane? That's my brother, Connie. He's crippled. I got him to take care of. I got my mother back in Chicago. You told me there was big money in the fight game. That's right. You take me on, and I'll make plenty for both of us. Oh, you will, huh? You bet I will. All right. I'll take you. Now you're talking. You're going to have to work. Well, let's go. You're going to work until your bones hurt, and you're going to learn to break other guys' bones. It'll be a pleasure. You're going to learn every dirty trick in the business, and there's plenty of them. Don't worry. I'll learn. I'm going to get someplace. He learned fast, and he learned right. And in his first fight, Midge was a killer tasting blood for the first time. And his dressing room after the fight, he was drunk with his first victory.  I heard them. Hey, what's the matter, Connie? I don't know, Midge. I didn't know you're in that ring. Ah, you're talking kid stuff.  Is that bad? Midge. Listen, I want to fight. My first fight, that's all. You hear that crowd for the first time in my life, people cheering for me. Well, you're deaf. Didn't you hear them? Yeah, but is it worth it? Aw, wake up, Connie. Smell the coffee. Smell the steaks. We're not hitchhiking anymore. We're riding. I'm on my way, and I'm going to get someplace. Boy, Kelly, promising young middleweight, keeping his promise for three great years, tossing hard leather from coast to coast. Salt Lake, Denver, Omaha, Tulsa, Dallas, St. Louis, Kansas City, Chicago, Cleveland, and New York. Then a chance of Johnny Dunn leading contender for the middleweight title. Oh, yeah. What do you mean? Oh, yeah. You were downtown today. When do I meet Dunn, huh? Midge, the boys gave me a cigar, patted me on the back, and told me to drop dead. What? They say you can't beat Dunn. Who says I can't beat Dunn? Dunn is a big draw, Midge, so you lose to him. He goes on to fight the champion and grab the title. Hey, you mean I toss the fight? That's the way they want it. Who cares what they want? They're the control. They own the business. Well, they don't own me. Listen, Midge, I'm not telling you to do it. But if you don't, you'll be fighting in the sticks until your beard is long enough to reach the rosin. Hon, nobody's rubbing dirt in my face now. What kind of a manager are you? What's in it for you? Hold it, Midge. Yeah. Three years. Worked like a slave. Build the muscles. Build the wind. Live like a monk. Beat your brains out.   And I can beat Johnny. None you know I can beat him. I know it, Midge. But this one, you'll lose. I don't know how to lose. Well, look, if you want to stay in business, you want to stay close to the real money, this one, you'll lose. Now, what's it going to be, Midge? All right. I lose. The main event, Midge Kelly, my boy, versus Johnny Dunn for clean sport and a cash consideration and a chance at the middleweight championship of the world. All right, Johnny, Midge, you both know the rules. I want you to watch yourselves on low blows, just have a nice clean break, shake hands, come out fighting. Take your corner. Relax, Midge. You're tense. Take it easy. Yeah, nice clean break. But toss the fight. Who's a flashy blonde at ringside? It's Johnny Dunn's girl. Why? What's she grinning at? Never mind her, Midge. Doesn't she think I can take her boy? I get it. Well, she can get the smile off her face, can't she? It's 10 seconds, kid. You know what to do now. Yeah. I know what to do. What?  Come on, Midge. We've got to get out of here. I told you I could beat him. Up the aisle. Don't get lost. Follow me. Come on. Come on, Midge. I want to talk to Johnny Dunn's girl a minute. Midge. Well, where's that smile now, baby? Who do you think you are? Call Skyler, 78941 and find out. Midge, come on. Don't forget, Blondie. Come on, Tommy. I got it, Tommy. Okay. Yeah. Nice address. I'm making you. What was that? Johnny Dunn's girl. Grace Diamond? Yeah. When it takes all, huh? You are listening to the screen director's playhouse production of Champion, starring Kirk Douglas and presented by RCA Victor. They say the census takers this year expect to find more American families together at home than at any time since George Washington's day. Yes, you guessed why. They'll be looking at television. Most of them at RCA Victor Television, America's favorite. A set which enchants families en masse is the RCA Victor T164, a 16-inch table model. Women love it for its gracefully proportioned, richly finished cabinet. Children love it because it's so easy to tune. Men love it for its matchless RCA Victor engineering. And everybody loves it for its really vast picture and incomparable performance. The suggested list price of the T164, slightly higher in some locations, is only $299.95 plus federal tax. Here's hoping such a marvelous television value will soon enable you to join the United Families of the United States. RCA Victor Branch. Now back to the screen director's playhouse production of Champion, starring Kirk Douglas in his original role of Midge Kelly with Frank Lovejoy as Tommy Haley. So, uh, my boy, Midge Kelly, had himself a parlor date with Johnny Dunn's girl. One sudden place. Nice address that one, sudden place. Four onion in your mouth. Olive. Olive. Thanks. How do you feel after the fight? Oh, fine. Johnny's in the hospital, you know. Yeah, I heard. They say you'll never fight again. Gee, that's tough. But he's planning a comeback. He wants a return match. Any time. Meanwhile, you're king of the world. What do you think? When it takes all? Come here, baby. I think this. Are you... I had a lot of time invested in Johnny Dunn. Did you think you could knock him senseless and then prance over here and try me on like a second-hand suit? Go on, crawl out of here. Go on. All right.  Wait, you. Well? Come back here.  I just wanted to see... if you thought I was too easy.  Does it hurt where I slapped you, doll? Oh, I've been slapped before. We got to talk about your future, doll. Yeah. You're dead in the fight racket now. You know that. Unless... Unless what? Unless you get yourself a manager. I got a manager. You got an appendix, too, but it'll never make you rich. See Jerry Harris. Johnny Dunn's manager? He can get you everything that Dunn was due for, and he'll square things with the gamblers for you. I can't drop Tommy Haley just like that.  Look, I didn't come this far to be through. And see Jerry Harris. No. For a shot at the title? For me, doll? You, uh, you know Harris pretty well, huh? We were the very best of friends, until he took on to himself a beautiful society wife. Okay. Get an appointment with him. Now, come here, doll. And, uh, so my boy, Mitch Kelly, shook me and signed up with Jerry Harris. And pretty soon, Mitch was signed for a bout with a champion. Oh, Mitch was getting someplace all right, whether his brother Connie approved of the method or not. You threw him out? You threw Tommy Haley out? Connie, I had to do it. It was our only chance. But this man was like a father to you. Well, he fed you. He put shoes on your feet. He made you. Who's been taking the punches? Haley or me? Oh, this rotten business. Oh, lay off the business. It's like any other business. Only hear the blood shows. Listen, Connie, it's time for you to grow up. Look, you and me and Ma, that's what's important nobody else. Mitch, what's happened to you? Nothing stands in your way anymore. You've got your own way of destroying people, and I don't think I want any part of it. Okay. Who's twisting your arm? Go on.  Feed yourself for a change. Ah, go on. Take your bleeding heart out of here. All right, Mitch. I'll tell Ma how you're doing. Yeah. Run home to Mama. Okay. He was a great champion, Mitch Kelly. Yep. And, uh, he was quite a boy. He dropped Johnny Dunn with those hard fists of his, and then he dropped me for Jerry Harris. And he began dropping Grace Diamond for Harris' society wife. Mitch found Grace waiting for him in his apartment one evening when he came home to dress for a big date. How'd you get in here, Gracie? Thanks for remembering my name. Ah, that's all right. Uh, I'm in a hurry. Will you excuse me, Gracie? Why are you going again tonight? Oh, I've got a date with a lady. You know what a lady is? Nah, how could you? You know anything about art? You know anything about opera?  Well, so long, Gracie, I gotta get dressed. Wherever you're going, I'm going with you. You're not gonna shake me now. Yes, I am. For good. You better promote yourself another meal ticket. No, Mitch. All I want is you. Don't do this to me. I'll do anything you want. You will? Yes. Then why don't you call up Johnny Dunn? Mitch, if you do this to me, I'll plaster your name all over town. I'll raise such a... Oh, no. You're gonna be a good girl. Because if you aren't, I'll put you in the hospital for a long, long time. I gotta change now. Don't be here when I come out. Mitch Kelly, champion, was hitting the high spots all right? But Johnny Dunn was coming back hard and strong, demanding a match with Kelly until Mitch had to give it to him. That's when Mitch dumped Jerry Harris. Well, Tommy, it's gonna be a tough fightin'. Well, you're the best trainer in the business. Look, I'll give you one-third of my purse. You're quite a boy, Mitch Kelly. I took him on a training camp. Men in motion, flick of jump ropes, rumble of punching bags. Tell it to me. Bill, can you come right away, Connie? Gee, Tommy, I can't go now, can I? It's up to you, Mitch. Oh, Ma's had those attacks before. You're no best. I know Ma wouldn't ask me to break training because she's sick. Look, it's Connie. I wish she'd grow up. What's it gonna be, Mitch? B, a fight. I got a fight on my hands, haven't I? Yeah. Well, so okay, train. Mitch. Hi, Connie. Hey, when'd you get in town? How's Ma? How's Ma? She's dead, that's how she is. Dead? And where were you when she was crying for you, calling for you? Training. Getting somewhere, defending the champion. Gee, Connie, I didn't think she was gonna die. I sent your telegram.  Ma's gone. She died calling for you and crying for you. All right. All right. Now get out, Connie. I got a fight. I got to relax. You stink. You stink from corruption. I have a beat. Don't do it, Connie. You! Why, you hit me with your cane, will you? Here we go, champ. There. There's your cane, Gimp. Coming, Tommy. The champion is not taken by a decisive margin. The champ looks worried, and there's a conference going on in his corner. I hit him with everything but a club. He's in good shape, champ. Yeah, I should have had him. I should have had him. Round eight. I don't know what's wrong, folks, but the champion's timing is off. He's missing offener and getting hit offener. He doesn't seem to be in the same fine fettelism. Round nine was even. Round ten. Ladies and gentlemen, Johnny Dunn is done. Kelly is hurt. He's definitely hurt. Only the pieces in there. He's cutting him to ribbons. The champ's covering up. The challenger reducing the champion, my boy, the human rubble. Mitch Kelly is face a mash. Still answering the bell, refusing to quit. Being led back to his corner. I'll get him. I'll get him. Mitch, you're through. I'm gonna throw in the towel. No.    Okay, then. Fight. Round 12. 13. Stop it. Stop it. Stop it. He's down. He's down. The champion's hurt. She's for him now. Johnny. Good boy, Johnny. Oh, sure. I love you, John.  I can beat him. I'm the champ.  You sure did much. Gee, do you hear them out there, Connie? I'm Tommy. Look, I'll get a doctor. You're talking kid stuff. I want to fight that, Saul. My first fight. Gee, for the first time in my life, people cheering for me. Mitch, Mitch, sit down. Take it easy. Go. Are you deaf? Didn't you hear them? Wake up. Connie, smell the coffee. Smell the sticks. We're not hitchhiking anymore. We're riding. I'm on my way now, and I'm gonna get someplace. Sit down, kid.   Get me a fight with Don. Mitch, the champ is dead. A statement for the press about my brother. Sure, I'll give you boys a statement. Mitch Kelly was a... Watch it, Connie. He was a champion. He went out like a champion. He was a credit to the fight game. He went to the very end. You have just heard the last act of champion, and our star, Kirk Douglas, with our guest screen director, Mark Robeson, will be with us in just a moment. Next Friday, another great star brings a fascinating performance to the screen director's playhouse. Our story for the first time on the air is Chicago Deadline, and recreating his original role will be Alan Ladd with screen director, Lewis Allen. Now here again is tonight's star, Kirk Douglas. Didn't I hear somewhere that you made a kind of sentimental pilgrimage to New York right after you finished champion? Yes, I did, Jimmy. I made the rounds of all the places I knew ten years ago when I was studying at the American Academy of Dramatic Arts. Places like the Star Club, you mean? No, no, places like Shraff's. Oh, I see. As a student, you ate at Shraff's. Oh, no, I only worked there. I couldn't afford to eat there. I suppose you visited where you used to live? Yeah, Central Park was looking fine. And you know, Jimmy, the RCA building was as nice and warm and hospitable as ever. See, often I know something about RCA Victor that you don't, Jimmy. What's that? You know, I spent a lot of cold afternoon in RCA's exhibition hall. Look, guess what they're exhibiting now? What, Kirk? They're new 45 automatic record changer and records. Well, dog my cat.  Did you know that in the 45 RPM system, RCA Victor has achieved the first record ever to be free of distortion over 100% of the playing surface? Right. And what they've done for convenience by the 45 changer is so small and light, my five-year-old boy carries ours all around. Yeah, and that guy in the RCA building told me you can attach it to any radio. And it's so easy to run. He says his three-year-old boy uses it for hours on end. Oh, did he tell you that you just have to push one button once and it plays 10 records automatically? Almost an hour of music? Yeah, that's right. Say, what's more, the 45 records are so tiny, you can carry them in your pocket. Yeah, they're non-breakable, too. And say, Jimmy, do you know how little the 45 changed your cost? As low as $12.95. Right. And prices on the 45 record start as low as $0.46 plus tax. The 45 is a beautiful proposition all around. No wonder it's the fastest-selling record system in America. Yes, the 45 is sweeping the country, like, well, like Kirk Douglas. Here are the 45 soon at your RCA Victor dealers. And friends, join the swing to 45 when you buy your next record.  At 170 pounds, he throws a very special kind of punch. It doesn't close your eyes. It opens them to all the powerful drama that a fine director can achieve on the screen. You'll know what I mean if you've seen such pictures as Home of the Brave, My Foolish Heart, and Bedlam. All of them created by the man who directed me in champion, Mark Robeson. Thank you. Now, let's see your face. Oh, here. Uh-huh. The bruiser seemed to have healed. You're ready for another fight picture. Oh, no, Mark, not again. Oh, Kirk, what if you do get beaten up just a little? Look, it's not the first time I get beaten up that worries me. Say, you know what really hurts? What? When I fall out of the ring and you step out from behind the camera and say, uh, Kirk, you got too much blood on your opponent's glove. Let's shoot it again. Yeah. Kirk, I apologize. I was a beast. Well, my wounds were soothed by the fact that I had Mark Robeson for my director. And believe me, that's worth a lot of punishment. Thanks, Kirk. And I promise next time I do a picture, I won't ask you to do any scenes over again. Oh, I'm glad you understand, Mark. Too bad I was thinking of doing a picture with a lot of love scenes. Love scenes. Oh, well, good night, Kirk. Now, wait a minute, Mark. Oh, good night, everybody. Now, wait a minute. Good night to you, Kirk Douglas and Mark Robeson. Remember next Friday, Alan Ladd in Chicago Deadline with screen director Lewis Allen brought to you by RCA Victor, world leader in radio, first in recorded music, first in television. Champion was presented through the courtesy of Screenplays Incorporated and producer Stanley Kramer, soon releasing The Men. Kirk Douglas can currently be seen in the Warner Brothers production, Young Man with a Horn. Mark Robeson's latest picture is the Samuel Goldwyn production, Edge of Doom. Frank Lovejoy may be heard in his own radio show, Night Beat, every Monday night over many of these same NBC stations. Included in tonight's cast were Reha Lin as Grace, Jack Edwards, Dan Riss and Frank Barton. Champion, from a short story by Ring Lardner, was adapted for radio by Milton Geiger, and original music was composed and conducted by William Lava. Portions of tonight's program were transcribed. Screen directors Playhouse is produced by Howard Wiley with dramatic direction by Bill Karn. We're excited to listen again next Friday when RCA Victor presents... Screen directors Playhouse, star Alan Ladd, production Chicago Deadline, director Louis Allen. Great Rupert Durante on NBC.


Welcome everyone to the Improve Resilience with Automated Chaos Engineering session with Gunnar Grosch over to you Gunnar. Hi everyone and thanks for joining this session. So chaos engineering has proved to be a great to have option in the SRE and SDE toolbox, but the transition into more complex systems is really accelerating. So my name is Gunnar Grosch and I am a developer advocate at Amazon Web Services. And in this session we'll look at how automated chaos experiments can help us cover a more extensive set of experiments and what we can cover manually and how it allows us to verify our assumptions over time as unknown parts of the system change. So chaos engineering, it is the process of stressing an application in testing or production environments by creating disruptive events such as server outages or API throttling. Then we observe how the system responds and implement our improvements. And we do that to prove or disprove our assumptions. Our assumptions about the system's capability to handle these disruptive events, but instead of letting those happen in the middle of the night or during the weekend, we can then create them in a controlled environment and during working hours. So I think it's important to note that chaos engineering is not just about improving the resilience of your application, but also its performance. We do it to uncover hidden issues within our system. And we often use it to expose monitoring, observability and alarm blind spots. And a lot more. We can use it to improve recovery time, to improve the operational skills of our teams, the culture of the entire organization and so on. So when we do chaos engineering, we follow this well-defined scientific method that takes us from understanding the steady state of the system we're dealing with, to articulating an hypothesis, then running an experiment, often using fault injection. After that, we're verifying the results of our experiment. And finally, we learn from the experiments in order to improve the system. And then we're back to improvements such as resilience to failure, the performance, the monitoring, the alarms, the operations, the overall system. And today, we're seeing customers use chaos engineering quite a lot. And the usage is definitely growing. And we've also seen that two very clear use cases have emerged. The perhaps most common way of doing chaos engineering today is creating what's called one-off experiments. And this is when you create a chaos engineering experiment by, for instance, looking at previous outages in your system and different events that might have happened in your system. Or perhaps you identify the services within your system that have the biggest impact on your end users or customers if they go down or if they don't function correctly. And then you create experiments for those services. Or perhaps you've built a new feature. You added a new service or you just made changes to the code or the architecture. And you then create an experiment to verify that the system works as intended. And companies are doing this in different ways. Some have dedicated chaos engineers that are creating and running the experiments. For others, it's parts of the SREs responsibilities. Or as we partly do at AWS, chaos engineering is done by the engineering teams themselves on their own services. The other very common use case is to use chaos engineering as part of your game days. And a game day, if you haven't heard about that, it is the process of rehearsing ahead of an event by creating the anticipated conditions and then observing how effectively the team and the system respond. And an event in this case could be an unusually high traffic day, a new launch, a failure that you've seen in the past or something else. So you can then use chaos engineering experiments to run this game day by creating the event conditions and monitoring the performance of your system and of your team. So doing these one-off experiments and perhaps the occasional game day, it helps us get very far on the road to improving resilience. So isn't this enough then? Well, it definitely can be. I want you to look at an example. So in this case, just a basic use case example. Let's say that you and I were running an e-commerce web application together. And this is a very successful application. We're selling stuff and we have thousands, if not millions of users using the web application and our mobile apps as well. It's a very straightforward application. In this case, we have an auto scaling group running EC2 instances spread out across two availability zones. We are using Amazon Aurora for our data store for our databases. And we have some level of resilience by doing it this way. And we have then started using chaos engineering to then verify the resilience of our service. So we're using, in this case, AWS fault injection service, our fully managed chaos engineering service. So we're doing our experiments. We learn and we gain confidence from doing those. So let's just make a quick demo of how we can do our chaos engineering experiments. So I'm simply going to do an experiment where we want to try what happens if an instance in our application stops. So this is the AWS fault injection simulator console. If you're familiar with AWS, you can see that it looks similar to many of the other services. So let's start this. All right, I'm creating a new experiment template as it's called, which basically is the template that defines our experiment. Start and stop instances, giving it a name and description. Then I'm selecting the role, the role that's allowed to do these experiments on my system. Next, I want to add the experiment action. And an action is what we're actually going to do, the fault injection injecting. In this case, we're going to stop the instances. So I'm selecting the EC2 stop instances action. I can then select that the instance should be started again after one minute. I can save this. So we have an action. Next, I want to define a target. So editing the target for our action. And in this case, I'm going to select one specific instance. But we can also do this by selecting a certain percentage. We can use different filters and so on to select more at a random way. Saving that target as well. Next, I have the ability to add what's called a stop condition. Stop conditions means that if an alarm goes off, it will automatically stop my experiment. Creating the experiment. And next, we can then start this experiment. This is the EC2 console. We can see my specifically assigned EC2 instance as part of that auto-stailing group. So let's start the experiment. I need to verify that I want to start it as it might have an impact on my system. The experiment is now initiating. It is now running. Meaning that AWS FIS fault injection simulator will now stop that specific instance. If we're checking the EC2 console again, we can see that it's stopping. And as soon as the experiment is done, when that minute has passed, it is then going to start the instance again. So it is completed. Let's check the EC2 console again. So now my instance is starting up again and it is now moved back into the running state. So that's a very quick and simple example of how we can use chaos engineering experiments. In this case, to verify that our system is able to handle that single instances are stopped within our auto-scaling group. And of course, we need to then verify that it didn't have an impact on our users by using monitoring, observability, use that steady state that I talked about early on. So back to the e-commerce web application, we had AWS fault injection. We're running experiments to it. But besides that, my team building this product service, we are of course also using good practices for deploying to our service. So we're using CI CD and continuous integration and continuous delivery. As you probably know, it has made it possible for us and it even encourages frequent deployments. And as we know doing frequent deployments, they are less likely to break as it's more likely that we'll catch any bugs or gaps. But frequent deployments are hard to cover manually with chaos engineering experiments. Think about the experiment I just did. Having to do that manually every time we're doing a new code deploy every time we're making any type of changes, well, it takes time. So next then, we, sorry, switching there. Well, so we had our product service and we're using chaos engineering on a manual basis there. We're using CI CD, but in a typical application, it's just not built with one single service. Instead, we have different services within our application. So for instance, another team, they are building the order service for our e-commerce web application. And we have another team building the user service. Perhaps there's a team building the cart service. We have a recommendation service, of course, for our users and we, of course, need to have a search service. So this might be built by different teams inside our company or organization. And these services, of course, they also have dependencies to each other. So the cart service depends on the user service and the product service depends on the cart service. And the order service, of course, needs to have both the cart service and the product service to work. The search service needs to work with the product service and the recommendation engine, of course, needs to work with our product service and the users to give proper recommendations. And well, when we're doing these kind of experiments on our service, we probably know exactly how the service works. But what happens when there are changes that are unknown to us in different parts of the system? Another team makes a change to dependency of ours. For instance, the order service. Well, we can't really know. These are unknowns to us. So we might need to run experiments quite often to be able to know that the dependencies, they are actually working as we expect them to. So if we look at this very simple example, I would say that frequent deployments makes it hard to cover with manual chaos engineering experiments. If we wanna make sure that every deployment we do work as intended. And to cover an extensive set of experiments is time consuming. We just did one single experiment now, but then perhaps we wanna test different parts. We wanna make sure that we do experiments that cover our data store as well. What happens if there's latency? So we need to create these different type of experiments. And as I talked about in regards to dependencies, even though we might have full control over the service or microservice that we're working on, unknown parts of the system might change. Other teams make changes. Other teams update their services. And so when systems become more complex, it's hard for anyone to create a mental model of how the system works, let alone to keep documentation up to date. And that brings us to automated experiments. So automation, it helps us cover a larger set of experiments than what we can cover manually. And it helps us verify our assumptions over time as unknown parts of the system are changed. So doing automated experiments, it really goes back to the scientific part of chaos engineering. So repeating experiments is really standard scientific practice for most fields. And repeating an experiment more than once, it also helps us determine if the data was a fluke or if it represents the normal case. It helps us guard against jumping to conclusions without enough evidence. So let's take a look at three different ways that we can automate our chaos engineering experiments. First, let's think about how our system evolves. So as I mentioned, we might have full control over the service or microservice that we're working on, but other teams or third parties are making changes, delivering new code, releasing new versions of their services. And those might be services that we depend on. So the verification we got from doing a one of chaos experiment a month ago or a week ago, it might quickly become obsolete. So by scheduling experiments to run on a recurring schedule, we can get that verification over and over again as unknown parts of the system changes. So let's have a look at an example of scheduling an experiment. And in this case, I'm building a simple scheduler for my experiments using a very simple serverless application. So jumping into VS Code, and I've created an infrastructure as code template for my scheduler. So we're creating a serverless function that will start based on the schedule. So I can schedule my experiment. And I will just simply set up so that this is able to start my experiments. This is the code for the scheduler. It will take an experiment template ID, like the template I created before and simply send a command using the SDK to AWS FIS to start my experiment. It's a very basic scheduler based on an AWS Lambda function. So I have an application running, as we know, a bunch of instances running in two different availability zones. And these are part of our service. I can then create an experiment template to begin with based on a JSON file in this case, instead of doing it through the console. And let me just copy the ID of my new experiment template. And now I will deploy this simple serverless experiment scheduler. And deploying that, running it in Dublin, pasting the experiment template ID and now setting the scheduler. And this is a basic Chrome syntax. So this experiment will run once a day deploying that. All right, so this will now deploy in the background. Let's switch over. It's fairly quick, so checking. All right, so it's done and now deploy this. So if we look in event bridge, which is our event bus, we can see that we have a rule and it's set to run at midnight every day. But I can now simply test this by creating a test event and run my schedule right now to just make sure that it works, pasting in my test event and testing it. So this will now send an event saying that it's time to run my Lambda function. It succeeded. And the Lambda function then starts my experiment. It is running as we can see, checking on the EC2 instance. We can see that this experiment is now running. This specific experiment is using up CPU. We're stressing the CPU on our instances. And we're also stressing the memory. So this experiment will now run and then use up CPU and memory on our instances. You will then move on to do other things as well, multiple actions. And this experiment will then run on my schedule every day, meaning that we're able to verify that assumption, that hypothesis every day to make sure that the system still continues to work as expected under these adverse conditions. And that helps us verify our assumptions over time in a very quick way. What's important when doing these experiments, of course, is to have stop conditions in place. So if an alarm is triggered, you will then abort the experiment. So next up then, we have what's called event triggered experiments. And it means that we're able to run experiments based on events. And an event, well, that can basically be anything that happens within your system. It could be an event related to the tech stack, for instance, that latency is added when there is an auto-scaling event or maybe a business related event, like an API being throttled whenever items are added to the cart. So building automation around these types of event, it helps us answer those hard to test questions. What if this, when that is happening, even when that is an event in another part of your system? So let me show you an example of that as well with an event triggered experiment. So back to VS Code, setting up in the same way, an event triggered serverless application. So once again, using a template, using AWS SAM, and this consists of AWS Lambda Function, which will trigger on what's called the CloudWatch event, which is an event within our system. And the pattern in this case is auto-scaling. So whenever an EC2 instance is launched, successfully, it will then pass this event on and trigger my AWS Lambda Function. So the function works in the same way as before, but looking in the event bus, we can see that there are a bunch of different event patterns that we could use. So for instance, based on the different AWS services, so any type of service we're using that's able to pass an event, will then be an option for us when creating these event patterns. So I chose to go with EC2 auto-scaling for this example. So we are then passing on the auto-scaling group that this should apply for, and setting up a new experiment template. In this case, I have three different stop conditions in place. So for making sure that it doesn't cause an issue whenever we're running these experiments. So let's go through the process again, create a new experiment template based on my JSON file. This will cause CPU stress on my instances. And now I'm deploying this event-triggered serverless application. We have it in our AWS Lambda console. And it consists of my Lambda function. These are the auto-scaling groups that we have. And so now if I manually make a change to this auto-scaling group by adding an additional EC2 instance, that will create that event that we're using. So now it should fairly quickly, yes. So it triggers my Lambda function which starts an experiment based on that experiment template. So it is running. It is, let's check the EC2 instance. Fairly quickly, it should then start using CPU and stress my instances. So we can then test a specific experiment based on an event. In this case, an EC2 auto-scaling event. All right. Next, we have the perhaps most common one. And I would say this is the one I'm definitely getting the most type of questions around. And that is doing experiments as part of your delivery pipelines. And we talked about before that continuous integration and continuous delivery has made it possible for us to do frequent deployments and they are less likely to break. So by adding chaos engineering experiments as part of our delivery pipelines, we're able to continuously verify the output or behavior of our system. So think about, you're doing a code change. You're delivering that in your pipeline. Then you're able to run these experiments to verify that the system still works as intended even after this new code change. Or if it doesn't behave as intended, well, then you can roll back and make changes needed to the code. So let's have a look at that as well by doing a demo of a continuous delivery experiment. So we are now in the EC2 console again and this is AWS code pipeline, our pipeline service. Very simple pipeline setup, fetching source from GitHub. We're deploying to a staging environment and then deploying to a production environment. And the most basic of the pipelines, I would say. This is set up using infrastructure as code. So here's that part. We have our pipeline, source stage, deploy to staging and deploy to production. But now I'm adding an experiment stage. And I wanna do experiments on the staging environment after we've deployed there. And the way, let me just kick off that deployment so it updates the pipeline. And the way this works is that it's gonna kick off an AWS step functions workflow. And AWS step functions, it is our state machine service. And this workflow then, it has a definition that simply starts an experiment and then waits for that experiment to finish. So let's see, all right, our pipeline, we now have an experiment stage set up. So it means that we can now make a code change. I'm just updating straight in GitHub in this case, a small change to the application. Committing that change. All right, so it kicks off the pipeline, fetching the source, deploying that to staging. There's no build steps, so it's fairly quick. Deploy that to our EC2 instances. And now gets to the experiment stage. And this is now in progress, meaning that it's called the AWS step functions workflow and the AWS step functions workflow will start my experiment. Checking, we can see that the experiment is running and that will run for a short while. This, since this is just a simple demo, it's a quick experiment. Usually we run experiments for a longer period of time. It has completed already since it's a quick one. And then it sends the message back to the pipeline that the experiment succeeded. So it can continue to deploy this into production. So instead, what happens if it doesn't succeed? So let's test that assumption as well. Let's release the same change once more and see what happens if the experiment fails. So releasing it, fetching the source once again and then it's gonna go off to deploy that into our staging environment, which is fairly quick once again and switching over to start our experiment in the staging environment. And now if we check the AWS FIS console, the experiment is running, it's doing whatever actions we've added in our experiment. But now let's just say that something goes wrong. So an alarm sets off. We can use the AWS CLI to set the alarm state of my alarm into the alarm state. So now let's run that command. And this is just to simulate that an error happens. And we can see that the experiment now turns into the stopped state because it's stopped by a stop condition that an alarm set off. And looking in the pipeline, we can see that it now shows the experiment as failed. And most important is that the pipeline then fails and will not move on to deploy this into production. So now we've looked at three different ways how to do automated experiments. We have the recurring scheduled experiments. We have the event triggered experiments.  So three different ways to automate our chaos engineering experiments. So the question then is, if you get to this point, should you then stop doing the one-off experiments and the periodic game day? Well, no, it's the simple answer, you shouldn't. Those should still be the core of your chaos engineering practice. And I would say that they are super important source for learning and it helps your organization build confidence. But with the automated way of doing it, you now have yet another tool to help improve the resilience of your system, automated chaos experiments. So I would say one way to think about it is that the experiments you start off by creating as one-offs or as part of your game days can then turn into experiments that you run automated. So after doing the experiment manually to start off with, they can then be set to run every day, every hour, or perhaps on every code deploy. So that brings us to the summary with a recap of some of the takeaways. So automation, it helps us cover a larger set of experiments than what we can cover manually. Running manual experiments, it takes time, it is quite time consuming. So this means that we're able to run more experiments than in a manual fashion. An automated experiment, it helps us verify our assumptions over time as unknown parts of the system are changed. Think again about these downstream dependencies we might have, different parts of the system that other people handle and deploy and make changes to. And to do chaos engineering in an automated way, you really need to make sure to have safeguards and stop conditions in place to do it in a safe way. So make sure that your alarms and your observability into your system are in place before switching into an automated way of running it. And just a final reminder, doing automated chaos engineering experiments doesn't mean that you should stop doing manual experiments. They should still be the core of your practice. And if you just can't get enough of chaos engineering for improving resilience, I've gathered code samples used in the demos and some additional resources for you in the link shown on screen right now. So you can either scan the QR code or simply enter grosh.link slash auto chaos. And with that, I wanna thank you all for watching. We looked at how to improve resilience with automated chaos engineering. If you have any questions or comments besides what might already be in the QA section, do reach out on Twitter at Gunnar Grosh as shown on screen or please connect on LinkedIn. I'm happy to connect with every one of you. And with that, thank you very much for watching. So let's see if there are any questions. All right, so we have, okay. So we have one question so far. So how is it different from load or stress testing? Is that enough? Yeah. And that's a common question I would say. Load testing and stress testing, they test how your system handles exactly those things, how your system behaves under stress. Chaos engineering or using stress testing is not uncommon to do in together with chaos engineering. So for instance, when we do chaos engineering experiments, we wanna do them as close to production as possible. So for instance, we wanna run them in production. That's maybe the end goal, but that's not always possible. So what's quite common is to run your experiments in a staging environment or a test environment and then use load testing or at least create load as well. So you're running that at the same time to make the system more production-like so that you actually have traffic running towards the system. But with chaos engineering, instead of simply testing load or doing stress testing, you can create experiments like the one I showed that for instance, terminates instances, but you can create quite complex experiments that perform different things on your system. For instance, removing a downstream API, you can throttle APIs, you can use commands to kill a process on a running instance and things like that. So this is something that might use stress testing as well as part of your experiments, but it's a bit different in how you're actually running experiments. All right, well, thank you so much, Vinor, for this session. And yeah, thanks everyone for attending. Thank you all.