Today's episode is sponsored by Kenhub. Learning for fun is often like growing a tree. There's absolutely no pressure. While you nurture the growth of the foundation and trunk and then begin to add the bits of details that ultimately make you an expert. Learning for school on the other hand, total opposite story. So today we're going to talk about how you can use that same simple tree method to help you learn something better on your medical journey. It's the same method that I use to help me get a 3.9 gp in medical school. Let's break it down. Now to understand how the tree method works and how to properly apply it, we have to first understand why normal typical lecture approach doesn't work.  So at this point you're really hoping for two things.  So as soon as the lecture starts you start doing your typical note taking system of writing, typing, highlighting, whatever it may be to create notes that ideally will be useful when it's time to go home. And fast forward in an hour later you're actually proud of the art that you now call your notes. But internally you're also starting to feel this anxiety grow because you know some of it's already starting to unfortunately look confusing. And if it's confusing now, it's sure going to be confusing in a week or two weeks from now when you have to start studying the coils or the tests using those notes. And that sheer amount of information of those big topics, the details, the charts, the bullet points, what do you really need to know and how do you master it? Well that's exactly where the tree method comes in. Now there's really two ways you can do this, the traditional method and my personal favorite, the Q&A tree method. I'm going to show you both step by step using a sample lecture exactly how to do this. But the goal ultimately is exactly the same, learn in both pieces as well as in organized fashion. So kind of demonstrating the first traditional method, we're going to take this example lecture that I've used from medical school for quite some time on these YouTube videos. This is an example video on e-fifth. And so this will be your traditional PowerPoints of lots of words, lots of data, and it's just busy. If you don't know anything about this topic, it can seem a little bit overwhelming and multiply this by three or four lectures that you may have a day in medical school. It can be a lot. So let's talk about how you can take a lecture like this and break it down piece by piece into something that's easy to learn from when it's time to go home. Now the first part for really any lectures to understand what are those big ideas, those big branches and trunks that you have to make sure you master before focusing on these little pieces of details and facts. And if you're not sure what they are, often they end up being the highlights or the headings of a lecture. So for example, here we're talking about ephib. So epidemiology is kind of one of them in the first few. These first few slides are talking about just people who get ephib. The next ones are kind of signs and symptoms and then basically how to diagnose somebody. And then we talk about workup, which goes with any disease. And then finally you get to a predictable part about treatment and the different ways to treat. So even as I'm looking through these slides, all of these are talking about treatments, but there's specific parts about treatments that they're breaking down even further. So I'm already starting to see an idea of where my trunks are, where my little branches are, and then those tiny bits of details that would end up being the leaf in this tree. So for this lecture, if you're somebody who likes taking notes through an outline, I may just take a word talk and go ahead and write my big trunks and branches that I would want to know. So epidemiology, we talked about symptoms, we talked about workup, and then we talked about management. These would basically be the branches that I would want to know and master. Now within each of these, as you can see from the slides, there are even more breakdowns. You may be able to see them through kind of individual bullet points that have more bullet points underneath them. So for example, they talked about the path of fizz of how somebody ends up getting AFib and then who's affected. Those are kind of categories. And then all these little bullet points would be going under this section. And now if I go to the next slide, we're talking about data, which we can come back to later. We're also talking about how to classify it, right? So different types of AFib. And then if we're looking from this slide, I can already see that they're just talking about related diseases and causes. Now when you're first making your tree method, you may find that at the very end there's going to be duplications or redundancies and you can take those out. But this is kind of an initial structure of what this tree will look like. Here's my big trunk for epidemiology. And here are all the things that they want me to make sure that I master by the time that I review this multiple times. Now if we go to the next truck, we talk about symptoms. So I have kind of the more basic symptoms and so, you know, classic presentation, maybe one of them. But on this next slide, we're talking about not only symptoms, but kind of more pathophys of who's affected and then risks downstream. So for example, I can see risk of strokes, risk of CHF and just dying in general. So those may be things that they want me to master on those sections. Now if I get into workup, we're going to go ahead and learn some basic workup and I can already see EKG workup, Echo workup. Now if I go to the next slide, I see a busy table and chart like this. And if I'm not familiar with AVID nor have I taken any notes or gone to lecture, this is going to be a lot. So I'm just going to make sure that kind of keep this in my mind and ask myself where this is going to go or if I need to create a new branch for this by the moment, we're just going to keep going. And now we're going into management treatments. And so we can see that there's going to be multiple different categories. So first is going to be prevention. And then next is going to be treatment. And then we can see how in treatment there's already a rate treatment and there's going to be a rhythm treatment. Now this is kind of an initial pass of the lecture. You can easily do this before going to class or maybe the five or 10 minutes before your lecture actually starts presenting to understand what pieces of details and categories you're going to be focusing on before anything really starts. But now we want to make sure that we get those extra bits of branches and details that we haven't quite gotten yet. So for example, if we just stay just in the management section, we can see how there's a score called a CHADVAS score. Maybe I need to know that. So stroke risk, scoring, and then it talks about anticoagulation. So clearly I'm going to have to know something about that and I can see what else they end up talking about. So here is more of a CHADVAS scoring that they're talking about. And here they're talking about the different types of treatments. And so I'm sure that I can either spend time now or understand that when I get to this anticoagulation section, there's going to be many bullets within them. So for example, when we use warfarin versus one of these other medications, so dox, indications for each, and the same thing for the rate and the rhythm. So I need to know drugs I can use and the same thing for the rhythm. And we can see that quickly as I'm scanning, I'm seeing treatments that are more like therapies versus just meds. And this is what we're getting through just an initial pass of the lecture. So you can do this on the spot as your lecture is presenting, or you could do a little bit of this beforehand and then add this. Now keep in mind that this framework, this tree has room to grow just like any piece of learning does. But now I know that if I'm going into lecture, these are the things that I'm paying attention to. And thus when I come home, I'm going to make sure that do I know the basic management of taking care of somebody with AFib before I start worrying about the indications for each specific blood thinner that they may have to take. If I don't know that they need a blood thinner to treat AFib, then I can't answer these questions. So you can already start to see how a tree method makes you focus broadly first, and then gets into the nitty gritty. Now the decision to create an outline of a tree method like this, either before class or during class is completely up to you. It's a personal decision. If you're somebody who is a fast typer and you can do this on the spot, go for it. You're somebody who has a professor who talks really quickly or somebody who just has very busy slides like this one is a great example of just lots of words. You can barely read some of the smaller texts. That may be useful to just spend a five or 10 minutes per lecture beforehand, either the night before or the morning up to create the structure. That way you're just ready to type in the details versus the individual parts. Now when lecture comes, you can go ahead and add the parts of the bullets that are there. If you identify more individual branches that help you kind of compartmentalize some topics even better, even, you know, you can go ahead. So for example, here on this slide, we're talking about workup. And if we're just looking under basic workup, we have a bunch of things listed out. But maybe the professor goes into more details about each of those or maybe a few of them. So maybe they are mentioning a few things on the HMP or they're mentioning why TSH is something important to check. Or maybe they mentioned what you may want to look at on terms of their electrolytes to see if that's the cause. So you can basically go ahead and add those small branches and those leaves, those details as your professor is talking for your future reference. And just as one more example, if we're going to this part that's about treatment, this really busy slide here, we can see that they talk about a variety of drugs, but maybe your professor doesn't care that you know all of them. He'll say like the main ones that I want you all to know are amiodarone and sotolol. The main treatment that I care for you guys who know is actually none of them. But if you have to remember one, here's the one that you'll have to do. That makes it easy to go from a really busy slide like this to this is what they consider to be important. Doesn't always happen that way. But if it does, you can go ahead and create a note that's much more succinct and brief for you to review from later. Now once you finish lecture and you have an initial template and the format for your tree method, how in the world do you actually review this to improve your retention before that quiz and test? Now before we get back to the rest of the episode, let's talk about today's sponsor we just can't have. Now on my medical journey, easily one of the hardest classes, but arguably the most important course to master was anatomy. It's essential to master for any future doctor and medical professional. But with the sheer amount of information plus the practical connections that you need to make to understand the functions, relationships, pathology, it easily becomes one of the hardest courses to nail down on your medical journey. And that's where today's sponsor Kenhub comes in to make that a whole lot easier. Now think of Kenhub as a high power search engine plus a learning tool for anatomy all in one place. Through their high quality modules, you can go through any topic you're currently learning about or about to learn about in anatomy and dive right into their high yield material. One of my favorite parts about their modules is that it's targeted to every type of learner. You can read through the outlines in the modules, you can watch the high quality videos even at 2x. You can learn through their mnemonics or flip through the outlets to visually see the structures you're about to see in lab or you can get right into quizzing and practical learning. You pick. Now because it's set to comprehensive tool, I wish I knew about Kenhub when I was in medical school because if I was going to go through anatomy again, I would easily go through one of their modules relating to an upcoming lab and do one of their basic ID quizzes to practice identifying structures that I may see in lab the next day. Then I would come back and do more of their advanced quizzes and multiple choice questions to nail down that material before my practicals and my tests. One of the biggest benefits of Kenhub is that regardless of what type of learner you are, all that information is there for you to master. So you don't have to alternate between resources to learn location, functions, and relationship anatomy. It's all there ready for you. Now if you're on your medical journey and you know that you want to absolutely crush it on a class as hard as anatomy, then definitely consider checking out Kenhub. To learn more, go ahead and click the link down below in description or check out their Instagram page at kenhub underscore english. And if you're ready to get started on master anatomy, then go ahead and check out the link down below and get a sweet discount. Thanks to our friends at Kenhub. So thanks again to Kenhub for being today's sponsor. So if we go back into this example that we have here for AFib, basically you have to make sure that you understand the big ideas before you go into the individual branches. It doesn't matter if I can memorize amiodarone and sodalol, if I don't know that those are rhythm treatments that are an option for managing AFib. And so the first thing that I'll do is if I'm getting to the part where I'm asking myself, Lux, how do you treat AFib? I need to know, okay, there's a few ways. First, there are some preventative things that you have to do, like getting them on a blood thinner based off a scoring system. We'll talk about that in a second. If I can mention that I have to control the rhythm of their heart, then I can say a few options for their rhythm include drugs like amiodarone or sodalol. If I can't mention rhythm as being a part of my treatment option, then I can't go up to those parts of details being the individual drugs. Thus, whenever you're learning, focus on asking yourself questions like, what's the epidemiology or the pathophys of AFib? You'll start to say, okay, this is how it works. Here's the pathophys. These are the people who are affected. Here are the classifications. And here are the related diseases and causes. In each of these, you can ask them as questions. So what's the pathophys? Is AFib who's affected? And if you can do them, then usually I love color coding things because it helps me kind of have a visualization of how well I know something. So if I know the pathophys and I know who's affected, but maybe classifications because all of that nomenclature is new for me, I may have to say it's a yellow. I need to come back to it. But related diseases and classic presentations of an AFib when I'm reviewing them and I'm not looking at what's listed below, I've nailed down. And the pathophys in terms of how somebody becomes symptomatic with AFib, like I don't quite get, I'm going to put a red. And so now when I'm done with the entire lecture, I can figure out where I want to start in terms of reviewing things the second time. Or if I ever come back to this lecture again in the weekend or before a quiz or test, I'll already know where to start first versus trying to go to the greens. You want to make sure you make those reds into yellows, yellows into greens. And ideally all of it is just mastered by the time that test comes around. Now, this is what we call the traditional tree method. You can use this. It's very simple. You have very effective and honestly, you don't need a word doc to do this. You can do it on Notion. You can do it on your notebook. You can even do it below the PowerPoint that you're taking the notes from or on the side. If you're using one note or any of the other apps where you can type or write next to them. But next, we're going to go into my personal favorite of how to transition a typical tree method into what we call a Q and a tree method to make it super effective. Now, the main difference between a traditional method and a Q and a tree method is basically what it sounds like. Instead, you're going to take each piece of detail and take it into a form of a question. So if I was creating this format, I would basically do what we kind of practice with with a traditional format. My notes would look like this. So what is that bidi-miology path of fizz of aphid? And I would make this into a question. Sometimes I'm lazy and I don't even write the full question. I know what path of fizz question mark means basically means luck tell me what the path of fizz is, who's affected, that's already a question, classifications. And then you can, if you want to be more full and complete, what are the related diseases or causes in question mark? And if there are specific things that the professor mentions, maybe he says paroxysmal aphid is the most common, you can say most common type.  That way, again, if I know the classifications, then I can say what is the most common type? Symptoms, question mark, classic presentation, question mark, you can write bigger sentences if they help you kind of remember what the question you were trying to go for. But you can say what diseases or outcomes are you at risk for? And then what is the basic workup? EKG findings. And then there was a mention on the slides about things that you happen to your left atrium. So I can put a question there. Sorry, that should have been under echo, but same thing. And same thing for management. So war friend, who can get it? And I'll just put that in the second thing. Same thing, who can get it? But now you guys can see how we've taken notes that you just come back home and read and tried to review, but there is a good tendency of just reading them to now notes that are meant to ask you questions before you move on. So if I physically can't answer the question out loud or on a right board of what the epidemiology of AFib is, I can't master it. And thus I will color code this yellow or orange. And I'll try to master that first before I go into these individual questions. The biggest issue with going through any lecture is we try to understand the details as best as possible with the same focus and quality that we do the big topics. But really you want to build that foundation first. And so I can't tell you what the overall workup of AFib is. I really don't have any business telling you those left atrial findings on an echo. It's silly to know the six millimeters or whatever measurement, but not know that you have to do an HMP, TSH, electrolytes and EKG.  The same thing with management. So asking yourself, what are the core goals of management, right? So that may be something that I write as a smaller branch as part of management. And if I can't understand that I need to focus on prevention and treatment, then I have not successfully answered that question and thus I can't move on. So now when I'm coming home and say, okay, well, actually you have to make sure that you have to understand that there's preventative focuses on AFib as well as actually treating the AFib itself. And then if my question is about treating, I have to say, okay, well, there's a rate and rhythm. If I can't tell you about both of them, I can't go individually and tell you about the drugs that I would use for rhythm. Doing it this way, again, avoids having the phone mode. I need to understand these pieces of details or this random piece of fact, learn the big pieces of foundation, turn them into questions to really help you focus on what the goal is of the question you're asking. And this way you can't BS yourself or convince yourself that you know something if you can't answer it out loud or put it on a whiteboard. Now I've talked about the Q&A method outside of the tree method in a prior episode, which I'll link down below and put it right here as well. But just remember that the entire option of using the tree method is to really just break down your learning and to learn this first. And ideally doing it in the QDA format helps you guide and move down that flow even further. And the more you do that repetition using color codes or flashcards to indicate this is what I suck at, this is what needs more attention, it'll be better and better at your learning and it'll just feel like learning for fun without the pressure of the greater score that's coming with it. Now if you enjoyed this method, go ahead and give it a shot. Let me know in the comment section how it works for you. But if you feel like you're just struggling so much on your journey that this is not going to be enough to help you, let's make sure that we help you. There's a few options that we have. You can go ahead and check the link down below to get our access to our free Med School Success Handbook. I talk about tons of step-by-step strategies and advice on how to study better, be more productive, including my own method of how I study in medical school, so that'll be linked absolutely free down for you guys down below. And if you're really struggling with your grades, I recommend one or two things. One, just check out our study program that breaks down the same six steps that all of our coaching students go through to help you understand here's what I'm doing wrong, here's what I can do better, here's how to improve my grades and repeat the process over and over again just like a top student was. Our level up your studying program will teach you exactly how to do that. That'll be linked down below. Again, all of those resources are available to you and there's no pressure to select any of them if you're not interested. But if you did enjoy this episode, you made it to the end, I would appreciate a like on the video if you're watching on YouTube tells me that you enjoy more content like this. Let me know in the comment section what questions you have. And as always, my friends, if you did enjoy this episode, then you'll probably enjoy this episode right here on all the methods that I used to get a 3.9 GPA in medical school, as well as this method right here on 20 minutes that you can do to improve your retention on pretty much anything you're learning. Go ahead and check out those two. And as always, thank you so much for being part of our journey. Hopefully we're a little help to you guys on yours. We'll see you guys in the next one. Peace.


At the plate, we've seen him do damage on a lot of different pitches, all right? So tell us what his biggest strength is. Well, Trent, as good of a pitcher as he is, man, I'm going to break you down a little bit on the hitting side of things right now. And as you can see right here, this isn't bad against the Oakland A's early in the season. Otani is a very selective hitter, man, only swinging at 35% of pitches outside of the zone. That means he's swinging at 35 or 65% in the zone. As you can see, he's tracked both balls right to the plate. He knows exactly what he wants to do when he gets to the plate. And once he gets that pitch, he's not missing it. At six foot four, 205, 210 pounds. When he can get full extension, he can hit the ball into the stratosphere, which is exactly what he did right here. If he continues to keep this up, man, he's going to have a tremendous season. The reason why he is having his most success as he is now is he's not swinging at these pitches up here and trade, you know, with the guys throwing these 100 miles an hour the way they are right now, you have to make your money in the lower part of the plate. I know he's hitting 333 right here, but that's only one hit and three at bats. So I think for him right now, if he can stay lower in the zone right now, like we talked about earlier in the season, man, you remember when he had that big leg kick? We saw his numbers in the spring. A lot of movement. He has made that adjustment to getting that front foot down, keeping his head as steady as possible and young kids at home. If you want to hit and you want to be successful, keep this still. Because if this is not still, it's going to make that baseball look like a whole lot more trade. This guy is dominating on every aspect of the game. How do you get this guy out? Well, as a lefty, I would want to attack him and establish the ball in and make him uncomfortable, but that seems to be his power zone. So for me, I would like to throw a sinker to follow his belt line so he can respect more in. It's to show him to try to move him off the plate and make him think about this element and then try to go down and away with the slider. And 286 is not bad. Don't get that twisted at all. That's not bad. But then try to rush him upstairs. When I think about bigger guys, I think about Jim Tomes, you know, guys like that, Richie Saxon, they want to get their arms extended. They want to show their power. So this is a danger alley. I better miss down. And that's why when you see the catchers, they throw their signs down and they tap that glove on the ground. Don't miss up because that's when he's able to extend his power and drive the ball out of the ballpark. This guy's only had like what, 61 at bats? But it's amazing. You talk about rushing him in, right? And we see that number three pilot. We saw Luis Severino go right here and that ball went about four. And I don't got his stuff. I don't got his stuff. I got D minus Severino stuff right there. So that's what I mean about the sinker and some type of movement that will follow his body line. But again, sometimes we say as pitchers, you got to pay the piper and you got to go in there for a strike. So he honors that pitch. It's been good. It'd be fun. I might get him once in a while. I might get him once. I have faith you'll get him. I know you. Get that whooper duper out of them. You know, listen, we like to analyze our players, but we also sometimes like to ask the players to analyze our analysts or at least ask them a question. D-Train, we have one for you. Oh boy. Oh boy. I got plenty of questions for Don Trell. But D-Train, I need to know where this leg kick came from as a pitching on your pitching motion because you had me in high school trying to pitch just like you and my legs flying all over the place. And I got coaches yelling at me all over the place. So I really want to know where you came up with it, how it started and what made you go to it. I love it. I love that.   I call him Sons of Train. Got a chance to play strikeout in Alameda, California. And we just, you know, we played it every single day in the summer. You know, I spray painted the strikes on my wall. Got the worst whooping ever. But again, after a while, I started to grow. Yeah, as you can see in my pants, you know, my back side's on my back. I just started kicking my leg up higher and higher. And guys were like, that's cool. So as I started to play.  I got to pay double for my pants. I got to pay double for my pants. And that's old D-Train. That's old D-Train. I'm on a 60 day. But it just became a part of me, man. And as more gangly I got, I got bigger. And I just got used to pitching like that, man. It was fun. And, you know, I had a good time doing it, man. The fact that there's a major leaguer in the major leagues right now that wanted to be you growing up, bro, it's got to be an honor. It truly is. And I really appreciate it. And I got a chance to meet him. And I was the first thing out of his mouse. And I'm just honored. And that's the reason why we play the game really at heart. So this has been a blessing. We're real proud of you. And send some of the checks over there, Haas. Send a couple of changes. You making that money over there.  Haas, if you could send him a massage therapist for later. Because we'll have to get the hands straight on that one. Hurt myself.


Live from Washington DC, it's theCUBE. Covering Boomi World 19, brought to you by Boomi. Welcome to theCUBE, but the leader in live tech coverage, I'm Lisa Martin with John Furrier. We're at Boomi World 19 in Washington DC. Pleased to welcome one of Boomi's award winners to the program from Gilead Sciences. We have the director of IT, Morally Anacavore. Welcome, Morally, and congratulations on Gilead being the 2019 change agent award winner for North America. Thank you so much, Lisa. It's good to receive the award. A lot of efforts have been put in place by our folks, so I'm very honored and privileged to receive this award. Fantastic, so give our audience an overview of Gilead Sciences, what you guys do, and then we'll start getting into the IT infrastructure and all of the great things that you have done with Boomi. Definitely, Gilead is being in the forefront of meeting unexpected medical needs of patients worldwide. And Gilead is the company, if you recollect, solve the epituracy problem in the world. They were the cure for it, and that's started the company, originally to come up to where they are today. They are in the forefront of science and R&D and technology when pouring therapeutics for inflammatory, infectious, and recently in big cancer treatments and auto treatments. So, the world is opening up big time. Our focus is to resolve unmet medical needs. The company is so focused and they want to be, they want to be probably the cure for all this. And it's so passionately too, it's all kinds of R&D going on. I'm so honored to be working for a company which is doing this great need for humanity, frankly. Absolutely, so the cure for hepatitis C, that's huge. We, whenever we talk about technology where it impacts every single person on this planet, infectious diseases, cancer as you mentioned, it's really, it's pulverizing. People understand it, it's, you know, there's a lot of gravity around it. Talk to us about what you needed to implement from a technology infrastructure perspective to connect all of these different data sources so that the next cure for all these different diseases has a foundation from which providers can actually, you know, glean data. Obviously, I'll talk about it. There are some backend services company, any company needs, let's say ERP system, I need some CRM system, those are good. But our company has the complexity of manufacturing systems that needs to make medicines. Companies' complexities of lab systems, R&D systems and product lifecycle management systems where things originated in a little molecule for the compound they call it and it expands into what is a clinical studies and a medicine. So I can imagine the plethora of systems that make this happen. So what happens in this environment is now people spring up systems for what they need and ERP does what they need. All of a sudden, I can't do without customer data, I can't do without my patient data, I can't do without my item data, how do I get the data? So it becomes, begs the question, like, oh my gosh, okay, we got all these complex systems in place. How are we going to share the data? Who is the master? What's the source of truth? All those are begging questions that kind of start up the landscape of integration, right? So that's where we are, launch that previous legacy systems for SOA that we have currently, mostly call it the ESB Enterprise Service plus it shares data with them, the premises. Now guess what today? Hey, I've got this cloud system that I'm accessing. I'm going to buy this Salesforce commercial system that's going to enable me to launch my commerce market better. How do I deal with these guys? How do I reach out to those folks? How do I make my engagement app on the events for doctors? How do I connect with my patients? So all these are big questions that we've been asked. So there was a need for a system that will kind of take care of all these diverse platforms in the cloud, on-prem, connect them together so that the data sharing happens. So that was the biggest challenge that we are trying to solve right now. And then with Pumi coming on to our platforms in a couple of years from in the past, we have matured into a place where we're going to launch a lot of things on Pumi and we are looking forward to it eagerly to consolidate all those legacy integration platforms into the Pumi world infrastructure. So it's exciting. Talk about the IT landscape in your company. What's going on there? How's it structured? What does some of the environment look like? Is it transforming the roles of the people? Stacking and racking? Is it cloud, hybrid? Talk about your environment. Fantastic. I think it's a great question getting into our pillars of what we do in IT, right? Our pillars are very simple, right? First thing is core services. You got to keep the lights on. You got to make sure things are working fine. The next thing we adhere to is people. So who do we need to make all this happen? IT's people, knowledge management, retain people, the best talent, get the best talent. The third pillar we have is the enabling of technology and that's where some of us come in to enable us. How do I migrate to cloud? Let's say we have a big data platform on an infrastructure, a dope infrastructure, teradata infrastructure on-prem and you know why, it's a plane space. So we, the data growth is enormous these days. So we are talking about cloud. We are already out of plants, we already have infrastructure in cloud that we're moving to. So if you look at it, the company is so focused not only on technology, we're just required to, in this teenage, to talking about data, talking about expansion, elasticity and the computing power you need. Yeah, there we are. We're adopting, we will be a multi-cloud, recipient and beneficiary, but at the same time we're also focusing on people and the core services we provide is IT. IT is technical, not difficult. So you have multiple clouds right now, Amazon, Azure. Yeah, we will have a multi-cloud eventually, not that everything is online and in production, but our plan is to have a multi-cloud strategy going forward because of the amount of things that come into our landscape.  You got a lot on-premises, some cloud going on. Absolutely, absolutely. So let's talk about business transformation, digital transformation. You did a great job of articulating the business, rather the challenges that you needed to solve. From an IT perspective, you have all of the hybrid multi-cloud environment. Where did the digital transformation initiative come from? Was it the business saying we have so much data in disparate systems, we want to be solving more real-world problems? Hey, IT, help us build a foundation that allows that. It's fantastic. If you look at our company, our CFO talks about digital transformation, not just IT. Our CEO talks about our digital transformation. So everybody, in fact, it was question A, we want to be digital. What does it mean to be digital, right? The question comes up. So in the landscape of IT VR, we are going to be a digital-enabled company. We're going to define what it means. To me, personally, digital-enabled means, hey, I need to share a piece of data across the landscape whoever needs it, whenever they need it, over they need it. That's called the digital transformation, if you ask me, because that enables other systems to consume it and then provide the care and attention it needs. Be it our customers, customers of patients, be it our hospitals that we work with. They are our customers. Employees are customers. Internet, you know, it could be your portal. So we are attacking it from multiple points of view. We want to make sure the technology enablement, moving forward in innovation, we care for all these areas of our customers where we can really digitally enable them. So focus is not just on one point of digitalization, it's customers or patients. How can we give them access? How can we get the feedback? All of them fall into 360 degree view of data enablement. So it's so focused and we are so thrilled to have such leadership that can pay a lot of attention to all these things. And I think it will be a transforming our company a big time in the next few years with the digitization we are looking forward to. Mobile applications, all kinds of things are coming out. So why Bumi? Bumi is a cloud-native platform. We saw the video, I don't know if you saw the technical keynote this morning, the first video started up with a few minutes of all the areas in which they were first. But they took this big bet back in 2007 when they were founded, they are this single instance, multi-tenant cloud application. What differentiated Bumi when you guys were looking for the right partner with which to standardize? It's interesting because we like the cloud part, at the same time being a real compliance or in a country in the industry. We said, I can't really put it on the cloud.  Remember, things were not really stable at that time or people were wondering what cloud, should I, can I put my data? So we chose the Bumi hybrid model, which is awesome because it gave us the benefit of both our metadata in the cloud and take care of everything that you need to do. Metadata, I'm taking care of my processing on site. So that gave us that bang, say, oh wow, that's a fantastic option to have. It's a very thin infrastructure. It's, people can build things faster on-frame, run your case, data cases on-frame, but your cloud metadata is protecting you, the deployment, everything is easy, it's managed by them, it's HA. So all those were factors when we decided to go into Bumi. We did do a POC among others as well, but then the speed to market, less code framework, and also the roadmap, they'll add for them, right? That's very important for us. I'm investing in the technology. I want it to go for the next five years, 10 years. Are you walking with me in the technology? Are you making insights as we talked about today? I'm just paraphrasing it, but those are the things matter to us. So that our investment is protected. We don't end up with some debt, right? Like the monolith platforms that we have today. So those were key factors in moving forward with Dell Bumi, so. And so let's talk about some of the business outcomes that you mentioned with you, but let's look at them kind of categorically. If we look at kind of this over this polarizing industry, being able to study different spectrum of diseases and identify cures for them, hopefully, what are some of the business outcomes that you guys are achieving so far with them?  So give us some of those really big wins that you've seen to date. So it's how to be proactive, right? It's a game, it's a data game these days. So the more data you have about the decision you can make, it's going to be differentiated in solving problems and being competitive as well. So we are trying to see these aspects in the data that we can collect from all places. Now once you have the data, you need some kind of integration that needs to happen to process the data, to serve the data to people who need them. That's where the integration comes in. Obviously there are other areas where we do big data processing. We need to have some kind of a cluster to compute them and give some analytics for scientists to see, hey, I got this data, this was the inference, and now we can introduce that integration to give them all the data that they need. What used to take, in my opinion, days and months to infer through these files and files of data, takes less than 10 minutes for people to know infer, okay. So dramatic speed improvements here. Wow, elaborate on that a little bit. What happens is, when you get this huge epidemiology data around the world, right, you got thousands and thousands of terabytes of data. Now, without proper computing and the resources and the modern platform, it is tough for you to crunch those data to come out with some analytics that your people can use. You can ask queries like, hey, this disease happens in this area, tell me the percentage that is relevant to this disease in this area that I need to concentrate on solving the problem. So you want to solve big problems and you want to make sure the population benefits from that. So this kind of data gives you those inferences that people can research on. They say, hey, I'm going to focus on this area, it's very predominant in, let's say, African-Asian population is amongst about three billion, four billion people in the world. So let's focus on that disease, let's get some traction going on, and then that's how you solve the world's problem one by one, one step at a time. I'm so happy to be involved in that kind of enablement because I'm a very, very minuscule part of the whole deal because we work with scientists who are fantastic, who are biologists, who are researchers. So our act in this helps them get to what they need to do. We are completely at their service for what they need and then we just want to enable things for them, make things faster, make the outcomes for them on R&D to be more clearer. So that's where we come in. It's more like a service but industry aspect within the company, but then we are far too fortunate to work for a company that cures diseases and we are part of that journey that they're going through. You've just articulated beautifully why you guys won the change agent, in the change agent category. Morali, that was outstanding. Congratulations on what you've achieved so far and I'm sure I'm excited to hear next year where the business goes. We appreciate your time. Thanks a lot, Liza. Nice to talk to you guys too. Likewise, thank you. For John Furrier, I'm Lisa Martin. You're watching theCUBE from Boomi World 19.


This is Dave Vellante of Wikibon.org, and this is theCUBE where we extract the signal from the noise and bring you the data that helps you make better decisions. Adam Fuchsia is here. This is the third series that we've done of Chalk Talks. The first one, we looked at big data lessons learned at the NSA. In the second, we took a look at the security ecosystem around Accumulo, the database that Adam helped build while he was at the NSA, and today, we're gonna look at how Accumulo is optimized to maximize performance. Adam, take it away. Thanks, Dave, good to be here. Yeah, so we're gonna cover some of the secrets of how Accumulo really gets all of its performance in real time. A lot of this derived from Google's Bigtable and things that we've extended in my previous career at NSA, as well as what I'm doing now with Squirrel. So to start out, we'll look at one of the key elements here, which is the log structure of Merchantry, which really backs up a lot of the key value operations inside of Accumulo. So Accumulo stores key value pairs and it stores them in sorted order. And we take tables, which are really just collections of key value pairs. We break them up into partitions, which are known as tablets. And focusing in on just one particular tablet, we can talk about a couple of operations specific to that data. So in particular, if we're just looking at the tablet data flow here, we have data coming in from the left and these are key value pairs coming in in random order within the boundaries of that tablet. On the right, we have key value pairs coming out, but they come out in sorted order. So in in random order, out in sorted order and in between, there's a mess of operations to perform that sort. And we're going to optimize two different elements as we perform that sort operation. The first is to minimize the latency. So as data streams in, we want that data to be able to contribute to a query with as little latency as possible there. At the same time, we want to minimize our impact on disk resources. So Accumulo is a disk based architecture as we store data on spinning disks. We don't want to do a whole lot of random IO. We want to perform sequential IO whenever possible on disks. So that's performed through this mechanism and I'll take you through that here. So key value pairs coming in in random order immediately go into an in-memory map and this is a balanced binary tree. It's random IO, but it's inside of memory so it's efficient and as soon as it's in that in-memory map, it can contribute to a query. So we've minimized latency there. However, in-memory map, that's a volatile memory. So in order to preserve durability, at the same time, we write the data to a write-ahead log. This write-ahead log for Accumulo version 1.5 and beyond is stored in HDFS. So it's actually replicated on multiple nodes and it's synced to disk by the time that we acknowledge a write. Another issue with just storing things in memory is that memory is much smaller than disk. So at some point, this memory will fill up and we'll need to perform what's known as a compaction operation or minor compaction, also known as a flush operation. We flush that in-memory map to a file which is stored, again, in HDFS. So that write on disk, we want to make sequential. So we buffer a fair amount of data in memory and write that all as one sequential stream to an R file. Memory is much smaller than disk drives. So it'll fill up again. We'll do another compaction operation writing to an additional R file. Each of these R files then participates in queries. And as we stream data out of it, we'll stream, we'll merge data from each of these independent containers through a mechanism here to provide a single sorted stream of key value pairs at the query. The more R files we have, the more sources of data that we have, the more seeks that we have to do on disk. So query latency is impacted by the number of these files. So in order to minimize query latency, we do this, an additional background operation here, which is known as a major compaction, where we take multiple files, merge them together to perform, to create one single globally sorted file across all of those. And that operation happens as a background processing operation. So we have background threads doing the minor compaction, background thread doing the major compaction, and then threads attached to the query or the write performing those operations. So all of this is great. This is basically a standard log structure merge tree design. It goes back into the mid 90s for technology. One of the things that we've done with Acumulo is to put another mechanism in here, known as the iterator tree. So as we stream data from these multiple sources and merge them together, it actually goes through a series of operators. And those operators take place not only on the query path, but also on the compaction paths. So there's a series of operators that these sorted streams of key value pairs go through. So if we focus in on what those operators are, there's another view here of that iterator tree. So you can think of a series of our files and the in-memory map contributing to some following process here. The first one that we're going to do is really a merge. So we'll merge all of these individually sorted key value sources together to perform a single stream of sorted key value. But we're not done yet. So operations like deleting key value pairs or the cell level security that you're familiar with inside of Acumulo, that all goes through iterators and is performed in iterators. So that's a set of system iterators. On top of that, we can extend our capabilities to application-specific processing. So you might consider the case of I'm inserting key value pairs, I insert the same key twice with two different values. What do I do with the values? Do I keep the most recent one? Do I keep all versions of it? One of the operations that we do inside of the application specific iterators is versioning. So we can decide to keep the most recent value. We can keep the most 10 recent values. We can keep the most recent 90 days of values. So those are basic, what we would call filtering operations. In addition to that, we can do aggregation operations. So instead of just filtering out some of the values, we can calculate a function of all of the values that we've seen. And if that function is associative and commutative, then we can reason about it and we can say that really any online statistic fits naturally inside of that iterator tree here. So one example of that is word count. Anybody who's ever done the MapReduce tutorial has gone through a series of documents, pulled out the words, mapped those words to a count of those words, and then inside of the reduce phase done a collapsing of all of those counts, adding them up to provide the final word count. We can do the same thing, but we can do it in a streaming fashion using the iterators combining capability or aggregation capability to perform a very efficient merge. So for example, if I have this corpus of documents, I generate a set of terms. Each term I associated with the number of times I see that.  I may see two of those key value pairs. I can add those up. I get another version. Maybe that's one of my compaction operations. I do another compaction operation on the next two. Maybe I do a major compaction, merging those two together to get my final or at least most recent count. So the term A being seen four times would happen as an aggregation inside of the iterator tree. So when we look at the performance of that, essentially what we're trying to do here is avoid read, modify, write. So as I'm inserting randomly ordered key value pairs, if I need to look up the previous value, I'm essentially reading that off of disk, causing a seek on disk, and then writing a new value of it could also result in a write to disk. That type of randomized disk is very inefficient. So since we're piggybacking on top of this log structure merge tree mechanism, we can get much more efficient writes of online statistical data, where we're keeping that aggregated footprint instead. So a cumulative has this thing called a compaction ratio. And that actually allows us to shift between extremes here. On one extreme, we might want to say that I only want to keep one file at any point to really minimize the read latency that I see. The cost of that is every time I write new data, every time it flushes the disk, I need to compact it with that existing file. And as such, I'm going to be doing a number of copies, a large number of copies of each of the key value pairs that I write, where those copies are essentially rewriting that key value pair on disk. The flip side is maybe I don't want to do a lot of copies. I want to minimize my impact to disk, so I can keep the copies down. But the cost of that is I get a lot of intermediate R files, and that has an impact on read latency. So what we've offered is a ratio that you can set in between there. We've tried to optimize it for the general use case, where it's a mix of reads and writes. But essentially, we can bring that number of copies down, which makes our writes much more efficient, and at the same time, keep our read latency fairly low. So there you have it. That's the secret to Accumulo's online real time performance for a number of applications. Thank you, Adam. So you're seeing some of the innovations that Accumulo built on top of Bigtable and, of course, Squirrel just announced Squirrel Enterprise, which is an application development environment to allow programmers to take greater advantage of Accumulo and dramatically simplify that environment. You can go to squirrelsqrll.com to see more information about that and some more of Adam's work. Go to youtube.com slash silicon angle to see this and other videos that are relevant to Accumulo and the big data space. This is Dave Vellante at wikibon.org. This is theCUBE. Thanks for watching, everybody. We'll see you next time.


I've noticed that many service providers and businesses that would normally consider themselves to be spiritual people or want to live by spiritual or more higher self values. It's for some strange reason. They toss that out the window when it comes to marketing and sometimes the rest of their business, but particularly marketing and sales. So I'd like to talk to you about that today in this video and hopefully by watching this video or listening to this episode, you'll regain a pure intention as you do your marketing. As we know, when it comes to spiritual growth or personal growth, addressing all of you who are eager to grow to become more aligned with your deeper values or your higher self to embody more of that in your day to day work, a spiritual growth, right? If you're eager for that, you know that the more pure and intense your intent towards growing is in every moment, the more meaningful life becomes because you probably perhaps can see that every single moment is a potential opportunity for spiritual growth, no matter what it is that's in front of us, no matter what it is that we're doing or the challenges that we're being that we're faced with. And yet, you start to learn marketing. You somehow doubt your own spiritual values. And some marketer says you've got to use manipulative sales funnels. They don't say manipulative, they say sales funnels, but sales funnels from most of us the way that we've been taught are quite manipulative. You just, like, I'm just, I'm really genuinely surprised.   You still pay attention. Eventually you may start to justify a bunch of the same things they're doing because you like them in other ways. And I know that a lot of their marketing is at least at the very least, not pure in its altruism or it's like the marketing people, they pretend they're being nice and altruistic to you. Oh, I'm gifting you this with this. This is a free thing to give yours, give us your email address to get this free thing like everything seems so altruistic and like it's a gift. But then the backside that you don't see the underbelly of it is there's so much strategizing that to look pure and wholesome, but it's really to convince you step by step into buying their thing. And so I'm just, I'm genuinely interested in your thoughts on this because it's like why don't you trust yourself that the stuff they're telling you, you don't have to do it like it's not. It's not aligned with your spirituality or with your values. So, but it, you know, some people say, they don't tell me this but I think this is what they're thinking maybe this is what you're thinking but George, I just have the marketers just have to do their thing. I just have to do the evil thing of marketing. And then when the clients come to me, then I can be my spiritual and integrity self with my clients, because that's really where the real work is with my clients whatever the marketing is is just a necessary evil. Right. It's a means to an end. And here's lies in the problem herein lies the problem is that the first me essentially the contact you have your business has with the world starts off as manipulation or as a means to an end or as a necessary evil as doing things that feel questionable to you.   I've said this before and it's worth repeating again and again. The real work starts in your marketing, your values actually impact a lot more people through your marketing than your clients. Let's think about this. Hold on really think about this. Your marketing, your, your blog posts, your videos, your sales pages, your website touches a lot more people than the few who eventually work with you. How many people need to go to your website or to see a to see your blog posts, all your many blog posts or your videos or how many people need to do that before one person ends up being your client. I don't know how many for for you is it 10 is it 100 it 1000 is it more than that. Let's let's say 100 people need to visit your website, and you get one client. You do not care about the other 99 people they're just tire kickers. No, of course you as a spiritual person. All right, you care about everyone. And we should care about everyone. I mean in the general sense, we don't have time to literally care for each person with the same amount of energy and time, but we care about the well being of everyone. Because we have those kinds of values you and I. Do you care about the 99 other people who don't buy from you. And you just care about that one person who does buy from you. If you, I know you care about it. So if you put your caring into your marketing. That means you say, I'm going to be aware of what doesn't feel right to me in marketing what's manipulated what's most of the marketers that are teaching us. I mean, I feel it, because I learned from many of them. And many of them are my peers, my colleagues in my industry. It's mostly manipulative BS, not BS because some of it works to get a few sales in the short term, but it's BS in terms of misalignment with your spiritual being. And so, back to this idea that you care about your spiritual growth. So, let's not throw your spiritual growth out the window when you do marketing or sales work on that kind of stuff or getting clients can't be spiritual I need to pay the bills. And this is the problem when you start to strategize from desperation. You've lost your way. You've lost your way, because it's like, Oh, I got to pay the bills. So let me just ignore my spiritual values for for now. I got to do the things that work to get sales George just get clients and then I'd be spiritual Michael, you don't have to do that. Let me.  Let me tell you how you can spiritual fully spiritual, fully aligned with deeper values of caring for the humanity and yet have effective marketing and get lots of clients ready. Here's how you do it. You care. You bring your caring into market research. Okay, so the reason why your marketing is not working there's, there's, I'll say there's, there's three reasons. Okay, why marketing basically doesn't work and why you're not getting clients not getting as many as you want. There's alignment. There's reach, and there's trust, the art method. Okay, alignment, reach and trust. Alignment is, is your product and service so aligned with the person in front of you and what they want that they say of course I'm going to buy that from you. Or do you not care enough for them and only care about your own thoughts and your own peak experiences and your modality, because if you only care about your own self. You say how come George, people aren't buying my stuff. You're just thinking about yourself.  You forgot about that you didn't realize that that was a thing. Yes, it is. You care. But when it comes to your service and your product, you are so not you, by the way, I'm just saying the person who is saying, how come I tell all my friends and I post on social media about my service nobody buys it, or not enough people buy it. Let's talk about first alignment, it's because what you're selling people don't want. Yeah, people don't want what you sell. That's why you're not getting enough sales.  You've been in yourself too long. You have forgot to activate your caring when it comes to your product design, your service design, how you what your what program you're putting together you forgot that the caring starts there. You care, you care by talking to your potential clients and saying, what would you like me to design, because we have limited time on this earth, and I want to put my efforts into doing stuff that you actually want. So, tell me what you want, and I'll put it together and I'll sell it to you and then you'll buy it, because that's what you want. Now you might say well George they don't know what they want. Now that's not true. You just have to ask them the questions to pull it out of them. You know, and I don't have the questions in front of me right now. If you want if you if you want to you could take my core program I online course about market research but the questions are basically something like this. The questions are, what have you been buying in my area of expertise. Because the fact that they're spending money on something that's remote even remotely related to what you offer means they want it.  Very important.  They know what they want. And you think you know what they need. Because that's where the money is going is what they want people as we know we often spend time spend money on things that we want but don't shouldn't right don't really need junk food. You know, whatever it's like, we spend time and money on things that are not good for us but we, it's pleasurable is desirable it's something we want.  They do want something and regard regards that you just have to figure out what it is. You have to talk to enough people. And this is where your caring comes in. If you say yeah of course yes I know I'm caring. And now I realize I have to activate my caring by talking to more people this is where I'm not this is what I'm not doing. I'm not talking to enough people you are not talking. I mean if you have trouble saying how come people aren't buying this thing. I have one answer the first answer for you is, you're not talking to enough people. If you talk to enough people and say something is off with this program of mine this service of mine because people aren't buying it and I'm just curious. What are you buying and or what are you seeking. What are you buying, whether it's related to my thing or not okay but you know we can talk about what you're buying I mean, even remotely related to my thing. What are you buying. Because that's what is a clear indication of what you want. And I want to align my service to what people like you want. So that's alignment number one number two is reach. Reach is I've, I talk about this all the time, Facebook ads, Instagram ads, LinkedIn ads, collaborations, or content that goes viral, because you have put up put out enough content. You know, let's talk about each of these very briefly here. Facebook Instagram ads. I have a whole course on that if you're interested but it's essentially it's like, wouldn't you like to pay $10, $10 us to reach 1000 for a brown fans, or name the celebrity or influencer that that you like to reach their fans yeah $10 can reach you 1000 for a brown fans. Did you know that. Brené Brown, Eckhart Tolle, Emma children. I don't know name name the thought leader that is famous that's well known, Tony Rob, I don't know Tony Robbins and right for you, whatever and we just name, name whoever it is but chances granted Doyle chances are, you know, hey house sounds true the chances are you can reach 1000 of those people with $10. Did you know that. That's the genius of Facebook and Instagram ads. This is also why people hate it. Right.  Me, they're selling it to me and you the advertiser. Yeah, you pay 10 I paid if I didn't, if Facebook didn't take didn't take your data and told me that you like Brené Brown, I wouldn't be able to spend $10 and reach you and 999 other people. So $10. That's all you need. I mean, no one's going to buy your thing after seeing you scrolling by your thing once that's what it means to reach someone, they at least scroll past your, your, your ad, at least scroll past some of them will stop and look at it. I'm looking at my phone. So 1000 people at least scrolling past some of them will look at it. And then they might go, okay that's kind of interesting and they keep scrolling and then the third or fourth time you reach them so $40.  It's interesting. $40 are you willing to spend that. That's reach. Okay, 40 bucks. Not saying you're going to get a client for 40 bucks, you might. But this is why I talk all day long about why aren't you doing Facebook and Instagram ads. Generally don't know because they're evil. You could say we could say every everything is. You could say Facebook Instagram is evil. And yet, they have been, they have been essential for so many small businesses like mine and like people like you, small, small businesses, like I don't know how to reach people. Oh I can pay $10 and reach 1000 of the right people.  Yeah, so Facebook is evil. Yes. And it's also the flip side of it it's also helping solo in micropreneurs like me and you to reach 1000 people for $10. Is that evil. No, I mean, like I said it's two sides of the same coin, they take the data and sell it to us. And reach has you can do ads or collaborations so other people who have an audience, similar size does you maybe you have 50 fans right now they have 50 fans, you do interviews with each other and now you've each reach another five people. They're 50 fans right maybe not all 50 will watch it but maybe five of them will watch it so now you've, you spend an hour swapping interviews with somebody else, half an hour, them interviewing you, half an hour you interviewing them. And you've reached five more people. Why is that that's great. Why wouldn't you do that all day long. Right. Reach people with a similar sized audiences you, and you can do that all day long. Right it's an it's like, it says spending an hour with one potential client you're spending an hour and reaching five potential clients. You know not one on one, but at least they're seeing your video or reading your blog post or something so swapping. I'm going to keep going here. The last one I said art alignment, reach and trust and trust is what we started this video with which is having pure intentions in your marketing.  When I create content. I create content to help. I create content to delight there's a pure intention there to serve. That's all I'm going to do I'm not going to try to. I know I'm sorry I did mention some of my courses in this video but I wasn't trying to sell you the courses I honestly wasn't. I want to communicate this framework and like help you out if you never buy my courses. I'm honestly okay with that. That's the practice. Are you willing to do that. I think you're willing because you have that deep sense of caring, and you activate your caring in your content to say even if you don't buy a single thing for me. I'm going to show up with courage and conviction. In my content, even if you don't buy a single thing from me ever. I'm still going to serve you with content. I'm still here to minister to care as a cause of what I believe in what I believe will help humanity. And in your offers. When you're selling a program or an event or product or workshop or or a coaching service. Do you believe in what you're selling. Have you done the alignment work of you're selling something you know people want. Well if you sign something people want why are you shy about selling it. You should be out there with gusto with joy saying oh my gosh I know what you want. Here it is.  I took that those 30 conversations and went back into my lab, my home office, and I designed this thing that you want so here it is I'm so excited to share why wouldn't you do that with gusto enjoy of course you. That's pure intentions and marketing to I don't have to use any tricks to try to get you to buy no tricks. I'm just telling you what I think you want this product or service at a price that I think you would find a good deal. That's it pure intentions and marketing and sales allows us to really do it with joy to do it with heart. And by doing that and therefore much more sustainably we actually we don't burn out because we, we show we don't even have it no longer becomes a chore, I think, because we get to to serve content in a way that's uplifting humanity. No matter if anybody buys from us. Now of course of course, if you keep doing it people will buy from you but that's not your main that's not your like that's not what you're thinking about you're thinking about that's one what I'm thinking about service. And then when it comes to selling, which you sell occasionally at least once or twice a month you say hey, here's my coaching package here's my coaching subscription here's my workshop here's my online course here's my group program.  I think this is what you want. What do you think it's honest, I don't have to use any tricks to get you to do it. So, anyway, I hope this is helpful. May we all find a purer intention in our marketing and selling so that we are pulled, not push we have to we don't. Hopefully no one has to push us to do our marketing. So what a chore. Oh, I got to show up for my content. Oh, I got to remember the cell no it's it's out of a pole towards the caring for the audience that we show up consistently. So, thank you for joining me for this and I hope this is helpful. Take care.


Hello everyone, welcome to the Linux Foundations open source summit Europe 2020 and in my session, simplifying first boot experience for your cloud VMs with cloud init. I hope you're having a great time in the open source summit and you're learning new things. My name is Ashish and I work with Microsoft as a partner technology strategist to help my ISP partners embrace the cloud and solve the technical challenges that they are facing. That's my email ID and the Twitter handle on the slide if you want to reach out. We live in an age of everything as a service. And that applies not only to computing but to the other aspects of our lives as well. But of course, we are only going to talk about software and computing today. The two things, the two innovations that have made it possible are virtualization and the cloud platforms. With virtualization, you could harness the complete potential of the hardware that you already had in your data centers that allow the organizations of all sizes to get much better returns on their investments. The cloud platforms today have made it possible for the developers sitting everywhere on the planet to get their hands on the latest innovation in the computing and software. We have services like App Service on Azure, Elastic Beanstalk on AWS, App Engine and Firebase on GCP that allow developers to quickly and rapidly deploy performance applications on any scale that they desire. This was really unheard of just a few years ago. But one thing that everyone still tries to create the moment they get their access on a cloud service is a virtual machine. And there are many valid reasons for that for the virtual machines to stay here. They are one versatile piece of technology that are available on almost all cloud providers and other platforms. You can install your front end, your back end, your database and any other software that you need for your solution to work and you can replicate that stuff among cloud providers because the virtual machines, the virtual machine images are almost identical between the cloud providers. And Ubuntu VM on Azure is going to be same as another Ubuntu VM running on AWS. And we are going to see that in the demos that we are, that I'm going to show you after a few slides. That makes the virtual machines really simple and cost effective solution and a preferred choice for the development and testing stuff. But it is not without problems. The images that you get from your cloud providers are immutable, which means you own the activity to customize the VM to provision them properly and then make them ready with all the necessary software application, database, configuration and other stuff that you need to ensure that your solution works in a stable fashion. And then you can probably create a clone or a master image of the VM, which allows you to tackle the problems of replication and scaling. And that's where Cloudinate comes into the picture to solve these problems for you. Cloudinate is a cloud instance initialization framework. In other words, Cloudinate is the framework that you can use to gain control over how your machine gets configured and provisioned at the boot time. When you create a virtual machine, you need to install software, you need to tweak settings and do other stuff to make it behave the way you want to. You often probably do this manually or you probably have scripts that you execute. With Cloudinate, you can line those up as the actions that get executed when the machine is getting provisioned. Cloudinate is also cross-platform and multi-distribution, which means that the configuration that you put together for the Cloudinate to customize your virtual machine on one platform is going to work almost exactly the same with little or no modification. It also means that the configuration, the multi-distribution tenet of Cloudinate means that you can also take the same configuration from one distribution and apply it to another. It supports all the major public and private Clouds and also gives you the fine-grained control over how the VM gets provisioned and initialized at the first boot. And this magic is made possible by instance data that is provided to Cloudinate. It can be classified into three categories, the Cloud meta data, the vendor data, and the user data. The Cloud meta data and vendor data are provided by the Cloud provider and the Linux distribution vendor. It includes information such as what kind of network this machine is going to be connected to, what kind of storage is going to be mounted on the virtual machine, and things like SSH configuration so that you can access the virtual machine after it is ready. The user data is where you and I get control over the customization that we want to carry out when the machine is being provisioned. As mentioned earlier, Cloudinate provides you with really fine-grained control over how and when you can customize your virtual machine. The generated stage is an early stage during the boot-up process. The local stage is when your root file system becomes read-write so that you can start writing data and configuration to the files. The network stage becomes available when the network is up. At this point of time, you can start calling the services outside and get your software and configuration in source code and other stuff downloaded to the virtual machine. And then you can configure them in the configure stage. And at the end, you have the final stage, which is similar to RC.local. The scripts in the stage gets executed after the machine is fully booted up. You also get control over how and when you want to execute the scripts. You can execute the scripts only once when the machine gets provisioned. You can also target a different set of scripts only during the first boot after the provisioning. Then there are scripts that you can also run at every boot up. So as you can see, the flexibility that you get with Cloudinate is really versatile. So that was the context about Cloudinate and what it can do for you. Let's jump into the demos to take a look at Cloudinate in action. In the official documentation, there are extensive examples that you can get your hands on. But for the purpose of this talk, we are going to take a look at some simpler examples. So there's a Cloud config example where we are going to perform the upgrade of the package repository and install Nginx as a package on the target virtual machine. Then we've got a way where you can use a different directory to run a script from a remote location. And then we have this example where we are going to run a script on the VM. So in this case, you can see that we have got a script that creates an index.estimal file with plain simple hello world in it. And then it serves that HTML file using simple HTTP server using Python. So I'm just going to copy this into my clipboard. And I'm going to start with AWS. So I'm going to launch a virtual machine, an EC2 instance on AWS. So we have the Amazon AMI virtual machine. I'm going to select the T2 micro. And then I'm going to click on the configure instance details. And after all these parameters on the screen, you have the section that is called user data. And that's where you can copy-paste these simple scripts here. As you can see, there are three different options available on AWS. You can paste your script as text file, you can attach a file, or you can encode it using base64. We are going to go ahead with the text options. Let's go through the steps and launch the VM. I'm going to use an existing key pair that I already have downloaded on machine. And I'm going to click on launch instance. And as you can see, the initialization is done. Let's click on the instance and it's going to try to log in. I think that goes a little bit early because it still shows pending here. So let's give it a moment before it becomes running. And let's go and log in. So let me make a copy of the address. Let me go back to my command prompt. And I'm going to point my SSH client to the key that I've downloaded on machine. And I'm going to log in to this machine. In fact, we don't really need to do this. So this is done, right? Now, if you remember, let's go back to the script that we were using. You remember, basically, it's prepping up a simple HTTP server using Python and that only serves Hello World, right? But I don't have my port 80 available to the world. I'm not open it up in the security group.  And you can see that the output is Hello World, right? So which means the script that we saw here, it worked. And the Python based simple HTTP server was running and serving the content that we actually put there. And if we go to slashware slash log, you can actually see the file where the execution log can be seen. So what I'm going to do is I'm just going to show you the output of the execution. So this is all that happened when the machine got provisioned and the script that we added to the user data part of the VM provisioning executed. There's not much here, but you can actually basically see that there was a national request and that got served from the local host, right? So that was the first demo. What I'm going to do is I'm going to exit from here and let's jump into the second demo that we have. For that, let me show you the cloud init YAML file. So this YAML file starts with a cloud config directive. And then there's a directive called package of bread true, which is equivalent on Ubuntu VMs. It's equivalent to APT update, which means it is going to just update the package registry so that you can get the information about the latest available packages. And then after that, it is going to install this package called Nginx. Nginx is a web server. I think that's something that everybody practically knows. So what we are going to do this, what we are going to do now is we are going to copy this. And this time, we are going to launch a VM on Azure. So I'm going to create an Ubuntu 18 VM here. My resource group is already created, so I'm not going to change that. I'm going to call it Hushes of Web 1. I'm going to put it somewhere closer to me. And I'm going to use a standard B2S, which is the burstable two core VM. I'm going to use an existing key that I have already stored in Azure, and which is already downloaded to my laptop. I'm going to practically keep everything as it is. But when we come to the advanced stage, advanced stage of configuring, advanced step of the configuration, what I'm going to do is I'm just going to paste that copy texture. But when we come to this advanced step of the VM creation experience in Azure portal, what I'm going to do is in the custom data section, I am going to paste the text that I copied from the code example that we were looking at. And then I'm just going to go and create this VM. The VM has been the deployment is actually in progress right now. And while that is happening, not to waste time, what we will do is we will actually go and create an Ubuntu VM on AWS as well. So I'm going to create a launch instance. But instead of using the AMI image, I'm going to search for Ubuntu. Ubuntu 18, LTS branch. The rest of the steps are going to be exactly the same that we did the last time. T2 micro, which is the equivalent of the size that we chose on Azure. And I'm just going to put this here. You see, it's the same text that I've used on Azure. I'm just going to use that exactly the same on AWS as well. And I'm just going to launch it. Same question, just going to use the key that I already had saved on my VM. And while that is happening, let's go back and take a look at the Azure deployment. So as you can see, the deployment is done. That's my IP address. And I'm going to do this from the command line again. So SSH, my key is actually stored in the same directory. So I'm just going to do this. And I've logged in, and if I run engine next here, it's installed, right? Let's go to slashware, slashlog, and take a look at the cloud init output log. So that is the basic stuff, the initialization stuff. And then at the end, if you see, this is the output of the APT update, APT gate update. And then after that, whatever you see on your screen is basically engine is getting installed. And if you remember the slide where we were talking about the different stages of the boot that you can target, anything that you put in the user data, or the config, or the custom data on Azure portal gets executed at the final stage. The thing about these stages is that everything that you put in the cloud init and target a specific state that basically blocks the boot process. So you have to be absolutely careful about what you are doing and also be careful about whether or not it is going to prevent your machines from booting up. So be cognizant about the fact, and everything should be fine. So that's one thing. Let's go back and take a look at our AWS instance. So yeah, that seems to be running now. Click on this. Is it the same VM that we had? Or yeah, that was not the same thing. So this is our open to VM. What we're going to do is the same thing that we did on Azure. So I'm going to log it from here. I'm going to use my AWS key and the username for the open to VM on AWS is open to. So that's what I'm going to use here. I think I am confused between my VMs. Let's take a look at this one. Let's copy this and try this. So that worked. And GINX command is available. And what you can also do is you can actually take a look at the output logoff cloud in it. And you would practically see the same output that you saw on the Azure VM because, like I said, the open to VM on Azure is going to be practically identical to open to VM running on any other platform. So we're done. So the output and similarly targets the final phase. So that was about how you could use the cloud init YAML format to execute stuff, right? There's another thing that we can do is that you can also execute a remote script through the cloud init. So while this gives you a lot of flexibility, what you could do with this, you can actually maintain a central repository of the scripts to target different roles that a VM is going to play in your deployments and not really change anything with respect to the VM in your automation scripts and just customize the script in the center location so that your deployment gets customized automatically. The directive of interest here is hash and payload. And then I provide a URL to a script that I've stored on GitHub. So that's the raw path. So what is going to happen is that the moment cloud init reaches the final stage, it is going to download this script and it is going to execute that on the VM. So let's try that with Azure first and then we will do the same thing on AWS. So I'm going to create a VM on Azure, same resource group, somewhere closer to home. And I'm going to use the same key that I've had that I used for my last VM. And going to jump to the advanced stage and put this script here. So before we do that, let me just show you that script. So let me just copy this URL and open it for you. So as you can see, what I was doing with the cloud init YAML file in our second demo, I'm doing that, but I'm doing that through the script here. So I'm installing NPM, Node.js, and Nginx apart from updating the app registry. So let me start the deployment here and then we are going to do that exact same thing on the AWS. All right, so that deployment is done. Let's go back and create a new instance. I'm going to use Ubuntu again. Going to use the same size that is allowed for my free tier on AWS. And I'm going to put the exact same thing from my example files to here. And just going to finish the process and launch my instance. And in the meantime, our VM on Azure was created. Let's copy the IP address and take a look at that. And we are in Nginx, it's not found. So what we can do is let's take a look at our cloud init file because I feel that since we are targeting the final stage, I think the installation is not yet done. And yes, I'm telling the cloud init output log and you can see that this stuff is actually still going on. If you remember, unlike the last example that we had, instead of installing only Nginx, what I'm installing is also NPM and Node packages. So that added a little bit of time. And that's why you say this delay, right? So it's happening in the background. And until it's done, we will not have the applications that we wanted to install ready on this virtual machine. And we are almost towards the end. Well, that's happening. Let's go back and take a look at our AWS instance. It says successful, let's refresh. It's initializing at the moment. Let's click on it. Let's see if we can log in. All right, this seems to be done. This was the Azure VM. And now if I run that same command that I ran first, we have Nginx running. And we can verify it's running by running curl against the local host. And yeah, you can see we have welcome to Nginx available here. So let's log in from this VM. Let's try to log in the VM that we created on AWS. We are here. Let's see if where we are. Exactly. So Nginx is actually ready on AWS, curl, as you can be called in slash, slash local host. And we have the Nginx web server running on this VM as well. And if you take a look at the cloud in it, output log in where log, you can see the information to that effect as well, right? So yeah. So those were the three things I wanted. So those were the three things that I wanted to share with you today. Let me log out and let's go back to our slides. So what we saw today in the session is that how cloud init really makes it easy for you to customize your VMs irrespective of which cloud provider you choose and with practically the same configuration. The one thing that would have been different in today's demo is when I wanted to install the Nginx package on my AMI images because the Nginx package for the AMI images on AWS is called Nginx 1. So I would have had to change the package name to Nginx 1 for the cloud init code snippets that you saw to work on AMI the way it actually works on the Ubuntu VMs. These are a couple of links that I believe is going to be extremely helpful and specifically the examples section. So what you saw today on my screen on this session in the demos were very simple demos but if you want to explore the broader capabilities of cloud init, you can go to the documentation and take a look at the examples that are there and with that you could actually see that the kind of customizations you can carry out for your virtual machines running on any of the public clouds and the private clouds is very extensive and that gives you really more power to ensure that your VMs, your primary site, your dear site are practically identical irrespective of how you are, what kind of images you're choosing and what cloud provider you are choosing. And with that we are coming to an end of the session. I hope it was useful and you learned something today. Feel free to reach out to me on my email and the Twitter handle and I should be able to help you with your questions and any doubts that you have. Thank you very much. Again, welcome to the Linux Foundation's open source summit Europe 2020 virtual edition and I hope you're having a great time and I wish you great learning. Thank you.