Hello everyone, I'm John Furrier here in theCUBE Studios in Palo Alto for a special CUBE conversation. Breaking news here in Silicon Valley and at Cisco Systems. News around Cisco partnering with Amazon Web Services. And here to talk about is Fabio Gorey, Senior Director of Cloud Solutions Marketing at Cisco. Good to see you, welcome to theCUBE. Hello John, how you doing? So big news, Cisco and AWS collaborate to accelerate innovation. A first kind of this kind of announcement. Love the pioneering aspect of this announcement. Obviously Amazon Web Services the leading cloud provider who's been into hybrid cloud lately because they've been talking about that as their connection point into the enterprise. You guys are the leader in the enterprise that networking and other services, I don't even know how much market share you have these days but you guys pretty much own the enterprise, everyone kind of knows that. This deal with Amazon, you guys are doing the first hybrid Kubernetes on AWS. Talk about the announcement, why is it so important to Cisco? So you name it, the solution name is actually a bit of a mouthful but you mentioned the three key words, is hybrid, is Kubernetes, is the AWS. And this is the first solution of this kind that really integrates this two environment in a way that will be exceptionally beneficial for organizations that want to accelerate their innovation path, which ultimately means delivering application faster without having to worry about constraints in terms of where to develop, where to deploy. It really set them free to take their decisions.  One thing that's been very clear is the public cloud has demonstrated speed, agility, faster time to value, and for app developers that's been great. Cloud native, if you're born in the cloud, it's just a great environment. If you've been on-premise and you had that legacy and or existing pre-cloud environment, that trend has been more towards cloud operations. So not so much everything's moving to the cloud, although Andy Jassy would love to see everything move to Amazon and that's his goal. But stuff stays on-premise going to be for a while. But the cloud operations on-premise is essentially cloud but on-premise. So that's this new hybrid dynamic. This is what enterprises have been reimagining their infrastructure on. This is where a lot of the energy has been. How does that, your solution for Kubernetes with Amazon solve that problem? Does it help customers get to the cloud faster? Is it an operating model? Explain the nuance of how customers have done that. It's fundamentally all of that. If you think about it and your introduction is spot on, is customers really want to use the public cloud, right? The services in the public cloud. Why? Because it gives them speed. I think that's a big change that we've seen since I would say a few quarters, right? Where people started really trading off speed and innovation for cost, right? It originally was like, I want to shut down my data center that the cloud is going to be cheaper. Well, it's not about cheaper, it's faster. And people want to develop new digital experiences which boils down to building application faster. So what ultimately they want to do is making the infrastructure on-prem looking like a bit more like the public cloud. Now it's never going to be just like the public cloud with all the bells and whistles and innovation. But it's got to be such that you can actually take the best innovation of the public cloud, Kubernetes first, to the on-prem rather than the other way around, right? That's our North Star, that's our belief. And Kubernetes is really a big winner in the container market. The way to develop new application is based on containers. Kubernetes is the orchestrator right now in the marketplace. Every single big cloud provider has launched Kubernetes based services in various forms. And so the enterprises are now looking at and businesses of every size, they are trying to figure out how to really develop this capability on-prem because in the end, as you know, it's never kind of black and white, right? We're still working with mainframes. Long life to the mainframe is going to be around for 20 years probably. We're going to have traditional databases, ERP systems and the likes for very, very long time. What do you do, right? Everything that you develop new in the cloud needs to ultimately connect back to the existing systems because that's what you need. So the simplicity of things is interesting. I want to just rewind that for a second. So you're taking the best of Amazon container service, last container service with Kubernetes, making that available on-premises through the Cisco container platform. Correct. So this is the linchpin. So it's almost like you're not trying to take Cisco and saying, oh, we're cloudified. Correct. You're taking the Cisco environment, which everyone runs and some people think it runs great and they're going to change that overnight, but you now enable them to take what they're doing here and make it compatible with the cloud and on-ramp to the cloud. So the idea is fundamentally not so much taking EKS on print. That's not the thing. But the idea is having a container platform that fundamentally gives you pretty much a transparent way of interacting with the other side. And when I say transparent, I really mean the linchpin or the solution which is around the identity and authentication. What we've done that really differentiates this that makes it so unique right now is that we have integrated the IAM in identity and authorization, sorry, and authentication in common. So you're going to use the same set of keys on both sides, which of course is the developer dream because you don't have to use different type of keys and authentication models if you're a user. It's the same thing. And it's a dream for IT operation because of course this is much simpler as well as for the CISO and the security team. This makes it extremely secure, reduces the risk so that you have really a very consistent integrated kind of solution, which is... So there's engineering involved on Cisco side. Can you elaborate on... Actually it's been a collaboration between the two sides. Explain the partnership. So it's been absolutely, it's actually a collaboration. So we've been collaborating to build this integrated architecture. It is a Cisco solution but developed in collaboration with AWS. And so what we've been doing is fundamentally looking at how EKS was going to be available to the container platform so that you'll be able to fundamentally orchestrate your containers in the most efficient way regardless of where the containers actually end up being. Which is actually what we're hearing from customers. Customers want to just take the containers that are coming from the developers and being free to develop whatever they want. Sorry, to deploy whatever they want. So the containers are key here. So the container service and Kubernetes orchestrates containers works across what the identity layer allows for what seamless interaction. Is that the key for developers? Is that I could take me through a quick use case. Explain it with an example. I don't know, you may take a new application that in the banking, on the banking side you can take some new artificial intelligence kind of applications or machine learning. What you fundamentally can do now is deciding, well first of all, what kind of tools you want to use. You want to use the AWS cloud with all the development tools. You want to use yours. It doesn't matter. At the end, there is an end over between the developers and the IT operations team. And the IT operations team now with this solution can fundamentally quickly and easily provision clusters wherever they want. And they do it on the basis of their specific parameters, their specific goals. What do you want? It could be cost, it could be security, it could be reliability, whatever it is. It doesn't matter. This is not about the religion of whether it's public cloud or on-prem. It's just using the best of both worlds and deploying whatever it makes sense. You know, Andy Jassy and I always talk when we reinvent and he always comes back to the same refrain. He always hits the same notes. We listen to our customers. We're driven by the customers. They take us where we want to go. I know Cisco has been very customer centric as well. How has the customer's reaction? What have they been telling you around why this solution is to develop? I mean, because we know shadow IT's been going on with Amazon for almost a decade. Put their credit card, they sneak up on Amazon, build some stuff and look how easy it is and then bring back to the IT department saying, hey, look what I did in the cloud. Now you implement it. Whoa, we've got network policies. So there's been kind of that kind of tension, kind of R&D if you will, but it's still happening. That kind of goes away here with this kind of announcement. How has the customer needs been profiled as you look at the announcement? What's the key reasons why they want this solution? And why did Amazon glob onto it because they're not going to do something unless it's a customer need. Let's talk about that. Well, I would say it's really meeting the customer where they are. And again, we have two environments that have been inspired by different kind of criteria. As a lot about application modernization, it's a lot about security, it's a lot about compliance on-prem. Of course, the cloud is also very secure. I think we're over this kind of artificial discussions, as AWS will say, is a shared responsibility model, right? They guarantee the security of the cloud and you're responsible for the security in the cloud. And so ultimately what people want to have is, how can we actually integrate these two worlds in a consistent fashion, right? So that I have a consistent environment that's really the key word here, consistent environment where I have common Mino networking between these things, whatever they are, common Mino securing them, including authentication, identity and authentication. Common Mino monitoring this application because the alternative is building another silo. And that's what people don't want to do, right? If I add another silo, I may add innovation but it comes to a very high cost. People want to add innovation without disruption. They want to have this consistency and just extend the way they do things. Of course, going into a DevOps model and getting faster and faster because that's the way to compete. I think IT operations is an area with the development and enablement you guys have had and with the work you guys have been doing with DevNet and DevNet Create, this notion of programmability, you're right in line with the wave that everyone wants to ride, which is lower the cost of mundane tasks and or scripts and things of that nature, command line interface, that's kind of like a hodgepodge. Make the network programmable and automate and make the developer freer to do better things. It seems to be the trend line. So with that in mind, does this fit that horizontally scalable vision of the cloud? Do you see this having impact into, say, network sales, application? Where's the key impact points for the customer? What impacts them? It's a huge impact, right? And it depends whether you're taking like a tactical view of things, like a literary application by application or classes of application or you're really thinking about where is this trend kind of taking you, right? Now, if you take the former kind of approach, then you're starting kind of identifying a whole bunch of different issues, like again, for instance, the security one, the networking one is huge, right? People go, I don't know, Office 365 and they get disappointed. Why? Because all the traffic gets trombone through the data center because that's how things are aware, right? Now you're completely changing the application on top and you discover that the infrastructure underneath hasn't been designed to accommodate those kind of traffic flows, right? And so you're starting solving problem by problem. The fact of the matter is, with the rise of the cloud, the infrastructure and the processes in IT need to change altogether. It's infrastructure, it's processes with of course the rise of DevOps. It's relentless automation, right? Potentially driven by more and more machine learning and AI kind of capabilities. Just talking about that because this is a big discussion because I'm interviewing a lot of CIOs or CXOs or senior IT practitioners and the ones that are successful, the ones who recognize the wave, some people take different steps, they'll experiment, they'll do some tests, some will just go all in and revamp but they all recognize the one point. They got to re-architect and re-imagine the IT infrastructure up and down and the cloud is a big forcing function, a role of data, programmability, automation, not new concepts in some cases, containers we've all been around for a while but how do you guys talk to your customers? Because this is something, first of all, do you believe in that? And two, what do you talk to your customers about when you're saying, look at the hard truth is how we got here is not how we go forward? Absolutely. Well, you know, there are different ways. You can either boil the ocean or for instance, you take a solution like this. If you take a solution like this, you can actually sit down and discuss how to build a solution and architect a solution like this in collaboration with AWS, they took establishing four key principles, right? The first one is got to be hybrid, right? Which means you need to strive to build this consistent environment between the two domains. Second, it has to be production grade. We're speaking with customers adopting Kubernetes, they're saying that they get to a point where they need to integrate 20 open source tools.  Can you actually do it with a kind of approach? Third, and this is a big one, you have to be able to manage this new hybrid reality, managing just the new apps, but the old apps as well. And fourth, it's got to be extensible. You're starting from containers and authentication, how about everything else, right? How about cloud management orchestration? How about application performance management? Because now apps are getting everywhere and of course, you know, that's probably the next episode of theCUBE that we can do together, they're going to the edge. So it's getting very, very complicated. So even with a simple quote unquote example like this, you're starting seeing some principles that you need to establish, and they should inspire how you actually transform your infrastructure and operation. The worst thing that you can do is taking a tactical approach and just going step by step and, you know, move by move. Well, let's definitely do that, Cube. I have a couple of statements I'd love to do more of more of a deep dive with some slides. Certainly the edge is going to be a big point, but I want to ask you the impact to your customer base because I think this is a game changing announcement. I mean, Amazon web services, they don't do a lot of Barney deals. They don't do a lot of deals that look good on paper. They're very specific about how they do their business development. So it's a huge win for them, I think, and for you guys. But I think Cisco customers are going to be impacted. So please explain the impact of Cisco customers. What does it mean to me? I'm a Cisco customer. I've got routers, I've got switches, I've got UCS servers, I've got all kinds of stuff in there. How does this impact my life? What changes? Do I throw away gear? Do I buy new gear? Do I buy software? How do I buy the service? Am I buying Amazon? Do I have Navajo? Explain all that. How does the customer engage with the solution and what's the impact of their environment? Well, that's a very big question. Let me frame it a little bit, right? First of all, how are they impacted? They're impacted by the cloud altogether, right? And very often they're using multiple clouds. We know it's multiple services. So they need to start thinking in terms of those principles that we said before. From a company standpoint, of course we've been well known over the last 30, 35 years, right? Not to leave everybody behind. We're trying to, of course, accommodate the change of the infrastructure. And for instance, how do you move from CLI to more programmability? Through, for instance, the rise of IBM, which is the intent-based networking, where you have more policy-based models that help you fundamentally automating the network. Whether it's about connecting your data centers or connecting your branches, you have to fundamentally adopt more and more automation into your strategy. And so what we're doing is we're fundamentally helping customers, making this kind of transformation. You mentioned DevNet. I think that's like the tip of the iceberg of also a new Cisco Wave, right? Where it's all about, if you want, transforming the talent that's been working with us in the company, and outside the company, and having them taking it to the next level, where instead of going classical CLI, you're more and more kind of thinking, you know, not to make the fashion, because you have to get fast. The only thing that really matters is getting faster. I noticed you guys, I'll just give you guys a lot of props here, because you guys have a lot of meat on the bone with this announcement. Simplifying container orchestration with the Cisco Hybrid solution for Kubernetes on AWS, Linux Foundation wants to see it that way, Amazon's that way. You guys have a lot of code up and running on the sandboxes and for the folks watching, developer.sysco.com slash awsdeveloper.sysco.com slash AWS. You already got sandboxes up already. Five labs for cloud native. You got the EKS cloud. Yeah, I will continue adding more and more material. The cloud is a different world, right? People want to experiment it. And by the way, if you think about how we're packaging and pricing the solution, you can actually start in a very modular way, right? You can just go with the software if you want, or you can buy the software and the hardware underneath. You can go with one, three, or five years. You can get demos of this solution. It's, if you want, it's a different way of experimenting Cisco, but we're there. I mean, we made the change. We're totally for adding a software motion to an already strong kind of hardware component that has been traditionally our strength. And if you think about it, having the full stack, we can do some magic. If you buy a Cisco software, like this solution, and then you put it on Cisco hardware, such as Hyperflex and ACI or data center infrastructure that a lot of customers are using, you get fundamentally a greater performance. You get a single number to call, which is actually. You know, it's interesting, Fabio, and I talked with Lutuck a years ago, and then I'll continue to talk to him every year, as well as Susie Wee. And we see this on the cloud native, born on the cloud side. IT doesn't exist in a lot of these cloud native companies because the developers do all the IT. So you guys are seeing a surge in DevNet and DevNet Create where the Cisco ecosystem, your customers are turning into developers naturally. And so we've seen that shift at Cisco. That has happened internally. You guys recognize that the developer ecosystem, not the cloud native, but application developers, and that your command line interface guys and gals are turning into developers, because when you're slinging code these days, it's pretty straightforward. You can look at our, actually, my friend Susie Wee, and how is she is pitching this change. She talks about DevNet Ops. Others talk about DevSec Ops. Whatever that is, you know, whatever kind of terminology you're using, it boils down to the same concept. You have to automate the way that you manage the infrastructure, right? Infrastructure needs to become more responsive and faster. You can open five or six trouble tickets just to provision a container to a developer that that's not going to cut it in the future. It's got to be fast. Yeah, and making the network programmable is the Dev Ops movement that's coming 2.0. Absolutely.  It's interesting to see how Amazon relates to that. When you talk about that to AWS, what's the conversations like? They obviously get it and they're smart. They must get it immediately. I mean, absolutely. The reason why we're having this collaboration is very simple. I mean, they get the same request from the customer. We're fundamentally speaking to the same people. Yeah, there may be differences in terms of the developer versus the IT operation. But in the end, it boils down to the request, hey, you know, the public cloud is fantastic, but I also want to have a solution for a prem, right? I have my needs. And if you're not totally born into the cloud, you have to, you want to have investment protection. You want to have your own prem environment for whatever reason, right? And it's not about religion, it's about economics, it's about viability of certain solutions and the likes. Well, great news, congratulations. Fabio, great announcement with Amazon Web Services. Good deal, hybrid cloud. Now, you guys also Cisco, you guys aren't married to one cloud, so I got to ask the hard question. What impact to Google, Microsoft, do you guys have relationships? How does this match up from a integration standpoint with other clouds? Is it deeper? Is it more coming on the other clouds? Can you just kind of give us a description of the evolution of Cisco with the other clouds in this hybrid architecture? Yeah, you know, I want to stay true to one of the principles that we mentioned and we orbited around this conversation, right? For the last 15 minutes. And that is, we're customer centric, right? Customers want to use the clouds that they want to use. We're there to help them, right? Now, AWS is, of course, if you look at the share, it's a pretty big market leader, but we will work with all the providers that our customers want to use. That's actually the North Star that we have. Now, if you look at the kind of, if you want products or stacks or architectures, you will see that there is a huge degree of commonality across all of this, right? So we're using kind of the same baseline software, but configuring slightly different ways for a simple reason, right? Because the clouds are different. And not just the clouds are different, the cloud providers are different. So we're playing in full respect.  Yeah, you just kind of do the work and integrate in. So you have to expect a slightly degree of integration because of the nature of the cloud, the business and the cloud providers. But I think when you look at from a customer standpoint, what they want and what they're asking Cisco to do, they want to have commonalities, right? They want to have the same mean of networking, the same mean of securing these environments. They want to have the same way of extracting analytics, especially for application performance. And they want to have a common mean of managing and orchestrating all of these resources. Because the alternative is fundamentally getting lost into different tools and different clouds that by design cannot work in other environments. And so that's what customers want. And that's what we're pursuing as a company. Fai, talk about the announcement in terms of just summarizing it real quick. You talked to a lot of customers, we've been doing press tours all day today, analysts, financial wall street, all the whole nine yards. Now you're in the queue. What's the summary? What's the big walk away? Looking back now after the announcement, talk about the impact. What is this about? What is actually happening in your mind? How are people reacting to it? How big will this be? You know, I have two things in mind when I, I gave myself that kind of question, right? The first one is I have this concept in my mind of making Kubernetes is the engine of your innovation, right? This is about really transforming this new container orchestration technology that sounded esoteric until literally a few months ago into the cornerstone of the innovation, right? We've been talking about hybrid for a long while, but we believe that is about mostly taking the best of the public cloud and making it work on-prem rather than going the other way around. That's for sure. And I would say in general is this is a big first step into closing that gap between the infrastructure and the applications, which is kind of by definition closing the public cloud, but when it comes to the on-prem world was still pretty far away, right? And so clearly there's a lot of competition in the marketplace and we want to win that battle to close this gap. And closing that gap means fundamentally enabling customers to innovate and developing their new digital experience faster. And that's actually the nature of their business. It's not an IT conversation anymore. It's a business. And the value extraction and creation from new applications. I think I got to give credit to the Kubernetes community because what's great about Kubernetes and watching that evolve, we were there at the CUBE president at creation when it started hanging around OpenStack and all the different activities around Linux foundation before it went there, was that you had containers obviously happening, but the industry got behind kind of a de facto standard. We've seen this before. TCPIP sounds like one of those things that just became a de facto standard and then it became a standard. Another example with Linux itself, right? I mean, once big companies started going behind it and offering enterprise class support, we saw a really very, very rapid ramp up. I think we're seeing the same with Kubernetes. I think now there are a bit less doubts about where the world is going. This is clearly a winner and people I think are now. And it's clear you guys are getting behind it. This Amazon doesn't do deals like I said, unless it's a serious thing. So congratulations to you guys getting behind Kubernetes. Congratulations. Yeah, thank you for that. All right, Fabio Gori here inside the studio with Cisco breaking down the hot news, game-changing news. Cisco's partnering with AWS with Kubernetes to really bring a level of industry standard and seamless integration between on-premises and the cloud. And I'm excited to keep bringing in more action coming up going to be at the CNCF event, KubeCon. Check us out there and also Amazon re-invent. People have multiple sets there. I'm John Furrier here in Palo Alto for this KubeCon conversation. Thanks for watching.


So it's it's really nice to be here without actually having to wake up at 4 am in the morning to do a hotfix release So I'm actually I I can follow my own thought pattern So today I actually want to talk to you about some constructive things after yesterday's negative things. So For this my talk will be a bit technical, but give basically given its very nature But I'm really hoping that you will see the simplicity despite the technicalities So first up a little perspective of of go ethereum and ethereum in general Basically as you probably know go ethereum c++ ethereum and Python ethereum were one of the three origin clients What this meant is that the clients kind of were already existing before the protocols evolved this meant that the client So the protocols that the peer-to-peer protocols the consensus protocols were all all specified based on the Experiences learned from the clients and what this meant is that the clients were kind of evolved like a startup Just hack together code hack together some other code delete some code. So the code quality was really really bad Now on top of this when me when ethereum was born then There weren't any other tools. So now we have quite a lot of tools in the ecosystem But with the birth of these three clients the clients were required to do absolutely everything that That's a developer would need and even further since we wanted to make ethereum to be useful as much as possible for everyday developers The idea was that we are going to provide the JavaScript environment because more or less everybody is familiar with JavaScript and because of this The problem became apparent that if you wanted to use go ethereum or the geth code base or any other code base as a Library from your own project not from a JavaScript app. It was extremely extremely hard and the reason was that The fast prototyping accumulated an extreme amount of technical depth the networking since Geth was kind of the network had the network majority in the protocol I mean had the network majority It was really hard to drop features and every time you try to drop something somebody was using it in hidden The end was really really angry at us and furthermore browsers since we kind of targeted browser based apps first it was The emphasis was always placed on JavaScript and it was really hard to somehow use it outside of this pre Predefined JavaScript environment. So this was kind of our world until now and if we fast forward to the present one of the our main features as So Joel already mentioned that we have light clients warm and other stuff But one of our main features for the geth 1.5 release is kind of a brand new Brand new code API so that actually any developer can use either go ethereum s full or pieces any Little tiny piece that they want in their own projects without actually having to use a command line interface And why are these good? Well, for example, we try to take a look from from different pain points Person from the perspective of different pain points One of them was that people don't really want to share they their private keys with the node Especially if you are running multiple depths against the same node Why do you want to place the key in the node? Keep the key yourself? It's much safer that way or the other thing that the RPC spec or joe is Jason RPC It has these fancy hex encoding for quantities and other stuff that are really non trivial So to get them right, it's not such an easy thing and although every developer will probably be able to do it It's just a pain to do it yourselves now If you actually want to interact with any theorem contract Ethereum has its own a bi the way to encode and decode function calls and parameters and that is very very complicated So yes, it can be done but it takes a ton of time and possibly you don't really want to waste that time you want to spend time developing your depth not Implementing some protocol and last but not least there are certain cases where it's really natural that you don't want an external node You want to be able to run your own node For example, if you have a mobile app then it's kind of sounds weird that okay to use my app Please download this app this app and this app so user will just say no, that's not go there and these were the pain points that we really tried to address in get 1.5 and So let's dig Dive deep into the technicalities So first of all can client-side account management be done in a simple way and our answer was that yes, of course it can be done and the following code that you kind of see on the screen are four method calls and full Account lifecycle management you can do fully client-side in your own code without actually having to run get parity or any other Client you can basically create a new account you can export that account into a JSON you can take it wherever you want you can import it back up and Yes, you can of course delete it and all of this is done client-side without any backing theorem node and that's actually the whole Program that's I just running there. So everything is full program Nothing else is outside of it and this is basically how we cleaned up the account management so you can take the account manager you can take your accounts ethereum and take it everywhere you want and You don't have to leave it inside geth or any other node. You can just do it yourself Okay, now what happens you can manage your own accounts, but another thing that you really want to do is Okay, without with only with accounts you can do much. You need a node to actually Interact with so the other the second part that we spent quite a lot of time is to cleaning up the remote API's and For this we also provided Really nice library. It's called the ETH client that can actually dial into any any ethereum Client either via IPC socket HTTP web socket Basically, it's a full-fledged ethereum client and Furthermore, it's not just a simple RPC client that you need to manually specify all the JSON RPC details rather It's actually all the all the officially spec the methods are available So you can for example query the current block So this basically this nil here is just saying that I want the current block and not the not any random block I Can I can for example also query the state? So previously that was querying the blockchain. I can query the state tries This is just querying how much funds the currently the ethereum tip jar has the foundation tip jar and One more thing that's I'm not sure whether it's what is in producing 1.4 or 1.5 But we actually do have Subscriptions so one of the problems with mist during the DAO crowdfunding phase But it was hammering the underlying node with tens of thousands of requests per second RPC requests And the node was basically dying because it couldn't serve those requests and the single problem was that the nodes didn't subscribe didn't Support push notifications and that's also something that we kind of fixed So now you can just you have a your ethereum clients can simply call subscribe to new head events And whenever a new block is mined it will be immediately Sent to you and you don't have to do polling at all anymore And of course if we run that again, that's all the code It will tell me that my chain height is at currently at 22 million or 2 million something It told me that the tip jar has about 3800 ethers and as you can see My laptop is actually connected to the main that now and as the blocks are being mined on the main That it is immediately pushing it to me and again the code is just the three function calls that you see on the screen full source code you can see it on the screen So basically you can do chain exploration and state querying and everything via a few API calls a Few programmatic calls. You don't have to implement anything yourself So okay now if you can have key management and you can interact with the remote node You almost have everything but if you actually want to interact with the contract Then you have a problem and the problem is that Your your code needs to actually implement ethereum ABI the ABI as I said is not trivial The basics are kind of easy, but there are quite a lot of corner cases For example, if you try to serialize or deserialize an array of structures in web 3js You will find many corner cases that aren't completely Properly handled and these many times people usually just say on the internet. Well, just use in well Yeah, but if solidity supports all these other types why not use them and Implementing them is kind of a nitty gritty detail. They are quite a lot of details So it would be really nice if we could have a library that does this automatically for us Then of course if I want to interact with a contract It would be nice if the library could also cover all the remote client API stuff So I don't have to care about RPC at all and that's what not least if you are so if I have an already existing contract And I just want to interface with it. Okay, then cool I can just create some codes to access a few methods and I'm done But what happens if I'm actually developing that contract if I if I'm developing it that often I'm just changing some solidity lines and the lines I change I want them to immediately reflect in my code And this is a really nasty part that I changed solidity Then I need to have to change my own code and then I need to make sure that none of my tests broke and it's it's really really an Long procedure and it's when you want to update solidity 10 times per minute. It doesn't really work out So our solution to this problem was who created a begin basically It's a native binding generator and what it does is that you can simply specify a solidity contract And it will generate you full go source code and you can just plug that to go source code into any project And you will have a minute the access to all the contract calls all the transactions all everything natively and you don't have to care about any of the encoding or any of the The RPC calls and the really nice part about that is that if you rewrite your solidity contract then immediately it gets recompiled I mean the go code gets regenerated and if there's it's type checked It's compile time type check you go. That's you don't don't get surprises During actual deployment of whoops something didn't work out So how does for example this look well if The but the top part you can see a solidity contract basically it's a snippet from our release contract the geth release Oracle what it is that's For every release we kind of bump a version number on the blockchain and then every time a geth note starts up it just checks the this version on the blockchain and if a newer version appeared and it just prints out a warning to the user that hello, please update and Well, it does a bit of maintenance in the background But essentially this single function is what is fetching the current version and if you run through this run this code through Abigail then it will give out about 400 lines of go code that we didn't have to write ourself of course for the other functions to in totaling up to 400 lines and But it does get give us a really nice API. It says they're basically I have a new Release Oracle method that I can just point it to a contract. I can tell it how it can reach an ethereum Client that might be over HTTP web socket or IPC or actually an in-process client And then I can just call that I want to get the current version and it will just if I run this Then you will see one of the nasty parts of One of our lazy sides is that we actually never updated the version for the yesterday's hotfix release So oops, sorry about that. So the blockchain didn't wasn't updated to the latest release, but basically I Could simply call a same single command line function single command line utility and then I can immediately work with my contract I don't have to write any boilerplate code myself and Then last but not least one of the interesting things that you can also do is Often Many so usually in this ecosystem. There has been a relatively little Request to run in process nodes, but there are quite a lot of cases where it's genuine You may genuinely do need to run in in process node For example, if I'm developing application, which isn't ethereum centered rather ethereum is just a utility in it Then I would like to distribute my application to clients or to any other people without asking them to first sync up an 80 gigabyte blockchain Or just selling telling them to please download another app whether that's one client or the other. It doesn't matter I just want to distribute my app. Here is a single binary. You can run it and it just works and and for that we cleaned up our API so that API wise in the go client. You can just create an empty peer-to-peer node It's just a deaf peer-to-peer implementation You can attach any protocol whether that's an official protocol to it or whether your own custom protocols We are free to implement your own protocols up top of the peer-to-peer and then I it's just a way to register that I wanted want to run the ETH service on top of that protocol. I just start up the stack and I can attach you so again just for function calls for setting up an entire ethereum node And if I run that now it is actually compiling building the full ethereum suit which takes about I know 10 seconds maybe a bit More with my power plug on my power cable unplug. So yes, that's another thing about go another nice thing that was the full compilation of go ethereum and Yep, I just started up it started it up in a new new empty data directory and Just create some basic information about it and as you can see This again as I emphasized with the previous releases with the previous slides again This is the full source code So there's no other boilerplate that you actually need to write yourself You can have a full in-process embedded node in three lines of code or four lines of code of course I left out the arrow checking so Do keep that in mind Okay, so if we have this all these awesome libraries available Let's try to put a twist on them What would it take maybe to allow supporting them on mobile platforms Well to tell you the truth mobile building to Mobile platform was kind of already supported in 1.3 about last year in September. I did the first Cross compilation to Android it looked horrible. It performed horrible, but it actually worked So I was really surprised it did we did have to fix up a few things in our code base But we could actually start up an Android debugger just copy a binary a CLI binary to the end to an Android device And just run it and it was running it was really an amazing feeling of course it was completely useless because you don't really run your Android programs by copying over a CLI binary and Requiring actually a terminal to run it So during the winter break Christmas time We started to play around with actually providing a library so that users can more easily interface Go with theorem in mobile apps and Well if we did provide Android archives and we did provide iOS frameworks But if we did provide all of these things Why aren't they any if they are mobile apps or any popular ones? Well, the kind of the answer is that that was our full API in the bottom line So that was everything that we supported. So basically we created the wrapper around the CLI interface Which is a horrible horrible idea But since we didn't have light client and it wasn't even on the horizon It didn't really make sense to put more effort into a mobile wrapper since nobody's going to use it anyway So it was rather a proof of concept that people can start playing around with it Wasn't ever meant to be something to be released. However, of course with the 1.5 arriving We want to change all this. So let's see how complicated will it be to actually run Geth as a library or parts of geth inside mobile devices And while it turns out that we have exactly the same API that we had available in go We have that available in Android We have the account manager life cycle management. It's exactly the same function calls If if somebody's a Java guru, you will immediately say that ooh that geth dot new is ugly You should have only used new. Yes, we know that is a limitation bit of the go Java bridge That will be fixed, but please bear with us until it is fixed So basically this was the Apart from a small Android boilerplate this was the full code to actually do account management inside an Android application and that's basically the screenshot from The application running in the simulator. So we have the same functions. We can add new accounts. We can export import We can delete them. So everything you would like to do with an account. You can do it Now, okay, you might say that account. Okay account management is pretty easy You can do it with any fairly nice Java library. Why what's the big deal? Well, let's go to remote API's Well, it turns out that with remote API's we can do exactly the same thing like with go ethereum We can create a new ethereum client which can attach to almost everything HTTP web socket IPC interface the same way as As the native go client could attach to it and it supports all the same functions plus it also supports subscriptions Now getting all of this working is a bit more involved since you also have to implement the RPC interface And you also have to implement subscriptions which aren't exactly that trivial to do already So push notifications client side handling them. It gets a tad messy, but we all you basically you get that for free Okay, so we got Contract, I mean we got the account management and remote API's. Let's see. Can we interact with the contract and The answer is sure So actually we extended a begin to be able to generate Java bindings to contracts So the same way you had a solidly contract and you could create a go wrapper You have a solidly contract and you can create a Java wrapper around it So basically it just spits out the Java file. You just included the Android project and bam you can create a Contract object and you can immediately call functions on them No, basically, that's all that it takes to query the guest version number from from a mobile platform and Of course last but not least if you are running an Android app Then this is particularly the case where you don't want to depend on an external app you want to run an in-process node and Yes, of course, we do can run an in-process node where we can just similarly create a new node if The API here is a bit simplified because it wasn't really a point to expose the entire go API to creating nodes. It's It kind of it was more Ethereum specific. This might change a bit in the future But in essence we can create a node really simply you can just specify a data directory and voila It's running which can just start it up and that's all we can start it stop it Interface with it attention Ethereum client with get all the data We want interact with contracts everything we can do with two lines of code essentially so That was the mobile platforms. Okay, you might ask what about iOS? Yeah, sure. It works So the same thing you I don't expect you to read the code. I just pasted it if you look at the slides offline But everything works really nicely so just to Cover the sum the whole thing up Basically go Ethereum or go actually supports deploying on a variety of different platforms Linux Windows OS X Free BSD on the All the platform or the architectures that actually matter and go Ethereum will provide Pre-bundled libraries for Android and iOS for basically all the architectures that actually matter as for Windows phone Oh, sorry, maybe in the distant future There's not really an interest to port it and If you are actually somebody is interested in trying out either the Android or the iOS libraries You are free to download them. Thank you very much


YouTube is demonetizing videos for comments. Nothing else, just bad comments beneath your videos. You might wonder Why do other people's comments affect my ability to make money if my videos are fine? One answer Advertiser boycott apparently Disney, Epic Games and AT&T all stopped advertising on YouTube Recently due to the discovery of some bad pedophilic comments the video giant YouTube said that within the first 48 hours of the scandal breaking it had Disabled comments on tens of thousands or millions of videos Terminated over 400 channels and report legal activity to law enforcement Were you hit by this?  You can all do that through the Creator studio in your YouTube dashboard So this article is a tube filter article. The link is down there in the description below if you want to read it It talks about how after child video scandal YouTube says ad-friendly videos Can be demonetized for inappropriate comments only comments nothing to do with the video itself the video is fine It's just the comments beneath it. So let me point out the highlights Ballinger with 1.2 million subscribers Said she had many of her videos demonetized by YouTube because of comments But she does monitor her comments Stringently and suggested that rather than punishing channels like hers YouTube remove the offending comments and ban the users themselves Of course if YouTube feels these are bad comments Why don't they remove them and ban those users instead of relying us on us humans to do it for them? According to YouTube millions of videos have been partially demonetized with the yellow icon and that YouTube is also Asking creators to more astutely moderate their comments Because quote we can hold Monetizing channel owners to a higher standard YouTube wrote this was part of another article from The Verge Which you can also read by clicking the link down there to this article and then clicking this link So what do you guys think of all this should YouTube just remove comments themselves and not punish the channel owner or Should YouTube hold channels that monetize to a higher standard so that they have to do Part of the job of monitoring comments themselves. Tell me down there in the comments below Personally, I think YouTube is correct that channels that are making money on the platform should do more To moderate their videos not just their own videos, but the comments I think there is a balance YouTube of course needs to do its part and channel owners need to do their part I know a channel that becomes very popular may get tens of thousands of comments So you might say well, it's unreasonable to expect a channel owner to hire people to moderate tens of thousands of comments I agree, but just look at the popular ones Maybe focus on the comments that have lots of likes or the ones that get Displayed at the top of the comment list when you're looking at the video that would be my Counter like don't look at all 10,000 comments. Just the top ones again I'd love to hear what you guys think tell me in the comments below And I also want to talk about yesterday's video where I said Hiring recruiters to freedom many of you contacted me on LinkedIn more than I expected So we'll have to create a better process I can give each of you a meaningful reply. Sorry if I haven't replied to you yet in LinkedIn. I Have hired three recruiters. I think four actually and we have a team lead so I'm going to in a new video explain a different process to Let everybody who wants to become a recruiter apply and go through a Interview where we see if this is a good fit for you and for us But I will continue replying to the LinkedIn messages So keep sending them to me and I'll introduce you to our new team lead his name is Matt Hamed and He will also help talk with you to see if this is a good fit. So recruiting is a lifeblood of an MCN It's about having people talk to channel owners to spread the love spread the message of why partner with freedom And I'm so happy that so many of you think this is a good opportunity. That's awesome big freedom family hugs and I'll do my best to get back to each of you and know that we would love to create a large team of recruiters Properly structured under team leads in different territories and communicating with each other So we all help each other grow together as a family. Does that ring a bell? That's our mission or not a mission. That's our that's the spirit of freedom But bear with us. We're just getting started with all this recruiting team building And if you think you can also be a team lead send me a message on LinkedIn I'd love to speak with you about how we can organize Teams of recruiters and of course we're looking for people with experience in that type of position Maybe you've already been a team lead for another MCN Or you've just had many years of experience on YouTube as a recruiter or a channel owner That's worked with many youtubers all those things count when We're looking for the right people to be our leaders to be our leadership team in building these Recruiting teams. I also need to give a big shout out to this guy behind me Mark Hider He created a long video called join freedom today. It only got 43 views So click that eye up there to watch this video and let's get him to at least a hundred views and Leave a comment. I wrote my comment. This is such an awesome video about freedom Thank you so much for making it mark. You are my favorite brony Because in this video he featured me and gave a short Introduction to the best parts of freedom according to mark And he talked about our payments. He talked about our music factory He talked about our 3d sets which are right here and he talked about Just everything that I felt were was really cool about freedom So mark, thank you so much for this video If you've made a video like this send it to me or send a link down there in the comments below I would love to spotlight and feature any video that says great things about freedom And even if they're not so great, I'd love to see that video too because we always want to improve We always want to hear your feedback on what's good and bad about freedom so we can make the bad go away What is our mission? Roll it We want to help you build your career in this digital world We want you to go full time doing what you love Which I think is youtube and not your current job, which is paying the bills We want youtube to pay your bills That's why we want you to become a recruiter for freedom because we can Pay you for finding great channels from freedoms cut as a recruiter You take nothing away from the channel They make the same amount of money whether they join freedom directly or not through you as a recruiter The difference is we pay you from our cut as our way of saying thank you for spreading the love And tell channels about tips like demonetized for comments Click that i to see the playlist of all the videos that I talk about in this kyc series know your channel Where I talk about how thumbnails can get you ypp suspended how music can get you ypp suspended All the ways that you can keep your channel safe is in that playlist. I hope this helps And I made a promise to make 15 videos Here they are so far click that i to see this playlist of my promise to make 15 videos where the latest videos are always at the bottom and When I finish this promise I will make another promise This is something you should do for your channel Make a promise to your viewers and keep it it could be something like I promise to create three videos in the next three days Or I promise to do a live stream with you my subscribers on sunday It's an important part of building credibility with your audience. Are there any other promises you think I should make or Anything I should do Tell me down there in the comments below. I'd love to hear your suggestions and feedback on what you think George should do So who am I I am George Sunpai Papa George and many other names you the beautiful freedom family has given me like obi-wan George nobi I illuminark I am the ceo and founder of little freedom today freedom For freedom and the freedom family where we all help each other grow together as a family That is the spirit of freedom that will always be the spirit of freedom And we are going to keep growing towards an IPO That's our final goal as a company We don't want to get bought by another company like every other mcn has been bought We want to continue building freedom towards an IPO so that we continue Growing without someone else telling us what to do when another company buys you the new owners are the bosses And we don't like that idea We think we have a pretty good thing going and we want to keep that thing going Without someone else telling us what to do differently And so an IPO is what lets us do that the main difference between an IPO and an acquisition is the management team stays the same So when you do an IPO, you get a big chunk of cash if you're successful as an injection And if you uh get an acquisition you get the same big chunk of cash But typically the management team is replaced by the guys that bought you doesn't happen in IPO Would you like to know more about My hope of our IPO would you like to know more about Uh, how close we are towards our IPO goals I'd love to share more if you're interested. Just tell me down there in the comments below If you are and if enough people are i'll make a few videos Dedicated to that to explain the concept and uh, how close we are towards our goal Until then freedom family Oh the music you're listening to it's a soundtrack that was custom built by music factory Uh for all of you It's 100 safe to use music because freedom owns it outright And we have over 200 tracks that you can use safely in all your videos and live streams Even if you're not a freedom partner, we recently made the decision To open up music factory to everybody Everyone can use it you will not get any content ID claims or copyright strikes even if you're not with freedom This is a new uh Direction for music factory in the past we treated it like other music libraries where you would could use it for free While you're partnered with freedom And then if you leave freedom then new videos you upload may get a content ID claim no more Everything in music factory is 100 free even if you leave freedom or if you've never joined freedom Click that i to see the music factory Videos and chat the channel we have and then you can go to the music factory website at www.musicfactory.tm To download all that music and use it anywhere you like We also create custom music as a sonic branding benefit for freedom partners And if you want to know about all the other benefits Here they are in my letter from the CEO of freedom Right talk about all the things that you that freedom does That either youtube doesn't do or other mcn's don't do We think and you can click uh the link down there in the description below to read this google doc If you'd like to know more and here's the sonic branding piece. I just mentioned Oh, and I'll just scroll down so you can see the other things custom games crypto minor tax reduction and 3d virtual sets professional music community the Uh refer a friend 15 percent that we pay you from freedoms cut. I mentioned earlier in this episode Until the next episode. I am george and you've been watching Click that i to partner with freedom and join the freedom family so we can all grow together You get many perks like position music. You also get epidemic sound a lot of other access to royalty free videos Sponsorships and many things to help you grow Just click the links down there in the description below to get involved in our community our forums our discord chat servers Meet our graphics team meet our community team all of that on discord and the forums What are you waiting for get started and we will grow together as a family? Because this is the freedom family You are part of it. We are all part of it and we're all growing together To get more george click that big f that will subscribe you to freedom Central home of the george show and pewdiepie gave one of you freedom family a big shout out click That video to see the shout out and to see our new 3d sets for you And click that video to see what youtube recommends you watch next


What is going on, mobile creators, and welcome back to another exciting video. Today I'm gonna show you how to create a cinematic travel vlog with your iPhone. Now, if you're someone who likes to travel a lot and capture those moments, then having a simple setup like I'm having right now with the iPhone 13 Pro Max just allows you to capture moments more easily without the hassle of having to carry a heavy camera back with you. It just takes up a lot of energy and you can't really enjoy the moment. While I'm doing this travel vlog with you guys, I thought about giving you some useful tips on how you can create your own cinematic vlog for yourself that you can apply. If you know how to use your camera's full potential, you can create some great looking results with it. So with that said, welcome to Croatia. What's going on, mobile creators? Ben at Grazer here with smartphonefilmmaking.com, the best online course where I teach you everything I know on how to produce professional and cinematic videos with your smartphone. And like I mentioned before, I'm here in Croatia with my girlfriend. We're actually doing a road trip, visiting different cities, and so far it has been really great. And I thought I would share my journey with you guys and show you how I create those cinematic travel vlogs. And it really doesn't have to be difficult. Most smartphones nowadays can produce high quality video with the right know-how and practice. You can get great results out of your smartphone. So the first tip I have for you guys when it comes to creating your travel vlogs is to avoid overpacking. The less gear you have with you, the more enjoyable your trip will be and the more creative you can be when it comes to creating your shots. The only thing I bring with me is really this sling bag over here that I pack all of my gear in it. And currently I'm using the iPhone 13 Pro Max with the Rode Video Micro and a Gorilla Pod.  It doesn't necessarily mean you can't create the shot. Try to think outside of the box on how you can create that shot. By the way, if you're interested in the gear I'm using, I will mention them in the video description below. So if you're wondering where I am currently, I'm at some kind of abandoned place here in Croatia. And what fascinates me about those abandoned places is that it's super scary, man. It freaks me out. Look at this. There's nobody here. It's creepy, but I love it. So we are currently in Zadar. It's a beautiful place. We just had some delicious ice cream. And the next tip I have for you guys is to be strategic with your shots. A lot of beginner mobile creators tend to just shoot everything they see. Really focus on a couple of shots and try to make those shots look as interesting as possible. This way you won't be overwhelmed in the edit having to search through thousands of clips and will make the editing process much easier. So my advice to you is to shoot more than necessary but be strategic about it, especially when you're traveling with friends. It's just more enjoyable if you take out your phone when necessary to capture those shots.  So just keep that in mind. So as for my fourth tip is to go with the flow like seen over here. You don't want to head back to a particular place again just to record a couple of additional clips because you think that the shots you've took aren't good enough. Rather enjoy yourself and record just those moments that you can capture because as mobile creators we get stressed out, especially when we're starting out to just capture as much as possible. And always thinking that our videos is not good enough. Your video doesn't have to be perfect. Probably know the saying better done than perfect. Just start making your videos, do mistakes and then learn from them as you keep developing your skills. It's gotten super hot. I think I'm gonna go to the other side and find some shade. So whenever I can, I always try to add a V-roll to my video to keep the viewers attention and to make the video just more interesting in general. Especially when doing travel vlogs, you don't only want to have a role in your video which is usually the talking head part like you're seeing right now. You want to support your story by having additional footage to help the viewers visualize what you're talking about. And it's always a good idea to think about what you said in your A-roll so that you can capture those clips needed to tell a better story. Now, when it comes to capturing V-roll I use the rear camera and record everything in 4K 60 frames per second. And whenever I do my A-roll I use the selfie camera and record everything in 4K 25 frames per second as I don't plan on slowing down the footage. And the reason why I like to use the selfie camera is because I can live monitor myself and see what I'm recording. So speaking of B-roll, my next tip is to shoot your B-roll in 60 frames per second. Especially if you're someone who shoots without a gimbal and goes handheld 60 frames per second really helps stabilize your footage. Being able to shoot in 60 frames per second and slowing it down allows us to focus our attention on a specific detail like a bird flapping their wings. And you don't only have to shoot in 60 frames per second you can even go up to 120 or 240 frames per second now with the iPhone 13 Pro Max but you are limited with 1080p but you can create a much more dramatic effect in your video. So depending what you're shooting you can really take advantage of the higher frame rate and use it more creatively. Ow, look at this view. So this is our last day here in Croatia. We're at the capital city, which is Zagreb. And the last tip I have for you guys when it comes to creating your travel vlogs is to simply add some speed ramp to your video. Not only does it look cool but it also helps connect two clips together. And the way how a speed ramp works is you actually slow down the footage first and then speed it up and then slow it back down again. And what I usually do is in Final Cut Pro I use the automatic speed that slows it down and then somewhere at the end I then speed it up and then do the same thing at the beginning of the second clip where I speed up the clip as well and then gradually slow it down to create a speed ramp. Now if you're serious about producing high quality videos with your smartphone, make sure to check out smartphonefilmmaking.com where I show you everything I know on how to produce cinematic and professional looking videos with your smartphone. Also make sure to download my free smartphone filmmaking guide which will help you get started making quality videos on your phone. So with that said, I'm gonna enjoy the rest of the day here in Zagreb. Thank you so much guys for watching. I appreciate all of you and take care.


From our studios in the heart of Silicon Valley, Palo Alto, California, this is a CUBE Conversation. Hi, I'm Peter Burris, analyst at Wikibon. Welcome to another Wikibon the CUBE digital community event. This one's sponsored by HP and focusing on hybrid storage. Like all of our digital community events, this one will feature about 25 minutes of video followed by a crowd chat, which will be your opportunity to ask your questions, share your experiences, and push forward the community's thinking on the important issues facing business today. So what are we talking about today? Again, hybrid storage. Let's get going. So what is hybrid storage? In a lot of shops, most people have associated the cloud with public cloud. But as we gain experience with the challenges associated with transforming to digital business, in which we use data as a singular value producing asset, increasingly IT professionals are starting to realize this important relationship between data, storage, and cloud services. And in many respects, that's really what we're trying to master today is a better understanding of how the business is going to use data to affect significant changes in how it behaves in a marketplace. And it's that question of behavior, that question of action, that question of location that is pushing business to think differently about how its cloud architectures are going to work. We're going to keep data proximate to where it's created, to where it's going to be used, to where it's going to be able to generate value, which demands that we have storage resources in place close to that data, proximate to that activity, near that value producing activity, and that the cloud services will have to follow. In many respects, that's what we're talking about when we talk about hybrid cloud today. We're talking about the increasing recognition that we're going to move cloud services to the data as the default and not move the data into the cloud, the public cloud specifically. So it's this ongoing understanding as we gain experience with this powerful set of technologies, that data architecture is going to be increasingly distributed, that storage therefore will be increasingly distributed, and that cloud services will flow to where the data is required, utilizing storage technologies that can best serve that set of workload. So it's a more complex world that demands new levels of simplicity, ease of use, and optimization. So that's where we're going to start our conversation. So these crucial questions of how data, storage, and cloud are going to come together to create hybrid architectures was the basis for a great cube conversation between SiliconANGLE Wikibon's David Volante and HPE's Sundip Aurora. Let's hear what they had to say. Talk about, let's talk about the breakdown of those three things, cost efficiency, ease of use, and resource optimization. Let's start with cost efficiency. So obviously there's TCO. There's also the way in which I consume. The people I presume are looking for a different pricing model. Is that, are you hearing that? Yeah, absolutely. So as part of the cost of running their business and being able to operate like a cloud, everybody's looking at a variety of different procurement and utilization models. One of the ways HPE provides utilization model that can map to their cloud journey, a public cloud journey, is through GreenLake. The ability to use and consume data on demand, consume compute on demand, across the entire portfolio of products HPE has, essentially is what a GreenLake journey looks like. And let's go into ease of use. So what do you mean by that? I mean people, they think cloud, they think swipe the credit card and start deploying machines. What do you mean by ease of use? For us, ease of use translates back to how do you map to a simpler operating and support model? For us, the support model is the key for customers to be able to realize the benefits of going to the cloud. To get to a simpler support model, we use AIOps. And for us, AIOps means using a product called InfoSight. InfoSight is a product that uses deep learning and machine learning algorithms to look at a wide net of call home data from physical resources out there, and then be able to take that data and make it actionable. And the action behind that is predictiveness, the prescriptiveness of creating automated support tickets and closing automated support tickets without anybody ever having to pick up a phone and call IT support. That InfoSight model now is being expanded across the board to all HPE products. It started with Nimble. Now, InfoSight is available on three parts. It's available on Synergy. And a recent announcement said it's also available on ProLiance. And we expect that InfoSight becomes the glue, the automation AI glue that goes across the entire portfolio of HPE products. So this is a great example of applying AI to data. So it's like call home taking to a whole new level, isn't it? Yeah, it absolutely is. And in fact, what it does is it uses the call home data that we've had for a long time with products like 3-par, which essentially was amazing data, but not being actioned on in an automated fashion. It takes that data and now it creates an automation task around it. And many times that automation task leads to a much simpler support experience. All right, the third item you mentioned was resource optimization. Let's drill down into that. I infer from that there are performance implications. There's maybe governance, compliance, physical placement, can you elaborate? That's in color. Yeah, so I think it's all of the above that he just talked about. It's definitely about applying the right performance level to the right set of applications. We call this application aware storage. The ability to be able to understand which application is creating the data allows us to understand how that data needs to be accessed, which in turn means we know where it needs to reside. One of the things that HPE is doing in the storage domain is creating a common storage fabric with the cloud. We call that the fabric for the cloud. The idea there is that we have a single layer between the on-premises and off-premises resources that allows us to move data as needed depending on the application needs and depending on the user needs. So this crucial new factors that have to be incorporated into everyone's thinking of cost efficiency, ease of use and resource optimization is gonna place new types of stress on the storage hierarchy. It's gonna require new technologies to better support digital transformation. David Floyer, an analyst here at Wikibon, has been a leading thinker of the relationship between the storage hierarchy and workloads and digital thinking for quite some time. I had a great conversation with David not too long ago. Let's hear what he had to say about this new storage hierarchy and the new technologies that are gonna make possible these changes. David, you've been looking at this notion of modern storage architectures for 10 years now and you've been relatively prescient in understanding what's gonna happen. You were one of the first guys to predict well in advance of everybody else that the crossover between Flash and HDD was gonna happen sooner rather than later.  What do you see as a modern storage architecture? Let's just let it rip. Okay, well let's start with one simple observation. The days of standalone systems for data have gone. We're in a software-defined world and you want to be able to run those data architectures anywhere where the data is. And that means in your data center where you've just created or in the cloud or in a public cloud or at the edge. You want to be able to be flexible enough to be able to do all of the data services where the best place is and that means everything has to be software-driven. Software-defined is the first proposition of a modern data storage architecture. Absolutely. Second. So the second thing is that there are different types of technology. You have the very fastest storage which is in the DRAM itself. You have NV-DIM, which is the next one down from that. Expensive but a lot cheaper than the DIM. And then you have different sorts of flash. You have the high-performance flash and you have the 3D flash, you know, as many layers as you can, which is much cheaper flash. And then at the bottom you have HDDs and even tape. As storage devices. So the key question is, how do you manage that sort of environment? Well, let me stop because it still sounds like we still have a storage hierarchy. Absolutely. And it still sounds like that hierarchy is defined largely in terms of access speeds and price points. Price points, yes. Those are the two Mason. And bandwidth and latency as well within that. Which are tied into those. Which are tied into those, yes. So what you, if you're going to have this everywhere and you need services everywhere, what you have to have is an architecture which takes away all of that complexity. So that you, all you see from an application point of view is data and how it gets there and how it's put away and how it's stored and how it's protected. That's under the covers. So the first thing is you need a virtualization of that data layer. The physical layer. The virtualization of that physical layer, yes. And secondly, you need that physical layer to extend to all the places that may be using this data. You don't want to be constrained to this dataset lives here. You want to be able to say, okay, I want to move this piece of programming to the data as quickly as I can. And that's much, much faster than moving the data to the processing.  I want to understand that architecture and I want to virtualize view of that across that whole, the nodes that make up my hybrid cloud. So let me be clear here. So we are going to use a software defined infrastructure that allows us to place the physical devices that have the right cost performance characteristics where they need to be based on the physical realities of latency, power availability, hardening, et cetera. And the network. And the network, but we want to mask that complexity from the application developer and application administrator. And software defined helps do that but doesn't completely do it. Well, you want services which say... Exactly. So there's services on top of all that that are recognizable by the developer, by the business person, by the administrator as they think about how they use data towards those outcomes, not use a storage or use a device but use the data. To reach application outcomes. That's absolutely right. And that's what I call the data plane, which is a series of services which enable that to happen and driven by the application requirements. So we've looked at this and some of the services include end to end compression, deduplication, backup restore, security, data protection. So that's kind of the services that now the enterprise buyer needs to think about so that those services can be applied by policy wherever they're required based on the utilization of the data where the event takes place. And then you still have, at the bottom of that, you have the different types of devices. You still have... You still want... You want hamsters making stuff. You still want hard disks, for example. They're not disappearing. But if you're going to use hard disks, then you want to use it in the right way for using a hard disk. You want to give it large blocks. You want to have it going sequentially in and out all the time. So the storage administration the physical schema and everything else is still important in all of this. But it's less important, less the centerpiece of the buying decision. Increasingly, it's how well does this stuff support the services that the business is using to achieve their outcomes? And you want to use the lowest cost that you can. And there will be many different options open, more and more options open. But the automation of that is absolutely key. And that automation from a vendor point of view, one of the key things they have to do is to be able to learn from the usage by their customers across as broad a number of customers as they can. Learn what works, what doesn't work. Learn so that they can put automation into their own software, their own software services. So it sounds like we were talking four things. We got software defined, still have a storage hierarchy defined by cost and performance, but with mainly semiconductor stuff. We've got great data services that are relevant to the business and automation that masks the complexity from everything. And a lot of the artificial AI there is automated. Running things, fantastic. So David's thinking on the new storage hierarchy and how it's going to relate to new classes of workload is a baseline for a lot of the changes happening in the industry today. But we still have to turn technology into services that deliver higher levels of value. Once again, let's go back to Dave Vellante's conversation with Sundip Aurora and hear what Sundip has to say about some of the new digital services, some of the new data services that are going to be essential to supporting these new hybrid storage capabilities. We have, and what it does is it gives us opportunity now not just to look at call home data from storage, but then also look at call home data from the compute side. And then what we can do is correlate the data coming back to have better predictability and outcomes on your data center operations as opposed to doing it at the layer of infrastructure. And you also set out a vision of this orchestration layer. Can you talk more about that? Are we talking about across all clouds, whether it's on-prem or at the edge or in the public cloud? Yeah, we are. We're talking about making it as simple as possible where the customers are not necessarily picking and choosing. It allows them to have a strategy that allows them to go across the data center, whether it's a public cloud, building their own private infrastructure or running on a traditional on-premises sand structure. So this vision for us, cloud fabric vision for us, allows for customers to do that. And what about software defined storage? Where does that fit into this whole equation? Yeah, I'm glad you mentioned that because that was the third tenant of what HPE truly brings to our customers. Software defined is something that allows us to maximize the utilization of the existing resources that our customers have. So what we've done is, we've partnered with a great deal of really strong software defined vendors, such as Commvault, Cohesity, Cumulo, Deterra. We work very closely with the likes of Veeam, Zerto. And the goal there is to provide our customers with a whole range of options to drive building a software defined infrastructure built off the Apollo series of products. Apollo servers or storage products for us are extremely dense storage products that allow for both cost and resource optimization. So Sundit made some fantastic points about how new storage technologies are going to be turned into usable services that digital businesses will require as they conceive of their overall hybrid storage approach. Here's an opportunity to hear a little bit more about what HPE thinks about some of these crucial areas. Let's hear what they have to say. In this Chalk Talk Short Take, I'm gonna introduce you to HPE Primera Storage. If you want the agility of the public cloud but need the resiliency and speed of high-end storage for mission-critical applications, this forces a trade-off of agility for resiliency. High-end storage is fast and reliable, but falls short on agility and simplicity. What if you could have it all? What if you could have both agility and resiliency for your mission-critical apps? Introducing the world's most intelligent storage for mission-critical apps, HPE Primera. It delivers an on-demand experience so storage is instantly available. Apple wear resiliency backed with 100% availability guarantee. Predictive acceleration so apps aren't fast some of the time but fast all the time with embedded AI. Let me tell you more about HPE Primera. Who is engineered to drive unique value in high-end storage? There are four areas we focus on. Global intelligence, powered with the most advanced AI for infrastructure, InfoSight, and all-active architecture with multiple nodes for higher resiliency and limitless parallelization. A service-centric OS that eliminates the risk and simplifies management and timeless storage with a new ownership experience that keeps getting better. To learn more, go to hpe.com slash storage slash Primera. So that's been a great series of conversations about hybrid storage and I wanna thank Sundep Arora of HPE, David Floyer of Wikibon Silicon Angle, Jim Cabellus of Wikibon Silicon Angle, and my colleague David Volante for helping out on the interview side. I'm Peter Burris and this has been another Wikibon theCUBE digital community event sponsored by HPE. Now stay tuned for our crowd chat which will be your opportunity to ask your questions, share your experiences, and push forward the community's thinking on hybrid storage. Once again, thank you very much for watching. Let's crowd chat.


Governor Darius Ishakou of Tarabah State has advocated immediate upward review of the current revenue allocation formula. This is to caution the pangs of financial burdens of the states and the local government areas in the country. He made the assertion during a two-day review meeting on revenue allocation formula with the Revenue Mobilization, Allocation and Fiscal Commission in Jalingo, the state capital. Governor Ishakou was represented by his deputy, engineer Haruna Manu. He stated that the upward review of the revenue allocation formula has become imperative because it has been long since the last exercise was carried out during the military rule in 1992. Our correspondent filled in this report. This meeting is on revenue allocation to state in Nigeria. The Revenue Mobilization Allocation and Fiscal Commission is here in Jalingo, Tarabah State to deliberate on the existing sharing formula. Governor Darius Ishakou is of the view that the nation constitution is drafted in a manner the state's government's way should change in terms of solid resource exploration. He's now suggesting a different approach. In the light of this uneven and unequitable revenue sharing formula, I wish to state that the revenue sharing formula is comparable to the second tier sub-government since it cannot keep up with our rising obligations necessitating an immediate review of the formula. The speaker of the state advocates that the current 13 per cent derivation being enjoyed by the oil-producing state should be reduced to 10 per cent. After all, the eight per cent has now been captured in the Petroleum Industry Act signed by President Mamadou Puhari recently. Two states to sensitize their respective governments or governors so that they can come up with their position in the ongoing exercise that will terminate in December that is embarked upon by the Revenue Mobilization Allocation and Fiscal Commission which is even the main plank or one of the main planks of our responsibility as a commission that drives its powers from the constitution in the sense that we are one of the 14 executive commissions that is recognized by the constitution particularly to come up with a revenue allocation sharing formula. I understand that this review meeting is meant to address the obvious challenges inherent in the present revenue sharing formula. Governor Yashaku joined Tarabans particularly the stakeholders to participate fully in the review process by submitting position papers and also engaging in meaningful dialogues will improve fiscal efficiency at the sub-national level. So you get notified about fresh news updates.


What's going on guys? It's your my dpj here today of another destiny video and today we have the five truths of Destiny basically a top five of people do some nasty things with that truth Lock it launcher. Now if you guys do enjoy the video do hit that like button I'd appreciate the support so meet any baddest clip you've got to the email just a link to the top of the video Description and I'll catch you guys on that next one Spark has arrived Enemy has the spark stop them enemy runner approaching the riff Mo available stop the lead Heavy ammo available Last gun in the fight like you I could end war


Bring him back Baltimore Ravens is what we have heard from a lot of the Ravens flock over the past 24 hours in regards to both Mark Ingram and Justin Houston. And before we get into that, make sure you subscribe to the YouTube channel and turn notifications on cause I do not want you to miss not one single update about these Baltimore Ravens or anything else that's going on. And also leave a like on the video too. Click the thumbs up button because it does help out the channel a lot. And hey, who knows? Maybe if you click enough likes then the Ravens will bring one or both of these guys back if that's what you want, of course. Now let's start off with Mark Ingram. Of course, we had Keaton Mitchell. We got the bad news the other day that Keaton Mitchell, he would be out for the remainder of the season. John Harbaugh let us know. And then the following day it was said that Keaton Mitchell, he tore his ACL. So that was officially him being done. And with Keaton Mitchell, I guess the good news amongst all that bad news is that it was a clean tear. There was no additional damage to his cartilage or anything like that. So I mean, we'll take it. We'll take any good news that we can get in regards to Keaton Mitchell injury. But the bottom line is that he suffered an injury and he will not be a part of the Baltimore Ravens for the remainder of this year.  That's a huge blow for the big Baltimore Ravens because Keaton Mitchell, he came on strong. He came on late. But when he started playing, he made a huge, huge impact with the Baltimore Ravens. And in my opinion, like straight up, his impact that he made, I don't think it's replaceable. I don't think you could just pick up somebody or elevate somebody or assign somebody to replace Keaton Mitchell because of what he did and how he did it. You can't just find somebody off the street who can do that. But a lot of Ravens fans have been wondering, should the Baltimore Ravens have a reunion with a running back who brought unmatched energy, an unmatched vibe to the Baltimore Ravens when he was with the Baltimore Ravens that being Mark Ingram. Because we know the inventor, the originator of big trust is none other than who? Yeah, Mark Ingram. And we know just his energy. It's sort of like O'Dell Beckham, Jr., his energy on the Baltimore Ravens this year. That's the same thing that Mark Ingram brought but just at a different position because he was a running back.  He wasn't just here as a hype, man. No, no, no, no. His first year here, he went for over 1,000 yards. He got a 10 touchdown. So Mark Ingram's impact was both on and off the field. So could the Ravens look to get that old thing back? Well, my guy Gamer God 29, who was one of the best Baltimore Ravens follows on Twitter. He tweeted this a couple of days ago. He said, the last dance. And it was a picture of Mark Ingram in a Ravens jersey. So that tweet started popping off but guess who caught wind of that tweet? Mr. Mark Ingram himself. And he tweeted a video and said, hit my line. So is Mark Ingram trying to come back to the crib? Is Mark Ingram trying to come back to the Baltimore Ravens where he had a lot of success his first year? Second year wasn't so pretty, but the second year, that's when the Ravens drafted J.K. Dobbins and J.K. did his thing. And of course, Gus Edwards, he did his thing as well. But should the Ravens make that move for a Mark Ingram? Well, when you think about, again, the vibes, the energy of his personality, oh, it would be great. It would be amazing. And Mark Ingram, somebody that is the third down, back catching passes out of the backfield. He could help him pass protection. But as far as running, I just, I don't feel like the impact would be there like that.  Now with Mark Ingram, he is somebody that you can trust with the football in his hands. But I don't know, man. Like if they brought him back, cool, but I just, cause again, Keith Mitchell, Keith Mitchell, lightning in the bottle, explosive plays, boom, just like that. If they brought Mark Ingram back. And then even with Mark Ingram, we remember his last year with the Baltimore Ravens where he did start getting less opportunities. But in my opinion, he just, he wasn't the same running back that he had been the year prior. And again, now the opportunity they did decrease and not saying that he will come here and get like a boatload of runs or anything like that. But I think if they were to bring Mark Ingram back, it would be more so for what he brought to the Baltimore Ravens culture, what he brought to the locker room. But can you use a roster spot on somebody mainly bringing something to the locker room over them producing? Hey, that's up to you. And now I know a lot of Ravens fans, when they look, they will look at who the Baltimore Ravens are expected to bring up that being Melvin Gordon. And I know a lot of Ravens fans would prefer Mark Ingram over Melvin Gordon. But hey, you never know. Well, I guess it's one of those things that we'll see when we see now. Somebody else who is also a free agent is Justin Houston. Now, Justin Houston, he signed with the Carolina Panthers this off season and it has not been pretty there at all. They had a top pick this year and now they're getting ready to have another top pick. Oh, wait a minute. No, I think they traded it to Chicago. But either way, regardless that the Panthers are a really, really bad football team right now. They are in the dumps, they are in the mud. Everything is going all kinds of bad for the Carolina Panthers. So I'm not sure what Justin Houston, if he requested it, if he asked for it, or if the Panthers just said, you know what?  We'll go ahead and release you. Have it happen, the Panthers are releasing and have released Justin Houston. Now, a lot of Ravens fans are like wondering, hey Ravens, should they bring him back? Should they bring Justin Houston back to the crib? And I even tweeted, I said, oh, Yoda, Yoda must want to come home for this playoff run, huh? Do we have any room on the practice squad? Because when you look at the Baltimore Ravens roster, I mean, it's all filled up right now. Now, Keaton Mitchell, he still has to go to injured reserves. That's going to open up one more roster spot, but you figure that that will go to Melvin Gordon. But if Melvin Gordon goes to the active roster, then that would open up a spot on the actual practice squad for whoever the Baltimore Ravens would choose. And they're going to have their options on how they want to fill that practice squad spot. But should they go after Justin Houston? Now, when you look at the numbers for Justin Houston, it's very weird because looking at his numbers this year, it ain't so pretty. Because Justin Houston, in all the games that have been played this year by the Carolina Panthers, in all the games that he has played this year as a Carolina Panther, he has a whopping half a sack, half a sack, not a whole sack, not two sacks, not three, not four, not a whole sack. A whopping half of one sack. So you look at that and like, whoa, the Baltimore Ravens really want that? Somebody who got a sack and we almost done with the whole season, he got a half a sack. It's not pretty. But then you look the previous year when he was with the Baltimore Ravens and we know that he had got hot for a little bit then he cooled off. And I always say, I feel like he just got tired from being the only guy out there who could really rush to pass like that. But you look at just last year, again, this is a year ago. He got nine more sacks than that. He got nine and a half sacks last year versus this year, just a half a sack. So what is the issue, what is the problem? Even the year prior to that with the Baltimore Ravens, he got four and a half sacks. And see the thing about Justin Houston, when you look at that, his last year was Mike McDonald's first year. Remember that? That was his first year. And we know that Mike McDonald, he improved the past rush of the Baltimore Ravens a lot. Like even now, Ravens, I believe they only got two sacks the other day against the Jaguars. But I know going into that game, they were leading the league in sacks. I'm not sure if they still are. I would assume that they are. But Mike McDonald has turned this past rush around. So we know Mike McDonald has a big impact. So with Justin Houston, is it ability? Is it that he really fell off that much from the Baltimore Ravens to the Carolina Panthers? Or is it about scheme? Is it about the playbook? Is it about the defensive coordinator? I'll let you be the judge of that. So those are two guys that the Baltimore Ravens could possibly maybe will see, but probably not. They could possibly bring those guys back. But then there's one more. There's one more guy that a lot of Ravens fans have been talking about, especially because the Baltimore Ravens have been putting film on tape for him to watch, to be like, hey, come here, please come here. And that is Adamakin's suit. A lot of Ravens fans have been calling for Adamakin's suit, especially over these past two weeks because the Baltimore Ravens have been getting run all over. And it has been, especially in that Rams game, and the Jaguars game has slowed up because the Ravens started pulling off a little bit. But in that Rams game, oh my goodness, it was nasty. So Adamakin's suit, though, he is another possible option for the Baltimore Ravens. Now that is one that I feel like is the most interesting because with Justin Houston, you know the leadership. With Mark Ingram, you know the vial with Adamakin's suit. Ooh, you know the ability on the field, but he ain't played in a while. But then on top of that, you hear all this stuff about him. You wonder all this stuff about him. And apparently, according to somebody who covers the Detroit Lions, apparently Adamakin's suit wanted to go back to the Lions this year, just last week or the week before last. And apparently Adamakin's suit reached out to the Lions. And it was like, hey, I wanna come on. I wanna sign with the team. I wanna be a Detroit Lion again. But apparently they shut it down. They said, no thanks. You are not welcome here. Because apparently, again, this is all alleged and apparent and whatnot, but apparently when he was with the Lions before, he was doing everything that he possibly could to get out of Detroit. And they remember that and they were like, yeah, no, no thanks. You wouldn't be good for a team. You wouldn't be good for our culture. So with Adamakin's suit, I'm not sure what type of teammate he is, but the thing about that is, you hear a lot of stuff about different players around the league, but a lot of times it just takes them being at the right place at the right time with the right team, the right coaching staff and the right culture. Because we had heard a lot of rumors about Jadevan Clowney as well. We had heard a lot of rumors that he was lazy, that he would take plays off, that he wasn't a good teammate. And then you see him with the Baltimore Ravens and you see everything go the exact opposite of what those rumors say. So with Adamakin's suit, initially that was a big concern of mine, how he would fit in, not as a player, but with the culture, with the vibes of the Baltimore Ravens. And maybe he wanted them players like, look, if we went in, I'm cool with whatever. I'm good, I'm straight. So maybe that's what the case is with Sue. And again, back to Justin Houston, maybe the case is with him. Hey, the scheme that the Panthers ran, maybe it wasn't a good fit. Maybe the coaching wasn't a good fit. Cause I just don't see how a player goes from nine and a half sex in a season to half a sec. So we got to take all those things into consideration, but what do you guys think? What do y'all think about possibly bringing Mark Ingram back? What do you think about the possibility of bringing Justin Houston back? Or the possibility of somebody that has never been here before or about the Baltimore Ravens adding Adamakin's suit? I want to hear from you on how y'all feel it.