Hey everyone, I'm Rajiv Dharazi and in this video I'm excited to bring back our very special guest Mark S. King, whom we sat down and chatted with earlier in the year, but this time we'll be discussing his new book, officially released today. The book is titled My Fabulous Disease Chronicles of a Gay Survivor. About Mark's book, Sean Stroop, author of Body Counts, said if the AIDS pandemic had a Mark Twain, it would be Mark S. King. And Peter Staley, prominent activist and author of Never Silent Act Up and My Life in Activism, said start with queer attitude, add a spoonful of humor, camp and or dark and top it all off with a heart of gold and you'll still be missing some secret ingredients found in My Fabulous Disease. Mark's writing is a diary of survival and a beautiful example of giving back. I know his words have helped me over the years and he has my thanks. Bon appetit. My Fabulous Disease is also the name of Mark's award-winning blog, which I highly recommend signing up for so you can receive those posts via email. Just visit www.marksking.com and I'll have that link below in the description box as well. To recap, Mark S. King is an award-winning blogger, author, speaker and HIV AIDS activist who has been involved in HIV causes since testing positive during my birth year 1985. And he's won numerous awards for his work. If you haven't seen our previous interview in which we got to know him and his story, living through the early days of the AIDS epidemic, talking about addiction and aging with HIV, I'll put up a card here so you can watch that as well. Mark, welcome back. So happy to have you. Thank you very much. Rafe is so great to be here and see you again. How are you? I'm doing wonderfully and I see that you are in your very beautiful new home. Congrats. Thank you. We moved. Yes. Thank you very much. Yeah. I can pick up the computer and give you a tour all around. I have a great bathroom if you want to see it. We'll have to reschedule for that one because I really want to get to your book. All right. Okay. Will you tell me, let's start off by going into what inspired you to put this book together? The same thing that's always inspired me, I guess, and that is just to tell the story, right? Of those of us living with HIV or all of the aspects of ourselves because I never want to reduce us to just that, of course, our diagnosis or even the fact that I made it out of the 80s alive. I want to make sure that we cover all aspects. And so there's like, there's five big sections of the book and only one is specifically devoted to HIV. The rest is about well addiction, but family and love and sex and a lot of sex in the book, I gotta tell you. And so, yeah, what's inspired me is to tell the truth and have some fun along the way, do it in an entertaining way. And was this a goal that you've always had in mind, putting a book together or did this kind of just come organically later on? You know, I am certainly immediate gratification in terms of what's been great about the blog is when I write something, I don't have to wait for an editor and for a publishing house and then a year later, you get to read it. I just press a button. But it's also true that over the years and this in the book represents four decades of writing over the years, there's been some pieces that are really near and dear to me. Some of them are very funny. And I didn't want you to have to scrounge through 40 years of my blog to find them. And so I have collected them from my site and from magazines, the advocate pause magazine, others other websites that I have contributed to and put them all very conveniently for you between two covers. Amazing. And I'm so glad you did that. I absolutely cannot stress how much I love Mark's book and everything that he and we'll get into that right now. Okay, so I want to start with I'm going to start with some excerpts because I took a bunch of notes. I hope you don't mind me revealing just little snippets here and there that I want to by all means reveal. I'm an open book and and and to Mark's credit, I haven't given him any of the talking points. So he has no idea what I'm talking about here. Okay, you said there was a time when old friends called to say goodbye and by goodbye, they meant forever when all of us had a file folder marked Memorial that outlined how we wanted our service to be conducted when people shot themselves or jumped off bridges after getting their test results. It's very clear from the beginning of your book that we're going to read what we're about to embark on what we're going to read will be brutally honest. And it's a bit shocking and also and also in a way like an invitation to to really understand in a different way that time and in a way that we often don't really get insight to. You know, I thank you for that. I I want I feel like a lot of people know the statistics so they know intellectually what happened. Oh, there's this thing that happened and it caught us all by surprise. A lot of people died and it was really bad. I want people to know how it felt. And when I that quote there, you know, it is is completely true. I would get calls at night and the phone would ring and if the phone rang after 11, someone was dead.  And that's the irony of it because that's who we were at that time. We were elderly. In other words, we had as much death commonly as would your grandmother and her friends, you know. And then the memorial thing is also true. I had my, you know, it's funny, I haven't updated it in a while, which shows you the fact that things have gotten better. But I would keep it updated and thank God that I'm still alive because I have so much more content for my memorial in terms of video. I might show a clip of this. Who knows? We'll see how it goes. We'll see how you rank.  And I haven't updated it in a while. I have a feeling that it's going to stay tucked away for a while longer. Well, good. I hope so. I also noticed very early on that there is a constant tension between the immediacy of what was happening in the 80s and how important, traumatic, devastating it was. Contrasting with the present moment and life kind of just continuing on, life is indifferent, and it just moves forward. You mentioned regarding the term long-term survivor. I quote, I have misgivings about that unsettling designation because it doesn't speak to my other parallel life experiences and it suggests a dismissal of my relevance in the here and now. I mean, that's true. It's funny. On the one hand, I've got HIV tattooed on my forehead, man, because it is what I do. And so it is the first thing people know me for and I'm okay with that. All right. Made my peace with that because it's kind of my vocation and that's all right. I guess what I'm saying there is just reducing me to that doesn't take into account all the other episodes that you're going to read about in the book about sexual misadventures and falling in love and my family dealing with a very kind of outrageous gay son, all of that stuff. I think I'm doing myself an all-long-term of survivors of disservice if I am only talking about that and I don't paint us with a broad brush in terms of all of our other life experiences. I've gone through a lot of shit, right? You know, it has nothing to do with HIV. Yes, I agree. And you bring up a really good point because I've had people actually say directly to me in the past when I kind of showed that my content was focused heavily on living with HIV and they're like, well, you don't want to be pigeonholed as someone who is the HIV guy. And there's so much more to that. And I've kind of wrestled with that a little bit and gotten back and forth because I think, yes, I am. I am so much more than that. And I have so much more to offer and give. But in the same vein, I'm kind of being called in this way. And so what if people see me as that person? You know, it's an immutable characteristic about us. And it's a character trait as much as my being a redhead. Or you being, what is that, Burnett? Whatever you want to call it. The fact that there are other aspects of you, you are a natural bodybuilder. I am not. But the point is, there's a lot more. You're right. And you know, there are worse things, I guess. In other words, if people need a shorthand and they go, oh, Mark, he's that funny guy with HIV, you know, that's fair. It's fair. That's okay. And I don't feel any stigma from that. If they want to reduce me, so that's my elevator pitch. Well, I write these funny nostalgic pieces of many of which are about living with HIV. That's fair. That's pretty much, you got it, you know. In other words, I'm not going to soak in any of the stigma as a result of that. You know, what the famous quote about no one can make you feel badly about yourself without your permission. Yeah. And you hit, I think you hit the nail on the head by mentioning stigma because I think that is subconsciously what is driving people to say that because when we hear about an economist or a prolific historian or something, we don't go, oh, you don't want to be the guy that's known as an economist. You're so much more than that, right? It's like, this is the same thing. Why is this different? And we are both in arenas. We are both in this particular arena in which we are excelling. And by that, I mean, we are in kind of a media landscape where we aren't afraid to put HIV forward. And we're doing it successfully and with meaning and intention. And that's great. Good for us. Okay. In another essay entitled Once When We Were Heroes, and for those of you who actually, let's take a step back. So this book is a collection of essays over 40 years, correct? Yes. And so I thought, I was surprised because I didn't realize that that was the structure of the book. And I thought, this is so great because you can sit down and curl up into bed at night and read an essay and then have so much to kind of soak in and think about. And it's over. It's like, I always say, I like to do what I do in about 800 words. I want to tell you a story and make a point and goodbye. So it's perfect reading for anyone who doesn't have a long attention span.  Whatever the circumstances are, it is they're bite-sized. They're easily digestible. But within them, there's going to be some stuff. And what I like about it, about the structure of it, is when you turn the page to the next one, you have no idea what you're going to get. It may be something sweet and nostalgic. It may be scary. It may be very funny. It's there's no talent and you'll have to turn the page and find out. Okay. So back to this essay entitled, Once When We Were Heroes, you speak to the bravery that existed during the early days of the epidemic and how bravery in your experience does exist today, but nothing like it did then. And how, quote, you said, your most courageous self, the best man you'll ever be, lived more than two decades ago during the first years of a horrific plague. It sounds like it gave you an incredible sense of purpose, all that tragedy, having to survive moment by moment and help others survive and sometimes pass away with some sense of dignity, one moment to the neck and how it grounded you in the present like nothing else. Almost like what you would hear from someone who had survived a war. I love the honesty of admitting that something so horrific also gave you a visceral sense of purpose and made you feel like, in your words, a hero. I don't think that's an easy thing to admit. None of us wants to admit we gained some sense of self-satisfaction or meaning from a tragedy. It's not politically correct. There's an expectation that we would only view that time as something very negative. But what you're describing is something I think is very human and very real. Can you speak to that a bit? I think heroism is what you do when you have no other choice. Often, I don't think people just say, I'm going to go be a hero and I don't think it's premeditated. I think it's circumstantial. I pulled the idea out of the burning car because I was there. I had to. I feel as if, yes, the best man I will ever be existed during those horrific years. When I stepped up, when I faced the things that terrified me most, death, dying, disfigurement, all of these things that came along with AIDS, because of our response to it. The most you can ask about life and your own behavior is how you respond to things. It's not like, oh, this terrible thing that happened to me. It's how did I respond to this thing that happened? I think that we behaved, we responded heroically and with incredible compassion for one another. Especially when the odds were stacked against us and a lot of people didn't care and a lot of people wanted to be done with us and quarantine us and not deliver meals into our hospital rooms and all of these terrible things. Despite all of that, we behaved admirably and did great work. I will say this though, tragedy is not a contest and younger people today are going to have their stuff, whatever it is. They're going to have their stuff. I have absolute faith in whatever that is for you, Rafe, for the next generation. They're going to respond wonderfully because I've seen the very best of human spirit. I've seen the very best of humanity and we stepped up and we did it. That tells me that you can do it too. This is not all about work. We grate. It's wow. Humanity. Humanity. Look what we're capable of when we're backs are against the wall. It gave me faith in humanity and that's shared with all of us. Again, we had no other choice. It was a situation where we were called up. We were called to do it. There will be other things. There will be more situations. For that matter, I think that this is a very dangerous time we live in right now socially, politically, etc. It's very dangerous and it's going to take a lot of that sort of courage. It's going to take a lot of people standing up going, whoa, I draw the line here. We're seeing a lot of it. We are seeing a renewed excitement and strength among women having agency over their own bodies. We are seeing enormous new energy amongst young people about climate change and about the world that is being handed to them and they're not thrilled. There are many, many challenges ahead. At the end of the day, I have faith in people. I think it's rough. I think these times are rough and maybe it's harder today because the enemy is at war. The thing we're fighting maybe it isn't as, it doesn't feel as, I think you used the word immediate. In the 80s, it was immediate. There's my best friend. There he is in bed dying. That's immediate. I can see that. It makes me angry. I want to go do something about it. Things like climate change. Well, the latest brush fire that kills people or the latest megastorm, maybe that's immediate enough for people to rise up. I think that we're seeing that. And like you said, it's born out of necessity. Yes. The flip side of that, isn't that right? That is, heroism is when you have no other choice, meaning it's only until we absolutely have to that we say, okay, enough. When is that point? It's a bit human nature and that's what will hopefully drive us to rediscover our humanity because I think that's been lost along the way. There's so much cynicism. There is, okay, I'll get, can I get a little political and say this, back in the day, in the early 80s when we were facing AIDS and all of that, there was a lot of ignorance and stigma and homophobia and all of those things about gay men who were getting, bearing the brunt of this new disease.  There weren't a lot of people out in the early 80s. We didn't have shows on TV. We didn't have movies that were showing positive characterization of the LGBTQ people. So there was a lot of education to do just so they would see us as worthy human beings. What's happening today is willful ignorance about who we are. What's happening today is so much more devious than then because when people are discriminating against us, when they are throwing hatred our way, it used to be out of ignorance and fear. Now it's out of political expediency and just this devious hatred because of being, I think it's still driven by fear. Oh, you're going to take away something from me that I have. I don't want to share whatever that is, rights, who knows, whatever it is. And so I think this landscape is more dangerous than the landscape I came of age in during AIDS. It puts it in perspective and it makes me so happy that like every third essay in my book is funny because we go there. I go there in terms of those dark years of the epidemic and helping you understand how it felt. But then I want to give you a break. I want to, okay, let's laugh because I got this hilarious story about shopping for socks in the mall with Larry Kramer, the great AIDS activist, or all the times I used to be in the health clinic when I was a tot in West Hollywood before HIV came along. And we were all just having a great time, getting busy on the weekends and then come Thursday we would have to visit the clinic. I used to say I got the clap so many times I called it the applause. Well, and isn't that life, it's not all doom and gloom. It's all not one note either. It's very, you're a three-dimensional human being and I think that you expressed that very, very well. Okay, I just want to, before we move on, I do have another follow-up question and that is when you say that you're the best manual you'll ever be lived more than two decades ago, what does that leave moving forward? Because I think that this is a very relevant question, not just people who survived the AIDS epidemic, but anyone who is professional athletes, people who have like risen to the occasion, risen in it during a tragedy at some point in their life, and then have to live, go about living the rest of their life. How do you make peace with that and how do you find purpose moving forward? Well, you know, I don't feel as if, okay, I did it and now my life is over and I'm going to coast my way through the rest. In other words, first of all, something else may come along and does. I participate in other cause related things. I think all of us are on a search for meaning. We're all trying to figure out what does this all mean? Why are we here? What are we doing? And for me, it's simple. We're here to help somebody else. It's simple as that. Help, help make the road a little simpler for the next person. As corny as that is, it's the truth.  I mean, that's a pretty, okay, so that's high drama. It doesn't mean that I don't continue to kind of what meaning is or my search doesn't evolve as we go along. Okay, yes, I did that. Yes, it may be like the most high drama thing that ever happened to me. But there are simple things day to day. I have friends now that need help for whatever reason. I have, you know, I have friends dealing with addiction and recovery, which I know something about. I am able to help them through that. There might be somebody, there may be a neighbor or a sister or somebody for whom you're going to help. And that's it. That's, you know, we all don't get these front page stories of our die-ins back in the day, you know. It doesn't mean our lives aren't worthy and that our capacity to help other people isn't there and isn't useful. I think that really crystallized that notion really well in my head because it makes me think of even just something we can all relate to is just getting older and how, when you mentioned drama, that instantly makes me think of like teenage years or early 20s. Life is so passionate and intense and relationships are so like at max level. And then as you get older, you realize, okay, like life is experienced not as intensely in a very different way. And it's, it's just as special and it's in a different way. Well, because when you're younger, like you, Rafe, when you're younger, there's still so many life experiences that you're having for the first time. And so your response to it is very heightened and it's exciting or it's horrible or it's whatever it is. And as you age, yeah, it's true that with maturity, it's kind of like, you've kind of seen it all.  It's funny, I used to get all caught up in righteous indignation, my favorite emotion.  I was young and had a lot of energy and it was great. And I invested all of that emotion into that. Today, I am more, I have more of a budget of how much of that righteous indignation that I'm willing to expel. And it's not that it doesn't, that people out there don't need it. I treat it more economically these days. It takes a lot to get me riled up. And it's not that I don't care. It's that I'm older. I've got so much energy. I'm not going to wear myself out. I'm going to be here as a resource for those who are younger and are willing to go out there and do it. And it's also true that in my recovery process from addiction, I have to be careful about becoming unsettled, about becoming angry and discontent. It makes me want to change the way I feel. And I have some real great shortcuts for doing that. So I have to be, I have to be careful. And the attitude I've developed is, okay, there's that thing over there and it's a real outrage. And there's other people over there and they appear to be handling it. I think it's going to be fine. They don't need me. They'll let me know if they do. I will finish watching my Netflix movie. And that's not a cop out.  Jumping into another essay, Surviving Life Itself. You talked about overhearing a woman on the bus who knew someone who died and she was having this kind of quiet conversation with someone next to her. And I was completely listening in. And your thought, your response was, quote, just one. You know, just one person who died, question mark. And again, it reminds me of what I imagine those that come from war or other major tragedies must have felt that perspective. Most of us today could never truly understand. I told you earlier, tragedy isn't a contest. And now here I am contradicting myself because I was kind of putting my life, preparing, comparing my life experience to hers.  Both these, these contradictions can exist in the same person. And most people, they narrate that out. They, they, they, they make it one thing, but it's, we have these contradictions. So thank you for doing it. Okay, continue. You're absolutely right. She was having this conversation that I was eavesdropping on. And she was saying, Oh, I have this friend that died and it was really bad. And she, she started by saying, Oh, I know somebody who died like, like one person, I know someone who died. It was a motorcycle accident and all of that. And yes, I was thinking to myself, one, you know, one person who died, right? And because back then, you know, geez, you know, the number of people I know who have died, even when I was young, was, you know, a commercial airline tragedy figure, you know, and then I realized hearing her talk about it, she was telling all the details about how he died and how people reacted and who went to the funeral and what they said and all of that. And I'm listening to this going, wow, you know, he got a death of his very own. His, his was a singular death. I didn't get that in terms of the friends of ours, because there was everybody was doing it. There were so many people dying at the same time that, you know, memorials were sometimes stacked, you know, over the weekend.  And people will tell stories about him and they'll remember him and he'll remember his, his singular death. And, and it made me realize, wow, you know, how, how nice for him, you know, how nice for him that his, that his family and his parents could really take care of one another and focus on him and on that and on the loss of him, that person. And because we weren't afforded that for a long time.  I'm in my 60s. So death among my friends, my social circle is starting to accelerate. Again, it's nothing like it was in the 80s. It's starting to, it's starting to tick up a little bit, I'll say. Well, and the big importance for me as a younger person, I wouldn't say young necessarily, there's now a lot of people that are younger than me these days. That's right. It's all relative is learning and through your words, experiencing your wisdom and your experience, your experience. And okay, so there's this quote where you said our heartbreaking past is important history that should be preserved. It is not a prevention strategy. Another quote, our influence as long term survivors may be limited, but we can find meaning and engagement as cultural elders and mentors. And it's one thing that our society, at least here in the US, in large part lacks, is valuing age and the wisdom and the experience that comes with age. We value youth disproportionately. And this idea of having and appreciating cultural elders and mentors is not a given. It's something that has to be taught. We need to speak to the importance of that and insist on reintroducing that as a part of a way of our life, not just as it relates to HIV AIDS.  Very tip top of the list of things. And thank goodness in the last, you know, 10 or 20 years, we've started to kind of welcome other type, body types, age types, started to give them cute little names, you know, like Ginger and Daddy. And so I check off two boxes now right away. And thank God for that, you know, as long as we're not using those labels, you know, those kind of shortcuts, the way we've branded people, as a way of excluding anybody, it's a way of including, you know, life is about addition, not subtraction, it's about addition. And so in a way, you know, the bears and the cubs and the puppies and the this and the that, and the daddies and the, you know, if we found a way to celebrate different kinds, that's great, because that all said, I sure hope that I will learn to value myself beyond whether or not I'm physically pretty, you know, or desirable, desirable, because we're telling you, we're getting to the end of that road. And I don't mean that to be funny. And I don't mean for you to say, Oh, Mark, but you look great for your age. I don't mean any of that. I mean that I've had a good run. I was an adorable little twink. And then I became the circuit boy and the muscle gym bunny, you know, I've done all of the stages, well, the stages of gay community. Okay, because I bought into that completely. And to my detriment. But nevertheless, I've kind of bought into how do I need to look what do I need to do as I enter this new stage of my life and now I need to look like this and all of it. And I still do because it's just inherent in the way I was raised in this community. We are we're getting to the end of that road.  By the way, I've let my beard grow out. This usually I have my ginger dye because I am a ginger, but I would bring it back to my original.  The question is, what are my intentions? Do I want to until the last dog dies? Do I want to hope that someone finds me desirable? Okay, first of all, I'm married. He thinks I'm terrific. So we got that. Okay.  But even then, at what point do I say, okay, all right, you know what? I'm just I'm wearing the stretch sweatpants. I'll be on the sofa and I'm good. You know, there's a Facebook page devoted to older ginger people. And they're admirers. I will post on it sometimes if I get a new picture and I in my beard looked really good and I look kind of redheaded. I don't post on it sometimes just some guys will go, oh, woof, woof. What am I doing? What am I doing? You know, okay, that was a quick, quick jolt of immediate gratification. But what am I doing? I am going to be 63 in a couple of months. Will I be doing this when I'm seven? You know, at what point do I say, okay, all right, that's enough. I'm comfortable in my own skin. This is how I look. Take it or leave it because I have all these other things to offer. Well, and to continue on that look, that's exactly the point. How important is physical attraction really at the end of the day? And and the whole point of bringing this up is that I hope we get to a point, especially now that demographically in the US, our older generation is just is ballooning and the amount of young people we have is shrinking. So hopefully we can allocate a little bit of the resources of our attention to older folks and really understanding the inherent value there, which isn't connected to physical attraction. You know, and this, this is going to sound like, woe is me, I'm so pretty. This just get ready because that's how this is about to sound. I feel as if I came of age and walked through most of my adulthood, aids aside and tragedy. And yeah, we're all, you know, there was that too. But I negotiated life as a very attractive strawberry blonde. And I walked into a room and people looked and I got used to it.  And I just got used to it and I just blithely swept through rooms with this sense of kind of, you know, hot privilege or something, whatever that was. And when I say to my detriment, I mean it. And that's where it sounds like I'm complaining because I was so pretty. I didn't develop my friendships as closely as I might have because I was busy collecting chips, collecting, collecting looks, you know, making sure my arms looks really great in this certain position, you know, whatever it was, I was obsessed. And because I saw what I gave me.  And so then now I'm getting all of this attention because I'm pretty, I'll take it. I took it, you know, but then it became an obsession where that's all I thought about.  That's it. If it isn't showing my tank top, I don't work it out. That's it. So I wasn't there for health. I was there for narcissism. And I feel as if in the last, you know, I'm 63. I feel like as if in the last 20 years, I've had to play catch up in my personal relationships. I've had to build better relationships with my family, better relationships with the friends that I have who have either survived or stuck around and spend more time just, just paying attention to them and listening to them and not always looking over their shoulders. See, who else is here that likes me? You know, I hope the right people are here are watching this and hearing this because I think there's a lot of people that can relate to that. And, and hopefully that will inspire some people to like reevaluate maybe their priorities as as they're getting older or even being young. And, and I know I have to put this delicately. Those friends I've had that didn't enjoy that sort of adoration who enriched themselves through meaningful careers and reading and the development of personal relationships with people, you know, those few friends that remained my friends with me, you know, thank God. It's almost as if I got to a certain age and they went, well, welcome into the room, Mark. Oh, finally, you're going to pay attention to life and culture and friendships. Are you done being pretty? Are you done? Can we move on? And yes, I've moved on. Okay, you also mentioned in that essay, feeling unwelcome as long-term survivors in the modern advocacy movement. Can you speak to that a little bit? What makes you feel that way? You know, it's funny. I wrote that piece about 10 years ago and much has been improved. We were kind of the afterthought because either you were focused on preventing new HIV infections. So everybody was focused on that, you know, among people who were negative or finding more and successful treatments for people who were positive. But for those of us who were aging, it's funny. We're like the guinea pigs. We are, we are the generation that started out where, you know, I was diagnosed in 85. There weren't, you know, treatments for 10 years. Wow, I wonder how long he'll live. Let's see. And they studied us and, you know, and then, oh, these new drugs came out. How long will he live now? You know, we've always been examined in that way. And, and now they're like, okay, well, now Mark 63 and he's been on these drugs for a while. I wonder how long until his, he gets osteoporosis or heart disease or these other things that tend to happen to older people with HIV. Let's find out. You know, in other words, after all these years, we're still the guinea pigs, long term survivors. We're still the ones being kind of examined closely. And I'm okay with that. I'm a lot better about it than I used to be. It's like, you know, and again, this is maturity. Okay, well, they're going to learn something about me and might the trajectory of the rest of my life, that's going to help the people coming up. You know, I'm good with that. And speaking with long term survivors, I, and folks hearing, seeing comments and DMs online, I've noticed that there is a desire and a need for hearing more of these stories and experiences such as yourself through the 80s epidemic. But I've always kind of struggled a little bit and been a little bit timid and afraid of being perceived as exploiting the stories. Do you have any advice for that? Because I know that it's important and I should, but I also don't want to be that guy that's like, tell me all your juicy hardships. You know, it reminds me, I got a new therapist about, I don't know, I don't have many more, but I had was I had had a first visit with a new therapist about five years ago.  He was so excited. He wanted to hear all about it. Oh, tell me about the pain of that. I'm like, no, no, no, no, you got the wrong guy. I'm good with that.  If you know he's a long term survivor, you're naturally interested. So I'm not offended by it. And if you're interested enough to want to tell our stories or hear it from somebody, I don't feel like that's exploitative at all. As long as you're treating them respectfully, like a whole person, you know, it's like, you don't want to objectify anybody for any particular characteristic and ignore all the rest. So go for it. Just be respectful. Okay. Good, good succinct words. I appreciate that. I actually have a lot, I have a lot of more notes that I wanted to get to, but you and I can gab easily for so long. And I know you have a very tight schedule. So I propose maybe in a few months from now, after I've read the rest, so that we you're not just covering HIV as well, we can do this. Any time you want, I enjoy these conversations very much. And it's exactly the sort of intergenerational stuff that we've both been talking about.  In other words, we always want to oversimplify what it is, you know, as opposed to maybe we're just friends. Maybe this is that we could talk to each other in an intimate way without it being reduced to something else, something as lazy as sex, right? So I enjoy these very much. And let's do it again, whatever it works for you. I'm so happy you said that. And it reminded me of something that I thought about recently, because when I was late teen and exploring my sexuality, I went, I discovered that there's a gay beach in Southern California in Laguna Beach. And I would drive there as often as I could because I had no other gay experience. And I found when I went there, there was all the really young, hot, sexy guys in their little, like, cool, popular groups milling about on the beach. And then there was also this big setup. And they were always there, same guys, much older, upwards of 80 years old. And they would play volleyball and they all congregated together as well. And I found that I was so much more comfortable with these older men. And maybe on some level, they did ogle me a little bit. But by and large, it was very respectful. And they were very kind and friendly and accepting and mentored me in a way. And I felt so comfortable that I would come back every time and I would go, and it wasn't about sex. But I found out later on, as I met some of these younger folks that they all just assumed that I was just some, like, sex slave to these dudes. And that I couldn't possibly have a meaningful friendship with these guys that were older than me. Okay. So as I'm starting to wrap up here, I wanted to ask, what are you hoping that people will walk away with after reading your book? They will walk away with a sense of pleasure, a sense of satisfaction, because so much of what they will have read includes them. Includes them.  There's a part there that I really related to, which I've been hearing, by the way, from, oh, I have a friend who's Mormon and married and has many kids. And he read the book and he's like, oh my gosh, this is so hilarious. And this happened to me too. In other words, the best I can do is try to reveal with honesty about myself and hope that you go, oh yeah, yeah, I know that to be true. So much of life lessons are universal. And that's the universal nature of writing, the kind of writing I like to do. So that's it. Just a sense of satisfaction. And then, oh my gosh, this is so great. I need to buy copies for all my friends. Absolutely. Are there any future works in mind? I'm going to keep doing exactly what I'm doing. I just posted on my fabulous disease yesterday. I will continue doing that. I love it as an outlet. I love being able to write something and just press a button. And bang, you read it. I'm so immediate gratification. It killed me to write a book and have to wait for it to come out. Okay. And then from our last video, I did have, well, it was a couple people that asked a similar question, which is they wanted to know, credit to you, what is your daily routine because you look so healthy and so strong for your age? Well, thank you.  And prior to it, I trained for it like an Olympic event. I was training every day.  I have not been back to the gym since the day of that photo shoot. And A, it's because my back started going out. And I don't know, now I feel like the guy that doesn't look like his photos. But to answer your question, I think a lot of it is positive mental attitude. I think that you're more attractive when you smile. Oh, that sounds like I'm telling people to smile. What I'm saying is for me, I'm happy to be here. And I have a sense of happiness and purpose. And I think that's what they're seeing. Otherwise, my routine is regular household stuff and feed the cats and get to the grocery store. And now that I'm in physical therapy for my back, as soon as I get that worked out, I will be back to the gym too. Maybe I'll work on my core. I hear there's this thing called your core, Rafe. This might be important for you to know. There's a core that helps you bend over and pick up things when you get old. And you need to work on that. It's one of those things you can't see while wearing a tank top. That's right. That's right. Well, it turns out that physical therapy, they're telling me I need to work on my core. And you're right, you can't see it.  But I will work on it. So that's my normal day is very mundane. I promise you, other than the cats and the husband and the snuggling. Okay. Is there anything we haven't discussed today that you'd like to talk about? Not at all. I look forward to talking to you again, Rafe. I really appreciate it. Okay. Well, Mark, thank you so much for agreeing to sit down with me to discuss your book release. I will have links to your website, to your blog, to your link tree, your Twitter, your Instagram, Facebook, all the things in the description box below so anybody can find those there. Everyone at home, please comment below your thoughts, comments, and questions. Do not miss checking out Mark's book. Do not miss it. The digital version is only $5.99. That is a steal. That is so awesome. Otherwise, you can get it in paperback for $19.99. Mark, thank you again, everyone at home. Thank you so much for watching. Be sure to like, subscribe, and hit the bell. So you get a notification every time a new video comes out and share this video with people who in your life who might find this information to be valuable. If you care to donate in support of this channel, you can send me a super thanks below. As some of you have done, thank you so much, or there's a new PayPal link as well. Until next time, cheers.


This episode brought to you by healthwithdronetech.com. If you're familiar with collagen and it's role in aging, then you probably know that its production decreases 10% in our bodies every decade. Users including myself experience a more youthful appearance, decreased wrinkles and smoother skin within days of taking this amazing multi-collagen. It promotes effective anti-aging through the use of 5 types of high quality collagen mixed into one. Try it today for 51% off by going to www.healthwithdronetech.com or by visiting the link below. Make sure to do it within the next 24 hours and get 51% off. And a battle over the pledge of allegiance erupted in Silverton this week. That says Mayor Shane Furman suspended saying the pledge and that led to a testy exchange with town trustee Molly Barela. And it's removed from agendas and our protocols until such time that we can discuss this at a board retreat or workshop. We already discussed this as a board. Any other unilateral decisions we need to know about? If you'd like to find somewhere in the code that does not permit me to do this, then I welcome that discussion at our next meeting. Yes, but it's just been done for a long time and we all took an oath. And we as a board collectively decided it would be done. This is not up for discussion at this moment, but if you'd like to add it to the next video, you can do that. Thank you. You are welcome. Then during the public comment period, an individual said she wanted to recite the pledge to board members and a handful of attendees stood and recited it, prompting Furman to say that we're out of order. Hey, hey, welcome back, Patriots. I'm DroneTech, and today we're going to take a look at what looks like a slow motion Maoist revolution taking part right in front of our eyes. We've seen increasing attacks on American history and monuments, including our most sacred like Mount Rushmore and even the American flag itself. We've watched our universities turned into Marxist indoctrination camps where kids who loved their country are increasingly coming out ready to overthrow it in favor of communism. Just look at this recent study done showing a growing acceptance of socialism and hatred of capitalism. We've even seen our military of all things infiltrated by a Marxist cult that seeks to tear down all of America's institutions. As you all well know, I could go on and on, but the point is that the America that we all know and love is under serious attack from within. That brings us to this Colorado mayor who thinks he could just unilaterally ban the Pledge of Allegiance and everybody's just going to fall into line. Then during the public comment period, an individual said she wanted to recite the pledge to board members and a handful of attendees stood and recited it, prompting Furman to say that we're out of order. Yes, I love it. Let's listen to this mayor's reasoning for banning the pledge. The indirect threats, inappropriate comments in and out of public meetings, and the general divisiveness issues creating in our community, we will not be doing the Pledge of Allegiance. Let me get this straight. You think that because of alleged threats and divisiveness most likely caused by leftist overreach like this, that you can then just unilaterally ban the American Pledge of Allegiance? I've received that threat. Who cares? You don't even know who made these alleged threats. For all we know, the mayor himself could have made them. Hate crime false flags are a favorite tactic of the left, so why wouldn't they be doing it again here? So the attendees ignore the ban and decide to recite the Pledge of Allegiance anyway and look what happens. I'd note that that's out of order and we did have a one strike policy. I'm not going to ask everyone to leave tonight, but if something like that happens again, we will. And tackling and other things like that are also out of order. So please don't ask me to make people leave.  I'm getting flashbacks to one of my all time favorite movies. Maybe Red Dawn really was a documentary. All I know is that it looks increasingly clear that we're being led down a path that looks suspiciously like past communist revolutions. Instead, this time they're using race to divide and conquer instead of class. Real American patriots have a duty to stand up and defend our country, whether that be attending these board meetings, marching, or standing up to the tyranny that is becoming increasingly visible by the day. All I know is don't ever let them take your guns or your right to free speech. Alright, I hear kids crying upstairs so time to get back to stay at home dad life. But if you enjoyed this, please hit that like button, share, and let me know in the comment section. As always, thanks for watching and I'll see you all for tomorrow's video.


Some of you people are tired of being mistreated tired of being talked about or treated any old sort of way being disrespected Well, here's the truth people treat you the way you allow them to or people treat you the way that you present yourselves Remember the disciples were accused of having been with Jesus They said we perceive that they have been with Jesus Why because they acted that way and how were they treated they were treated as people who had been in the presence of God If you want people respect your walk make sure they see your walk If you want people respect what you say make sure that they hear what you say and see and hear your convictions People will treat you in the way that you present yourself to them present yourself as a man or woman of God They'll treat you that way


To our talk, I'm Nathan Smith from Chef Software. This is Rob Kidd, also from Chef Software. And our talk is about strong practices for continuous delivery using Ruby on Rails and Chef Delivery. And I'm an engineer at Chef. I do mostly front-end development, so you can find me working on our web applications at Chef. I do a lot of stuff on the Ops side, as many of us do at Chef. And how about you, Rob? I am on the community engineering team. I maintain a Rails app that is the RubyGems equivalent for the Chef community. Supermarket. Web app. The community site where cookbooks are shared. I'm a sysadmin by trade and a software developer by Happenstance. So we're going to start out talking a little bit about DevOps and why we do some of the things that we do and how we solve some of the problems that we face. So if you look at this graph, this is kind of a graph of engineering anything. And what you want, you want to be at that top corner where you have a high level of quality with whatever quality standards you're reaching for and compliance with either, you know, depending on what you're working on, it might be compliance with regulations or compliance with your company's internal rules, but you want your stuff to be good and you want your stuff to have compliance. And you also want to go fast and you want to have a high rate of innovation to be able to try things, break things, do things, and create new things. And there's a trade-off here. You can go really fast, not care about quality, and make lots of stuff that's bad and you don't want that. You can have very strict adherence to all of your compliance guidelines but move very slowly. And if you've ever worked in the kinds of companies that have a lot of compliance requirements, there's a lot of moving very slowly. So how do we take this curve and move it so we can get closer to the corner without sacrificing our rate of innovation or the quality of what we're building? So some of these processes, these are some of the challenges that exist in engineering software. So we have manual processes where things can take a long time to spin up a new server, get new hardware, acquire some kind of software you need. So I'm just going to kind of roll through these different challenges and things that we can do to help solve them. So with manual processes we want to automate. So we want to be able to build and use tools that let us get rid of these manual processes and be able to do things more in a more automated fashion. So a lot of us are probably using cloud for this. It's a lot easier to spin up an EC2 instance than it is to order and rack and stack new hardware. Another thing is moving from legacy systems that are a lot harder to change to dynamic infrastructure. Again, some of that cloud-based infrastructure that lets you do a lot more dynamic management and be a lot more flexible in what you do. You know organizations, silos can be a problem that don't let us collaborate in between teams. So what we want there is to build a culture where there's common trust and collaboration between teams and we can work towards those goals to increase our quality and the rate at which we innovate. And then if you've ever tried to deploy something where you've made a lot of changes over a long period of time, when it's time to deploy that, it's really painful because so much has changed. But if you can decrease the size of the batches that you're sending out and continuously deliver your applications, then it's a lot safer to make those small changes and your customers get them a lot quicker rather than having to wait for a big release. And then we have regulatory burdens where we have these compliance rules that we have to keep up with and the way we can increase that is to integrate what we're doing for our compliance workflow into the very beginning and we can build safety and security end-to-end so we don't have to have this stage at the end where now we've done our thing, now we have to wait to go through this arduous compliance process. So these are some challenges and some techniques that we can use to deal with those challenges. And then the result of that is we take this curve and we move it so we can build higher quality things that are more compliant and we can do it faster by applying all these principles and we put things like dynamic infrastructure, infrastructure as code and DevOps, then those are the ingredients we can use to increase the DevOps, well, let's talk about DevOps. Why don't you tell me what DevOps is? I got a slide for you right there. At Chef we have determined, you should always be wary of somebody who's defining DevOps for you because vendors do it a lot. We're a vendor and I'm about to give you our definition of DevOps. We believe at Chef that it is a cultural and professional movement focused on how we build and operate high-velocity organizations and the movement and experiences come from the experiences of the parent fishers. That's a mouthful and it's kind of dense but we believe that organizations move quickly, not necessarily software, organizations that move quickly, move quickly with software. And the formula for that is you have good people, they build, how about this, let me start over, you have great people, build great products and those great products build great companies. If you have sad people, they're going to build sad products and they're going to make sad companies. So what you want is the ingredients and the people and the culture that will let you build great products and great companies. How about diversity? Diversity is super important. Well said. And another thing that you're going to hear, if you start learning about DevOps and this movement and the kinds of companies and people who are doing stuff in this way, you're going to learn some Japanese or at least you're going to hear Japanese words. You might not know what they mean. Because a lot of this philosophy comes from originally from the Toyota production system and from a lot of work that was done in Toyota and in other companies to increase quality in their processes. And so there's a lot of this lean, these lean words. So we have, we want to eliminate non value added action. So eliminate waste and Japanese for that is Muda, I guess it says right there. And then you want to have a system, if you ever used a system like Kanban where you want to pull the work in rather than pushing it through a system. And Kaizen is a word that means continuous improvement. So as you're going through these processes, you want to be looking at what you're doing constantly and finding out how to improve the process over time. But then sometimes, instead of making these small changes, you're going to want to do what's called Kaikaku, which is a big disruptive change. And you want to do these things in small batches. You want to do experiments and be constantly improving what you're doing. And one of my favorite books, you should go read, it's called The Goal. It's by Eli Goldrat. It's a business novel. And it's a novel about a guy who is running a factory. And it's terrible. And he learns how to apply some processes like this in order to improve it. And it's a very good lesson on what lean means. And there's lots of information about this. If you don't know about it, it's great stuff to learn about and to think about and to apply toward how we build systems. And if you're going to move quickly, you need to embrace failure. You need to prepare for it. And treat failure as a learning opportunity. Hold postmortems when there are outages or breakages or breakdowns in the process. And not hold people to blame, but to take them as, you know, hold learning reviews so that the organization can learn from that experience and improve. And you're going to want to automate everything. Because the more manual things you have, those are, they'll stand in the way of what you're trying to do. So you can make donuts, but if you have this donut machine, you can make a lot more donuts. And we want to make a lot of donuts. And we want you to make a lot of donuts. So the rewards of adopting a DevOps culture and workflow is that you will deploy more frequently. Because you can deploy more frequently, obviously your shipments are faster. And so your customers get changes faster. And presumably they are happier. You will have a shorter mean time to resolution when a problem is discovered to when it gets resolved, because you have gotten very good at pushing change out into production and in front of users. The ability to push new features is also the ability to push security updates or bug fixes. Profits go up, company is happy, users are happy, everybody's happy. Yeah. And if you want to sell this kind of stuff to your boss and say we should be doing DevOps, prove to them that you make more money and then your boss will be cool with it. I promise. And there's science behind it. Science plus money can pretty much answer that. All right. So you all this was a talk on continuous delivery. We will shift from talking about DevOps to a continuous delivery pipeline. We still have some practices to talk about to prepare you to continuously deliver change to your users. This is I don't think this is a legal license plate, but it says, I think it's pronounced but the tools that you're using matter. You can choose any tools you want. But a good example of how your tools will shape your culture is is using a thing like get like pretty much everyone here probably uses get or a similar capable version control system. And and it's important to use tools that will help you get your stuff done, get done. The other tenant here is that absolutely everything should be in version control. One of the well, you can manage risk by having everything. There's an ideal that you can rebuild your systems with what's in version control, what's in your data stores, your databases and compute that you have asked to exist. Either you get new metal servers, you get new EC2 instances. Absolutely everything should be in version control. Changes, like we pound this drum a little bit, small batches to test that you are making the right thing. So you make a small change, put it in an acceptance environment where some ideally a customer or end user can say, yes, that's the thing that I wanted that validates the work that you're doing. It does introduce volatility in the near term, but you get long term stability and reduce long term risk. And another thing that we should be practicing is continuous integration. So you do not want to have long lived branches. And and we we stress that you want master to be whatever you call master to be something that you can deploy. And it should always be in a stable state. Because if you have these long long lived branches, they get out of sync. You have an integration problem when you try to integrate these things back in. If you keep everything in small changes, merge to master as quickly as possible. If you find a problem, you fix it right away. And you do continuous integration. You should also practice as we do the four eye rule. This means two sets of eyes should review every piece of code, every set of changes that are going through the system. Two people should agree on that. Pretty simple rule. But we like getting Marvel people in. We like, yes, we also like telling people what to do, I guess. But this is advice. And I think if you follow this stuff, it'll be to your benefit. Right tests. I mean, we're among the Ruby community. So I don't think this needs too much stressing. As far as unit testing goes, you know, Ruby has a very good testing culture. That's one of the reasons I love Ruby. And also, you know, integration and functional tests that are higher level, more oriented toward the user. I think Ruby's still pretty good at that. But those things are less common. But but having all these different kinds of tests should be there and are important in order to to ensure the quality of your software. There should be one path of change in an organization to move change from idea to production in front of your users. The delivery pipeline that we'll be demonstrating to you shortly is fixed. These are the stages that a change goes through, whether it's configuration change to a server, whether it's a code change to an application. It goes through these stages where you get to be flexible about what does it mean to say verify and unit test an application that depends on the application stack. I'll go into that in a little bit. Okay, so today, the rest of our talk, we're going to kind of show how we're going to take an example Rails app, something really dumb and simple, and move it through this pipeline. Well, you didn't write it. You just copied it off the internet, right? Rails, new, and then let's do this. Basically, it's totally growth sample. Yeah. And we're going to be deploying that app. So this first stage here, we have verify and approval. So one of the things we want to do, the verify stage is going to run every time you, if you're using GitHub, it'll run every time you open a pull request. Before we go into that, I'm going to pull the room here. How many of you are right Ruby? Okay, all of you. You're at Rails.com. Are you Rails developers? Hands up. Okay, cool. How do you lint a Rails app? You don't, okay. This is what I'll be encouraging you to do. Anybody? Rubocop. All right. So how do you syntax check a Rails app? Also Rubocop. Turns out, in the Rails community, we have a lint and syntax checker that we can use one tool. So that'll be some important later. And Rubocop, Rubocop can be kind of a jerk and pull you over and give you a ticket and not be very nice. But you can customize how Rubocop works so that you can tell it that you should always use double quotes because that's the right way to write Ruby. Or you can tell it to use single quotes when you're not interpolating things. It's up to you. It's up to your team. You should define those rules. And also to get back to people and having some empathy for others, get Rubocop to be that nitpicker. Like, a human shouldn't have to tell another human which style of quoting to use. Get a computer to do that so that everybody can, like, bond in frustration at the computer. It's good team dynamics. All right. So how do you unit test Rails app? This is where we get maybe a little controversial. I don't know. Anybody? Unit testing a Rails app. RSpec. What else could you use? Any test? Absolutely. It's up to you. You can use RSpec or many tests for our purposes. We'll be using RSpec in our demo. How about security testing a Rails app? It's totally something we should do, right? Breakband. Exactly. What else could you do with breakband? In addition to breakband. Bundler audit. It is an awesome little gem that the maintainers keep up to date with a database of gems, versions that have vulnerabilities in them. So you can very quickly audit your gem file, specifically your gem file lock, the versions of the gems that your application is using, and are there no vulnerabilities against them. In our pipeline, my master will go red if I have vulnerable gems. And that's something I have to How about quality testing? What would rake Tether? I'm sorry? Oh, yeah. Reek. Looking for code smells. Yes, Reek. There's Flog. There is Flog from the same fella. There's Flay. So there are a few tools. This one I'm not as opinionated about in the Rails community. I don't think the community has come to a consensus of what quality means, and it can be kind of subjective for a team. I will be hand waving over quality in this pipeline. There is a hook. If you decide on how you would measure quality and ensure that you don't go below a particular measure, my recommendation is decide on what quality means for a particular application. Maybe don't go below a 3.5 in code climate. And then your quality check is, is this commit above or below 3.5? This is sort of a quick glimpse at the Chef ecosystem. We have assessment tools. There's a ChefDK, which is a development environment, a Chef delivery pipeline environment service, centrifuge that can control what changes are going into production. We're going to be focusing today on the delivery tool. And this is what the pipeline looks like. The fixed pipeline, this is the shape. You go through these six stages to take code change into production. In the verify stage, this is where if you have a pull request and it needs to be reviewed, this is the equivalent of having, say, Travis run your tests. Delivery would run these three phases in verify. Lint we've already established is Rubocop. Syntax we've already established is also Rubocop. So I'm going to turn off Syntax highlighting for this particular Rails pipeline. And unit tests are running my spec. It is after these three phases succeed that delivery would go nag a person and say, Hey, this is worth reviewing because it's past tests. So a human needs to decide, oh, no, I'm getting ahead of myself. Okay. All of you are Rubyists. Have any of you ever written Chef? Okay, a few of you have written Chef. The ones that haven't written Chef. Tell me what this does. This is not a trick question. It runs Rubocop. If you cross your eyes, you see it's just Ruby. It's an execute method. It takes a parameter. There's a block that does a thing. So this is the link test in our delivery pipeline. That's the code that does the link testing. This is unit. Do you see the difference? It runs the spec. Obviously, there's a lot of boilerplate there. I could improve this by wrapping it up into a, you know, test execute that takes the repetition out. But I wanted to not show, not hide too much of the magic. Alright, so tests have passed and verify and a human has been asked, does this code look good? This is the four eye rule in effect. A human decides whether this change looks good. It looks great. It looks great. We're going to move into the build phase. So something that I would like to point out about the unit syntax, all of these light blue boxes that are running. Because we advocate continuous integration, on the build node that's going to be running these tests, it takes the change set the branch that is under review and merges it locally to master. So clones get merges it locally to master and then runs your test. Because if it doesn't merge cleanly to master, it's not been integrated against master. Continuous integration. You might run on your feature branch on your laptop, but delivery will tell you, hey, you're out of date. And you have an opportunity very quickly, because your branches don't live long to catch up to master. So in build, we rerun lin syntax and unit, because it might have taken a while for a human to push approve. So master might have changed. So we merge it to master at this point in the central repository and rerun lin syntax and unit to make sure that everything has integrated correctly. If those pass, we move into security and quality. I'm hand waving quality, but insecurity will run breakman and bundler audit. And then we move into publish. What is publish? One of the messages I wanted to, that we would like you to get out of this is make a release artifact and promote that into staging and production. You should not be running bundle install and production. You should not be running bundle install and staging. You should be building release artifact and then testing that in your integration environment. So to that effect, we will be using bundle package in the publish phase to cash our gems. We pre compile our assets and then we put that into a tarball. We're going to be deploying to Heroku. So the choice of release artifact format depends on your production environment. So in this example, we're going to use Heroku. So I'm going to give it a tarball that I have pre cashed stuff in so that I don't depend on Heroku being able to reach Ruby gems or needing to compile my assets. So, so Chef delivery, that's, it's a program for deploying apps to Heroku. It could be. Could I use it on EC2? Yes. Okay. But not on, not on like physical machines though. Okay, okay. Okay. We're trying, we're trying to kind of focus on on the delivery pipeline and how you get an app through it. So a simple way to do that is to just use Heroku. If you're just using Heroku, as you normally do going through their tutorial, you're probably not going to use these API's directly. You probably haven't, you might not have heard of the Heroku source API. But there's an API on Heroku that you can upload anything to and it'll give you back a URL, which is just an S3 URL, where you can get that artifact. So we're just kind of using that as, hey, we created a tarball of our thing. So we need to put it somewhere Heroku conveniently has a place. And we can use the URL that it gives us in the Heroku build API. This would be the secret code. The peak behind the curtain, when you do it, get pushed Heroku, all the tasks that it takes, whether you're asking Heroku to do the bundle installs or whether you do it ahead of time with this tarball. In the end, when Heroku has gotten your app runnable, what they call that artifact at the end that is the runnable state is called a slug. And this is a way to poke the API with tarball to get a slug out of it. And if you, if you are just using Heroku, you might not need to do this, but to kind of think about the flexibility of how Chef delivery works, say you're using Heroku and then you get big and Heroku is not economical to use anymore. And you want to switch over to using Chef to spin up EC2 instances and deploy your app that way. Then you can use your same workflow and your same pipeline. And for the end you the developer end user, nothing's going to change. And everything's going to work the same way. So this is another reason to just let's take the simplest possible thing and deploy with Heroku. Right. So the simplest possible thing, the thing that I'm going to do, if I succeed at making that release artifact, and in our case, it's a slug, a Roku slug that Roku stored and I have an ID that, that is the identifier for that release artifact that Peroku is storing for me, I could move into an acceptance environment. And in the acceptance environment, I'm going to spin up the app at this version that's being tested and test it and then make it available to a human to accept the changes. It's a little bit like a QA environment, if we use acceptance. In the provision phase, I'm going to make sure that a Roku app exists, that I could deploy to. If you were in EC2, the provision phase would be spinning up a VPC and load balancer and your web nodes and database. It's make sure you have run time infrastructure in place to deploy to. The deploy phase obviously deploys. And then if those two succeed, no errors in either provisioning the infrastructure or deploying this version, smoke tests are very fast tests, just see if it's worth going into the longer running functional tests. So we hit some URL endpoints and make sure that we get 200 okays. If we get 200 okays, we know it's worth testing with the longer runs. Functional tests in this case were feature specs that are told to run against a remote URL instead of the locally running rack app. Yeah, so copy bar. Yeah, it's a good thing to use. Use cucumber. So what does prevent so using the Roku API in this example, what does provision and deploy like it says, the app name project stage stages, I'm in the acceptance stage right now. So make me a project acceptance dino app. I poke her Roku app create with some parameters and say, I want to make sure that this app exists. This is a simplified version of the code. There's a little thing that if it already exists, it's fine. And then that succeeds, I test that succeeds, I have an app, it might not be running anything. And then in the deploy, I'm using the API again to say, hey, you have just come into existence, or maybe you're using maybe you still exist from the last time I ran, I want you to run this version. You poke it with a slug ID and Roku handles spinning that thing up. And you're not running bundled like installing and you're not compiling gems and you're not compiling assets. It's ready to go. So it's a very fast swap out at and then you have enough delivery will poke a human again and say, All right, acceptance is up, it's past all the automated tests. And now a human needs to go and decide, was this change implemented correctly? So I have an opportunity, like a QA group can now go and poke a thing and confirm that like customers would want to see this. And your choice now is, do I deliver this to production?  And it moves into a union environment and it runs those same four stages. Provision a union environment, deploy our application to the environment, smoke test and functional tests. What is different about union is that union is the environment in which all your components run. And your tests will test against other components that are related to this pipeline, but not directly in it.  But then in union it would be tested against the latest front end app.  So you would find interaction errors in union. Some people call union staging, we call it union because it has a very intentional purpose to be the first opportunity for the delivered versions of all of the components of a system to be tested together. If union is green, all the tests pass. It automatically a rehearsal environment is spun up. I'll explain rehearsal in a moment. If rehearsal is green, all the same tests pass. It moves on to the delivered environment which is probably your production environment that your users are hitting. I'm reading your minds and your question is what's the purpose of rehearsal. If union breaks, if you discover an interaction error between two components that were tested in isolation and in acceptance and they break in union, you need to fix it. So union has gone from green to red and now you need to push a change through the pipeline again to bring union from red to green. Rehearsal is where you test going from green to green and ensure that the fix for the error does not assume that the system is broken. My example, my go-to example are schema migrations. If you have a schema migration and then your data looks wrong, if your fix is I assume the data looks wrong and I make it right. In an environment like production where you didn't break yet, if your fix for the fix for the data error, the schema error is the scheme is broken, it's not going to pass. So rehearsal is an opportunity to go from green to green and catch it there. And we can kind of show a little bit of the Chef Delivery UI and then we'll have a few minutes for questions. You're not on the internet. Yeah, yeah we can show you. So pretty much when you're using Chef Delivery, which you can get with a Chef Premium subscription, you you have a web interface that you can run a delivery cluster that has build nodes and it has a web interface where you have you can visualize all this stuff happening and you can see the output from your test runs, you can click a button to approve things and it is important that we have those those manual gates are built into the system in order to ensure that we can have a human look at a thing. So if you want to stick around we can kind of show you on the UI of delivery but now we can we can take some questions if you have any. All right, well thanks for coming everybody. We really appreciate it.


Good afternoon everyone. This is Melissa with the stockswish.com and welcome. Thought I would do a market review I have not done a market review in a little while And I think it's important to do it here now today because the market has been a hard For a lot of people to trade I'd say the last month month and a half. I've been reading it very well Simply because I know how to re-gaps well. So I've been reading it very bullishly now the day that we fell down last week On Thursday even I was a little surprised how deep we came in But then when I saw where we were at then the morning of the 8th I realized that we were gonna hold and that's exactly what we did and I wasn't really that surprised because the market is Bullish the market is in an uptrend and I know a lot of people thought we're gonna fall off the planet here It would have been fine by me because I loved it short, but the market just wasn't gonna have it The interesting thing was I expected the market on this following day here was Friday to actually gap down But we didn't when we didn't gap down and then also I didn't find a lot of gaps I was in love with Friday. I knew that the market was gonna hold So it was like a lot of things going on one It was raining on my gaps and I didn't like anything Friday and then to the market wasn't gapping down Which I felt that it really should have based on this sell-off on Thursday and also the area Do you see this bullish gap back from here? The low is 8135 and where we closed here on Thursday was 8137 that is utter perfection in the market This gap here is holding and what is this gap? This is a bullish continuation gap in the market and clearly it's holding because you know what if the market Would have come in all the way down and here it could have and that would have still been fine, too We still would have been in a bullish uptrend It would have been a deeper pull-in, but the market didn't do it and isn't doing it and isn't going to do it And I even thought today we possibly actually I thought even Monday Monday or Tuesday I thought we possibly lived higher already start to make the move up. We are we rested here Monday. It was a holiday Even though the market was open and then we traded very green today The interesting thing is the way that we traded today was very sloppy Because we rallied up first Fakes like we were going lower at 10 o'clock, but didn't do it which I didn't believe because the fact is I knew we were bullish Ran up broke out a new high here This is a 1015 came in and triggered on a sell set up again here But there's no reason to think this is gonna hold why again the markets bullish I had made a new high here and didn't fall through in this sell set up Which it should have if it was gonna come in one more area on the daily But it didn't do it came in here and this is just sloppy because you see how this made this pivot here But again retested an area retested an area of what an area of support This is support on the 15-minute chart this area here around 82 20 ish came down here We tested it and here was actually a goodbye in the market here at 1 30 in the afternoon 130 into 145 reversal time into the 2 o'clock you could have bought the market stop here under 82 20 For follow through we didn't really go much of anywhere today But I think tomorrow the market's going to trade higher and be bullish This is a nice hold in here for the cues nice scoop here up to the upwards direction Nice hold here in the 15 minute I'm saying it's been very choppy for people because it's been hard for people to get any Volatility and momentum just looking for strategies that are looking for the market or any trades that you're need the market I trade dapps So I'm lucky that I know how to do that because if I didn't If I needed a strategy that I needed the market to get the directional bias correct for my trade It would be a very choppy last month And and last week was actually a really really good week So we'll see what this week brings, but the market is bullish. There's no doubt about it We're going to follow through and actually trade higher into the close at the end of the calendar year this year in 2013 I don't see anything stopping that now and if the market wanted to come in here in the last few days and Fought through with this rev art could have did it it didn't and not only that it held this bullish gap back here That was from the 18th an absolute utter perfection. So again, I love to read numbers. This is how I trade I read price action when I make determinations and I read gaps specifically the gaps helped me determine what to do with a stock chart that's how I know what direction to trade something and The QQQs are holding beautifully in the bullish uptrend and when they do break out over this area I don't know when this is going to happen But I I think it's going to happen in the next five to seven days when the market trades over this area here of eighty three forty eighty three fifty It's going to have a big big rally And so I think this happens in the next week It could even happen this week because we're getting really close to it We're only a dollar away and that's really nothing to the market A lot of people think this looks topping. It will be broken broken to the outward direction higher If you don't short tops as a trade, it's just a poor way to trade You trade with directional bias you trade and read the gaps you follow through and trade in the direction of the gaps and that's the right way to trade and enter trades and Here it is look at this chart. This is all so let's actually look at the whole year Here's the year now you see it. Everybody says oh we're extended. We're not extended. This has been a nice consecutive move gap up consecutive move gap up consecutive move gap up pull in here Gap up gap up beautiful follow through here ever since really this was July Incredible beautiful moves Rest higher come in higher come in higher come in higher higher higher come in And this isn't even really big pull-ins That's why I was saying we could come all the way down here to 80 and still hold but it does not happen now We're setting up to break out higher Into the end of the calendar year 2013 almost almost over it's hard to believe So this is Melissa with the stocks which commas is a QQQ market update for November 12 earnings this month and I hope everyone has a terrific trading week if you need anything if you're interested in the next golden gap class It will be December 14th and 15th. That will be the last golden gap class of December of 2013 I'm doing one more class this year December 14th and 15th if you were interested. I would suggest a pre-register Since it's going to be the last class of the year My email is Melissa at the stocks wish calm. Thanks everybody. Have a great day


What is a demon set? A demon set ensures that all the nodes of the Kubernetes cluster runs a single copy of a port. If you add more nodes, then new instances of the port are scheduled. And if you remove nodes, then the instance is terminated but not rescheduled. Because remember that we said that a demon set runs exactly one port to each node. To create a demon set, we just need to use the kind demon set. We set it a name and a label, everything is more or less the same, like in a deployment. And of course, we set the image that we want to run in all nodes. Then we can do keep call apply, which means f, apps, kubes, quarkus, demon set. Now it's just deploying this port to all my worker nodes. In this case, I've got three worker nodes, which means that three instances of this port are going to be alive. If I do keep call again, you see that now there is three ports running each one in one of my worker nodes. So demon sets is the way you need to use when you want to deploy the same content to all your nodes. One typical use case, it might be when you want to send the logs of all your nodes to a central loading system. Thanks for watching and don't forget to like the video and subscribe to the channel.


A building in the Camps Drift Park, which contains macro and China mall, burned on Tuesday morning after being looted by robbers in South Africa. Eyewitnesses video show the building ablaze with the scattered merchandise and a looter packing products in front of the shop. Concerns are growing over food and fuel supply in parts of South Africa as days of unrest and looting halted exports, damaged crops and forced food retailers to remain closed. Valence in several parts of the country was triggered by the jailing of former President Jacob Zuma as his supporters took to the streets last week, with some protesters clashing with police and looting shops. Local media reports the robbers started the fire.


Live from New York, it's theCUBE. Covering Big Data New York City 2016. Brought to you by headline sponsors, Cisco, IBM, NVIDIA, and our ecosystem sponsors. Now, here are your hosts, Dave Vellante and Peter Burris. Welcome back to the Big Apple, everybody. This is theCUBE, the worldwide leader in live tech coverage. We're here at Strata plus a dupe world. We run Big Data NYC in conjunction with that. John Furrier this week, it was in Orlando covering splunk.conf. Scott now is here, he's the CTO of Hortonworks, longtime CUBE alum. It's good to see you again. Thanks for having me back. You're welcome, I was saying, I was seeing you in the audience last week at Edge and now we're in New York. We got to come to New York to see each other, it's good. And so, you know, lots going on. We had Sean yesterday kind of gave us an update on the strategy, but what's going on here for you at the show? You know, we've got a lot of exciting things going on. And you mentioned last week, we participated in IBM's Edge conference, announced our partnership with the Power organization. You were like the star of the show.  Yeah, you know, it's really great. You know, being able to give more customers more choice on the technology they deploy, how they deploy it, being able to bring Hortonworks data platform to the power line of servers just creates more options as our customers, our joint customers really create their data fabric, right? And you know, when I've been here before, we've talked about the value of the ecosystem, right? In today's world of big data, there's so much data flying around, there's so much change in agility. It's really about being able to fit into a broad ecosystem and not having monolithic converged systems, right? And that was just another example of some of the things we're doing. I'll be speaking later today, talking a little bit about some of our latest product releases and feature functionality, again, giving more choice to customers on how they deploy their data fabric, how they combine different kinds of technology to solve their business problems. We also are bringing that technology, of course, to cloud, so working with Microsoft and HD Insights, making the technology more consumable by persona and allowing data science clusters to be spun up in the cloud, whether they're ephemeral or long running. This is really exciting, not just because of the technology, but really... Before you say, I'm sorry, when you say making it available by persona, could you kind of clarify that and then go into why it's exciting? Sure, so you think about all of the technology that's out there in the open-source stack and how we're trying to bring all of that technology together and create choice, that can also be a very daunting thing for someone who's, gee, I wanna go run some machine learning against a set of data to see if I have any interesting correlations, right? That user has a persona, wants to do machine learning, a certain discrete set of technologies, doesn't wanna know about the 37 other things that are available, just wants to get the job done. And so we make it less daunting by saying, okay, spin up a machine learning data science kind of cluster in the cloud. So the persona thing is really important as we're trying to get very discrete solutions, time to market and agility, okay? And so it's a packaging of all the broader stuff that we offer. I'm asking the other parts of the stack too. But it matches the persona of what's that use case that I want to go do. And then being able to execute that in the cloud exponentially makes it even more valuable because you think about ephemeral and cloud and all the advantages of cloud, that's really great. The key thing is there are applications that can be tested against a whole sample of data, very economically. This is stuff that couldn't have happened before. If you think about, yeah, I've got to go to a capital committee, I've got to buy a bunch of hardware, I've got to spend millions of millions of dollars, and I don't know if this thing's going to work. You'd never do it. If you can spin it up in cloud, load the data, go find it, yep, it's great, I'm going to keep it, I'm going to go do something with it, or you know what, there wasn't anything really there. I haven't spent a lot of money, shut it down, right? And so there's a whole new class of applications that are spawning because of this capability, right? And it's a combination of the open data platform, some of the open source technology, some of the newer algorithms, all that innovation. And then the ability to go deploy it in a very simple and seamless way. So summarize the cloud strategy, Hortonworks cloud strategy. It sounds like you want to make technology available. We were talking this morning about technology needs to be plentiful for revolution to occur, and technology's certainly plentiful today. But from a cloud standpoint, you're making the technology available in the cloud for your customers, gives them choice, they can still do on-prem, they can do cloud. But summarize the strategy for us. You know, the easiest way to think about it is there are two things that we want to go do for our customers. One is we want to make their experience with Hortonworks data platform and Hortonworks data flow the same regardless of how they deploy. If they deploy on-prem, if they deploy in the cloud, we want that experience, the applications, the integration, all that stuff to be consistent. So that again, flexible choice of how it gets deployed. The second thing, and we think that this will be happening, we're starting to see it now, but I think it'll be kind of mainstream in the future, is that the entire move to cloud is happening, but I don't think that that implies that customers will move from on-prem to a single cloud instance. I believe that they will have data in multiple cloud instances, maybe with the same provider, maybe with different providers, they maybe have some data still on-prem. Why is that? Think about devices on the edge and the collection of that device information. That device information is probably going to live in a cloud. Companies are going to buy that from the provider that they bought the devices from. It's going to live in the cloud that that provider put it in. May not be their cloud. So data having gravity, you may not want to move all the data from there to somewhere else, causing latency, complexity, more expense. You want to play it where it lies. So we believe that companies will have, ultimately, multiple cloud implementations and footprints, and so we want to actually build that common set of shared services so that they can have common security, common governance, and common management across the entire ecosystem that they're building out, whether it be on-prem in the cloud or multiple cloud instances. We call that the data plane and being able to play data where the data lie. And when you talk about, and we talk about, and we know IoT is coming, the whole notion of getting value out of Internet of Things devices is being able to push processing to the edge. Why do you need to push it to the edge? A, that's the only way it'll scale, and B, you need to push it to the edge so that it happens in a timely fashion. And so the only way to really enable that is to enable this notion of a data plane with that shared service so that you can actually have a discreet view on a single pane of glass of all your data assets and applications and how they're running, and be able to push and move processing around and have choice in the decision that you make. And that data plane is a collection of open source technologies that you and your open source, committers, partners, whatever, develop that then becomes available wherever on-prem or in the cloud. And your cloud partners, let's say it's a Microsoft or other cloud partners, will then, you will deliver that through their marketplace or is it a code element? Yeah, so obviously, different cloud providers have different business models and different ways to go to market. Our goal is to make it the same look and feel and touch and feel and to conform within each of those business models. So yeah, they'll be able to go natively to a cloud provider and spin up either a persona or the whole breadth of infrastructures of service. Again, whatever look and feel they want will allow that to happen. Or with these shared services, we'll also create that data plane where they can actually go through our data plane and have that single pane of glass and spin up cloud instances however they like. Let's talk roadmap. What's new, what's coming? We've had a lot of releases this year and one of the neat things about the model we work in and I think the fundamental shift to open source and open community development is this consistent pace of agility. As technology typically matures, it slows down and gets a little bit harder to do upgrades and so on but the open community driving that agility is allowing us to keep at that pace that we've been at for a very long time. So we just had two major releases of course, new release of our data platform that includes integration of security and governance, the integration of Apache Atlas and Apache Ranger. Why is that important? Well, security's important, right? Making sure that you encrypt PII data, that you're able to secure the perimeter of your clusters that you're able to understand who has access to what data. That's all really important. Core security as part of the Hadoop 2.0 versioning, that's all very strong. We've taken it to the next level and integrated our metadata tagging Apache Atlas with the security so now you can do tag-based security, role-based, tag-based security, why is that important? Think about multinational corporations that I travel around the world. If I'm sitting in the United States, I have access to certain pieces of data. If I happen to find myself traveling and in Germany, I may have different access based on where I'm logging in from, based on frankly the rules of different countries. So being able to tie that security to other metadata tagging like where I've logged in from, kind of location-based, context-based, role-based, as well as taking a look at one of the big opportunities we have is if I have access to this data and that data and there's no PII data in either source, but when I join that data together, I could potentially infer PII data. Being able to do tag-based metadata security based on saying you cannot have access to that data joined. You can have access to it separately, but if you join it, you can't see it. This is a really big deal. We talk about deploying data lakes, the value of all the data that's out there, but the importance of doing governance, having this core technology in there is a big deal. The other thing, and there are millions of things that are in the stack, we've added interactive query with Hive 2.0 in tech preview, being able to do interactive query, sub-second query response. Again, rather than creating a new project or some other complexity for our customers to understand, we actually work with the community to improve Hive's performance, and this is something that a lot of customers have downloaded they're using in tech preview. We've created a new release of our Hortonworks data flow, 2.0, where we've expanded the footprint of our ability to manage data in motion. So not only now can we manage very complex data flows, bi-directional point-to-point data flows. This is a huge IoT use case as sensors need to talk to each other. With 2.0, we've actually now created edge agents so we can move further out to the edge, lightweight, either in C++ or a lightweight Java instance, very small footprint, so we can actually push out the security, the governance, as well as the provenance of data collection and data movement. So it's a really exciting times, I think, for the community and certainly for Hortonworks and what we're delivering back for our customers. What's going on? All right, we're out of time. We have to leave it there. Scott, great to see you as always. Thanks for coming on theCUBE. Thank you very much. All right, keep right there, everybody. We'll be back with our next guest right after this is theCUBE, we're live from New York City. Right back.