Welcome back to another one. If you are new to the channel, I'm Gold Pony. I do new car truck SUV reviews on YouTube. And today we are in the extremely fun 2020 Hyundai Vlaster N, courtesy of Jack Giumble of Hyundai in York PA. For more information on their inventory, please feel free to check out the link in the description box below. And so some of you may already know as of February 2020, Hyundai is now offering three years of complimentary maintenance to go along with the very best warranty that America currently offers, being five-year, 60,000 mile bumper to bumper, 10-year, 100,000 mile powertrain, which is excellent when you consider cars like this, cars that are extremely fun to drive being warrantied for that long. And so if you were comparing them, though, the Vlaster N is actually $10,000 less than the Civic Type-R and has around 47 more horse power than the Golf GTI. All of these reasons made me definitely want to check out this thing once again. So what do you guys say? Let's just go ahead and jump right into it. And as always, let's start with pricing. It's a MSRP for the 2020 Vlaster N. We'll start at $27,600. Do want to mention though, there is a performance package that we do actually happen to have today that actually then puts the starting price at $29,700. But regardless of which setup that you go with there, power plant is going to be the same. Powering this little beast is a 2.0-liter turbocharged inline 4-cylinder, putting out 250 horsepower at 6,000 RPM, 260 pound-feet of torque available at 1,400-ish RPM, power sent to the front wheels through a six-speed manual with rev matching. That is pretty cool. And although for 2020, there's no automatic or DSG available for 2021 coming soon, there will be a dual clutch transmission available. So if your heart was sent on a dual clutch, just wait a little bit longer and then it's going to be there for you basically. So then zero to 60 time comes in at approximately 5.5 seconds according to car and driver, quarter-mile time, 14.2 seconds, top speed, 155 miles per hour. That's pretty insane considering it's a hatchback. And FPG numbers 22 in the city, 29 highway taking regular unleaded fuel.  It's kind of cool. I emphasize that because of course the Honda Civic Type R takes premium fuel, so I always have to mention that. And so one other thing when it comes to that performance package that we have today that actually bumps the horsepower number up to 275 horsepower. So that is actually the one we have today. But now for anybody wondering what N actually is when it comes to the Veloster N, N actually stands for NAMYANG, which is the Research and Development Center in Korea for Hyundai, of course. So that is why you were going to begin seeing a slew of different N cars, NSUVs coming out from Hyundai in the near future besides just strictly the Veloster N that we have here today. Let's hope that then before we test out the acceleration on the Veloster N, I did want to mention there are some drive modes that do come standard on this one. All of those drive mode buttons are actually located on the steering wheel. There is a drive mode button to the left, and there is that checkered flagger N mode on the right side of the steering wheel. Of course, we'll put it in that a little bit later, but that is going to be how you're actually going to adjust those driving modes. What they're actually going to do is adjust things like the shift points, throttle response, steering sensitivity, the exhaust sound, and the suspension settings. So quite a bit actually being adjusted by those driving modes. I like that, especially the exhaust sound. We'll get to that exhaust later in the video, but also with that N mode button though, you can also create your own customized mode where you can adjust the settings or just about everything up on that infotainment screen. So you got that too if you wanted to. But so now having mentioned all of that, what do you guys say? Let's go ahead and get back on the highway here. Let's do a quick little acceleration. Nothing too crazy, but just kind of want to feel out how this thing shifts once again. I remember reviewing this car last year. That's why I put it that way, but want to feel out how it shifts the grab points, all that fun stuff. We'll do a quick little acceleration here. Let's see how quickly we can get the new 2020 Blaster N here up to speed. All right, let's get on the highway here. Got a little bit of a rolling start. Here we go. No loss of grip. Okay, there actually wasn't all that much torque steer.  But really, with the Blaster N there, that wasn't that bad. There was an ever so slight bit, but really nothing that would bother me on a day-to-day basis. That was a good bit of pull. That was actually quite fun. I'm digging that. And actually, I wasn't even in N mode. Silly me. I should have done that, but still a ton of fun even without being in the fun driving middle. Let's go ahead and switch that up. There we go. Oh, wow, that exhaust note. Okay, I'm looking forward to that. But anyways, to go along with that acceleration, as always, braking is equally important. So, up front you will find 13-inch ventilated front discs. In the back, 11.8-inch solid rear discs. And actually, with that performance package, those rotors are upsized quite a bit. So, up front with the performance pack that we have today, 13.6-inch ventilated front discs and 12.4-inch solid rear discs. As far as the braking feel goes, it's been excellent. Certainly no issues with any brake pedal delay or anything like that. Did what I also mention again with that performance package, you actually get red brake calipers with the N logo on the front. That is pretty darn cold. But overall, braking feel is perfectly fine though.  And if you were to go with the performance pack that we have here today, once again, you will get a limited slip differential as well. That is pretty darn cool. Sending torque to the wheel with the most traction. That's always a plus as well, especially in a performance car like this. So, anyways, as far as the steering feel goes, since I put it in that end mode now, it is much weightier. I am a fan. I should have put it in that from the start. I do apologize. But definitely a very heavier weighted steering feel. I can hear the crack already. I love this. But definitely a nice weighted steering wheel, especially in that end mode. And again, those steering modes do adjust. So if you wanted the looser steering feel, that is going to be available for you ultimately. As far as ride quality goes, I would say it's pretty much as expected for a car like the Vloster. And it's certainly not the smoothest ride in the world. But I wouldn't expect that out of this car, honestly. It's kind of close to my Mustang GT, basically. It kind of feels like that. So you can feel a lot of the road. But honestly, again, that's a good thing for a car like this. You're kind of better connected to the road. So you're going to feel a bit more, that's expected. As far as cabin noise goes, all I continue to hear if I downshift, we'll do that. Crackle all day long, man. Absolutely love that. When you put it in the end mode, the exhaust clip is absolutely amazing. So anyways, when it comes to cabin noise, not a whole lot of exterior noises coming into the cabin minus the exhaust, which is absolutely beautiful. But touching on visibility, I actually can see decently good out the back. I will say with the sloped roof line, it's not the best. It's not going to be the best visibility out there. But you know what? It's manageable. I certainly wouldn't have any issues driving this on a day-to-day basis with that visibility. So no issues for me. But that about rounds out the performance segment of this review, you guys. Let's now go ahead and take a look at the exterior of this beautiful performance blue 2020 Hyundai Vlaster N. All right. So here she is, you guys, the beautiful 2020 Hyundai Vlaster N. Love the look of this thing. I don't know why. Anyways, as far as the colors go, there's actually only four of them, so I'm going to list them off real quick. Chalk white, racing red, ultra black, and performance blue, which is kind of what the N brand is known for at this point. And that's what we have today. Of course, absolutely love it. But to the sides, go ahead and start up front. LED headlights do come standard with the automatic feature, meaning when it starts to get dark out at night, they do turn on automatically for you there. So that's always nice. LED daytime running lights also coming standard up there. That N-specific front fascia with the N logo found in the upper corner of the front grill there. Definitely looks good. And you got some red accenting along the side skirts and the front there as well. So and the red accenting is there. It goes along with the N colors as well, the black and red and the N logo. So it definitely looks good overall and definitely gives it more of a unique look, making it know that this thing's got a little extra power compared to the other cars out there. All right. So making our way to the side now, here's the fun part about the Vlaster. Get ready. There is one door. You guys can see that there is clearly one door on the driver's side. But if we switch around here, there are actually two doors on the passenger side. Love that about this car. It's so quirky. So you got two doors on the passenger side. If you ever have rear passengers, that's the side they're going to want to enter on. One door on the driver's side. I don't know why. That's so cool. Take a look at the side mirrors. They are gloss black power adjustable heated side mirrors with integrated turd signals. And you do have some gloss black side skirts to go along with their side mirrors as well. With the red accenting to tie in with the front, of course. Take a look at the wheels and tires. 18 inch alloy wheels do come standard. However, with the performance pack, those are upsized to 19 inch alloy wheels wrapped in Pirelli P0 summer tires. Perfect fitment for this nice almost summer day. We're at the tail end of spring here. But now let's go ahead and make our way to the back of the end here. Of course, you have that performance blue shark fin antenna up top. Just below that, a very menacing gloss black rear spoiler with an integrated brake light in a triangular form there. Just below that rear window wiper. Of course, you have some end badging on the rear hatch as well. Actually, LED tail lights do come standard on the Vlaster end here. So, got them as well. And there's actually, let me show you guys, you guys can probably see that there's actually Vlaster etched into the tail lights as well. I love that little cue there.  So I told you guys before we'd be doing a exhaust clip. Get ready. Here it is. Variable valve exhaust system coming only with the performance pack. So that is why you're definitely going to want to get the performance pack, not just for the increase of power, but for this amazing exhaust systems. One of those exhaust systems where you almost don't even need an aftermarket system for it because it sounds so freakishly good without it. So enough talking. As always, here is that exhaust clip. It's been now since we are around back of the Vlaster and there are a couple different ways to go ahead and open that rear hatch. One of them is there is a button on the key fob itself. The cooler way there is a button kind of incorporated into that rear window wiper. It's kind of hidden and it's just underneath of it. So that's probably the way I would use. It's kind of cool. But once opened up, cargo capacity is going to come in at 19.9 cubic feet. If that was not enough space, there is a 6040 split, meaning the rear seats do fold down, bumping that up to 44.5 cubic feet. So a decent amount of space back there for what it is. Making our way to the rear leg room that is going to come in at 34.1 inches. So for reference, I'm an even six feet tall. This is how much space I had in the back there. There is also a center tray storage area for those of your passengers. There are dual cupholders back there. And again, the passengers are supposed to enter through the passenger side, although they could enter through the driver's side. It's just easier with the passenger side. But anyways, making our way to the front seats and specific claw seats with performance blue stitching and perhaps my favorite part about the interior, performance blue seat belts. Love that. How many manufacturers actually put a color to their seat belts? Almost nobody does anymore. But I love that Hyundai did that in this one. N logo at the very top of that seating, of course. And they are six-way manually adjustable front seats, and they are actually plenty comfortable. And they are bolstered better than I thought they would be for the performance that this car actually comes with. They're not going to be bolstered as well as the Civic Type R, but they definitely have some good bolstering to them. I will say that. Let's take a look at the steering wheel. This tilt and telescoping is wrapped in a perforated leather. And of course, you do have that N logo at the bottom of it as well. And again, the drive mode buttons can be found on that steering wheel. And I love how they're finished in performance blue to match the exterior of this one. That is so cool. But anyways, making our way to the startup, let me start by showing you guys the key here. You do have that N specific key with your N logo on the one side, all of your buttons on the other, including lock on lock, panic button, that button to pop the rear hatch. But it is all keyless entry. So simply just leave the key in your pocket, walk up to the blaster end here, put your foot on the brake and clutch, and press that engine start button, which is located just by the driver's right knee there. And so, but then once started up N specific gauges, once again, tachometer with the N logo is on your left speedometer is on your right. There is a small digital display front and center, which can be controlled by using the steering wheel mounted controls on the right side of the steering wheel there. Through that, you have a ton of different information, including a lap timer. There is G for statistics. There's also a digital speedometer. If you wanted to display that up there, of course, there's your tire pressure when you need your next oil change. And it is, of course, going to show you your drive modes being displayed up there as well. So all of that is super nice. But making our way now to overall interior quality, you do have alloy foot pedals. It's probably the first thing I noticed when I first got in this one. Love that blue stitching throughout also nice thing as the exterior of this one is that performance blue color. Also blue accents on the shifter itself in the front and the back. And I like the shifter itself. Actually, some shifters aren't the best, like one that comes to mind is the Kia Forte GT. That one kind of feels like an automatic. It's really weird, but I like how this is more of a cue ball type shifter. So I do appreciate that. Also have an overhead sunglass holder found on the roof here. And as far as the rest of it, it's essentially got your basics other than that. Just in front of the shifter, you have a good bit of storage actually with the rubberized bottom there, 12 volt power outlet, USB charging port times to auxiliary port as well up there. Just behind the shifter, you have dual cup holders. And of course, you got a little bit more storage within the center armrest there as well. So overall, the interior quality, it doesn't blow me away, but the performance does. So that kind of makes up for it. But anyways, let's go ahead and make our way now to the tech display front and center. 8 inch color touch screen display coming standard on this one. Bluetooth and audio streaming as well as Android Auto Apple CarPlay. Also standard, meaning if you have a smartphone, simply hook it up to the end. Therefore, you have free navigation display up on that tech display as well as the ability to like and dislike your Pandora songs. Of course, you can also check out your driving statistics up there as well. And of course, you have your end mode statistics up there as well. I love that. There's a performance timer, G4 statistics, all of that being displayed up there. So that's pretty cool. You can also check out of course, your radio information. By the way, when it comes to the sound system, the standard sound system on this one is an infinity 8 speaker sound system with an external amp and subwoofer. So I do believe you guys know what we have to do next. As always, let's go ahead and turn on the radio. See what we got playing today and let's test out the clarity of this one. Definitely feel that there's a subwoofer without a doubt that was a ton of bass. Clarity is definitely plenty good as well. So really for what this car is, that sound system is perfectly fine.  But last thing I wanted to mention to you guys on the tech display is when you do put the Veloster in reverse and to put this one in reverse, let me show you guys that real quick. Simply lift up underneath the the shift or slide it into the upper left hand corner. When you do that, you will find a rear view camera letting you know who or what is behind you, which is always is going to lead us into safety. Let's start front side and side curtain airbags do come standard. In the back, you're going to have latch, aka lower anchors and tethers to children for the rear car seats, rear child door locks back there, tire pressure monitoring system and a driver's blind spot mirror as well. And so overall, when it comes to my final thoughts of this 2020 Veloster and love the performance blue color on this thing, it's really what the end brand has come to be known for. So love that love that the blue seatbelts tie in with I almost never see colored seatbelts, like I was saying, the power on this is absolutely amazing, plenty of power to have fun in this thing. Six speed manual is excellent. I will say that as well. And so I learned how to drive manual and a Honda s 2000. So I'm used to a lot of Honda manuals, although I've driven basically all of them at this point, but this is definitely closer to a Honda manual. So it's very easy to find the graph points, very nice clutch feel of the rev matching. It definitely makes me feel like I'm a professional driver in this thing. Definitely a very fun car to drive. Perhaps my only constructive criticism now that they're having the dual clutch, I think that's definitely going to increase their sales for this one. Although I think I probably would go with the six speed manual. It's not much fun. But my only constructive criticism is I wish they would have put an all wheel drive system in this thing, make it like a rally car to compete with cars like the Subaru WRX, even as an added option. I would absolutely love that in the Vlaster. And if you made it all wheel drive, it would be seriously difficult for me not to consider getting this thing. So anyways, especially living in Pennsylvania, that is about it for this one. You guys, thank you so much for watching. Feel free to follow me on social media at the bottom of the screen there. If you like, be sure to hit the subscribe and the bell notification button. If you're in a new car reviews, that is what we do here on this channel. After all, do appreciate you guys watching more than you know. And I will see you guys all in the next video. Stay gold. Dang, this car is fun, man.


Hey everyone, I have to be on camera a little bit for this one because I'm pretty excited and it's a little bit of a different video. Now we're talking about the 35th anniversary of Mario. Also the supposed Super Mario 3D world deluxe game and a potential Nintendo event or Direct next week. Building off of our video from yesterday about a massive Nintendo Direct coming next week that came from a reliable source, you want to hear about that thing, click up here or up here wherever it is on that little card that pops up and you can check that one out. I'll even put a link to that video down in the description as well and maybe even in a pinned comment for those that want to read more about it. Also we just did a video about Breath of the Wild 2 and how it might be coming out sooner than we think whether it's this holiday or early next year. Again, link up here again or down in the description or in the pinned comment for that video too. But let's get into this. By starting with our giveaway for this month. We are giving away a copy of Final Fantasy Crystal Chronicles Remastered Edition. All you have to do to enter is comment down below, like this video, subscribe to the channel and hit that bell icon. Yeah, that's all you gotta do. You can get the PlayStation 4 or Switch version. Winner will be announced at the end of the month.  We are on our road to 50,000 subscribers and if we hit 50,000 subscribers before November 1st of 2020, we will give away in the month of November an Xbox Series X, a Nintendo Switch or a PlayStation 5. It will be up to the winner of course. If we hit 50,000 subscribers some point after November 1st, we'll still do a bigger giveaway. Maybe multiple games, 3-4 games or something, but we won't be doing a big console giveaway unless we happen to hit it in that lead up that hype launch for those new next-gen systems. If you just happen to want to switch instead, they'll sweat off my back and it'll probably be a lot easier to get you one of those. Anyways, that being said, let's get into the Mario stuff. This has been rumored forever, right? I think March was the first time something popped up about a potential Mario 3D collection and all that jazz, but what's been interesting is I watch spawn waves videos. I don't watch them all the time because I don't want to feel like I'm getting all my information from one source. He doesn't appear to be the direct source of this either, but he's hearing from other people like Direct Beat Games, which his name is also ironically Nate. My name is Nate, his name is Nate, and he's been really, really good with insider information over the years, even though his YouTube channel obviously focuses on direct gameplay feed of games. But he said this last Friday, he kind of slipped it in at the end of the end of the week news wave. Check it out. Mario 3D collection, expect that in like a week or two. I mean, that's going to get announced and it'll probably come out sooner than people are realizing. So keep that in mind. It's just these are rumors and, you know, people want there to be a Mario 3D collection. They want a Metroid Prime trilogy because those sound like awesome collections of games and when they're not there immediately, they obviously start to get some doubt, frustration, all that kind of piles up. But the good news is look forward to the 3D collection pretty soon, like I said, and here's hoping Metroid Prime trilogy isn't too far off, but as of now, it's still a rumor. Hopefully not like the Grinch leak. So correct me if I'm wrong here. John, that's the spawn wave's name. John, he seems pretty confident here about that direct next week and about the 35th anniversary 3D pack, collection pack, whatever it is getting announced next week, doesn't he? Oh, and by the way, he just said this, well, I don't know, today. We're going to start right away with Nintendo's announcements that seem to be coming up. See, if you've been listening to the spawncast or any of that podcast, of course we do, or even on Nate's channel, you know that part of the plan was to have an indie showcase first and then a direct second. The idea now is that this week will be the indie showcase. I saw a lot of people in the comments for it or responses on Twitter, for example, or on YouTube commenting on it. They weren't happy, of course, because this is an indie showcase and it's not a big direct to announce games. That is coming at least, it seems, okay? So the idea indie showcase this week, a little patience next week. Maybe we'll see a direct possibly, because there are some things that need to be announced specifically. And I know, again, I see it, the Mario 3D collection. That's what we're calling it right now, tentatively. I'm sure the real title will be something crazy. Maybe they'll even throw a U in there.  Anyway, it does seem that Nintendo continues to double down on the Mario themed accessories. And of course we've seen all of the collaborations. It's Mario's 35th anniversary. So of course we expect these kinds of things, but the games will come soon, okay? Expect 3D world deluxe, that's showing up at some point. And then expect the 3D collection, most likely in some sort of event I'm going to stick with because who knows with Nintendo and these directs anymore next week. Also check this out. These popped up on Amazon with a starting release date of September 1st. You can see two different ones here. Which includes the Hori mini pad, that's the Super Mario edition, which the sticks themselves look, I guess like full analog sticks, similar to what's on the pro controller with the little D pad there, ABXY. For the most part, it's just a Mario themed wired controller from Hori. Keep in mind though, that is coming out September 1st at $25. And then just a few days later, September 4th, the PowerA enhanced wired Golden M controller at $25 is also releasing. Now the interesting thing here, obviously the controllers seem to be timed at a release point that would seem like there's going to be some Mario game announcements coming next week. And while he's not willing to call it a direct because this is Nintendo, it could do something crazy, it could just be a special 35th anniversary celebration of Mario and then it's just like, a half hour of Mario goodness or whatever they decided to show. He's very confident it's coming next week. So this is why we're going to kind of talk about it because I think it's interesting that someone who, a YouTuber who has a reputation much grander than my own is not necessarily making himself the source of this information, but he's sort of throwing his weight behind the idea that the people he talks to, the people that he has on spawncast are correct that we're getting a Nintendo Direct or something like that next week and we're going to get a bunch of Mario goodness very, very soon. Now, he does seem to be pegging a Super Mario 3D world if you dig through some other content and some of his Twitter account. He seems to be pegging that more for like a December or January release, which makes a lot more sense. Even though this is the 35th anniversary to kick off next year with a Mario game like they did with New Super Mario Brothers U Deluxe, that would make a lot of sense. But yeah, it's very, very interesting. Obviously, he kind of hints also that the game might be coming, this 35th anniversary collection pack that supposedly exists the one with Super Mario 64, Sunshine, Galaxy One, Galaxy Two, all in HD remastered.  They've done like collection packs before, that's not unheard of, but games of this caliber, they usually remaster and sell us 60 bucks a pop. Gotta wonder, what if this would be like a $100 collection pack? I don't know, but they've also done Super Mario All-Stars, so I have no idea. But I will say that he seems very confident that we are going to be getting these games sooner rather than later, as in potentially before Pikmin 3 Deluxe, which comes out in October. So are we talking about a September release? Is Nintendo just been holding the cards close to the event the best and dropping this game for next month? That would be very, very interesting of Nintendo to wait this long to announce something that is going to sell five, 10 plus million copies easily. And then obviously that leaves us up to debate if this isn't the big game for the holidays, because some people might have presumed, hey, the 35th anniversary games, that collection packs, clearly gonna be the holiday push for Nintendo.   I don't know. Or is that the Breath of the Wild game? Are they gonna sneak that out this holiday? Breath of the Wild 2? Even though like, Zelda's 35th is next year, so wouldn't it make sense for next year? But then if they need something for this holiday and the game's already ready to go, I don't know, this is getting kind of crazy. And we have all this crazy stuff going on. And yeah, I'm just left here with my mind spinning in circles and circles and circles and circles, trying to sort through all of this stuff. There are so many credible people pointing at this 35th anniversary, pointing at next week's Direct. If they sneak this Direct out and Spawnwave said it himself, if they sneak this Direct out next week, it will be just under a year that they were since their last full Direct. And this is even if it's called, what if it's just Nintendo Direct Mario Edition? And then does that really count as a full Direct? If it's just all about Mario? Won't that just be a Mario Direct? I don't know. But a lot of people, a lot of people, not just him, are hinting that, hey, this indie world thing we just had today, that was the first thing coming in August from Nintendo. There's much more. So hold on to your butt cheeks because next week is sounding like the week to pay attention to Nintendo, especially if you are a Mario fan of any of the games that we've grown up with, basically. So let me know what you think about this down in the comments below. Do you think John and Spawnwave is overhyping this?  After all, we had that really credible thing about a Direct next week, credible stuff about Breath of the Wild 2 from a verified retailer that has leaked Switch games in the past, like Witcher 3. We have had people that are very trusted like Direct Feat Games at King's El and all this talk about the 35th anniversary edition.   And the funny thing is about the indie world is that Direct Feat Games, which is where Spawnwave gets a lot of this information from, told us, told everyone we would get an indie world this week and then Nintendo Direct next week. And he said this last week. I'm just saying, things are adding up. All right, folks. I am Nathan Roberts from Nintendo Prime, looking fly as hell over here. Thank you guys so much for tuning in. And yeah, I'm gonna catch you guys in the next video.


So my name is Michele Tartara. I'm a software engineer at Google, and I'm working in the GANETICore team, which is the team developing virtualization software that we call GANETIC. I will start with a short introduction to GANETICE itself, and then I will present some of the newest feature, which came out in the latest revision released last week. And finally, I will give a brief update on our participation in the Google Summer of Code program for the first time this year GANETICE participated in the Google Summer of Code as a mentoring organization. So traditional approach to installing a virtualization cluster.  We hit the one of your choice, sign KVM, LXC, if you are fine with just using Linux solutions, then you set up some storage or application mechanisms because you would like to be able to keep your VM running, even in case of some hardware failures in the hard drive source, and so on. Then you try and everything works, working nicely together, and then, well, stuff. Basically, all the usual configuration steps that you need, and then, finally, everything works, hopefully. This is a traditional approach, works perfectly fine, but it's also nice to simplify your own life. So you take a bunch of physical machines, install GANETICE, and basically, all the other steps comes for free because it is GANETICE doing the configuration of the RBDE and all that other stuff for you. So what does GANETICE actually do? What is GANETICE? GANETIC manages clusters of physical machines. It deploys some KVM, LXC virtual machines on them. Basically, you just have to start from a basic Linux system with the packages of your distro installed, and GANETICE will configure them for you. It allows you, for example, to do live migrations of virtual machines between the nodes of your cluster. It gives your resiliency to failure. So if you are using, for example, the RBDE, it can give you data redundancy. Or if not the RBDE, you can have some external storage that you tell GANETICE, OK, assume that this will be available on all your nodes, and everything will work perfectly fine. GANETICE can also automatically restart instances after power outages. There is a watcher that controls that if a machine was configured as up by the CIS admin and it is detected to be down, then it will be automatically restarted by the watcher.  So if something does not work, GANETICE will help you fix in that. It is open and is built on top of open source technologies. So Linux and all the standard utils, then, as I said, KVM, SAN, or LXC as the hypervisors, DRBD, LVM, or in general, any kind of storage area network is perfectly fine. And it's implemented in Python and Haskell. Traditionally, it was mostly Python. Now, Python is still the majority of the code base, but especially for all the internal demons, the ones that even in the worst case, the CIS admins will never really want to touch. All these parts are slowly migrating towards Haskell. Basically, and mainly for a reason of code cleanliness. With Python, it's too easy to modify something. OK, it seems to be working. Then you have your software in production and randomly runtime crash, which is terrible. And when you realize that most of those crashes, you can detect them at compile time. Why not? So a bit of core concepts that Gannety is based upon. Gannety interacts with the cluster as a single entity, instead of interacting with the single physical machines or even worse with the single virtual machines. Basically, all the commands that you give to Gannety, you give them on the master node, which is one node of your cluster that is selected as the manager. And then it will be up to the software to execute the command where it's actually needed. It makes the entry-level cluster with realization as easy as possible. Is it to install and manage, as I said before, and based on common of the shelf hardware? You don't need specialized hardware. Usually, it would be nice that all your nodes are equal, but it's not really required. You can have different nodes. It's perfectly fine. And Gannety is built to scale to enterprise ecosystems. So you can start with one node. OK, it's not a great virtualization cluster, but it's just one single machine. But you can scale up to hundreds of nodes, which are the configuration used inside Google. And you can have more than one feature. And then another core concept for Gannety is to be an open-source citizen and be a good open-source citizen. So all the design code discussions, it's all done on the public mailing list. You can follow completely the development from there. External contributions are more than welcome. And actually, we have a bunch of them, especially from JRNet, which is our biggest external contributor. And we have some guys from JRNet here. And they gave a talk yesterday about their CNAPO system. And as I said, JRNet is one of the big Gannety users. But in general, we try to have an active mailing list where the core team reply to the external users. And also, it's nice to see that it's an active community because the users are replying to each other without even our interventions sometimes. Just to give you an idea, Gannety is maybe not well known, but it's quite used and on quite big installations. So of course, Google is using Gannety internally for all of its virtualization requirements. And when I say this, I mean the internal ones. There is no user-facing service based on Gannety. So for example, Google Compute Engine is made on something else. Gannety is used for internal infrastructure. So for example, if somebody needs a virtual server for some development or something or a virtual abstraction, this is all managed with Gannety. Then we have JRNet. As I said, it's the Greek Research and Technology Network, which is running a really big, multiple Gannety clusters, actually. Then there is the Oregon State University open source lab, which if you look at the name might seem like some obscure laboratory of a university until you find out they are hosting a lot of machines of the Apache Software Foundation, the Python Software Foundation, a bunch of Debian machines, and so on. I didn't know this myself the first time I read the name, so impressive. And then there is, for example, Scouts, which is a company making a price comparison engine in Greece and the Free Software Foundation France on their website states that they are using Gannety. So a bit of terminology that I will be using in this presentation. In instance, when I say instance, I mean virtualization guest, EVM, no more than that. A node is a virtualization host, so the physical machine where you install something. We have the concept of node group, which is an homogeneous set of nodes, usually when you have an instance installed, and you have a primary and the secondary, which is ready to come back. These are inside the same node group, but the cluster can be composed of multiple node groups, which is a set of nodes, and it's all managed as a collective by Gannety itself. Every node, when it's used as part of a Gannety cluster, might have different roles. It might have different administrative roles, which is master, which is controlling the entire cluster.  So for example, if the master crashes or it has some problem, the administrator can go on the master candidates and say, failover the master here. That node will become the new master with all full power, and this is possible because master will always send a full copy of its configuration to the master candidates every time this is updated. But of course, not every node will be a master candidate, otherwise copying the configuration continuously everywhere would be terrible for scalability. But many nodes might be master capable. So they might be master, but currently they are not configured for that possibility. Then there is the regular nodes, which is all the other ones, and you can also have offline nodes, because of course, sometimes you have configured a node, but this went offline for any reason, and you know this happened, you don't want the cluster every time to go and ping that node to find out information. So you just say, okay, this is offline, don't even consider it for now, but don't remove it from the configuration. Then regarding the nodes that are actually able to host some VMs and are not just the master node, for example, they can be VM capable or non-BM capable, which means, for example, nodes containing only storage, but no actual hypervisors. So how can the user, the sysadmin, control GANETI?  The public interfaces are the command line interface, which is a bunch of commands named gnt-something. We have gnt cluster, gnt node, gnt network and so on, which is the usual way for this sysadmin to interact with GANETI. These commands of course require loop permission and are made to be scripting friendly. So they try to have a really regular output and take a really regular set of input. We try never to change this between one is and the other one unless it's really, really required. So it can be used for scripting. But of course, if you need to do proper scripting, there can be better way. And this better way is our remote API, which is a REST HTTP HTTPS API with authentication possibility of supporting multiple users, which can have read access or write access to the cluster. And this one is explicitly granted to be stable because it's meant for automation. On top of that, not directly provided by GANETI, but by external contributors, there are also graphical interfaces. Between these, it's nice to talk about the GANETI Web Manager, which is a really complete interface which includes permissions and quota management systems. It's the one developed by the open source lab at the Oregon State University. And with this one, users can be granted access to a cluster, multiple clusters, single virtual machines and so on. It's really complete, allows you to manage really everything. On the other hand, can be a little bit complicated. It's meant for sysadmins, mainly. So as you can see, this is just one of the screens, is that the dashboard, the overview, get a list of all the clusters you can manage with the summary of their version, allocated memory, allocated disks, how many nodes there are in the cluster and so on. How many get from machines. Another interface is the Cinefo interface, developed as part of Cinefo, which is the software developed by Garnet, which is an entire cloud layer developed on top of GANETI. GANETI is only a virtual isolation cluster management. There are cloud services, like the one made by Cinefo, built on top of GANETI. And as part of Cinefo, there is also a user interface, which is mainly meant for end users, because they are running a huge cluster for providing computation services to Greek universities. So they want to give this university and the users of the universities the possibility of starting their own virtual machines. So as you can see in this image, for example, the focus is on the single machine with a few data, only the important ones. So let's go a little bit more into the detail of GANETI. This is an overview of the GANETI infrastructure. As I said, you control GANETI either through command line interface tools, or through some client, which communicate with the remote API. Remote API is a demon, which is listening for the commands. Then we have the master demon, which runs only on the master node. And it's responsible for managing the configuration of the cluster, for managing the queue of all the jobs submitted by the system administrators, and for managing the locks, which control the proper execution of all these jobs. Then there is also ConfD, which is the configuration demon, which basically is another demon that gives access to the configuration, but it's meant to be read-only, and it's meant to be accessible even by other nodes of the cluster. ConfD is also meant to be robust, because there is one ConfD running not only on the master node, but also on all the master candidates. It has its own protocol, which is based on UDP. Basically, when you want to know something about the configuration of the cluster, you can ask all the master candidates or a subset of them, an information about the configuration of the cluster, and as long as at least one of the master candidates is still alive, you will get back this information. So it's something meant to be robust and be always available, even in the worst case of your cluster being seriously damaged. And then, of course, you have the node demon, which is running on the node capable, on the VM capable nodes, which is the one receiving commands from master D and actually executing them. So basically it's the one calling KVM, send whatever to do the actual stuff. How can you install virtual machines in GANETI? Basically, for every virtual machine, for every instance, as we call them, you need to have an operating system which is associated, because, for example, at some point, you might want to reinstall the instance and you want to reinstall it exactly in the same situation.  We have a create script, import, export, rename. So with these scripts, you can create your operating system. These scripts can just unpack some tar-compressed image. They might be running an entire external tool like the bootstrap for downloading and creating your operating system, whatever. It's scripts executed with root powers from the target node and that's it. For this reason, the images that you are installing need to be trusted. So GANETI, as I said, is meant for virtualization, is not meant for cloud services. So it's supposed that when you are installing an operating system, this is a system administrator who put the image of that operating system there. That's why right now we are using this approach. For example, the guys from GANET, which are running a cloud infrastructure, through these scripts, they do something which is more secure. Basically, the scripts are just running a virtual machine and inside that virtual machine, the actual process of creating and updating and personalizing the operating system takes place. So it's in a safe environment separated from the actual node of the cluster.  We have defined an API for these scripts. So these scripts will receive a bunch of information from GANETI and therefore many people implemented different installation scripts. The bootstrap is the reference one. It can install every operating system that the bootstrap provides you and it's the one we develop. Then there is GANETI instance image, which is based on creating operating systems from already existing images. Cinefo image provides an encapsulated environment for the installation. GANETI OS depth is one of the oldest one. Actually, I'm not even really sure that it's any more compatible with nowadays GANETI. Basically, it was used for installing a VM starting from some ISO image of some CD-ROM and then you would manually install it. So this was a little bit of overview about what GANETI is and what GANETI can do. GANETI is quite an old project. Sometimes we get asked why did Google decide to develop GANETI and not using OpenStack? Well, because when Google started developing GANETI, OpenStack was still really, really far away in the future to come. So it was not existing. But of course, the fact that it exists since a long time also means that we keep implementing new features. And now I'm going to present some of these new features released in GANETI 2.8, which came out last week. One of these is the monitoring daemon. So the idea of the monitoring daemon is to provide information about the cluster state and about the cluster health. So this information can be computed automatically by the daemon itself. And it will be able, for example, to tell you whether some instance is running correctly and it will export it in an easily parseable format. Because the idea is to have this information live or it only, but we don't want to write a general-purpose monitoring system. We don't want to compete with Nagios or a pacemaker or whatever else. We just want to integrate with them. We want our daemon to provide these systems with easily parseable information. But this information will be about the internal part of GANETI itself. So something that Nagios or pacemaker wouldn't really be able to find out because it would need to take a lot of information about the cluster and finding out what this information actually means. We provide this thing already. How is it implemented? Well, basically, it's an HTTP daemon. It also has a REST-like API. Actually, it's less than REST-like. It's meant just for giving information, not for modifying the state of the cluster. So it's actually just getRequest. Provides replies in JSON format. Why JSON? Because it's easy. You can parse it with every language. And because it's already used inside the rest of GANETI basically everywhere, so we didn't really want to add more libraries for parsing some sort of serialization language for no reason. Another potentially interesting thing is that it's optional. So if you want it, you have it. Otherwise, it's no additional security risk as posed on the network. It's just don't even configure it and it will not run. It's also implemented in Haskell based on the SNAP library if you are interested. And it's dependent on ConfD. ConfD is the configuration daemon, which I described before in the overview of the system. And it's also not required. So if you want, you can just compile everything without ConfD, without the monitoring daemon, and the core of GANETI will keep working. So where is the monitoring daemon inside a GANETI itself? It's running on every node. Before I described the architecture, master daemon is running only on master, not daemon is running only on the VM capable. Why monitoring daemon is running everywhere? Because we wanted to provide information about all the cluster. Clearly, it will not provide the same information on all nodes. It will provide the information about the daemons that are running there. It will, for example, not provide information about the hypervisor. If it's a non-VM capable node, it will only provide information about the storage, in this case, and so on. But we want it to be everywhere, and we want it to be as stable and as always running as possible so that you can actually use it to find out what is going wrong when your cluster is not behaving correctly. Oh, by the way, if you have questions at any time, you just ask. Feel free to stop me. So what information does the monitoring daemon provide? There is a bunch of information. Currently, it's providing information about the status of the instances. For now, only for Xen instances, just because we didn't yet have time to implement the KDN version and the LXC1. It's providing information about the status of the disks, specifically taken from the PROC disk stats. It's providing information about the LVM logical volumes, which are used in the system. It's providing information about the status of the RBD, and it's providing information about the average load of the CPU on the various nodes. Soon enough, we are planning to implement the instance status also for KDN. We want to provide information about all the demos that are part of GANET itself and that are running on the nodes. We want to provide information about the resources that are available inside the app provider and the resources which are available on the physical node. So, if you noticed in the previous slide, sometimes I was saying that some data collector was providing status information. Sometimes I didn't say this. This is actually a really specific difference inside the monitoring demo because we have two possible kinds of data collectors. One is the performance reporting data collectors, which means they only provide data as is. They take the information somewhere, they provide it to you in a nicely formatted format, and that's it. There is no interpretation. But then we also have the status reporting data collectors, which are the ones where GANET is actually able to infer something from the data it has, and it will provide you this information in that specific information about whether GANET considers that node or that resource in general to be healthy, to be not really healthy, but GANET knows how it can fix it. And so it's working on a fix. So just in case I'm fixing it, please don't touch it. I know it's wrong. Don't do anything. I'm taking care of that. Unknown, of course, can happen that GANET is not able to say anything. So it's worse than being broken but out of fix and not as bad as being broken, which is the other possible state. What is the format of the replies provided by the monitoring agent? As I said, it's JSON. It's basically a list of all the collectors that you ask the monitoring agent to run, and every collector then provide its own report. But we didn't want just to provide a bunch of JSON data. We also wanted this JSON data to make sense, in a way, and to be a bit more structured. So each of these reports actually has a common format which is well-defined.  Specifically, this is the format of the report. Contains, of course, the name of the collector itself. Contains the version number of the collector and the version of the format. We decided to have these two specific things because with the format version, you know if you need a new parser for the same data, but maybe that the format was maintained but the collector was updated and now provides better information, more accurate. Then we have a timestamp, which, as you can see, is in nanoseconds just because for some things you might really want to have the detail. But of course, many collectors are not that precise so they will just pad the number with zeros. Then you have a category. The category is really important and I will explain more about that later because it allows you to say what is the actual data of the collector. Kind is just status reporting or performance reporting, as I described before. Data is theoretically free format. Every data collector is able to provide its own information in there but even here we didn't really want to give complete randomness. So we introduced the concept of category. Some data collectors can belong to a category and in that case, the category will say, okay, this collector will provide at the very least this set of information so you know what fields you will find in here. Then the specific collector maybe will provide more information but a basic set is sure to be there. Regarding the kind of data collector, if it's performance or status, of course if it's performance, it's just data. So it can be whatever. If it's a status data collector, we want to have a specific way that you can go and find out whether the system is healthy or not. Which means that inside the data section, you will surely find the status variable which will be made of two components. One is the code, which will immediately tell you if the system is working as intended, if it's being auto-repaired, if it's in an unknown and therefore potentially dangerous state to get ready your pagers or if there are really problems and so the CIS admin has to do something manually. And then of course there is also a message where the data collector can provide a more specific description. So okay, if everything is working as intended, this message will be optional, but if there is a problem, the data collector is supposed to write what the problem was. So you can see this as a summary of every other information in the data field. If you have a status data collector, just go and look at the status field. If everything is okay, ignore all the rest. You won't probably care. If there is a problem, well, the rest of the data will help you understand even more what the problem is, but you just need to read this one to know that, okay, it's a bad time, something wrong is going on. A bit more goodies. There is actually not only the monitoring demon itself. There is also this tool, which we call MonCollector, which is a common line tool, really simple. It contains the same collectors and provides the output in the same format, but instead of being listening on a network connection on HTTP, this one runs locally, provides output on the standard output, and why? Basically, this is either for quick checks done by the system administrators, or it's for some local scripting, if you really want to script this information without passing to an HTTP interface, and especially for another reason, because it shares exactly the same code, so it provides the same data in the same format, but it's a physically different executable. So if something is, again, really wrong with your cluster, we want to give you another way to find out what's happening. This is self-contained executable with all the things that are needed to run immediately the collectors. So even if the demon is not running because it failed or is not accessible over the network or whatever, you always have another way to try and find out something about your system. By the way, how many of you didn't know something about GANETI before? Okay, how many have actually tried it? Okay, at least somebody, which is not bad. Yes, there was a question. The question about this, is this only for stuff that's in context on the node that you run it on, or is it C to whole cluster? No, so something that I did not specify before. The monitoring demon only provides information related to the node it's running on. So if you want to have information about all the cluster, currently you have to query all the nodes, and it's meant this way. Theoretically, we might want some data to implement some master monitoring demon, but it's not there. Right now it's one node, one demon, and one collector is the same. It runs only locally. It might happen though that one collector to provide more complete information, we'll have to call confd to ask some information about the cluster configuration, and of course, if the cluster is badly damaged, that won't work. But in general, all the implementation is made in such a way that if some information that should come from the net, or from running some local command is not available, it will still leave that field empty, but try to output as much as possible. They say it's made in such a way that it tries actively hard not to crash. It will provide some information. Maybe it's not so complete as you would like, but whatever. It means that your cluster needs some love at the time. So what is where exactly? The Gannetti development especially since October November last year has been switching to a quarterly release schedule. So of course, the implementation of all of this is happening over a bunch of releases. Specifically, Mon Collector and the DRBD Data Collector, which was the first one to be written where it is in Gannetti 2.7. The monitoring demon itself is in Gannetti 2.8, which came out last week. 2.9, which is currently in RC, if I recall correctly, is going to provide more data collector. So specifically the one for logical volumes, the one, the instance status collector for XEN, and the one for information from PROC disk stats. And the CPU load collector will be in Gannetti 2.10. As I promised, more information. Yeah. So here in this, when you talk about information, it's about, what is that? Sorry, as well? Information is about load. It's not about instance. It depends. Actually, it's about all the instances in one node, for example. If you run the instance status collector, it will provide you information about all the instances, the old XEN instances that are running on that node. So actually it's about informations that are available in a node or related to a node, but they can be at different levels. Also, if you look at the data collectors regarding hard drives in some way or storage, we have something which is quite low level. Disk stats is how the hardware is behaving. We have logical volumes, a bit higher. We have DRBD, even a bit higher. And if you take into account these three together, they are made in such a way that each one of them is providing you some information that you can use as a foreign key with respect to the data provided by the other one, so that you can, for example, say, okay, I have a problem in the DRBD volume in some instance, because this one will also tell you, okay, let's say from another point of view. I have a problem in one instance. I see that it's a problem related to the disks. Disk collector will tell you this instance is running over this DRBD minor. From that DRBD minor, you know on what logical volume it is. From that logical volume, you know on what physical drive it is, and you can go from the instance to the lowest possible level following this change. So it's trying to provide you as many information as possible that can be used by an external tool to take decisions to find out what's wrong about the cluster. So categories. As I said, there is a bunch of categories that are usually defining a minimal set of information that every collector has to provide. We have the storage category, which is for the collectors, which I just listed, which indicates that those collectors will gait our data about the storage subsystem, that will provide information about different granularity levels, about physical disks, partitions, logical volumes, and so on. And that is always possible to trace back to the instance. So the storage collectors are built for this reason. But they don't actually provide any common field. It's just, okay, this will be about storage, and you will also always be able to go along the entire chain from the instance to the level you are interested to. Then we have the hypervisor category, which is actually the less defined category right now because there is no data collector yet, which will be about hypervisors. As I said, we mean to implement some data collectors will provide information about what the free or use memory in one node is, about the number of CPUs available, CPU average load. For sure it will be performance reporting collector, but everything else for the hypervisor is still a bit undefined. Then there is the demon category, which tells you that we will provide information about the memory, which is used by a specific demon. At the time of the demon, we want to know if maybe the demon, okay, now it's running, but actually just crashed yesterday and you didn't even realize. At time. The amount of CPU that that specific demon is using, maybe it's still running, but it's using 100% of the CPU because something is wrong somewhere. We want to know. And of course, with this information plus more specific for the demon, we can actually say if it's a normal behavior or not. And therefore it's a status reporting kind of collectors. It will say, okay, this is healthy, this is broken. Let's try to find out what's going on. And there will be one collector for every demon. So we will have a collector for MasterD. We will have a collector for the configuration demon, one for the node demon, and so on. Regarding instances, right now we have the collector for the status of sending instances. As the name says, it will be a status reporting collector. And both this one and the one for KVM will provide at the very least, name unique identifier for the instance, which is the one used internally by Gannetti for tracking all these instances. Admin state, which is what the admin want the instance to be, up or down. Actual state, what the instance is doing. Up time, timestamp of the latest modification to the configuration related to that instance. And also state reason, which is something quite interesting. Basically, this is a chain containing information of all the parts of the system that have been crossed by the last command that changed the state of the instance. So for example, it will tell you at that given timestamp, a user used this command line tool to perform a change on the instance. That command line tool activated this internal, created this job, which activated this opcode, which made your modification. So it's trying to track what's going on inside Gannetti and potentially also outside because you can specify the first level of this chain and it will be recorded. So through this, you will always be able to find out what changed the instance last. Something more, something that was introduced only that actually will be introduced in Gannetti to 10. It's already implemented, but it's still not out there. It's only in our Git repositories. The difference between stateful data collectors and stateless data collector. Most of what I described to you up to now were stateless data collectors.  But some collectors, as the one for the average load of the CPUs, doesn't really want to do that. As the name says, it's an average. You want to know, wants to know what's happening over time. So this kind of collectors is run not at the request of the user. It's run automatically in a timed way by the demon itself, collects data, and when the user is calling the collector, it's just activating a reporting function, which will just go and assemble the data in some way and print a nicely done report. For now, the one about the average load is the only one existing, but of course, in the future, we will have many of them. And the current implementation supports a single timer event at, let's say, clock cycle of this timer. All the collection function will be run, but of course, we want to be able to specify a different collection time for every specific data collector in the future. So this was the description about the monitoring agent. Some question about that? Okay, okay, gone. Another interesting tool, which was introduced in GANETT-2.8 as well, is the HAREP, which is our auto repair tool. Basically, before GANETT-2.8, there was no self-repair. The only thing that could happen was restarting automatically a crash instance through the watcher, but the self-repair of the instances wasn't really possible. Whereas, for example, if a DRBD of an instance is broken, you would have manually to fail it over, then trigger a disk replacement, and then everything would be fine again. Or if a plain instance is broken, okay, the disk is gone. The only thing you can do is to recreate it and reinstall, but still would be completely manual. Sometimes you want this to be automated, especially when you have many, many instances. It can be useful. Therefore, we introduce HAREP, which allows you to auto repair your cluster. Basically, what it does, well, it's meant to be run by Chrome automatically every now and then, and the admin, of course, can allow or disallow specific repairs, because as you can imagine, some of the repair operations might also be a bit dangerous so you don't always want them to happen. So, first of all, if you have no idea what HAREP is and you just try to execute it just in case, well, it's not a good idea if your RSS admin to do something like that, but HAREP is going to prevent you to do anything bad. It will just start, have a look at the system, note what is wrong, and that's it. It will print an output saying, okay, this instance is a problem, but it will do absolutely nothing because HAREP will only act on instances where this is admin as manually add or do some tool, added a tag authorizing the auto repair operation. Tag that will have this shape and the type. The type specifically will say what kind of auto repair operation is allowed and this auto repair operation can be of different and increasing levels of importance and of danger. So you can just say, fix storage, which means replace disks or fix the backend without affecting the instance itself. Basically, this is possible only for the RBD instances or with instances who have some kind of replication mechanism. If the secondary is broken, okay, whatever, shut down the secondary, recline the data, recreate the secondary, everything is fine, the instance is still running, nobody notices anything. Migration, well, sometimes you know that the node is not in a good state, but the instance is still running, you decide to move it away to its secondary. But of course, migration can always go wrong for some bad reasons, so you want to be able to decide that you want to do it. Failover, even worse. Live migration is not possible. Should I try shutting it down and starting it again somewhere else? If the tag is allowing me, why not? Worst case, reinstall, everything is destroyed. The only thing we can do is recreated the instance from scratch, so okay, the service will be there, but all the status of the instance will be completely lost, both the running state and the actual drive. It's something you might want to be automated, but of course, you need to approve it. So these tags can be added to the single instance, they can be added to the node group, and the orbit can be added to the entire cluster, because sometimes you don't want to add them manually to every single instance. But what happens if there is some authorization conflicts between all these tags? Basically, the conflicts are resolved through these really simple rules. If there are two tags in the same object, the list destructive will take precedence, and if there are two tags across different objects, the nearest one will win. So in a really simple example, if you have a cluster with two instances, I1 and I2, and I1 has failover, whereas the cluster has fixed storage and reinstall, what happens is that I1 will take failover because it's the closest one, whereas fixed storage will be for instance two, coming from cluster and taking the lowest level between fixed storage and reinstall. You can also prevent auto-repair. Sometimes you have configured all your wonderful auto-repair on all your cluster, and then there is something you really want to do manual to one instance, and you know that auto-repair will interfere with what you are doing. You don't want to remove all the configuration, so you just say suspend the repair for this instance, this node group or the entire cluster for a while. You can also specify an automatic aspiration timestamp, so it's really convenient from that point of view. The operation will go on, and at the end, it will leave you a tag describing what was done, when, in what way, and if it was successful, a failure, or if it could have been theoretically successful, but the policies actually blocked are itself. To conclude my presentation, I will also give you a small outlook of what happened during the Google Summer of Code for GANETI as a mentoring organization for the first time. So I guess most of you already know, but really quickly, the Google Summer of Code is a Google-funded program for post-secondary students who want to work on some open-source software over the summer, and they get paid fairly well for doing this, and students are paired with the mentor from the participating organizations, and for GANETI, it was the first time as a mentoring organization. It might seem funny, but even if we are Google, we were not at all part of the Google Summer of Code program, and in order to enter in the Google Summer of Code program, we had to apply as every other open-source project in the world. So we had to go through the selection process, which makes sense, in my opinions. No special treatment for anybody, I really loved it. So 12 students applied, we had the five slots, so we managed to accept these five students, and your mileage may vary. Actually, it's really the case. So we had a project which was to implement the support for GlasterFS inside GANETI, so that GANETI would automatically, first of all, user-mode support, which is present in KVM, we would like to have not automated ways to deal with that, and then to also introduce support for the actual GlasterFS blocker device as a possible share file system to be used, or automatic configuration of a Glaster cluster, which would be even better, and the student was failed at midterm. It didn't even manage to get to the end of the project, because in the specific case of the student, I'm not going to say any name, but everybody on the GANETI mailing list, we remember the student, he was not really independent. Let's say that at the hottest part of his participation in the project, he managed to send me, I was his mentor, in 24 hours, 26 emails, plus public IRC, plus private IRC. Basically, his approach was, I have a problem, I go and look at the code, no, I send an email. So not so nice. So unfortunately, it didn't work out. But now we have somebody who is working internally, we have an intern, was working internally on this project. Then we have the exactly opposite, we have another project, it was to modify our tools for allocating or rebalancing the cluster, which currently are based only, we're based only on configuration information. So the number of CPUs that your cluster had, we wanted to have the possibility to use CPU load average for deciding where to move instances. And this project was successfully completed, it will appear in GANETI 210, and actually the author is Pierce, who's here in the room. So if you want an applause for Pierce. Then we had another problem with another project, which was implementing OpenVswitch support in GANETI, for having virtual networks. It was not bad, it was supposed to implement the management of the switches on the cluster and the creation setting up and connection of instances to VLANs. There is a basic support, which is working now. You can set up the switches, you can connect instances to the switch. So basic support working successful project overall. Then we had support for the huge pages as implemented by KVM, the student just disappeared. Who knows, as anybody seen our students, we didn't. And finally, there was another project for improving the already existing rados of supporting GANETI. Basically, we wanted to have the KVM user space support, also in this case. So basically it was a twin project with the cluster one. And also this student was failed at midterm because it wasn't really able to contribute any code by that time and the rules of the Google Summer of Code say by midterm, there should be some actual visible contribution. So what are our lessons learned from the Google Summer of Code? Which is a great opportunity, but it can also be a great resource hog. So basically what we think to do if we go on with the project next year is to be stricter in the selection process. The students usually in the Google Summer of Code are selected on the base of a project they present. They say, I want to do this, this is my time scale, which I'm envisioning, and you have to decide. Unfortunately, this didn't really work. So all the students presented projects, they were pretty good ones, but then, given how we work, we always ask for a design document before implementing the actual feature. And just writing the design documents took the students, most of them, the failing ones, basically one month, two months of the tree and something that were part of the Google Summer of Code. So it didn't really work and there was no real correct interaction with the community about this. So probably if we decide to participate again, we will ask the design document as the project, as the presentation of the project. So we can, or at least if not the final approved design document that of course can take some time, at least a first version of the design document already of such a quality to be sent as a proposed patch to the set of design documents. So this is what we'll probably do. This was our experience and this is my talk. So some content is taken from slides made by my colleagues and presented in various other venues. But feel free, if you have any question, I'm here. Anybody?  Sorry? Couple of words about what?  Oh, so personally, I didn't use much, I didn't, I don't have much experience with commercial solutions. So I'm not really able to give a general overview. If you have some specific question in mind, maybe I can tell you how Gannett is doing things. But first of all, the main benefit, as said in many other talks in these days, is that being an open source solution, you know that it's going to be around or worst case, you can still be able to modify the source code. And you don't really have issues with licensing, which can happens with commercial solutions, where if you want to scale your infrastructure, well, now I need a bigger license. What's the cost of the bigger license? Well, a lot. With Gannett being completely open source, you don't have this problem. So from what I know about OpenStack, for example, my idea is that OpenStack can be more flexible. It has a lot of components, and this can be really good, but it can also be bad from the point of view of the initial setup, probably. Because when you have so many components, yes, you can substitute any of them, but you still need to set up all of them. Gannett, it has various demons, but it's a single package, it's a single software. So it's easier to set up at least initially, in my opinion, and it's already able to scale a lot. So if you want to start from a brand new system, implementing something from scratch, I think Gannett might be an easier solution. Whereas if you want to integrate with something that is already existing, or you have some specific needs for some component which you cannot really change, maybe OpenStack can be better before, because it's a stack, whereas Gannett is a single product. This is my impression, my opinion at least. What's the state of LXC support? So that's the weak point. We have the support, but it's not actively being worked on. So, and actually I don't even know of anybody actively running LXC. So what is there? Probably still working, but it's not actively supported. Whereas Google internally runs Xen, so of course we have complete support for Xen, and basically everybody that I know in the list of other projects using Gannett are running KVM. So both Xen and KVM are perfectly tested and known to work really well. There was some, okay. Are you running any additional layer to do the same task we've done? What I was seeing out there was like a live migration. KVM and Xen has their own mechanism for that.  No, actually what Gannett does is using their mechanisms, but the difficult part there is to ensure that you have the data also on the node where you are migrating. So Gannett is helping you by automatically managing all the data replication either over the RBDE or over some other shared file system, depending on what you want. We have support for many of them. And that's the thing that Gannett is actually doing is making your life easier in general. It's not really adding new features. You might do the same thing manually, but it takes a lot of time to set up, to maintain them and so on. Whereas with Gannett it's just, okay, I want to do a migration. GNT instance migrate name of the instance. You don't even need to say where because Gannett already knows what the secondary is, so it will just migrate on the other node.  I was just asking if you use, for example, Xenapi for that. Yeah, we are based on the existing solutions. We just take away the difficult part of that. And there was another passing back there, I think. Okay, perfect.


The article discusses the limitations of using randomized controlled trials, RCTs, as the only tool to evaluate non-specific effects, NSEs, of vaccines which can be ethically problematic, time-consuming, and expensive. Instead, triangulation of RCTs and observational studies can build a strong argument for causality by merging multiple lines of evidence with different underlying bias structures. The article examines two examples related to measles vaccine and oral polio vaccine, an expert commentary suggests that results from both RCTs and non-RCT studies should be triangulated to strengthen causal interpretation. This article was authored by Christine Stable-Ben, Ayn Berent Fisca, Andreas Rieckman, and others.


The challenge of the Yukon. The Wonder Dog King. Swiftest and strong as the Vescomole lead dog, blazes the trail through storm and snow for sergeant Preston, as he meets the challenge of the Yukon. Sergeant Preston was typical of the small band of northwest mounted police who preserved law and order in the new northwest country, where the greed for wealth and power led to frequent violence and bloodshed. But in spite of the odds against them, Sergeant Preston and his Wonder Dog King met that challenge and justice ruled triumphant. It was many years before that great organization, the Seeing Eye League began to train dogs for the blind. But the instinct and devotion of dog to master is timeless. And so it was that when Pete Ramsey lost his sight, Alec became his eyes. The two of them walked along the Tolson City's main street. They were the object of kind curiosity on the part of a small group of trappers and prospectors who stepped aside to allow them to pass. Hi there, Pete. How are you? Well, I haven't seen you in quite a while. How are the traps these days? Got some mighty good silver boxes yesterday. That's good. What brings you into town, Pete? Oh, you here too, Jim? Oh, Alec and me just decided to pick up a few supplies. How's Mary? Fine. Stop by at the cabin next time you get up our way. Yes, thanks, I will. All right, Alec. I'll see you later, boys. So long, Pete. Take care of yourself. See you later, he says. Poor Pete. You've got to hand it to him. Aren't many men who'd have what it takes to stick it out up here? Blind as a bat like he is. What I'd like to know is why he doesn't get back to the States. Sally Michaels would marry him in a minute. He doesn't go back because he ain't got a thing to his name, except the cabin he's living in and that dog of his. The truth was to be known, though, that there's money a day that both him and the dog go hungry. Ah, Pete's a proud son of a gun. No charity for him. He won't marry Sam Michaels, girl, because he's afraid she feels sorry for him. I thought there was even a chance Sally married me. I sure wouldn't stop to wonder whether she did it because she was sorry for me. You and him are different, Clem. There's only one man in this territory who can make Pete share a can of beans without getting an argument. Yeah? Who's that? Preston of the Mounties. I bumped into him over at Circle City last week, and from what he said, he ought to be here in a day or so. Come on, Clem. The drinks are on me. Lead the way, Father. The two men turned and walked into the saloon. Pete Ramsey forgotten. Because people forget more than they remember, they thought of the proud handicapped young man only when he intruded into their world. There were three people, however, to whom Pete was an important consideration. One was the slender, dark-haired girl who put a jar of jelly on the round wooden table in a single-roomed cabin later that evening. And you needn't get healthy either, Pete Ramsey. It's only a jar of jelly I brought over. No, you shouldn't have done that, Sally. Why do you have to be so stubborn? Why do you have to close yourself up in here, never being with people, staying by yourself? Why should I go anywhere? I'm satisfied this way. Ellie can all...  Well, you're shellfish, Pete Ramsey. Selfish and stubborn. Has it ever occurred to you that it gives me pleasure to see you? I won't hold you to a promise you made before. Darling, it was I who made the promise. I love you now just as much as I did when I told you I'd marry you. The promise was mine, so... Well, it's mine to break or keep as I choose. And I choose to keep it. No. No, it isn't any good. I have nothing I can offer you. You don't need anything. My dad's claim is richer than we ever thought it was. We could do... Ellie, I don't want charity. I won't have your father supporting me. I suppose you wouldn't. All right, Pete. I guess I'd better start with a cabin before it gets dark. I could send Ellie with you. No, never mind. I'll be all right. Bye. Goodbye, Sally. What is it, Ellie? Come here, boy. Come here. Come here, fella. Well, what do you see, fella? Or is it something you hear? Alex saw nothing. But with that strange sixth sense inherent in all dogs, a thousand warning signals were alive within him. He felt the presence of intruders, and with it, a strong, unreasoning premonition of danger. As she walked from the cabin, Sally Michaels noticed the two figures standing at the edge of the creek on Pete Ramsey's property. She might have hesitated instead of hurrying on. Had she realized that these two men were very much interested in the man who was staked on the land where they stood. Just take a look at these flakes, chick. You can pick them out of the gravel. What kind of a fool is it that leaves this stuff where anybody could help himself? Maybe he's already got so much out of this claim he can afford to leave it laying around. Hey, what in the... Hey, he's setting his dog on us. Ellie, where are you? All right, fella. Now, tell me what you want to know. Hey, who is it? Well, my partner and me wanted to fill our canteens. You ran out of water, and we thought when we saw your stream... Christ, it's perfectly all right. Take whatever you need. I don't believe I know you. Where are strangers in these parts? My name's Crane. Chick Crane. This is Steve Lindsey. Glad to know you. My name's Ramsey. Planning to camp out tonight? Well, yes. Well, you're welcome to stay at my place. I don't have much to offer you. There isn't much food, but you're welcome to what I have. What do you think, Chick? Well, it's fine. Fine, Ramsey. Thanks a lot. No, not at all. If you have your canteens filled, then go to the cab. It was early the next day. Chick Crane and his partner walked slowly back from the stream. Where they'd gone to refill Ramsey's canteens. Well, it's a cinch, Steve. We'll never find anything easier. He doesn't have any idea there's gold in this land. Yeah, I know, but I... Oh, no, buts about it. Now, we can fix the whole thing so it'll look like an accident. An accident, huh? How do you figure that? Well, you'll leave it to me. When we get back to the cabin, I'll show you what I got in mind. Uh, just one thing. What's that? Watch out for the dogs. A few minutes later in the cabin, Pete Ramsey sat quietly in a chair with Allie at his feet. While his two guests busied themselves packing, I've been quite glad to have your company, though I'm sorry I didn't have more to offer you. Why, that's all right. Steve and me ain't very fussy. You got the rifle, Steve? Yeah. Here it is. Well, then use it! Ah! Ah! Ah!   Get the rifle out of there!  You should have brained him. Oh, rather both are cold. Bring that oil lamp over here, will you? What do you want with it? Sprinkle this oil around. We won't need much of it. Just enough to get started. I get it now. No fooling. Come on now, let's get out of here. We'll make camp a couple of miles up the trail. As far as anybody will know, a blind man can't handle matches. See?  You sure figured this out, chick. And we move it on a rich steak, huh? All right. Much walkie. Much. The two men had disappeared from view as another dog sled cut tracks in the snow. The great dog king leading Sergeant Preston's team had caught the scent of smoke and had urged the pack to a faster pace even before the mountain and the young girl riding in the sled saw the clouds of smoke plummeting in the sky. Sergeant! I see it, Philly. That's the king, that's the... Our new Malamute! Oh, it's the carbon. He's in there. He's in there, Sergeant. The mountain hauled his sled in front of the cabin and with King at his side rushed to the door. Fire was already devouring the logs of the small cabin and as Preston pushed the door open, the intense heat blasted at him suffocating and driving him back. A second and a third time the policeman tried to fight his way through the flames to the cabin. King, watching his master, hesitated no longer. He raced forward into the burning building. His eyes clouded, but smoke steered them mercilessly filling his throat with an ache that was suffocating. With his nose close to the floor, he made his way through the one room inferno and then suddenly he sensed rather than saw the man and his dog. Steve Lindsay thought he'd missed when he fired but the bullet from his gun had caught Alan. The dog was struggling violently to put his sightless master to safety but weakened in days as he was, he could find no way through the flames burning on all sides of him. With one hand, Pete clutched Alex collar, sinking his strong white fangs into the man's coat, King pulled Pete Ramsay and his dog. King, King, oh boy, here, wait for help. Good fellow, King. Sally, bring me my medical kit quickly and then slowly, Pete told as much of the story as he remembered while Preston cared for Alex's wounds. Will he be all right, Sergeant? Yes, I think so. Sally, will you bring some water from the stream? Take this canteen. Certainly, Sergeant. Wait, it's been burned alive, Alex and I, but it hadn't been for King. You and I know the value of a good dog, Sergeant. You're sure Alex will be all right? Mm-hmm. He's taking this very bravely, Pete. Not a whimper out of him. Going after those two men, the tracks of their sled show plainly in the snow. What I can understand is why they did it, why they would try to murder you. Here you are, Sergeant. Pete, Pete, did you know that there are flakes of plaster gold in the gravel down by the stream? Plaster gold? No, I didn't. A Jim and Clem built this cabin for me. I didn't move into it until after I'd lost my sight. That's where those two men were standing when I noticed them last night, Sergeant. They must have known. So that's the motive, hmm? Sally, you finished dressing this wound of Alex's. Sandy didn't apply this medication. I'm going after those two right now. King, oh boy, think you can get the dogs up? You ready to travel? Good. Then come on, fella. Sergeant Preston returned to the site in the burned cabin an hour later and found Sally helping Pete Ramsey into a sled. About he had two men with him. Both of them walked sullenly and thought of him toward the man they tried to murder. That's your fault. Pete Ramsey wasn't burned alive. I tell you, I didn't have anything to do with it. It was checked through. Why are you dirty, double-crossing blabbermouth? You're in this as much as I am. Yeah, the ones I didn't. I recognize their poison under both of you for attempted murder. Sergeant Preston, I think you'll back me up on this. Pete's a rich man now. There's gold on his land and... I know very well that if you can't work it yourself, Pete, my father will pay you any price for it. Oh, for heaven's sake, Pete, do I have to propose to you? Sally, honey, if I thought your father would... Well, I hate to interrupt you, too, but... The reason I came up here, Pete, was to tell you about this friend of mine who's in town. He's a surgeon. I told him about your accident, and he thinks you may be able to restore your sight. You may be able to work this mine after all. Oh, that's wonderful. Yes, fella? The case is closed. These copyrighted dramas originate in the studios of WXYZ Detroit, and all characters, names, places, and incidents used are fictitious. They are sent to you each week at this same time and originate in our transcription studios. Bob Hyde speaking.