Hello and welcome to the Grand Line Review, your source for everything One Piece, and today we have a review of chapter 964, Odin's Adventure. And this week was just amazing. I can't remember the last time that I was this on board with the flashback chapter in the entire history of me reading this series weekly. I mean it really just has everything going for it with incredibly hyped characters, great comedy, a charming story, and a profound sense of adventure that oddly enough doesn't show up a lot in One Piece in the post timescape era. Add an incredible cliffhanger-ish final page and you have all of the ingredients that make One Piece an incredible experience to read and not a single straw hat was even required to create it. Although I guess technically one literal straw hat was featured in the chapter, but none of our primary protagonists in any case. To really start delving into this though I do need to begin with Whitebeard once again because it's pretty incredible to think that almost 10 years after his death in the series he can still continue to be developed and rise in my personal rankings of characters. I said this last week because we got one panel of Whitebeard in complete shock and it wasn't an expression that we'd ever seen from the strongest man in the world, but this chapter went full on and gave us an incredible spectrum of Whitebeard expressions including happy cheeky, shock once again, and my favorite pure disgust, which Merid Odin's disgusted look in regards to Wano and was a brilliant piece of comedy. Actually though you know what my favorite moment of the chapter was when he and Kinamon had their little bro fist agreement in regards to not taking Odin out to sea. Seeing that panel was absolutely surreal because in the story we've come to know up until now Whitebeard and Kinamon have been completely separate entities. Like we weren't even introduced to Kinamon until way after Whitebeard's death and it's cool to see this connection being forged as I'm sure we'll also see with Roger eventually because Momonosuke did say that he'd met the man himself so Kinamon probably has as well. It was also nice to hear Whitebeard mentioning his former crew being the Rocks Pirates and the experience he'd had when a whole ton of leaders get together as well as the chaos that such a thing can cause. It makes me hungrier and hungrier to take a step back just a little bit further into the past and explore them but I'm sure that will happen at some stage in the future possibly even during the Wanowak with some sort of Big Mom Kaido flashback but right now I think we have quite a bit to captivate our attention. Back to Whitebeard specifically though he did have one very interesting phrase this chapter when he welcomed Odin aboard his ship and decided to call him Little Brother instead of a son which is how Whitebeard would typically refer to his crew members and I thought this was a wonderful touch because the entire discussion up until that point had been surrounding the idea that Odin isn't the type of man to be a follower and Whitebeard recognizes and respects that by referring to him with a term implying a large degree more equality to himself. So if anything this doesn't simply make Odin a brother amongst the Whitebeard Pirates but in fact something more akin to you know a quirky uncle and speaking of his quirkiness it was certainly on full display during this chapter as Odin blatantly refuses Whitebeard's refusal and attempts to force his way aboard the ship leading to Whitebeard's bargain that if Odin could hold on to the chain for three days then he would allow him to join his crew and this moment was also commonly gold because Odin emerged proudly exclaiming that I knew you would try this Whitebeard followed immediately by Iso emerging and yelling I knew you would try this Odin which had me laughing probably a lot more than it should have and actually just briefly speaking of Iso he and Whitebeard are off to a bit of a turbulent start with Iso claiming that he would never forgive the pirate captain for what he put Odin through. Of course we all know that that's going to change quite significantly although I am curious about how exactly that's going to play out because at some stage Iso's loyalty is going to need to switch from Odin and the Kozuki clan to the Whitebeard Pirates. He is going to become a son of Whitebeard and it wouldn't surprise me if when this occurred we actually got a mirror of the scene where Whitebeard invites Odin aboard as little brother and in this case he refers to Iso as a son. Weirdly enough though Iso actually reminds me a lot of Ace at this point traveling aboard the Moby Dick hovering such animosity for Whitebeard although I guess I suppose at least Iso isn't actively trying to kill him for now but it's that same sort of situation and I do wonder what that moment of epiphany is going to be like how Marco's discussion with Ace is what changed his outlook it's going to be interesting for sure but back to the chain gambit this sort of thing is just classic one piece the idea of some impossible task being pulled off by a person whose sheer willpower cannot be broken by anything and watching Odin endure it was a visual feast seeing him get dragged for days on end through water giant aquatic life and smashing into what looks like icebergs he's such a legendary yet somehow believable feat for a man like Odin to be pulling off although the greatest part of the entire sequence is definitely that one panel of Odin holding on to the chain fast asleep this whole scene was just brutal beautiful and hilarious all at once which is a great little microcosm of what one piece is and all of those ideas are very much consolidated in that moment where Odin emerges from a sea to save Toki and everyone thinks that he is an Umi Bozu and what legitimately made me laugh out loud was the close-up of Odin's face when he's asking Toki if she's safe and what looks like to be as serious a voice as he can muster but his bloated waterfield face is just such a wonderful comic contrast and now that we've mentioned her I have to say that after what seems like an awfully long wait we are finally able to properly introduce Lady Toki whose name is actually Amatsuki Toki and that is a very interesting development because how Amatsuki is spelt in kanji actually contains the character for moon just as the Kozuki name does and also Toki's kimono is also plastered in moons so the connection here is it's fairly obvious I mean at this stage I would not go so far as to say that Toki herself is necessarily from Wano but perhaps her parents or grandparents or some sort of relative was and that's why she's so keen to visit the nation of course this would have been a Wano from 800 years ago which is a very very important number actually because that would plonk Toki's point of origin as smack bang in the void century which is supposed to have taken place eight to nine hundred years prior to the current timeline so all of a sudden things have gone from extremely interesting to the idea that we're going to receive potentially well-changing information in this flashback because barring any crazy theories about him or the Gorase being immortal Toki is the first character we've actually met who has firsthand experience of the void century and there is no way that a character like that is going to be included here and not provide us with some tasty tasty information in fact it's entirely possible that Toki being from this time understands the will of D as well as the ancient kingdom which is yet another intriguing idea because of course Odin and Roger are destined to be on a path of collision so if Toki is present and he is of a man named Goldy Roger and she could provide some casual insight that could even shock Roger himself thus leading to a situation where she Odin, Nekomoshi, and Inorashi join the Roger pirates now I have to say that the other less fun thing about Toki is how expectedly disappointing her design is it's the complete opposite of Odin where Odin presented this grand figure who could never be mistaken for anybody else and in contrast to him we have Toki who looks like every woman in one piece ever she's classically beautiful and has the same stock standard body type and really if we did not know that this was Toki or if we weren't aware of her incredible time related devil through powers then her introduction probably would have been the low point of the chapter and just wish that Odin had the balls to really diversify his female designs in the same way that he does with his male ones he definitely has the talent to do so probably more talent than any other mangaka in the industry he just chooses not to push the boundaries when it comes to female designs which is a shame but like I said this was not entirely unexpected and of course this is just my opinion I'm sure that there are a ton of people out there who are going to be completely satisfied with Toki's design and are going to post mildly aggressive comments about how I'm not a true fan although I should just draw my own manga but whatever look it's a valid criticism and one of the greatest flaws of an otherwise near perfect manga series but while we're on this the most obvious resemblance Toki has is to her daughter Hiyori these two are identical but the reason why I don't bring that into the realm of criticism is because I'm hoping against hope that this is on purpose and that in the future there is going to be some sort of revelation that Komorasaki slash Hiyori was Toki all along and the real Hiyori is someone like Toko although it actually can't be Toko because Hiyori and Kalamatsu were separated when Hiyori was 13 so Toko is far too young but you get the idea that that's sort of a timey-wimey thing and it's entirely possible for this to be the case actually more so the most of my time travel ideas because it just requires Toki to fake her death which you know being trapped in a burning castle is a good start to that and then to travel forward in time find Dendro the most mysterious of the retainers and take on the identity of Komorasaki however the issue does come up with the whole idea of why Toki would bother to pretend to be Hiyori in the first place but at the same time it also makes the whole Hiyori not wanting to see Momonosuke think a lot more reasonable because he would surely recognize her as his mother in fact come to think of it Hiyori hasn't met any of the time traveler retainers yet either the only one she's spoken to is Kalamatsu and he having lived the last 20 years would certainly not have as fresh of a memory of Toki as the others would so you know perhaps there is method to the madness of keeping Hiyori away from the allied forces and yeah there are options here and I'm really hoping that an idea like this is going to play into the Toki character but at the same time one piece isn't exactly a stranger to daughters looking exactly like their mothers so meh. Moving to the final page of the chapter now and it's time to talk about Roger this was an incredible ending to a chapter because young Roger is quite a fine sight and he just looks so much like Ace at this point in time I mean if you got rid of the moustache that is but it's bizarrely nostalgic and I don't know if this is just me but Roger looks so full of life compared to pretty much any other time we've ever seen him and I guess this might be because we almost always see him at the end of his life you know being executed or behind bars or his final chat with whitebeard but this bright young future pirate king really is a sight to behold for me as is very young shanks and very young buggy they look simply adorable and you know what if there was one thing this flashback was missing up until this point it was an injection of buggy it's pretty crazy to think that they were not only sailing with Roger at such a young age but also sailing in the new world I mean shanks isn't that old actually I think he's 39 post timeskip which actually means that he was born when Odin fought Ashura Doji and went on to cling curry so that actually makes shanks nine years old at this very point in time so what the hell is a child like this doing in the new world buggy as well he's the same major shanks I think which would make him nine as well so I really can't wait to discover what circumstances brought them aboard the aura Jackson and while this clearly isn't shanks as part of the story to shine it is entirely possible that we may get an answer or at least a hint of an answer here but to conclude this was a brilliant chapter of manga it was the tensions easing from beginning to end and evoked a profound sense of one piece that I don't think I've truly felt in the post timeskip era also I didn't even mention Marco's words of there being something like 10 to 20 million islands in the world which is absurd and he may be exaggerating but hey there it is it's entirely possible somehow all in all though it was a lot of pure concentrated adventure content and a lot of fun it really was like stepping into the early days of the series where Oda crafted shorter arcs and made swift moving but highly potent chapters that tell their story gloriously and don't outstay their welcome I think that this flashback really is on an upward trajectory and who knows how high it will reach it still feels like we have so so much left to explore before moving back to current events and I for one cannot wait although I guess I will have to wait because there is a break next week but you know if there had to be a break then I think that this was a good lasting impression to go out on but that pretty much does it for chapter 964 if you enjoyed this video and the content this channel produced in general then please do consider donating to the ground line a few patreon because the support of all of your amazing people is what continues to make this channel possible and if you'd like to see more videos like this but applied to other anime manga series then please do check out my second channel New World Review for all of your wider needs and if you'd like to join the fun at any time then please do head over to my discord server where a wide array of shenanigan retakes place on a daily basis and finally please do comment with your thoughts on the chapter this has been the ground line review and I'll see you next time


Hey, everybody. Thanks for joining another exciting episode of the OpenShift Commons Briefings. Today, we are very fortunate to have Mark Borstein and Brian Culhane join us here from Cromolo Security. We're gonna be talking about how to securely automate GitOps. Mark, welcome to the show. I have seen you at just about every major trade show for the last these four or five years. You've been at our OpenShift Commons activities. You've been at the OpenShift Summit activities.  But I've never actually asked you, like, Cromolo Security, is it Cromolo Security? What's in the name? So it's pronounced tremolo, kind of a L, EL sound there after the M. So a tremolo is a sound fluctuation. So if you have ever played guitar or even the organs, with the guitar, you hit the whammy bar and that fluctuation, that's a tremolo. And so where the name originally came from was when we were first starting the company, we're a day management company primarily. That's where we got our start. And the very first product we were building was a web access management solution. So anybody familiar with service mesh will be familiar with this concept. There was a reverse proxy where you authenticated on the front end, we're actually gonna use Kerberos on the back end to lock down access and we're gonna be this universal reverse proxy. We wanted to get away from agents, which is a big thing that our competitors were doing. And so I wish I could say it was a marketing maven, but I am not. The first name for the company was gonna be auto IDM. Simple, kind of talked about what we did. My co-founder who actually is quite good at marketing came back and said, no, that's a terrible name. It's clunky, I'm gonna think of something else. So he came back and he said, well, it's a web access manager, Whammy Bar, Tremolo security. I was like, oh, that's a terrible name. Nobody's gonna know what it means. You know, my co-founder is a friend of mine from Boston and he's got a very thick Boston accent.  I was like, ah, that's just not gonna work. Go back to the drawing board. And so that night I spent a good three hours trying to find a domain name for the company that had the word identity in it. I tried different languages. I tried different combinations, acronyms, everything. Couldn't find a thing. It's like, so who is TremoloSecurity.com? It's open, cool. Now it's the name of the company. So then that's how we got the name of the company and the guitar logo and everything there. How long ago did you find the company? Must have been about four or five years ago, six? No, we actually started the company in 2010 was when the company originally started. And we kind of flew under the radar somewhere between a hobby and a science project for a few years while we were kind of, getting our feet under us, building out the technology. And then in 2013, we got our first customer, public safety environment here in the DC area, which kind of catapulted us. And then we didn't really come out of like, not that we were ever really in stealth mode, but we didn't really start getting out there until 2015, which is when we had our first booth actually had a red hat summit. That was kind of our coming out, come and ask stealth mode party was that first booth at Red Hat Summit in 15 in Boston. And it's also when we became an open source company and we said, you know what? Open source is gonna be the way to go. It's gonna be the way to get to the most people. So we decided to go ahead and open source up and it's been off to the races since then. And before starting the company, you were where? So I was a consultant at PricewaterhouseCoopers. So if folks are familiar at all with the audit industry, they call it the big four PricewaterhouseCoopers, which I was, Deloy, Ernst & Young, KPMG. And so I was an identity management consultant there for about seven years. And if you name a vendor and an industry, there's a pretty good chance I was involved with some kind of cross-section of doing an identity management deployment there. And so what we found when we were doing these deployments was that we were spending a lot more time customizing this beautiful vendor demo to what the customer needed rather than actually implementing their business logic. So the vendor would walk in and say, here's this big gorgeous demo with all our opinions of how you run your identity management. What's interesting about identity management versus a lot of other technical disciplines is it's very closely bound to the business. It's got a tie to the way the business is set up because often you're saying, okay, our management process is a certain way or an organizational process is a certain way. A lot of enterprises are very siloed organizationally. So your technology has to match that siloing. And so we would spend most of our time kind of pulling that demo apart and reconstructing it in a way that would work for customers. And so this was before the term microservices really existed. But we said, the better way to do this is instead of building this monolith identity system that you then have to pull pieces out and reconnect. Let's start from basics and build what would today be described as microservices for identity management.  And so we built that out. And what became really interesting was as we were building it out, it just meshed really well with the open shifting Kubernetes world because we had built these small building blocks that we said, okay, here's your Lego set. Here's a picture of what it could look like. But here are the 25 other designs that it comes with that you can do like when you buy Lego sets, right? So here's your Lego set. Go ahead, build it however you want. And it really turned both the implementation time on its head and the costs on its head. You know, one of the things, one of our rules of thumb was that your ratio of professional services to licensing dollars is gonna be two to one. For every dollar you spend on a license for software, you're gonna spend two dollars to implement it. We wanted to turn that on its head. And we found that by going with a microservices-like approach, a building blocks approach, our implementation times just bottomed out. And we were able to, you know, we had one customer, as an example, we replaced a long-standing legacy system that took them, I think, three years to get implemented. We had the proof of concept up and ready to go in three days to replace them. And at that point it was just provisioning hardware and applications and whatnot. So how have things changed since you started the company now with Kubernetes becoming mainstream and identity management in Kubernetes? What does that mean? So a lot has changed. We got started in Kubernetes back in the one, three days, maybe one, eight, whenever our back first came out and open shift at first come out. In fact, we had a booth at the first KubeCon NA in Seattle four years ago, when it was still small enough to be in a hotel lobby. Not small enough to do that anymore. Right. And so we actually originally got involved with open shift and then later with the upstream Kubernetes and with our back. And so we started with, so when you go to the Kubernetes authentication page and it talks about OpenID Connect, we rewrote all that documentation and donated it back to Kubernetes. We then went ahead and started to look at the way OpenShift and Kubernetes deals with identity. One of the things that's really changed over the last several years is this notion of what goes into your cluster. And we're gonna talk a lot about that during the demo. It's more than just Kubernetes. It's more than just OpenShift, right? I mean, you've got monitoring systems. You've got your GitOps system. We're gonna talk about our go CD today. You've got your build system. We're gonna talk about Tecton. You got your code system. We're gonna be using GitLab for that today. And all of these systems have their own concept of identity. And so specifically when you're looking at like an enterprise world, most of the implementations are multi-tenant. You know, it's most enterprises are looking for multi-tenant solutions. They're not, you know, most implementations I've seen that are where the tendency is at the cluster, that doesn't scale real well from a management solution. It, you know, there are advantages to it. And obviously you're going to have multiple clusters. But when all is said and done, the management process of multi-cluster doesn't scale when you're trying to have a cluster per application. So multi-tenancy becomes really important. And so identity is, you know, it's kind of like the force in Star Wars. It's, it binds everything together. You know, Argo CD has its own internal RBAC system. It doesn't work with Kubernetes RBAC system. It's got its own thing. GitLab has its own identity system. And then of course OpenShift and Kubernetes has its own identity system. So if you're going to provide a platform for your developers to be able to access these systems securely and to, you know, really get the IT people out of the room, out of the way, right? You know, the goal is, is that the people who own OpenShift are not involved day to day in applications, right? If, you know, one of the things in the identity world I always say is if I'm in the room, something's probably gone terribly, terribly wrong.  You know, it should be the same way with the people who run the Kubernetes and OpenShift deployments. If you're running OpenShift or Kubernetes and you're in the room during an issue, something's gone really, really wrong. Ideally your application owners are managing all of that process. So speaking of being in the room, we have somebody else from your company here, Brian. And he's sitting there down in the bottom left corner of my screen. Brian, who are you and how did you get involved with the company? Hey, great question, Mike. Thanks for having us on this morning. I go back 20 plus years in the identity access management space with some very large programs of record. The early days were extremely challenging to enable access to uniquely different data repositories. It suffice to say it was painful, time-consuming and expensive. Many development hours had to be built into these projects. Fast forward to 2011, I met an innovator named Mark Borschtine who had an answer for this challenge. He had started his own company, Tremolo Security. Most intriguing was his subject matter expertise, successful consulting background and the fact that he had developed his own IP to secure the authentication process and speed the implementation phase. Huge game changer for organizations leveraging their existing infrastructure to deploy a solution in weeks, not months. This resonates with all organizations concerned with cost savings, dedicated IT resources and securely enabled privileged access to their internal team contractors and partners. Okay, fair enough. Back to you, Mark. I couldn't help but notice when you were talking just a couple of minutes ago that there was something in the background there and I thought maybe you might wanna talk about something that's exciting, that's gonna be coming out here. Is there a book coming out, if I need to? There is. I'm gonna show off the book cover here. I'm gonna do a little bit of shameless self-promotion. So I co-authored a book with my partner in crime here, Scott Serovich on enterprise Kubernetes. So when we started talking about writing this book together, we found that there was a big gap in the knowledge out there, the written knowledge, I guess, on how you implement Kubernetes between enterprises which are really unique from kind of your more consumer facing companies. In enterprise, you have to work around the organization as well. Most enterprises, you might only have a dozen, maybe even less of these massive, truly enterprise wide applications, right?  But then most of your applications are these siloed systems that might have a couple of hundred to a couple of thousand users. And so the people who own it, it's the most critical application in the world. And they're now responsible for keeping it up and running and their paycheck depends on it, right? Their bonus depends on it. So we wanted to write a book with that in mind. So heavy focus on identity. So we have full chapter on authentication, our back authorization, pod security policies and open gatekeeper. And then a lot of the stuff that just, you might think is kind of mundane but is really important to managing that kind of a diverse environment. Backups, logging and log aggregation. And then what we're gonna demo here was one of the most fun things that I've done a while. Our last chapter, we said, we're gonna build a platform. We're gonna talk about how you build pipelines and then build a platform with the goal of not having to have, excuse me, not having to have a Kubernetes admin building these bespoke clusters. Everything's automated. Everything's done through GitOps. What we really wanted to handle with this book was to say, look, this book is more than just theory, right? A lot of books are theory, and they give you great information, but it's not necessarily always in a practical context. We have cookbooks, which give you really specific recipes. They'll give you great ideas and great knowledge, but they might not relate directly to what you're doing. We wanted to kind of go in the middle where it's a practical book with a lot of theory in it. So the thing's huge. I think it's 650 pages of Kubernetes. And there are labs in most of the chapters that you can go through, and everything's open source, it's up on GitHub. And so we had a blast. It's coming out on November 6th, and then anybody who wants to get their hands on it, we have a discount code. We'll have it on the last slide we put up. It's 25 Kubernetes. You go to Amazon and order it there. You'll get a 25% discount. I just linked it in the chat as well, but we will have that up on the last slide, as you said. Awesome. 650-some-odd pages. I can't wait to pull that down. Yeah, it can be used as a doorstop if you really don't want to read it. Right, right, right. Well, demo time? Can you show us something? And hopefully, there's going to be lots of terminal windows and manually editing config files or prove me wrong. I promise we will not manually edit a single config file. So I'm going to go ahead and share my screen. And everybody can see what's going on here. We've got a lot going on on this demo. So when we're done, so when we built that final chapter and we wrote the book, Building a Platform, I have a graphic where we automated the deployment of Argo CD projects, GitLab, and Kubernetes projects and Tecton so that they're all integrated. And I made this diagram of all the different objects that we had to create in their relationships. And this is just the one cluster because it was a book, right? It's not a production system. 20 plus Kubernetes objects. I think I had about 45 GitLab calls to create the various projects, forks, et cetera. And a handful of calls to Argo CD. Argo CD has a combination of its own API plus it's reliant on Kubernetes. There's some CRs in there to create all these relationships. And then you think about the automation part of it.  You want everything to just happen. So in the background, that's all built on web hooks. So you've got to create the web hook. You've got to create the secret. You've got to provision the secret. All these different things. It isn't rocket science, but there's just a lot of stuff to do. And so what we're going to show you is what the results of that are. Because it's one of those things that I could probably sit here for two hours and go through each little detail. Your audience will not enjoy that. Let's dive right into the demo. So we're going to show how we're going to integrate Argo CD, GitLab, and open use and open shift so that you have one kind of seamless process. As you're deploying your applications, you don't want to get your open shift team involved in having to set it up. So what we're going to do is we are going to provision an application through self-service request, create all the objects in GitLab, create the objects in Argo, create the objects in Tecton, link everything together, and then we'll show the progression of how that all comes about. So the first thing I'm going to do is I am going to log in as my user. Now, a lot of enterprises have sampled too. If you don't have a testing identity provider to work with, we actually provide one. So it might be something that you're interested in. Go to tremolo.io. So we're going to sign in as our user. And we're going to go ahead and create a new open shift application. Let's make sure that we get the right name. So we're going to submit the request. Now, this is going to be different from like your, you might be used to like an email where you have to request access via an email that says, okay, email that says, okay, let's go ahead and do the email shuffle of, hey, can you create this project? And you get these bespoke clusters. We're going to avoid that. So let's go ahead and now that the request is in, an admin would have gotten an email that says, hey, there is somebody waiting on a request. We're going to log in as an admin user. And you'll see that we got this open approval. Here is the request that came in. So let's review it and approve it. Of course, this workflow can be customized, however you need it. So we've submitted the request and take a look up here at the logs streaming through OpenShift. And you're going to start to see a lot of provisioning action here. There we go. So when we wrote the book, built this diagram to link all of the different objects we had to create. There were 20 plus Kubernetes objects that had to get created, probably about 40 GitLab API calls that were created. The Tecton objects or Kubernetes objects. And then Argo CD has kind of a mix of Kubernetes and its own API. You had to create all the webhook connections. So when you commit some code into GitHub or into GitLab rather, you want that to automatically trigger your workflow or your pipeline. You don't want to have to manually kick that off. So that's going to take a minute to provision all those different objects. We're not just provisioning objects, we're creating SSH keys on the fly. We're creating secrets so that your webhooks can't get hijacked, all sorts of good stuff. So let's take a look here, see where it is. Nope, we're still provisioning, I think. Nope, I think we have finished provisioning. And just to kind of prove my point of how many objects got created. Oops, I actually didn't want to log out. Let's come over here and look at our audit reports. So we're not just creating these things, we're actually creating an audit trail. So that way when it comes time to do an audit, you can tie all that infrastructure we just provisioned back to a single request and who approved it. So let's come down here to our actual provisioning and you can see this is our new application. Here are all the objects that we created. We created bindings, role bindings, groups, all sorts of stuff that connects everything together so that this all works seamlessly. So now that we are there, let's go ahead and log in to get lab. And we're going to log in as our original user, MLBIM6. And you'll notice that we just have a handful of projects here. We're also going to log into Argo. And we see the same projects here. So let's talk about these projects real quick. So let's start here, up here, we have our application built. So this is where the source code goes. This is where our actual microservice or application, whatever it is, is going to go. That does not have an Argo CD project. So that's just source code, right? Argo CD is purely for the operations side of things. So we're going to have a pipeline project. The pipeline project has all of our tecton objects in it because there are webhooks, there's security, you want to keep that isolated. And so that project does in fact have a Argo project. And we can see here there's a couple of stub objects that we created to support the webhook. We then have our operations project. So we have two operations projects. First operations project is our production project. And that also is linked to a Argo CD project. There's not a lot in there right now because it's an empty project. Additionally, oops, we have a dev project. Now what's important about the dev project is it is simply a fork of the prod project. So when it comes time to move into production, what we're actually going to do is do a merge request into the production repo and let Argo CD then go ahead and kick in and provision everything. So the first thing we're going to do is we are going to check in our source code. We're going to go to the application and I'm going to create a fork. It's forking, okay, good. So let's go ahead and check out our fork. Let's go into our application. So nothing spectacular there. We've gone ahead and we've put some code into our fork of the application. So we're going to put that on hold and come back to that. So next we're going to come to our operations code. So let's come to dev operations. We're going to come here to our Argo project as well. Now there's not really anything in here now. In real life you're going to want to fork this to do some work first but for this demo we're going to keep it simple. So let's go ahead and clone that and we're going to go ahead and copy our operations code. So what do we mean by operations code? We're talking about deployment, right? Nothing too crazy. Take a look at that in a second. So let's go ahead and push. Now we've pushed it into our dev repo and in a few moments here we can see that Argo CD is already on the job of syncing it in but we got this little broken heart. That is because our repository points to a container that doesn't exist. So we take a look here and it doesn't have a tag on it. We've got to add that tag. So let's go ahead and do that next. The next thing we're going to do is we need to check out our build. So this is actually going to do the work of building our code. So let's go ahead copy that and just to show what's going on let's go into the build project. So again we've got kind of our stubs here but we've got to build that out. We've got to add a pipeline. We've got to add bindings. We've got to add a question for the container too. So let's go ahead and do that now. Let's copy. Let's take a real quick look to make sure that the I think it's the trigger template is pointing to Python test 11. Okay, good. So now what's going to happen is we're going to add it. We're going to commit it. We're going to push it. So what's going to happen is our tecton pipeline we're going to talk a little bit about what that pipeline is doing is being pushed into Git at which point there we go. Argo is picking it up and saying yeah, let's go ahead and deploy all this stuff. So we want to wait until everything is green. So everything's being synced in. We now have a working webhook in a build environment. So let's go ahead and push some code, shall we? So we're going to go back to our fork and show you there's nothing up my sleeves, right? No pipeline found. So let's go ahead and create a merge request with our dev operations code or with our application code base. And part of that GitOps flow is once that's been submitted GitLab says okay, somebody's got to approve it and merge it. So once it's been merged you can see almost immediately Argo CD is off to the races and starting to do its thing with a build. So let's take a look at our pipeline. What am I doing wrong here? Python test 11. There we go. So we're off and running. So let's go ahead and oops. Pipeline run. Go ahead and watch this as it goes. So that's off to the races and we have three tasks in our pipeline. The first one generates an image tag based on a time stamp and also saves the commit hash that triggered the build. The second one actually builds the container. So we're using Koniko in this instance, that's a tool from Google very similar to Pogman same type of idea building a image without having to have a daemon. And then finally the last thing we're going to do is update our dev repo and in fact if we come here let's come over to dev. We're going to update our dev repo so that we're patching there we go. So we can see here the updated commit and what we did was we checked out the code from dev, the dev repo and patched it with our time stamp. So now our image has a time stamp on it and it also has the commit of the code that triggered the build so we now have something to reference. And so if we take a look here and do a quick refresh you can see that syncing and our dev instance has picked it up and now it's running a new pod. So this little broken heart is going to go away here in a minute. So there was no API call right? The pipeline checked out the code made the update pushed it back in. That was the final step. And all this requires a lot of automation because you need to build SSH keys out to do this, credentials, different things to do it that you don't want to be doing manually. You'll also notice so far I have not actually run the OpenShift command to do anything other than perhaps look at some logs. So that's kind of firing up here and we want to wait for the circle to finish and for us to be able to say, yep, it's running a good version of the pod and the broken heart has gone away. What's really great about this is that something to point out is that I as my application owner can see everything that's going on. I don't have to get the OpenShift came involved. I can monitor what's happening in Argo CD because I have secure access and we can see down here we're now at a green heart, the old one's gone. So we're happy everything's running. So let's go ahead and push this into production. So how do we push it to production? Well, it's GitOps, right? So let's go over to production and there's an error because there's no source code we can fix that or there's no operations code. So let's go ahead and push this into production. So let's create a new merge request and create that merge request into production dev and we're going to commit the merge. So now Git is our source of truth for all changes to operations. We've done no commands and OpenShift. Everything has been external to OpenShift. And so we take a look here in prod give it a second and there we go. It's launching up and it's pulling down and we can see that it's actually launching and we're all green. So we've gone the whole gambit, right? We went from requesting that an application be created provisioning all the infrastructure automated. We went ahead and committed our code a pipeline built everything and we didn't have to get the OpenShift team involved for any of it. Just to show you there was nothing up my sleeves. I'm going to go ahead and log out and show you here we only have the Python test application, right? So let's log out here and let's make sure we're fully logged out. Now we're going to sign back in to GitLab. This time I'm going to sign in as my super user. So you can see all the projects I have access to that my application owner didn't. That's because we're using the power of identity to know who has access to what and to bind these different systems together. Test 7, 4, 2, let's log in via OpenUnison here. Here's all sorts of projects that the user doesn't care about. So we're not just leveraging automation we're leveraging security to give you a better approach that is more hands-off for your team and is far more satisfying for your customers. What does it mean for customers? So what's the business impact of identity management in a multi-cloud environment? How does that affect the bottom line for customers? The biggest effect for customers is the fact that their IT departments or the people who own their infrastructure don't have to get involved with the day-to-day of applications. So a customer that I built a similar solution for we went live about a year ago and I hear from him once in a blue moose a hedge fund over in the UK, small as these things go, I guess a small hedge fund is like five billion dollars and their developers wanted to be able to launch micro services. But they didn't want to have to get the IT infrastructure side of the IT department involved. So we set up a very similar solution for them where their developer would log in and say create me a project. Now we based the permissions off of their active directory so there was no request approval. But based on that it provisioned out everything, it provisioned out the Git repos, it provisioned out the build systems, it provisioned out the namespaces, it tied everything together. And so the developers were then able to say hey I'm going to just go ahead and start pushing code and we actually gave them a little button so that they could say I'm going to push from Open Unison, from the Open Unison portal rather than from inside of Kubernetes. And he's like yeah I don't get phone calls. I mean that is one less thing that that guy has to manage because at the end of the day we all have better things to do than building bespoke clusters for people. So it really becomes a force multiplier people are happier because they're getting their job done, they're not complaining oh I don't have access to this, I don't have access to that. And really you're spending hundreds of thousands, maybe even millions depending on the size of your organization on this automation solution. Do you really want to manually onboard people? It doesn't work well. So it really becomes a big force multiplier there. You earlier in the discussion you interchanged the words Kubernetes with OpenShift and I would imagine that your technology and your solutions work on any Kubernetes based implementation. Not just OpenShift is that correct? Sure, yep. But we have been working with you folks for years. You guys are a member of OpenShift Commons you have a Red Hat certified provider for OpenShift which means that it's gone through the Red Hat internal testing and blessings so when customers want to use it they know it's tried, tested, trusted and they can get support from Red Hat and your company at the same time. So I did want to put that gratuitous plug in there so thank you for doing that. It makes a big difference for customers when they want to go and run these things absolutely. We're a security company we're going to the CIO and saying we're going to help make your infrastructure more secure and being able to say and we're certified on the platform that you're using. We're here in the DC area, back in the before times when we used to go places you go on the metro and they're signed everywhere. 100% of government agencies run Red Hat Linux. That's not hyperbole that's true and so in the enterprise being able to say yep this is certified on the platform that you're using we had to go through their rigorous process they had to review it. We're also in the Red Hat marketplace so that's an additional avenue to be able to get access to but we have we made big bets on OpenShift very early on in our Kubernetes journey and those bets have definitely paid off. So war stories. Everybody loves a good war story you've been in the security business for quite a long time both at your company and previously tell us one of your favorite war stories that you've addressed. So honestly one of my favorite stories is actually before my time at Tremolo is one of the inspirations for the way we approach infrastructure. So while I was still with PWC I was on a project where we were helping a customer a name brand that everybody's heard of and everybody's used was migrating between different identity vendors. I was brought onto the project and I was told look you have a limited number of hours to get this done. 400 applications across six continents here are three or four developers in India just have them go and manually update the configuration. That sounds like a terrible idea I don't want to do it they're not going to want to do it and it's going to be error prone and all sorts of problems. So I said look I'm telling you we can automate this we're going to come in under budget customers going to be happy they're going to have a much better product and they're going to have a much better time and so got with the team in India and you know there are always issues with different time zones and whatnot to be able to get that done but we all were able to work together and build this amazing system and this was before DevOps DevOps wasn't a word yet and so we were able to build this system that queried the APIs of the old system constructed out a framework tested the old system to make sure that that framework worked the way we thought it did provision that and automatically into the new system test the new system and then turn it all on automatically and you know the project went really really well for the most part we did have one issue we accidentally turned off SAP in Japan which didn't really go over real well but we fixed that pretty quickly but then we went ahead and once we got that you know figured out the original go date we had to cancel because our product owner our project owner from the customer had to have an emergency appendectomy remove his appendix in an emergency appendectomy I think appendectomy there you go I'm not a doctor but I do plays so you know he said no I'm not we're not going live with this okay well I was promised to another project so I had to go and they delayed the rollout three weeks and I got a phone call one day I was like yep done I was like wait really yeah no bridge call we threw the switch and everything just worked and it's like we came in under budget we automated everything people were happy with it of the 400 applications they were able to automate like 395 of them and so that was a big inspiration for for the approach that we ended up taking when we started trouble getting into the automation space hmm you mentioned early on here today when we first started talking that you're not the marketing guy that you're the big brains you're the techie behind it all and that your other co-founder is more of the marketing genius of the company he's not here today what would he want you to talk about and bring up for the audience that you haven't covered so what I'm trying to prevent is the second we end the show you get a phone call from him and he's like why didn't you talk about XYZ so here's your opportunity to prevent that phone call from happening so I guess the biggest thing that I'd want to let people know is that everything I showed is not vaporware right it's real it's it's out there we're constantly involved in the Kubernetes and OpenShift world if you're asking questions on either OpenShift Commons or in the Kubernetes Slack channel we're gonna be there and we're here to help we are we're experts I'm a CKAD I went through that certification process the dark ugly truth of most enterprise software is that the people who write this stuff never have to use it we use our own software with customers we're out there deploying it we're making changes as customers need it so we're not just building in fluff features that nobody is going to use we're building features that people are actively using actively need and so as you're kind of going through that journey of figuring out how you're going to automate your infrastructure think about tremolo security think about how you're going to automate your infrastructure with security in mind okay so your books coming out on would you say November 4th correct November 6th November 6th okay and we have the 25% discount code that's going to be available for any of the use of the listeners from the show it's good in the U.S. only until November 15 what I will say because I know a lot of folks especially in the open source world care very much about these things is that if you do go direct to the publisher once it's available it's DRM free I'm sorry it's DRM free if you go directly to packet who's the publisher okay I linked it in the chat for those people that are on the bridge here why don't we go ahead and put that up on the screen so everybody else who is not here with us today who's going to be watching this later on can get that URL and of course you can find us on twitter you know our github repo where we have all sorts of fun stuff even beyond identity so you might end up running into you know we have like an SMTP black hole that we keep updated that's really useful we hope you all the best with the book I think I will obviously be pulling down a copy using my 25% discount code where are we going to see you next you know in this world where everything is virtual these days we're not going to see you physically in person we're not going to see you on humans or the Red Hat Summit but where can we see you next so actually I'm going to have the great pleasure of giving a lightning talk at the KubeCon NA virtual security day I'm going to be talking about why you should be using OpenID Connect with your clusters and not certificates for authentication so that'll be my next kind of big thing that was at November 17th right I think the yeah I think 17th is the security day conference it's a co-located event correct it's before KubeCon starts good well I would like to say on behalf of everyone here on the OpenShift Commons briefing our that we'd really appreciated having you join us here today I think we'd love to have you come back again when's your next book coming out we'll bring you on sounds great and thanks so much for having us Mike okay great well thanks everybody I hope that hope that this was informative and useful you can tune in every Wednesday at noon time and we have a full lineup of software partners booked out all the way I think we're booked all the way into March at this point so all of our software partners with Red Hat Certified Operators for OpenShift we're going to be here on the show talking about their technology their products their war stories and hopefully some more books thanks again Mark and we are signing off for the day thanks for joining


2020 presidential candidate Jay Inslee, who is the governor of Washington. He's basically running on climate change That's his number one go-to issue and he's not my number one choice But I do find what he's doing admirable He's trying to draw attention to climate change and he originally floated this idea that we hold an entire debate on Climate change itself now I wasn't sure how to think about that at first But the more I thought about it the more that I loved it because we have an entire party 50% of elected people in power who deny the reality of anthropogenic climate change So if you got more than a dozen candidates running for president on the stage for more than an hour, I'm assuming and They didn't debate whether or not climate change is happening But they had a real debate on what to do about climate change that really could be an educational Experience for the American people because you're not setting up this false debate between whether or not it exists Or it doesn't you're debating what the best plan of action should be so I absolutely Really like this idea. Although the DNC who sanctions all of these debates They responded and they said no now I Think a lot of people will probably question. All right. Well, they said no, but why not just have the candidates Subvert the DNC and have MSNBC or CNN host a climate change debate Well, you see the problem is that the DNC once again brought back this exclusivity clause meaning that if you participate in a non DNC sanctioned debate you will be barred from participating in future debates So if the DNC says no debates on climate change There will be no debates on climate change if you want to get into future debates now of course since a lot of people namely young people care a lot about climate change this wasn't a very popular decision and Tom Perez was confronted by activists because he shot down this idea So he defended himself Here's what he had to say as Christina Cabrera of talking points memo reports Democratic National Committee chair Tom Perez told environmental activists that it would be impractical for the party to host a primary debate on Climate change according to a Sunday Tampa Bay Times report on Saturday The activists confronted Perez at a gala in Orlando, Florida and asked him about the party denying 2020 Democratic candidate and Washington governor Jay Inslee's request to hold a debate for the candidates to discuss solutions to global warming Perez told them that once you have one single issue debate then every debate leads to become a single issue Debate in order to address the concerns We will have issue areas in debates including but not limited to climate But it's just not practical for us to have one debate on democracy reform one debate on voting But chairman said and as someone who worked for Barack Obama the most remarkable thing about him was his tenacity to multitask and a President must be able to multitask Inslee who's made climate change a cornerstone of his campaign expressed disappointment on Wednesday when he announced the DNC's decision the DNC is silencing the voices of Democratic activists many of our progressive partner organizations and nearly half of the Democratic presidential field Who want to debate the existential crisis of our time Inslee said the climate crisis merits a full discussion of our plans Not a short exchange of talking points. Yeah, so I'm actually siding with Jay Inslee here I think Tom Perez is wrong and his reasoning is completely bogus. He's using the Slippery slope argument, which is a logical fallacy Because what he's saying is we'll look if we allow for a debate on climate change Then we're gonna have to allow for a debate on healthcare and a debate on Democratic reform and you know once you open up that door then it just becomes a little bit too You know a little bit too difficult to manage. So let's just keep it to multi-issue debates and that's that except a slippery slope is a logical fallacy because it almost never comes to fruition and in fact since the DNC is Sanctioning debates you can say All right, I'll I'll allow it on climate change and then no other debates will be a single issue oriented debate Everything else will be you know various issues, but for climate change We will allow for this one exception But he's saying no And then he says I worked for Obama and he was a fantastic multitasker So if you're gonna be the president you have to be able to multitask That doesn't even make sense. Like what does that have to do with talking about climate change? Here's the thing about climate change. This issue is unlike every other issue. It's so incredibly important It's literally an existential threat to humanity It is more important than any other issue. The only other issue that you can argue is relatively equal in terms of importance is Campaign finance reform because it's going to be difficult To get climate change Legislation enacted if you have these fossil fuel industry Shills and these oil and gas companies bank rolling politicians But with that being said climate change is such an important issue That it totally makes sense for you to allow an entire debate on this if we Put these candidates in front of a national audience And people get to hear them talk about solutions to climate change for two hours Can you imagine the impact? That could have it would be really educational But tom pares is shooting it down and he just his reasoning is really bad. It's a slippery slope Okay, but you're the dnc chairman. You can stop that slope from being a slippery slope like it Okay, whatever, but you're not making much sense here tom imagine how awesome it would be to see Each candidate present different plans as to how they're going to tackle climate change. That would be incredibly Incredibly constructive and eventually somebody is going to win and go up against donald trump What's that debate going to be? It's going to be about. Oh, well climate change is real versus climate change is not real When that's not The range of the debate with regard to this issue We need people to see that this is a very serious issue and here's a whole range Of policies that we can address climate change with But you know, it's it's just a missed opportunity, right? It's a missed opportunity If you're looking about This in terms of the broader impact it could have on political discourse with regard to anthropogenic climate change And people acknowledging how important it is then having presidential contenders debated could do a lot It could raise awareness about this issue, but You know Tom Perez is rejecting it. So I guess we don't get to Debate climate change now. Will it show up? At the democratic party debates. Yes, but will it be given the amount of time that is justifiable? Absolutely not given the scale of this crisis So I support having a debate exclusively on climate change And I hope that J. Insley as well as others fight it But um, you know, it's disappointing because this could have been really informative educational and just overall constructive


A team of us from the Open University's Children's Research Center and the Psychologist-led Organization Children Heard collaborated to analyze international survey responses in four languages from 240 children aged between 3 to 12 on their thoughts, feelings and experiences of living through the COVID-19 pandemic. The report argues that children's voices are missing from the pandemic response and that they have questions which remain unanswered. As researchers, simply saying that we are going to listen and be reflexive isn't enough. My experiences of doing research with children as co-researchers taught me that it takes time and attention to hear what children say. Ironically, I found myself writing a reflexive memo asking, why was I so charmed and delighted by one of my co-researchers' engagement in the research with me? Why was another co-researcher's response so unexpected? However hard I tried, I couldn't escape my social conditioning as an adult, whose instinct it was to protect, make allowances for co-researchers' lack of experience of the world and so to be delighted by insightful responses. It was only over the course of a year or more that I was able to truly respect their research offerings as those of a citizen of the world just like me. One who's concerns about COVID was for their communities, how other people were coping and how their governments were responding to the pandemic for them. What is the most difficult decision you make on what to do to keep us safe? Why did hand sanitizers become more expensive so it was harder to buy them? Why do you use a virus for your political career? You can be kinder and not scared of us. What is the most spot-missed stick for your music? What was most impactful for me from our analysis of the survey findings was the direct nature of children's questions. These were some of the questions posed by children aged 8 to 12. They were answering a survey online, but they could equally have been in the room with policymakers and decision holders asking their questions. Children knew what was happening in the pandemic and their questions for decision makers remained unanswered. Their questions are important and showed a nuanced understanding of not only their own situation but also demonstrated a deep concern for those in power. I'm not sure many adults would have asked about optimistic visions or shown the same concern for the difficult decisions that were being made. Where are the places children go to have their questions answered? Parents and caregivers don't always have the answers and unlike Norway and New Zealand where the government's held press conferences for children, there were no authorised spaces for children to take their questions and to have them answered. As we report in this research, the pandemic was not only a global leveler but a generational one. The big question for me remains, why don't decision makers listen to children? What could we as a society have gained by taking the time to invite children to share their questions, listen to their concerns and for their questions to be answered? As a Children's Research Centre, we will continue to lobby for organisations to work together to prioritise listening to children.  It's all over the world, it's dangerous and I'm not comfortable. I wonder whether this will end and if mum and dad are in danger. We take measures, wash, disinfect, wear a mask, stay at home to prevent the spread of the virus. I want us to stay healthy. To me, the narratives, insights and observations children share with us demonstrate that children's honesty and sensitivity is a particular strength. Children show willingness to express their feelings. They make their struggles and experiences visible which to me is courageous and shows openness that is often in my opinion missing in a public discourse. Children are not afraid to ask questions and be part of conversations. It is now up to us how we engage with and respond by acknowledging and co-shaping such conversations in our homes, schools, communities as well as at a government level. Also what strikes me is the us that children keep coming back to in their narratives. The us is however also something that is often pushed aside in our responses to the impacts of the pandemic. Children emphasise the importance of relationships and communities for our health and well-being and show that if we are to strive for the pandemic we must learn to help and care for each other. This research led to multiple assets a project report and an affiliated child-focused poster for practitioners and researchers to use in their Covid recovery work with children. We have also co-hosted Children aged 0 to 11 and Covid-19 a conversation event attracting 200 attendees from across the third sector public services and higher education with key notes from Professor Carol Robinson and the Children's Commissioner for Wales. A key element of the online event was the curation of a virtual and interactive research gallery showcasing the work of 25 other research organisations and we are looking ahead to organising an international conference later in the year. Responding to our project report's recommendations we have mobilised an online resource with our sister centre the CCW called the Our Voices Initiative to enable practitioners and children to research together. The aim is to facilitate children's voices in research and offer them a shared space where their questions could be heard and conversations had.


Oh my goodness. I'm so happy and it's very excited in my life. I'm very happy. How about you? Amazing. I'm so excited Yeah, be good. Once I give the little heading on to the Chancellor. Great way to celebrate and milestone We've achieved at the end of the road. It's really great. Pretty surreal. Yeah I'm just happy we made it to the end. Yeah Have the degree never thought it would happen, but it did Like don't take any moments for granted. It's a really good culture if you get involved. There's so many International people you get to know everyone from everywhere and you get so many different perspectives of people and yeah It's amazing. Just to try and see that there isn't any insight and to look to your friends for support. Be a nice person and go to your classes I think it's very important to do so. Especially if you're having fun while you're studying as well as Massive so getting involved with sport or just making friends. It gets hard and you wonder why am I doing this But keep going you get there. It goes quick. That's all worth it. Just try your best to do your best. That's all


My name is Davison Gumbu. I am a regional scientist with the Centre for International Forest Research responsible for the Zambia Country Office where we have been focusing primarily on charcoal production as well as creating or developing a monitoring reporting and verification system for the Zambia. This entails primarily providing additional evidence to the government in terms of the status of forest resources in one site here in Zambia. In this site is the Njimba District. The charcoal scoping study was driven by the need to provide evidence to the general public on where the charcoal was coming from, who was producing the charcoal, how the charcoal was being conveyed across the country and what policy options needed to be taken. If you read any average document in this country it will talk about charcoal as a major driver of deforestation but what has not been done in the process is to kind of say what is driving that production itself, who is doing it and why they are doing it. So we set out to prove that, to look at the socio-economic implications of charcoal production in addition to what is already existing which is more to do with the ecological issues pertaining to charcoal. The findings have been varied but primarily focused on the issue that charcoal is produced widely across Zambia and wherever there are trees people are producing charcoal. It is an easy business to get into. There are no tenure constraints in terms of where you cut and what you cut and as a result people use it as a safety net and as well as a major source of income for the household. I think the reaction we got was that they are going to run a charcoal endeavor, a national meeting to discuss some of our findings as well as other work that has been done on charcoal. I think we saw in the last couple of months I think that there has been an attempt to actually address charcoal issues by government but primarily from a point of view of law enforcement. The Nyemba Forest Project is a USAID funded project primarily meant to generate additional evidence for use by what we call the NJP or the National Joint Program which is addressing red preparedness in this country and red being reduction in deforestation and degradation. We have two main thrusts really that we are looking at. One is generating a sub-national MRV or Monetary Reporting and Verification Program that will focus primarily on the district level. Two, we have also discovered that it is not worthwhile just to develop that sub-national MRV if you do not look at what happens at the coming level. So we introduced in this case participator forest inventory at the village level to complement what we are doing at the district level. The data are just coming in at a very early stage and I think that maybe by March we will have a comprehensive dataset. The signals we are getting from the local level is yes we want to use this data, show us how to use this data so that we can make better management decisions of our forests. I think that is a challenge we are facing at the moment. I think at different levels people appreciate the project in terms of data generation. It is well understood by surprisingly by the traditional authorities who think they will use the data for bargain purposes. At community level just knowing where your resources are seems to be the most important issue coming out of the project. I think we also noted that as we were carrying out the various inventories some of the species that the communities thought were no longer there we actually discovered that they were there. And in the process we also found a lot of illegal activity which clearly showed that these forests are still alive and they have got resources that communities can use. I think what we have done so far I think misses only a few issues that I think need refocus. The one area where we really need refocus is a better understanding of deforestation in this country. We need to start off by actually saying what is deforestation, get it defined, get it better understood and see how it fits in within our present understanding of research. The second issue that I also consider very important is that we see a situation whereby there has been a lot of studies done. But because research has been limited we are basically recycling the same information and arriving at the same conclusions. I think a typical case is Chaco where everybody says Chaco leads to forest loss. But when you look at Chaco very closely where does it take place it is done in conjunction with agriculture expansion. So the question is what is it Chaco that comes first or is it ag expansion. So these are some of the issues I think personally we should now be looking at instead of just simply stopping at those studies that have been done and recycling the information in those studies.


You know, me and Ice T, we have a report, that's my guy. You know, he pick up the phone when I call and likewise. So, I got Jason Lee, you know, coming to the show. That's hard. I have Adam 22 from Nojumper, you know what I mean? Man, I tried to get him here. Yeah, we tried. Me and Adam 22, I tried. I know already some things have him down south, baby. Don't forget about me. Let him know when you talk to him. Say, hey, man, he a good dude, man. Yeah, oh, for sure. You know what I'm saying? Yeah, Adam's cool, man. And you know, I even want to get glad on the show. You know what I mean? Yeah, I got to ask you about all these interviews. You did Snoop Dogg, you did Boz, you did. You didn't think you were sending me Boz? I mean, big Boz was the dopest interview, man. Yeah, man, that's my brother. The way he be answering the questions, the way he be, man, his demeanor, all that, man. I'm loving everything on that. Yeah, Boz is like Yoda, man. You know what I'm saying? But you've done everybody there. I see everybody on the show. Who do you want to do next? Man, that's a good question, bro. I got Ice-T coming again. He's spending the block. Yeah, I got him spending the block. Jason Lee, actually, I don't know when it's air, but next week. Y'all going to do it? Yeah, for sure. Ice is the homie. He wanted to come in. I called my call, and I was like, I wanted to do it while I was out here. But my guy told me, no, we going to New York. Yeah, don't try to mess with it. Don't try to mess with it in LA. Do we flying in? Is it going to be dope or let me do it my way? I said, OK, I'm going to pull up. My boy got him out there. Yeah, yeah, excuse me. Ice-T, he hit me.  We in? 17th of February. Wow, you going to be out there? Oh, yeah, for sure. You know what I mean? But you know, me and Ice-T, we have a report. That's my guy. You know, he picked up the phone when I called and likewise. So I got Jason Lee coming to the show. That's hard. I have Adam 22 from No Jumper. Man, I tried to get him here. Let me try to get him. Adam 22, I know already, there's some things how I'm down south, baby. Don't forget about me. Let him know when you talk to him. So hey, man, he a good dude, man. Yeah, oh, for sure. You know what I'm saying? Yeah, Adam's cool, man. And you know, I even want to get Glad on the show. You know what I mean? You know, Vlad?  I don't know what. You know, Crunchy Black called him Glad. I call him Glad. I told him that the other day. I was like, we need to get Vlad on the show. Yeah, yeah. And I know Glad gets, you know, he gets flat. I personally like his show. He's good at what he does. You know what I mean? I can't be mad at him. I mean, I can't be mad at him. I think I do get a little area about different things that have what happened over the years. But everybody's evolving, man. Yeah, everybody can't be put in the box if you can't never get out. No, that's true. That's true. And I think that, but then it's like a catch 22 because me being on the other side, right? You know, we do podcast and ours is a conversation. So he's kind of more of a journalistic investigation type thing, right? So he's going to ask you the uncomfortable questions and the hard shit, right? That's his job. Now, it's your job to understand how to respond.   It's my job to say what? What do you say these things for?  That's real. I'm not going to come up in here. Yeah, bro, you know what? Let me tell you, E-Brustle was just one of you, right? Like, that's what I'm going to do. And then you do that. Like, I got some partners. Listen, let me say that. I got some partners this. They steal street, right? And they be asking, can I come on the podcast? And I'll be like, why would you want to come on the podcast? You have to check them. And then they'll tell you, man, you right. Man, my boy be laughing about that. The other side of it is the integrity. Now, if I did say that, if I did say that and do those things, if I did say and do those things, it would be up to you to say, well, you know what? I'm not going to do him like that. Yeah, I'm going to use. I'm going to protect him from himself because I've done it too. You have to, you have to, man. You got to look out, man. That's the thing like people, you can do better. You don't have to do everything, try to get cloud of views and all that. It's more about integrity, too. We got to agree. That's why me and my wife sit here because that's why court don't mind sending somebody else. Big court is going to say, man, go talk to them because you know there's going to be some guidelines there. And I always say family. People ask me all the time when I say, well, man, what you think? Ba said the same thing. He said, hey, what you want me to say? I said, man, they family. They good. Thank you so much, man. Still, I said they family. That's all right. I say that all the time. Man, thank you so much, brother. The funny thing when you're talking about Big Boss, like one of my favorite parts in his interview was when he was talking about Master P.M. when he said that they went into that, the condominium. Yeah, for sure. And did you see that part? I loved that part when he was talking about how he respected him because of what he said. What he stood for. What he stood for and then he walked out. Yeah, yeah. Did he say that on your show? Yeah, he did.  But the thing about it with Boss, like Silk said, Boss is, he is, he's, yeah, Boss is, like I say, he's like Yoda, bro. Like he's very wise, you know, and he understands a lot about life, you know what I mean?   He gon' tell you. That's on you.  You know how he talk?  Oh, he's serious about it too. That's on you. He ain't gon' really show no expression toward one way to the level, to the way he gon' keep it. But then, you know, one time, let me tell you a story about Boss. I remember one time, I tell you how God working, just when you have a brotherhood and you're connected. This was maybe a year ago, you know.  You know what I mean? And I think I was having one of those moments. I hadn't talked to him. You know, it just be today, right? He called me out to clear blue, you know, and he just was like, bruh, yeah, I just want to tell you, like, man, I'm proud of what you're doing. And he was like, man, just stay the course. You know, I promise you, he, I hadn't talked to him. He just randomly called me and told me that, you know. And it was like. How did he, he was like, man.  And I was doing some other stuff with a TV show I was shopping. And he was like, man, you good at what you're doing. You know, you're coming into your own in this space. You know, he was like, man, don't trip on the money. Just, just do, just keep doing the work. But I needed to hear it at that, at that moment.  It was very random. It was random. He called me out to clear blue.  I got to get Snoop on boss talk. Yeah, yeah. I got to get Master P on boss talk eventually. Yeah, for sure. It's coming because I'm going to be honest with you. I'm going to keep working. Sure. And I'm going to keep on connecting the dots. And then I'm going to keep calling you from blowing your phone. For sure, but you know, I answer when you call. You always answer, man. Yeah, we on boss talk one on one, one on one. Yeah, we going to talk.


Item Number SCP-886 Object Class Safe Special Containment Procedures SCP-886A Alpha and SCP-886A3 are to be kept in dedicated humanoid containment suites at BioSight 66 and allowed nutritious rations three times daily. SCP-886B21 through SCP-886B23 are to be kept in containment chamber 886-Delta designed as an appropriate climate-controlled indoor paddock on-site and provided with appropriate feed. Additional members of SCP-886 may be bred if appropriate reasons for research are presented. If research is not being undertaken, offspring of both SCP-886A and SCP-886B are to be destroyed immediately after birth. Descriptions SCP-886 is the collective designation of unique mammals capable of cyclic asexual reproduction. SCP-886A are identical human females, homo sapiens of Irish descent SCP-886B are identical female domestic Irish goats Capraegogreus hercus. Members of SCP-886A and 886B develop and behave as expected of ordinary individuals of their species and are completely ordinary outside their shared anomaly. SCP-886A Alpha is the oldest and presumably original instance of SCP-886A. SCP-886A is a human female, age 37, of average intelligence and stature. Once a year during the spring, SCP-886A Alpha will spontaneously become pregnant and carry twin instances of SCP-886B to term. Gestation mirrors that of a standard goat, averaging between 140 and 160 days. Instances of SCP-886B will be female, with white fur and of average size. SCP-886B are friendly and notably docile, having never displayed any form of aggression towards humans during containment. The milk and meat of SCP-886B may be consumed safely. The anomaly does not appear to be infectious. At the age of two and a half years, each specimen of SCP-886B will spontaneously become pregnant, each with a single human infant. Infants born of SCP-886B are genetically identical to SCP-886A Alpha, designated SCP-886A-XX. SCP-886A-XX will develop as normal human females until age 15, when they will begin to exhibit the anomaly in the fashion previously described. SCP-886A Alpha does not know how or why she began to exhibit her anomaly, only that it began suddenly and without warning. Similarities between SCP-886 and SCP-2910 have been noted. An investigation into whether SCP-2910 is a variant or altered version of the anomaly seen within SCP-886 is currently ongoing. Addendum. Recovery of SCP-886. SCP-886A Alpha was discovered by embedded agent Donnelly when a local newspaper released a story regarding her anomalous pregnancy in a weekend column. A cover story revealing the column as a piece of short fiction was released and associated civilians were altered appropriately. A task force was called to the area, and SCP-886A Alpha was extracted into the guise of a car accident. Family and friends are being monitored for further anomalies, with special attention paid to the subject's sisters and daughter. Lesson complete. If you missed the previous orientation, go watch SCP-885 Living Vacuum, right now. Or for the complete course, watch this playlist.