So welcome to the special of Nutanix.next coverage, theCUBE. We're in our remote studios in Napa today. Let's see two great guests talking about hybrid multi-cloud. We've got awesome Dennis, who's the senior director of product marketing. Dennis, great to see you. And Sabine Pakla, VP of product management for platform at Nutanix. Great to have you on. A lot of cool things happening with hybrid cloud. Architecture is when people want to have more cloud. They want it more invisible. They want it faster. They want it on multiple clouds, AWS, Azure, GCP, and others. So welcome to theCUBE coverage. Thanks so much, John. Thanks for having us here. It's been a pleasure. Tendy, if I can start with you first on the, what is driving the hybrid multi-cloud architecture? Is it just the fact that there's clouds out there as are specific things that you're seeing that customers really want that's a need for their business? So you're right, John. Over the past few years, we've seen cloud investments really taking off. In fact, last year in the midst of the pandemic, when the economy was showing a downturn, cloud spending was up by 30%. So organizations are looking at cloud for speed, for scale, for elasticity, and for app modernization. However, the same organizations will also tell you that there are some workloads that will continue to stay on-prem, either in the near term or permanently. So what they're really talking about is this notion of hybrid cloud, which is interoperability between their on-prem investments, their existing investments, and their public cloud investments. In fact, I would say Gartner in 2020, they did a survey and 75% of organizations actually talked about hybrid cloud being the preferred IT operating model. And an overwhelming majority of those 80% who had public cloud in their infrastructure, they had two or more public cloud providers in their space. So that's the multi-cloud aspect of it. So whether it's happening as a happenstance or it's a deliberate IT strategy, what we are seeing organizations take on is this hybrid multi-cloud infrastructure. It's interesting. It's so funny to see the dynamics of the evolution because it's like, oh yeah, I want more cloud. I want more cloud. I want more cloud. Wait a minute, I want to give up the on-premises piece. We've got Amazon. We've got, okay, we've got multiple things happening.  So Savina, I got to ask you the blockers. What is holding back? Because I mean, it's kind of like it happened, right? People are replatforming with cloud. They're not giving up their data centers and or the on-premises component. What's the blockers? It's inertia, is it time? Is it evolution? Is it skills? What's holding everyone back? Yeah, you know, John, over the last several months, quarters, what we have seen is that there are four typical issues that sort of come up when customers start to look at their hybrid multi-cloud journey. The first one is, how do I move my on-prem applications workloads to public cloud? Do I need to refactor the applications as I do that? How do I move that application from one cloud to the other and potentially move it back to the data center? And because the underlying platform are disparate between these different destinations, it's usually very challenging. The next question then you come up with is, hey, after I move the application to the public cloud, what about management, right? It's going to be different. It has its own island of infrastructure. The management tooling is different. The skillsets required at different processes are different. So that becomes another challenge. Then comes the service levels. I still, I'm still responsible for all the service levels from backup perspective, DR security performance that I was responsible for on-prem. I'm still responsible for those in the public cloud. And then lastly, I would say, customers want to know that their investment is protected. As they move the workloads all around, they want to know that the licenses will follow them. They can actually take advantage of the licenses they've already procured and not have to procure something new just around the same workload. So those are some of the challenges that we've seen come up. It's always good to chat with you guys because I remember covering Nutanix back in 2010. It was kind of a new thing and everyone got on the same bandwagon copied that the hyperconvergence and it was very instant when the whole nother level. It seems now there's another inflection point. You want to get your reaction tenuous. You can weigh in that be great too and get your reaction as well. This whole shift from design thinking, which has been great for a decade or so to there's a whole nother kind of conversation around system thinking. And systems thinking is about platforms and it's about outcomes. But now what you guys are discussing and launching this year.next is, it's a systems concept. It's distributed computing. This is kind of a new kind of mindset. How do you guys see that evolving in the customer base? And how do you talk about that? Because this is something that is coming up kind of like that design thinking mantra. It's like systems thinking, think about the impacts. Can you guys weigh in on your reactions to that? Sure, yeah. So when you look at the systems level problem, it's really that of having the same platform, be available at multiple locations wherever you want to run your workloads. That's sort of the underpinning or the foundation if you will of your system. And we've done just that with clusters. We have basically taken our hyperconverge infrastructure stack plus the hypervisor plus the management stack, that was running on-prem and we have essentially made it available on the public cloud, right? So that's really the special thing about that is that it's a single infrastructure and single management plane across your private cloud and your public cloud, which really helps organizations to accelerate the hybrid cloud journey. And it was the impact for customers. If you have that single layer, it's unified. Yeah, I mean, it's the problems and the challenges that it just mentioned earlier, customers will be able to address all of them with by leveraging something like clusters, right? Customers will be able to deploy their workloads on private cloud or public cloud without having to have disparate management models, right? They can have a single, simple and consistent management model between private cloud and public cloud. They would be able to meet the same service levels that they've been able to on-premise, whether it's DR, whether it's backup, whether it's security, whether it's performance and all along knowing that their investment is protected with Nutanix, as you know, we have licensed portability of all our software licenses between private and public cloud. So these are all the benefits that are very real and you know, customers really value when they think about the overall problem statement they have at hand. And what's your reaction to systems mindset, system thinking in terms of customers and other holistically looking at hybrid cloud? Yeah, so John, as you talked about, right, we started from a place of making infrastructure invisible, just taking away that complexity of infrastructure. And now we have evolved it to the next level where we're really making clouds invisible. This whole idea of you could be sitting on any cloud, you could be private cloud, it could be any public cloud or multiple public clouds. You don't have to worry about the complexity. There's the software layer that's sitting on top of that, that's really making that underlying layer invisible to you so that you can just get about doing your job. It's all about business outcome at the end of the day. By the way, I love the invisible mindset because that's also like, that's what DevOps infrastructure code was supposed to be. Make things invisible, make them programmable and you got to see serverless and functions coming out. People are really getting excited by the ease of ability to just provision resources. This is a major wave that's going to have a major impact to enterprises. How is this specifically impacting this hybrid cloud architecture? What do you guys do to make that invisible? Cause customers are all like, no one's denying it's happening. They know, like, okay, we know what's happening. But they don't know what to do. How do I start? Who do I hire? What do I change? What do I automate? These are questions. How do you guys see that? Yeah, look, I think customers routinely tell us that, hey, ultimately I invest a lot in really making my enterprise IT repeatable, reliable and predictable, right? So after they've invested in the process, the tooling, the people, they want to be able to leverage that regardless of where the IT direction takes them. When it comes to public cloud, they want to be able to take the same investment that they've made and be able to leverage that and capitalize that on the public cloud. And that's really, you know, the problem statement that we really focused on, just making sure that to your point, making the infrastructure invisible has to do with, you know, having a platform that hides all the complexity underneath and provides a simple, consistent, you know, framework, if you will, for the applications and the management, the people and the tooling. So I mean, talk about Nutanix clusters. What's that about? What's the value? What's the pitch there? What's it all about? Yeah, in a nutshell, you know, clusters is simply Nutanix offers back delivered on public cloud. Really, it's a, it includes our ECI for the AWS hypercondition infrastructure, the HV hypervisor and Prism Management Plane. And it's the same stack that we have been, that we actually introduced 10 years ago, run by thousands of customers and they've taken the exact same reliable, baked stack and we're available on the public cloud. And with that, you know, customers get some of those benefits that we talked about earlier. And then talk about the use cases because everyone's talking about day one, day two operations, shift left for security. If I bring that stack into the cloud, what is the use cases that emerges for the customer? Yeah, so John, there are definitely some patterns that have emerged with customers who go hybrid cloud. In fact, our viewers won't be surprised to hear that disaster recovery is foremost. A lot of organizations are starting with disaster recovery on public cloud with Nutanix clusters. This helps them avoid maintenance and investments in a secondary data center, just purely for disaster recovery. But it also gives them geographical separation and it gives them the regional cloud options so that they can still meet their data residency requirement, which as you know, is very key for especially companies based in EMEA. Interestingly, most of these organizations that are looking at disaster recovery in public cloud using Nutanix clusters are also leveraging their investments in clusters and their cloud instances to drive capacity bursting. So using it for death test or seasonal on demand bursting. So when you're not using it for failover for disaster recovery, the same cloud investments are being optimized for cloud capacity bursting. And then finally, there's workload migration, right? So either it's for data center consolidation or migration or for app modernization, our customers are looking to migrate some of the workloads to the cloud, but they want to do that quickly or in a timely fashion. So the idea is that you migrate them as is without any app refactoring right away with clusters. And then once you're on the cloud, then you can refactor at your own base. You can modernize some components of your applications on an as needed basis. So those are the three use cases that we are seeing disaster recovery, capacity bursting, workload migration, but then to your point about day one and day two operations, day two operations are really, really key when you have public cloud investments, private cloud investments and multiple public clouds in the mix, it could be really complex to have your IT operations in play, right? So this notion that Savina alluded to earlier of a unified infrastructure and management plane that oversees your public cloud, multiple public cloud and private cloud infrastructure as well as provide operations, not just for your VMs, but also for your containers and storage is key for our customers. So this whole notion of using up on day zero and day one operations, but also day two and day N operations is top of mind for our customers. That's really well put. I think that tying that layer, that horizontally scalable control plane, whatever you wanna call it, really creates a lot of value from the blocking and tackling meat and potatoes, disaster recovery to enabling the migration and replatforming and then refactoring of those apps. I mean, this is the modernization trend. This is what people are talking about. So this is what people want. This is hard to do and seems hard. Maybe it's easier with you guys. What's holding it all back? Because I'm sold. I mean, I've been preaching against for years, like this is finally coming at scale. And then is it multi-cloud that's the bottleneck or is that not yet fleshed out? Is it more architectures are not ready? The containerization or the stateful data apps aren't the tools aren't there? Can you guys give me a sense of why it's not going faster or is it going faster? Yeah, so maybe I'll chime in and let Tanu add as well. So we introduced clusters late last year and we have seen a lot of momentum and ton of interest from a customer base. And for the use cases that Tanu just talked about, it's not already happening. There are many customers that are already well on their hybrid multi-cloud journey. And ultimately it comes down to just where the organization is in their journey. And especially if you're a Nutanix customer, very familiar with the stack, for them taking the next step, taking with clusters in AWS is actually not that big of a jump, right? And, but if you're not on the platform, then some of the challenges we discussed earlier are the things that get in the way. It's almost like day one operations, Tanu, is like innovation and day two operations is rain it in, get the value. Day one, go and do some experimentation and day two make it all operate cleanly. I think. You know, oftentimes, you know, we have conversations, even in the first or second conversation, the topic gravitates towards app refactoring. When, you know, that is a much more heavyweight and complex time consuming project. You can actually get to cloud without app refactoring and do it at your own pace and you know, on your own terms, really. I think the migration thing is a huge thing. I mean, I see a lot of that. And then once they get to the cloud, they go, wow, I could do a lot more here. And it just spawns more. It's a step function value there. And then as open source continues to grow, oh my, it's just a successful way. Don't overthink it. Just get to the cloud, understand the distributed nature of the on premise piece and boom, then go from there. You see that accelerated value extraction. And as Tanu said earlier, I mean, we are taking a much more of a holistic and not leveled view of management in this hybrid multi-cloud environment, including non-neutonics environments, right? So we're not stopping at just the Nutanix environments or just VMs. We're talking about containers. We're talking multi-cloud. We're also talking about non-neutonics environments that you may have and give you that one sort of, one single class, if you will, right? It's DevOps happening. The dev has always been there. Now the OS is getting stronger and stronger. Now it's changing too. The intelligent edge is around the corner. That's just another edge. It's another premise in my mind. So again, this flexes with what you guys are thinking about. So I think the edge brings up a lot of action too. Big time. Exciting news. Let's get into the news. So you guys have some exciting news. Talk about what's new. What's the big stories? What's breaking? What's exciting? What's the top stories coming this year? Sure, sure. So since we launched clusters late last year on AWS, we have focused on a couple of things. One is expanding the availability, right? So we have added multiple regions. Now the total number of regions, AWS regions that we support is 23. We also recently added support for AWS GovCloud for our US federal customers. And we have FedRAMP, moderate authorization. So that's, which is very key for that customer base. We've also added some really new and exciting capabilities such as Elastic DR, some of that Thanu already mentioned. Hibernate and Resume, which is a very unique capability from clusters where you can hibernate entire clusters and give up all the bare metal nodes or compute, but still have your data intact in S3, just so you can resume it very quickly whenever the need arises again. And last but not the least, we are super excited about bringing clusters to Microsoft Azure. This has been a long and strong partnership with Microsoft. And as you heard in the keynote, we are actually starting the preview at this event and opening up to the customer so that they can get their first hand free for the product and work with us in bringing the product to GA. Multi-cloud world. Oh, sorry, Dan. No, so this is exactly what I was going to say. This is multi-cloud coming to bear, right? So we talked about hybrid cloud and now here we are with multi-cloud options for you. What's interesting is that everyone always, as the trends change, this is changing, that company's shifting and you guys have evolved beautifully. And I think the way people are leveraging cloud really shows their strengths. Everyone, the cloud actually highlights the strengths. If you play it properly, you can survive.  They're a data cloud now. So if customers can bring their architecture to the cloud, they can actually do a lot of re-architecting and re-changing and modernizing their business. This is something that's kind of, only in the past few years that's come up. This is quite a big trend. Do you guys see the same thing happening faster or is it just we're inside the ropes and we love it so much? Like I said earlier, organizations that are at different levels of the journey, but we're seeing happening all around us and we're embracing that. We're actually embracing that trend, enabling that trend because we truly believe hybrid cloud is the more practical reality and we want customers to have the cloud on their own terms and not feel like they have to do something just because they're forced to or they're not able to cost effectively or even technically for that matter. Okay, well, go ahead, Tendon, sorry. I was just going to say that RCE or Rajeev Ramaswamy puts it really well, the cloud is really an operating model, right? So it really should not be about where your workloads are residing. It should just be an easy operational model for you to engage with. Yeah, I think you guys have a great strategy. I think the invisible really brings true with me as well as that horizontally-scaled control plane because the innovation is happening but the operations have to be reined in and support the expansion as well, which means you have to kind of focus on the fact that you got to rein in the data and you got to make it invisible. If you look at Lambda functions and you got serverless trend booming with the edge, it's got to be invisible and programmable. It just has to be. Exactly, yeah. Great stuff. All right, final question for you both. If you don't mind, Tendon, we'll start with you. What's the big story this year at Dotnext? If you had to summarize it and tell your friend that you're driving in the elevator up to the top floor, what's the big story that should be talked about that's being talked about this year at Dotnext? Taking unified infrastructure and management and having Azure in preview is really the big news here. So go to Nutanix.com slash Azure to learn more. Show us your interest there, sign up for a test drive. It really is a very easy way for you to experience the product and action. And you just see how simple it is to deploy a hybrid cloud with clusters on Azure and under an hour. So the final word for you. What's the big news? What's the takeaway? Yeah, look, I would say that, you know, your cloud on your terms is really the big news that's driving everything we're doing back in the office building products and ultimately, you know, delivering or making that whole hybrid cloud journey and reality for our customers. And then to me, thank you for coming on, sharing that commentary on theCUBE coverage. Dotnext, thanks for coming on. Thanks so much, John. Thanks for having me. Thanks Raymond, John. I'm John Furrier with theCUBE. Thanks for watching. More coverage, stay tuned.


Hi everyone, Joe for Jaspy's CaseBreaks.com coming at you with a little mini break to get into The Bowman mixer pick your team one which is actually coming up in a separate video And that's coming up next for those of you watching live. So in order to move these last few teams right here We're gonna do a quick little one-pack break. So we're gonna do the break itself first one spot gets you two teams and For the purposes of the randomizer at the end We're gonna just use the original 15 names, but let's do the break itself first. Let's roll it Let's randomize it three and a three six times six the hard way one two three four and six All right Fred down to Trevor Ryan Shaq was in a break Jason early in the full case looking to get another bone But I'm confused as what's going on with all the fillers now I'll explain in a second they they're right next to each other So the the mini break is right next to the break. That's supposed to fill. I think Nick's organized it like that three and three six times Or just buy indiscriminately and eventually it'll break Five and six and hopefully we'll send you some nice hits diamond backs down to the Astros after six in this little pack break Jumbo pack break All right, so I'm not gonna read off all these names I'm gonna save the voice for the actual break itself But there's everybody right here. Basically we're looking for Who maybe it's on this half right there? So Jordan Cohen you got you have Bobby with junior opportunities Fred Williams Robert Poston opportunities Fred Williams Jason Dominguez opportunities among others and a lot of other teams have some some hot prospects as well I think so until a feud comes on Which is not for another hour or so All right, no trade windows on these sorts of things Yeah, five to ten Local time five to ten local time game show network The day they change that the day is not the day. I'll be writing angry letters and written letters Oh, man, if you change so we don't get GSN I would just quit I Don't know what I do I would have to download the GSN app and just watch it if they even have one but stream it on my iPad or something like A family feud YouTube just rewatch rewatch YouTube things right here. All right, guess what this these jumbo packs are also from a fresh From a fresh box So there you go. That's what we're looking at Eenie meenie minie moe catch a tiger by the toe if you always let him go. Eenie meenie minie moe All right. Good luck everybody Paper paper paper paper paper We've got Isaac Paredes for the Tigers from Mexico We've got Braylon Marquez Bobby with Junior Jazz Chisholm Cal Mitchell to Kate nice Robert Possen All right, so the Robert Possen chrome will go to Fred Williams and the A's and The Bobby with Junior paper so once again Bobby with Junior Robert Possen and Jason Dominguez are the only paper that actually ships in any of this This is applies to all of our bow and brakes on the site There you go, and there you have it. Those are a couple a couple of nice cards. They're no auto in the particular pack Of course, the whole point of this break Is to see who's gonna win those teams, right? Those are the teams right here So we're gonna snag all of your names Fred all the way down to Zack or no, we're using the original 15 names That's why I had this set up. All right. Let's roll it. Let's rent so the top three after in that particular order after four three and a one four times We'll get teams in the mixer. We're just coming up next one four times two three And good luck fourth and final time Congrats to Adam Fred Fred. They certainly had the odds Thanks to both of you for getting in. Well, thanks everybody for getting in. I appreciate it.   We'll do jumbo. We'll just call it jumbo one. We'll know that those are one-pack breaks There are actually a shackleton is right. There actually has been so so many of These breaks we kind of have to it's easier for us to find in case there's any issue Anyway, there you go. Joe for Jasper's case breaks calm coming up next is the bowman baseball mixer. Bye. Bye


Okay. Hi, I'm John Day. I'm here from Fred Hutchins, Seattle, Washington. And I'm the author of Easy Update, which was on the survey. Can I just get, like, do my own survey right now? Like, how many people use Easy Update or heard of it? Oh, okay. A few users out there. I just threw this in real quick. So the Fred Hutch, we're Seattle, Washington. We're home of three Nobel laureates. We have a pretty nice campus. Pretty good budget. We're federally funded. And we have over, well, very close to 300 faculty at this point, which we refer to as PI, personal investigators, people who have funding to do research. And that's our campus. So our and Fred Hutch. So the Fred Hutch has had a really interesting relationship for R. The main maintainers used to be on campus for eight years. They were there a long time. There's a lot of leftover R users there. The main bioconductor people were there up until about a year and a half ago, and somebody's wife got a different job and they ended up moving to a different part of the country. So we have hundreds of R users and they're very demanding people. And when R comes out, they want a new one, like within days. So I'm very highly motivated to do that. So when your local R build has 800 modules and you have to go through that list by hand and update them all for the next version of R to be released. I just think it's a level of work that can be performed by humans. It's just, it's not possible anymore. So it's just a real difficult task. And of course, Python is in a similar. So the motivation of course, so R's coming out four times a year. Python comes out a couple times a year. There's Python 2, Python 3. And again, these things have hundreds of modules and it's just really hard to go through and update the versions for all of those. It's also very hard to unwind all the dependencies and make sure you have them and they're ordered correctly in the easy build file. So R is pretty straightforward. It has a really nice API. The metadata is always correct. It's a beautiful thing. Whenever I'm updating R, it works really, really well. Bioconductor is a little different. Their metadata is JSON files that you download. So when I'm running easy update, there's a slight penalty to pull those files down, but we do it once. We load them. And if I see them locally installed, I'll just open them again. And again, the Bioconductor metadata is beautiful. It's always exactly right. The dependencies have already researched. It's very well maintained and they only update that file on new releases of Bioconductor. Python on the other hand, it's just a swamp. Anyone can upload a Python module. And the type of things I see in Python are like the project name is different from the module name, which is different from the download name. The dependency names that people use, it's like street slang. It doesn't actually match the project name. So they might be referring to the import name. They might be referring to the project name. So I've just had to write a lot of extra logic to kind of tease that apart, try variations, dashes, underscores. One's allowed in URLs. One's allowed in the language. Something to think about the next time you design a language Guido, it's should you make language constructs match across different domains. Perl, I had to do BioPerl around Christmas. So it's not in the code. I haven't pushed it yet and it's really ugly. I've been looking for an API for Perl. Now I've put that out. I joined the Perl developers mailing list and sent that out there and they just treat me like I'm a crazy person. Why would you want an API? Why would you use the internet for Perl? It's in Perl. So the only way to really get the metadata you want is to do the latest install of Perl and then use Perl tools to interrogate it. I found there's some people out there who have taken the CPAN database and have put it all in Elasticsearch and it's searchable. But it's not so much like an API as like a curiosity. Elasticsearch, I'm a huge fan. It's a great product. You can certainly get data out of it in a lot of different ways. But like the idea of the latest version or something like that, there's no real nice way to do that. So the next time I'm under a lot of pressure to update Perl, I'll probably do a better job and I'll get that code out there. So I'm supporting three and a half languages right now. And then the dependencies. Again, R is really great. Everything that's in R, if they list the dependency, it's actually needed. No one ever leaves stuff out. And Python, people forget things. Again, it's pipi.org. It's just humans typing. It doesn't seem to be any gateway there that really enforces this or they don't put it in a Jenkins container. They don't try to make sure it actually will work or do what you say it does. So I don't want to come here just to whine about Python, but if you run Easy Build and there's some mistakes, you get what you pay for. The pipi maintainers are very aware of this and they basically say, yeah, we can fix it. They can't. There's a blog post somewhere that explains this situation and they basically say, yeah, we're getting whatever people put in and we can fix it. I can say it's gotten a lot better from a year and a half ago and then this spring, they really shut down pipi.python.org. You don't get a 404, but they're not serving it up anymore. So through that whole process and people are cleaning it up, it does look a lot better now than it did even two years ago. So someone's paying attention and they're working on that. So this came over the mailing list just last week, so I thought I would throw it into the slide deck, but somebody wanted to, you know, what would happen if you included rstan in r and a feature of Easy Update is you can run it on the command line. As long as you give it the r version you can also say py version and then dash dash search. And the output of this is something that you can just cut and paste with the mouse and put it in your ext's extents list. So r stands in the bottom here and above it in two columns are all the dependencies. So that's what it takes to walk that tree. So if you were just building a single r instance with rstan in it, you know, this is what would be in there.  So after you've typed this and you have this huge list, almost certainly there's a lot of duplication between what's in this and the official easy build distribution is. So you'd like to be able to subtract that out because again we're humans and I don't want to spend all day picking through this file and looking for those duplicate entries. And the diff is a really weird feature. It's not something you'd use every day unless you're forced to build r over the weekend. And I'm really in the automation. It's something I think of a lot. So 2019a was just released and I'm thinking like, why don't we have all 1000 easy build modules updated over the weekend? Like we should just be able to go out to the internet and update all the version information, not just the entries into r and Python, but all of our bioinformatics modules. And there's no answer to that. That is a... But I think about putting maybe the idea of like hints. The easy build file itself tells you it's in GitHub or it's in a private repo it tells you a lot about where it might be coming from, SourceForge, and there's not that... There's APIs for that, but you could probably... I don't know. It's probably not worth the effort, but just talking about it, I think in the future people need to be cognizant of things like that and educating programmers when they're young in school. And GitHub's a really great thing, but even when we look at GitHub, it's just a morass. I mean it could just be master.zip. It could be v1.4 instead of... It could be releases. It could be versions or no information. And when I find that in the wild, I'm that guy putting an issue in. Please tag your software. Please make a release. Please get that v out of there.  But doing something to improve software in general, how it's being released. And we're all using EasyBuild because we want it to be a reproducible science. This is something I've had in mind for a while, having a backdash update. Yeah. Trying to figure out what the latest version is. And you're right, getting it perfect is going to be very, very hard. It's a mess. But I think we can probably do it for like 90%. Yeah. Which just GCC or Doom software has a very standard way of just looking through the directory and sorting the right way I think for some, even for most of the software on GitHub, it's still okay if they do proper release tagging and if you see a v and just throw it out there. So we can probably do like 90% good and then very special ones like openfoam or no tagging or I don't know what. Yeah. You do those manually, but it will still save you a lot of work with 90%. I might take a stab at the GitHub stuff and as a first go see what I can get. Just run it through, just run it over the weekend and see what the results are. Oh yeah, like Linux from scratch. That's such a great site. It's just like it's not really like releases. You know, it's not like a distribution. So all the modules that are out there in Linux are there. And it's a place I go and I look for stuff a lot to see what's possible. It could be in CentOS or Buntu, but it's kind of like a neutral site for me. And then, you know, Nanopore, they're difficult to deal with. And so I think like a lot of people, we started using EasyBuild around 2015. We just at the time just thought like, oh, this is a great tool for building software. We'll be able to save our easy configs. We'll be able to reproduce it. We are saving every time I download a file, a source file for some project. I am saving it along with the EasyBuild. It's amazing how many source files disappear over the years or projects get pulled on GitHub. And, you know, again, we want to make science reproducible. So having those source files on site and spending the money on the storage to keep them will help make that reproducible. But, you know, we were just all over the place with our easy configs. We had to grab something and it's like, well, we're using this version of the Zlide. So, you know, we'd end up making a new easy config just because of like something that's very inconsequential, I would think, you know, like who cares which version of Zlide is in some bioinformatics package. The researcher doesn't know. They just want their stuff to work. So the last year, we really made a big effort, like how can we use, and the 2018B course is a huge release, making sure that all the dependencies are the same. I'm in that boat. I don't want them to change. I want, you know, consistency across the line for that. So we're very much on committed to being, you know, 2018B making sure everything's consistent and for the first time trying to contribute back. And like our R and Python have always been very divergent and we're not going to do that anymore. We're going to use the standard Python, the standard R that comes down from the community and then all make a bundle that has all the extra modules that we want. And we'll do the same with Python. So just want to try to encourage, like, you know, more sharing and have more uniformity in the recipes and not have so many of them. And, you know, again, so I'm personally we're upgrading our clusters operating system. And what a task. So I'm the guy who's rebuilding all the software. And so, you know, I'm maybe about 80% of the way there. I've got to the end of March to get there. So like the idea of the community, I know it's out there and like issues and stuff like that.  But we would, I don't know. We'll get this somewhere. I don't know. My boss has mentioned the same thing, like maybe getting funding a position and that money would look like it's well-spent. If it's national money, the National Institute of Health spending that, you know, then prove that we're contributing this back into the community and it's being shared with a large number of people. So I think that's kind of our angle on funding now. Maybe a central place to list wanted software is actually a good idea because many people are sitting on it or not contributing because of a lack of time. And they could just tell you, look, I have something here. I don't have time to do the proper contribution, but take it and use it as a starting point. And I'm sure some of the software at least would already be there handled by someone in some way.  I'm going to have to parse through them all at the end of the show. So get my list of places to go. Maybe we should even have a separate repository on GitHub where you just open an issue like a wanted repository. And if people have an easy copy file, just copy paste it in the issue and you can take it from there. That could work. Yeah. We could at least try it and see if it works. Yeah. So just quick and dirty contributions and then someone else can take it from there and that would be a big, big help.  So, yeah. No, I get it. I was going to ask which OSF. Yeah. So we're moving from 14.04, which is rather embarrassing, up to 18.04. And from ToolChains 2016B to 2018B. So we've put the, there's a little hook you can put in lmod that writes a message to syslog. And so we're using that hook. We want to make some changes to it. And then we take that syslog information, we put it in Splunk. So for our entire cluster, it takes hours to run these reports, but we can actually get a report on every module load command across the entire cluster. So that's kind of the basis of how I'm picking what to build for the next release. So we have 138 modules that are in the bio directory of, you know, that nice little easy config at very, very, very at the bottom where it says module class. That is super helpful. So I'm just kind of like looking at layer 8, just like what the researchers see, just those bio-traumatics modules and all of that other stuff, all of those other lives are just kind of making themselves with dash dash robot. Yeah, so 51 million module loads are clusters not anywhere near the size of some of you that have presented. And 1.3 million of those are in bio packages. So that's my target for what to rebuild. So there's a pull request that's still in the works, right, about updating dependencies. But this kind of transition where you're going from 2016 B to 2018 B, it would automatically pick up all the latest versions and insert them into the things that you're trying to do, that you're trying to move over. So there's no hand editing of anything like that. It'll automatically update stuff that's already available in 2018 B, right? Well, I'm not sure I understand. So say you have something in 2016 B that uses auto tools, an old version, right? And it's a later version in 2018 B, it will automatically update that in the transition. And that's available in the easy build today? No, it's not. It's still, we're still waiting for a review. But it's working, I mean. Okay, that would be a big help. You know, some things I've done is I've just, you know, go to the 2018 B repo and every bio module that you have, whether I needed them or not. I looped through that last week and I think I built 57 packages with this script that ran over the weekend. So, yeah, just kind of like scoop up whatever I can. And that's the end of my talk, just a quick update on easy update. Oh, do you have like a demo? The other half of easy update is something called easy annotate. So the same code that reads an easy config, you know, I can take that and unwind it and publish it. So this site is a GitHub markdown pages and this is attached to our easy build repository. So whenever I check in a new module, it's kind of awkward. You have to do it twice.   So here's my current one. So what easy annotate does is it publishes a list of all those modules that are inside the easy config. So with this site now, a user can just go here and hit the little search thing. And if they're looking for a module, you know, maybe it's already installed. Probably about half of the help desk tickets I have now are stuff I already have installed that people don't know how to find it. So trying to keep everything we have published, all of our bioinformatics stuff published, all of our easy configs published, and in like a user friendly way, overview using like a little tutorial on how to use modules. So in general, we can just kind of direct users at the site to this page. And then all of these are linked back to their original. So if you want to know what that module does and that's all easy, you know, all the features and easy update of crawling the web and finding all of these links, you know, so it's all in the code so I can annotate this and produce markdown.  And of course, since we have a module list of just bio, you know, I can publish that. So these are all the modules we have in our bio. And mostly, again, like having it on a web page makes it searchable so people at the site can just go here and look before they open up an issue with us. So, questions? First of all, great talk. I mean, it's really great that you're tackling one of the problems which many of us fight. Out of curiosity, and since you are kind of related to the bioconductor community quark position, locality, whatever, R essentially is sticking to a semantic versioning scheme, but not officially. And I recall the day where the bioconda community asked the RD well-opist to actually announce that they stick to semantic versioning and they never got a reply, they never get a confirmation that R will adapt semantic versioning. Even though, if you look up the details of every release, it's essentially semantic versioning. And all the dependencies and the minor patches could be dependable. And do you have any work from the RD well-opist or not? No, we're kind of out of touch right now, but I know people who know people, so I could get to them. But yeah, it's pretty frustrating, right? Some of the R modules obviously don't move at the same rate as some of these things have been sitting around for a few years. It wouldn't be a problem if the update wouldn't be enforced because it's actually compatible in most of the cases. Yeah, and I've had to fudge things. Things are broke. I mean, I would just drop down a version and try again. Yeah, it should be better. Thank you. Thank you.


A very good evening aspirants, welcome to the Hindu Newspaper Analysis brought to you by Shankar IA's Academy, displayed here are the list of news articles that we have chosen for today's discussion, now without wasting much time, let's get into the news article discussion. Now have a look at this news article, see this news article speaks about the pneumococcal conjugate vaccines, see in Tamil Nadu know the government health centers have been running short of this pneumococcal conjugate vaccines in the last 2 to 3 months. This is due to less supply from the union government than the state government's requirement, so this is the crux of the news article given here, and in this context let's learn about pneumonia disease, its causes, spread symptoms and treatment, and specifically let us learn about the pneumococcal conjugate vaccines, ok. See pneumonia is a form of respiratory infection that affects the lungs, know that the lungs are made up of small air sacs called alveoli, when a healthy person breathes the alveoli are filled with air, but when an individual has pneumonia the alveoli are filled with pus and fluid which makes breathing painful and limits the intake of oxygen, ok. See pneumonia is caused by various infectious agents including viruses, bacteria and fungal, the most common bacteria that cause pneumonia are streptococcal pneumonia, mycoplasma pneumonia and hemophilus influenza type B, then the most common viruses that cause pneumonia are influenza, the flu virus and respiratory synestial virus and pneumocystis duropec is the most common fungal cause, ok. Now coming to the spread, pneumonia can be spread through airborne droplets from coughing or sneezing, then it also spreads through fluids like blood during childbirth and also from the contaminated surfaces, ok. Now let's see about the symptoms, the symptoms of pneumonia include rapid or different breathing, then chest pain, cough, headache, fever, loss of appetite, wheezing, etc. So having seen the symptoms and causes, let's see about the treatment if there is available. See pneumonia can be treated at home but in severe cases the patient needs to be hospitalized and antibiotics should be given for a speedy recovery, ok. Now we all know that prevention is always better than cure. So let's see about the preventive measures, see vaccines are an important and effective way to prevent both bacterial and viral infections in children and adults. The pneumococcal conjugate vaccine and HIB containing pentavalent vaccine are some of the vaccines used in India to prevent pneumonia, intake of adequate nutrition and reducing the indoor air pollution are some of the other measures to prevent pneumonia, ok. Now let's see about the pneumococcal conjugate vaccines, see the pneumococcal conjugate vaccine can protect both children and adults from pneumococcal disease. This vaccine contains a mix of several bacteria of the pneumococcal family which causes pneumonia. Hence the term conjugate is included in the name of the vaccine, ok. See this vaccine is also highly effective against other diseases like bronchitis, sinusitis, meningitis, sepsis, bacterium, etc. Also pneumococcal conjugate vaccines have reduced the burden of antibiotic resistant bacterial disease globally. This was said in a Lancet study report that was coded in the year 2017. Note that pneumococcal is India's first fully indigenously developed pneumococcal conjugate vaccine. It was developed by the Serum Institute of India and was introduced in December 2020, ok. So that's all you have to know about this pneumonia or the pneumococcal conjugate vaccine. See these science related topics are very much important for your preliminary examination, ok. These are facts that has been provided in this discussion. Make a note of it and use it for your prelims preparation, ok. So with these key points in mind now let's move on to the next news article discussion. Have a look at this editorial article. This editorial article as its title aptly says focuses on the global south's assertion in geopolitics, ok. Here what is global south? See the term global south is used to identify regions within South America, Asia, Africa and Oceania. See the global south mainly includes the developing countries, ok. And these countries are also called the third world countries. Look at this map here. In this map the areas highlighted by red represent the third world and global south countries, ok. The editorial mainly focuses on the increasing bargaining power of the global south and that these countries are using this bargaining power to maintain their autonomy, ok. See this is the basic essence of the editorial. Now in this discussion let us see all points mentioned in the editorial in detail. Before that the syllabus relevant to the news article is given here for your reference just go through it. Now let us start the discussion by seeing the reasons for the rising bargaining power of the global south. See the first reason is the US desire to maintain its hegemony in geopolitics. To understand this we have to go back in history first. Before the world wars during the age of colonialism. It was the erstwhile British empire that had ultimate power over global geopolitics. Am I right? It was essentially a unipolar world with the British empire at its center. But what happened after the two world wars the British Empire lost its central position and in its place came the US and USSR. And from 1945 to the demise of the USSR the world was bipolar with the US on one side and USSR on the other side. Then after the collapse of the USSR the world has again become unipolar with the US at the center. This has been the scheme of things for the past three decades. But now with the rise of China the US is worried that its position is threatened. This scenario is called the Thucydides trap. See the Thucydides is a Greek historian who lived in the 4th century BCE. He said when a new power is rising which is threatening an already established power then war or a conflict is inevitable and this is called the Thucydides trap. Here the established power is the US and the rising new power is China. So based on this hypothesis a conflict is inevitable. So both the sides China and the US are fishing for alleys so that they will stand by them when conflict eventually arises. So both the US and China are trying to win over countries from the global south. This is the first reason why the bargaining power of the global power is rising. Now comes the second reason. It is the US desire to prevent the re-emergence of Russia. See after the collapse of the US-12 USSR Russia's sphere of influence has reduced. But under Putin's regime Russia is trying to recapture its old dominant position. This is why Putin invaded Ukraine and this is a worrying thing for the US. To counter Russia in Ukraine the Western led by the US provided military aid to Ukraine. In addition to this they also imposed sanctions against Russia to cripple its economy. But where the West led sanctions effective? No, Russia started increasing its trade with China, India and other countries of the global south. So for the sanctions to be effective the US needs support of the global south. So this is the other reason why the bargaining power of the global south has increased in recent times. Okay, now having seen this let us see the reasons as to why the countries of global south are not picking up sides and trying to remain independent. See the major reason is mistrust. The countries of the global south mistrust both the US and China. Why do countries mistrust the US? See all the US policies are motivated by self-interest. The US is now sweet talking with countries like India not because they like our country. But currently they need our country's support. They let me quote some instances where selfishness of the US and the Western democracies in general got exposed. First instance was during the wake of the first wave of the pandemic. When the developing countries asked the Western countries for an one-time exception for patents for the COVID-19 vaccine, they rejected it. They acted purely on self-interest and their actions were not guided by morals. The second instance was during the Syrian refugee crisis. No countries in Europe accepted the refugees in open arms. But now they are readily accepting refugees from Ukraine. This shows the racial mindset of the US and other Western countries. Last one the present US Federal Reserve action which resulted in the depreciation of currencies of developing countries. See the US Fed increased the interest rate. This resulted in investors pulling out money from stock markets of developing countries. This has resulted in collapse of exchange rates for various developing countries. And this move of the US Fed without consulting with other countries has angered the global south. So all these instances raised the mistrust surrounding the US. Now we will see why do countries mistrust China. See the global south's mistrust of China is self-explanatory, am I right? First China is militarily very aggressive. It has border disputes with all its neighbouring countries and the way in which China is vastly militarising is also a concern for other countries. And second is the dept trap diplomacy of China. We have seen this concept so many times, am I right? Now China is extending unviable loans to developing countries and making them fall into debt and this also increases the mistrust. Finally, almost all countries in the world are having a negative balance of trade with China. This is due to China dumping its good in other countries. See these are the reasons for the global south's mistrust for China. So since they mistrust both the sides, the countries of the global south are trying to stay neutral. While staying neutral, they are not isolating themselves. Instead they are engaging with both the western bloc and eastern bloc. The recent example for this is how India is trying to balance its relationship between the US and Russia. What is India doing here? India is engaging with both the US and Russia but not angering both countries. See these are the points discussed in the editorial. And finally before concluding, the author of the editorial mentions that the countries of the global south must use this bargaining power in order to bring the developed countries to the negotiating table and bring long term solutions in the areas of global concerns like climate change, ecological devastation, rising inequalities and increasing militarization. The global south must use this opportunity to make the world more inclusive. So that's all regarding this discussion. See in this discussion we discussed why the west and the east are mistrusted by the global south and we saw who are the global south countries who are called the third world. See in this we had covered the multilateral relationship regarding US, China and the global south countries. This is very much important for your mains examination. So kindly note down each and every points in this discussion and utilize it in your mains answers. Okay. So with these three points in mind, now let's move on to the next news article discussion. Have a look at this news article. See the news article is about the special tourist circuit announced by the central government. This tourist circuit encompassed five key sites associated with Dr. B. R. Ambedkar. The five sites selected by the government include Mo, his workplace, then London where he resided and studied, then Nagpur, here also Baba Saheb studied, okay, and then Delhi where he passed away and finally Mumbai where he was cremated. See this circuit was announced to increase the tourism potential of these areas. But the issue here is the various Ambedkarites and Dalit scholars or of the opinion that the places in the circuit does not do justice to the life of Dr. B. R. Ambedkar. Instead they want to add places like Rai Gaur district of Maharashtra where Maharsatyagraha was held and they wanted to add Erawada Jail where Poonapak was signed and they also wanted to add Sri Lanka where Baba Saheb attended the Buddhist Continent. These sites they said highlighted the true legacy of Dr. B. R. Ambedkar. And this is about the news article. So in this discussion we will see some major events in Dr. B. R. Ambedkar's life that are important for our examination, okay. See 1924 Ambedkar started Bhahishkrit Hitakarni Sabha and this is to promote education and socio-economic improvements among the Dalits. Ambedkar also started some journals for empowering the so-called depressed class. The journals include Moknayak, Bhahishkrit Bharat, Samat and Janatha. Then in 1927 he organized the Maharsatyagraha. The Satyagraha was organized to ensure the people from the depressed classes have access to water from the Mahat water tank. Through the Satyagraha he tried to ensure basic human rights. Then in 1930 he organized a temple entry movement in the Kala Ram temple at Nashik. Through this movement no he tried to ensure social justice. In 1930 Dr. B. R. Ambedkar participated in all the three round table conferences that were held between 1930 and 1932. While participating in the conference he represented the interest of the people of the depressed class. Then in 1932 when British Prime Minister Ramseh McDonnell introduced the communal award, the communal award was announced to provide separate electorates to the depressed classes. Mahatma Gandhi opposed it and undertook the fast until death while lodged in the Aravada Jai. So Dr. B. R. Ambedkar signed the Pune pact in 1932 and the Pune pact instead of providing separate electorate guaranteed reservation for the people of the depressed class. Note that Pune pact was signed between Ambedkar on behalf of the depressed class among Hindus and Madan Mohan Malavya on behalf of the other Hindus. Then in 1936 Ambedkar formed the Independent Labour Party. Through this party he opposed the Brahminical and capitalist structures in India and supported the Indian working class. He also sought to dismantle the caste system. Then in 1942 this party was transformed into All India Scheduled Caste Federation. And as we all know Ambedkar played a crucial role in drafting the Indian Constitution. He was the chairman of the 7 member drafting committee which was tasked with drafting India's new constitution. And in 1956 at a place called Dixabhumi at Nagpur Ambedkar along with his followers converted to Buddhism. He did so arguing that converting to Buddhism is the only way for the people of the Dalit community to gain equality. See whatever we have discussed in this news article are most important facts about Ambedkar and some areas of potential preliminary questions. Okay so we took this news article in order to make it very much useful for your preliminary examination. Okay so with these key points and facts let's move on to the next news article discussion. Have a look at this news article. This news article speaks about the Lokayukta. This is a news because yesterday the Supreme Court has stated the Lokayukta probe against to form a Karnataka Chief Minister. This is over a bribery charge and this is the crux of the news article given here. In this context let's learn about Lokpal and Lokayukta. First let us take up the Lokpal. See the Lokpal is established under the Lokpal and Lokayukta Act 2013. The main function of the Lokpal is to inquire and investigate into allegations of corruption against public functionaries who are falling within the ambit of this act. Okay now let us see about the membership. See the Lokpal consists of a chairperson and the member shall not exceed eight people. Note that the person to be appointed as a chairperson of the Lokpal must be either the present or former Chief Justice of India or the present or former judge of the Supreme Court or an imminent person with integrity and outstanding ability who must possess special knowledge and a minimum experience of 24 years in matters relating to anti-corruption policy or you can say public administration, vigilance, finance including insurance and banking, the law and management. So this is all about the chairperson. Now speaking about the members, see 50% out of the total members shall be judicial members. They must be either a former judge of the Supreme Court or a former Chief Justice of the High Court. Coming to the remaining 50% members, they have to fulfil the eligibility conditions same as an imminent person which I mentioned earlier. Okay, also know that at least half of the Lokpal members must be from schedule tribes, schedule cast, other backward classes, minorities and women. This is about the membership. Now talking about the appointment, the chairperson and the members are appointed by the President on the recommendations of a selection committee. The selection committee consists of the Prime Minister as a chairperson, then the members include the Speaker of the Lok Sabha, Leader of Opposition in the Lok Sabha, then Chief Justice of India or a Judge of the Supreme Court dominated by him and one eminent jurist. Okay, now we will focus on its jurisdiction. See the Lokpal has jurisdiction to inquire into allegations of corruption against public functionaries who are or who have been in the office including the Prime Minister, Ministers in the Union Government, then Member of Parliament, Group ABCD Officers and the officials of the Union Government. See also functionaries of any board, corporation, society, trust or autonomous body either established by an Act of Parliament or wholly or partly funded by the Union or State Government or also covered in the gambit of the Lokpal. Then it also covers any society or trust or body that receives foreign contributions above Rs. 10 lakh. So, this is all about the Lokpal. Okay, see for the centre we are having Lokpal and for the states we have Lokayukta. It was also established under the Lokpal and Lokayukta Act 2013. Its structure is not the same in all states. Some states have created only Lokayukta and some states created both Lokayuktas and Uppalokayuktas whereas some states have designated officials as Lokpal. Here the chairperson and the members are appointed by the governor of the respective state on the recommendations of a selection committee. Here the selection committee will consist of the Chief Minister as the chairperson and the members include the Speaker of the Legislative Assembly, Leader of Opposition in the Legislative Assembly. Okay, then for states those who are having Legislative Council know the selection committee should also include the Chairman of the Legislative Council and the Leader of Opposition in the Legislative Council. Note that while selection the Chief Minister has to consult with the Chief Justice of High Court. Like I mentioned already there is no uniformity regarding the jurisdiction of the Lokayukta in all states. See annually the Lokayukta presents a consolidated report on its performance to the governor of the state. Then the governor places this report before the state legislature and we have to note here that the recommendations made by the Lokayukta are only advisory and not binding on the state government. Okay, so that's all regarding this news article. See in this discussion we saw about Lokpal and Lokayukta. See these are some static topics from quality where you can expect straightforward preliminary questions. Okay, so these key points in mind. Now let's move on to the next part of the news article discussion which is the preliminary practice question discussion. See today we have three questions in which two I'll be discussing and one will be a quiz question for you. Okay, now let me take up the first question. See this is a previous year question that has taken from 2020 prelims. Okay, and it is regarding the pneumococcal conjugate vaccines. Since three statements are given let me go ahead with elimination technique. Okay, now let me take the statement three first of all. Okay, see these vaccines have no side effects and cause no allergic reactions. See this statement is absolutely incorrect because take any vaccine it will have some side effects and some allergic reactions. So you can easily eliminate two options if you know that statement three is incorrect. What are they? Option C and D. Okay, now going ahead with other two options. If you just know statement two is correct or incorrect you can arrive at the answer. Now read statement two. Dependence on antibiotics that are not effective against drug resistant bacteria can be reduced. See this statement is correct. Take the Lancet Journal. See the Lancet Journal in a study said that the pneumococcal conjugate vaccines have reduced the burden of antibiotic resistant bacterial diseases globally. So ultimately the dependence on antibiotics that are not effective against drug resistant bacteria can be reduced. That is why we say that statement two is correct. Okay, now what will be the answer? Since the question is demanding for correct statements the answer here will be option B one and two only. Okay, now let me justify why statement one is correct. See this we saw ultimately in the discussion itself. That is apart from pneumonia the pneumococcal conjugate vaccine is also highly effective against other diseases like bronchitis, sinusitis, bacterium A, meningitis, sepsis etc etc. So that is why I said statement one is also correct. Okay, now finally what is the answer for this question? It is option B one and two only. Okay, now moving on to the second question. Who among the following attended all the three round table conferences? Here three names are given. Dr. B. R. Ambedkar, Ratai Malai Srinivasan and Tej Bahadur Sapru. What is the answer for this question? Yes the answer is option C one and three only. See Dr. B. R. Ambedkar attended you are sure about it. We just now saw in the discussion. And along with him Tej Bahadur Sapru is the one who attended all the three conferences. When you take Ratai Malai Srinivasan, he assisted Dr. B. R. Ambedkar in the first two round table conferences alone. Who is Ratai Malai Srinivasan? He is one of the important Dalit leader from Tamil Nadu. Okay, so what is the answer for this question? The answer is option C one and three only. And now displayed here is a quiz question for you. See if you had keenly listened to the discussion it is a very easy question. So go through the discussion one more time and try answering the question. Post your answers in the comment section and the right answer will be posted in the comment section itself. Okay and displayed here is a means practice question for you. See go through the question, try writing answer for the questions and it will definitely help you in improving your writing skills. Okay and that's all for today's discussion. If you like this video, do like, share and comment and don't forget to subscribe to the Shankar Aiyaz Academy's YouTube channel. Thank you for listening.