Marjorie Taylor Greene is one of the biggest morons in America and she is a lawmaker but yet she knows nothing about law or policy therefore she kind of is forced to just be a cheerleader for the far right and for Christian nationalists in America which she says by the way is a good thing but because she can't actually come up with any policies to improve the lives of her constituents well she's forced to try to goad people into giving her publicity stunts which she can then fundraise off of for example she tweeted to Parkland mass shooting survivor turned gun control advocate David Hogg I hear you when your girls are funded to come to town this week to once again try to manipulate some of my gutless week colleagues to vote for gun control that will violate our freedoms and leave Americans defenseless I don't see you on my schedule why not first of all note the homophobic jab there I see that you're in town with your girls it's funny that you're always hanging out with girls is that you're only friends are you not a real man do you not have friends who are male you must be gay and that's bad definitely I mean what a horrible person she is but she is trying to get this person who literally became a gun control advocate because he almost died during a mass shooting to come to her office so she can then tell all of her constituents hey I just defended your rights I defended your freedom maybe chip it and give me 10 bucks it's just so shameless it's so transparent and yet she does it all the time and anyone who engages with Marjorie Taylor Green and tries to have an honest conversation is wasting their time to have a conversation with her would be less successful than having a conversation with a houseplant and I mean that literally it's why people like AOC refuse to engage in a debate with her it's why David Hogg turned her down because you're not going to have a conversation with someone this bad faith this moronic and David Hogg responded by ratioing her into oblivion saying congresswoman green I'm more interested in protecting children and meeting common sense people who are looking for reasonable solutions to stop children from dying don't really have time to help you go viral for attacking survivors so you can fundraise respectfully David and he adds since you were going to use me as a fundraising opportunity I will ask people to please donate to support our march on June 11th of Americans both democrat and republican demanding gun safety go to marchforourlives.com slash donate now Fred Gutenberg whose child Jamie was murdered during the parkland school shooting tweeted this to Marjorie Taylor Green hey representative mtg I will also be coming to dc I will bring pictures of my girl Jamie who was murdered in parkland if you are looking for people to put on your schedule please put me Wednesday Thursday or Friday what day is best for you now for some reason Marjorie Taylor Green hasn't responded hmm interesting maybe she didn't see it maybe it's just a little bit more difficult to look a father whose child was murdered in the face and say you're taking away my freedom she can't do that it's easier to try to bully someone who is a lot younger than her probably you know she's twice his age and who she perceives to be gay so therefore you know maybe she could push him around because he's gay he's weak he's always hanging around with girls but she doesn't want to talk to this father doesn't want to look him in the eye interesting can't fundraise off of that right you can't get a win out of that situation because you kind of look terrible no she still looks terrible either way this is an individual who followed David Hogg around in dc and was yelling at him harassing him because he wants to take away her freedom supposedly because he's advocating for common sense gun control I mean this is who we have elected in congress and she's going to win re-election almost certainly I mean if you look at the GOP primary that took place in her district she won with 69.5 of the vote so GOP voters specifically in this district they see that they have this imbecile representing her they're not getting any wealthier they're getting more poor more disadvantaged they still don't have out health care basic access to education that is affordable and yet they're saying you know what we want to send this imbecile back to congress because even though she's not doing anything to improve our lives economically or socially at least she's making people um feel bad by owning the libs and calling gays pedophiles which on that note she uh kicked off pride by doing just that saying I could care less what two consenting adults do sexually nor do I judge but when it comes to adults training children sexually both mentally and physically I do care and so do most people we must protect children from child grooming predators and abusers in every way possible first of all the saying is I couldn't care less because if you say that you could care less it implies that you do care at least a little but she's implying here that LGBTQ plus people are groomers and pedophiles and that's what they're doing en masse meanwhile one of her closest allies in congress Matt Gaetz is being investigated for sex trafficking of minors and to make matters worse she just hired fellow christian nationalist Milo Unopolis as an intern who was fired from Breitbart literally because he made pro pedophilia comments the new york times described a tape where he made these comments in a 2017 article saying but in the tape the fast-talking polemicist is clear that he has no problem with older men abusing children as young as 13 which he then conflates with relationships between older and younger gay men who are of consenting age no no no you're misunderstanding what pedophilia means Mr. Unopolis says on tape in which he is talking to radio hosts in a video chat pedophilia is not a sexual attraction to somebody 13 years old who is sexually mature pedophilia is attraction to children who have not reached maturity he adds dismissing the fact that 13 year olds are children the notion of consent he says is arbitrary and depressive at one point in the video an unknown speaker says that the behavior being defended by Mr. Unopolis is akin to molestation by Catholic priests Mr. Unopolis responds in an ironic tone by crediting a priest for having helped develop his sexual technique conservatives reacted with near unanimous disgust at the comments but what does marjorie green do she hires this individual who made pro pedophilia comments he defended child abuse and said that age of consent laws are oppressive and yet she's like i want to hire him i want to align with the person who's under investigation for sex trafficking of a minor whose ally is in trouble for this thing and yet she's saying oh my god we have to protect children from groomers lgbtq plus people marjorie it's not lgbtq plus people who are groomers you need to look in the mirror because you're aiding and abetting actual fucking groomers or people who advocate for the abuse of children it's truly astonishing but again she won her election overwhelmingly her gop primary so you know she wears this hypocrisy on her sleeve in a shameless fashion and her constituent said yep let's give her two more years at a minimum in congress overwhelmingly so so it's not just that gop lawmakers are unhinged and insane the base has become so detached from reality that now they don't care about their own well-being they don't care about the economy as much as they care about triggering the libs they don't care that they can make a living wage and don't have health care so long as marjorie taylor green continues to call gay people pedophiles isn't that astonishing one of two major political parties is essentially an alliance of christian nationalists and far-right fascists and they make it known that all they care about is total domination and subjugating the rest of us to their theocratic beliefs but yet the base is like yeah i'd rather stay poor and vote for that so that way they can own the libs than actually vote for someone who cares about us it's truly ridiculous but this is the state of american politics the gop is a cult and until we convince our gop friends to wake the fuck up and stop voting for these ghouls nothing is going to change in this country the gop base loves it right there's no such thing as ultra maga it's not like marjorie taylor green or donald trump is some sort of an anomaly this is who the gop is and to deny it is to be complicit in what they're doing to this country so that's marjorie taylor green shamelessly hypocritical shamelessly trying to make money off of school shooting survivors who she thinks that she could bully and yet you know she's gonna get elected she shouldn't even be in congress mind you because it is unconstitutional literally for an insurrectionist to be in congress but yet she's gonna get elected overwhelmingly i mean what kind of a backwards as country is this where we actually have somebody in violation of the constitution because she's an insurrectionist but yet she gets to remain in congress even though illegally she should be disqualified from running and on top of that we have a secular constitution as fucked up as the u.s constitution is but at least it's secular and it says that you know the government cannot establish a religion but yet the theocrats have taken over and they get to choose the way that we live our lives trans people shouldn't be able to transition if you're a parent you can't seek out gender from and care for your child if you're a woman you can't get an abortion but yet these people are the defenders of the constitution it's just truly ridiculous but again this is the g.o.p marjorie green isn't the exception to the rule she represents all of them do yourself a favor and click the join button on youtube to become a member because makes doing a great job getting to watch his videos before everyone else is tremendous many people are saying this join today folks you won't regret it


Harry Show brought to you by the United States Army and the United States Air Force recruiting service. That's right, it is, fellas. S. Vandenberg, chief of staff of your United States Air Force, said in a recent magazine article, air power alone does not guarantee America's security, but I believe it best exploits the nation's greatest asset, our technological skill. Your United States Air Force, in order to keep winning, needs men who have technical skills. Veterans trained in any service, veterans with needed skills in such fields as radio, radar, weather, maintenance, and many others. You veterans who have such needed skills, if qualified, can now enlist in your Air Force, get back your old grade or better, skip basic training, and get your initial assignment to a nearby Air Force base. So take a look at the list of technical skills needed and find your spot in the Air Force by visiting your nearest United States Army and United States Air Force recruiting station tomorrow. You'll be glad you did, because your Air Force is a great outfit. One you'll be proud to serve in. And now, Harold Perry, as Honest Harold, the homemaker. Once upon a time there lived an awfully nice fellow named Honest Harold, that's me, and he had a sweetheart named Flora Belle Breckenridge. Pretty. One day Flora Belle moved to the neighboring town of Charleville, where she became engaged to Willis, a big green merchant. Oh, he was bigger than that. Last week she came back to Melrose Springs on a visit, and who did she run into? But Honest Harold. That's me again. Well, Harold acted just like a brother to Flora Belle, but Willis misunderstood and became very jealous. So Flora Belle broke her engagement with Willis, and Willis threatened to come over and break Harold in two. Sounds bad, doesn't it? This evening now, and Honest Harold is nervously pacing up and down his living room, wearing out Mother's Congolium. I wonder when Willis is coming, for all I know he might be in town right now, lurking around outside. He could come in the back door, hide behind the laundry tubs, then sneak up behind me and... Hello, Harold. Oh, it's you, Mother. Why, what's the matter, son? Nothing.  Nervous? Not at all. Why, do you keep looking out the window, Harold? Are you expecting someone? Well, a fellow might pay me a little visit. Maybe he won't be able to find the house. Shall I turn on the porch light? Yeah, no, Mother.  I'm afraid. Well, I've finished the dishes. I think I'll sit down and read a while. Oh, still reading that same book, Mother? Crochet Your Way to Happiness? No, I've finished that. I'm reading a murder mystery magazine. A murder mystery magazine? Yes. I got it at the drug store yesterday. The story I'm reading is about a rejected suitor. He murders the man who stole his sweetheart. It's called, uh, My Body Lies Over the Highway. I don't know how they think of those titles. I do. But it's very exciting. Would you like to hear a little of it, Harold? Well, I... It was a dark, moonless night. And Fenwick, he was the rejected suitor, Harold. Fenwick stalked his prey relentlessly. Uh, Mother? He was determined to kill the man who had stolen his loved one, a man who was known as Archibald. Archibald could be me. Archibald awaited the killers coming fearfully, trembling, and the only sound in his room was the ticking of the clock. Tick, tock, tick, tock. Sounds like Mother needs winding. Suddenly, Archibald heard a noise. And then his door opened slowly, slowly, slowly. And there he stood. Who, Mother? I don't know. It says continued next week. Oh, my goodness. I guess we'll just have to wait. The magazine will be out around next Wednesday. I hope I'm still around next Wednesday. Certainly didn't get much sleep last night. Well, things don't seem so bad in the daytime, though. After all, why should I be scared of Willis? Let him come. I can take care of myself. I'll look him right in the eye and say... Oh, Doc. What's the idea of sneaking up on me like that, you old horse doctor? Oh, sorry, Herr. I'm wearing my surgical sneakers today. I guess you're pretty nervous these days. What? It must be awful to walk down the street and never know when sudden death will strike. Doc, please. Figure speech, Herr. Matter of fact, you don't have to be afraid of Willis. You can be ready for him if you just take my advice. Uh-huh. What's that? Just answer this ad, Herr. I cut it out of a magazine last night. Let me see. Men and women learn jiu-jitsu by male. Oh, my goodness. Oh, it comes in very handy, Herr. See what it says? Learn to disarm burglars, surprise bullies with your strength, protect yourself against mashers at the movies. Mashers at the movies. And, of course, only takes eight weeks, Herr. That's wonderful. I could study it in the ambulance coming home. Thank you very much, Doc. That's all right, Herr. When you're in trouble, you can always count on Doc Yancey. Yeah, for more trouble. Yes, sir. He's Johnny on the spot when you need him. All right, Doc. When you're lost on the desert without water, who comes right into the rescue on a camel? Rudolph Valentino. I'll see you on the desert, Rudy, where you're surgical sneaker. So I'll know you. Yeah, you'll be shy, Herr. Oh, Doc Yac-Yac in his jiu-jitsu. Wonder when Willis is going to show up. It's getting to be a war of nerves. Wish I could declare myself an open city. Better stay away from Flora Belle that we get this thing settled. Maybe if I can just see Willis alone, we can arbitrate this thing. Oh, Judgey Ro! Oh, God, it's Flora Belle. I better get out of here. She's right on my heels. Herr, what do you call me? Gaining on me. Hot of breath already. I have to cut out those banana splits. I can just make it to the YMCA. Darn it, the only single in town that had a change on me. Herr, are you trying to run away from me? Run away? No. I believe you will. And that's not very nice after I broke my engagement with Willis on account of you. Well, you see. Acting this way after all we meant to each other. Remember when you wrote my memory book yours till Niagara falls? Well, yes. Are they still falling how? I'll go see. Goodbye. Well, you're not worried about Willis coming here, are you? Worried? Of course not. Well, I guess I never should have come back into your life. But I was drawn like a bee to a flower. Yeah, well, in Flora Belle. Oh, don't fight it, Herr. It's bigger than both of us. Yeah, but so is Willis. Well, if I can forget Willis, what? Herr, I just looked at the almanac and you know something. There's a moon out tonight. I think there's a moon out tonight, too. Oh, it would be nice to go riding. Visit all our old spots and park in the dark. Park in, well. How about it, Tessie Roll? I'd love to go for driving your car. Driving my car? Sure, I'll be busy, but here are the keys. Drive any place you want to. Car's kind of hard to start, though. Give it plenty of choke. And don't ride the clutch. Goodbye. I'll connect you. Hey, Gloria. Oh, Harold, there was a man here looking for you. What? What did he look like, Gloria? Well, he was tall, had big, broad shoulders. Was his name Willis Cider? No, it was Percy Jones. Oh, well, who's he? An insurance salesman. He said you might be interested in his hospital insurance. Hospital insurance? That's ridiculous, Gloria. Who gave him my name? Willis Cider. Zeef. Here's his card. It's awfully clever. For broken bones, he Percy Jones. Gloria, you're making that up. No, I'm not. And he left this booklet for you. How to be happy though hospitalized. She didn't make that up. See you later, Gloria. I'll be in my office. Imagine that Willis sending that insurance man to see me. Suppose he thinks that'll intimidate me. Well, it does a little. Maybe I'd better lock the door. Just forget all about Willis. Line up my program for this morning. Let's see here. It's the first number on the list. I'll be glad when you're dead, you rascal. You better change that. See, I'll use I'll never be the same. Wow. It's no good either. Who's that? Hello? Yes, Gloria. Charlieville. Wait. Who's calling please? This is Willis Cider. Hello, Willis. How's your friend Percy Jones? Never mind him. Okay, we'll skip him. Nice of you to call, Willis. How about having lunch together sometime? I'll have lunch with you all right now. Settle your hash. Lunch? Settle that. Hey, that's very clever, Willis. I thought so too, Harold. Gloria, get off the line.  Is that a threat? Yes. Well, it's a pretty good one. Don't worry, I will. Willis, when do you expect to come today? No, in three years. What? I'm enlisting in the Air Force today. Air Force? Oh, well, I'll see you in three years, Willis. Roger. We'll come over and out. Goodbye. Off we go into the wild blue yonder. Are you comfy, Flora Bell? Mm-hmm. I could ride like this forever. Well, I'm afraid this 36S6 won't last that long. Yeah, this is fun, Flora Bell.  Yes, maybe we ought to stop a while and give the car a rest. Ah, good idea. Yeah, as he has been a little run down lately, been coughing a lot in the morning. Well, we stopped, Harold, right in back of our old high school. Yeah, in the same old crickets. Mm-hmm. What's that wonderful perfume in the air? Winter blooming jasmine? No, that's oil of wintergreen, we're parked behind the gymnasium. What? Well, this morning I thought you were afraid to see me on account of Willis. Afraid? No. As a matter of fact, I think little old Willis is a pretty nice fellow. Oh, I'm glad. He just called me this evening and told me about enlisting in the Air Force. Oh, he did? He felt awful bad. They wouldn't take him. Wouldn't take him? Oh, no, poor Mayan. He couldn't pass the physical. Oh, well, what am I worried about? He's probably a physical wreck. They said they couldn't use him in the Air Force. He was too big. Oh. And Willis told me to tell you he'd see you tomorrow. Zoink. I'm going home and call Percy Jones about his happy hospitalization. Return for the second act of our story, Honest Harold, in just a moment. Here's a special note for the women. That list of the best dressed women in America hasn't come out yet, but we can tell you right now that one girl is sure to be on any such list. She's the smartest woman of the year or any other year. She's the girl in that new Air Force blue uniform worn by the women in the Air Force, but that girl in the WAF uniform is smart in another way too. May be a better way if you like. She's found a good career in a great outfit, working on equal terms with men of the great Air Force and hundreds of interesting, challenging jobs. She's found a service in which the way is open to the top by means of officer candidate schools that produce smart WAF officers. What's more, many girls with college degrees are coming into the WAF to go directly to officer candidate school and win commissions. Another way of being smart. How about you? Can you qualify? If you're between 18 and 34, ask your nearest United States Army and United States Air Force recruiting station for the details tomorrow. And now back to Harold Perry as honest Harold the homemaker. Well it's a chill windy day in Melrose Springs. The skies are ash and gray and honest Harold is a little gray himself as we find him on his way to the Melrose Springs police station. Gosh, I don't know when Willis is gonna spring out at me. The lad will have tracked me down anytime. I feel like a cornered caribou. This is the right thing to do all right. I'll see Pete the Marshal. I'll demand protection. Sure. Pete, I want to talk to you. What a police force. What can I do for you boy? Well you can wake up first. Okay Harold. Pete, I'm a taxpayer and I demand protection.  Pete, Flora Bell's fiance is after me. What's the matter? He want to marry you too? Another doozy boy. Look Pete, this is a serious matter. This fellow is threatening me with bodily harm and you've got to do something about it. Okay, first I got to fill out a form. Oh, you guys. Let me see here now. First question. How was victim injured? What? Gunshot, stabbing or miscellaneous. Pete, for heaven's sake, I haven't been injured yet. Oh, that's too bad Harold. What? I can't do a thing until after the assault and battery has taken place.  Sure Harold. I'd do it for anybody. I'm wasting my time here. I'm going to dump your mac and on boy. I just got an idea. What's that? What you need is that bodyguard. You said it. And I got just the man for you. Nephew of mine got in town last night. Look Pete, I don't want any of your sleeping relatives. I want somebody big and tough. Harold, he's from Texas. Oh, he's? Yep. Used to be one of them Texas Ranger. Really? Well, I guess he's one of those big tall fellas. Well, he slept in my room last night. That is, he was in my room. His feet was out on the screen porch. Hey, sounds like just the thing. Pete, he's hired. Who's afraid of Willis? Tell Tex to meet me tonight over at the ranch house partner. Yee-hoo! To meet love and say, well, I'm a long and dear. But I'll have a wonderful time with Flora Belle tonight, dancing at the Antler Hotel in the moose room. I won't have to worry about a thing with Pete's nephew guarding me. Pete's from Texas. You ought to feel at home in the moose room. Yes, that's my Texas Ranger now. Let's have a look at this big, tough hombre. Good evening, sir. Oh, my goodness. Are you Pete's nephew? Yes, or my name is Virgil. Uncle Pete said you wanted a bodyguard. I am Pete.  Looks like an anemic semaphore signal. Come in, Virgil. Thank you, sir. Ah, shucks, I've bumped my head again. Eyes open. Yeah, yeah. Sit down, Virgil. Thank you, sir. Sits down in sections.  Oh, shucks, I never carry a gun. Why, it might go off. What? But Pete said you were a Texas Ranger. Oh, I was, sir. When I was 12, I belonged to the junior ranger. What? I was in the coyote patrol. Mind me a boonman row. Look, Virgil, did your uncle Pete explain you were supposed to guard me tonight? Oh, yes, sir. Well, he is certainly tall, but you don't look very strong. Well, I was pretty athletic in high school. I was on the basketball team for a while, but I had to quit. Oh. My head kept getting stuck in the hoop. Probably still wearing it under that hat. Well, come on, Virgil. I have to pick up my date and then we're going dancing. Oh, good. Nice of you to ask me, sir. I'm kind of good at the one step. Yeah, Virgil, Flora Bell and I are going to do the dancing. You're supposed to stay outside and guard me. Oh, I get it. I doubt it.  What am I saying? Come on, Virgil, and watch out for that door jam. Nice. I've never seen the moose room looking so lovely. Yeah, it's a cute idea putting that neon nose on that stuffed moose. And it's so cozy here in this little booth, just the two of us. Yeah, I hope it stays the two of us. Oh, you don't have to worry. Willis will never get past Virgil. He won't have to go past him. He can walk right under his legs. Besides, it's getting late. Looks like Willis won't come at all. Yeah, maybe you're right. You know, Harold, you've hardly looked at me all evening. It's not very flattering. Well, you do look awfully pretty in your off the shoulder. Oh, thank you, sir. You know, if you would lean over this table, I might reward you with a little kiss. I might just do that. I'll be right over. Just wait till I move this Dr. Pepper bottle out of the way. I'm waiting. Here I come. Pardon me, sir. Kevin's safe. What is it, Virgil? Hello, Virgil. Evening, man. Virgil, what are you doing in here? Well, I got kind of hungry outside. So I came in the moose room and got me a moose burger. Oh, that was a doozy. Oh, goodness. The doozy's running the family. Okay, Virgil, you've got your sandwich. Now will you get out of here and watch out for that? See, that music's kind of pretty, ain't it, ma'am? Yes. I don't suppose you'd care to have this dance with me. What? I'd be delighted to, Virgil. Look, you're supposed to be guarding me. Oh, well, just one little old dance.  But if Willis comes in, you just call me, sir. Oh. And, sir? Yes. Would you mind holding my moose burger? I'll show you the Texas Waddle. Dallas, Houston, San Antone. Clang here, partners. Don't get thrown. Texas Waddle. Willis could walk right in here. What a bodyguard. Better keep Waddle. Watch myself. They could peek out in the lobby. I think I'll hide behind that potted palm in the corner. Nobody can see me from here. Oh, good evening, sir. Good evening. I didn't see you back here. Well, I'm watching for somebody. Oh, so am I. Pretty good place to hide, isn't it? Oh, it sure is. Big boob I'm looking for. Could walk right in and never know I was back here. Same here. Who you waiting for? Some double crossing dude that stole my gal. His name is Harold Hemp. I need him. I'm going to pull this hemp apart strand by strand. That's good. I think of this love thief breaking up my romance. I get so mad I could. Sounds like you could, too. Got to be going. I hope you find him, Willis. Just a minute. How did you know my name was Willis? Well, your laundry market. Did I say Willis? I thought I heard that voice before. You're Harold Hemp. I am. How do you do, Willis? I'm going to break you in two. You've got to catch me first. Hey. Hey, Hemp, where are you? Here I am on the other side of the palm tree. Hello.  You small town sanatra. Oh. That did it. I could be pushed just so far, Willis. We'll settle this thing man to man right now. That suits me. Unless you want to wait eight weeks while I take a Jiu-Jitsu course. Disregard that, Willis. You may be bigger than I am, but I'm not going down without a fight. I can't help with the flora bell. It prefers me to you. There's nothing you can do about it. Oh, yes, there is. You come out of here. I'm going to take you and... Saved by the bell. Flora, that is. Oh, Willis Cider. Are you and Harold getting to be child? I hate him. Likewise. Well, isn't that cute? Flora Bell, you're going to have to make a choice between us right here and now. Yes, right here and now. Willis, coin your own phrases. Willis, though I can't be engaged to you anymore, you'll always be one of my dearest, dearest friends. Yeah, yeah. You see, Willis? And Harold. Yes, Angel Puss? Would it be all right if you and I just went steady every other Saturday night? Ha. You're not doing so well either, Hampton. You see, Virgil has invited me to a bond dance this Saturday night, and he's just so cute, I couldn't say no. You do understand, Harold. Oh, sure. Mr. Hampton, sir. What do you want, Virgil? Your bodyguard reporting. Haven't seen Willis yet. Fine, but don't you worry. Willis won't get by me. He could bite him, and he'd never know it. Oh, will you excuse us, gentlemen? Come on, Virgil. Let's get back and try that Texas waddle again. All right. You're doing just fine. Houston, Dallas, San Antonio. Willis? Yes, Harold. Can I come out now? Sure. Pal. Thanks. Flora Bell, the wonderful girl, but a little fickle. Yeah. Wonderful girl, but a little fickle. Come on, Willis. I'll buy you mooseburger. I'll eat Virgil's. Yeah, yeah, yeah. General Hoyt S. Vandenberg, chief of staff of your United States Air Force, recently had this to say about the mission of the Air Force. I quote, the overriding purpose of every plane, whether it is a bomber or a fighter, is to win the air battle on which final victory is predicated. Let's think about that for a moment. That sentence means, above all, that your United States Air Force needs only the best qualified young men, men with the skills necessary to keep your Air Force winning. That's why it isn't easy to qualify for your modern United States Air Force. That's why your Air Force is now making a special offer to the trained veterans of any service who've proved that they can qualify as men of skill and courage.  You trained veterans, go to your nearest United States Army and United States Air Force Recruiting Station tomorrow, and get details. You have just heard the Harold Perry show, Honest Harold. Yeah, that's me. The supporting players tonight included Jane Morgan, as Mother Hemp, Harley Bayer, as Pete DeMarcel, Shirley Mitchell, as Flora Bell, Life Erickson, as Willis, Bob Easton, as Virgil, and featured Gloria Holiday as Gloria and Joseph Kearns as Old Doc Yak Yak. Yes, yes. Norman McDonald directed and the music was composed and conducted by Jack Meakin. Yasha. The Honest Harold created by Harold Perry was written by Gene Stone, Jack Robinson, and Dick Powell. Yes, an important name. The Harold Perry show has been brought to you by the United States Army and the United States Air Force Recruiting Service. That is, fellas. Visit your nearest Recruiting Station tomorrow, Bob LeMond speaking. This is CBS, the Columbia Broadcasting System.


All right. This is the end of the paved road. Maintaining links to 4.4 beyond LTS. I am somebody who has been paid to do Linux stuff for a very long time. A few weird acronyms that need to be defined so you all understand what I'm talking about here. CIP is the Civil Infrastructure Platform. It's provided by the Civil Infrastructure Platform project. And it's a kernel and user space for civil infrastructure and industrial applications. The Linux stable kernel maintainers once in a while pick a branch of the Linux kernel and maintain it as the LTS long term support kernel. And this is maintained for a couple of years and it's something that is used most prominently in Android and Debian and in some other applications. Once in a while the Civil Infrastructure Platform project picks one of these LTS kernels and chooses it as the super long term support kernel. And the way that works is that while LTS is maintained the SLTS kernel runs in parallel with the LTS kernel and once LTS goes out of support the CIP project takes over and maintains that kernel for as long as it takes but for a minimum of 10 years. And this is what I'm going to talk about today, the SLTS kernel, how and why. When you talk about old kernels people have opinions. When the CIP project was looking for an additional kernel maintainer who eventually became me or I became that maintainer. Chris Patterson was scouring the darkest corners of the internet to find a suitable candidate and one day he dropped into a private IRC channel where I and a bunch of other embedded kernel developers hang out and asked if somebody wants to help with that. So this is the first reaction he got. Maintaining a gerontic vendor kernel with a billion backported patches until the end of times sounds exciting, not really. A lot of people don't want to do that kind of stuff. I don't know why I'm quite happy with that. But yeah, this is a matter of personal preference. So people just viscerally don't like that idea like old stuff. We don't like to maintain that. Another kind of feedback that we got is after the announcement by Pavel Mocek that we are going to keep maintaining the 4.4 kernel as an SLTS kernel, a prominent kernel maintainer wrote this, it costs more money and time the older the kernel is to keep it alive and it's cheaper and easier to use more modern kernels. Well, how valid that argument is and how relevant it is is something I'm going to be talking about today. And to understand that we need to talk a bit about time scales. How you perceive time depends on what hat you're wearing. If you are like a chip designer you think in nanoseconds, if you're a geologist you think in millions of years. Linux kernel developers think sort of like that. Now is the time where we are at. The last release was a complete bogus done by imbeciles. We don't talk about that anymore. And 12 years ago that's antiquity, it was kernel 2.6. Now I'm poking fun at this but if you tell me kernel 2.6 I think Jesus. Did that even have networking already? It feels incredibly old even though it was only 12 years ago and 32 years ago is the beginning of time before nothing existed. This kind of thinking in these scales is good if you are developing products that have a similar lifespan. Mobile phones being the canonical example. If we're looking at civil infrastructure things are a bit different. First thing you can look at who makes civil infrastructure and for that look no further than the members of the CIP project which are obviously engaged in that kind of stuff. There are nine of them. All of them are corporations and four have been around for more than 100 years. Those being Siemens, Toshiba, Bosch and Hitachi. So that's generations. I think Siemens predates Germany so that's quite a bit. So these are super human time scales. Nobody lives that long. So that gives you kind of a hint. We left that frame like back when we were young and we're now at the point where we say back when my great-great-grandfather wasn't born yet. But these are just names of course. No person who works for these companies is the same anymore and they're also largely not using the same technology anymore. So what about the actual stuff? I call it stuff because honestly I could not come up with a term that describes everything from elevator controllers to fusion reactors. I just call it the stuff. Here's a bit of stuff. This is the Yaruga-2, a hydroelectric power station in Croatia. That's the River Krikka in the front. And it's number two. It has an older sibling number one, Yaruga-1. That was built in 1895. And its distinction is that it is the second oldest of its kind. The second oldest multi-phase alternating current power station. The first one went up two days before that on Niagara Falls in the US. And if you didn't know anything about the state of telecommunications technology, at the time you would think they did that on purpose. But it was probably just a coincidence. So a couple of years later Yaruga-2 was built because new industry popped up in the area and more electricity was needed. So this was completed in 1903 and it went online in 1904. And that's the end of the story because in this year of our Lord 2023 it's still online. And it still does the same thing that it did 120 years ago. Without any fundamental changes it has been refurbished about four times per century. I think in 1936 or 1937 they installed an additional generator. But it's fundamentally the same plant. And it's a production power station. It's not something that technology enthusiasts keep alive for fun or as a tourist attraction. This is production. It supplies energy to the grid. And it is not an outlier. Power stations of similar vintage, there are plenty of those that are still running. And if you look at slightly younger ones, younger as in only 70 years old or 80 years old, there are at least dozens if not hundreds. I didn't count all of them, but I would say it's in the hundreds. So the actual stuff also lasts for forever, for generations. So if you have something like that, if you want to run Linux, or if you want to use Linux in running it, you probably do, what kind of a kernel would you want for that? You don't want any regressions ever. If something works, it should keep working no exceptions. That is understandable that you would want that. But there's an easy way to achieve that. Just don't update your kernel, which for some applications would actually work. But in many cases you want stuff fixed. You want bad bugs to be fixed, things that might break stuff in the future that haven't been triggered yet. And of course, exploitable vulnerabilities. You don't want anybody else to break your stuff. So that actually needs updates. So it needs to be maintained. You also want to keep the same code base as long as possible, and that's maybe not immediately clear what the benefit of that is. But one thing is in major kernel updates, regressions are inevitable. And I'd like to open a parenthesis here.   Unfortunately, we haven't been doing that for long enough yet, so I don't actually have meaningful numbers. I can crunch the numbers, but if you want to identify regressions, you need to look into the future. Because if we knew it was wrong, we wouldn't have put it in the kernel yet. So we only know in the future if something, if a patch was bad. And we've only been doing a few releases so far. So I might be undercounting regressions, especially in the super long term support kernel. So I didn't feel comfortable giving you numbers. But unofficially, I am incentivized to think that it's bad. It's actually worth very bad. The other thing that is less disputable is that if you change your entire operating system kernel, you might have to recertify. I don't know anything about the actual practice of that. I'm an open source developer. I throw code over a fence and then what people do with that, it's their business. But I've yet to meet anybody who says we had a great time doing recertification. So how do you provide something like that? We thought about that and we have an approach. How you can provide such a kernel in the face of limited resources. Step one is limit the scope. We are not maintaining a kernel that you can drop into everything from IoT devices to supercomputers. It's intended to be used in specific cases. And what those cases are is informed by our members' needs. If you're an embedded Linux developer or probably an embedded operating system developer in general, you know that you're not necessarily told what your stuff is being used for. But at least in the CIP project, we know our members' platforms. We have reference platforms and we know their kernel configuration. So we have an idea what our stuff is being used for and we can focus on those things.  I'd like to point out, no, it's not. We are not exclusively doing that stuff. We don't intentionally leave things by the wayside because they're not part of what our members' needs. We do the other stuff as well on a best effort basis. And we also accept outside contributions. So if we say, okay, we didn't put that in because it's too much work, you can do the work for us and say, I did that, I tested it here. Have some and we will look upon that favorably and we will probably include it. The other thing is, within that scope we want to minimize changes as much as possible. If it's not trivial or important, it's out, that's an inclusive or. If it's trivial, if you can see it's a one-liner patch, it's correct, it's in. There's no question about that. If it's important, if it can break something, if it's exploitable, if you really want to have it fixed, it's in no matter how complicated it is because what are you going to do? We just have to invest that effort. If it's neither, which in other words means it's a complicated useless mess, then it's not going to go in because back porting may introduce bugs and you need to have some benefits for that. Why would you do it if there is no benefit? And the more complicated a patch is, the more likely it is that something will go wrong. So we only do that when it's actually important. The good news is that most patches for stable currents are small, like as in really small one-liners, and they typically deal with stuff where you say, well, of course. They didn't shake far out of memory, didn't bring down the clocks again when the device fails to probe, checked for the wrong return value, checked for zero when you should check for negative one, for equality if it should be inequality, things like that. That's the vast majority of patches in stable and these are of course very easy to back port if you need back porting at all. So this is how we do it, or more specifically how I do it. I am maintaining the 4.4 kernel and part of that is policy, part of it is best practice and part of it is my own judgment, but this is how it actually happens. So step one is ingest all the patches. We originally base our stuff on LTS. Once LTS is no longer maintained, we don't have patches anymore that we can apply. So we just do the next best thing and look at the next supported LTS kernel at the moment that is 4.14 and just hoover in every patch there is. We have a tool for that and just throws all these patches at the 4.4 kernel and see what sticks. If it applies, okay, we leave it in for now. If it doesn't apply, it gets put on the side and this tool produces a log file and that is in my opinion the most important thing about the entire project, that log file details what we put in, what we don't put in, what automatically applied, what had to be manually back ported, what was ignored, why it was ignored. Basically, you know exactly why something went into the SLTS kernel or did not if you look at that file. Once that is done, you have to look at the stuff that didn't work. What about the patches that didn't apply cleanly? Most of them are not applicable at all that is to say they don't make sense in the context of the 4.4 kernel. The most obvious case being it's a fix for a driver that doesn't exist yet. You can obviously ignore that. Another very common case is it's a fix for a problem that was introduced after 4.4. You don't need that either. If not the majority, then at least the plurality of patches fall into the category. Most of the stuff you can just ignore. The next step is back port the easy ones. Remember when it's trivial, it goes in. If it's a one line and if it's correct, you just back port that. I don't generally spend time thinking about how important is that. Do we actually need that because it's faster to just back port the thing if it's obviously correct. The other thing that needs to be back ported and are the important patches, the stuff that basically the point why we're all doing this is they're really bad things that need to be fixed. What was I getting at? These are the ones that were mentioned earlier in the comment by the kernel maintainer is that it gets increasingly difficult to maintain an old code base, the older it gets. That is true, but it only applies to this specific case, the important patches that need to be back ported even though they are not trivial. In practice, that extremely rarely happens. There's maybe one per release. I think the worst was like two or even none. This is, yes, that's difficult, but it's a very rare case. Once all the patches that didn't apply have been reviewed, you have to look at the ones that have applied because just because something applies doesn't mean it actually works. In some cases, somewhere down the line a bit of code was removed and then somebody thought about it and maybe we shouldn't have removed that and then it gets added again. But it has never been removed from the 4.4 kernel, but because the patch only sees a small snippet of the context, it might still apply, so it might have the same piece of code in that twice. You actually have to look at all the patches that do apply. Do they make sense? After that, we basically have everything that we want in a release on top of the previous release and we need to run a few tests. Usually these local compile tests, they go together with reviewing the patches that automatically apply because that's actually the easiest way to find them because they use APIs that don't exist yet. Stuff that doesn't make sense that easily falls out of those compile tests. And the other thing is the Linux CI PCI, which we, as project members, we can use to just push a kernel up and have it run through the entire test suite, through which all of our stuff goes once it's released anyway. After that, the next step is push out a release candidate tree. That is for review. And then I send a request to CIPDef, that's our developer mailing list, and ask for reviews of the back ports. Final step, release. There are four flavors of the SLTS kernel. Once reviews are done, test pass or I release the 4.4 ST kernel, that's the vanilla SLTS kernel, that contains all the stable patches that are not specific to vendors or to our member stuff. The next step is merge this new ST kernel into the 4.4 CIP kernel. That is a kernel that contains a lot, and I mean a lot with capital letters, of member patches that are specific, that are submitted by our members that they would like to see in their 4.4 kernel, even though they were not yet enabled at that time. And that is the thing that you saw mentioned in the first quote about the billion back ported patches. And again, yes, they are a billion or something like that, but completely hassle-free, never had an issue with that, even though there are lots of them, it just works. So that might sound like a big effort, but in practice it actually isn't. And then there are two more flavors, which I'm currently not maintaining, probably still maintaining that. Those are the real-time branches, again 4.4 ST, the vanilla SLTS kernel, with real-time patches and 4.4 CIP RT. The process is similar, so I'm not gonna go into that here. So, what's the point of that? Why am I telling you that? Why am I telling you in detail how I do every patch, et cetera, et cetera? The thing is, cheap and easy, if you remember the quote from before, that's not what we're going for. It's long-term stability until the end of times. And what this is to show you is not to encourage you to go ahead now and start a new project with 4.4 SLTS, even though it's such a great kernel maintained by me and everybody wants it, you are not supposed to do that. The point is to show you that we are willing and able to do that. It's a proof of concept, and to show you that if you start your project today with 6.1 SLTS, we are going to be there and we are going to maintain that thing, we'll keep it running for as long as it takes. That's it already. So, thank you for listening on behalf of the team as well. And I think I was much faster now than I thought I would be. So, there is time for questions. Yes. Thank you. In the patches that you apply, what is the percentage of security versus all the general backfixes? I can't give you an exact number, but I think it's pretty low. We also have an announcement for every new release that details which security issues have been fixed. It's a small number compared to the overall number of patches. So, now it's 4.4, I just saw 6.1, this is the next one. Have you thought about scaling because per new SLTS you decide to have, do you have a separate maintainer? This will stack up over time, we will have a lot of SLTS. I think we don't want to go beyond what we currently have, which is 4.4, 4.19, 5.10 and 6.1. We already have four. And you're maintaining them all? No, we have three maintainers. Okay. As you can see, a lot of other people who are working on that, but we have three people who are specifically for that maintaining the SLTS kernels. Thanks for the talk. How are you making sure that there are no new regressions introduced or maybe more security issues in the old kernels that you're trying to maintain? Is there some testing process going on in the vendors or at CIP? There is, yeah. Chris, do you want to say anything about that? We're collaborating with other testing projects like ComCI to build up, reuse their stuff as well. So yeah, we're testing. We don't have so many specific tests for like specific CVEs and seeing whether they're exploitable still and that it is kind of like, would be nice but as with all these projects it's a case of how much time you've got and resources we're doing. Slightly getting there. Hopefully that helps. So anyone running such an old kernel would probably do so on an old hardware so how do you plan to test on the long run? I'm sorry, I didn't get that. I also can't see you, where are you? Yeah. So, what hardware do you plan to test on the long run? We have reference platforms and we use those. That is the best I can tell you about that. Maybe to follow up on the question regarding how do we scale, how do we want to scale? So the current promise is over 10 years. So as long as it takes is we think we take us 10 years right now to keep the kernels alive, that's the promise and that does the mass that if we continue to release or to commit on one kernel every two years we will end up at max with five kernels in flight that has to be kept this way. Obviously the scale out depends on the capacity that we have as a project and that's also a limitation factor. I mean, if there's a larger interest then you have possibly the probability to extend that. If it really has to be extended beyond 10 years what's your plan on that? I'm interested if you have to respect some kind of upgrade paths between the kernels or is that only on the 25 year scale? That is a good question. I don't actually know that. Upgrade path? About the upgrade of the kernel itself. So if the super LTS kernel is somehow fixed there needs to be an upgrade on the facility on the stuff itself. So is there some kind of agreed on border what kind of upgrade on the stuff is considered harmless so there is no need for a re-certification or things like that and beyond that there is a need for re-certification? I guess that depends on your regulatory body when they require re-certification they try to make the kernel in such a way. The point of the kernel is that you can really just drop it in and don't have to be afraid that something goes wrong. Of course do test it because you know something always goes wrong but the aim is that it's dropped in and there is no issue with that. Thanks for the talk. Do you have a list or a collection of fixes you're not going to backport if they are too complex like the micro-architectural IOU ring or something like that? Yes we do. Like I said we have that file 4.4.org that details everything and specifically what isn't included because it keeps me honest because I can say okay it's easier to throw something out because then I don't have to do any work but there has to be a reason for that and that's detailed there and if there are very prominent components that are left out we also have a known box file inside the kernel tree that explains those things. Apart from announcing the CVEs that got fixed do you also have a more elaborate process for handling CVEs because I would imagine that over the years they accumulate. You probably have fixes for like 400 CVEs there or even thousands. There is a repository I unfortunately forgot the name I'm actually using that to make these announcements that tracks these things so the CIP project has its own repository that tracks such issues. So now the question got me curious did you backport the spectrum mitigation fixes? Nope and the reason for that is it's very intrusive it's very tricky and it's very hard to test so we thought is it actually necessary and the conclusion was the use cases run a specific set of user space binaries and nothing else so bar there being some other vulnerability that allows you to get in it's not exploitable these speculation bugs are not exploitable so we left it out that is a very prominent example that is also in the aforementioned known box file we didn't do that. Do you use the fixes tag in your backport process you didn't mention this in the process so do you make a use of the fixes? Yes you wouldn't make use of the fixes I use it to semi-automate finding out if stuff actually applies or is necessary or not if something fixes an issue that is not in 4.4 I can find that out via the fixes tag and that makes it a bit easier I still look over every single patch but that already gives you an idea which way you're supposed to look so yes we are making use of that. Then the follow up question what else from the upstream maintainers could make your life easier I mean is there something which you want to ask upstream? Correct fixes tag is really very helpful because many aren't like people just come up with ok yeah linux 2.6 is what's being fixed you know that's the favorite and some are just not correct because the bug originates somewhere else and it's just triggered by something and then that is considered the fixed thing which it actually isn't because the bug actually originates somewhere else so correct fixes tags would be really really helpful So recently we found a bug which had originated in 3.7 kernel and we noticed that you have picked that patch up thank you in reverse when you find bug fixes that say 4.4 kernel what's the process that you insist on ensuring that bug fix goes upstream into the latest kernel Basically so we find a bug in 4.4 that is also in upstream How do you enforce that? We get our fixes from LTS so typically those things are already sent to be included in mainline and just are siphoned off to stable and thus end up in our kernel so that usually doesn't happen I don't think it has happened so far that there is something if we have something that is specific to the SLTS kernel then it's something that is a regression in the SLTS kernel and there's not somewhere else that has happened before but typically we don't have anything that actually needs to go to mainline Yes So for the back ported fixes the rules in stable are that you should never back port it to older LTS already in the newer LTS so it's a waterfall model but what do you do with all the extra code that's in the CIP kernel because some of that are back ports from a very recent kernel some of that is code that's not yet upstream that may be back there as well Only back ports really But it means that if you back port so everything should be fixed so if you back port a fix then if there's a similar issue in one of the CIP extra stuff then it should have already been fixed upstream as well because it's upstream only Maybe it also clarified that so really we have this upstream first policy for the suggested feature back ports about support back ports it's a clear rule I'm not aware of exception of this if we had any plug it up that applies obviously you cannot only look at 4.14 to identify all fixes relevant for 4.4 kernel because actually some may only affect 5.10 because this is where the story started so to say for that stuff which wasn't in 4.4 back then so that's why you are reviewing also you're starting to review on the 6.1 baseline currently and end up even newer to get aware of fixes which basically have to jump from the oldest LTS or the newest LTS whatever to our CIP kernel but really this is not a vendor kernel in the sense that you really have stuff there which hasn't been improved by upstream yet Hi How do you track your patches do you have a tool for that do it manually How do we track the patches for example you back port patches from your LTS kernel to yours and then you obviously drop something getting automatically applied something you need to rebase obviously it requires lots of maybe manual work or maybe there is some tool that you use I'm not talking about tool I'm talking about tracks your patches that tool also does the tracking or at least it creates the template for the tracking so we have a look of these patches and we append that to a file and as the process goes along as back porting happens as review happens this template gets filled in with the relevant information has it been put in or not put in how did it go in, why did it go in why did it not go in where all of that stuff is being tracked so yeah we do have that Thanks for doing this I'm wondering how much time do you spend doing this each week on average Personally I spend two days per week Do you use any of the tool language Greg and Sasha use to assemble the LTS kernels because apparently they use some automated scripting as well I think ours is completely homegrown Yeah Well theirs is probably as well but is there some overlap functionality wise there probably is overlap but I have to admit I haven't looked into that because I basically joined the project and the tooling was there so I'm just using it Thanks I think you had one sentence on the slides where you talked about not only the kernel but also other stuff of the system is that other stuff is that or misunderstanding that The CIP the Civil Infrastructure Platform includes user space that's the only thing I can think of right now so it's a combined user space and kernel So you also do patch tracking there or That I don't know I'm only a kernel maintainer Jan can say something about that So the strategy for user space is that we align with Debian and initially thought we had to do the same thing as Ulrich and Koz are doing now with the 4.4 but fortunately Debian LTS and ELTS projects step forward and we are supporting them for a while now so the strategy here is to basically bring our requirements and do these projects and support them together with others from other domains So what would be the next version of an SLTS? The latest and greatest is 6.1 The next one? After 6.1? I don't think we hold that for yet that depends on how things You got an estimate? I cannot really estimate it It will definitely be 6.10 or 6.15 6.10 is a good guess because just from the distance of origin numbers what we have is 4.4 4.19, 5.10 and 6.1 so you can extrapolate from that if you want an estimate So that's no real practice? Yeah That sounds about right Thank you


Extracting the signal from the noise, it's the Cube. Covering VMworld 2015, brought to you by VMware and it's ecosystem sponsors. And now your host, Dave Vellante. Let's go everybody, this is the Cube. We're here live at VMworld 2015. Ed Walsh is here, he's the CEO of CataLogic and Charles Fan is the Senior Vice President and General Manager of Storage and Availability at VMworld. Gentlemen, welcome to the Cube. Thank you for having us. Great to be here. Charles, you're in charge of storage, availability.   So, the weight of the world on your shoulders. So, we saw the keynotes this morning. A lot of talk about hybrid cloud. Had the container conversation of course, but the sand was right in the middle of that sort of hybrid cloud discussion. Sort of the platform on which you're building out the connections to the outside world, but also sort of emulating the facility and ease of use of that public cloud within your own four walls. So, talk a little bit about the keynotes. That was an exciting keynot. They're great to see Yen being up there. I think she looked great. She actually leads all the storage engineering team. And Visa is certainly a core part of our unified hybrid cloud infrastructure. And we are actually great to see Visa as being part of the storage part of a self-defined data center architecture and enabling the long distance V motion across clouds and that was great to see up there. And also a great kit session about the cloud native apps is very important to us. That we must pay more attention to the developers as they're developing their applications. It's actually quite related to the partnership we have with Catalogic. Yeah, so Ed, so I mean I know Catalogic. You and I have known each other for a long time. But for the audience that's not familiar with Catalogic and catalogs, you know, what's that all about? What's the company about? Tell us about Catalogs. Okay, so about Catalogs. But copy data management is where we play. And copy data is pretty simple. It's a copies of production data. Everyone has copy data. In fact, it's good. You have it for resiliency or DR or test dev or dev ops, the application team needs copies of copies. But too much of a good thing can be a bad thing. So copy data is becoming an industry buzzword because IDC and others have done these studies. And IDC say it was very telling. They found it in the enterprise. If you have one copy of production data, you have at least up to 50 of the same copies on disk somewhere. Consuming about 60% of your disk, but also about 85% of your spend on software hardware to store it in enterprise environments. That's a big number. And most of these copies sit completely idle. So the same idea is how do you take a catalog? How do you understand what you have? So what we simply do is we take your infrastructure, be it your VMware environment or storage. We don't make you move it, don't change it. We talk to it via public APIs and we build this metadata catalog. Exactly what's out there and how it's being changed over time. And then we add things like orchestration automation for really interesting use cases. In the end, you're able to drive out a lot of CAPEX but really OPEX. All the manual error prone tasks you have to deploy things, self-provision. And now what you can do is literally publish those templates, allow the app teams now self-provision. Save the app team time, OPEX, but also the storage teams out of the business of even though it can be complex, multi-data center, hybrid cloud deployments, multiple recover points on each side. Very complex environments you can employ but now you can really push it out and let the app teams go provision. Those are the type of use cases we've seen and that's where we're really complimentary. When you hear VMware talking about run, build, deliver, that's what we do on the copy data side, on the storage side, how it all works with the orchestration. And that's where the relationship is. We leverage VMware's powerful APIs, also your storage primitives if you'd call that, right? So the VMotion, the storage VMotion which I studied a relationship or announcements just happened today. But also things like VADP are doing copy services and change block technology or VVOLs. Great abstraction layers but you do need a catalog to keep track of what it is so you have visibility but also the orchestration built around that to leverage it. So okay, so you're solving the copy creep problem which is a waste, economic waste but there's also a value component I heard there. And Charles, you were talking about sort of the developers, the DevOps crowd if you will. So what's the relationship in your mind between sort of this ability to sort of catalog what I have and the development team and that whole notion that Ed brought up about self-service? Right, so obviously we're seeing a great growth of data volume, a lot of copies of the same data. And traditionally we're looking at those as backup copies but now more and more they are test dev copies. As developers deploying their application they have multiple copies of data. So it's not only about data protection but also about building applications, testing applications and deploying applications. So we are seeing more and more customers running to problems like this. We're also seeing partners in our ecosystem like catalogic and others who are providing better solution in helping customers managing those copies both for data protection and application development use cases. And it's our intention really to build the best APIs to working with these ecosystem partners and really making our software defined storage and architecture complete to address the customer needs. Okay, so the catalogs have been, I guess I don't know, catalogs have been around forever. They're just buried inside of some appliance or some array, right? So your strategy is to make that available and open. Is that right? Well, you want to simplify it. So we talked about DevOps. How do you simplify that by using enterprise storage? We use the catalog to understand what's there and then the public API is to now simplify the workflows so it can be very, very complex. The infrastructure guys can set it up but now the DevOps team by making a simple REST call can go either self-provision, gold, silver, bronze, but more importantly, do DevOps. Fence off, use it, promote production, do that multiple times. Who would better do DevOps? Oh, actually the only one that can do that automation is actually the Dev team and we simplify the access by allowing the infrastructure team to keep control. Or DR, who would better do DR testing than the actual app team themselves but what you do need to do is simplify it as they can consume it. You can't make them do the same complexity but all these things also simplify the life of the guy running the infrastructure itself because now they're not doing the mundane tasks. So the catalog's a key thing. So if you don't have a metadata catalog, you can't keep track of this complexity when you had one platform was one thing but as it's the complexity is kind of spiraled in the last 25 years, you need the catalog to keep track of it but really that's a base of how you can add all these different value sets. So Charles, I wonder if we could talk about automation. Sure. You know automation obviously is hero, automation that's a good thing but a lot of times customers say, ooh, automation. I'm afraid of giving control to a machine. So talk about automation, sort of the state of where we're at with automated management and where the catalogs fit into them. Sure. So automation is the important benefit virtualization brings. In particular in storage, we introduce something called storage policy based management. This is allow you to, when you provision your VM you can specify what type of SLOs that you require from the storage component to support this VM. As opposed to traditional way where the storage management is sort of separated from the compute management whereby SPBM storage policy based management we combine the two and let the storage management to be driven by the application by the VM side. And that's the important component of our software defined data center and software defined storage vision and I believe catalogic shear that vision where a lot of these automation can be enabled by the software. So the unit of granularity for policy based management is the VM? It's the VMDK, the virtual disks that are attached to the virtual machines. Yeah, okay, and I wonder if you could follow up. Just talk a little bit about VMware storage strategy. You announced? Sure. VSAN, last year you announced Evo Rail and then followed that up with Evo Rack and create a lot of buzz. The whole hyperconverged thing is taken off. How would you summarize VMware storage strategy? So our strategy is software defined storage and hyperconverged infrastructure. VSAN was shipped 18 months ago. It's got over 2,000 customers. It's the most deployed hyperconverged solution in the market today. And in fact, there are more units of VSAN deployed than any other hyperconverged solution. And our vision is to allow customer to standardize data center with the same hardware and enable the storage functions by the software from VMware and from our partners. Okay, so, okay, so you hear that? Yeah. That's probably music to your ears, because you're not selling an array. Right. Okay, so from your standpoint, and you hear what Charles just said about the VMware storage strategy, and then you heard the keynotes this morning about hybrid cloud, where do you see catalogs fitting in midterm to longterm? So again, hybrid cloud just adds more complexity, but it has a lot of power. So a lot of things that VMware's doing to make it seamless to go across those environments and powerful, what we do is give you the catalog to see what you have as far as copy data in the environment, correlate that what you do with the VMs or the application groups, and now it's actually more powerful. In fact, when you go hybrid cloud, having a catalog, understanding it, is the critical piece to keep in control of it. And then the automation pieces, you have to understand the catalog would also tell you things like location and lineage. You understand what the production data set is and the copy of the production set. You understand what physical locations those are in, even if it's hybrid cloud or not. Having that knowledge, that allows you now automate in a much more intelligent way and do very interesting use cases. So the catalog's a key piece, but it's all the enablement that goes on top of it really gives a value because it simplifies. You hide that complexity and allow people to just consume how they want to be consumed, either an app user or the storage IT guy. Without dumbing down things, all the high power that you have in your environment, you can be as customized, but you can simplify it for users. And the point of control for what you described is in this world, vSphere? Sure, vSphere, but also the public APIs of any of the storage platforms that you're currently running. vSAN, but also IBM, NetApp, VMware, vSAN, EMC in the future. So it's wherever the customer wants that control to be. Right, exactly. And we believe the data center will be a hybrid environment, in the sense both of hybrid cloud as well as the storage will continue to see arrays for a long time. So it'll be a lot of arrays from our storage partners, but there'll be increasing amount of hyperconverged storage in the environment as well. And the beauty of software defined storage, you can manage both of them with a single policy. Okay, so you're not going to get into the hardware business, right? You guys are staying a software company, so where does, I think, thinking from a customer standpoint, I've got all these choices. Where do I, and this certainly gray area is allowed, that's cool, but generally speaking, if we can do that, generalize, where do you see the fit for your vSAN versus say the array-based solutions? Sure, so vSAN is a new solution. It starts with three strongest use cases, namely VDI, virtual desktops, the remote offices, branch offices, as well as test dev use cases. That's what we introduce a version one of vSAN. Now with version two that we shipped in Q1 this year, we're extending it to tier one mission critical production apps. In fact, from the latest customer survey, we found that quickly become the number one use case by our customers. So vSAN has quickly stepped up to really addressing both the data center use cases as well as continues to be a great solution for the user's VDI environment. So why do I need an array? No, I mean so, I know there's a spectrum of mission critical, right? But is it largely because I've got processes around that array or those arrays can do things that is not going to do with vSAN? Where we still have a gap is the completeness of data services, where traditional arrays has been developing those data services for 15, 20 years. A storage stack. The storage stacks, the various deduplication, for example, compression, encryption and various data services. And those are the areas that we are still working on. We're actually previewing a beta version of our software in Q4, that's going to introduce in a dedupe capability as well as the erasure coding. So we still have a little way to go in terms of completing our data services, but customer is finding vSAN to be a very robust and performance solution for their enterprise use cases. So dedupe is going to, you know, the data reductions, you know, solve the economic issue and then the other services that you build out will take some time, but it's your strategy to continue to add value in that space, right? Right, right. And I think the key is no matter what customer chooses, whether they pick an array or whether they pick a hyperconverged solution, they can be all managed through the same automation layer, which is our SPBM. So through SPBM and vSAN and vVol connecting to the arrays, you can have a single management playing for this mixed environment. And Ed, what's unique about CataLogic? Well, I think what we do is we're very complimentary to what VMware is doing. Everything you just said, we do exactly the same thing, but we focus on the specific issue of the copies that are being created. What's unique about it is we actually don't make you change your storage. There's other solutions that make you take your copy and make another copy of it to solve your copy problem. We look at the specific issue and give you the, what I'll say, more holistic solution to it, but we give you the flexibility and openness, just like VMware just kind of is a software-defined copy data management. Download in 15 minutes, don't change what you have, and I can give you all these great use cases. And it doesn't matter what you have or how you evolve what you're using underneath the covers, it doesn't matter. The same workflows, the same policies, the same single-painted glass goes through. And so you've announced for VMware, you mentioned IBM. And NetApp. And NetApp. And you'll see more. So basically we started in February with one storage provider, and now we have nine. You'll see us very easily go across the rest of the infrastructure. So there's nothing architecturally that limits you from doing that. And you as well are a software company, you're not planning on. 100% software, in fact, that's a differentiation. Some people are using the term copy data dimension 2.0. It's like all about in place. What you currently have, don't move it. Let me give you the flexibility that simplify those workflows across it. And have ISVs started to sort of pick up on this and give us the update there? Well, MSPs for ISVs as well, but people are looking for, how do I get control? The metadata catalog is rich, so we're seeing a lot of different people saying, boy, if you have that metadata catalog, how do I get after it and leverage for analytics and other use cases? But the biggest use case we see is people trying to get on top of their OPEX and CAPEX in their enterprise hybrid cloud. And in almost all cases, we're there with VMware. So metadata. Charles, are we going to see a day where we have more metadata than data? Is that take over? Are you there? I mean, it's really, I mean, we never used to talk about, but we used to talk about metadata, but the public didn't until Snowden came out. But now it's like on everybody's mind, but it's true, there's so much data about the data. And that's where a lot of the value is, right? Where does metadata fit into your storage strategy? Well, metadata is data about data, and that's actually the key pointers to where your data is. I don't actually think the volume of metadata will ever exceed data, but without metadata, your data is useless. So that's certainly really the backbone of your data infrastructure. All right, Ed, we'll give you the last word.  Give us the bumper sticker. I couldn't say any better. So we're excited to be here. It's exciting for us to see kind of the adoption of the market, a copy data management. In fact, people come out and buy the booth and call it the new buzzword, which is great. But in general, it tackles a really big prompt for clients, and we do it in the most easy way for people to consume. It's an agentless download. Don't change what you have, and you get these great benefits. So it's exciting to see things grow and really take off. Well, congratulations, Ed. You have a knack of finding these companies that have interesting technology, great ROI. So thanks very much for coming to theCUBE. Thank you. Charles, good to see you. All right, keep it right there, buddy. We'll be back with our next guest right after this. This is theCUBE. We're live from Moscone in San Francisco. Right back. Thank you. Thank you.


Hi this is Julia and welcome back to my channel and for today's video I'm going to be talking about some series that I need to finish. I have five here to share but let's get into it. First up here I have Girl of Nightmares by Kennar Blake. This is the sequel to Anna's Rest in Blood. This is a YA horror series about a ghost named Anna and a ghost hunter and they kind of like each other, they kind of fall in love sort of thing. It's not as cheesy as that. The problem is book one was actually really good and yes so I need to get around to book two. I was supposed to, I was going to read it during Halloween and then I didn't so I'm like okay I'll wait. I don't know when I'm going to read it though but I really want to read it. Next up here I have the Spenster Club series so I'm actually currently reading the third book so the first book is Am I Normal Yet, How Hard Can Love Me and What's a Girl Got to Do and this is the 3.5 which is Anna Happy New Year. This is the one I just had in my room at the moment but yes I'm currently reading the third one which this is a mature YA feminist romance kind of series. It's really wonderful. Book one deals with a character who has obsessive compulsive disorder. It's such an amazing series. I love it so much and I'm currently reading the third book again but this is the 3.5 so I want to finish up this series just because it is really good but then I'm going to need to buy more of her books because I think she has one more book out that I haven't bought yet or checked out, whatever. Here I have the Raven Quartet by Maggie Steve Otter. This is actually the fourth book I'm holding up but I've only read the first book, The Raven Boys, which this is like a YA. I haven't even described this series. Supernatural-esque fantasy-ish. I don't really know how to describe this series but book one was amazing. The characters were amazing. The writing was beautiful and I just haven't gotten around to picking up book 2 and then this covers one of my favorite covers of all time because I love Dears and Stags and the whole shebang and this is just beautiful to me. So I'm super excited to finish off this series. I don't know when it will happen because like recently I've been bad with series but it's fine. So next up here I have Harry Potter. I still haven't finished this. My goal for 2017 was to finish the last three books which is order of the phoenix half blood prince and then death of hallows which I did not do this year. So maybe next year? I don't know. I love Goblet of Fire. I love Prisoner of Azkaban. Chamber of Secrets was fine. The first book was good, yeah.  My poor books. But I still haven't continued. I think it's mostly because this book and chip it needs to be for some reason. Like oh I could read it but I can't read Harry Potter in the order of the phoenix but I want to read it. I just have lacked motivation to pick it up because then when I pick them up I know I'm not going to be able to like stop reading them so then I'm just going to marathon them but like I need a good amount of time to do that and I want to like dedicate my time to them. So what kind of see? But yes I still have not finished Harry Potter yet. I've read the first four books in the series so far. No the first three not four. But not least I have the Vampire Academy series by Rochelle Mead. This is a very fun YA paranormal series fantasy romance but they're actually very good books. I've read the first three so I have the last three to read. This is just book six that I'm holding up. Again it was, I have my books stacked at the bottom and it was on the top so I got this one. Book one it was good. Book two was really good. Book three was a game changer so I haven't gone around picking up the fourth book yet. Again because I won't want to stop reading them and I want to dedicate enough time to them. So there you guys have it. Those were the series I need to finish. Let me know some of yours in the comments down below. I hope you guys are enjoying all the blog and this videos. Let me know down below and if you want to follow me on any other social media platform my Twitter, Tumblr, Instagram, Goodreads, Pinterest, the whole shebang is all linked down below and yes thank you guys so much for watching. Bye.


Hello everyone. Today we will be discussing about implementation of MQDT and CYB protocols. Here is the learning outcome. By the end of this session, students will be able to create MQDT broker and client to publish and subscribe to topics and receive messages. Here is the outline of this session. I will be first of all taking you through an introduction of Cloud MQDT broker. What exactly is Cloud MQDT broker and by relating it with one of the previous examples what we have seen in our earlier video and then I will show you how to initialize a broker and it's a client package by using Google's Chrome package called MQDT Lens. So it's a good moment here for the students to pause and think about how and think on how a client communicates with another client in the IoT scenario whenever we are employing MQDT protocol. So the solution is as we have already seen in the earlier video here we have a broker, a central broker which is surrounded by three clients as we have seen. If client A wants to sense a sort of temperature then it will be sensing it and it will directly send the message to broker. So here we generally refer this particular process as client A has sensed the temperature and it has published the data to broker. So now depending upon which other clients like client B and client C have actually subscribed to the temperature topic will only be receiving the data. On the other hand some other clients like client D who are non-subscribers I mean who didn't subscribe to the topic called temperature won't be sending any messages from the broker. So let's have a detailed look at how to initialize broker and what are the roles of broker. So basically the role of broker is to manage the protocol as well as the incoming and outgoing messages. Generally we call this message sending activity as a publish and whenever a particular client is getting some sort of message you know whenever it subscribes to a specific topic is known as subscribing. So in this case so let's have a detailed look about Cloud MQT. Cloud MQT is basically a hosted message broker for Internet of Things and as you are able to see we have a producer, broker and consumer. Like in the previous slide client A was actually a message producer which was then published to the broker and broker has taken care to properly publish the data further to those clients who have the role of subscribers and whenever we say that a particular client has subscribed to a certain broker it happens through an ID called topic. So this is a mechanism of identifying which people or which clients in the network are actually interested to get the message that is being published. Now let's have a detailed look at how to initialize MQT broker by using by browsing to the website called Cloud MQT. So here I am opening a website called cloudmqt.com. Here as you can see first of all you are supposed to log in so let me quickly log in and I have already mentioned I have already input my credentials so that I have already logged into this session. Now once you enter to this particular portal all you are supposed to do is click on list all instances if you are already created one or if you are trying to visit this for the first time then simply you are supposed to click on create new instance. I have already created it once so let me show you quickly how to create all these things.  So as we are already logged in I have already put my credentials and I am able to log in to this Cloud MQT server and if you are trying to log in to this website for the first time you are supposed to click on create new instance and make sure that you have given a suitable name to this like I have given the name called IOT and then select the term I mean the plan as cute cat free because this is the only plan that is available which is offered free of cost on this website called Cloud MQT. So I will be going back and I will simply click on the instance that I have already created for this session. If I click on this name of the instance once it loads you would be able to see a couple of details which we will be using. So this is the current plan that we are using which is offered free of cost by this Cloud MQT based server. Now there are some important details that we are about to watch here that is the server address is what we generally refer it as address and the username and password is what we need to log in to this particular broker and then have an access to send messages I mean publish and get the things done. So the four important information so the four important things that we are supposed to focus generally is the server name there is this entire tailor.cloudmqt.com of course the username and password are the credentials which we would try to mention in our clients and of course the port number is one more important thing which will make sure that no two instances are getting clashed together. So along with this we so with this I will open a small chrome Google Chrome extension with a name called MQT lens you can easily go to Google Chrome web browser and install this. Once you install and open this the reason why we are using this is it can be easily used for publishing and subscribing to certain topics which are already live. So let me quickly show you how to put the details. So I'll first of all copy the address from cloud MQT server and give this a proper name like test then I'll paste that address over here now I'll copy the port address now I'll copy the port address and I need to enter username and password so simply copy paste these things and you may put it here. So what we are trying to do is currently we are trying to configure a MQT client. So this client would be connected to this MQT cloud and cloud impurity broker that is hosted online and we are trying to use this cute cat plan of its variants. Now once you do this simply click on create connection you should be able to see a green content like this otherwise if you don't put proper details then probably it will be showing with the help of some red color. Now let me first of all initialize a client here with a specific topic let it be temperature. So I have a client who is trying to subscribe so as you can easily see I have a topic called temperature and I have subscribed to it. Now this particular entity I mean the lower entity below this published heading is nothing but what the broker generally does. So if I post some data like temperature maybe 30 degrees and if I click on publish then this particular subscriber will be receiving that particular information. So this is how the data is transferred from the broker if it is published with a given topic name otherwise it can't. So on the other hand if I type temperature one to which nobody has subscribed I'll be clicking on subscribe now sorry I'll be clicking on publish now and let us see. So that message is sent to nobody. So this is how things often work in the back end with the help of a cloud impurity we'll be getting into the details like what are the various quality of services offered by MQTT. Here are the references used for this session. Thank you.