Hey everyone, welcome back to the Nintendo Prime podcast, and I am your host Nathaniel Ruffaljantz, joined as always by Eric Moore. And this is it. This is the week that we essentially have been waiting for almost since the start of this very podcast. Oh yeah. The switch comes out baby. It comes out. So for our video viewers, just so you know, we're only doing four topics this week because we do not want to release a podcast on Friday. Because anything we talk about isn't really going to matter by Friday, is it? No, not at all.  By then, anything we talk about is going to feel antiquated to me. And that's not anything. Obviously we could say we could talk about retro stuff, but we could come up with something. But let's be honest, we're going to be live streaming like crazy that day, all weekend, doing lots of stuff. So there's going to be so much content coming your way from Friday through the weekend that the podcast is just going to feel irrelevant. Right? Right? Yeah. At least for now. Obviously, listen next week because that's when we'll have a lot of impressions and a lot of stuff. But we are going to do our best to kind of hype things up for the switch because we're hyped. Oh yeah. And that kind of gets to our first topic this week, which is how hyped we are for the switch. So let's just, we've talked in the past about what excites us and everything about it. So some previews have now come out for it, and also for Breath of the Wild, which we'll get into on our next topic. But what I want to know from your end is this is like the first Nintendo console you've probably gotten at launch, maybe ever. Yep. Because I mean, you have a 3DS, but that wasn't at launch. Yeah, no. So we obviously know Breath of the Wild's the number one thing that's sold you. Yep. Number one thing. Well, what about the hardware itself excites you? Hmm. I like the fact that it's a console that you can just get up and go. And what situations do you see yourself using it? Because I've always said it's like nice to say if I go, but we live in Wisconsin, we have to personally drive ourselves everywhere. So it's not like something we're going to use while we're driving. Well, right, right. Well, I know I'll be playing it over my lunch hour at work. I can definitely tell you that. Um, I don't know, just apparently you can go out and go for walks with it. That's going to be nice. I mean, yes, you can do that with like your 3DS and whatnot, but this is like an actual home console. Nice, large screen, great graphics. You know, that's the part that I'm actually looking forward to. Nice. Um, for me, it's kind of a catch-trony to you because I was always going to get the Switch Day one because I do this podcast on a Nintendo site. I'm technically still editor-in-chief at Zelda Informer at the time of launch. The Breath of the Wild is kind of a big deal beyond just my personal hype for it. I feel like as editor-in-chief of a Zelda site, it's kind of important I play the latest Zelda game on the latest hardware, especially since it's 900p in docked mode versus the 720p that's going to be our Wii U. Plus, I assume there's better frame rates. We don't really know better draw distances. We don't really know because we haven't seen any Wii U previews. Every preview has been with the Switch version. Well, I mean, we've technically played the Wii U version. I know. But it is one thing we know about the Wii U version, but I'll bring that up in the next topic. All right. But what we know right now about the Switch in terms of the positives is that it does seamlessly transition from TV to on the go. Yeah. And I know I watched this earlier today. I watched this Teen's React to the Nintendo Switch where they showed off the Switch reveal, a couple Switch commercials, and some of the Teen reactions were like, yeah, it looks very smooth and everything, but there's no way it's that smooth. It is. Previews say it is. You literally dock it and it's on your TV in less than a second. You undock it. It's on your screen in less than a second. It is that smooth. We're not BSing you. And that's impressive because we've had some supposed clock speeds and stuff confirmed by Eurogamer because there was a recent update, one of their developer contacts. There was a recent update to the Switch that made handheld mode get a 25% boost in GPU power. Now, everyone's like, oh, so it's 25% better than dock mode? No, no, no. Because dock mode is supposedly running at 768 MHz and original handheld mode was only running at 300. And now there's an option in handheld mode to run it at 380 something or whatever. It was like a 25% boost. And it's like, that's great. That's cool. And knowing all that, there's a few takeaways from this because like you mentioned, you know, great graphics, home console and portable. I think it's important to frame this conversation when it comes to that kind of talk because it's not as powerful as other home consoles, not even close. And Nintendo's keep home console, home console. Yeah. Because that's what Nintendo, that's what they're pushing in their marketing. But it's important we recognize this thing for what it really is. The most powerful tablet in the market. Oh, yeah. Period. Yeah. Even more powerful than the game shield. And all of a sudden the video it's supposedly even better than that. So it is the most powerful tablet on the market for gaming purposes. And it's a hell of a lot cheaper than all the other powerful tablets out there. Yeah. That run $800, $900,000 at times to get a powerful tablet. Yeah. Obviously, those have the benefit of they're not just for gaming. So you have an app store, you have proper web browsing, you have Netflix at launch, I said like, but that's because those are multi-purpose tablets for gaming specific reasons. This is the best. Oh, yeah. Yeah. I would agree. And, you know, I have a feeling that in the future here, probably not too far off, you're gonna probably have Netflix. You're gonna probably have a decent web browser you're gonna have. And that's the thing.  And it's like, okay, doesn't matter at launch at launch to me, it does not matter. What matters to me, I think the main reason why it doesn't matter to me right now is because I'm gonna be so involved with Breath of the Wild that it's... Well, that's the thing. At launch. Not gonna matter. You're not, you don't buy a console at launch for virtual console. Like that's the thing. Yeah, no. If you're buying it at launch, it's because there's a game or two that you really want to play. This case, Breath of the Wild. So I don't really care that there's no virtual console at launch. And you can bring that up as a negative maybe later because one of the topics we talked about maybe some things we're worried about. But no one worries about with me with the virtual console is just that we don't know anything. It's not that we know what's gonna happen, we just don't know anything. Yeah. But the thing is no virtual console at launch, no Netflix, no all this stuff, it doesn't bother me at launch. Right. So that's the thing.  This is actually something I like about the launch. And I hate saying like because obviously I'd rather have all that stuff at launch. But I like that the focus on this system when it comes out because it is a tablet. And that's gonna be the first thing people think is what other tablet things are gonna use it for. Yep. They are literally saying this is a gaming machine. Period. You are not buying this thing unless you want to play games. Right. You're not buying this so you can run Netflix.  Period. And that's kind of interesting because in the past if you look at some of the mass market sellers out there beyond Wii, like PlayStation 2 blew up because you could play DVDs on it. So you could justify, I'm buying this thing to play games and play DVDs. Right. PlayStation 3 have Blu-ray players. So I'm buying this for Blu-rays and for games.  Yep. You're buying an Xbox One S like I did. Not because I cared about anything else with the 4K except for the fact that it has a 4K Blu-ray player. Yeah. And 4K Blu-ray players are even more expensive than the Xbox One S. Yeah, yeah, definitely. So it's like you'll look at all these other reasons that people buy electronics because they're multi-purpose. And Nintendo is like look there's other tablets out there. We're not trying to be them. We're not trying to be the 4K PS4 Pro, Scorpio, or even the 4K Blu-ray player. Although as we read in the spec sheet or whatever in the leaked document, it does support 4K video out for like Netflix sites or something. So it has potential that we do get 4K Netflix with it, which will be nice. Yeah, yeah. But that's not the primary purpose. That's just kind of in a side like, oh, it happens to support that but no one cares. It's just kind of it doesn't because it's not going to be used for gaming. Whereas like the Xbox One S can upscale everything to 4K. It's just upscaling. That's it. So I look at it as, for me as a gamer, I don't know how this is going to hit with mass consumers. I just said all these other things are massively successful because of the multifunction stuff. It's cheaper to get that multifunctionality than it is to get the individual functionality. So I think that's why this system is specifically made for gamers. Yeah. And I know a lot of people like Nintendo are starting to go blue ocean again. Are they really? Because what's so blue ocean about this project at launch? The fact that you could take it on the going at home? What gamer doesn't want to do that? Well, right, right. Exactly. And on top of that, it doesn't have any of the services that other people want at launch.  Yeah. Yeah. That's something that excites me about that because this is, Nintendo's continued renewed focus on games and the renewed focus on making something that matters for gamers. As an example, I remember back when it was rumored at the time that it would have cartridges. We now know it does, that that was viewed as a negative like, oh, cartridges. Why would you? So what's cheaper with this blah, blah, blah? It's better for gaming. Yeah. Yeah. I never knew why they kind of went. I mean, I get it because CDs were the newest thing. And well, the CDs happened. There's a few reasons. One, they were really cheap. Cartridges are more expensive than especially back then like N64. Yeah. Yeah. The you spend 10 cents and get 100 CDs versus one cartridge was like freaking 10 bucks to produce. Yeah. So it it was a lot cheaper. And at the time they held a lot more data. Right. So like CDs made a lot of sense, but even with the Blu-ray discs on like the PlayStation 4 and the Xbox One, that all made sense. Yeah. Because they hold more data and they're cheap to produce. And they output at, you know, like in case of like Blu-rays, you can put very high quality stuff. Yeah. Not 4K unless it's a 4K Blu-ray. The Squish novels do exist, but it was still really, really nice. And so it was always cost to performance, cost performance, cost performance. And what happened with the PlayStation 4 and the Xbox One is they started becoming what I call the Vendor and PCs. Yeah. That's basically what they are because what they started doing is stripping away a lot of the conveniences of home consoles because PC gaming and in all time, it's just getting cheaper and cheaper and cheaper. Oh yeah. Yeah. I mean the day that Switch comes out, so does the Ryzen CPUs. And that's AMD's new line of CPUs, which you probably haven't done a lot of research and do. Nope. But I know just based on what AMD is telling us, no one's done any benchmarking themselves yet. So we just have AMD benchmarks to work with that they are not only cheaper, they are better than a lot of comparable CPUs out of Intel.  Of course, no, but they don't have anything released at that price point. Right. Like one of their CPUs was a six core or an eight core or something CPU that was like 350 bucks. And that was beating out a thousand dollar CPU out of Intel. Wow. So it's like, wow. AMD's just about to change the game and make everything cheaper again. And this is before they get their new GPU line, which is supposed to come out later this year, which supposedly performs really well. Again, we don't have enough information yet. But the point is that PC game is getting cheaper. And it's getting easier and easier even if you don't feel comfortable building a PC, which I understand why. Like our PC build took a long time for us, but that we use to edit all this stuff. Right. But like, it would take a, I could see us doing it under an hour easily. Oh, yeah, yeah, definitely. I could see us pulling off and under a half hour, to be honest, not even what we're doing. Well, right. There was a lot of, we didn't have as much experience lately putting PCs together. Right. I used to put to do a lot when I was younger. And so, you know, what tools I need, usually just Phillips, and then there was things like, Oh, I didn't consider out my placement of the radiator before. Right. Yeah. All this kind of stuff. And then worried about, Oh, did I break the CPU socket? No, I really didn't. But I just haven't right messed with them on a new wish motherboard in the last 10 years. Right. Yeah. Yeah. So now that I have all the experience, like, Oh, I could put that out of the computer again. Well, that and at the time, we were also really worried about actually breaking something. Yeah. No, I'm not. Because I've done more research. Like it's really hard to break a even if we didn't have static bands. It's extremely hard to actually burn something out from static. And if you're actually concerned, all you have to do is just plug in the power supply and just touch it randomly. Yeah. And it decharges you. But anyways, we were going to take the extra precautions because $1,800. Right. Right. And especially considering that it was going to break to do what it does. But anyways, that's at the high end. Most PC gamers are at the low end. You're talking under $500. And you're talking about consoles that cost $400, $500. And so why would you get a home console over it? Well, convenience, right? You know, that that's ultimately what home console gaming is always provided is convenience over PC gaming. PC gaming has always been ahead visually. It's always been ahead control wise because, Oh, there's motion controls. Yeah, you can make those work through your PC. Yeah. So like, there's nothing that the consoles can do the PCs can't. And PCs now have easy ability to hook up. You can buy living room PCs now, like easy ability to hook up to your TV, media centers, etc. stuff that's always been around, but usually took a tech head to figure out now it's becoming more consumer friendly. Right. Yeah. And it even started kind of dating back to maybe the Microsoft XP days, when they used to were certain to sell media remotes with some of their stuff, and you could use their media center with the remote on your TV. Yeah. But again, it wasn't popular bad, then PCs were still kind of expensive. Now it's cheapening out. And PlayStation 4 and Xbox One, as much as I enjoy, especially the Xbox One, because that's the one I own, installs suck. Yeah. Their patches suck, especially apparently on the PlayStation 4, they purposely limit the download speed. So like it's why so you can have like a one gig day one update and you might not get to play for eight hours. Yeah.   So like if you buy like, say you buy the new Madden game, you preload it when you're downloading it before it comes out. So of course you can play it right away at midnight. Yeah. But are you still allowed to play other things while you're actually downloading it? Well, yeah.  They let you multitask. Okay. And you can play online. Obviously you got, I don't know, I think it actually pauses the download when you play an online game on those systems. It's been a while since I've done an actual digital download. I usually buy physical. I like having resale value because a lot of the games I play are things like yearly releases like Madden. Yeah.  For the only 10 bucks, then they're going to turn around to sell for like 20, 25. Well, if they never sell it, you know, copies of Madden. Most of the stores I've been sitting around because no one buys them, buys the old copies. Anyways, so I kind of turned that all around to the switch and where I was talking about it being a gaming focus platform. And think about the thing that Switch is doing. One, it doesn't have all these extra stuff at launch. So it's definitely only targeted at people who want to play games. Yep. Two, it's convenient. Oh, yeah. The whole thing of in the dock on the go. That's one convenience. The other convenience is popping the cartridges and play. Yeah. Done. Yeah. Right. And no installs, like updates will download in the background. Yeah. That was one thing we learned. We learned that the rest of the wild people who have it is if there's an update that comes out, it's downloading in the background, you can still keep playing. Oh, wow. That's nice. And the thing is that is nice. You can do that with other games. Obviously, in other systems, I just said that. But again, it feels like it's better on the Switch because of the fact that I also didn't have to install the game to play it. Yeah. You just pop the cartridges in and you go. That and to me, cartridges seem a lot more rugged.  These cartridges are actually smaller than the 3DS cartridges. Oh, really? Yes. So like even easier to lose. Yeah. I can pretty well lose my 3DS cartridges. It's really easy.  So if there, I'm hoping there's a game pouch in there. So I think there is. And if there isn't, then I'm going to buy one of them. They have like a little hard separate case that I could just set on my desk and it can hold like 20 games. Yeah. And that's hopefully going to hopefully fit in there. And obviously, you can always just keep them in your cases and put them on your shelf too. That's always an option. Well, right. But who does that? I have children. So like, I'll have the cases on my shelf or maybe someday in the background of my videos, but I'm not going to keep the games in there. Yeah. I have children. I got to keep them on a reach. But it's all to me about convenience for gamers. And that's what I really, really love about this console.  Let's you take the Joy-Cons off, put them in there.  You want to play, you want to play traditionally with Breath of the Wild, but then you want to play Just Dance. The controllers already are what you need for Just Dance. You want to play a two player Mario Kart. It may not be the ideal way to play it, but you already have two controllers. As I said, maybe not the ideal way, but it's there. You don't have to buy more if you don't want to play two player. It has the convenience of if we want to play Mario Kart together, our switches can go together and we can have our own screen for everything. We don't have to split screen. Same for Splatoon. Same for probably any game Nintendo releases that's multiplayer anyway. I assume we're going to take advantage of local wireless connections. So everything just feels convenient. And convenience as a gamer, as a consumer, matters a lot to me. And that's maybe what I'm most excited about beyond the games. Games are ultimately why you buy it. Like, you're buying it because it's got Breath of Light. You're buying it because of Bomberman. You're buying it because of Super Mario Odyssey. You're Mario Kart. There's all these games that make you want to buy it. But what makes me confident in buying it is that it's providing me something that there is nothing else that provides it. 3DS does provide some of it. I'm popping the cartridge to play. Right. But even then, 3DS also feels extremely dated. It's very clunky and slow at times. Yeah. Yeah. It definitely slow at downloading updates, that's for sure. Yeah, that it is. I can't play it on my TV. So like, there's all these things, or I can't play them, like, some people can. You can't play on your TV in a convenient fashion. You can buy add-ons and just like I have it, I have a modded 3DS so I can record footage off of it. So technically, it makes it easier to hook up to my TV. But it's also really expensive, so that's not something I suggest. Again, not convenient. That's not insane. Like the 3DS is nice. It works for what it is. Which personally, I think since they're keeping the 3DS going, at least for another year or two, that I think they should repurpose its marketing. I think it should be marketed at children, whereas this should be marketed at adults for the Switch. Yeah. Because they should take the 3DS and be like, look, kids don't control the TV. Parents control the TV. So kids can control their handheld. And it's cheaper. You can get like 2DS units for under $100 easily at many places. 3DS units for under $150 in many places. And kids kind of have the cool thing, you toss in your backpack. You're not really going to toss a Switch in your backpack and bring it to school. At least you should not toss a Switch in your backpack and bring it to elementary school. College is fine. Proper case, but don't bring it to elementary school. You're going to get so much trouble playing that thing there. And if someone steals it, you're not going to get it. College kids, that's your own risk. There's what it is. You control it. Even high school kids, it's your own risk.  I personally wouldn't do that because I don't want to. I wouldn't carry it around in my backpack. I wouldn't carry it around in my locker that's locked. Oh yeah, definitely. And just take things that I need in between classes. But some kids like carrying everything everywhere. I found that out even when I was at, I went to a private school and we still had kids that were like, oh, I'm going to bring everything with me everywhere. And I'm like, I guess I get that for security purposes or like, I guess you never forget anything. But it's like, yeah, dude, the school books are heavy. Yeah, that they are. No, thanks. Yeah, no, thanks. I'll just bring my one book to my one class. I know eight books to one. Yeah, I know. I kind of went half a day, half a day type of thing where I'd stop in after lunch and switch out my books for the back half of the day compared to the front half of the day. Yeah, so that's kind of how I ran it. I don't know. I'm excited for the system because it's just really everything about it feels convenient. The thing is, like you brought up a situation where you're going to use it like on the go. The only situations I think I'm going to use it on the go either if we go on there, like we go back to E3 plane flight. Oh yeah. We drive, so we go to a Bucks game in Milwaukee.  Right, yep. Like there's all these convenient things that you can use it for. But the most time I'm going to use it is when I'm going to the bathroom. Yeah. Like I always like browse and stuff on my phone. I mean, I might still do both. Yeah, right? Like that's one of the things like I keep thinking all these things I do with my phone now I'm going to be kind of doing with my switch. Listen to sports radio while playing. I'm playing baseball game with my phone. No, I'm not. I'm playing Breath of the Wild. Yeah, yeah. And then in bed. I think in bed it's just really nice. Yeah.  So instead of us taking over the TV to play Madden, we could play Madden. A thing and I'm playing against you, you're playing against me. And what's nice about us having two of them is that if Madden does come out, we can actually do like the online server thing and get fast simmy. Yeah, right. We do a lot of simmy. So yeah, that's the one thing he doesn't own the Xbox. So like when we do the simmy, we can't do it over because online, their online servers have really, really fast simmy compared to their local console. Anyways, you guys, that's something that I'll care about. But if Madden comes out for it. But yeah, it's I'm just really excited. I don't know if the excitement's coming through because it's just I'm still in a state of disbelief. Right. That we're under a week out. Like it's happening. Yeah. Everything's paid off. It's happening. We're going to be there. Yeah.  But yeah, yeah, because yeah, because I'm coming home, like, like, but let's end this topic with talking about what are we doing day one with that switch? You tell me what your plans are. You have to go to work. So I'm charging it home by asleep and then taking it to work and playing it over my lunch tower. That's what I'm doing. Nice. Nice. So me, I get to take my home and film an unboxing. And then film another unboxing of the Breath of the Wild special edition. And then hook it up to my streaming setup and pray it all works. Like I'm not going to record like setting up like there's plenty of videos out there setting up the switch and everything. So I'm not going to record any videos of that. But the next time you'll see me after that point, we'll literally be playing with the switch on Breath of the Wild on the live stream. So I'm going to hopefully I'll get those videos edited if you come over Friday night. Working. Yeah, you're working. So Saturday, whenever you get a chance to come over, that's what I'll finally get to sit down and edit those videos and get them out. So hopefully I have them out that weekend. I would love to give them out the same day, but we'll kind of see what kind of see how it goes because I really want to just get straight in the live stream and I'm playing Breath of the Wild. I don't really want to waste all this time editing videos. I don't really want to record the unboxings, but since I can't live stream the unboxing anyways, I might as well record it. So that's my day one. And then day two again, more live streaming, more live streaming, more live streaming, just live streaming like crazy. And then finally, I think my day three is when I'll finally get more experience with the system undocked and doing other stuff, whether it's playing other games, whether it's trying to browse the internet, there's no web browser, but maybe they have there's someone talking about there might be a developer way around it. So I might try to see if I can get to the developer mode and get around it and try to browse the internet just to see if I can do it. Because you know, maybe it's a situation where every switch is a dev unit just like every Xbox one is a dev unit. I don't know. I'm excited. It's one of those things. One thing I am debating you guys can let me know in the comments is if you want me to do like like a Facebook or YouTube live of like literally us walking into the store and getting to it. I was kind of thinking that like like it's up to you guys you want to see because I'm going to be so pumped. I don't know if I'm going to be first in line because I'm not going out hours early because I already have it preordered. But I'll be out there about 30 minutes early and be you know obviously among the people getting out. I'm just I'm debating if that's something if you guys be interested in seeing the live reactions to us getting it and the excitement and everything and then obviously getting into the car and looking at a little loot and being like oh my god yeah right yeah right you have to go to bed that sucks I'm going to go well you never know I might end up staying over here and just sleeping sleep like yeah um yeah then I'll say you work and then work so yeah I'm going to be at work from probably 8 30 to midnight yeah so he's he's pretty much dead until maybe sometime on Saturday yeah until you get super addicted to the rough of wild that he's still asleep yeah right what's gonna happen


A drone is an unmanned aerial vehicle, UAV, operated remotely by a pilot on the ground. Drone technology often includes other survey programs and GPS systems. Drones have found a role in land management and are becoming more popular in agriculture and forestry. In agriculture, drones allow farmers to complete crop assessments, efficiently count and survey cattle, and monitor different crop diseases. In forestry, drones are used for timber sales, plant disease detection, production of aerial photographs for landowners, and locating and fighting wildfires. The use of drones has improved worker and landowner safety. They assist in remote damage assessment of trees blown down after storms. Drones can also stream live video of land management activities, such as a prescribed fire or tree planting.


Hey Coach, how's it going? My name is Ben Navers. I'm the creator here at BuildMySportsBiz.com. Here is where we show basketball coaches or coaches in any sport who want to create, grow, or scale their private basketball training business or any sport business out there. So today you're watching this video because maybe you haven't started your basketball business yet and you want to learn how to do that. So fortunately for you, I've already helped a lot of basketball coaches. I've helped coaches in every sport actually and I help them get started very quickly. This is going to help you get started within the next 24 hours. So here's what you do.  I'm sure you already are coaching either players on your team, players at your high school, players at your college, whatever it is. You already have influence over kids and parents. So what you want to do, very simple, is get on the phone, find two or three players that you've already coached, call their parents, offer them a free evaluation session into your program, have them come do a private training session with you, and from there you are off to the races. You do not need a website, you don't need to have this crazy payment system yet, you don't need to be running Facebook ads, you don't need to have these logos, you don't need to have a bunch of t-shirts. All of that stuff that you see people have, don't need. When you're just starting, you need to go quickly. You do not need to hesitate. The longer you take, the more you're going to be thinking about, oh man, I wish I could have this business. You don't need to wish anything. You can wake up tomorrow or do it now.  If you want a strategic step-by-step system on exactly where to get insurance, what is the best payment system to use, what is the best website, how to get more clients. If you want that, I've created a complete e-book and a video program that will definitely help you out. I've already had over 700 coaches who've already gone through that product. It's definitely going to help you if you want to take action. If you are a coach that wants to get started, I highly recommend our product. You're going to see, it's going to come across the screen here. You click on that, you'll go to a page where you can learn more about it. It's a complete e-book and it's a video program. It'll take you maybe an hour and a half to go through. You'll see great results there. But regardless if you're going through that product or not, you can get started by simply just taking action right now. Don't wait until tomorrow. Don't wait until the next day. Get on the phone, start using your resources that you already have and look to create the business of your dreams. That's what we help coaches do here. That is my whole mission. The only reason why I create these videos is the only reason why we've created hundreds of podcast episodes is to help you personally with your business. If you want more help, definitely go through our program. It's called the Startup Sports Academy. Go through that program and from there, if you want additional help, I would love to talk with you over the phone. You go to our website, BuildMySportsBiz.com. There's an application form there where we can chat if you need more one-on-one help. That's it for today's video. I'll see you guys next time.


Hello, this is LaptopMedia, and today, we will show you how to open the HP Probook 635 Aero G8 and what's inside of it. To get inside of this device, you need to undo 6 captive Philips head screws. Then, pop the bottom panel with a plastic tool, and remove it from the chassis. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. Here, the battery has a capacity of 53 watt hours. Despite the lightweight of the device, HP has managed to put two RAM Sodom slots for up to 64GB of memory in total. As for the storage, you get 1 M.2 PCI EX4 slot. Lastly, there is the cooling, it employs one heat pipe, as well as a heat sink and fan of medium size. If you'd like to see more disassembly videos of the latest notebooks we would highly appreciate if you hit the like button and subscribe to the channel.


Myself, Mr. Vishal Angeere, Assistant Professor, Department of Electronics and Telecommunication, WIT, Sulapur. Friends, today we are going to study IDEs, that is integrated development environments used in embedded development. Learning outcome, at the end of this session, students will be able to use IDEs for development of an embedded application. So friends, before starting with IDEs used in embedded development, you have to pause this video here and you should recall which IDEs you have used to develop a mini project and how we are going to use that IDE for development of a small project or small scale embedded project. First point is embedded software. So embedded developer is going to execute software which is to be present in its hardware. So think it's embedded hardware will remain same and based on application, the software will go on changing. So for different applications, different type of embedded software are to be used. So think it's the hardware will remain same and we can embed software or we can burn different wrong images into the same hardware for different applications or to upgrade a current system. So to create software, the following basic components are to be needed. Into that, first one is operating system. So different type of operating systems are there which are going to be used to design embedded application. So Windows CE, Linux, ThreadX, Nucleus, RTOS, such type of operating systems are to be used. Languages. So the program is to be returned in different type of languages. So into that, C, C++, Python, JavaScript, Visual Studio, these type of languages, we are going to use tools. So IDE, PDK, SDK, compiler, tool chains, hardware and software debugger. So these type of tools we are going to use. Example is ST-Link Sega. Now we will see types of some embedded software development tools. First one is editor. For writing C code or assembly memonics using the keyboard of personal computer for entering the program, we are going to use editor, which creates a source file that stores the edited file. So generally, we have to use editor to write C or assembly language code or C++. So for this purpose, we are going to use editor. So JNE is a good example of text editor. This is small and lightweight environment that uses the GTK plus toolkit. This JNE supports C, Java, PHP, HTML, Python, Perl, Pascal and some other types of files. Next tool is compiler. So a compiler is tool used for transforming high-level programming language code into low-level machine language code. So when user writes a program, so that program is in the form of high-level language. So the compiler will convert that high-language programming code into low-level machine language code so that a machine can read the low-level language. So the conversion from high-level language to low-level machine language is to be done by compiler. So keelC51 is a popular compiler that creates app for 8051 microcontrollers and translates source code written in the C language. So this keelC51 will perform the task of converting a source code which is written in C language into machine language or low-level machine language. Next type of tool is assembler. For translating assembly memonics into binary opcode that is into an executable file called binary file we are going to use assembler. So that assembly memonics is to be converted into binary opcode or binary codes which is to be executable file. So JNU assembler that is GAS is widely used for Linux operating systems and can be found in the Macintosh tool package. Next debugger. Debugger is a tool used for testing. It eliminates bugs and errors notifying places where they occur. Debuggers identify the lines where issues are found so programmer can address them quickly. So generally debugger is to be used to detect error so that we can correct that error and the embedded system or that embedded application which is to be developed is to be error free. A good debugger tool is IDA Pro that works on Linux, Windows and Mac OS X operating systems. It has both free and commercial versions and is highly popular among developers. Linker. Linker links codes with other codes required. Linking is necessary because of the number of codes to be linked for creating the final binary file. So generally embedded application is to be developed with the help of small codes. So generally all the small codes are to be linked with each other. So linking of these small codes is to be done by linker. If we consider a simple example that if we have writing a code for linking of LEDs so in a main program we call delay, delay subroutine. So generally delay subroutine program is stored at somewhere in the another memory location. So linking of the main program with that delay subroutine is to be performed with the help of linker. So JNU ID is one of the linker tool which we can use. Next tool is emulator. So emulator is used to simulate all functions of an embedded system circuit including that or additional memory and peripherals. It is independent of particular target system. So this emulator is to be used, generally used to check how that application works in real time environment. So it is exact replica of that system which we are going to be developed. So all these are the tools to be used while developing any embedded system. One thing is all these tools are necessary while developing any embedded application. So all these are must, so all these tools are to be included in a single package or in a single system. So for that we have to use IDEs. So IDEs integrated development environment. Something about the list of embedded software development tools, we can't but mention integrated development environments. All the above mentioned tools are needed for creating your embedded software. But it would be extremely inconvenient to use them separately as I said before. So adding another layer of complexity to the project. So hence to simplify the development process it is highly recommended to use integrated environments. So IDEs, IDEs software that provides a set of necessary tools in one package. So these are some embedded software development tool list that is IDEs we are going to use while developing an embedded application. So into that first one is ANKIL, next WebStorm. Next one is Ordino which is to be generally used or in many educational systems regular practice is to be done on Ordino ID, next MPLABX, Visual Studio, Eclipse, NetBeans and MATLAB. So these are some IDEs or embedded software development tools which we are going to use to develop any embedded application and these IDEs will include all these tools like Emulator, Linker, Debugger, Assembler. So all these are to be included in this IDEs. While preparing this video lecture I have referred Internet of Things by Raj Kamal and the web page. Thank you.


Okay, we're back at Caesar Forum, the Snowflake Summit 2022. The Cube's continuous coverage is day two, wall-to-wall coverage. We're so excited to have the analyst panel here, some of my colleagues that we've done a number, you've probably seen some power panels that we've done. David Menegar is here, he's the Cedar Vice President and Research Director at Ventana Research. To his left is Tony Baer, Principal at DB Insight and my in the co-host seat, Sanjeev Mohan, Principal at Sanjimoh. Guys, thanks so much for coming on, I'm glad to be here. Glad to be here. Thanks for having us. You're very welcome. I wasn't able to attend the analyst's action because I've been doing this all day, every day. But let me start with you, Dave. What have you seen that's kind of interested you, pluses, minuses, concerns? Sure. Right on. Well, how about if I focus on what's, I think, valuable to the customers of Snowflake? Right. And our research shows that the majority of organizations, the majority of people, do not have access to analytics. And so a couple of the things they've announced, I think, address those or help to address those issues very directly. So Snowpark, in support for Python and other languages, is a way for organizations to embed analytics into different business processes. And so I think that'll be really beneficial to try and get analytics into more people's hands. And I also think that the native applications, as part of the marketplace, is another way to get applications into people's hands rather than just analytical tools because most people in the organization are not analysts. They're doing some line of business function. They're HR managers, they're marketing people, they're sales people, they're finance people. They're not sitting there mucking around in the data. They're doing a job and they need analytics in that job. So, Tony, thank you. I've heard a lot of data mesh talk this week. It's kind of funny. I can't seem to get away from it. Yeah, I can't see it. It seems to be gathering momentum, but what have you seen that's been interesting? Well, what I have noticed is that unfortunately, because the rooms are too small, you just can't get into the data mesh sessions. So there's a lot of interest in it. It's still very, I don't think there's very much understanding of it, but I think the idea that you can put all the data in one place, which to me, Snowflake, it seems to be sort of in a way, it sounds like almost like the Enterprise Data Warehouse, Cloud Native Edition, bring it all in one place again. I think it's providing sort of, I think for these folks, the thing, this might be kind of like a linchpin for that. I think there are several other things that actually, that really have made a bigger impression on me actually at this event. One is basically, is very much their move with Unistore. And it's kind of interesting coming from MongoDB last week. And I see it's like these two companies seem to be going, converging towards the same place at different speeds. I think Snowflake is going to get there faster than Mongo for a number of different reasons. But I see like a number of common threads here. I mean, one is that Mongo was a company, it's always been towards developers. They need to start cultivating data people. These guys are going the other way. Exactly, bingo. And the thing is that, but I think where they're converging is the idea of operational analytics and trying to serve all constituencies. The other thing, which also is, in terms of serving multiple constituencies, is how Snowflake has laid out Snowpark. And what I'm finding is like, there's an interesting dichotomy. On one hand, you have this very ingrained integration of Anaconda, which I think is pretty ingenious. On the other hand, you speak, let's say the data robot, folks, and say, you know something, our folks want to work, data scientists, we want to work in our environment and use Snowflake in the background. So I see those as kind of some interesting sort of cross-cutting trends. So Sanjeev, I mean, Frank Sloobin will talk about, there's definite benefits into going into the walled garden. Yeah. And I don't think we dispute that, but we see them making moves and adding more and more open source capabilities like Apache iceberg. Is that a move to sort of counteract the narrative that Databricks has put out there? Is that customer-driven? What's your take on that? Primarily, I think it is to contract this whole notion that once you move data into Snowflake, it's a proprietary format. So I think that's how it started, but it's hugely beneficial to the customers, to the users, because now if you have large amounts of data in park air files, you can leave it on S3, but then you're using the Apache iceberg table format in Snowflake, you get all the benefits of Snowflake's optimizer. So for example, you get the micro partitioning, you get the metadata. So in a single query, you can join, you can do select from a Snowflake table union and select from an iceberg table. And you can do store procedure, user-defined functions. So I think what they've done is extremely interesting. Iceberg by itself still does not have multi-table transactional capabilities. So if I'm running a workload, I might be touching 10 different tables. So if I use Apache iceberg in a raw format, they don't have it, but Snowflake does. Right, hence the delta. And maybe that closes over time. I want to ask you, as you look around this, I mean, the ecosystem is pretty vibrant. I mean, it reminds me of like re-invent in 2014, you know? But then I'm struck by the complexity of the last big data era and Hadoop and all the different tools. And is this different or is it the sort of same wine new bottle? You guys have any thoughts on that? I think it's different. How so? And I'll tell you why I think it's different because it's based around SQL. So back to Tony's point, these vendors are coming at this from different angles, right? You've got data warehouse vendors and you've got data lake vendors and they're all going to meet in the middle. So in your case, you're taught operational analytical, but same thing is true with data lake and data warehouse. And Snowflake no longer wants to be known as a data warehouse. They're a data cloud. And our research again, I like to base everything off of the research. I love when you bring your research in. Our research shows that two thirds of organizations have SQL skills and one third have big data skills. So, you know, they're going to meet in the middle, but it sure is a lot easier to bring along those people who know SQL already to that midpoint than it is to bring big data people to that midpoint. I remember Amarara Adala, who was one of the founders of Cloudera said to me one time, John Furrier in the cube, that SQL is the killer app for Hadoop. Yeah. Yeah. The difference with Snowflake is that you don't have to worry about taming the zoo animals. They really have thought out the ease of use.  One is ease of use and the other is scale. And they've had, and that's basically a very, you know, I think very much differentiates it. I mean, Hadoop had the scale, but it didn't have the ease of use. But don't I still need, like if I have, you know, governance from this vendor or, you know, data prep from, you know, don't I still have to have expertise that's sort of distributed in those worlds, right?  Yeah, so the way I see it is, Snowflake is adding more and more capabilities right into the database. So for example, they've gone ahead and added security and privacy. So you can now create policies and do even set level masking, dynamic masking. But most organizations have more than Snowflake. So what we are starting to see all around here is that there's a whole series of data catalog companies, a bunch of companies that are doing dynamic data masking, security and governance, data observability, which is not a space Snowflake has gone into. So there's a whole ecosystem of companies that is mushrooming, although, you know, so they're using the native capabilities of Snowflake, but they are at a level higher. So if you have a data lake and a cloud data warehouse and you have other like relational databases, you can run these cross-platform capabilities in that layer. So that way, you know, Snowflake's done a great job of enabling that ecosystem. How about the Streamlet acquisition? Did you see anything here that indicated they're making strong progress there? Are you excited about that? Are you skeptical? Go ahead. I think it's like the last mile, essentially. In other words, it's like, okay, you have folks that are basically that are very, you know, very comfortable with Tableau, but you do have developers who don't want to have to shell out to a separate tool. And so this is where Snowflake is essentially working to address that constituency. To Sanjeev's point, I think part of it, this kind of plays into it, is what makes this different from the Adoop era is the fact that all these capabilities, you know, a lot of vendors are taking it very seriously to make, you know, put this native, and obviously Snowflake acquired Streamlet so we can expect that the Streamlet capabilities are going to be native. You know, the other thing too about the Adoop ecosystem is Cloudera had to help fund all those different projects and got really, really spread thin. I want to ask you guys about the SuperCloud. We use SuperCloud as this sort of metaphor for the next wave of cloud. You've got infrastructure, AWS, Azure, Google. It's not multi-cloud, but you've got that infrastructure. You're building a layer on top of it that hides the underlying complexities of the primitives and the APIs, and you're adding new value, in this case, the data cloud or super data cloud. And now what we're seeing now is that Snowflake putting forth the notion that they're adding a super pass layer. So you can now build applications that you can monetize, which to me is kind of exciting. It makes this platform even less discretionary. We had a lot of talk on Wall Street about discretionary spending, and that's not discretionary if you're monetizing it. What do you guys think about that? Is this something that's real? Is it just a figment of my imagination, or do you see a different way of coming? Any thoughts on that? So in effect, they're trying to become a data operating system. Yeah, yes. And I think that's wonderful. It's ambitious. I think they'll experience some success with that. As I said, applications are important. That's a great way to deliver information. You can monetize them. So there's a good economic model around it. I think they will still struggle, however, with bringing everything together into one platform. That's always the challenge. Can you become the platform? That's hard to predict. I think this is pretty exciting, right? A lot of energy, a lot of a large ecosystem. There is a network effect already. Can they succeed in being the only place where data exists? I think that's going to be a challenge. I mean, the fact is, I mean, this is the classic best of read versus the umbrella play. And the thing is, this is nothing new. I mean, this is like the old days with enterprise applications where basically Oracle and SAP vacuumed up all these, all these applications in their ecosystem. Whereas with Snowflake, and if you look at the cloud, the hyperscalers, they'll build out their own portfolios as well. Some hyperscalers are more partner friendly than others. What Snowflake is saying is that we're going to give all of you folks who basically are competing against the hyperscalers in various areas like data catalog and pipelines and all that sort of wonderful stuff. We'll make you basically all equal citizens. The burden is on you to basically, we will lay out the APIs. We'll allow you to basically integrate natively to us so you can provide as good experience, but the onus is on your back. Should the ecosystem be concerned as they were back to re-invent 2014 that Amazon was going to nibble away at them or is it different? I find what they're doing is different. For example, data sharing. They were the first ones out the door with data sharing at a large scale. Then everybody has jumped in and said, oh, we also do data sharing. All the hyperscalers came in, but now what Snowflake has done is they've taken it to the next level. Now they're saying it's not just data sharing, it's app sharing. And not only app sharing, you can stream the thing, you can build, test, deploy, and then monetize it, make it discoverable through your marketplace. You can monetize it. Yes, yeah. So I think what they're doing is they are taking it a step further than what hyperscalers are doing. Because it's like what they said is becoming like the data operating system. You log in and you have all of these different functionalities. You can do machine learning now, you can do data quality, you can do data preparation, and you can do monetization of data. Who do you think is Snowflake's biggest competitor? What do you guys think? It's a hard question, isn't it? It is. Because you're like, because we all get the, we separate compute from storage, we have a cloud database and you go, yeah, okay. That's nice, but it's this. I'll take a crack. That's uniqueness. I mean, put it this way. In the old days, it would have been the on-prem household names. I think today's the hyperscalers. And the idea with, I mean, again, this comes down to the best of breed versus get it all from one source. So where is your comfort level? So I think their co-opetition are the hyperscalers. Okay, so it's not Databricks, because why, they're smaller? Well, put it, there are some, okay, now within the best of breed area, yes, there is competition.  I think what, you know, another potential competitor, and I think Snowflake basically, you know, as admitted as such, potentially is MongoDB. I was just going to say, yeah, I mean. Exactly, so I mean, yes, there are two different levels of competition. They're sort of on a longer term collision course. Exactly, exactly. Sort of service now and Salesforce. The only thing that was the reaction I get when I say that, and a lot of people just laugh, I was like, no, you're kidding, there's no way, and I said, excuse me. Well, but then you see Mongo last week, you know, we were adding some analytics capabilities, and always been developers, as you say. They trash SQL, but yet they finally have started to write their first real SQL. We have MC, MQL, now we have SQL, so. What were those numbers, Dave? Two thirds of one third. So the hyperscalers, but the hyperscalers, are you going to trust your hyperscalers to do your cross-cloud? I mean, maybe Google, maybe, I mean, Microsoft perhaps, AWS not there yet, right? I mean, how important is cross-cloud, multi-cloud, super-cloud, whatever you want to call it? What is your data showing? Cross-cloud is important. If I remember correctly, our research shows that three-quarters of organizations are operating in the cloud, and 52% are operating across more than one cloud. So, you know, two thirds of the organizations that are in the cloud are doing multi-cloud. So that's pretty significant. And now they may be operating across clouds for different reasons. Maybe one application runs in one cloud provider, and another application runs in another cloud provider. But I do think organizations want that leverage over the hyperscalers, right? They want to be able to tell the hyperscaler, I'm going to move my workloads over here if you don't, you know, give us a better rate. Yeah, I mean, I think, you know, from a database standpoint, I think you're right. I mean, they're competing against some really well-funded, and you look at BigQuery, rarely solid platform, Redshift, for all its faults, has really done an amazing job of moving forward. But to David's point, you know, those, to me anyway, those hyperscalers aren't going to solve that cross-cloud cloud problem. Right, right, no. Certainly not as quickly. No, no. Or with as much zeal. Right. We'll operate across cloud, but we're going to operate better on our clouds. Exactly, yes, yes.  So the way Snowflake does multi-cloud and the way MongoDB do are very different. So Snowflake says we run on all the hyperscalers, but you have to replicate your data. What MongoDB is claiming is that one cluster can have nodes in multiple different clouds. That is, you know, quite something. Yeah, right, I mean, again, we got to go, but last question, Snowflake. Undervalued, overvalued, or just about right? In the stock market, or in customers' minds. Yeah. Well, but, you know, I'm not sure that's the right question. Well, but no, that's the question I'm asking, you know. No, I'll say the question is undervalued or overvalued for customers, right? That's really what matters. There's a different audience who cares about the investor side of it. Some of those are watching. But I believe that from the customer's perspective, it's probably valued about right. Because the reason I ask it is because it has so hyped. Yes. It had a $100 billion value. It surpassed service now's value, which is crazy. For this, now it's obviously come back quite a bit. It's below its IPO price. So, but you guys are at the financial analyst meeting. Scarpelli laid out the 20, 29 projections, signed up for $10 billion, 25% free cash flow, 20% operating profit. I mean, they better be worth more than they are today if they do that. If I see the momentum here this week, I think they're undervalued. But before this week, I probably would have thought they are at the right valuation. I would say they're probably more at the right valuation, especially because the IPO valuation was just such a false valuation, so hyped. Yeah. Guys, I could go on for another 45 minutes. Thanks so much. David, Tony, Sanjeev. Always great to have you on. We'll have you back for sure. Thanks for having us. Thank you. Keep it right there. We're wrapping up day two on theCUBE at Snowflake Summit 2022. Right back.


John, please take your seats. So we want to start, please take your seats. Our next speaker is Martin, the rest of the Red Hat, who will talk to us about leveraging the standings and improvements on digitalization.com. Welcome to the session about e-event, FDM, and virtualization. My name is Martin Redkin, and I'm working for the over the networking team. In specific, we'll talk about the integration of the over the project with OpenStack OpenDoorful Network. The agenda for today is... First, I will give you a very brief overview of the software behind networking and the overview of them. Second, a very brief overview of their over networking. Then I will talk about the feature called Over External Network Providers. And last, we'll go over to the integration between Over and OpenDoorful Network, the Over Provider of the End Project. Let us start with a brief introduction to software-defined networking. Software-defined networking is a concept where you programmatically configure all the networking devices in your network environment, such as routers or switches, in order to make your networking environment to appear to have desired logical networking capability. In simple words, if you have a physical environment like we have on the left, we configure the switches in such a way that the device is connected to the network, as you can see as it has a topology on the right. Typical software-defined networking solution is built like this. We have an FGN controller, which takes in the logical network topology that we desire. It reads the physical state of the system, and based on those codes, it computes the networking configuration for our network device, and sends the required configuration to the SDM node. One of the implications of software-defined network is OpenVisual OpenVirtual Network. It's called OVEN central. The level is meant to represent it. OVEN provides us with layers 2 and 3 virtual overlays on top of a number of obvious instances that we have in our system. It gives us logical entities, such as logical switches, which are the equivalent of OVEN networks, or OpenVisual network networks, logical switchboards, logical routers, load balancers, accept control lists, and more. The OVEN architecture. Architecturally, OVEN consists of two layers. We have the OVEN central and the distributed OVEN controller. OVEN central consists of two databases. We have the NORAS database, which holds the logical state of the system, this is the state that we desire, and the SOUTH database. The SOUTH database holds the physical state of the system, and it also holds the meetings between the physical devices and the logical entity. We have something called the NORAS demon. This is a demon that looks at the NORAS and SOUTH databases and updates the SOUTH database to mirror the changes to our logical network technology. The other value is a distributed OVEN controller. It's installed on top of an obvious instance on each of our networking tools. It monitors the SOUTH database to update it with the physical state of the system, and to change the meetings of the logical entities to the physical devices that it controls on the OVEN network. Let us look a little bit deeper into how OVEN works. It consists of three items that enable OVEN. One is a number of obvious instances in our system. The second is the open-to-protocol, which allows us to control the behavior of our obvious instances. And the seventh item is tunnels between our obvious instances. When we look at a basic obvious bridge, it just connects all the ports connected to it to all the other ports on the bridge. Now, let's introduce the open-to-protocol onto it. Now we are able to control the traffic going between our different ports. For example, with some of the simple rules below, we are able to specify that any traffic originating at a port with a source MAC of 1 going to source MAC 3 will be outputted to port 3, but any traffic going from MAC 1 to a destination MAC of 2 and 4 will be dropped. So we are able to divide our obvious switch into multiple logical switches, which will separate the networks into the logical networks. Another item, the tunnels between our obvious instances. If we add another port to each of our obvious instances and connect the port with a tunnel, all the traffic from one switch will be moved to the port, will be moved to all our other switches and in turn all the ports on the other switches will be able to see all traffic originating on the other switches. So in result, what we get is not just multiple switches independently fitted, but one big aggregated switch. When we combine all this, we will have our big aggregated switch consisting of all our switches in the environment, which will be sent divided by using the open-to-protocol and tools controlling the traffic into smaller logical switches. Let me now go over to give you a brief introduction to our other networking. I will skip the introduction to other. If you are interested, please come to our other course in building today. This is how we talk about our native other networking. It's pretty nice, it has nice features like bonding, brilliant support, network filters, but it has some problems too. One, it is based on the Linux bridge, so this is very little networking. If you want to create a network and add some virtual machines to connect some virtual machines to this network, we connect a Linux bridge and we attach our port to that Linux bridge. If we want our network to span over multiple hosts, we have to make sure that the appropriate host we connect the Linux bridge to a nick on the host and we must connect the nick between the hosts. This is a value two connection, so network separation is our problem. Another way that we ensure network separation. Another problem is that since we can only connect one bridge to a network interface, only one network per nick on a host. We can go around this using villains. If we have villains, we can have multiple networks on one nick, but then we must also make sure that our infrastructure is connected to the host support of this. Another probably bigger problem is that our network networking can only control the networks within others and our internal networks can only be controlled by others. So no external control for our network. Now, the problem I mentioned three slides ago about not being able to control our networks from the host side. In the data center, it becomes a problem. The data center is usually not only ordered, we would like it to be sold, but somehow people also want to use other systems. So usually we have multiple systems running in the data center. Systems that need to connect to each other. It would only have a network management confined to our different subsystems and it becomes a problem. What we would like to do is to have one centralized network management system that would allow us to manage the networking over all our subsystems in the data center. So we can create one network for instance that all our subsystems would be able to connect to. The metaphor is probably not a good one. Somebody wanted it out for me today because in the book nobody likes centralized management and they did it away with but in the data center it's actually a good solution. So what we came up with is a feature called external network providers. It allows to externalize their network implementation in order to external network providers. It could be any network management systems out in the market it could be for example OpenStateU from or as you will see later OpenVisage OpenVirtual Network. One problem that we had we had to come up with an API that would allow us to control the external network providers. It was pretty tempting to come up with our own implementation our own API reinventing the rule is always pretty exciting. But instead we have chosen to implement an already existing implementation something that is widely used open and like. So we chose the OpenState network in API. If you want to connect an external network management system all you need to do is make sure it implements the OpenState networking API and you can connect it out of the box. So because of this decision the first implementation that we had was OpenState Neutron. OpenState Neutron uses the OpenState networking API so it was almost just enough to connect it it was working out of the box. The OpenState Neutron external provider is available you can use it it's still in the experimental stage we never finished it in such a way that we declared it ready to be supported. This is because it was not really live the problem was that Neutron itself was pretty complicated just to install the external network provider OpenState Neutron and it had more resources than for already itself. So not many people do. Let me just go over how an external network provider would work in connection with over. We have a scenario where we want to create an external network and then create a port to connect to an external network that we can just create. As the first operation we will go to the other UI and we will click to create a new network. On the other network panel we will just have to click one checkbox make it an external network and choose the external provider that we want to create it on. That request will be sent over using the OpenState Network API to the external network provider. The external network provider would create the network as the second operation it would talk to the external network to the network controllers and create the network in our network meeting process. The second operation we would be creating the port, the veneque on our VM. We want this veneque to be connected to this specific network. What our engine would then do first it would create a port to the external network provider. The external network provider usually it would just create a meeting between the logical port and not yet existing veneque in the system. So probably no interaction with the network infrastructure yet. After creating the port on the external network provider Ovid would send a request to VDSM. VDSM is the Ovid agent on top of our virtualization host telling it to create a veneque on the VM and plug it into the external network. We have a feature in VDSM called hook scripts. Hook scripts are user defined scripts which allow the user to plug in into every single significant life cycle event of a virtual machine. So you can do it either before a life cycle event or after. You can do it before we start the VM after we stop it, before we stop it. The ones that we would be interested in are the hooks relating to networks. For example, in our case this would be before veneque plug and after veneque plug. In one of those tools we would have to tell the network controller on the VM host that a port with such a logical port ID would be plugged into this specific physical port. The network controller usually tells the external provider that this has just happened. We have a new method logical to physical and the external network provider would send a wire of this port to our to our external provider network. Let's recap what we know so far. One fact is that other network management is limited. The second one is software defined networking is not that easy. OpenStack Newton is heavy and complicated. The problem with Oven is that we speak OpenStack networking API. Oven only speaks command line or it speaks obviously protocol. So you have to talk to OBSDB directly. They don't have bigger expressions like network port, you have to do it all manually. So how do we resolve it? If you can guess right I can offer you a free speaker that's the only thing I can offer you. Any tools? Yes. So after the session this time the editor speaker what we decided to do is create a project called Oven Provider Oven. What it does is just an adapter from Oven to Oven so it's an Oven adapter for the OpenStack network in the API. I will go back to the diagram showing Oven architecture adding two items. So on top we have our cloud management system below that we have our Oven cloud management system and below that we have Oven as we saw before. Our cloud management system that is Oven it could be Neutron Neutron is providing support for Oven but as I said previously we don't really need all the complication connected with Neutron we don't need to have a few additional VMs just for hosting OpenStack we don't need all the complicated configurations. What we need is just a really simple adapter that would allow us to use Oven using the OpenStack networking API. So what we have is a really small process the code base is less than 100K and it's really in Python it's just as simple it's just a simple adapter. The job initially was pretty easy the basic entities in OpenStack networking and in Oven are pretty similar the OpenStack network is almost an equivalent of Oven logical switches the ports can be mapped to logical switchboards there are a few small differences like the current relationship in OpenStack the child keeps a reference to its current in Oven is the other way around so initially it was pretty easy what would come in as an OpenStack networking API for here we create a new network to end up with an Oven configuration at least on the right hand side now if you notice the IDs of the different entities are the same so if you don't want to limit your control of Oven just to Oven you are pretty used the Oven tools like the Oven command line using the same IDs you are not only limited to Oven if you want other applications in your data center to also use Oven and to control it you are pretty useful by the way any changes down to Oven externally outside of Oven will be taken care of and Oven will be able to handle this too sometimes the job is not as easy in the case of load balancers we can see on the right hand side that in Oven a load balancer is actually one liner in a logical switch we only have the big property tells us the source IP and the endpoints for which should be used for balancing this one IP in Oven stack the load balancers are much more complicated we have quite a nice hierarchy of different entities that contribute to creating the load balancer the problem is that we not only have to create an Oven load balancer based on the information that we get from Oven stack API that would be pretty easy but we have to also do it other way around so if somebody issues get request he wants to get the information of the load balancer we have to reconstruct the whole Oven structure based on the little information that we have in Oven when we worked on the project we wanted to create an abstraction mail for the Oven database not to deal with the role of the SVP calls every time but to create calls for network calls and so on while working on it we saw that we are not the only ones trying to solve the problem another thing that have exactly the same issue and tried to use also Python project was Oven stack Newton they were the code wasn't complicated but the result was almost the same so we talked to them and we decided to pull the common code out Oven stack Newton was much further advanced than we were so the decision was to take the Oven code out of Oven stack Newton and create a new Oven stack project so this way Oven stack OBSDB project was created if you need higher abstraction API for the Oven database you are free to use Oven stack OBSDB now let us look at what we have achieved the benefits of using the Oven in Oven one is centralized management this is actually a benefit not only for Oven but for all external network providers you can use centralized network management you can manage your networks from outside of Oven you could also use Oven to manage your other networks second benefit is much easier configuration as I said previously native Oven networking it was layer 2 networking now with Oven outside of the host it is layer 3 networking so instead of taking care of the network separation yourself what you need is just layer 3 connectivity between the hosts to create the channel and that's it don't worry about anything else if you are configuring your network the only thing you need to take care of is the network connectivity network configuration is much easier very similar it's resistant to infrastructure changes if you have your hosts connected you need to change anything in the networking infrastructure sure go on just make sure my packets can be routed to the other hosts when working on the provider initially it was supposed to be one of the many network providers in our system we already had the new phone provider there is one external party that is working on their own network provider for Oven legacy solution so it was supposed to be one of many but while creating it we decided that we like it so much that we wanted to be to create a solution next to our networking so now Oven provider is available out of the box it's supported when you install Oven engine and you configure it you can specify the Oven provider Oven to be installed alone with Oven engine it will be automatically configured it will set up all your keys all your connections it works out of the box the second item is the Oven host from the engine from the engine UI you can also request the Oven provider Oven along with Oven and OpenVis which should be installed on your host and to be automatically configured to be used with the engine another benefit it now has an OpenStack network compliant proxy to Oven if you want to use Oven not the other way by using the command line or going into OBSDDR directly you can use it via the OpenStack networking API we tried to advertise this with some other projects and there was some interest in some and we actually managed to convince ManageICU that is a good idea and ManageICU decided to support networking using our networking provider so if you now go into ManageICU you can add networking provider based on Oven our at the beginning for Oven we just needed networks, ports and some that was it we don't need to control anything else in Oven but when ManageICU started using the provider it turned out that they need much more than just the basic entities they need routers, load balancers and access control with probably there will be more so far that's all we want so network ports and subnets we already have that we are almost done implementing routing it's already partly available in our release 4.2 for the next releases we have plans to implement load balancers access control lists there could be other things later on like quality of service et cetera so we are ready in close to the end I was actually told every time I reversed I was much over time so I tried to do I saw out if it's like Oven production I tried to be as fast as possible and it looks like we are much ahead of time the summary I would like you to remember from this session one now on Oven it's not only the Oven it's networking we have the Oven based networking available too using the Oven provider the other item if you are looking for a nice sdx solution a small one you can use Oven using our provider using the Oven stack networking API and deal with high level Oven stack networking extra so thank you do you have any questions excuse me the question is is it for production yes in Oven 4.2 we support networks, ports and subnets this is already supported routers are still anything they are being tested they should be provided they should be supported I don't want to state that really but critical one other feature which is it's probably not not related to the Oven stack network in API our Oven external Oven networks can be connected to to the legacy to the network so you could have a bridge between you can specify a bridge between Oven network and our network any other questions the question is is it possible to use Oven SDV app as a standalone application I don't know by Oven SDV app you mean the Oven stack Oven SDV app right Oven SDV app it's actually it's not a product it's a library that allows people access Oven SDV you have to actually what you have to give it to Oven SDV app is the host of the Oven SDV the talk and passing the type of connection it's an accessibility another key that you need for the SSL connection with this configuration you can use Oven SDV app and you are ready to go with Oven SDV app if you have any further questions I'll be available here for the next half an hour or so and later on I will be at the Oven boost and do it okay Oven thank you


Hello everyone and welcome to Blackstar Potential. My name is Lee Fuge and I'm here today with MusicTeacher.com and in this video we're going to learn another riff that you guys have requested in the YouTube comments. This is the classic riff for the intro for the Joan Jett track, I Love Rock'n'Roll. All the tones you're hearing in this video are coming from the Blackstar HT20 Mark II which is currently set to the overdrive channel and I'm using my Shurgold Provocateur for this with the bridge humbucker engaged. So here's the riff in full and then we'll break it down. So for the most part this is a pretty straightforward power chord riff using the E5 power chord, the A5 and the B5. So those are the only three chords I'm actually using for the entire riff. But there is a weird bar towards the end of this where it just shifts into 3, 4 for a bar before going back to 4, 4. So there is some little timing things there to watch out for. So the first bar of this riff is based around the E5 power chord. I'm doing a double hit of the chord on the one end and the three end. On the fourth beat I'm doing a muted hit so you can do this on one string or you can mute all the strings whatever's more comfortable. And then I'm hitting the third fret of the low E giving that a quarter tone bend. Now the timing of this is I'm actually doing a sixteenth note on the mute so that's four and then I'm hitting the bend on the E so if I'm counting sixteenth notes four E and a, so it's four E. So it's got a slightly rushed feel.  The second bar is the same rhythm except this time I'm doing the A5 on the one and the B5 on the three beat. And that mute and bend are all so there so here's the first two bars. The third bar is exactly the same as the first bar so back to that E5. So the fourth bar is where the bar of three four comes in so instead of counting four beats I'm just counting three. On the one beat I'm playing the A5 twice and on the third beat I'm playing the B5 and the A5 so three and so it's one and on the A, three and on the B to A. As soon as you go from that B to A you're going straight back to two hits on the E5 which again now falls on the one beat and then you rest for the rest of the next bar. So that comes in on the one and then you've got a three beat pause. So here's the riff up to that point. After that three beat rest we then hit the E5 chord on the one beat again but then we've got a lead lick to end the riff. So the E5 falls on the one end again but then I'm coming up then to the first position of the E-minder pentatonic scale and I'm playing a bend on the 15th fret of the B so I'm going up a full tone and releasing it and as I release it I'm pulling off to the 12 then I'm playing 14 and 12 on the G. So here's that riff in full played slowly and once again at full. So there you go there is the intro riff for the Joan Jett track I Love Rock and Roll. Don't forget to let us know down below in the comments what other riffs you'd like to see us break down in future videos. There are a bunch of other riffs and other lesson videos over on the Blackstar YouTube channel so go check those out as well and if you're looking for a guitar teacher in your area please check out MusicTeacher.com there's a great network of teachers all around the country waiting to help you guys out. Thanks so much for watching and I'll see you soon.


All these effects were known before Albert Einstein's theory of relativity was published, and he was familiar with them. The thinking by 1905 was that there is still an ether that represented nature's absolute reference frame, but the timed dilation and space contraction made it impossible to detect. The ether was held to exist for two main reasons. One, it gave light a medium to propagate through, and two, it provided for an absolute frame of reference like the one we used to have with the Earth. With it we could claim that there is such a thing as simultaneous events in two places in at least one preferred by nature reference frame. Einstein parted with this theory for two reasons. One was that he studied James Maxwell's equations that showed the speed of light was the result of empty space's resistance to the formation of an electric field, permittivity, and a magnetic field, permeability, as we covered in the microscopic segment of our How Small Is It video book. So there was no need for a propagating medium like the ether. Empty space will do just fine. Then relative motion would not change these basic properties of empty space, thus making the speed of light the same for all observers. The other reason was more philosophical. What does it mean to postulate the existence of a thing and then explain that it cannot be detected? In the end he accepted the idea that there is no universal frame of reference and all time, space, and simultaneity were relative for all inertial frames. In Einstein's paper he articulated two postulates. One, the laws of physics are the same in all inertial reference frames. This means that formulas like force equals mass times acceleration will hold in all inertial reference frames, and all experiments run the same in all inertial reference frames. For example, if you drop a ball standing at home, it falls straight down to your feet. The same thing happens if you are standing on a moving train. The ball falls straight down to your feet. Postulate number two is that the speed of light in a vacuum has the same value in all inertial reference frames. With these two postulates, Einstein generated all the relativity equations of Lorentz and others. It was his study of relativistic mass, momentum, and energy that led Einstein to the famous equation E equals MC squared. No one else had made this relationship between mass and energy. Today's nuclear power industry is a testament to the accuracy of this special relativity formula.