That's it. That's it. Yeah, see there we've got the push-in connection. Connecting goes into the clay. Our band seals wouldn't fit over this clay, it's very big, so we've actually got another one of these. But when the flow's going that way, they work really well, because it goes into the pipe. Once all that's done, and it's prepped, we're going to get half a mix in, just to get them brick and block in so we can actually get that concrete in when the time comes. And we've done four tonne of stone, insulation, and now it's got this end up. So we're all ready for concrete. We're all on Tuesday. On Monday, hopefully. This is tucking into the rest of my bacon-butty there. It leaves all the best bits, all the crispy bits. We're here, we're going to have a woody coffee. Here we are. We've been to grab a cheeky coffee. We've had a fright Thursday since we were working on our third bank holiday on the truck. Yeah, so today's job is getting this slab prepped. But first job, get the new gully put in. Yes, we've just been to Tool Station to pick that up. Yeah, and then... Excuse me. First job, sun cream. And then, you see how? Cut that out. And then, we're going to just get this slab prepped up. We made a bit of a start yesterday. Just smashed up a few flags and just getting some buckets of that MOT tossed in. But, excuse me, what's up with you today? Today, we're going to just get the rest of them flags smashed out, tossing that skip, get the MOT in, get the sand in, get it whackered, visqueen, song and dance. So, not much else to say but to take you over there. There we are. So as you can see, we've made a bit of a start getting some flags up and there's a little bit of MOT thrown in. Just while Dad was getting that gully sorted out last night, I just made a bit of a start in here. So, we're going to continue with that. And then, oh yeah, once all that's done and it's prepped, we're going to get half a mix in just to get them brick and block in so we can actually get that concrete in when the time comes. So, that's the battle plan for today.  All sorted. Alex, just push away that. Show it to push in. Connection goes into the clay. Our band seals wouldn't fit over this clay. It's very big so we've got to get another one of these. But when the flow's going that way, they work really well because it goes into the pipe. Little bend, straight coupler, another little bend. Nice, new, neat gully. A little bit more flooding because that thing was solid. Solid and it had a crack in it. I think we cracked it when the digger fell in but it is what it is. New gulley in now, worry-free drains. We're going to get this all back filled. It's got a nice wide area to work at now and get this lot prepped. Passes to you, hot potato. Recording. Yeah. Filming. Yeah. It's nearly 10, isn't it? Yeah. Yeah. We're almost there at 10. This pipe's all packed up on the MOT now so that's solid, going nowhere. I'm going to put some pipe bedding over that. Pipe bedding, 10mm limestone, P-shingle, P-gravel, shingle, Dingley-dingle, jingle bells. Anything else, comment? No, no, no, no, no, no, no, not again. Anyway, yeah. So that's ready to go. We're going to work from that end, work our way back now. Alex has been filling the bars. I've been taking the bars and bringing the bars full of MOT back. So, drains in. This is all backfilled now so we can work on this side. We've got a much wider area for coming in and out with the bars. That's our stone level. So we're going to bring that through level now. Yeah. So once all this stuff's out, we're going to have a quick break and then hit it again after the break. So far so good. No hybrid pofins today and the hip seems to be doing all right. So we've done a few laps so far so we'll catch you after boot time. Just thought I'd show you the step real quickly. That didn't take much. As soon as the top flags came off it just crumbled to bits. And of course, another Coke can.  But once that's out that's all of the taking out of this slab prepping. It's just putting stuff in then. Yes. So I think one or two more bars will do that and then we're ready to have a break and just whack this in. So that's the stone level, isn't it? Yeah. And then it's just a bit of sand. Yeah. Visqueen, insulation, visqueen, concrete. No reinforcing. No reinforcing this time now. This slab's 2.3 deep and the ground is solid. I'm not reinforcing it. It's not like the previous extension. This one's a lot more manageable. What is now? Yeah. What is now around the ground? Yeah. But you saw the size of that other one so this one doesn't need the reinforcing. Anyway, let's... next time you see us it'll be after the break. Welcome back. The steps gone. Wackers here ready and now we're just burrowing this stuff. Let's get you set up and just get this thrown in and whack it up. Oh, not checked out. I'm far have walked yet but it's a long way. You see it's just dropping on the bricks there. That's ready for the sand blinding now. Bring it up level for 100 mil of concrete. I'm going to put a 100 mil insulation down there to bridge that cavity and then our insulation goes over the top of that and then the concrete goes over the top of that. We're getting there. Good size ring. Now all the crap's out of it. See how big it is. So we're going to have a quick dinner now and then get it lined up after dinner and get it all prepped. It's been a long day. Very long day but as you can probably see around me that's just getting the last little bit in but this slab is ready. Well, we're just going to do that last bit of this screen but we're doing that on the Tuesday or the Monday depending on when the concrete arrives. The screen goes in the day before. Yeah, because if it rains we're not gushing it all out then we can let the poly can absorb some of that. There's really good ground under there and plenty of stones, right? It'll just get a little bit of dissipation underneath. Yeah. And there we go and there's the you call bridging as well all the way across where it sticks out. There's a lot done today.  Got four tonnes of stone moved in here and I was just barely enough. And then obviously... It was tight, wasn't it? Yeah. And then obviously got all this prepped with the sand and the viscuin and the wacker we had to get this put in which I did while Dad was doing the polystyrene. So... Massive actually. Got the block working and the brick works in all joints and the sponged and we're also toothing into this.  He's doing all that while I've been doing the polystyrene. But it's very tough stuff but we're going to through. Well obviously you can hardly to lay it but it's going to make a difference. Instead of just having a big expansion joint in there. You can't put an expansion joint in because you need to set ties for an expansion joint. Oh yeah, that's true. So it can't be an expansion joint anyway. Yeah. Well there you go. But that is that. Is this going to be the end of this video? The prep? Um... We're going to have the concrete being a separate video or? The concrete slab, prep and concrete is all one video. Right. Just take us back on there there. But there you go. There's one prepped slab. Next time you see us it'll be to, not tomorrow, it'll be Monday or Tuesday and we'll be getting the the viscreen in and the concrete in. Let's bloody fingers crossed, manifest that it doesn't really rain because we have a habit of it always rains when we go to do concrete of any kind. So fingers crossed we'll see you when the, we'll see you on concrete day. And as you can see we've got the GoPro back. That feels a lot better. So then we're all set. We've got the ramp set up as sturdy as we can get it. Give it a bounce, give it a bounce. It's got a little bit of a, got a little bit of bounce for the, for the barris. So just thinking we had the barric for the concrete is 18 stone apart. Yeah. An operative. There's a, there's my best friend. And as, What was your best friend? What? What was your best friend? And as you can see he's showing us the sill's been cut back a bit with the, yeah, been cut back with the grinder so we can get the concrete and really get the float in there now. And we're ready. We're going to have probably one of the earliest breaks I've ever had now while we wait and, oh, and the laser's all set up as well so, and our little new method of putting the laser on the tamp. All right, so we'll see when the concrete arrives. And there you have it. I think our friend approves. One nice concrete sliver's in. So we're going to let this go off a little bit before we tamp it. So in the meantime we're going to clean up all that sludge and once that's all done we're going to finish up the bloody break that I'm going to do and then tamp up all that, get it floated and we've got places to be today so we're going to be buggering off after that so tomorrow we'll be cracking on with that brickwork. I can see him. He can tell he just wants to just walk all over that and leave his footprints everywhere. I can see him. I don't know if you can see him. There he is. I see you're looking. But yeah, so we'll catch him a little bit once he's done our cleaning up and we'll be getting this tamped in and floated. Another speed bump. Actually getting extra bar just in case. Not now. It should be okay. Boom. Half a bar short. So mad dashing the car to get some vast bits of mint there because we have no van today. It's getting serviced now.


Natus level 22 starts out with practically nothing on the web page So the first thing to do is just go ahead and take a look at the source code See if they actually are trying to hide anything here So I'll paste that URL into our Python script and we'll go ahead and download the page gonna need to de-entitize this all again That's okay remove any break statements or anything else that we have in there That's getting in the way, but it looks like at the very start of the web page There's some PHP code here It starts with the new session and then determines if an array key exists if there's a get parameter Revealio, I don't know. I would assume this is revealio since they're trying to reveal the password And the common here is only admins can reveal the password So this is interesting because it's testing if the session admin key exists, and if it's set to one But only if it's not set to one it'll do something It will redirect you or it'll set a header location like an HTTP header to move you back to another page Like the root directory or the root page of the website here So that's peculiar because it only does it if you are not admin But the only PHP code in the page here is testing whether or not you're passing the Revealio tag in they the HTTP get variable. It doesn't worry about the session admin here So is there a way we can ignore being moved or Following a redirect if we just supply this get parameter But we don't know this admin session or read because it doesn't look like there's any way to actually set this There's no vulnerability to Kind of get in the way or inject this admin credential in our session. So let's try Just trying to run with this Revealio HTTP get variable and it looks like it will just bring us to the page Yeah, so no no admin credentials there Because it redirected us right because we weren't session admin so it kicked us back. Is there a way we can ignore that header Absolutely so you can totally do this in burp if you wanted to because burp will see the original request return the output to you And then move you along with the redirect if you want it to but since we're doing this in Python with requests That module is gonna follow the redirect, but by default You can turn that off allow redirects That's another keyword argument for a get request You can just say false and that will load only that page the one that you requested So now if I go check this out. Hey, you're an admin Even though we haven't modified that session admin variable that PHP global and session We are still able to get through it because of the code in the website We're not being redirected because just telling us no browser I don't want you to do that stay where you are credit us with the next level We've got the password and we can move on so credit a new script here. I'll call this natus 23 Paste the password in and we will keep moving. We don't need to do this allow redirects anymore But that's something good to know Maybe you do want to use that allow redirects keyword argument more often in some of your Python scripts If you're doing some of this webhack and CTF style stuff. So thank you guys for watching. Hope you're enjoying these If you are, please do like the video. Maybe leave me a comment Let me know what you think what else you'd like to see how you solve this and what I can do better If you're willing to subscribe and if you really want to support me, please check me out on patreon A shout out to the people that already support me on patreon Spencer Clark Thank you so much for your support You are helping the channel grow and develop and helping me out for sure I do know the reward if you support me whatsoever through patreon I'll give you a shout out and include this stuff at the end of the video And if you've five dollars or more, I'll let you see some YouTube videos in advance before I get them uploaded or scheduled So thanks for watching. See you soon


recording. Sorry, David, just to say that there's no containers on regarding the no SDK today, so I'm not sure, but if it's recorded, I suppose we can pick that up, okay. Yeah, yeah, we'll record it, so folks can listen to it later, give any feedback if they want later. Okay, let me just show the JIRA dashboard for the roadmap. So these are basically any Epic in JIRA that's tagged for v2.x. I will start with the update for improved fabric samples since I'm currently sharing. So the samples, updated samples for v2.2 and using test network are well underway. We've got a whole series around asset transfer scenario. There's a bunch of chain code samples done. I'll show you that over in fabric samples. So there's asset transfer basic, ledger queries, private data and secured agreement. Those all have chain codes done and they are in various states in terms of the applications that can drive those chain codes. They can also be driven through CLI, but we're currently working to finish out all the applications at least for the basic samples so that there's a model for people to use for any language to drive a basic chain code. And then as you go down the list, they get more advanced in terms of ledger queries, showing how to use private data, showing how to use state-based endorsement. And then a final one kind of puts everything together for what we call the secured agreement scenario. Anyways, the applications are in progress for those and so are the tutorials. Some of the tutorials have been updated already. We've gotten, for example, the test network tutorial and the chain code lifecycle tutorial updated from Fabcar to use the asset transfer basic and we're rolling through all the other tutorials to update them as well. Any questions on the samples? Okay, so then I guess we'll go in order here. Jason, are you on? I'm going to give a quick update on VFT. Yeah, I guess I can give a quick update. There's some work that's been progressing on the library, but there's some items that have sidetracked me a bit, so it's been making a little less progress than I'd like it to, but still aiming to have at least a feature-complete library by the end of the quarter is my hope, but we'll see how that goes. And from there, we would start looking at integration. Okay, thank you. Channel Participation API. Will, do you want to talk to that one? Sure, yeah, I can chime in here. So yeah, things have been moving along pretty smoothly here. Yoav's been continuing to leave the charge on the join channel work. So I think we have a good base of that in now, as well as some refactoring work around some of the order registrar and things like that. So that's continuing along. We have the remove channel, also in progress, and some integration tests around. So yeah, nothing out of the ordinary really to report with any of that. Okay, thanks, Will. The config transaction library. Yeah, so there's been a couple of releases out for that already. I've just seen some initial ones. The development of that is more or less still ongoing pending feedback from initial consumers. So we've made a couple of changes already to the original API that had been released as part of the 001. I think we'll un-release 007 now with periodic incremental improvements securing their two pieces of the API just based off of feedback from community members. Still looking for more people to kind of use it and provide more feedback and then continue development on that as needed. Okay, cool. And then the doc around fabric network deployment guides. Yeah, thanks, Dave. So work is continuing on the fabric deployment guide. We've started work now on the peer deployment process. We have a work group that happens on Thursdays at 2 p.m. Eastern if anyone's interested in joining. Similar to what we did for the CA Deployment Guide, we're planning a three-part topic. Part one is going to be planning and considerations for your production peer. Part two is the configuration settings in the core.yaml that you need to understand. And a side shout out if anyone else has favorite settings in the core.yaml that they want us to highlight, they can join our work group call. On Thursday at 2 p.m. or put comments in the fabric documentation channel on rocket chat. And then part three is a tutorial of the deployment steps. So that's where we are with that. The other thing I wanted to bring up is that we need to start thinking about documentation for the fabric 2.3 release. Specifically around the ledger snapshot and checkpoint work and the channel participation API. We plan to follow the normal process where the developers draft the documentation content and then we take it from there. So I would ask the developers who are working on those features to start thinking about what kind of documentation is required, how you think it should be docked and where the dock belongs as we will start to work on that together. So that's it for me. Okay, thanks Pam. And then ledger snapshot and checkpoint. Yeah, yeah. So in this one on the development front, you know, like we had divided the this thing into four or five high level user stories. So on those, the snapshot generation story is done. And the bootstrapping story is done basically leaving the private data aside. And then to expose these functions at the peer level, the engine is working on CLI commands. So that should be done soon. And our going forward, the plan is that in parallel, we will start with the we would like to start with the system tests so that we get to see some input or some issues which we run into when we perform these things on high data volume. And so we would like to know basically those issues sooner than later, while in the background, we would keep working on the bootstrapping private data handling. So that is the development side will keep going in parallel. And after that, there are like some minor tasks kind of adjustment of existing commands, rollback reset, etc. So those should be, I think, fairly straightforward. That's the overall status. Any questions? Okay. Thanks, Manish. And then finally, the programming model updates to add high level programming model to the go SDK. Okay. Hi. I'll be quite short because that's been completed now. And for is available in the beta two release of that. I don't know how much more you want to go into it. Yeah, no, we talked about that a few weeks ago. And we've, you know, talked about maybe if that would be ready for production soon, we decided to hold off and keep that in beta for a little bit while longer and get some more feedback on that. But Leslie, and maybe if you could just update the current status field for fab g928. I think it is updated. It's actually closed. What? I mean, just this field, it says in development, you can highlight that the beta is available. All right. Okay. That's in the current status field. If you've never seen that, that is right here. All right. Okay. I've got that. Yeah. Thank you. Okay. So I'm thinking with, you know, ledger snapshot and checkpoint and the channel participation, channel participation API potentially coming in a next release might be good to do it to do a deep dive on those two topics and subsequent contributor meetings. So we'll see if one of them is ready to go in two, in two weeks or four weeks. But we'll try to do a playback in this meeting for those two items since they're kind of the next two big features coming into fabric. And we'd like to get feedback on those as well. But any other questions on the overall roadmap? Okay. So let's hand it over to David. He can show us what he's been doing around the module for Fabric Admin. Yeah, thanks. Can you see my screen? Yes, we see it. I will charge a typically technically specific and try to keep it in case we see it because we just had a little about trial just this trial of slides. Okay. This is the name of the MPM module. I published this here. Some, yes, it's already several months ago because as long as these admin capability parts of the Fabric SDK, Fabric Node.js SDKs will remove the community peoples are keeping on asking that where do we go? Where do we go? So I spent some, our roadmap is one month store or deeply dedicated for to create this compensation, compensation parts of admin capabilities, portion of the SDK. Okay. Let's go directly. It depends on the existing SDK modules that the Fabric SCA client, because it is unstable. Fabric Commons, another part is quite simple. It's my personal format. It only contains some of the constants and format adapters. So it's simply for development. Actually, if we in the future, we can get rid of it because it's just some statistics, static files. Okay, it is dependency. And this sign is, firstly, I will follow the design of like most of the rest part of the SDK that is object oriented, just coding styles. And we try, I'm trying to recover most of the helpful function as deleted from the SDK itself. And the features is now current base cover includes the channel operations, some of the query join update and check operation install approach can be. And I intentionally not to touch up about doing actual transaction part because it is quite nicely handled in Fabric Networks. So this is my design. And some of the, some of the, why see some of, one of the helpful function that I did not recover is the channel come, get channel dog gun, get channel come back from peer, do not be reviewed because nowadays from, after the refactor of the US service that we can easily get it from peer or a gate from order. And I additionally, I give some things like a gate policy Jason is the chest data for the gate DSL to end out of the syntax. I follow the, follow the design of the Fabric Core of the policy parts of the code. So you can easily have a string representation of gate DSL DSL to a portal message, which show us, show us an end out of syntax. Okay. Component map again, because aside from the deletion of the, of February SDK, I mean capability parts, some of the component is highly renamed for the newcomers when you have already played good with the old SDK that you will find, where is the PRJS, where is his order here. Now I also have a conversation parts that it is recovered, but it is built based on the new design of the Fabric SDK. So it is PRJS, it is a combination of the end also in the inventor and order, which is work as a committer and inventor. Now you may see that why the order PRJS have to work as an inventor because event, it is not designed to be, because the order is not designed to be can emit an event. I build this because I, because for the, for the intention that we could easily get directly get block from the order and the channel operation as you all know here's channel creation is just another part of the sample of the channel update. The channel update process is placed in the channel update of JS, aligned with the fabric command design. You could either use, I've decided two fashions to use as in channel update. You could either use an envelope entirely, or you can use a compact area with signatures. The first one is quite, if you can use when you want to use a combination fashions that you, first you use the command lines to, based on PR channel to sign the config, then you load the config files into the envelope, into four SDK developments. This is one fashions, another fashion is that you want to play it all within JS. So I provide two fashions here, and the channel operation, the next part is channel join, PR join and channel in nature is sending a system chain proposal to PR. So it is done in the cccc proposal of JS. You can extract the genesis data from a file, or you could use a method that gets specific block in signing identity JS. If you, or as the new design in the committer, so it's here, you could never get a block directly from the order of JS. So I compass, I, however I say, I would say it's reviewed of the old gap block from the order, the functions based on the GIPC streaming back to the order of JS. So that you can get us use other JS as the, as usual as before. And the channel operation parts they're separated in the, in the life cycle, life cycle mostly, life cycle proposal, JS mostly, it is here is the most, JS is more, more like this. For the painful package part, I will not, I have not included in that module because there are several ways we can packs, make our archive. I will provide a sample in another NPM package, but it's not included in this NPM package. Yeah, so as the, as a proof, as here, which shows all is done in these fashions. The proof for my org is a function inside the JS. And others I also implement a stream this discovery service in discovery JS. The only return, the only return the robbery resented of discovery results, no further object rebuilt in size. So for some developer, they may want just to inspect the, what is the, the raw percent raw results when the discovery has done instead of the recover all the peer and order and channels into the, they are already convect the in memory objects. And the rest is the mercenaries you may use or not to use. And I, if it is not required in, or if maintenance say it is not necessary to include in that package, I would like to remove it. This simply just wrappers, something like an event hub for event service, identity surface or wrapper of identity surface and user JS for common, the user JS in fabric comments. And some of the utils includes not here. This is the portal transmitter. This part can also be refactored in a little bit because nowadays I have noticed that the fabrics SDK had already refactored the, the port fabric portals structures is nowadays they based on fabric portal six, you are pure JS and a passion to do that inside the bee. This is another utils. I require, I recover or build collection configs function from the ones and add another functions. Now it's for a standard. What does it mean? Is there a translator from the collection config.json? What, what I have to make it that from the standard because inside the collection config.json, which is show in a sample of fabric documents that the syntax to, to represent a sign and endorsements or rather say endorsement policies inside the collection is used gate DSL instead of N out of. So along with the previous the translator where what I have mentioned about it is that I also incorporate here with a translator with, with a translator of gate DSL to the N out of syntax. You may, you may, you need to know that we as the test coverage of that entire MPM modules, I have to say, because while I want to keep it, keep it keen, I use another project is here if I fabric is me, my main main, I maintain for just as a home of the network push a composer and also the home of integration test. Some of the unit test is done inside the MPM module but I see it's not enough for the rest of the first part of this, this MPM module. I place it here. So my plans is I have, I remember several months ago, I discussed with the red logans he's not here. I want to, whether we can propose this as a third party or community contributed development tools when people were looking for the, do some big abilities for people by using private SDK as they usually, as they usually do. And the second my friends do is miscellaneous stops. And that's all of my presentation today. Okay. Any questions and I'll suggest that I could you share. Thanks, David. So what's your vision for this long term? Would you envision it being contributed to hyper ledger eventually and being kind of the notice DK for admin operations? I, I would like to contribute to the hyper ledgers because I'm, I'm also having a technical investor. So, but it depends on, because I, I am not exactly, you know, the why this, this part is removed from the fabric SDK nodes. And so when I contributed back, I am wondering which is best format or structure I could contribute back is the best for the communities. I would like to contribute in any ways. And I would like to see what kind of help but it all depends on the maintenance. So it is important for your feedbacks. Right. Yeah. I think it was just a, you know, a prioritization that it wasn't prioritized for to, to, you know, to the Fabric 12 chain code to update the SDK. So I think it would be good if there's a contribute contribution like this. And if it got, you know, consensus and community behind it, then it could become, you know, if the official hyper ledger contributed SDK for admin operations. But I think, yeah, it's, it's, you can, I would recommend putting it out on the mailing list. And people can start using it playing with it. And we'll see if it gets some traction. Okay. Yes. So I remember I posted in the node just the blockchain channel and some of them use it. But I, because several things have already passed and there's not too much discussion on this part already. So I will try to remind it again in a merit maybe. Yeah, I know a lot of people had have asked for this in the various forums. So I think it will, you will see demand for it. Thanks for helping. I'll try. In terms of the experience is if people were using the admin capabilities and the 1.4 SDK, would they see a similar use model here? A little bit different, but I try to keep the function names are same as that the old ones. Maybe you can see it because at least you will see the chunk of stories total difference. And before the package, something like I try to keep it the same experience as before. It's sometimes hard. And, and actually in 2.0, the structure of the new, actually why I see is the pool, the new, new, new structure of the SDK itself is quite good because we expose the fabric portals outside that we can place entirely. So, so, so that's the code is much more slimmer than previous than the old ones. And you do not need to have all things inside the channels. And most of, most of the, how will I say it? Another way, another fashion I usually decide is I'm trying to keep it stainless instead of keeps all that all the components inside a channel or client. You have to keep that in memory object very carefully. I will play I the way I decide this when you play out, play with the operation, play with the class, you can entirely get rid of it for the next times. So you do not have to keep this instance globally inside a node just one time. So it is designed to be stainless. In all, in all design of fabrics SDK nodes, sometimes not purely stainless. So I've tried to avoid that. From this point, I sometimes it is have different experience. Okay, thank you. Any other questions for David? All right, thank you, David. Like I said, put it that out in the mailing list. I think that would be the best place to publicize this. And then we'll see what kind of traction it gets. Thanks. Yep. Okay, anything else for today? Anybody? Could I stop sharing? You can go ahead and stop. I think we're done. If there's no other input today. Okay. Thanks, everybody. We'll see you in two weeks. Bye.


Well, not many schools can say they are the first to have an academic program that will connect Indigenous perspectives with sustainability efforts. Haiti Clotter shows us how Bemidji State University is setting a new standard. In its quest to separate itself from other institutions, Bemidji State University has found a way to connect environmental and Indigenous studies into a new sustainability degree program. BSE was the first public institution to be asked to apply for a Margaret A. Cargo Foundation grant. We're extremely excited about the opportunity to have a degree program that is really rooted in Indigenous values. The program is funded by a three-year grant that launches in January 2018 until December 2020. All of the projects will run during that time with an end goal of continuing after the grant period ends. Now what we're calling it is Guaya Kocha-Gaywin, and Guaya Kocha-Gaywin means making things right. BSU's sustainability efforts examine wellness and economic and social issues. Students will have the opportunity to explore those topics. Undergraduate internships and then graduate student fellowships. So we have two programs for students that will also be through this project. A portion of the funding will focus on hiring a new faculty member who will oversee the program and be responsible for creating the courses. People of the environment Indigenous knowledge perspective course that will be ready for this faculty member to teach because they're going to be like play a critical role in deciding what we do moving forward. Since BSU is located in the center of the three largest tribal nations in Minnesota, the representation of Native Americans in the classroom was essential. I think a student from Oklahoma who wants to be an environmentalist that's from a tribe down there is going to see this article or some of the publications about the program and say oh my gosh this is somewhere I want to be. The From Scratch program is designed to help BSU become a destination university for Native students. In Bemidji, Haiti Clauter, Lakeland News. In 2016 the American Indian student enrollment at BSU was 134 students or 3% of the student body. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


What's going on guys? Got Kyle and Donnie here, latent sports cards, and we are ripping! This is 2023 Tops Archive 6 Series Retired Player Edition 20 box case number 11, Random Division style. We had our divisions here, Tony in with the central AL central down to Brett V with the NL West. Good luck here guys, you can always find those results on our website, latent sports cards at the very bottom. Got a results tab. We got another random hit style after this one with four to go. Four to go guys, interested in that one. Get that going right after this. Good luck on the divisions here. Alrighty, good luck here guys. Good luck, good luck 20 box number 11, random division style. Is that you Bradley? Rag? And let's start it off the way we ended. Raleigh Fingers for the Padres NL West. I'll be Brett V with the Raleigh Fingers for the Padres. I don't know if I've ever seen him for the Padres as a 2016 Throwback Tops. Nice one there Raleigh Fingers, what a mustache there, NL West. Nice hit, Brett. Start off with the 101, that's how we end it, why not? I know Timmy, that is the ultimate stash man, Raleigh Fingers. This one is to 99, it's going to be Gene Tinas for the Pirates there for the NL Central. NL Central Bradley, one is from 84 Tops. Gene Tinas for the NL Central. I'd let you guys know if I was Raleigh Fingers, I swear, I swear I would. I'd be a little bit older, that's for sure. To 25, we got Cecil Fielder for the Tigers there, AL Central. I believe that's Prince's dad, Cecil Fielder there, that one's 11 to 25, 96 Tops, AL Central, no Keith Hernandez. Keith Hernandez got a stash going too man. I would Steve, I would, I would.  Let's go into the NL East Braves, 2011 Bowman Crome, sick looking Tim Hudson there, 15 of 18, NL East. Good luck, Box 5. This one is to 99, Tommy John, Tommy John for the Yankees. I assume that is where the surgery comes from, AL East there, Bradley R, Tommy John for the Yankees. That one is 74, 99, Tommy John, Box 6. I'm going to make a note to myself not to pull any more Raleigh fingers. Get the comparisons going. Alrighty, good luck here, Box 6. We got 1 of 1, it is Fred Lynn for the AL East. That one is Orioles, Bradley there, Fred Lynn on the 1 of 1 Tops collector series. That one is 86 Tops, another 1 of 1. Yeah, Phillip, I moved this one in front because I had a couple spots left. I'll do it right after this, Phillip. Nice one there, AL East. Yeah, we had a couple spots, so I moved it right behind this one. Let me see here. We are full now. We're full now. Perfect, guys. Let's get that one going right after. Appreciate that, guys. Yeah, thank you, Phillip closing us up there. Carl taking a spot in iMac for later, and Powell taking some spots for later. Appreciate you, guys. Appreciate you, guys. Right, let's keep it going. Box 7 to 12. We got George Foster for the Metz. I'm not comparing my stash to Raleigh fingers. To 12 there, George Foster for the Metz, AL East, AL East. I said he's got a great stash. Nice one there, AL East on the OPG. Jared, Box 8. The Copham Super Troopers. That works, too, though. Let's talk about Farva. This one is Coco Crisp, the 33, AL East there. Coco Crisp, 13 to 33. Name I haven't seen in a while. Boston there. That is on a 2009, 2009 throwback. Top's Heritage. Coco Crispotto, AL East. Box 9. This one is 11 to 28 Phil Hughes. Going to the Twins. Second Phil Hughes of the day. This one is AL Central. Twins, Tony. Tony with the AL Central. Box 10. This one is to 87. Got to be Sean Green, AL East there for the Blue Jays. Blue Jays, Sean Green. That one is 1996 tops. Only Sean Green for the Blue Jays. I do remember that, Justin. Holy cow. I do remember that. Yeah, I do. I do remember that, Justin. That's crazy. That's awesome, man. I wish it came back to you quicker, but the Jersey number on that is sick. I do remember that green redemption, man. Good to see you again, Justin. How you been, sir? I do remember that. That's funny. To 13, we got Jim Palmer on the Kmart card. Kmart 25th anniversary. What? What is AL East? That's a Kmart card. Did anybody get a Kmart card? It's tops. 1987 Kmart. Collector's edition. Jim Palmer, AL East. Cal, you ever been to a Kmart? It's 12. I have been to a Kmart. Used to buy tech decks from Kmart all the time. Oh, yeah. Used to hit the tech decks from the Kmart. Oh, yeah. I've seen guys on TikTok. They're still tech decking. Really? Yeah, they do live streams of them tech decking. That's awesome. It is awesome. A mini car. We got one of one. It is Orlando Zapata there for the NL West on the mini from 2021 Allen and Ginter. Sick one there on the mini. Orlando Zapata in the Big Mag. Nice one there. NL West, Zapata 101. It's 13. My blockbuster membership. That was wearing a blockbuster shirt the other day, I think, or Rich was. Rich was, yeah. So 52, we got John Croc. What the Croc? NL East there. John Croc, 7 of 52 for the Phillies and NL East. They're going 14. Yeah, maybe.  This one's going to be Paul Canerco for the White Sox there. AL Central. Top's gold label. That one is from 2001 Gold Label. Paul Canerco. That's a slick looking card. 4 of 7 on the Canerco. You have a Mike Piazza Tombstone frozen pizza card? Let's go. That is awesome. That is awesome, Detroit. Box 15 was not thinking that card existed, but I like that. Yeah, I used to buy cards from Kmart too, for sure. We got another one here. We got the autograph redemption. CC Sabathea. CC Sabathea. We do not have a team on this one. So I guess we'll have to go to longest tenure on these CCs. We did the cardboard connection a minute ago. Did not have a team on the checklist. Yeah, no team on the checklist. Think we'll have to go longest tenure on this one, guys. CC Sabathea. I think that's going to be Yankees, right? Yeah, definitely Yankees. Yankees on the longest tenure. So this one go to the AL East. AL East Yankees. Hey, happy birthday, Frosty. Happy birthday, sir. Yankees there. AL East. He went 10 years on the Yankees. Yankees. Yeah, it doesn't say on the checklist. So we just have to go to longest tenure. Don't know what version, what buyback they're going to use. This one is Sick Larry Walker, 13 to 23 for the NL West.  Sorry, NL East. That one is Expos. I thought it would be almost from 1995 Topps. Larry Walker on the stadium club.  He's got the goalie, the hockey stick. That one will go to the NL East. That one will go to the Nationals by way of the Expos. AL East. This one is NL West. It's going to be Heroki Corota for the Dodgers there, 3490 NL West. 2012 Topps there, Heritage NL West Corota, 18. Yeah, it is a young Walker in Mars. Probably the youngest Walker I've seen. I don't remember him being that young. There's a Greg, Greg, Greg Nettles, 16 of 29. I thought it was Greg. That's a G. Greg Nettles. That's a G. Not pronounced Greg. On 84 Topps, Greg Nettles. Yankees, AL East. Never seen a spelt like that. 19. Okay, yeah, I'll give you that. Yeah, it's spelt like Greg. This one is Expos. Again, go to the NL East. It'll be Andre Dawson, nice one there to 44. The Hawke. From the, what's that, 87? 87 Topps. The Hawke there to 44. Last box. It is Scott Rowland, 9 of 20. Nice Scott Rowland there for the NL Central Cardinals. That one is out of 2008. Topps. Nice Scott Rowland just got inducted to the Hall of Fame. Alrighty there, guys. That will do it for Archives 6 Series Retired Player Edition, 20 box number 11. That was Random Divisions. We will get Number 10 going next, guys. Number 10, we'll go back to the Random Hit Style. Appreciate you guys. Get those cards right out to


From Seattle, Washington, it's theCUBE, covering KubeCon and CloudNativeCon North America 2018, brought to you by Red Hat, the CloudNative Computing Foundation, and its ecosystem partners. Okay, welcome back everyone. This is theCUBE's live coverage here in Seattle for KubeCon and CloudNativeCon 2018. I'm John Furrier with Stu Miniman, breaking down all the action, talking to all the top people, influencers, executives, startups, vendors, the foundation itself, but we're here with two co-leads of Kubernetes at Google, legends in the Kubernetes industry, Tim Hocken and Brian Grant, both with Google, both co-leads at GKE, thanks for joining us, legends in the industry. Kubernetes is still a short life, but still, being there from the beginning, you guys were instrumental at Google building out and contributing to this massive tsunami of 8,000 people here, who would've thought? Yeah, it's pretty crazy. It's amazing, it's crowned. It's a little overwhelming.  How's that feel? It's a little weird. I sort of, I don't buy into the celebrity culture for technologists, I don't think it works well. Yeah, we agree, but it's great to have you on. Let's get down to it. Kubernetes, certainly the rise of Kubernetes has grown. It's now pretty mainstream. People look at that as a key linchpin for the center of CloudNative, and we see the growth of Cloud. You guys are living it with Google. What is the importance of Kubernetes? Why is it so important, fundamentally at its core, has a lot of impact? What is the fundamental reason why it's so successful? I think fundamentally, Kubernetes provides a framework for driving migration towards CloudNative patterns across your entire operational infrastructure. The basic design of Kubernetes is pretty simple and can be applied to automating pretty much anything. And we're seeing that here. There are at least more than half a dozen talks about how people are using the Kubernetes to control plane to manage their applications or workflows or functions or things other than just core Kubernetes containers, for example. And CloudNative is about one of the things I'm involved with is I'm on the technical oversight committee of the CloudNative Computing Foundation. So I drove the update of the CloudNative definition. If you're trying to operate with high velocity deploying many times a day, if you're trying to operate at scale, especially with containers and functions, scale is increasing and compounding as people break their applications into more and more microservices. Kubernetes really provides a framework for managing that scale and for integrating other infrastructure that needs to accommodate that scale and that pace of change. I think Kubernetes speaks to the pain points that users are really having today. Everybody's a software company now, right?  And these things, they build up pain. And when it was just a little thing you didn't have to worry about scale and internet scale and web scale. It was, you could tolerate it within your organization, but more and more, you need to deploy faster. You need to automate things. You can't afford to have giant staffs of people who are running your applications. These things are all part of Kubernetes purvey. And I think it just spoke to people in a way they said, I suffer from that every day and you just made it go away. And what's the core impact now? Because then now people are seeing it, what is the impact to the organizations that are rethinking their entire operation from all parts of the stack, from how they buy infrastructure, which is actually cloud, you see some cloud there and then not deploying applications. What's the real impact? I think the most obvious, the most important part here is the way it changes the way it changes how people operate and how they think about how they manage systems. It no longer becomes scary to update your application. It's just a thing you do. And if you can do it with high confidence, you're going to do it more often, which means you get features and bugs fixed and you get your rollouts done quicker. And it's amazing, the result that it can have on the user experience, right? User reports a bug in the morning and you fix it in the afternoon and you don't worry about that. Yeah, you bring up some really interesting points. I think back 10 years ago, from a research standpoint, we were looking at, how can the enterprise do some of the things that the hyperscale vendors were doing? I feel over the last 10 years, every time like Google released one of the great scientific papers, we'd all get up here inside and say like, oh, hey, when I went to the first DockerCon and heard how Google was using containers, when Kubernetes first came out, it's like, oh wow, maybe the rest of us will get to do something that Google's been doing for the last 10 years. Brian, maybe bring us back a little bit to Borg and how that led to Kubernetes and are we still all the rest of us just doing whatever Google did 10 years ago? Yeah, Tim and I both worked on Borg previously, Tim on the Node agent side and I worked on the control plane side. Borg, one lesson we really took from Borg is that really you can run all types of applications. People started with stateless applications and we started with that because it's simpler in Kubernetes, but really it's just a general management control plane for managing applications. And with the model of one application per container, then you can manage the applications in a much more first class way and unlock a lot of opportunities for automation in the management control plane. So at Google several years ago when we started, Google had already gone through the transition of moving most of its applications to Borg and it was after that phase that Google started its cloud effort and the rest of the world was doing VMs. When Docker emerged, we were in the early phases, Tim mentioned this in our keynote yesterday, of open sourcing our container runtime when Docker emerged, it was clear that it had a much better user experience for the way folks were managing applications outside of Google and we just pivoted to that immediately. Yeah, I mean, when Docker first came out, we took a look at it, we, my node agent team in Borg and we went, you know, it's kind of like a poor man's version of Borglet and we sort of ignored it for a while because we were already working on our open source effort and we were open sourcing it and not really to change the world and make everybody use it but more so that we could have conversations with people like the Linux kernel community when we said we need this feature and they'd say, well, why? Why do you need this? We could actually demonstrate for them why we needed it. And when Docker landed, we saw the community building and building and building. I mean, that was a snowball of its own, right? And as it caught on, we realized we know what this is going to. We know once you embrace the Docker mindset that you very quickly need something to manage all of your Docker nodes once you get beyond two or three of them and we know how to build that, right? We got a ton of experience here. Like we went to our leadership and said, you know, please, this is going to happen with us or without us and I think the world would be better if we helped. I think that's an interesting point. You guys had to open source to do collaboration with Linux to get that fly wheel going for you guys out of necessity. And then when Docker validated the community acceptance of, hey, we can just use containers. A lot of magic will happen. It hit the second trigger point. What happened after that? You guys just had a debate internally. Is this another map reduce? What's happening? Like we should get behind this. And I knew there was a big argument or debate, I should say, with on Google. At that time, there was a lot of conversations. How do we handle this? And that was around the time that Google Compute Engine, our infrastructure as a service platform was going GA and really starting to get usage. So then we had an opportunity to enable our customers to benefit from the kinds of techniques we had been using internally. So I don't think the debate was whether we should participate. It was more how, for example, should we have a fully managed product? Should we have to open source? Should we do managed open source? So those were really the three alternatives that we were discussing. Well, congratulations, you guys done great work and certainly huge impact to the industry. And I think it's clear that the motivation to have some sort of standardization, de facto stand, whatever word can be used to kind of let people be enabled. On top or below, Kubernetes is great. I guess the next question is, how do you guys envision this going forward? As a core, if we're going to go to decomposition with low levels of granularity tying together through the network and cloud scale and the new operating model to have confidence in this, how do we preserve, how does the industry maintain the greatness of what Kubernetes is delivering and bring new things to market faster? What's your vision on this? I talked a little bit about this this week. You know, we put a ton of work into extension points, extensibility of the system, trying to stay very true to the original vision of Kubernetes, right? It is a box and Kubernetes fits inside the box and anything that's outside the box has to stay outside the box. And this gives us the opportunity to build new ecosystems. You can see it in networking space and you can see it in storage space where whole sort of cottage industries are now springing up around doing networking for Kubernetes and doing storage for Kubernetes. And that's fantastic. And you see projects like Istio, which I'm a big fan of, it's outside of Kubernetes. It works really well with Kubernetes, it's designed on top of Kubernetes infrastructure, but it's not Kubernetes. And it's totally removable and you don't need it. And there's systems like Knative which are taking the serverless idea and up leveling Kubernetes into serverless space and it's happening all over the place. And we're trying to sort of pretty fanatically say no, we're staying this big and no bigger. It's a really, you know, from an engineering standpoint, it's much simpler if I just build a product and build everything into it.  And I've got all these APIs, there's all the security issues and things like that. But what I love, what I've heard here is some of the learnings that we've had in open source is these are all of these individual components that most of them can stand on their own. They don't even have to be with Kubernetes, but all together you can build lots of different offerings. So how do you balance that? How do you look at that from kind of a design and architecture standpoint? So one thing I've been looking at is how do we ensure compatibility of workloads across Kubernetes and all different environments and different configurations? How do we ensure that the tools and other systems built in the ecosystem work with Kubernetes everywhere? So this is why we created the conformance program to certify that the critical APIs that everybody depends on behave the same way. And as we try to improve the test coverage of the conformance suite, we're focusing on these areas of the system that are highly pluggable and extensible, right? So for example, the cubelet in the node has a pluggable container runtime, pluggable networks, pluggable storage systems now with CSI. So we're really focusing on ensuring we have good coverage of the pod API, for example. In other parts of the system, people have swapped out in the ecosystem, whether it's Kube proxy for Kubernetes services or the scheduler. So we'll be working through those areas to make sure that they have really good coverage. So users can deploy, say, a Helm chart or their case on a configuration or whatever, however they manage their applications and have that behave the same way on Kubernetes everywhere. I think you guys have done a great job of identifying this enabling concept. I mean, what is good enabling technology and now others to do innovation around it? I think that's a nice positioning. What are the new problem areas that you guys see that are to work on next? And I'll see things are developing in the ecosystem. You mentioned Istio, service measures, people see value in that. Security certainly is a big conversation we've been having this week. What new problem areas or problem sets you guys see emerging, that are needed to just tackle and just knock down right away. The most obvious, the thing that comes up sort of in every conversation with users now is multi-cluster, multi-cloud, hybrid, whether that's two clouds or on-prem plus cloud or even across different data centers on your premises. It's a hard topic and for a long time, Kubernetes was able to sort of put our finger in our ears and pretend it didn't exist while we built out the Kubernetes model. And now we're here at a place where we've crossed the adoption chasm, right? We're into the real adoption now and it's a real problem. It actually exists and we have to deal with it. And so we're now looking at how is it supposed to work? Philosophically, what do we think is supposed to happen here? Technologically, how do we make it happen? How do these pieces fit together? What primitives can we bring into Kubernetes to make these higher-level systems possible? And would you consider 2019 to be the year of multi-cloud in terms of the evolution and trying to tackle some of these things from latency to? Yeah, I'm always reluctant to say the year of something because... Part of the media business. Someone has to get killed and someone dies and someone's winning. It's the year of something. It's the year of something desktop. But... EDI, just saying. I think multi-cluster is definitely the hot topic right now. It's certainly almost every customer that we talk to through Google and tons of community chatter about how to make this work. I mean, you've seen companies like NetApp and Cisco, for instance, and how they're been getting a tailwind from the Kubernetes. It's been interesting, right? I mean, you need networks, okay? They have a lot of networks. They can play a role. And so it's interesting how it's designed, how a lot of people put their hands in there without kind of mucking up the main... Yeah, I think that really contributes to the success of Kubernetes. The more people that can help add value to Kubernetes, more people at a stake in the success of Kubernetes. Both users and vendors and developers and contributors. We're all stakeholders in this endeavor now. And we all share common goals, I think. Well, guys, final question for you. I know we got a break on time. Thanks for coming on. I really appreciate the time. Talk about an area of Kubernetes that most people should know about, that might not know about. In other words, there's a lot of hype around Kubernetes. And it's warranted, it's a lot of buzz. What is an important area that's not talked about a much that people should know more about and pay attention to within the Kubernetes realms of that world? Is there an area that you think is not talked about enough that should be focused on in conversations, press, or just in general? Wow, that's a challenging question. You know, I spent a lot of my time in the infrastructure side of Kubernetes, the lower end of the stack. So my brain immediately goes to networking and storage and all the lower level pieces there. I think there's a lot of policy knobs that Kubernetes has that not everybody's aware of. Whether those are security policies or network policies. There's just a whole family of these things. And I think we're going to continue to accrete more and more policy as more people come up with real use cases for doing stuff. And it's hard to keep that all in your mind, but it's really valuable stuff down there. For programmability, it's like a holy grail, really. Thoughts on the things that put you in the spot there? Yeah, no. I think this question of how people should change what they were doing before, if they're going to migrate to Kubernetes. You know, to operate any workload, you need at least monitoring and you need really CICD if you want to operate with any amount of velocity, right? So when you bring those practices to Kubernetes, should you just lift and shift those into Kubernetes or do you really need to change your mindset? And I think Kubernetes really provides some capabilities that create opportunities for changing the way some things happen. I'm a big fan of GitOps, for example, and managing the resources declaratively using version control as a source of truth and keeping that in sync with the state in the live clusters. I think that enables a lot of interesting capabilities like instant disaster recovery, for example, migration to new locations. So there are a few folks here who are talking about that and giving that message, but we're really at their early stages there. All right, well, great, great to have you guys on. Thanks for the insight, got to wrap up. Thanks, Brian, thanks, Tim. Appreciate it, live coverage here. Kube is at KubeCon, Cloud NativeCon 2018. I'm John Furrier, Stu Miniman. We'll be back after this short break.