Well, go. Good. I hope you're here for this talk, a cloud native application management with the Stratos console UI. My name's Neil McDougal. I'm with SUSE. I've only got 10 minutes, so I'll go through this very quickly. Probably won't have time for questions at the end, so if you're interested afterwards, then come find me on the SUSE booth, which is just out on the right-hand side. The bulk of my presentation is going to actually be a demo. I figure it's a bit more interesting than just whizzing through slides. Skip that one. So what is Stratos UI? If you've not been to our booth and talked to anyone from SUSE, it's a management user interface, management tool that allows both developers and administrators to manage their Cloud Foundry deployments. You'll see these from various vendors, I guess. The difference with what we're doing is it's open source. SUSE has an open philosophy. So this is out on GitHub. You can go and try it now. We've got a team building it at SUSE. We're using it for our own needs, but it's extensible and customizable, and we are obviously moving the feature set forward, and it's easy to deploy. So why am I here? Obviously, I want to make aware of this project. I want people in the community to kind of take it, give it a try, give us feedback. If you find bugs, if you have feature suggestions, then let us know. And indeed, if you want to take it, develop it, add your own components, then we'd love to hear from you as well. And I think that's the GitHub URL. One thing we're trying to do, I think, is to propose it as a CF extension so that there's a good open source UI for Cloud Foundry. And we'll keep you posted on that. As I said, give it a try. We've tried to make it flexible and easy to deploy. So you can just CF push it. You can clone the Git repo, do a CF push. If you have a Cloud Foundry instance, and you're good to go, you can deploy it using Bosch. We have a Helm chart, so you can push it into Kubernetes. And if you just want to use Docker locally or Docker you can do that, too. I'm actually going to skip. I've got a ton of slides in case my demo didn't work, which I'm going to skip. And I'll just go straight into the UI. And I'll talk through what we've currently got implemented, which hopefully will give you a better view of what it does if I can switch. So this is the login screen. We authenticate against UAE. Then we only have two roles, so a regular developer and an administrator. There's not much difference with them at the moment. We've tried to build something that's well designed, have a UX team that helps us out. So I've logged in, authenticate against UAE. I've already set this up. If you'd come in to a fresh system, you wouldn't get this view necessarily. The key thing to start off with is what we've called endpoints. So we've tried to pick a generic term. At the moment, this just means Cloud Foundry. But down the line, we might want to use other or manage other kind of services from this UI. So it's kind of kept generic. And you can see here I've got a number of Cloud Foundries already registered and connected to the UI. So an administrator would go in and register a Cloud Foundry. So they would enter the URL and give it a name. So they would use this facility. And then each developer would log in. They can come here and they can connect up to the Cloud Foundries for which they have accounts. They use their credentials to ensure that they get the right level of access to each Cloud Foundry. And I guess one of the kind of differences here, maybe to some other tools you might have seen, is we're allowing you to manage multiple Cloud Foundries through one UI. So it's not a one-to-one mapping here. So I can connect up multiple. And I'll show you an aggregated view in a second. As I said, if I hadn't connected some up, then I can go along, connect, provide my credentials. Other things to notice here is we're working against the Cloud Foundry public API. So as well as a bunch of SUSE's Cloud Foundries here, I've also got Cloud Foundry from another vendor, just trying to show that we're not tied down to anything specific while their own Cloud Foundry always work against the public surface. OK, so as a developer, one of the things I want to do is know a bit about my applications. So one of the key views we have is what we call the application wall or the application view. Here, I get a view across all of my applications. I've already been in here, so if I hit Reset, you'll see I see all of my endpoints or all of my Cloud Foundries. I can't choose an organ of space because that will depend on which Cloud Foundry I've chosen. I can go in and say, hey, well, let me just look at this one. It's filtered down. I could choose a particular org or space. I can sort all that kind of good stuff. I can choose either a grid or a list of you. From the UI also, I can deploy an application. I'll kick this off now because it'll probably take a little while. We currently support deploying either from GitHub or Git URL or also from a local file or folder. So we use the same CF push code that the CLI uses. So we're not doing anything clever here. Well, we are, but we're not doing anything clever as far as the push concerns. So first, I need to choose which Cloud Foundry I want to deploy to. So I'll choose one that will just load the orgs and spaces. Hit Next. As I said, I can either choose a file or folder. So I could browse to a folder and choose a folder or I could drag and drop onto this UI if I wish, if I've got the code locally. Or I can choose a Git project. So let me just choose a sample one I have if I can spell it. Cool. So what it's done is it's gone out to GitHub. It's just fetched a bit of information about that GitHub project, what the current commit is on this branch. I could change the branch if I wish. I'll go ahead and hit Deploy. There'll be a little bit of setup. What that's done in the back end of the UI, we have a go back end and an AngularJS front end. It's cloned that repo. And now it's going through the standard push procedure. And we're streaming the log directly over web sockets in real time. That's going to take a minute, 30 seconds. So let me dive into the app view. So this is the view you see on an application. On the wall I just showed you, you could dive into any app and get this view. You'll see the bubbles here because it's busy staging, and then it will obviously run it.  Close that down. Add a number of tabs, which give me more information about the app. So as I said, log stream. This will stream the log in real time as well. I can see what services are bound to the app. I can also view the service catalog and bind service if I wish. I can create new service instances and all that good stuff, short of time. Let's see. I can look at the app variables. I can manage those, create new ones, delete modify. I can look at the events for an app in terms of what's happened in terms of a push lifecycle or enabling SSH, that kind of stuff. And I can also actually SSH into the app from the browser. So here, because I've been talking long enough, the app's actually come up. There's one running instance. I can see how much disk and memory it's using out of its quota. I can click on this one. That will select that instance. And I should. OK, cool. Get a SSH shell onto that app directly in the browser. So we're using quite a rich X terminal here, so I can do top things like that. I can obviously do a PS, if I could spell.   And in the background, it's already brought up another, although it's bringing up another instance because I've killed that one off. So that's an app. I can also edit it. I can turn off SSH access. I can scale it up, if I wish. If I can find it. There we go. So I could have three instances, and you'll see it'll update. And that should ping. And we see those being created. I can get size. Oh, it's busy at the moment. I get CLI information. I can start, stop. So I could do general app lifecycle operations for here. So that's pretty much what we've got there. Very quickly, I'm running out of time. Cloud Foundry itself. We provide some management of Cloud Foundry. So because I've got three registers in connected, I can go into this view where I get a tile for each. I get some overview information. You can see I'm an admin for the SUSE ones, but not for the other one.  I can see the organizations. We have some read-only views, which give you information about your security groups, your stacks. You'll see I've got the open SUSE stack on this one. You can see the feature flags, that kind of stuff. On the organizations, I can see my orgs. I can drill down into spaces. And when I get to the leaf, I can see my apps, my services, and some routes within those spaces. And from here, I can also create orgs, create spaces. I can manage the user access to those orgs and spaces. So that's pretty much it from a high-level run-through.  I'll just get through all this. So this is what I showed you. I think the deck will go out, so you'll have screenshots. But obviously, you can check it out yourself. I'll just touch quickly on this at the end. We've tried to build it to be customizable and extensible. So we have a kind of component model. We have a back-end front-end. You can build components that extend either of those. So much of the functionality I showed you in terms of SSH and being able to push, they're all done as components that plug into this UI. You can do branding. You can add in tabs to various places. So if you don't like the SUSE branding, you want to take this UI and use it for your own customers. You can easily create a new theme that removes our branding and push your own in. If you don't like any of the strings, it's fully localized, so you can create your own language pack. You can add languages for whatever new locales your customers may want. Okay, so hopefully that was a quick whiz through what we've done in terms of UI. Open source, please go take a look. Tell your friends. We'd like to get more people involved, either just using it and giving us feedback or helping us to move this forward. That's me. I will be outside if you want to come and speak to me. I'd love to talk to you. Thank you.


And finally for the International Roliston Award, which harm reduction international gives out to an individual or organization whose contribution to harm reduction has international significance. And what we talk about when we mean international significance can be any number or a variety of different things. It could be the pioneering nature of the work, it could be demonstrating courage or leadership in the performance of that work. It could be the resilience of a particular individual or organization. And of course the impact of the work that that person or organization is engaged with. And on behalf of Harm Reduction International, I'm very pleased and excited to present the International Roliston Award to Edo Agustin Nasusian. Edo is an Indonesian drug user activist who has worked to address stigma, violence and discrimination and violations of human rights against people who use drugs for almost 15 years. His work began in the year 2000 at the start of the HIV epidemic amongst people who inject drugs in his native Indonesia when he founded the first support group for people who use drugs living with HIV in his hometown of Medan, North Sumatra. He later co-founded the first self-organized group of people who use drugs in Bogor, West Java. Since 2011, Edo has coordinated the Indonesian Drug Users Network, PKNI, one of Asia's strongest, most resilient national networks of organizations of people who use drugs, representing the common priorities of 24 self-organized drug user groups across 19 provinces in Indonesia. Under Edo's leadership, PKNI developed into one of the most effective drug user networks across Asia and globally, gaining international traction through their advocacy on work on HIV, hepatitis C, harm reduction, service quality and drug policy. Through PKNI and through his lifetime work, Edo has worked tirelessly to improve the status of people who use drugs from mere objects of service delivery to informed, valuable stakeholders in the national response to drugs in Indonesia and globally. And I'd like to present Edo to you. Thank you, Rick. This is a big surprise for me. Okay. Yes, first of all, I would like to thank you to Harm Reduction International for this award. On behalf of the Indonesian Drug User Network, Prasodara and Korbanabsa Indonesia, I feel honored and I want to dedicate this award to the drug users community back home in Indonesia and all around the world. I am who I am today because the drug users community and many long-standing allies who have always been strong believers in drug user activism, together we will continue to fight for drug use to be decriminalized, for drug policy to be more human and for more investment in harm reduction and drug user movement. To all the researchers, practitioners, experts, government officials and donors in this audience today, continue to involve people who use drugs in every aspect of policy and programming. We are always part of the solution. Thank you.


I'm Joe Eichle, the Extension Weed Specialist at NDSU, based out of campus in Fargo. Out here at the Carrington Research and Extension Center today to do a virtual tour of our crops school. So what we're going to do now is go through our annual and popular herbicide motive action demo plot. So we've planted about eight crops one direction with some weeds and sprayed single active ingredient herbicides the other direction and we'll talk about symptomology of the herbicides on crops and weeds to figure out what we have out here. Our first herbicide stop here I'm standing in spring wheat is the crop and as you can see the spring wheat is actually very dead. So we've got a dead wheat crop if I look at the round of the weeds I'm looking at we have some wild buckwheat some of that is controlled some of the buckwheat still has some green in it and looks like it will go on to survive. Another weed I'm seeing quite a lot of is common malo some of it is untouched some of it has chlorotic symptoms but none of the malo is actually going to die here. So the weeds we have surviving wild buckwheat common malo we have killed our spring wheat crop if you see the strip behind me most things that we have are dead if I look at the other weeds or weed carcasses in this plot we've done a good job on a broad spectrum of weeds. So this would be our group 9 herbicide which is glyphosate controls a lot of our weeds and our crops but can be weak on some vines such as wild buckwheat common malo is another weed that we can have some weaknesses on. We don't have glyphosate resistant weeds in this plot so that's why we don't have any other escapes that we might expect in some parts of the state. For our second herbicide I'm standing in our corn block so here we have a round up ready corn hybrid what we're seeing is our corn is purple and chlorotic and stunted if we look around the weeds in this plot all the broadleaf weeds are untouched zero symptomology we have some wild oat and other grass weeds they are also chlorotic and turning that purple color so we have a herbicide broadleafs aren't affected grasses are affected pretty slow to work this is one of our group on herbicides in this case this is cluthidum the product we sprayed was select max so beyond the discoloration of grasses we can also pull out the growing point of grasses so for corn can bend down pull out the top of the world and we'll see in the chronic growing point that's a textbook symptom of a group on herbicide. For our next herbicide I'm standing in our pea block so what I'm seeing here is our peas are very stunted there's a lot of necrotic tissue on the peas if I look around the weeds that we have in here our grass weeds are largely unaffected we do have excellent control of some of our weeds there's two weeds that we did miss have no activity on them common lambs quarters and horseweed so those two broadleaf weeds no activity we do have some dandelion in this plot and there's some necrotic speckling of the dandelions as well so our symptom is necrotic tissue more activity on broadleaf weeds not a lot on grasses and we missed a couple of our broadleafs in this case we have a group 14 herbicide and we used fumesifin which is known as flex star or reflex so good on broadleaf weeds we missed some like lambs quarters and horseweed and we've not labeled for peas in this case for our next herbicide we've moved into the soybean block so I'm seeing what the soybeans they are stunted chlorotic and the veins of the soybeans are black or purple shows up better on the underside of the leaves when I look at the weeds we have a mix of activity on weeds we have some activity on grasses some on broadleafs it tends to be very species specific and the the symptomology is chlorosis and it's all located mainly on the new growing points of the weeds here so this would be a group two herbicide in this case we use trybenuron which is express so symptomology shows up on new growth and then on soybeans those black veins are textbook group two injury on soybeans for our next herbicide we're back in the soybean block when looking at here the soybeans are once again injured symptomology is chlorosis to bleaching on the newest trifoliates the the injury is located more around the leaf margin but we can see some trifoliates completely injured when I look around the weeds we've controlled our small seed of broadleaf weeds we have some large seed of broadleaf weeds escaped and some grass escapes what I don't see in this plot are any weed carcasses so we mix things up every year and do throw some pre-emergence herbicides into this screen and that's what we have here in this case a group 27 herbicide we sprayed isoxa flutol which is balance not labeled for soybean and we're seeing the textbooks symptomology of bleaching showing up on the soybeans here okay our next herbicide we're back in our pea block what I'm seeing here the peas are very twisted the growing points are are losing some color as well so very very effective on the peas when look around the weeds our grass weeds are all unaffected when look the broadleaf weeds all the broadleaf weeds are showing the same symptomology as the peas so we're seeing some twisting or some epinasty and some discoloration and really severe injury on some of the growing points so in this case this is a group for herbicide in this case we did spray dicamba so effective on most of our broadleaf weeds does nothing to our grasses as far as crops that we would spray this in sprayed in our grass crops or dicamba tolerant crops such as extend soybean okay our next herbicide we're back in the soybeans what I'm seeing is most of our soybeans in this plot are dead the soybeans that are along the edge of the plot they received a partial dose of the herbicide we have some unique light green symptomology on those soybeans when I look at the weeds our broadleaf weeds are mostly controlled we even did pick up our wild buckwheat that we missed in an earlier plot our grass weeds I see some of our grasses are dead some of our bigger grasses there is still green at the base and they're starting to grow out of this symptomology so a broad spectrum herbicide on grasses and broadleafs this is our group 10 herbicide which is glufosinate or liberty on a non-liberty link soybean broad spectrum can control most of our broadleaf weeds can be weak on grasses especially once they get some size on them for our last herbicide we're back in the corn and what I see here is our corn is severely injured there's a lot of necrosis expectually on the ends of the leaves if I look at the corn on the edge of this plot we have a lot of necrotic spots that have a halo around those spots when I look at the weeds our grass weeds we've controlled several but we have our large grass weeds that are escaping this application excellent control of many of our broadleaf weeds but we were weak on common lambscorders and on wild buckwheat so a broad spectrum herbicide effective on grasses and broadleafs so what we have here is our group 22 herbicide which is paraquat or grimox stone it's here's an interesting thing that we see in these demos every year we actually expected a little bit more activity out of paraquat especially on our on our grasses but we kind of get these weird things that happen every year and this is actually a real world situation where sometimes for whatever reason we have not teased out our herbicide was not as effective as we hoped


Hello Really excited to be sharing with you this Countdown 30 days to wiki tree day 15th anniversary happy October fest. I don't have an anniversary shirt yet. So We could get Ricky Dave's shirt, but so until then it's October, you know, so that's right So What we're going to be doing is each day we're going to share a question Most of them will be from past question of the weeks if you've been following wiki tree on social media we have a question of the week that we do and that's where most of these questions will be coming from and From those if you can answer each day's post We'll do a random drawing from the respondents So the next day so tomorrow same time same channel same bad channel As we do the drawing And let me go ahead and share that today's question Okay, is do you have any innovate innovators in your tree? So answer this post On your favorite social media account and we'll do a drawing from everybody who responds And of course we're talking about wiki tree day Yes, there's a link for that And if you haven't registered Please go out and register. It's a free Genealogy symposium and it's going to be from November 2nd through the 5th So we're counting those days down to to that to that event You've got some amazing speakers lined up for the starting on the Thursday night on the 2nd and then all day Friday and Saturday Like well-known Genealogists from around the world. So that's amazing. Yeah, it is. I'm so excited in there Fine doing good good, but we're just shared what the Question for today is Excellent. Do you have any innovators in your tree? And we'll be drawing From everyone who responds for a prize Well, that's really exciting Vicki's here All right, well, I think that's all we we have to share it was there anything else you wanted to share a win I shared the link for wiki tree day and I shared the Registration where people can go out and register for wiki tree day Fantastic, yeah, nope. We're just gonna pop in every day. Let's you guys have another chance to win something cool All those cool prizes Okay, well, I'll go ahead and QS out. Thanks everybody for tuning in. We'll see you tomorrow for the prize draw


Okay, welcome back. This is theCUBE. We're live here in Silicon Valley in San Jose Convention Center, heart of Silicon Valley. This is Hadoop Summit. We're here live for two days. This is theCUBE. theCUBE is Silicon Angle and Wikibon's exclusive coverage of Hadoop Summit. It's our flagship program. We go out to the events, extract a signal from the noise. I'm John Furrier, the founder of Silicon Angle and I'm joined by co-hosts. I'm Dave Vellante at wikibon.org. Tomer Shiran this year. He is the Vice President of Product Management at MapR. MapR is a company that has been going hard after this big data in Hadoop business for quite some time now. Adding innovations, making Hadoop Enterprise ready is really what MapR is all about. Tomer, welcome to theCUBE. Thank you. So give us the update. You guys, as I said, you kind of just don't get involved in all the urinary Olympics, I like to call it. You just kind of focus on the customers. You dive right in, trying to solve problems. Give us the update on MapR, M7, which is your platform. How are things going? Yeah, things are going great out in the field. A lot of new customers. The things we do at MapR is we make Hadoop Enterprise grade. We bring customers all the innovation that happens in the open source community. We combine that with our own innovation to make the platform more Enterprise grade and we provide significant architectural advantages if you look at things like being POSIX compliant and offering full, random read-write access so customers can just mount the cluster that they would mount a giant NAS and integrate all their standard tools. Yeah, there's a lot of things there for the customers. We're way up front on that one, right?  It's not something you can add kind of as an incremental patch to the existing systems. Maybe add some color to that, if you would. Talk about the underlying architecture. I'm inferring from what you said that there's an architectural flexibility. It allows you to add features in a way that are not bolt-ons. I'm inferring a lot from that statement, but I wonder if you could just double-click on that a little bit and share with our audience what you mean by that. Sure, we've, talking to many, many companies that use Hadoop in a lot of the largest enterprises now use MapR as a distribution. What we've found is there are a lot of limitations with kind of the other Hadoop distributions in terms of, for example, only being able to append the files, essentially, HDFS being a read-only file system. And so MapR has really come up and solved those problems by providing the ability to do random reads and writes and the ability to expose a standard storage interface. So it's very easy to use the platform. And those kinds of innovations, like having an NFS interface, are only possible when you have the underlying random read-write capability that we've built. And that's not something that can be just bolted onto HDFS. You know, the same things apply for all the enterprise-grade business continuity. If you look at things like high availability, not having a name node or snapshots for a point-in-time recovery with full consistency or disaster recovery across data centers, those are all features that are unique to MapR and they're enabled by the advanced architecture. Tom, I've got to ask you, obviously, MapR M7, big news here. Also, the joint testing with Fusion IO company, we've been covering since they've been private, now public pioneering the Flash SSD space for, you know, on server side, among other things, just really changing the game on IO and then these, you know, we call up, you know, software-led infrastructure, software-defined infrastructure. What have you guys found? Because obviously, writes and reads is a big debate. You know, get these data lakes out there being talked about. HBase makes a great opportunity to take advantage of those data lakes. What did you guys do in M7 and with Fusion? What have you guys, can you share with the folks some color behind the Fusion relationship and that announcement? Yeah, absolutely. So, you know, MapR's M7 edition is all about bringing together the different types of the Hadoop workloads as well as the NoSQL workloads with the ability to run HBase applications in a production environment. So M7 is all about enterprise-grade HBase in addition to Hadoop and having that one platform. From a performance standpoint, you know, we've solved all the inefficiencies that otherwise exist in the software layer and with M7, it's really all about driving, you know, we're really able to drive the hardware at its raw speed. So if you look at technologies like SSDs and specifically Fusion I.O., that brings to the table, you know, additional performance improvements at the hardware layer that MapR can uniquely take advantage of. If you look at other Hadoop distributions, they're bottlenecked in the software and I've seen blog posts talking about how Hadoop can't benefit from SSD. I think we heard that today it won't benefit from SSDs in the next three years and really that's because, you know, there's inefficiencies at the software layer that needed to be addressed and MapR has addressed those. And I think the other point there is, you know, most customers, they don't want to run the entire cluster just with SSDs and so MapR gives them the ability to provide tiered storage where they can do some workloads, for example, the HBase type workloads on SSD and other workloads on the spinning disks. It's funny, we've been, you know, it's funny for watch and interesting to watch, not so much funny, but it's just funny to watch that the early criticisms of MapR and that when you guys were founded and launched, oh, well, they're non-standard, et cetera, et cetera.  But now everyone's catching up to you guys with this enterprise grade messaging. So I really want to ask you, you guys have stayed true to your mission on the enterprise side, really building, using open source, building a product for the enterprise. So just comment anecdotally if you can, just on everyone else kind of catching up, because Merve said it's the bike race where everyone kind of catches up to someone else. Or have they caught up? Are you extending your lead? And what have you found in the enterprise that's going to keep you ahead of the pack in terms of differentiating on that enterprise grade? Yeah, so certainly the MapR... Take your choice. There's a lot of questions there, but the MapR message around being enterprise grade and the features and the capabilities we've delivered to accomplish that. You know, we see our competitors talking about wanting to be enterprise grade or providing features that may sound similar to MapR. So to give you an example, some of our competitors talk about H-based snapshots. Well, snapshots are all about point in time recovery. Well, H-based snapshots don't have any consistency in them. So they're not snapshots. And if you read the JIRAs, they talk about maybe we should rename these fuzzy snapshots so that we don't confuse the customers and why don't we just let's leave the name and we'll document it and things like that. So I think it's great validation for our approach to the market, for our strategy that everyone talks about enterprise grade and our competitors want to have their features called similar to MapR's features. But there's no silver bullet though in the enterprise. I mean, it's clearly, it's not a one size fits all marketplace. I mean, do you agree with that statement? Do you see it differently? I mean, there's no one Hadoop. It's a lot of different solutions depending upon the use cases, right? Or how do you see that? Well, I think Hadoop in itself and specifically a lot of the things we've done are about enabling more and more use cases to run on the platform. You know, one of the things that sometimes people don't realize is that with MapR you get the benefit, all the advantages of the open source and the open source community and any new open source projects that happen or that come up or are integrated into the MapR platform and our customers enjoy our 24 seven support on those. And then we combine that with our own innovation so the customer gets the benefit of both worlds. So talk about that a little bit. So let's talk about that in the context of yarn. So how does that statement apply to something like yarn? Take us through sort of a practical rollout from a product standpoint. Yeah, so you know, there's, you know, I think one of the presentations this morning talked about Hadoop being not one project but many projects. And so yarn being one of the projects in the Hadoop ecosystem. We at MapR, we're really excited about yarn. We'll have a GA release with yarn later this year. Yarn is all about expanding and the use cases for Hadoop and enabling interactive queries as well as batch and streaming and so forth on the single platform. And by bringing that innovation that's happening in the open source community to our customers, to MapR users, they can take advantage of that. For example, projects like Apache Drill which are about interactive SQL queries, those are baked into yarn. Those run within the yarn context and they're part of that. And I think what you'll see going forward is that yarn will enable new types of workloads running within Hadoop and by having that unique underlying platform that MapR has which allows any application to access the data, not just applications that were designed for Hadoop, all of a sudden you'll see things that can run in yarn like MPI which will only be able to access the data when they're running on a MapR distribution. Okay, so classic example of you guys adding value to an open source component. All right, so what's next for you guys? What's the roadmap look like? Give us some hints. Yeah, I mean, if you look at the MapR, we traditionally haven't talked that much about our futures. We haven't set up conferences and talked about futures of Hadoop. We talked about futures of Hadoop. Futures of Hadoop. What kind of gaps are you guys going to fill? Right, our vision for Hadoop is the one platform for big data. As these clusters grow bigger and bigger and MapR now has customers that run over 1,000 servers in a cluster, that's where the data lives. And it's not really possible anymore to kind of move the data around to different other systems for different types of access to that data. And so it's all about expanding the use cases and the types of access you can have to that platform and then continuing to provide more and more enterprise-grade capabilities so that customers, our enterprises, are comfortable using this in the most mission-critical environments. Tellmer, thanks for coming on theCUBE. Vice President of Product Management at MapR, obviously one of the big pioneers here we call them, we're part of the big three, Hadoop, CloudEra, Hortonworks, MapR. You guys have been there from the beginning. Congratulations, great company. We've been following your progress, big fan. Again, we think this model's going to evolve faster and faster and faster. This is theCUBE, this is Hadoop Summit. I'm John Furrier with Dave Vellante. We'll be right back with our next guest after this short break.


Currently still on my staycation here. Another place by the Israel Lebanon border called Tel Kedesh. It's actually a historical site. We're actually are going to Hula which is kind of along this direction. This is the sign here. It says in Hebrew, Atsur Gvula Fanecha, which means stop. There's a border ahead of you. This sign is placed wherever you are in Israel, where you're getting really, really close to a border. And basically telling civilians don't go any further. It's forbidden to go any further. So I'm not going to really push things too far here. And this is an extremely rest of border. It's probably safe to say. This is what I find fascinating about this part of the country. Maybe about this border in general and about even the Gaza border is it's so deceptively peaceful.  And yes, there is probably a lot more going on here than meets the eye because this is basically not exactly at this point, but pretty close by around where we were yesterday, where Hezbollah were found to be digging this elaborate underground tunnel network that the IDF announced and neutralized slash destroyed. And it's kind of widely understood that Hezbollah or our God forbid, planning a some kind of a mass infiltration event right across there until Lebanon. They are committed to Israel's destruction, massive, massive armed force. And so the IDF is for its part, continuously reinforcing this part of the border. There are some natural obstacles in terms of cliffs. It's a very, very cliffy area as you go towards the border. And there's a cliff on the Lebanese side, but they are doing what they can to keep an eye on it. And it's probably safe to say that the Lebanese side is gathering intelligence kind of all the time as well. So yeah, this is the border sign here. Just saying this is as far as you can go. And from this point, from this point forwards, it's probably either private agricultural land. In some cases, the army actually closes it off to position a base there. But we're looking northbound here into southern Lebanon. Coming into the Kedich National Park here. This is an ancient historical area.