Hey everyone welcome back to Six Sister Stuff. Today I'm making chicken and rice bowls in the Instant Pot. So my name is Kristin. I am sister number two from SixSisterStuff.com and every Monday I'm sharing with you a new Instant Pot recipe because if you are new at the Instant Pot watching a video makes it so much easier to go and use your own. So today I'm making chicken and rice bowls.  So I like to use the bowls and I like the sour cream and guacamole on top of it or you can put them in enchiladas, tacos. I even put it on salad. You can use this recipe for so many things. Now if you're ready to make this recipe let's go into the kitchen, get my Instant Pot and make these chicken and rice bowls. You're gonna first start with two cups of rice that you have rinsed and drained so the water runs clear and you'll dump it right into the bottom of your Instant Pot. Add two and a half cups of water right on top of the rice. Now it's time for the seasoning. Now I just added pepper to taste because I love pepper. Then you're gonna add one teaspoon of salt. Next add one teaspoon of garlic powder and then that should be it for the seasoning. So I have one can of black beans that I've rinsed and drained and then add one can of red enchilada sauce. I used a 10 ounce can there. Okay so now I have two cups of shredded chicken. I like to have mine already cooked and chopped up so we'll make this recipe cook even faster.  Now you're just gonna put the lid on make sure that it's on sealing not venting sealing and you are ready to cook it. So I like to use my manual button. That's about the only button I use. I'm pushing manual and because we just have to cook the rice we're gonna go down to 10 minutes. Alright when it's all done I flipped the knob over and did a quick release and then just carefully pull the lid off to where it's still gonna be hot and steamy but everything should be cooked all the way through. Now like I said before I love this recipe because it will work with enchiladas with tacos on top of your salad. You can do all kinds of things with this recipe but I have to say my favorite is the rice bowl. So I like to add cheese on while it's still hot so it can melt then add a little bit of sour cream a little bit of guacamole and then if you love cilantro I love to add cilantro to the top. Alright guys if you haven't checked out my Instant Pot Recipes Facebook group I'll put a link in the description for you. We're almost up to 10,000 people in there who are sharing recipes and ideas. That's all I have for you today. I hope you have a wonderful Monday and I'll see you next Monday with a new Instant Pot recipe. Alright see you later. Bye!


Super. So this is something that we're presenting to you for your information, and thoughtful comment, but there are no specific questions in that that we have at this point. So this is a meeting that's, as Eric mentioned, that we held in early January at the National Academy of Sciences. We actually had a very nice sort of impromptu partnership with Adam Berger, who leads the genomics roundtable there, and very much appreciate his help. That led to this, and we've reported to you previously on our genomic medicine meetings. There's a working group of council that's focused on this. And a few years ago, no, sorry, maybe a year ago or so, began to see increasing numbers of reports from various countries on sort of genomic strategies for healthcare in their systems. The first came out from the U.K., and actually this one's in January of 2012. The European Science Foundation came out with one on personalized medicine for the European system. There was an approach published from Italy. Another somewhat recently from Canada, Genome Canada, funded a number of programs that are moving genomics into clinical care. And it occurred to us that, you know, gee, maybe we should have such a strategy in the U.S. We actually held a meeting in May of last year to try to address that with various agencies, and there's still a number of things being followed up from that. But that was preparatory to really trying to get a number of these countries in the same room to ask, you know, what are the things that you're doing, how can we share, how can we build on what's going on, et cetera. So we sent out invitations, basically said, you know, we're having this meeting January 7th and 8th, and we can't pay your way here. But if you can get here, we can at least put you up and, you know, have a wonderful conference room at the IOM. And we also arranged for them to go and see the genome exhibit at the Smithsonian, which was a very positive experience, I think, both for them and the Smithsonian, and many thanks to events and others for arranging that. We were also very pleased to see we had 50 international leaders from 25 countries with a really nice representation of people sort of outside the Eurozone and the U.S. kind of Anglo axis, which was very interesting and unusual to us. These are the countries that were represented. We all gathered with about 40 genomic leaders from the U.S., including many members of our Genomic Medicine Working Group and NHGRI staff, and spent two days talking about this. And our objectives were much like they were the first time we gathered U.S. centers in genomic medicine to identify areas of active translation and implementation, sort of determine what common barriers might be and how we might overcome them, frame a policy agenda to the degree that we could, highlight nations with unique capabilities. So are there certain things that are going on because, for instance, there's an electronic medical record or those are biobankers, or the other thing, and then potentially discuss some opportunities for international collaborations? What we found was really quite surprising. I think certainly the many of the Americans were kind of thrown back on their heels. Aravinda said he was just floored by the number of things that are going on in some very relatively small and to us out of the way places. Not the U.K., obviously Genomics England announced its plans to sequence 100,000 whole genomes and link them to the medical record in the National Health Service. But in Belgium, there's a medical genomics initiative that's creating a national framework for clinical exome sequencing. In Singapore, they're beginning with a pilot test of sequencing a single gene to test for disease diagnosis in stromal corneal dystrophies, and I'll talk a bit more about this in a moment. In Estonia, there's a plan to sequence 5,000 individuals developing an Estonian chip and offer it to everybody, age 35 to 65 in the country and link it to their medical records. In Thailand, there's a pharmacogenomics card that identifies risk for the top 10 drugs causing Stevens-Johnson syndrome or toxic epidermal necrolysis, which I'll describe in a moment, as well as doing clinical exomes and genomes. Israel is finding a way to push family history data when a case of disease, typically breast cancer, but others as well, when that's diagnosed, finding a way to push that information to their first degree relatives in a confidential and privacy-protected manner to the degree that that's possible so that that information is then available for treating that person's siblings or children, et cetera. In Sri Lanka, there's carrier screening going on for thalassemia and modifier genes. There's a high prevalence of thalassemia in this country, and they hope to convert it to a chronic manageable illness. Luxembourg has a program for early diagnosis and stratification of Parkinson's disease based on genomics. Japan is implementing a three-component, actually multi-component genomic medicine project, including prediction of drug response, efficacy, and cost-effectiveness studies. And there's a genomic medicine alliance that I'll describe for you briefly that's attempting to bridge developed and developing more low-income countries. It actually has over a hundred members in various, some very out-of-the-way places, at least again to us, combining, for instance, eight national ethnic genetic databases from various places like Kuwait and Saudi Arabia and Serbia, et cetera, and economic evaluations going on in Croatia, Serbia, Greece. So we were quite surprised to see all of this. Just to show you a few of them in a little bit more detail, the stromal corneal dystrophies we learned are almost all, or if not exclusively, the ones that have been identified to date. Our genetic conditions, they're caused by misfolding or other abnormalities in proteins that then end up being deposited probably everywhere, but in the cornea, they lead to opacities and blindness. TGF beta-1 is a well-known risk for this, for a particular type of this, and I've forgotten which one, but there are a number of other genes as well. And what they did in Singapore was to identify this problem, identify it as something that they saw fairly frequently, and also as something where they had a willing group of clinicians who said, you know, we want to be able to do something about this, we want to try, you know, identify it preemptively and treat it. We also wanted to identify family members who may be at risk. And so they took it as a sort of a pilot example of something that they could move forward on. So looking at the clinical utility of this for disease diagnosis, treatment selection, and screening of family members, interestingly, this may not be evident on clinical exam, and yet if you're at risk, you shouldn't have certain things done to your corners, such as corneas, such as LASIK, or other such things. So important information to have, this was from Patrick Tan with a Duke collaboration with National University of Singapore. And they identified all the difficulties that we're identifying in our newborn sequencing program and a variety of other things, legal and licensing agreements across institutions and ministries that are complex, reimbursement options for genetic assays that cross medical centers, a general lack of genetic counselors and advisors, a common problem that we've come across here, and official policies on patient consent, incidental findings and aggregation of genetic genomic data. Doesn't this sound familiar? So wouldn't it be nice to learn from the efforts of their Polaris effort, as the pilot effort as they've described. They have this in the field now and they're hoping to expand to, I believe, about 50 genes in the near future. So that was Singapore in Estonia, a program approved by the Estonian Government Research and Development Council just in this past December involves healthcare, educating healthcare professionals, patients, and developing their eHealth electronic health decision support systems. Research and development, as I mentioned, sequencing 5,000 individuals and developing this chip and collaborating internationally. And then some hopes for commercialization in business agreements and IPR, this is from Andres Metzpalu. And so their pilot project is to sequence 5,000 individuals. They estimate that they'll get the SNV actually, the frequency down to about 0.1 percent, minor allele frequency. They would then propose or they're going to develop an Estonian chip of about a million SNVs. And then pilot that with 50,000 gene donors from the Estonian Biobank. The Estonian Biobank has been going on for a number of years now. And they're planning to do that during one year and link it to the primary care provider. Their eHealth database which is extremely well developed, one of the best in Europe, in fact, and decision support software. That's the pilot. Then the main project is actually to offer it to everyone in the country age 35 to 65. They estimate about 75 to 80 percent will accept and they project them. They'll have nearly or roughly 500,000 people in the database who have electronic medical record information, genotype samples, and longitudinal prescription data that can then be both mined for research as well as used in clinical care. As Andres points out, the system could be used as an additional instrument for physicians in diagnosing, treating, and preventing disease. And he refers to this actually as evidence-generating medicine, which is a little bit different from other ways of looking at it. But I think also the term has come into the U.S. as learning healthcare systems or that where one is able to use lessons learned from ongoing clinical care to improve that care in a research format. That's Estonia. Lastly, the Stevens-Johnson syndrome that I mentioned, Thailand has one of the highest, maybe not the highest, incidences of this disease, which they they have referred to and anyone who's ever seen it would refer to as a fate worse than death. Basically, after taking drugs to which an individual patient is sensitive, they proceed to sort of slough their entire skin surface, including internally, the GI tract, the respiratory tract, the corneas, and it's just a horrible disease. They have identified and show here that the prevalence of this, sorry, the incidence of this, hopefully people don't get it twice. But at any rate, these are the accounts that they have seen and in each of these places where there's an arrow, there are genomic markers have been found and utilized as predictive tools by their group. So basically, you can test for these markers and a number of them have been identified through genome-wide association studies and in other ways. And then preemptively, if you're concerned enough about it, avoid having those people get those drugs. So the first of these that was identified, to my knowledge at least, is carbamazepine and the HLAB-1502 variant. And you can see that that has the highest prevalence in this area where Thailand is and then it decreases as you get further and further away from that area. These slides are a courtesy of Boston Chandra Tita from Ramathbodi Hospital. And what they are doing now, in a pilot program, soon to be expanded if it works out well, is basically a pharmacogenetics card. So it's an ID card, essentially, that has the name, you know, first name and family name, the outcome of a pharmacogenetic assay that is run on every patient in this particular hospital. The date, obviously, the pharmacogenetic interpretation and that interpretation in this person is that they have a high risk of Stevens-Johnson from carbamazepine, according to the most recent available information. On the back of the card, then, is sort of the recommendation of clinical action. They have a high risk and if they take that particular drug, if you need more information, ways to contact that laboratory and the signature of the molecular pharmacist. So this is something that really, I think, captured people's attention and said, you know, this is a wonderful, wonderful idea to deal with a dreaded condition. And in fact, they have done some very nice cost-effectiveness analyses. Shown here is an economic evaluation for severe adverse drug reactions, pointing out that the cost-effectiveness ratio for universal screening in that country, where obviously the incidence is much higher and the minor allele frequencies are higher, at about 222,000 Thai Baht, which is about $7,000 per quality adjusted life year, gained for patients with epilepsy about half, a little more than half of that for patients with neuropathic pain. That is considerably below many of the interventions that currently are approved and used in the United States in terms of cost per quality adjusted life year. And interestingly, and I thought what was compelling here is that they only need to test 343 patients to prevent one case, which is really amazing. On the patients who are scheduled to get this drug, it would be much lower in a setting obviously where the incidence is lower. But again, this was something that I think really captured people's imagination. So having looked over a variety of these things, there was agreement that the products should include a base structure, a white paper, that sort of thing. We would like to continue international collaboration and communication through a variety of working groups and a steering group. We recognize that the leadership must be multinational and we're looking for leaders and volunteers. We had five breakout groups, which were the five working groups that you saw there minus the communications group. We realized communications was something we needed to add. And I've just shown here some of the top ideas from there's an IT Bioinformatics group that wanted to define key elements to be stored in the medical record, identify robust solutions. They were very interested in a global resource for actionable variants, which could build on our ClinGen resource that we're developing here within the U.S., an education group that wanted to propose defining workforce needs, developing tools that could be shared, including region-specific teaching materials. This links very closely to the work that we're doing with our inter-society coordinating committee here in the U.S. and there was great interest in trying to expand that beyond just the U.S. The evidence generation group, we had initially thought that they would propose large-scale collaborative evidence generation project, however that might look. And what they said actually was that there seemed to be enough going on that we probably want to first stop and kind of take an inventory of those catalog existing projects. Not a simple task when you consider the world, luckily there is a project funded by the European Commission, the EuroBio Forum, personalized medicine observatory, which is something that we might be able to build on. They are basically cataloging these kinds of projects in Europe, so might there be a way to then expand that to look beyond Europe and include others. We'd like to identify poolable or extendable projects and develop systems to capture evidence through the systems of routine clinical care so that hopefully it's not adding on too much more burden and get so much more generalizable population. In pharmacogenomics, Alan Shuldiner stood up and said, you know, we should try to basically address global eradication of Stevens-Johnson toxic epidural necrolysis, which would be a challenging thing to do, but wouldn't that be cool if we were able to do it? And I think there was a lot of enthusiasm for at least exploring how that might be done, at least in places where it's highly prevalent. And the pharmacogenomics card, again, was something that was quite attractive, I think, to many people. In the policy arena, obviously we need to share efforts in consent and results reporting and also, I think, a strong endorsement for studying economics and cost-effectiveness. I should mention that there were several groups that we were aware of and that we became aware of doing work like this. One of them is the Genoic Medicine Alliance, which is organized by George Petrinos from the University of Patras in Greece. And what he has done is basically managed to pull together a whole huge number of both developing and developed countries to encourage multidisciplinary collaborative research, facilitate introduction of pharmacogenetics, propose guidelines and recommendations, and develop and coordinate educational activities, all things that all of us are interested in doing. This is their website shown here. And one of the things that I think impressed us was that in some of these smaller countries, they had a certain nibbleness and flexibility to be able to move forward that we were quite envious of. And we're a little bit concerned that should you bring in some of the larger and more pondersome groups, you may remember in the 60s that the Bambi meets Godzilla film where basically you sort of end up with ruining the very thing that you are most enamored with. So we need to figure out how best to do that that would not really inhibit their ability to do the things that they've done so well. So our next steps were to distribute a meeting summary, an executive summary that's just been done over the weekend, establish a steering group and working groups, engage and leverage related groups, and we recognize the Global Alliance for Global Health is a group that's working particularly in the data sharing realm. We had hope to have representatives from that group at the meeting, but that didn't work out and we're hoping to make contact with them. We have tried in terms of how we might be able to work together going forward. The International Rare Disease Consortium is another group that's been suggested and the European Personalized Medicine Alliance, I think it is, is another, but there are obviously several others. We would draft a white paper, or circulate it to the group and hopefully submit it very much like we did with our first Genomic Medicine meeting. We'll share this information with other NIH institutes and centers and encourage their participation as we're encouraging their involvement in many of the Genomic Medicine things we're doing. And then the Genomic Medicine Working Group now feels a bit like we have a tiger by the tail or maybe a couple of tigers following the great success of the efforts in professional education. We have the Inter-Society Coordinating Committee that is keeping us very busy. We also have a number of collaborations from our May meeting with the federal agencies with the interactions with the FDA and with CMS and others. And now we have this group and so we're going to sort of regroup and try to ask ourselves what our priorities should and could be and where we might go from here. Before we have another meeting that gives us another tiger. So any thoughts that you would have on that would be most welcome. I think Howard, maybe since you were at the meeting I'll give you an opportunity to comment and then open it. Thanks, Jerry. It was a great meeting. I think there was not only was there a lot of evidence that things were going on across the world but there was very clear desire to try to have a United Nations of Genomic Medicine except more effective than the one in New York. And really trying to not reinvent things and the beauty is a lot of these things will be led by other countries as well as us. Not just the U.S. as its thing and other people are welcome to tag along. And so I think that was it was pretty clear that people were going after this in a very in the same spirit. Really not that different than a lot of the genomic things over the past while the HAP map, the SNP consortium, all these other things in the past where people just wanted to get things done. And so I think that was exciting. The other piece is that a lot of these things would not require a lot of money. There would be some amount of coordination and there would be obviously some stat, in a GRI staff time but it's people weren't didn't come to the meeting looking for money. They looked for it for collegiality, camaraderie, but more importantly really working together to solve these problems. So I think that part was was great. There the number of problems are immense and I think I think if you know we just can't take it all on but if we take on something like eradicating Stephen Johnson syndrome. Right now, there is still polio in several countries in the world. It's increased in Pakistan over the last years but the concept of eradicating polio caused countries to get serious and go after it. And so just the concept of eradicating an adverse drug reaction that's genetically driven will cost people to think about it differently than they do right now. It's just all it's part of the price of doing business whereas it could be wait a minute that's a preventable disease and let's solve it. And so I think we can change the language with this kind of a group. And often it might need the rest of the world helping remind us what to do in order to help change us. And we always bring an outside consultant to tell your bosses what you've been telling them for years. And this might be a similar situation with other countries helping us see straight. Great, thanks. Yes, sir. Terry, has there been an attempt to engage the World Health Organization? They've been very interested in tracking. I can remember the late great Roger Williams was actually on the Swiss air flight. Meeting when it went down in the middle of the Atlantic and trying to track people that have all the various mutations one to identify an indexed case. And I wonder if they might be in a unique position to help organize this worldwide instead of a very western Judeo-Christian look of the leadership. Yeah, no, that's a good point. Actually, Roger's efforts in the MedPed program which we're identifying of familial hypercholesterolemia heterozygotis were incredibly effective in finding cases. But I agree that would be one group we haven't reached out to them yet. All right, hold on there, Jane. I'm mindful of the need to keep council caffeinated in the fact that the cafeteria closes. They say 3.30 but sometimes they're doing that. So why don't we take a 15 minute break, be back here no later than 3.10 and we'll resume with the H3 Africa report.


what's up guys my name is glassfoot so no review this week um i kind of just wanted to make an update video um more over on uh where i plan on taking this channel in the future what i plan on doing next year um and kind of just where my life currently is so um i like that a little bit better um so i just moved out of my old apartment um which is more of a cottage into my current apartment um where i am living on my own i don't have any roommates uh so i should be able to get uh videos out a little more faster um i'm working on a star wars video uh right now that is going to be um like a video on why eight episode eight last jedi isn't that bad i actually think it's a fairly good movie sorry that noises my cat in the behind the camera messing with stuff um i'm probably not gonna film with her in the room very often this is bryit she is my she is best key and cutest one she also has had her acromia which is freaking dope in my opinion but okay go explore um where was i uh star wars um i'm working on a uh a video on legion of superheroes right now i plan on keep doing the critical reviews those aren't gonna go anywhere i very much enjoy doing them and i like the whole editing process that i have with them um i'm going to start doing more analytical type reviews of movies and video games and tv shows uh to get honestly to uh just get better at editing and doing more content that i want to i plan on doing um some dnd style stuff uh that kind of like explain the rules maybe i'm honestly not sure where i want to go with that i just i felt i needed to get a video out this week um so i apologize for the not very edited nature of this um probably a couple of cuts here and there but uh yeah i i felt i need to get a video out i wanted to tell you what was going on uh kind of where i was um where i want to take this channel in the future i do plan on putting more vlogs up uh honestly maybe just once a month i don't know how often i'm gonna do those they take a little bit more time for me to do uh more over that it's just it requires longer filming and then a little more editing um and just i working almost every single day i don't have a ton of free time to go out and do things to film for a vlog i'm hoping that come 2019 i'll be able to get more content out to a little more frequently other than just my reviews of newer movies that are coming out i can do older stuff um and i hope that you guys enjoy what i start putting out um just in general i hope you guys enjoy the more the longer form that i'm gonna start doing the yeah but yeah i kind of just felt like i needed to do this um this is also more for me of a way to track where i want uh what videos i want to do in terms of like like going forward but so uh my camera battery's about to die so let me just quick uh sorry quick i was editing didn't really like where that video was ending um basically i want to start putting out a little bit longer form content um and i'm planning on doing that with some frequency so um you can expect longer reviews of tv shows and movies definitely potentially video games you can expect more vlogs to be coming out maybe not with a ton of frequency but hopefully maybe once a month i can put something out there um and i'm going to just make content that i enjoy making that's why i started this and that's what i'm gonna keep doing um but yeah i hope you guys have a great and i'll see you guys whenever i post a new video peace out


one thing is very rarely addressed and this is solar cooling and for heating with solar energy we always have the contradiction that when we need heat most in the northern or very southern latitudes the sun is not very strong and in the very hot climates we often have excessive sunshine and that's why solar cooling is a good choice and it's actually on the market but it's not very visible so far and so have a look at that and one word to air conditioning for air conditioning the key issue is humidity it's not the cooling energy itself but it's to make the air in a range of moisture that is good for the house so dehumification is very important and if anybody of you is very interested in this issue Professor Schmitz here from THH is an expert in this and maybe some of you have followed classes with him


Drums and sharing can be heard all across Lake Bemidji as practices kicked off for the annual Dragon Boat Festival. Josh Peterson takes us into a practice as team prepare for the big event. For 13 years the phrase paddles up has become a signature term at the annual Lake Bemidji Dragon Boat Festival. Each evening this week teams will gather to get some much needed practice before the race day this coming Saturday. These practices are important in that the steers people are awesome in showing them the technique of how to paddle on a Dragon Boat. It's not necessarily like you would paddle in a canoe. Each Dragon Boat team is given two practice time slots. For many these practice sessions will be their only opportunity to find their teams rhythm. We have some drills that we take them through. We do one called a hesitation drill where at the end of a paddle when they bring their hands up it's a pause and then they paddle so that brings everybody in time together. For this practice session many of its participants haven't been in a Dragon Boat since last year's festival. For many groups it's a great team building experience. We've got lots of companies that use this as a great team building activity.  But when it all comes down to it the Dragon Boat Festival is all about having fun. For team captains only having two practices is no big deal. I really think so partially because everyone knows each other somehow either their co-workers or their family or some of us who get together through the Tuesday night practices. So everyone's kind of got some sort of chemistry. But you don't need a team to paddle. Anyone that wants to try it out is welcome to sign up. We still have teams looking for paddlers boats that aren't full. So if you're interested in getting on a boat and you might not know a team or you might not know a company that's short you can go to the Dragon Boat website and sign up as an individual paddler. With a week full of activities Dragon Boat organizers are looking forward to another year in the record books. In Bemidji, Josh Peterson, Lakeland News. If you'd like to paddle on a Dragon Boat team we've posted the link at our website lptv.org slash news or you can check in at the registration tent behind the Carnegie Library. If you enjoyed this segment of Lakeland News please consider making a tax deductible contribution to Lakeland PBS.


Welcome to All Hands Update. I'm Petty Officer Tony Rosa. These are your headlines from around the fleet. The November 4th election will be here soon, so now is the time to register to vote. The Federal Voting Assistance Program, or FVAP, has the resources you need to vote in the upcoming election. You can register and request a ballot in an easy one-step process. Just submit the federal postcard application. Eligible spouses and dependents can vote absentee as well. Go to fvap.gov and exercise your right, privilege and responsibility as a citizen. Its fiscal year 15 and new general military training or GMT courses are available. The new bystander and intervention training will replace the GMT requirements for fraternization and hazing. This realistic, pure-led instruction will help sailors recognize potential negative situations and how to safely intervene. Mobile training teams will visit commands worldwide to train instructors starting in November.


Hello everyone. Good morning and welcome. My name is Navin Joy. I'm a Cloud Architect with Cisco Systems, and my topic is this. So we will be working on and analyzing some Cloud Network architectures today. Know your presenter. I've spent 17 years in IT, primarily on IT operations, networking, system administrations, 15 years. Last two plus years, I've been involved in development, Python hacking, got to know quantum open stack, deployed a private Cloud, and today I want to share some of that experience. So I've been using Cisco UCS in my environment, but you can use any general purpose system as you please. It's not a problem. So we have all been in the trenches a lot, woken up at 3 AM, 4 AM, helping our customers troubleshoot problems. So let me ask you a question. What is the most important thing to us all? You got it right. It's sleep. So we want to design and build stable and reliable infrastructures. At the same time, as much as we want to automate, do software-defined networking, and all of those cool stuff, we want to be able to go home and be able to sleep knowing that our customers are happy. I would like to get to know you just so I can tailor my presentation a bit. So how many are new to open stack networking quantum? If you can raise your hand. Okay, great. So hopefully this talk will enable you to go back, take some architecture designs, and test it out in a small environment and see how it works for you. How many are experts in quantum? Great. This talk is not for quantum experts anyway. So this is a traditional enterprise network architecture. Most of us have deployed in our workplace today. How many are running this traditional hierarchical network environments today? Good. So it doesn't have to exactly look like this, but some form of fashion. You have different layers, compute, storage, networking, and you do some VLAN management helping out users with provisioning ACL and things like that. That's how most of IT works today. But going forward, the Cloud has actually thrown a curve ball at it. In the sense that IT needs to be delivered as a service or users are expecting more and more control. IT as a service, so you need some programmability capabilities and things like that. So users have to do self-service. They want to be able to talk to the networking here. They want to be able to provision their own virtual networks, VIPs, and things like that. So we want to be able to help them out, and OpenStack Quantum is a way to be able to do that. You don't have to do a complete rip and replace of the infrastructure. You don't have to spend a million dollars implementing something like that. I will show you how you can take some of the capabilities of OpenStack Quantum, try to implement in your network in a very controlled fashion to get some of that benefits. What are some of the most desirable Cloud network features? I just, as I was building and designing networking, I just thought about it and about four or five bullet points came to me based on my experience and my interactions with my users. Users meaning my developers. Elastic scaling is one thing, which means that if I have to scale my network, I have to scale out. It should be as simple as scaling out my compute. I should be able to horizontally scale, add more nodes and scale. I want to be able to invest in my infrastructure incrementally, and then balance that cost against my demand. I want to be able to scale, commensurate with demand. I just don't want to scale up and invest a million dollars or something like that. So I want to be able to do that in a more controlled fashion and that should meet my demand requirements. I want APIs for programmability. Back then when I was a network engineer working down in the trenches, my applications guy used to come to me and say, hey, Naveen, why do you have to do Vips? Why do you have to create VLANs? Why do you have to do all of that? My application, I want to be able to do that, give that control over to me so you can do better things like architecture, design, more of the backbone stuff. So at that time, I did not have quantum. So I had to tell him, I would want you to be able to do that, but there's no way by which I'm going to give you complete root access into my networking here. So that was the only answer that I could tell him. Otherwise, if he were to use CLI or anything of that sort, things would change.  It didn't work out. So there were constraints then, but now you can solve some of that with quantum. Reduce complexity. So what used to keep me up at night was that if something fails in my network, it's so complex that, how do I know where to go and look? Because solving the problem may take five minutes, but looking and figuring out where the problem is used to take about half an hour. So I want reduce complexity in my environment. And at the same time, I want to be able to reduce the complexity for my end users as well, the application developers. I want to be able to expose some very simple abstractions that my developers can use to program the network. Consistent policies. Today we have a multi-vendor environment. The policies have to be consistent. We have a lot of regulations such as SOCs, HIPAA and things like that. So if you are implementing a security policy or things like that, it has to be consistently implemented for all users. It can't be just broken here and there, manual things. I've seen that in a lot of environments, people say that our policies are implemented, but the ACLs are all not implemented correctly. So that's a problem. High availability again, especially at the core. You don't want to just wake up again in the middle of the night. So these are the five key features that if you are an architect looking to design a cloud network, should always have it in front of you and make sure that your design meets these requirements. So now what are the challenges for an architect? So when I was thinking about these, the following questions came to my mind. So how does a conceptual network architecture look like, like a bird's eye view of a cloud network architecture? Is it possible to transform some of my existing network infrastructure while preserving my investment? Nobody wants to raise their house down and rebuild everything from the scratch to add a few new features, right? You wouldn't want to do that. You would want to just add everything incrementally as and when your budget permits, right? Automation and things like that. Similarly, is it possible to add quantum into my existing network without doing a million dollar investment or doing a complete rip and replace? It's not going to work for most organizations today. It's not practical. And how can I implement networking as a service by using OpenStack Quantum in a reliable manner? I don't want to use the latest and the greatest features and then stay up all night, but I want to do so in a very reliable manner, testing out and moving incrementally one step at a time. So we will find answers to most of that questions today in this talk. So this is an architect's high level view of how a conceptual network cloud network looks like.  What do I mean by that? So these application developers don't want to deal with a whole lot of details. They just only want to know just enough information to be able to talk to these APIs and as a result program the network. For instance, to give you an example, a good abstraction is that create a network for me. They shouldn't be able to say create a network with VLAN ID 10. That's a bad way of abstracting information. You want to hide that VLAN ID and things like that within your implementation detail that is plugging behind that API, right? Because that's important because if a VLAN ID is exposed to the application, tomorrow you may replace it with, let's say VXLAN ideas, things technology changes. At that point you'll have to go and re-architect your application which is not feasible. So you'll be stuck. So choosing the correct properties for abstracting your network is very important. So we spoke about programming your network. So what enables programmability? It is this network abstraction that enables programmability that my application developer who doesn't know much about the network can actually use these abstractions to program it. What is it about? It's about simplification as we saw earlier. It's about hiding the unnecessary details only exposing what the application needs to know to the end user. It defines two roles, client role and an implementer role. What is a client? Client is just a piece of code that talks to the APIs and the implementer as you've seen is a piece of code that sits behind the APIs and provides implementation details. And the key thing here is that the implementers can change without causing any changes in the client code which means you are keeping your API abstraction constant. So your client code is the same and you can, as your network evolves and changes, you know, you're making some changes here, doing some new things, you can change out the implementation of the backend. So this helps to make both people happy. The network engineers can try out new innovations and try out new backends and your frontend application developers are also very happy because their program that creates a network still is able to create a network. It just conceptually looks like this. And in quantum, the client is a quantum client and the APIs are quantum APIs and the implementers are quantum plugins. I don't want to complicate this, but this is the abstraction model as defined by quantum. It defines high level of network, exposes some properties of that network to the end user. You can see, for instance, you can set a state, right? Admin state, up or down. You can just give a name to it and you can associate some subnets with the network. So everybody can understand the application developer can understand and manage this abstraction model. And then you have the notion of a subnet, some kind of an IP subnet CIDR thing here, host routes and also a port which is actually the attachment point from a VNIC to the network. So the simple abstraction and some properties that could be set. And if you show your developer this model and say here is your abstraction model, write your application around it, he'll be happy. This is a logical architecture view of quantum. How does it look like? One is that you have at the, I tend to view of this in three layers. The underlying network infrastructure layer, where you have your network devices, your physical network gear, your virtual network switches and things like that. All of the networking here, interconnected networks down here. And the quantum network service layer, you can think of it as a software layer that just envelopes your network, right? And quantum implements this abstractions using which your client applications can control your network or do programmability. You can program your network. So today you have abstractions for L2, L3, load balancer is there in Grizzly, firewall is coming up, VPN is coming up. So all of these services can be abstracted and exposed to a client application. So the application doesn't need to talk to a device A or a device B or million different devices in the network. It can talk to a single API endpoint. And that could in turn talk to all of those devices to realize that abstraction model. And there is also a database that's used by the plugin to maintain the state, its view of the network. How do I view the current state of the network to be? So this is a combination. This is what we'll be talking about. How to get this implemented on Cisco UCS platform that I've used, you can use any gear that you want the approach is the same. Now I've been playing around with quantum software architecture for some time. I've got a chance to look at it deep down and this is how it looks. So there are several components, it's not complex. You can see a quantum API server. This is a server that exposes the front end APIs to the client applications over here. And then when the client makes a call, the API server in fact routes the client call to a back end implementation, which is the plugin module. Okay, so far good. And then the plugin module, what it does is it takes that request and then converts it into a message. You can think of it as a message or some piece of bits together and then sends it to what you call as the RabbitMQ. What RabbitMQ does is it knows one thing, takes a message and then it knows how to send it out to a queue. It receives and sends out messages. So that's what happens here, a message is sent and then there are different agents that are running on the endpoints. For instance, if you want to plug a VNIC into a network port, so then the open VSwitch plugin agent, this guy, he receives a message saying, go ahead and do that job through this message bus. And this guy has a driver here, which is the actual code that does the programming of that switch. So one cool thing about this is that the components you can see are loosely coupled. What do I mean by that? Let's say tomorrow something happens and this agent dies. Is it going to cause your client application to hang here? No, that's because these components are loosely coupled. The RabbitMQ will buffer those messages up and keep it. So as an administrator, you don't have to wake up in the middle of the night or even if you wake up, you can sleep an hour and then wake up and restart that agent. It will go to the queue and the queue buffers all the messages, picks up and starts processing. The end user doesn't care. It's in the middle of the night. As long as before he comes up in the morning, if his network is all built, he's very happy. So you can just wake up maybe at six, seven and then restart that agent. It will start processing the messages from the queue and then start building the networks. So this is the asynchronous coupling that's very important in any cloud architecture deployment.  If it's a single box, everything sitting in there it's not cloud scale. It's not asynchronous coupling. And similarly, you have agent programs that does DHCP layer three and load balancing, the same model.  The virtual L3 agent picks that up, creates a router. So that information is sent in the message. This is another architecture enabled by Quantum. So you can see that depending upon the plugin that you use, you enable different architecture models. Here, you may have an SDN controller, an external controller and that controller could be a Ryu controller or Cisco one controller that's going to come up. So you can place that controller behind the Quantum API using the appropriate plugin. So when the client API makes a call or the client makes a call to Quantum API, that call is routed to the Quantum plugin module, which in turn will drive the controller. And the controller will use a remote control protocol, such as OpenFlow or any proprietary protocol to program the actual switches to realize that abstraction. So this is another model, the SDN model that is enabled by Quantum. Now the question is, how can Quantum be used to deliver a network as a service? A very simple solution. This is a very simple solution that I think is very stable. It's a single network solution. If you want to test it out in your environment, if you have a Cisco UCS environment, you can try to deploy that.  Here the administrator has created a Quantum network named Hosting. He has also assigned an IP subnet. And what he has done is, he has connected that network with a VLAN in this environment. Here in this case VLAN 10. And that VLAN is trunked to his existing gateway router. So this network is now available and it's exposed to the tenants. So tenants don't, they don't have to deal with networking. So when they create virtual machines, this network will show up on Horizon GUI that you have created and they can just click it. And their VMs will be launched. So this is a very simple model. If you want to start playing out, playing around with Quantum, you can just create it, create a virtual network as an administrator, map it to a VLAN, and let users create VMs there and play with it. A very simple, stable deployment for Quantum. Leveraging your existing, a redundant gateway router. So again, you're not going to receive that call saying something failed because it's all handled by your reliable infrastructure. All you're doing is just, you have just created a virtual network and you've exposed it. So how do you scale it? Earlier on you saw that you had only a single network, just created a single Quantum network and then mapped it to an existing VLAN. You can scale that. You can create multiple Quantum networks if you want. You may have different user groups, your HR group or finance group. You can trunk that to your existing gateway switch. And then either you can keep these networks as shared networks, in which case all of your tenants will be able to see that on the horizon GUI. Or you can map it to a certain tenant if they're very picky about the fact that they don't want to share networks. So in that way, they will only see their own networks, that the networks that they own. So this is another way to extend and scale out the previous model by connecting it to multiple VLANs in your environment. Leveraging your physical, reliable gateway routers and switches that you have already without doing a rip and replace. All you're doing is Quantum mapping, creating a virtual network and mapping it to your VLAN. It's as simple as that. Now some of your tenants may not be very happy. They may want to create their own VMs, maybe some researchers and things like that, QA groups. So you can give them some API control in which they can create their own networks, virtual networks, in addition to all of the shared networks that you have created.  It'll be totally separate. So in this way, you can keep some of your tenants who are very picky, very kind of happy. So you have deployed shared networks for those of your tenants who don't want to deal with networking and those who want to deal with it, you give them some control in which they can create their own networks and manage it. So again, it's a scale out model with some tenant control against stable, reliable because you are just leveraging what's out there. You're not ripping and replacing or introducing some heavy duty overlays and things like that that could go wrong without central monitoring, right? So that could be a problem that will require a lot of night work. So this is just for research if you're using Falsum in the way that you can use virtual routers. The problem in Falsum is that this model has scalability because Falsum restricts you to a single network node. So all of your outbound traffic will have to be funneled through a server node on which the routing is deployed.  So all of these virtual routers are nothing but Linux stack. And then the advantage you get is that you have a routed connectivity. You're not dealing with VLANs anymore. So you have a layer three connection from your gateway network node to your gateway router. This is your physical router, right? But this is just purely for, again, has scalability and availability issues in Falsum. Grisly will resolve this so you can have multiple scale-out network nodes much easily. So just play around with this if you want to in your lab environment. And then you can create as an administrator multiple tenant networks and then assign tenants and place tenants behind these virtual routers. So you can tell them that this is an experimental network so they can just play around with layer three capabilities now. The advantage that the tenants will get is that they'll be able to do some floating IPs. So floating IPs are nothing but NAT translations mapping a public to a private. And they can play around. They will get some advanced capabilities with this that they can use. So you have seen several models, about three. So how do the previous models compare with networking in EC2? It's almost similar, right? So basic networking in EC2, you go ahead and launch an instance and it connects to a network. You are not controlling. You're not creating a network. You're not creating a subnet IP and all of the, it's all abstracted away from you. So that's what it is. That's a model that you've enabled using Quantum and leveraging your physical hardware. So in this case, it's very similar to the default Amazon VPC model. And that's what the tenants will see. And they will appreciate that because it's very similar to what they already know if they have some instances on EC2. So now this is for your real advanced tenants. If the tenants want themselves, they want to create routers and isolate their environment, right? So this is something, again, in Falsum, it has scalability and availability issues. So you give tenants the ability to create their own virtual routers and place their own networks behind that router and completely control that isolated environment. And you can think of it as a virtual private cloud, a layer three separated cloud for a tenant. So this model is similar to an Amazon VPC model. In Amazon VPC, which stands for a virtual private cloud, as a tenant, you can create your own isolated environment. Create a place, your subnet behind a router, connect it to an Amazon gateway and get internet access. So that model is the previous one, the tenants creating their own routers, getting gateway access, creating floating IPs, then security groups and things like that, right? So that is just for testing currently in Falsum, maybe in Grisly and maybe in Havana, it'll be ready, I believe. So how do you design your network to support quantum? You have seen the various models that quantum enables, but how do you design your network for quantum? So before you design networks, you should ask the first question is, how many networks do I need? And the answer to that is, you will have to analyze your traffic to see how are the traffic flows and you may want to group all the similar flows together. So far here, one set of flows is that the traffic generated by OpenStack components themselves, the AMQP, the rabid MQ traffic, the MySQL traffic, know what to quantum API, all of this management traffic, you want to isolate onto its own network because you don't want, when the network goes down, you don't want to be able to not to SSH or your monitoring system to go down, right? So you want to be able to build a separate VLAN or something of that sort for this network. Now, application traffic between VMs. So the VMs, they communicate, the tenant VMs communicate with one another. For some reason, maybe that web tier is talking to a database tier or an app tier or something of that sort. So the VMs themselves send traffic, so you want to be able to isolate that. So you have to provide a network for that. Then VM communication with the internet, the floating IPs and things like that gateway, you have to plan for a network. And the traffic generated by tenants interacting directly with quantum API. So if you want to expose your APIs out to your tenants, so the traffic generated by tenants. So there are four different networks that come into play, management, data, API, and external. So here's a network that I'm, so this is how you would deploy a test quantum in your environment. So you build these four networks, external API, data management, and these are all your servers. One server is your controller server. You run the API, NOVA API, controller, or RabbitMQ, MySQL, and the quantum API. And you have the compute nodes, the nodes on which the VMs will be spun. This is where the NOVA compute runs. And the network nodes, these are the network gateway nodes if you're planning to do that gateway kind of an architecture. So all of these nodes will need connectivity to the management of course, right? So data network is for VM to VM traffic. So the VMs are spun here on the compute nodes. They will need to go out through the network nodes gateway. So you will need both of these guys to connect through the data network. Then APIs are for your end users to talk to your environment. So you will need your external router to connect your API network, and you will also need your API server to connect your gateway network. So your tenant sitting here on the internet can come through the gateway and talk to the API. Then you will also need the network nodes to connect to the external network for gateway access. So this is something, this is how you would wire up your compute network, quantum APIs, gateways, and things like that to get some minimal or small setup going. So that concludes quantum now. How about load balancing as a service? That is coming up in Grisly. A brief overview of a load balancer. So load balancer has a VIP. A VIP is not just an IP address. A lot of people think it's an IP, but it has a combination of an IP, a port, and a protocol.  These are just the virtual machine instances. And you tell the load balancer to basically distribute traffic to these pool members. And you can also attach a health monitor to a pool. So the load balancer has enough information to check the health of your instances. So if an instance fails, then the load balancer will be able to take that out of load balancing and send traffic to the remaining instances. So these are the basic abstraction models that you would see in the upcoming load balancer. In Grisly. So you have built this earlier network, right? So how do you incorporate that load balancer into this network? So you can do that in two ways. One is you have already deployed this router, which is nothing but a Linux stack. And you have the ability to run HA proxy in there. It's like kind of running a multi-service appliance, right? You have an appliance that can do multiple things, routing, load balancing, and things like that. So you can turn up a HA proxy in here and then turn that routing module into multi-service appliance. That's one way of doing that. So in this case, you have also created a web tier and an app tier behind the virtual router. And you are telling this load balancer, hey, whatever traffic that comes in, here's a VIP. You just balance traffic to one of these pools. So you create a VIP for each one of these pools and balance traffic. So this is called as an embedded mode of load balancing. So you will see that in Grizzly. Another way to do it is inline. So if you have a dedicated load balancer appliance tomorrow, you can also insert that and attach it to your external network and then do inline load balancing. So it is kind of, traffic is not flowing through that multi-service gateway appliance anymore. You have a dedicated device that does load balancing. So what are some of the key takeaways from here? So you have to always design to handle failures. So you don't, again, going back, nobody likes to stay up at night, although we are all good people and we want to help everyone, we have to minimize that. So you have to always design to handle failures, especially when quantum you have that pluggable architecture module. So you want to make sure that what you plug in is also designed to handle failures, otherwise it could be a problem. Quantum is built to handle failures, but that plug-in that is sitting here is not designed, it has a box at the back end, that's not a good design. So when you sit down to talk to your vendors, you may want to ask this question, is your plug-in designed to handle failures? Is there a single point of failure? That's a key question. You want to loosely couple your components. That's important because if one component fails, you don't want, again, to wake up in the middle of the night and try to fix that. Let it just relax, let it die, maybe tomorrow at six a.m. or seven a.m. before my users get in, I can restart it and it'll start processing messages, loosely couple, it can pick up. There's something, there's a queue that stores all the messages, so nothing is lost. Things are down, but it can wait, unless it's, of course, an emergency. Implement elasticity, so you want to always scale out and not scale up, which is very important because you want to invest in your infrastructure incrementally, rather than just investing a million dollars and buying a huge, big solution. So those are the three key takeaways from this talk. Closing thoughts, quantum is evolving. Production deployment and operations is still very hard, so you want to just plan and take only those features that are thoroughly tested, reliable, and also use your redundancy that's available in your existing infrastructure, because there are some things that are missing today. And the plugins that you use must be architected for the cloud. It's not just the quantum, it's the entire solution has to be architected for the cloud. Be aware of the L3 scalability and reliability issues in quantum, in Falsum release, so make sure that you only do some testing with this, so you just get a feel of it, so you can plan for a reliable L3 deployment in the upcoming releases. Research and start slowly, because that will pay. So you learn from your experience, rather than going all in. Document your work and contribute to the community. Doesn't mean contributing code alone. You can contribute your designs, your experience, and anything that you want, your architecture designs, blueprints, everything counts here. And that concludes my talk. Thank you very much for attending. Any questions? Yes. Where do the agents run? Yeah, so these agents typically run on the network node. If those agents are networking agents typically, so you have a class of nodes called the networking nodes that basically all the traffic going out of your virtual network environment will be routed out through the networking node. Basically it's a server, and that's where you will run all the agents. And there is one specific agent called the open V-switch agent, which is a switch configuration, right? So that V-switch is there in pretty much every node, each and every server. So that agent has to be run everywhere. So it depends on where you want that functionality to be provided, so you'll have to run that agent over there. Yes. Separate device, yes. Is exactly, yeah. That is a separate service. That's called as the L3 service. And load balancing is again a separate service called the LBAS. Those are all different services. Yes, today with load balancing, what's supported at least in the Grizzly release is just the HA proxy, the Linux load balancer. But going forward you can see load balancing solutions from multiple vendors being supported through their own plugins. It will, the virtual router plugin will run on the device where you want to create virtual routers for your gateway. So those classes of devices are called network nodes.  You will have to allocate a few nodes that you can scale out called the network nodes. That's those are the nodes that will run your virtual routers and the virtual routers will be the gateways for all the VMs that you create. So it's a separate class of nodes called the network nodes and that's where you would run the L3 agent. Yeah, two questions. Okay, go ahead. It is protocol aware, absolutely. It's an IP address, it's a protocol and it is a port. Those are the three things. So you can say I want to load balance for a certain protocol, for instance, TCP, port 80. And it's also aware about some of the application level details such as persistence. So it can look at cookies and source IP addresses and things like that to say, if I have a certain cookie in my request, I want that request to always be sent to one of my servers because that server is doing some in-memory processing or something of that sort. Please don't load balance that request out. Yes. Yeah, I will, absolutely, yeah. It's just got confidential but don't, that's there in all the templates. Yeah, so the challenge that I had with Nexus 1000V is that it's still being kind of engineered to be supported in a KVM environment. The ones that is available, you can end up seeing the plugin and you can talk to the VSM and then control multiple 1000Vs. So just have to wait for 1000V for KVM being available. Yes, that's a good point. RabbitMQ supports active, active HA. So the idea is that you can run two RabbitMQ nodes and virtually combine them logically as one RabbitMQ. You may want to do that scenario if you're doing production. So RabbitMQ, active, active HA, this very clear documentation that's available on RabbitMQ if you do a search. You can just follow that step-by-step procedure. One last question? Yes. Yeah, so in that case, you will have to set up your routing on your physical infrastructure to say, right, pointing into that virtual router but then you will again have a problem of overlapping. You can't support overlapping IP addresses for your time. Yeah, so that's possible, yeah. Okay, thank you very much.


and Come back. I'm gonna refill my water. I might get a snack It's been about three hours Just I had my other snack and then we'll come back and start progression. I think I got enough to craft some bullets We're gonna try to get this this plankerton node knocked out because we have to do pump up the volume So I have to do three more Relay survival missions, so I'll be right back. Thanks for watching you guys are the best We don't anybody tell you different I've been rocking this uh This battle tech soundtrack But where'd it go? Oh No, I had I had a tap for that There is I've been rocking the battle tech soundtrack for um For my breaks and stuff. It works pretty well. I'll be right back Thanks for watching So I breep I'm back chat. Thanks for waiting. All right, let's get right to it switch over to Change Mr. Jonesy I'm gonna get right into our progression. I'm new to save the world and was wondering if you could help me out No, dude, I can't help you. I'm sorry What guns do I have? Hydra is my best gun. I was given some guns since I'm new. I Was given a nocturne typewriter But I don't have that many of them So the best schematic that I'm rocking right now is is Hydra You can see from the title. I'm only like 24 So I'm really really new in terms of progression Although I've had the game for a really long time I didn't play it for a while because it was making me sick with all the screen shake and they recently fixed that So I was really happy to be able to come back to the game Nope, don't want to trade. I don't really have anything. Does that mean I played Battle Royale? No, I didn't really play Battle Royale.  I want to get this I want to get this leveled up any of these mats Box with a host thanks, but thanks buddy. I was gonna call you muddy because I said I was gonna say thanks man And thanks buddy and it came out as thanks muddy You're not muddy pots. Thanks, man. That other host appreciate it So you're playing Warcraft Warcraft 3 customs It's muddy much give her it's muddy I'll be all right Is that noise? All right, let me get some blue glow So I can least be helpful on that front. Hi guys one Gotta conserve bullets man. I'm low on mats So I'm using the pistol as much as I can That the that that So here's my inventory. I have a dragon's roar. That was a gift Definitely not my schematic You should pay attention to this side over here rather than what's in here And I got some nocturnos that were given to me That's about it and no I'm not interested in trading we did it blue glow in the house You want grave cool? I've heard of grave They're trapped underneath So, yeah, I'm just trying to make sure I'm very paranoid about my nuts and bolts now I'm not gonna buy that many bullets from a hydra because it's about to break and I don't have the mastercraft another one The crafting of the hydra I Need I need sturdy mechanical parts and I need a lot of blast powder. I think don't you get blast powder from caves? I think I remember it being there. Oh grave digger. I Don't you just make grave? Yeah That was good too. I'm trying to use those guns if I can help it like I break them out when I'm You know you get the bosses and stuff, you know because it drew a building Started building at the ten minute mark. I guess wrong gun Not a mimic. Yeah, you can craft blast powder. I thought They auto-crafted required stuff Maybe I'm thinking of another game. I thought if you had the mats for the required thing It would just auto-craft it. Maybe it does. I don't know what's going on chat That's probably gonna be good enough Put some traps down You thought this game was free. It's going to be free. It's still considered pretty much early access T. Yeah, T. I guess I could just throw these cheap ones down here. That's it. I don't have any more Yeah, whatever and then there's one of these Wall traps I have these I don't need that and I got the spikes but the spikes aren't gonna help there. I Can craft some more. I don't have the schematic for darts Yeah, I melted the green one down. That's fine. I guess It's muddy Well pretty much this campaign Funded BR and now BR is like a trillion dollar industry seems like for those guys. So End up being very smart investment. They can fall through here. Can't they yep. I have like no floor traps come at X I don't have any I guess I should focus on get some of those. Oh, I mean I picked up some here, but It's like they're all crap Well, that may not break that one again They fall in there. That's gonna be funny Still kind of odd to me how BR exploded. I know, right It's kind of crazy No, I think it was though. I think it was it was a perfect storm because call of duty and CS go Halo and Battlefield where it lows So I think it was a perfect storm of all of that. I think it was a perfect storm because everybody is like all the CS go people all the halo people All the call of duty people they were just like all at the same time Switching to BR There's like H1 Z1 was a big benefactor of that in this heyday.  I think I don't know. I just made one tunnel It may or may not work. I don't know That goes literally nowhere Here they come Didn't count on that That'll work. I don't know why I put that one there. Goodbye Hydra. You're about to break No, oh it broke switch to a nocturnal These are all great guns. I don't want to use these getting getting getting kind of heavy loud noises Dropper camp fire Yes, all weapons in the game do have durability except your pickaxe now. I can't get in there. Thanks You get the schematics from found this back You can recraft them That's the thing. There's a difference between Schematics and actual weapons So yeah, the ones you get from the founders will eventually break, but you can recraft them But they give you schematics going back to the fire. What fire am I my seat? Oh The pain Yeah, the key in this game is the finding schematics People trade all the time for temporary weapons, which I personally don't understand because I Don't know I Guess if you want a gun I Guess temporary is good enough, but they basically trade the the ones that the great trading materials makes sense, but