A little bit extra time for folks to join us. Looks like that number is leveling off. Hi, everyone. I'd like to thank you all for joining us today for today's CNCF webinar, the cloud native storage for the enterprise. My name is Ariel Jitib. I'm a CNCF ambassador. I'm also a business development manager for cloud-native technologies at the company called Data. Today, I'm actually moderating the talk with a couple of my colleagues. I'd like to welcome Chris Mertz, principal technologist and George Starani, product leader for Kubernetes and cloud-native data, also in that app. A couple of housekeeping items. Before we get started, during the webinar, you're not going to be able to talk as an attendee. There's a Q&A box right at the bottom of your screen. Please feel free to drop your questions in there. And we'll get to as many of those as we can at the end. Reminder, this is an official webinar of the CNCF and as such, subject to the CNCF's Code of Conduct. Please do not add anything to the chat or questions that would be in violation of the Code of Conduct. Basically, please be respectful of all your fellow participants and presenters. Please note that the recording and slides will be posted later today to the CNCF webinar page at cncf.io forward slash webinars. With that, I'll hand it over to Chris and George. For today's presentation. Great. OK, well, thank you, Ariel. Hi, nice to be on today. Very, very happy to be on a CNCF webinar and be able to talk a little bit about how we've been enabling cloud storage, cloud-native storage, for the enterprise, including our enterprise, our customers. And today, I'll be presenting along with my colleague, George Turani. And George has been leading our product efforts around Kubernetes and cloud-native data storage for a number of years now. My name is Chris Meyers. I'm principal technologist in the NetApp Hybrid Cloud Group. And my focus has been for the last several years on DevOps and cloud-native technologies. So to get things started today, here's our list of objectives, basically our agenda for the day. We're going to talk a little bit about the state of state. George is going to kick it off with that. And then I will go ahead and talk about the inside view. How has Kubernetes and cloud-native affected our organization, NetApp, in that case? And we'll go through how it's affected us internally and spurred internal transformations. How Kubernetes and cloud-native technologies have affected our product and GTM strategic response and how we resource various products and efforts, engineering resources, et cetera. And we'll talk about a few example end-user cloud-native storage architectures that our customers are putting in place today. And then Hannah, back over to George. We'll talk about principles of cloud-native storage. And then we'll close it out. So without further ado, I will hand it over to my colleague and friend, George Tarani, for a little bit about the state of state in cloud-native storage. Thank you, Chris. Thank you. Hello, everyone. Good day. Hope you are well and safe in these crazy times. And we really appreciate you joining us for this webinar this afternoon. One of the levels said, if you could go to the next slide, please, Chris, if you don't mind. And Chris is driving today, so bear with us. Kind of level said, preaching to the choir, I guess. Stateless indeed is for TV. Maybe the only application that I know that genuinely has no state is Hello World. But any workload, I think we can agree on this, that any workload of value to the enterprise needs to be persistent. In fact, if you have a look at the Docker Hub, seven out of the 10 top images are stateful applications. So even the most basic applications, I think you require some kind of state. For instance, take Windows Notepad. You notice if you change the view option to wrap sentences. Next time you launch Notepad, it will remember us to do that exactly. So the point of the gist of what we're trying to say here is that indeed, whether you're running databases, line of business applications, you're lifting and shifting monolithic applications into containers, or even starting brand new cloud native applications, persistence and storage is a must. So with that said, and by the way, for those of you who are not familiar with the show Stateless, it's a great one. I think it's coming on Netflix, so I strongly recommend it. Anyway, with that said, let's go to the next slide, please, Chris. Very good. So they say you never know where you're going if you don't know where you've been. So in a prehistoric days of containers, the main objective was to basically accomplish the bare minimum, which was to connect external storage to your containers. So what most storage vendors did, NetApp included, was that we developed our own volume plugin. In fact, I think NetApp was the first one that published a plugin for Docker back in early 2010s, if I'm not mistaken. By 2016, I think it was noticeable that there was a shift to Kubernetes and this sort of ushered in a whole new set of users that weren't particularly storage experts. And so as a result, they wanted to manage data from the Kubernetes level, not necessarily have to do it at a storage level. In some cases, they didn't even have access to storage because, as you all know, still this is probably true that most organizations have a storage admin class that basically manage the entire storage infrastructure. But these new users wanted to bypass the storage admins all together and get to and manage the data from the Kubernetes level. And this was a catalyst for NetApp, basically transforming our open source posture and the way we contributed to the community. We merged our Docker code with a new branch of code for Kubernetes and named it Project Triton. Some of you might be familiar with it. This is, it's got a bit of a cult following. This project was the first external provisioner for Kubernetes. And now, fast-forwarding to today and what a crazy year 2020 has been, right? First, we almost started World War III. Then the Prince Harry and Meghan Markle stuck down from the Royals. And of course, now the global pandemic and COVID-19. Now, while all those events haven't directly impacted the open source ecosystem, it certainly has indirectly had an effect. I mean, for instance, QCon was postponed, unfortunately. And one could make the case that this period has allowed us to reassess our current predicament, maybe reevaluate our wants and needs. So one of those related to this particular discussion is that Kubernetes users want Kubernetes in containers and associated data with it to go together. They also want some form of a de facto standard for what makes up an application to Kubernetes. As you all know, there is not a standard today. Some folks have their own interpretations, but there isn't one that the community follows as a whole. And the application currently is a loose connection, collection of Kubernetes objects. The point is that we have some work to do as a community, but I'm glad that this community is focusing its attention to operations that matter, like application consistent backup and restore, full stack application migration, disaster recovery and so forth in a multi-cluster and a multi-cloud environment. Next slide, please. So I stole this from CNCF website. As you see, as evidenced by this chart, the cloud native storage ecosystem is very vibrant. And it's really a collection of innovative vendors who come from all walks of life, and which adds flavor and depth to how the community approaches, building out solutions for workloads and containers. Now, admittedly, some have a more profound understanding and impact because they bring in decades of experience in a multifaceted way, meaning not just solely focused on storage, but take NetApp, for instance. Now, NetApp's been around for 20-some odd years. Been sort of, and recently, in the past, recent past, the NetApp has been one of the most active contributors to the open source community. And that successfully re-engineered itself to become a hybrid cloud vendor. And we're able to draw from deep storage expertise as well as combining that with the mastery of Kubernetes. So this space, as I say, watch it, it's growing. We believe we're better aligning ourselves with customers' needs and wants, and we hope to cover some of those topics today. Here's Chris. All right, thanks, George. So bearing in mind that what I'm gonna present over the next few minutes is not necessarily in serial. This is what's happened over the last four years, and a lot of these changes have happened kind of in a flowing manner. So what I'm gonna show you in the next set of slides is basically a condensation of what we've done over the last four years as Kubernetes has gained popularity in the marketplace and eventually won the orchestrator wars. So 25 years of data storage meets cloud native, and it's actually 27, I think now, something like that. So we'll start out with this quote from William Gibson. The future is here. It's just not very evenly distributed. And that's how I would describe cloud native technologies in general, but especially cloud native storage and advanced cloud native storage architectures and requirements. Just to set the stage a little bit, for our organization, let's take NetApp IT, for instance, your standard corporate IT department. As almost as pretty much down the middle center of the road as you can get. So we came from a waterfall background. We transitioned to Agile. I've been transitioning to Agile across the board for the last number of years. And it used to look like this. You got your semi-annual releases and then you start moving to Agile to experience. But in the modern world and modern app development, our developers wanted to be able to push apps faster. We wanted to be able to get new capabilities out to our internal users with our corporate apps faster. We need to be more responsive. We need to be more responsive to the C-level, to marketing, to sales, all the things that happen in a shifting marketplace. When things change or you need to get new capabilities out to customers quickly, really the only option is to do CI CD or things that we would consider cloud-native today. Things that kind of came from DevOps and have transitioned to be baked into cloud-native. Things like CI CD, self-healing architectures, auto-scaling, stuff like that. So approaching this problem for us.  If you're going to be cloud-native everywhere both in the public cloud and on-premises and create hybrid clouds, to be able to do Kubernetes, containers, microservices, other types of cloud-native technologies and patterns everywhere you have to basically extend the cloud. So each cloud has a compute service for VMs. There's also a block storage service, also probably an object storage service, probably also a file storage service, maybe containers as a service or Kubernetes as a service and type of star KS. And then monitoring and observability to kind of tie it all together. And every cloud follows this basic pattern of surfacing physical resources into services that are consumable as metered, paid by the drip services for end users. Well, on-premises, if you're gonna create a cloud, especially with an I-towards cloud-native, you gotta do the same thing. You gotta have a compute service. You might be doing all kinds of things with that, including serving regular VMs, maybe VDI, which is just another form of VM. These are things that corporate entities run into all the time. Then you also have this modern app development. You've got containers as a service. You've got some type of Kubernetes service involved, depending on what flavor of Kubernetes your organization is going down. And then of course, particular to corporate entities on-prem, you've got a lot of business apps to deal with. So that's a little bit of a different story, but there's the analogs for that in the cloud as well. And then object storage, file storage, block storage, monitoring observability. So cloud is a cloud, is a cloud, is a cloud. It depends on how you architect it. So moving forward, so you build the cloud, what makes this a cloud-native experience? What's really about ease of use is one big part of it. It's not just about the technology, it's about how you deliver it and how you consume it. So it calls cloudy with a chance of I-As on-premises. So folks are looking for stuff that's always available, self-service, serial lead time, containers focused, capable of workload portability so that you're not running into lead times or waiting on troubled tickets. Everything's moving pretty much generally as fast as possible in the world of machine. So what does that mean for architects? Well, you've got to have self-healing designs, ways to create catalogs easy for self-service. You want this all to be API-driven so you can integrate it with DevOps automation platforms and tools of various types. Should be Kubernetes compliant and have hybrid cloud extensions to be able to extend what's on-premises into the public clouds and back. So what does this mean for corporate IT, evolving corporate IT leaders? Congratulations, IT, you are now a cloud service provider. So these are the types of things that folks who are cloud enabling cloud native within their data center have to deal with now. So how did we go about that? We realized MetFIT basically realized, okay, now we're a cloud service provider. What are we going to do about that? So this is how we organized ourselves, kind of a DevOps model, Hubbid spoke, line of business, app dev teams, with kind of an SRE role baked into that, going into what we call our IT one cloud, right? Which is, this is not a product we're selling. So just to caveat there, this is just an explanation of what our internal systems look like for NetApp IT. So we use a lot of industry products. A lot of these, most of these should be familiar with the folks on the call. And these are things that have to do with either our internal predilections for app development, as well as our partnerships. Because our internal IT systems, we tend to drink our own champagne, eat our own dog food, that type of thing. So we try to incorporate as many of our tech partner integrations as possible. So that we're absolutely sure that we're getting primary feedback from our internal teams. That, those third party platforms are built on top of an amalgamated NetApp platform, which has some of our storage and infrastructure products in it, as well as Trident, which George mentioned earlier, which is open source. Which basically is the connector for doing persistent volume claims and intelligent storage orchestration, et cetera. For cloud native workloads. So this is what basically took several years to get to this point, but now we're running basically cloud native, container space, Kubernetes driven CI CD, et cetera, so forth, to hybrid cloud, hybrid multicloud, if you will, because we're extending into all three public clouds. So that's how Kubernetes and cloud native technologies and especially cloud native storage have impacted us internally. So what about how it impacts our product strategy and has impacted our product strategy over the last several years?  Cloud consumer consumption context. So we've got new cloud native consumers. What is their consumption context? And these customer needs that we directly from our customers and prospects translated into our product strategy over the last several years. So what we learned was that, you know, folks who organizations, enterprises who are in transition need VMs and Kubernetes to coexist in relative harmony, that's a desire. There are certain flavors of Kubernetes that are dominating the commercial marketplace. You know, you've got your Anthos and your OpenShift and various other flavors coming in, Tanzu and Pacific, all kinds of good stuff going on in the commercial sector, but of course it all comes back down to open source, right? And folks are shifting their mindset from storage to persistence layers. You know, it's not about storage volumes or runs.  I can just, you know, put a config in a YAML file and less than a second later, there's my storage, right? So all of our future storage services and products must be Kubernetes ready. That's another thing we learned. And we need parity between the VM data services that we've been providing for years and Kubernetes data services. Also a huge, huge, huge part of this is workload mobility. We've been talking about app mobility, ad infinitum for a number of years with containers. And that's all well and good. You know, as George talked about at the top of the talk, you know, stateless apps work really well that way.  But what if there's data associated with that? What if there's a tight coupling of data associated with that application? What if there's a data-rich application? Then in order to make that portable, you actually have to move the app and the data in concert. And that's workload mobility. True workload mobility is hard to come by. And the folks who've been doing it today are generally rolling their own or using one of the, you know, the non-standard capabilities that exist today. But this is a problem that is currently being solved that is not solved yet. So how did that translate into our product strategy? Well, we became a founding member of the CNCF. And I'm saying this is not a drag slide. I really, I want to get this across. This is simply me sharing what we did as corporate entity to respond to a shift in the marketplace. And we've been very successful with that.  So I joined the CNCF founding member, significant ongoing engineering investment in our CSI Trident provider, which is open source. Warren, welcome to come take a look, download it from GitHub, submit changes, whatever you'd like. We had contributions to the creation of the CSI also ongoing. We did mandate and it provide Kubernetes integration for our current future products and services. That's not a blanket statement, but all those that make sense. And then we're still going through a massive application modernization effort that includes all of our base products. So, you know, constantly working with engineering teams and seeing how they're basically containerizing and turning our service, you know, various products that maybe sell architectures into microservice architectures. And some of them were born that way, Greenfield and the rest were transitioning. Also, you know, made great efforts to work with the public cloud providers to provide tier one storage services and partnerships, validated hybrid architectures with self saying partners and other third party vendors. This is to cover the commercial enterprise space and the spread, you know, the goodness of Kubernetes and cloud native technologies as far as we can. And of course, you know, microservice architectures underpin a lot of our cloud data services that are in production today. So here's just quick example, not a much customer use case. It's a major global network vendor. And I was able to kind of help set the stage for the architecture here for their internal development cloud. And it's basically as straightforward as you get. You got developers producing, you know, containers which are then orchestrated by Kubernetes and then tried into the peanut butter layer that attaches the persistent storage to the entire system. And this allowed them to accelerate their timelines and prove their scalability and reliability, et cetera. Also, global IT services vendor, you know, this is a more generic use cases. It allows them to provide cloud native services to their customers around the globe. And they chose to, you know, use OpenShift, which is an upstream brand of Kubernetes or close to it. And, you know, using the right type of cloud infrastructure on-premises enabled them to basically revamp their global systems for modern application development. Another example is a media and entertainment company in Amia and they are heavily data-driven, lots of media and data-rich applications, all orchestrated by Kubernetes and most of their, you know, applications are obviously container-based. And, you know, in this case it was more complex. They were using a lot of object storage. They wanted to make it geo-distributed, created containers as a service platform, as they called it. And, you know, to ensure there was data mobility between their systems. And this allowed them to, of course, you know, achieve the faster performance and, you know, the ROI improvements that they were looking for.  So, now we're sitting at this point and what I've noticed is that right now, even acceleration is accelerating. There's a lot that either, right now, it can be an opportunity to accelerate some of the changes and transformations that we've been undergoing in the enterprise and corporate environments. And so I think it's time to kind of look at the horizon line and say, okay, what's next? Are we gonna have standards for workload mobility? What is the community going to settle upon? And with that, I would like to hand it back over to George and he can show us a bit more about what's next. Thank you, Chris. You know, one thing you said that actually resonated with me, honestly, and that is things are accelerating much faster than before, aren't they? I remember when I was a kid, the world changed every 10, 15 years. Now it seems it's changing every month. Yeah, no, it seems like it's, what's terminal velocity? It's basically where the acceleration is accelerating. It's a bit mind-blowing at times, but yeah. Take it away. Sure, thank you. So we wanted to share with you just what we've learned from you and folks like you in the community and of course our customers. And I realized the priority of this list might vary, it's relative, but I think the characteristics of what essentially make up an ideal cloud native storage infrastructure for a Kubernetes environment, I think these generally cover the entire gamut. So cloud native should be highly available and, you know, with tiered performance SLA, it needs to know that it's running inside containers. It should, you know, wholly and completely embrace upstream Kubernetes and avoid deep integration or customization with branded distributions. There's nothing wrong with it, but we believe in order to, you know, in the spirit of keeping things open, you know, we embrace as an organization upstream Kubernetes. Last but not least, the world has changed, as we just said. Not everything's on cram anymore. Not everything's going to be in the cloud either. It's going to be somewhere in between. We go to the next slide, please, Chris. So just kind of drilling down a little bit on these, what does that, what do I mean by availability and high performance? You know, SLA's are of course important, right? You need robustness in the organization to make sure your applications stay up. And that is, that should also apply to your cloud native storage. Performance, of course, you need, whether it's IOPS latency or bandwidth, all these characters and parameters are important to maintaining a storage infrastructure that is consistent with the level of consumption as far as the applications are concerned. Good cloud native platforms should, you know, be supported by their respective vendors because not all organizations can solely depend on their own internal IT to do the problem solving, do the integration and consulting and so forth.  And the operational experience that I'm referring here is really that sort of that SRE sort of angle, right? It's one thing to know how one's hardware or software is architected and what its limitations are and how it operates, but to actually do it in a real life situation in a real data center, managing a variety of different types of use cases across the board. That level of experience, it's got to be sole service with all kinds of automation and have an observability angle, right? It's very important that the infrastructure teams understand their place in terms of where they are. Critically important to the organization when it comes to standing up services. But I think at the end of the day, the ideal scenario is to make the consumption model such that as users, we don't necessarily have to go to the source every time we want to make a quick modification or make a request. And last but not least, it needs to be programmable, right? If you want to deploy this at scale, you have to have the mechanism and the tooling to be able to do this in a fully automated way. Next slide please. So why it's important for the cloud native stories to know that it's running in a container environment because it understands what the consumption model is. It really goes back to that. And it also needs to integrate with the story services in the cloud. I read somewhere recently that 47% of enterprise workloads now run in some form of fashion in the cloud. If that's the case, then this is the new reality and as such, the cloud native infrastructure also needs to understand it, which means that if you're running your application today on-prem and you decide to the next day run it in the cloud, there has to be toolings and mechanisms and software and intelligence that knows how to move data back and forth in a way that it stands up the application in its entirety, not in pieces, not just volumes, not just the application cause, it's got to be a complete solution. It also needs to do a robust and solid cloud native storage infrastructure needs to provide traditional storage tools for the infrastructure folks. So as I said, the storage teams aren't going away. You'll always need that level of expertise. You may not need them for every particular, you know, opportunities in order to manage storage at scale. And of course, bringing it back to the user and application level. Basic data management functions and data manipulation capabilities have to be available at the user level from the Kubernetes sort of perspective. Snapshots shouldn't be exclusive to storage administrators. As a development manager, cloning capabilities should be readily available to the users and not something that is exclusive to the storage team. So some of the other characteristics that we think are critical. Next slide, please. Native integration upstream and downstream. What I really mean by this is obviously CSI is a great step forward. It sort of democratizes the way container orchestrators interface with the underlying storage. But of course it's early days and it needs to mature more and we realize as participants in the community and vendors who cater to customers that we need to do more and we need to do better. So that part, I think it's gonna take its own course and I think everyone is comfortable with the idea. But in terms of additional, surfacing up additional capabilities and features that exist in the storage infrastructure, the idea is I hinted to this earlier embracing the sort of pure upstream Kubernetes is important. Now you may choose to go to distribution that has particular tools and provides additional application level feature sets that are important. So long that the container orchestration piece is untouched and is consistent with the upstream Kubernetes, I think that is the key factor that differentiates it. And the other part is downstream with the actual, you know, the integration itself in the case of NetApp, for instance, we talked about Trident. Trident is NetApp's integration for Kubernetes and see what it's comprised of, what it's doing. So there are no sort of pockets of proprietary IP, intellectual property in those integrations. Next slide please. And I believe this is the last one of the four, right? So I hope you guys can hear me okay. Apologies if I'm dropping off. I sneak to lose packets here and there. So, and finally, the hybrid cloud use case, the cloud-like on-demand elastic and scalability in a way that how consumers use run their applications in the cloud. And of course, the Kubernetes infrastructure that supports those deployments, right? So whether they're hosted or gone prem or hybrid environment, the idea behind a genuine cloud-native storage infrastructure is to be able to accommodate all of those. Now, there are many tens of Kubernetes distributions that are out there, but it's important that the native to a particular cloud service providers, as well as the major distributions. Can you guys hear me okay? Sorry about that. I'm getting some message that some of you may not hear me. So let me just repeat myself one more time. My reference was to the cloud-like consumption of storage in line with how applications are consumed. And of course, last but not least, basic data management capabilities when it comes to storage. Being able to back up your important data, but not just the volume itself. This is the data in the context of full stack application consistency. So that you could back up your data application data and stand it up in a different cluster or in different cloud altogether in its entirety for a variety of reasons. Whether you wanna have a, be able to quickly switch over to a different environment and or you're doing this as a means of, for instance, if you're having a, Chris, could you switch over to the next slide please? Guys, apologies, my bandwidth seems to be a little bit unreliable here. I hope you can hear me. I'm gonna hear you, Josh. Okay, very good. Sorry about that. I'm actually connected directly to my router here, but I think everyone's home these days and this is understandable, right? I know how many of you folks get on Zoom or various other sort of collaboration software these days. And so freezing and losing packets that seems to be a commonality these days. So I apologize. In any event, one additional sort of component that I might suggest in terms of what to consider for your cloud-native infrastructure is to understand and sort of vet the idea of making sure that these, this type of storage provides the coverage for most, if not all use cases. And there's some in the deployment model, whether or not it runs in a cloud or on-prem and or as far as the storage back in itself is concerned. Chris, if you could go to next slide please? Excellent. So just wanted to close out and again, I hope you guys can hear me and apologies for the unreliability of my internet connection here. So I wanted to just quickly talk about Trident. We made references to it a number of times. This is a MedApps integration for Kubernetes. It's an open-source project and it's been around, I guess by Kubernetes standards for Eons. It's been around since 2016 actually. So it's a Kubernetes native application, which is to say it runs as a container in a cluster. The operator, the Trident operator monitors the obviously Kubernetes API server. And when it sees a storage request or a PVC comment, it processes that in real storage backing. It quickly sets up paths between the containers and the back-end MedApps storage. Trident is, as I said, it's an open-source software solution. It leaves a very small footprint on every node. So you only need to run one copy of Trident per cluster. So it's very lightweight. And I think importantly from the performance standpoint, because it is a control object very much like Kubernetes itself, Trident's not in the data path. So it really doesn't have any impact on performance. Chris, back to you. All right, thanks, George. Just as George mentioned a little bit about Trident here. And if you'd like to learn more about the open-source project, try to go to netapp.io or check out our GitHub at github.com slash netapp slash Trident. And with that, I'd like to just leave you with this consideration. It's not the most intellectual of species that survives. It's not even the strongest that survives, but the species that survives is the one that is able to adapt and adjust best to the changing environment. That is a quality that humans have above all is adaptability. And what we're finding is that tech companies and enterprises and corporations in the space, especially those that've been around for quite some time, can choose to either adapt or perish. So with that, for more information, if you'd like to join us in our developer and open-source community, there's netapp.io or the pub. There's also cloud.netapp.com, which is where you'll find out more about various things that we're doing in that space. Also our GitHub, Slack, Twitter, and by all means, please reach out to us more than happy to engage in conversation. And I think that is it. So I'm gonna turn it back over to Ariel and I think we're gonna do some Q&A. Yeah, so awesome. Awesome, thanks, Chris and George, for the presentation. We have some time for questions again. You can use the Q&A tab down at the bottom or just drop them into chat. And listening to talk, especially kind of dovetailing a little bit on your part, I wouldn't quote Chris. Can you speak a little bit to the barriers that the IT team and netapp encountered in adopting cloud-native technologies? Yeah, sure can. I think that, you know, I've talked many, many times with our IT team about their transformations over the years, starting with DevOps and then moving into cloud-native and really the biggest barriers that they encountered were mostly cultural. You know, getting folks to understand that just because you're changing consumption context, that doesn't mean that you're necessarily that what you know is becoming obviated or outdated. It just means that you're grafting new best practices and new modalities onto a worldview that you already have. So once people start viewing these transitions as career enhancers, career enablers, growth opportunities, rather than necessarily being concerned about, you know, resisting change, I mean, to put it bluntly, that's where you get past the first big bottleneck. And after that, it becomes a matter of assessing the organization's needs and then seeing what are your biggest blockers to tackle? What's gonna be the biggest blocker that's in the way technically? And fortunately, thanks to the work that had been done with Trident, you know, in parallel, we grew the wheels a lot on that one. Cool. And to dig into that, into Trident and storage a little bit, can you all kind of discuss a little bit, some best practices for data backup and recovery in this cognitive context? George, do you wanna handle that or? Of course, yeah. Sure, be happy to. Hope you guys can hear me. Yes, absolutely. So actually to the Trident users out there, I have one advice, and if you don't already know about this, we have a website which we affectionately called the pub, which is netapp.io. This is the home of all things open source, netapp, including Trident. And as part of that, we actually have published a four part series of technical blogs that specifically cover that very topic, Ariel, which is backup and restore by the way of using Trident. Now Trident itself, as I mentioned at the onset, is not an application or a backup application, I should say, it is really generally the means of integrating your Kubernetes environment to the backend network storage that is based on netapp storage systems. But we do have best practices that specifically cover that. And actually, if you don't mind, I'm gonna make a quick little segue and plug something to those folks who are still listening to us. On the 22nd of April, netapp is making some interesting announcements in our opinion. It's something that we're quite excited about. And it particularly targets this very topic, which is about application awareness, application. Yeah, what George is talking about is our, yeah, we are definitely gonna be talking more about this next week. So tune in on the various channels and it's pretty exciting. Okay, all right, cool. So thank you so much for the presentation again. And thanks to all the attendees for joining us today. Again, the webinar recording and the slides will be available later today. And we look forward to seeing you at the next CNCF webinar. Have a great day. Thanks, Ariel. Thanks, everyone.


Everything you do is in the best interest of those animals. If they're sick you're there to try and help get them better. Since I was a little kid I always wanted to do that. I always wanted to work with animals and specifically love the idea of the medicine behind it. The first year is very science based but you do jump kind of straight into the animal handling. In the mornings you'll do like a lecture on animals and then in the afternoon you'll go out onto the farm and be hands on and actually apply the knowledge you've just learnt. The facilities at Roseworthy are really good. It's a mix of old and new so there's the old main building which is really nice and then there's also like the brand new vet facilities with all state of the art kind of equipment. I think a lot of people don't realise the industry is not just cuddling animals all day during our cattle handling practice. We're also just getting covered in the mud and the poo and it's good fun. True life of a vet student.


Hello and welcome to theCUBE's coverage here. We are in the lake house at Databricks, Data Plus AI Summit, it's CUBE coverage. We are co-locating with Databricks' massive stage here. This is their media hub, Central theCUBE is going to be here for two days, wall-to-wall coverage. I'm joined by our CUBE analysts, new CUBEs and Rob Stretchy. Rob, we've been on a tour since CUBECon at Amsterdam. What a world win, and AI center stage. It's great to see you. It's data week too, so this is really exciting to be here and talking all about AI and data and how it's really going to turn. I just dropped an exclusive interview I had with Matt Garmin who was cheering the ship of Amazon to the promised land of generative AI. You Google out an event in Seattle, all developers. Snowflake had an event in Las Vegas, and here in Databricks in San Francisco, you got Databricks, it's data week, everything's happening, everyone wants that prize. The whole industry wants to win the mind share of this massively surging developer community. And we've said, Rob, we've been on the CUBE record now for months, open source will win. And you heard from Ali Ghazi today on stage, it's very clear that open source is a big theme of their history and their future and their present. And what's more exciting is he even dropped a few bombs out there by saying, we're going to end the format wars with this uniform layer bringing things together out of the metadata. I mean, bold move, Databricks really accelerating the game in the open. It's going to put a direct strike on Snowflake. It's going to hopefully level the play field. We'll see what's real. We're going to dig into the analysis. What was your take? Yeah, I think it was really well put together. I think there was a lot of going through it at rapid pace today. And I think they were really looking at how do they get to all of the content they had to get through. And I think a lot of it was around how is generative AI going to develop and how do you make it easier? I think also it was unified governance and how you can bring that together and democratization of analytics as well. And I think that's a big piece of it. Those were kind of the three big themes that they're taking with them and taking forward. One of the things I noticed knowing Ali Godsey for since the beginning of Databricks, he's been a candid Cube alumni. He was a mix of super excited and nervous because it was so crowded in there. I've never seen that audience that big for Databricks. He was delivering the lake house positioning 3.0, which was a combination of lake and house data warehouse. It's interesting, they're kind of reinventing data warehouse from the word lake around it, but that's kind of their focus. They're trying to get back into that world and modernize it, create a unified layer. And some things I liked was the delta sharing, the unity catalog and this format wars ending with uniform their positioning. I thought that was clever and just the sheer open source penetration that has legs and I think the question will be, will that be adopted? Yeah, I agree. I think it's going to be interesting. I think Ali was kind of pre-briefed us a little bit yesterday on this stuff and I asked some questions around some of these things and I think one that you're mentioning around the whole ending the war, it really, it's on by default, being able to do all those three different formats. Obviously Delta Lake is always there but the other two formats and bringing that in, I think what's key about this and what's going to be key in the future is that it gives much more spread across there and if you look at some of the other announcements that they're making, they're really focused on how they have a control plane, that data control plane going forward. And I think that's where the battle lines have been really underneath AI, that's where the battle lines are being drawn with them and Snowflake. Well, you know, we had Ali Ghazi on our SuperCloud event too, original I should say, he's won one, our inaugural event. He was also a keynote exclusive for our re-invent coverage last year and now with this Databricks data plus AI, every company will be a Gen AI company and that's his focus. You heard a lot of, not a lot of multi-cloud because we like to bring that term up, SuperCloud. Having Microsoft's CEO Satya Natala on stage or remote and Skyped in, they still use that word Skype. Not sure why they even keep that brand name, but that's a whole other story. He was Skyped in and it was a very interesting dialogue. One, two, it was not AWS, their big partner. They're doing more business with Azure so they're increasing their TAM. Databricks clearly going multi-cloud, so is Snowflake. This SuperCloud dynamic is happening, little bit kind of a submessage in the subtext of that kind of thing and I got to tell you, a smart move by Databricks by expanding in with Microsoft, they increase their total addressable market, they increase their customer base. JP Morgan Chase, again, joint customer of Microsoft. Satya Natala showing his chops, his technical, bringing infrastructure knowledge. Microsoft leaning in, winning the messaging war, winning the marketing war. It's pretty obvious to me that Microsoft clearly is outgunning AWS right now on the PR front, absolutely controlling the messaging and causing other clouds to be on the defensive. Yes, yeah, definitely, they're being reactive all the rest of the clouds and I think we've seen that over the last month and a half to two months, even maybe even a little bit longer and I think really when you start to look at how Databricks and Microsoft are messaging, it's really similar messaging in how they're trying to bring LLMs to the masses and how they're trying to really bring more out to them and be really clear about, hey, here's how you make it easy and I think one of the big things was, even though they're not calling it an assistant, which is really, you know, they're inside of their Lakehouse AI and what they're trying to do with the assistant that can help you build the queries for your Lakehouse and I think that's key. It's their version of co-pilot and there was a lot of talk with Satya about co-pilot which makes a lot of sense. The other thing I did announce was the marketplace was a big part of their initiative. Again, it's open to everyone and they kind of dinged the clouds by saying lock in and saying the clouds only optimize for their clouds which is true. So they're trying to build this federated kind of marketplace to be open. I thought that was interesting. You know, that combined with the Delta sharing protocol, you got some interesting open source power dynamics going on. I think that's going to be something we're going to unpack a lot over the next second half of the year, Rob. I agree, I agree and not only that but also their clean rooms initiatives which is the Delta sharing and when they started to look at Lakehouse apps which they didn't really go into that much but we kind of talked about it a little bit yesterday which is, again, under the hood, it's Kubernetes and when you start to look at it it's going to help some Greenfield customers extremely quickly get into a marketplace and be able to have security and governance over that by running on Databricks' infrastructure. You know, I always liked Databricks, I always liked their approach, I always liked the conversations but one thing that's notably different this event is they're stepping up their game. They got Moscone, 12,000 people's packs, 75,000 people online, both South and North packed venue. They're brand, they're stepping up. They could be a big player. They could be the dominant player in the modern data warehouse world which is essentially data cloud. They could be the dominant player for what we're talking about a lot here on theCUBE is having data products in a marketplace and then ultimately the term we coined called data developer, Rob, is really the emergence of what will be a new persona if these dots connect. If Oligotsi's vision, combined with what Matt Garmin told me in my exclusive, is that as this scale continues from data infrastructure reset with Generve AI, the data products enabling a data developer, those apps are going to come online, they're going to be running on the cloud, this will be a new power dynamic and the developer will be in charge of the data. We saw this with DevOps, we saw this with security now, shifting left, the new power dynamic will be the data developer.  Yeah, I think the data developer joined with platform engineering and what you have is them actually going out and engineering that data control plane. And I think with Lakehouse Federation, one of the announcements today, it's another one where both them and Snowflake are competing for the heart and minds of both platform engineering and that data layer, data engineering layer. Dave Vellante loves horse racing analogy, so we have to go with one here. A lot of horses on the track, they're clustered up, they're all kind of like jockeying for position, they're all kind of in a pack right now, some are ahead, some are not, but ultimately the other dynamic is people might be switching horses. You know, Amazon to Azure, this model to that model, choice is becoming a huge factor before putting things into production. We're still in discovery phase with generative AI and LLMs and foundation models. So again, tapering down the hype, which is all time high, generative AI is a game changer. However, it's early, we're still in discovery mode with developers, we're seeing people thinking about do I have the right horse for this? Is this the right model for that? How do I tune it and scale it? How much is it going to cost? Is it ethical? Do I run it on the cloud? These are all questions that are being asked here and in the industry. Yeah, and it's fascinating with the customers that are here and having some conversations with them already. Really what they're betting on is how are we going to be able to keep our data private? That message was super strong in the keynote today about privacy, about keeping your PII private, being able to actually monitor that and I thought that was a neat little demo that they did as part of that. I think again, there's a lot of hype around it. There's a lot of things that need to be figured out. A lot of swirling conversations around which cloud's going to be the leader. Databricks is not holding back. They could be an emergent kind of super cloud layer across all clouds, something that we've been tracking. I had an interview with Matt Garmin who runs the heads up Amazon's field and sales and operations, former EC2. So he's got technical chops, kind of like South Indian Nutella flexing his chops. I know Garmin's got some technology chops, which gives him a unique position. He was echoing in my interview with him some of the same points that Ali Ghazi was saying on stage and I want to get your reaction to these points if you don't mind. One, the AI potential and ethical concerns. I'll just run the list and we'll go through them. Securing data, amplifying choice. Augmenting human capabilities with AI versus replacing them. Innovating around some constraints and opportunities around GPUs. Little nuanced point we heard today. So let's start with AI ethics. Of course, adoption and consumption of AI. So let's start with the ethics piece. What's your take? What did you hear here? They kind of had the proverbial, it's not going to tell, whoa, we got to be careful. You know how I feel about that. I think everybody wants to be careful but I don't think anybody knows how to be careful yet. And I think it's early days in figuring this out. I think you'll see the industry come together as regulation is ramping up. I mean, you already have the first bill of regulation going through the EU. I think they have to get in line and they have to nail the ethics part of this because it's really key to not having it over-regulated or pushed back or stamped down. I'll say what everyone's thinking. I think it's virtue signaling. I think it's BS. I think there is no notion of regulation at this point. We got to get this stuff out of the garage and into the streets, into production. We got to watch it monitor it. That's the only issue. Regulation is a bad path for AI.  I think we got to avoid that. I think everyone's just virtuous. Oh yeah, we got to be careful. That's code words for don't regulate us. So I think that's one thing. The other thing that's the ethical issue that comes up that's not talked about is the intellectual property rights. This is what Ali was all about today.  Don't put that into the LLM. Matt Garmin and AWS also echoed that sentiment. Hey, that corpus is public. Once the genie's out of the bottle, you can't put that back in. So this is a huge issue around data and then how the data engineering, platform engineering has to now refactor to drive these new data products. Yeah, and I think even Satya brought it up with watermarking and things like that and how do you deal with copyright? How do you deal with intellectual property? These are huge and I think that to your point, most people, I was talking to a healthcare organization just earlier before coming on here and they were talking about how they're using Databricks but they're using it in a very private way because you're talking about people's healthcare information. You've got to be careful with that and right now you can't be using these SaaS-delivered public models that are proprietary to go and do this where you don't know where the data's going to end up. I got to talk about adoption real quick, fostering consumption and adoption. You heard that out there today. They're trying to push ease of use within the platform. These customers are diverse. JP Morgan's different than a startup, right? So you have different diversity of solutions that are needed from the infrastructure layer all the way down to the, up to the application layer. You're starting to see packaged solutions and hardcore code. So infrastructure, silicon, GPUs to the application stack and everything in between is going to be a huge adoption. Yeah, and I think that they actually had some really interesting stats on stage. They're seeing from actual use inside of Databricks where two exabytes of data is processed every day through Databricks and that in the last month they had over 1,500 actual transformers used within the Databricks environment. That's showing you some of the adoption and how it's really accelerating. That's up from 400 just earlier on in the year. So the other thing is cloud-enabled growth. One of the things that's come up is scale. Ali didn't really talk about it in the keynote because they're not the cloud, obviously they're in ISV by as far as the Amazon's concerned. But they got an ecosystem, 12,000 customers in person. So as you look at the cloud enablement here, you got to have the scale. And again, if people are going to be switching horses, how do you decide how to run this stuff on cloud? Do you run it on Databricks? On which cloud? That becomes an interesting factor here. The clouds are enabling at the end of the day all this innovation. And I think being across the clouds like you were talking about with SuperCloud, it does give you that data layer, that commonality of data layers across clouds. And I think that is a big key. They're not everywhere yet. I mean, there's still a lot of sovereign clouds that can't get Databricks. I think that that will be a challenge for them being that control plane long-term. But for a good portion of the companies and countries, they actually do a good job of that. And we heard about Mosaic ML with the GPUs. Yeah, you and I found out through the Grapevine, they got a stockpile of GPUs, but a lot of CapEx to build out.  One of the reasons why the cloud's looking good right now is AWS, and I'm sure Azure's got a bunch of GPUs. They can offload the GPU needs as a managed service versus having it on site. And that's an opportunity for Mosaic ML here with Databricks on the training side. Right, yeah, I think it is. And I think where they're aiming to be, the trainer, the builder, the underlying, I guess you could say infrastructure for AIML versus trying to be the ultimate only model you use. So it's the bring your own model concept, but how do you get to success faster with your data? That's where they're focused. And final point is enterprise demands are very much in line here. JP Morgan on stage, amplifying, almost gushing over Ali's celebrityism. Clearly a testimonial on stage. I mean, who's basically a walking data sheet for Databricks, highlighting the advantages of Lake House. He was almost as he was reborn. Like, oh my God, I came from the old way. I thought that was a very telling interview, really showing the needs of the enterprise is about governance and nailing some of the things we were talking about on our last cube, which is nail those foundational elements and then you can enable the value. That's what the platforms offer is that kind of enablement. That's a huge part of Ali's talk today. Yeah, I think they had Unity Catalog weaved within and throughout the entire keynote. And I think that they're standing on that as a differentiator for them and how they bring that to market over all the data layer. What's your final thoughts on the interview? Why don't you give it a grade? How would you rank it? Obviously they had a lot to go through. What's your thoughts? I'd give us a solid B. I'd say we'll be bringing it up a notch as we go through the day and get with some more people and get some more interesting content going. But I think we, you know, again, we covered all of the interesting facts. No, I'm talking about their keynote. Oh, their keynote? No, we're in A. Come on, we need to talk about B. We're in A. We're always at the A. We always got the A game. I would say, I'd give Ali, I mean, again, they had so much to try to unpack. I think that it got a little muddled at times but I'd give him a B. I think it was really good. I give him a solid A minus because it's hard to get an A out of.  I give him an A minus because, one, JP Morgan was an incredible guest. The way they were just glowing with testimonials. You don't, that's not stage, that's real. That's authentic. I can squint through that and say that was pretty real. Happy customer. His positioning was amazing. The Mosaic ML acquisition on the heels of the event was a home run for Databricks. The venue, the posture. They're standing tall right now and if you're snowflake, you got to wonder, there's almost two types of companies here, Databricks, Snowflake, both with different vibes and you got to look at that and say, it's like the republicans and the democrats. It's like, who's on side you going to pick? And they both work together though, so I thought that was a great move by them and the content was very developer education focused without placating to the crowd too much. They weren't talking down to the crowd. They aligned with the developers. I think this data developer theme is right on point for them. I think they're going to wake up and realize that they have an ecosystem that's going to be with them for the next 20 years. And so that room was very much aligned with some of the early days of VMware. It's a lot of demos, a lot of learning. So I thought A minus for sure, pushing an A, but again, the clock was tight. They had to go fast, overall great event. Yeah, I agree. I thought it was very energizing to say the least. All right, that's theCUBE's keynote analysis here inside the lake house on the floor of the Databricks AI plus data events summit. And you get theCUBE ongoing coverage two days, wall to wall. I'm John Furrier, host of Rob Stretching. We'll be right back with our next guest after this short break.


Hello everyone, welcome to the Narc Survival YouTube channel. Please hit the thumbs up button down below to show your support, thank you. Proof, narcissists do not love their children. There's normally no greater connection in this world than what is shared between a parent and their child. But unfortunately this is usually contaminated by the narcissist as they affect it with their bad and undesirable qualities. Because narcissists are not motivated by connection or love. They're driven by their desire to maintain their false image. Because how people see them is very important to them. But this then complicates their relationships with their children. Because they don't value genuine connection. They just view people as objects. And their children and relationship partners are often nothing more than trophies or fashion accessories. Rather than them being separate individuals with their own personalities, who have the right to live their lives under conditions that they decide. Narcissists view their children as possessions. They manipulate and control their children to their own interests or advantage without any consideration for them. Because they do not love them, they are incapable of loving their children. Instead they create the solution of the picture-pure family, which is really just based in shame and feelings of unworthiness and incompleteness. So they obsess over physical attributes and accomplishments. As though these are reflections of their own effectiveness, skill or expertise. There is a clear fixation on surface level characteristics, rather than emotional depth. Which actually destroys the potential of any real connection in the relationship. Their golden child is expected to meet their parents' standards and expectations. And in the process they end up losing their own sense of identity while developing narcissistic traits. Their scapegoat child is seen as though they fail to meet their parents' unrealistic expectations. And then they are devalued and abused. So Narcissists treat their children very differently. Because all they're concerned with is maintaining this illusion of perfection, which is based on their own ideas or opinions. But it may also be based on reference to whatever certain people in their lives deem to be desirable. So it's not always a one size fits all. It may not be suitable for or used in all circumstances. And in fact at times they will shape shift and try to mould themselves into whatever they think they need to be to extract the most validation. But that only works if their audience is on the same page about what they deem to be appropriate. Because otherwise it could have an adverse effect. They will often show favouritism to one child, where they're given unfair preferential treatment, often at the expense of the other children.  When the Narcissist isn't especially fond of the child, they're just using them to dominate and control the other children. The Narcissist is like the puppet master of the family dynamic. They are always pulling the strings. And each child is programmed and indoctrinated to behave in a certain way. Typically in an effort to win the parent's approval, other than the scapegoat child of course. Because the scapegoat child is the only one who truly understands the family dynamic and how it is affecting everyone. Which is why they are typically neglected or abused. While the other children may be showered with love and affection, especially in public. But even then it isn't real. The Narcissist doesn't really love their children. It's just something they use to gain aberration from people outside of the family. Which is why they will often neglect their children within the home. But then in public they will seem so loving and caring. Because that's how they want to present themselves to be. Even though they actually have no genuine concern for their children's happiness or well-being. All they care about is the show they put on for other people. Their relationship with their children is transactional and inconsistent. It's based on certain conditions, rather than the child being loved unconditionally. It's all about what the child does for their parents. And it's only when the child achieves their standards that they are then deemed to be lovable. But even then the Narcissist is never satisfied. So nothing their child does will ever be enough. And they will always feel like they're not good enough. But nothing can fill the void of a Narcissist. Nothing will ever make them feel whole or complete. But there are short periods of time where the Narcissist may shower their child with love and attention. If their child is doing something beneficial for them. But even then they just view their children as tools that they use to manipulate and control other people. And their children become their personal therapists. Someone who has to listen to them complain every day or mediate disagreements. Which are responsibilities that they should never have to tolerate or endure. As well as this, the child may also be used as a weapon against the other parent. Which may make them feel like they are trapped in an unpleasant situation in which they lack freedom. Which of course will cause them agony and distress. Because they're being deprived of the proper guidance, support and direction. And they're being manipulated and controlled by their parents. So that their parent can indulge in their delusions of grandeur. While their own needs and desires are not noticed or considered. Because all their parent is concerned with is their Narcissistic supply. They don't care about developing an authentic connection with their child. They just want to present an image of the picture perfect family. Which is actually very damaging to the child. As their emotional needs are disregarded. Because all their parent really cares about is their appearance and accomplishments. Rather than any emotional depth. Which destroys any real connection between the child and their parent. Because the parent just feels the child is an object with fashion accessory. Rather than a separate person with their own feelings once in needs. Which affects the child's personality and identity. Because they're in the copious amounts of pressure and control. They're not being allowed to develop naturally on their own. And instead the Narcissist molds them into their desired image. Because all they want is an extension of themselves. Which strips away the child's individuality. Even if the child tries to express their unique qualities and characteristics. The Narcissist will see this as an act of rebellion or defiance. And then they will coerce the child into compliance and submission. While also using the child that they show approval and preference for. To manipulate and control the defiant child. Because they're not concerned about the child's emotional needs or genuine connection. They're seeking dominance and control. So there is no room for love in that type of environment. Because they view their children as objects who has extensions of themselves. Who has pawns on a chess board. That they can use to manipulate and control the family dynamic. So they discourage self expression. Individuality and deviation from their expectations. And instead they suppress their child's identity. Because they're only concerned about their Narcissistic supply. About gaining approval and admiration from other people. But then in private they will be detached and disconnected. It's only when other people are around. That they will pretend to show an interest in their child. Because they don't care about their child's well-being. Their entire lives are a show, a performance. And everyone in their lives is just a supporting cast. When the child is a toddler. It may seem like the Narcissist loves their children. Because at that age the child is able to gain admiration from other people. And the child is obedient to the Narcissist. They're not even able to talk yet at that age.  As this thing that belongs to them. And the child always wants their attention. Which is a potent source of supply for the Narcissist. So it may seem like the Narcissist loves the child at that age. But as the child begins to grow older. And develops their own separate personality. That is when the Narcissist will begin to tune against their child. And try to suppress their development. Because any unique qualities or characteristics. Are seen as an act of defiance and rebellion. While Narcissist demand compliance and submission from their child. Because all they're really concerned about. Is creating this picture perfect image of a family. Rather than any emotional depth. Which is why the children who support and enable the Narcissist parent. End up losing their identity in the process. And they all typically end up becoming Narcissist eventually. While the scapegoat who receives unjust and unfair treatment. Tends to hold on to their identity. Rather than trying to conform to the picture perfect family image. Which is why they tend to be the only child in the family. Who is able to experience a genuine connection. And that is why the entire family tends to tune against them. Because Narcissist despise authenticity. It reminds them of how they're not authentic. And how they have to manipulate everyone. In order to get their needs met. Which is why if you are the child of a Narcissist parent. Your individuality will be mocked and ridiculed.  In an attempt to prevent the development of your identity. Because they see it as a threat to the illusion. It exposes them. Thank you for watching. If you found this video helpful. Please give it a thumbs up. Share your thoughts in the comment section. Hit the subscribe button to receive the notifications. If you would like to support the channel. You can donate at paypal.me.com. You can book a one on one with me on my website. It's narxiviver.co.uk. Thank you for watching.


Most designers don't know how to give feedback. So I'm here to share with you a system I use every single day. Note this down because believe me, you're going to need it. It's called the air feedback model. A stands for action, what they did. I stands for impact, the consequences. R stands for request, what you want them to do. Let me give you an example. Let's say someone on your team will not prepare to present in the weekly design critique. So you have to share with them this exact problem because that's what they did. That's the action. Tell them that this ended up wasting a lot of time and could have damaged the team's reputation as a consequence. That's the impact. Finally, help them get over their anxiety by letting them know that you want them to prepare slides in advance and that is your request. Did you note this down?


Sniff's so good. This bird sniffs so good. Yeah. No! No! No, it gets me! Finny! Oh my gosh, I don't have enough lemons. What? Sniffers, flighters, and hatchlings. My name is Marlene McCohen, this is Georgie, this is Brando, that's Merlin, and we have Rocky in here. In here. Welcome!  I love you guys so much, Patrick Williams, Barb, thank you guys for joining. I want to get right into this video because I'm absolutely so excited about it. You guys remember when I asked you to submit video imitations of me on TikTok? Well, here we are. I got your submissions and I'm going to react to them. Right now, also a hello to the early bird squad, I love you guys so much. So I invited George here today to react to because I figured that... His reactions are better. I think I'll enjoy this. Yeah. Okay. For the first act, we have a balancing show of a Merlin on a paper towel. Look at him. He's pretty chunky. He's holding himself up. Are you ready, George? Yes. Ty Ty! Ty Ty Ty! This is a submission from Kylie Cecile. Hello, my fellow sniffers, flighters and newbies. Welcome to another episode of Parrot Talk. Today, I'm here with Vinny and Vinny's been really naughty today. He ate the wall. You can't really see it unless I go on this angle. There we go. Vinny ate the wall. He's been dive bombing George all day. Vinny is obsessed with this new box of his and George charged it today, even though I told him not to, cody ate all my nails off, cody's in the Avery right now because she is just so rambunctious. It's unbelievable. Cody is crazy. Vinny has just come down from a big flying session having to do Vinny. I just love these birds, guys, but they are crazy. Stay tuned for like a part two or something if you want to meet my other bird, but always remember, engage in a cage. Vinny is about to dive bomb George again, guys. Dive bombing you. Very good. What's your favorite part about that? She's really good. She's funny too. Do you have something to say? I like the pink hair. I think that works for my mom. Didn't she do a good job? Yeah, very good. No, she did so well and also I think what was great is she captured like, like cody being rambunctious. Like it's really amazing to see what people remember. You know what I mean? And the box and the wall. You did a really good job. Good work, Riley. Video number two, live left birds. Hello, my fellow Snippers flyers and newbies. Welcome to my channel where I promote engaged, not caged. So today is a super exciting day and you're never going to believe what's about to happen. Vinny, come here. Vinny. Don't watch me sleep. She has a cage upstairs, yeah, in my room where she has a window and watches me sleep. That's so Marlene. I just can't. I can't. I swear that's the best shirt right there. The sniff is too good. The sniff is too bad. I know. That's the next one. I like that. That was really good. She did a really good job. And then I don't know, she captured the whole Brando situation. She really got the Brando thing. Like I don't know if anyone else is going to do that or pick you because you are The whispering and the nighttime when she does that. That's like exactly Marlene. Yeah. Such a good job. Good work gal. And then like she made this look at one point where she's like, it's really funny. Kimberly with a voice. Hello Snippers, flyers and newbies. Today we're going on a meet and greet. Let's go. I love this. Are you guys? Oh my gosh. I cannot. I cannot. Oh my gosh. Who is this? Who's the first person to do it? Oh my gosh. Who is this? Hi are you a sniffer? You a sniffer? Oh my gosh. Who is your bird? What's his name? Hot coconut?  Oh my God. You guys. You guys. You guys. Look at this bird you guys. Oh my gosh. Oh my gosh. Can I sniff you? Can I sniff your bird? Is that weird? Can I sniff you? Did you get permission? Bring it in for the sniff. Bring it in for the sniff. I think I do do that a little deep. I do that. This bird is acting like it's never been sniffed before.   Sniff so good. This bird sniffs so good.  Sometimes birds do sniff like they should. Sniff so good. Oh my gosh. Alexa play Britney Spears. You guys don't have Alexa here? Oh whatever. Hit me baby one more time.  My birds do that all the time. I have this box that you could subscribe to full of toys every month.  Sniff so good. She's such a good singer. Follow her. Oh my God. I'm so tired already. Do I ever say I'm tired? You're coming home with me. You're your mommy's baby. Mommy's baby. Mommy's baby. Mommy's baby. I might be a little bit. Kisses. She's got the lipstick on her nose. Kisses. She's so good. Oh baby baby. She's like a good actress and a good singer. Oh my God. I'm on her cheat sheet. She re-girded all my music. Nancy Tyrus. Hello my fellow Sniffers flighters and hatchlings. My name is Marlene McCoy. And today you won't believe what just happened. So I just walk in my house. You won't believe what he said. What did you just tell me? I think we should get another bird. What's on this Rocky? That's a good one. And this is Cody. What are you doing up there? As long as you stay there. It smells so good. By the way, welcome to my channel. Hope you like birds. If you don't like birds, then you should watch my channel. And if you do like birds, then you should watch my channel. Because we've got a lot of birds on this channel. Oh my God, should I forget? So what do you guys think? Should I get them? So good. She's top down to your excited one. It's so you. Remember we met her in VidCon? She was so good. I don't even know how she got her bird to do that. Video 5. Josie's guns. I think that was me getting Leo. That was really cute. I enjoyed that.  Yeah and she has a bird named Leo. That was what she was trying to say. So she was basically saying that she is Leo. Now we all know about her bird Leo. Yeah, very cool. Nice to meet your bird. Is it a dove? Yeah, I think it was a dove. Okay, next. Newbies today. George Coffee. George. Always want to interact with our bird. It's you saying that. Because you do that all the time. I don't say it's dying. It looks awful. Poor little guy. It looks awful. It's a living thing. That was so good. One thing, everyone looks so beautiful. They all try to be you. No, everyone really looks beautiful. Not trying to be me. They really look so beautiful. This is my take on all of this. And the red lipstick. Hello my lovely snippers, flighters and hatchlings. My name is Marlene McOwen. So my lovely flighters, let me introduce you one of my favorite birds.  Don't go out that door.  Vinny? Vinny, get down from there. Vinny, get down. Where's my coffee, George? You know, I can't work without my coffee. One thing I love to do with Vinny, I can smoke Vinny. I gotta take a good sniff. Don't bite me, Vinny. God, it smells so good. Next birdie I'm going to introduce you to my favorite and the newest birdie I've had. Now, this little birdie. She's so special and sweet and she's spoiled and she only likes sleeping with me at bedtime. That's right, look. That lipstick all over your beak.  Hey there, Marlene. Oh my God. He's a little shy right now but Marlene just puts his speech to everybody. She don't tell everybody else but he loves LL the best. What I'm going to introduce you to today is an African gray. African grays require a lot of interaction and they need a lot of trust. Here we go. Here is Cody. Hi, Cody. Cody is a Cody or is it Merlin? I know there's some pink feathers involved. He's Cody. Where's Marlene? Merlin, Cody. Merlin, Cody. Anyway, they're both fabulous birdies too. Well folks, that's another edition of Marlene McCullough. Next week we'll have another episode of Stay Tuned and Keep Sniffin'. Keep sniffin'. Keep sniffin'. Come on, Merlin. I mean, eee. All for you, Marlene. All for you. Look at me. Flower. That was so good. She had cutouts and she put the audio in it. She put the audio in it. Yeah, that's pretty good. Oh my God. Very good, Ella. That was so good. She understands me. What does she understand about you? I need my coffee. I love your coffee, George. This is so funny. That was so good because there was something hilarious. This is our house. Someone did this in our house. It's gotta be Mandy. Where's my coffee? I need my coffee. No, it can't be in this cup. It can only be in my blue cup. I will only take coffee in my blue cup. You don't have blue cup. George, have you seen my blue cup? George, I need my blue cup. That's right there. Thank you, blue cup. I found you. Oh, I need sugar. But don't tell Tracy. Shhh. I need my stylist right now. I can't even respond to anybody. You know I can't touch my phone with my fingers. Somebody get find me my stylist now. I love lemons in my tea. I think lemons cure everything. They're just amazing. Oh my gosh. I don't have enough lemons. George! I need to write something down. And I have a pen, but I have no pages to write on. There's just no paper. You know I can only write on my yellow notebook. Megan, help me find my yellow notebook.  Look at Vinny. He is so cute. I just love him so much. But really, this is my favorite shirt. You can order it on www.parastation.com You guys, this is my all-time favorite shirt. I just love it. This is my favorite. It just, it really represents what I stand for engage not cage. And this is my favorite. You can get it at www.parastation.com You guys, this is just my new favorite shirt. Hello my fellow sniffers. I don't know if you guys know this, but this is my all-time favorite shirt. Oh my gosh. I just love it. You can buy it on www.parastation.com I have just had the busiest day. And do you know what I need at the end of a busy day? At Jersey Signature Blend Tea it is the best. And no caffeine so I can share with my church church. It's great marketing. I want to buy that stuff now.  Tell me about your shirt. This is my all-time favorite shirt. You can get it on www.parastation.com Oh my god. This shirt right here is like my favorite shirt. You can get it at www.parastation.com No, no, no. www.parastation.com www.wessai Oh my god. This is like crazy because the people that know me like Megan and Mandy and Ella like I feel exposed. Yeah. And also coming down the stairs that's what I love to do. I can't do it. No I can't. Your closet is in color order thanks to me. So much. Let me know in the comments who you think nailed it. What you just learned about me. Honestly a lot of it's exaggerated guys. Some of it is very exaggerated. It's not exaggerated. It's so real. It's actually more real than it really is now. Anyway, so anyway I love you guys so much. Oh my god Eric touched me. Eric I don't like Eric touching me but also I love you guys and enjoy this. I'm cold. I'm cold. Well don't have it. Great cause George feels needed and he likes to feel that way. So this has been really good for him. Do you guys want to see how much it is really her? I'm just going to walk out of this room and we'll see how she calls for coffee. My coffee is right here in my little mug. In her mug. Enjoy this pygmy Marlene submission. Don't forget to submit your own. I'm always looking at them all. Follow the hashtag. I love you guys so much. Bye. Bye guys. Love you too.


Hello everyone, I am Venkatesh Bhingi working as an assistant professor in the CSC department of Walsh and District of Technology, Solapur. Today we are going to discuss Amazon EC2 service which is provided by Amazon. So before starting EC2 service, we will discuss about the outcome of this video. At the end of this session, students will be able to create instances of EC2. Second, deploy applications by using EC2 service. So what exactly Amazon EC2 service is? Amazon Elastic Compute Cloud, that is, Amazon EC2 provides scalable computing capacity in the Amazon Web Services Cloud. It eliminates your need to invest in hardware up front so you can develop and deploy applications faster. For example, suppose you have developed some application and you want to make it live without purchasing hardware, then that time you can deploy that application by using Amazon EC2 service on AWS and you can make that application live. Next you can use Amazon EC2 to launch as many or as few virtual servers as you need, configure security and networking and manage storage. So this is a flexibility which is given by the Amazon EC2 which you get according to your requirement, you can increase the capacity of hardware, networking capacity and storage capacity you can manage. It also enables you to scale up or down to handle changes in the requirement or spikes in the popularity, reducing your need to forecast traffic. And there is auto scaling functionality which is provided by the EC2. Next some services, virtual computing environment known as instances. It provides a virtual environment in the form of instances, pre-configured templates for your instances known as Amazon Machine Images that packages bits your need for your servers. So Amazon Machine Images is like a copy of virtual operating system which you get on your Amazon AWS. Various configurations of CPU, memory, storage, networking capacity for your instances known as instance type. So by using this EC2 service you can configure CPU, memory, storage devices, networking capacity also you can decide for your instance types. Secure your login information for your instances using keypads. By using public and private key you can secure your account. Storage volume for temporary data that is deleted when you stop or terminate your instances known as instance store volumes. So this is one of the best features which you get for Amazon EC2. And you also get persistent storage volume for your data using Amazon Elastic Block Store that is Amazon EBS. And you also get multiple physical locations for your resources such as instances and Amazon EBS volumes known as regions and availability zones. So these are the features which are featured by the Amazon EC2 service. And a few more, a firewall that enables you to specify the protocols, port, source IP ranges that can reach your instances using security groups. Static IPv4 addresses for dynamic light computing known as Elastic IP addresses. Metadata known as tags that you can create and assign to your Amazon EC2 service. So you can get a static IPv4 address for your application if it is required. And you can do the tagging for your application also. Virtual network you can create that are logically isolated from the rest of AWS cloud and that you can optionally connect to your own network known as virtual private clouds. So you can create virtual networks by using Amazon EC2 service for your own application according to your requirement. Now how exactly to use Amazon EC2 service on AWS that we are going to discuss? In order to do that, first you log into Amazon AWS by using your account. Log into AWS management console, sign into the console. You enter your username password. Now in order to create your user, now we logged into this Amazon AWS account.  Now you can see zero running instances, zero dedicated host, zero elastic IPs. Now we want to create instance of EC2, so what you say launch instance. Here you can select Amazon machine image AMI, which we discussed during slide show. What I'll do, I'll select one Windows free tier eligible operating system, which is of 64 bit, I selected this. So this is first step of creating instance. Then it is asking for instance type, that is how many cores it is required, how much memory it is required. Now I'm going for this free tier eligible one CPU, one GB, main memory. This is internal storage type EBS. So I'm selecting this because it is free of course, review and launch. Then you go to next, you can say you can select edit storage. Now this is the secondary memory for your application. I selected by default it is 30, I'll go with the same. Add tax if it is required, you can add tax for your application. This feature is required when you are using multiple application. Now here it is not required. Now security related changes also you can do like you can create your new security group or select existing security group, which we'll discuss later. And see this is the type of connection by which you can connect to this service, RDP, TCP protocol, the port number is this. You can give IP address, source IP address. And once you give this, you say review and launch, then finally you say launch. And here you say choose an existing key pair, I say launch instances. So once you get this message, that means what you have successfully created an instance for EC2 service, and the ID it is this. So once you click on it, you can see instance is in the process of creation. This is the instance ID and the instance type T2.micro. And the instance is created under the ability zone US West 2A. Still it is in the process, so it is showing pending. Once it is ready, it will show ready. It is getting initialized status checking. This is public DNS address IPv4. So my IPv4 address is <IP_ADDRESS>. And you can also check the details of configuration for your EC2 instance, clicking this down button. So this is the instance ID, which already discussed instance state. Now it is in running state. Now it has been in the state of execution that is running. You've got IP address for your instances also, which is live IP address. Instance type is T2.micro. Private DNS, this is for internal purpose. Private IP, this is again for internal purpose. And this is the built-in security group. Launch wizard and AMI ID also you can see. If Windows Server 2019 origin we have created. So like this we can create instances. Now the instance has been created. Now whatever the hardware configuration which you got with this instance, you can configure your application on this hardware. Now suppose I want to make any changes to instance. Suppose I want to stop this instance, you say stop. Yes, stop. So once it got stopped, you can see the status, instance status that is stopping. So still it is in the process of stopping. Again if you want to start, again you can say start once it has been stopped. And if you want to terminate, you can terminate your instance if it is not required. So you can see the warning message on EBS-backed instance. The default action is to root EBS volume to be deleted when the instance is terminated. Storage on the local drive will be lost.  Yes, terminate. Once it is terminated, see be careful when you are creating any instance on AD AWS because some services are not free of cost. So you say sign out. So once you sign out of it, that means you have completed this now. So this is how we have created EC2 instances. Now pause this video for some time and answer this question. Which of the following features is used for scaling of EC2 sites? First question. Second, Amazon Dynamite provides developers a tool to build failure resalent applications and isolate themselves from common failure scenarios. Think for some time and answer this. So the first answer is auto scaling. The second one is EC2. These are the references which I used to create this video. Thank you.