All right, the recording is on. All right, thank you. Hello, everyone. Welcome to the weekly TSC call. This is a public call. Everybody is welcome to join and participate. There are a couple of requirements to doing so. You must be aware and live by the antitrust policy, the notice of which is being displayed if you're online. The other piece is the code of conduct. So please be aware and live by those. So we have a couple of agenda items. There's an announcement first. I don't know if Jessica is on, but she asked me to echo an email she sent out a little while ago on the TSC list and a bunch of other lists as well. There is a marketing opportunity. The Hyperledger team is organizing webinars. So each project has the opportunity to put a webinar together. It can be of two different kinds. There is the one hour version or the 30 minute version, one being more hands-on, demo kind of oriented. And so there is a requirement for people to have the backup of a sponsor, which has to be a maintainer of the project you intend to present for. But other than that, it's a great opportunity to put educational material for your project out there and get the whole communication team of Hyperledger to socialize it through social networks and the likes. So if you're ever interested, there is a form for you to go and fill out to get the process started to submit a proposal. If there's any questions you can contact Jessica and well, anybody around the team, I'm sure can help you get to the right people if needed. All right, so we have received a quarterly report for Hyperledger Indy. It came in a bit late. There is no rush. I saw that a few people, a few among us had the chance to look at it. Nobody raised any issues yet, but I'm happy to carry that over to next week. There is no, you know, there's nothing in the report that calls for some immediate action. So I'm very comfortable doing this. Let's just keep it to next week. There are two main items for the agenda today. One is I would like us to make a decision with regard to the proposal to move the beef lab to a project and then later we can talk about the common maintainers management policy issue. Regarding the first, I don't know how much people want to discuss and ask questions. I saw, so following up on the TSE call last week, Hart posted on behalf of their team behind the proposal, a fairly extensive email trying to provide additional information and answering some of the questions that had come up during the calls. And then Peter sent, posted some slides yesterday. Is Peter on? Yes, Peter, if you want, I can give you five minutes to go over your slide. There's really one slide. And if you care to do that, I can accommodate. But I really don't want us to spend too much time. I'd rather we focus on trying to come to a decision as a group. So if there's anybody who has an urgent question, you know, before they can make a decision, obviously, if you have some still the need for clarification, you will have an opportunity to do that. So Peter, you want to present your slides? Oh, I was just posting those slides on behalf of Fujimoto Sun. So I'll forward your question to him. He's also in this call, right? So, right, if you click on the latest slides link in front of you there, that will get you to the email from Peter. And there there's the attachment. It's a very simple day. There's really just one slide. The first is the title. And so do you guys want to talk to this slide? Shingo, would you like to say something? Yeah, he's got his hand raised. Oh, yeah. Yes, please go ahead, Shingo. Thank you for this single for Fujimoto from Fujitsu. This slide is showing that as a response to the previous meeting, the request, we need to show the use case and non-financial use cases like the simple use cases. So this one is showing to the token ratio and marble, the ratio will be integrated as one single service. And actually the main member of the BIF agreed to provide this example as an implementation as an example of the BIF. So you will see that this one is in a few months later are the workable that is only the same for the slides. Thank you very much. I'd like to take your questions. All right, thank you. So I don't know if people needed that, but hopefully it adds to the picture. So now with in mind the fact that I'm going to call for a vote on whether we should approve this proposal to create a project out of the BIF lab or not, it does anybody have any questions for the team here? I don't know, this is Angelo. I have more a question for you actually for the other TSC members. And this I've seen also in the emails that are in the thread of emails. I don't remember who was questioning which are the actual criterias that the TSC will use to make a decision on such a move. So I would like to ask the others or the other TSC members about which are the criteria that we should use to evaluate this decision? Because I'm a bit confused. So it's depending on this criteria, I might take a decision. I will definitely, to me I'm not convinced by the proposal but depending on the criteria, I might change my decision. All right, so we don't have to directly answer your question. We don't have a document that defines the criteria. What we do have is what is called HIP Hyperledger Improvement Proposal which is a template document that people are being asked to fill out that provides what was considered to be key information to make this decision. And they have done that. This is what's linked from the agenda, the first sub-bullet blockchain integration framework beef proposal. That's the Google document that follows a template that provides, as I said, key pieces of information. This template was put together at the beginning of Hyperledger. Nobody has asked for this to be updated or questioned it. So that's what it is. That's all we have. But we have Chris here who has even more history on this than anyone else. If Chris wants to add something, I don't know. No, I mean, you've pretty much said it. There really isn't, you know, it's kind of like the definition of obscenity when we see it, I don't know. But I'm still, I gotta say, Hart, I saw your note and I appreciate it, but I'm still, I looked again at all the use cases and they're coin, coin, coin, coin, coin. There are two non-coin use cases. And I'm still struggling, maybe it's just my, I'm just not sort of getting it, but I still don't see what the difference is between this and Quilt. Sure, I mean, I'd be happy to explain that in more detail. Quilt is, you know, specifically using, it's using a very specific mechanism, I guess, to do inter blockchain transactions, right? Where's the BIF is totally pluggable. And I guess, again, in our document, I guess we've probably presented too many token applications, but the point is it's flexible. You can do anything you want. So is there something, so Hart, can I just, can I just add something real quickly? Sure. So Chris, my interpretation of this is Quilt is a protocol about a very specific kind of transaction and a very specific kind of asset. BIF is really an SDK. It doesn't tell you what a good application is, but it does allow you to create these applications that involve transactions that span blockchains. So when I read it, I read it as an SDK for building something. Some of those some things are gonna make sense and some of them are not gonna make sense. But that SDK itself is something that I think is pretty valuable. So, I mean, again, as I've said a number of times before, as I've said a number of times before, I think that if we were going to try to come up with an SDK that could be portable from one platform to another, then you can write clients that they don't care what's behind the curtain, right? The APIs are all exactly the same. And the implementation of how you do consensus and whether you use a Merkle tree or whatever irrelevant. So from that perspective, I mean, it's the one place in our architecture that I think makes sense to start working on. But I think that we need to walk before we can run. And so now we're putting together a SDK that you're intended to plug stuff into the back end. And I suppose that's one way of doing it. But I would think that it would be better if we can come up with the model that says if this is our data model, this is our model for how transactions are made, then we should be working to get the frameworks to adopt that model rather than try and shoehorn in things that don't necessarily fit. If you follow me, I mean... What do you mean by shoehorning in things that don't fit? When you have to build in a shim and implementation of a driver that's going to make the back end calls, there's an assumption made that the models are basically, maybe not isomorphic, but they're extraordinarily similar. Right. You're going to have a situation, I think, where you're going to be trying to adapt a platform. And its SDK, its protocol, its APIs are going to be a square peg for a round hole. There's a big difference between the kind of SDK that Chris talked about before, which was to have some kind of common SDK that allows you to plug your application to different networks. And this actually implies that you're talking to multiple networks at the same time, right, doing these kind of transactions across networks. Well, I think that's a secondary thing. I think that comes afterwards. I just, I don't know.  And the last comment I made was, I still think that it makes sense to make sure that everybody, all the maintainers and the contributors to these various projects are essentially bought into the same model. And I don't know that we're there. I don't know that we're even trying. So, you know, I guess sure. But I just think we're. Yeah, I agree with you totally that the best possible solution would be if everyone agreed to a common data model. But I'm not sure this is even a reasonable thing to ask within Hyperledger, much less outside of Hyperledger. Like, you know, a lot of the business applications that say, you know, Accenture does involve Corda. Are we going to be able to get Corda to collaborate on a data model with us? Are we going to be able to get Ethereum to collaborate on a data model with us? I hear what you're saying. And yet at the same time, I'm also very mindful of the fact that the integration happens at the application level, not the blockchain level. And so in a sense it almost doesn't even matter what the underlying data model is. But one way to think of this Chris is that this is your application level SDK. I mean, yes, it's not sitting on the client, but this is how you build your application. And the criteria that I would ask you for is not, is it a perfect data model? The question is really, is it useful? Is it useful for building applications? And I think the reality is we're not going to have consistent data models. It's unrealistic to believe that there's going to be an effort among the maintainers to coordinate that kind of activity. So the question is, how do we get usefulness out of this? You've got two companies that are Well, but I mean, okay, I hear what you're saying. And yet at the same time, let's say I'm trying to do the food interoperability use case that's in the white paper. Let's assume I'm doing that. And organization A's blockchain uses GS1 data models and organization B's uses ed effect. That's the application data model. These things are not the same. There are some ontologies that try to make them somehow rather somewhat interoperable, but that's a huge thing. It's not just some smart contract. It's a whole right. Well, to go farther on that from the identity side, we've learned that having different data models is actually a big advantage and one of the drivers behind having separate chains. So it's not about just telling everyone they have to follow the same data model. And so this adapter type approach has a lot of business value and application value because it allows you to have loose coupling between the ledgers while still having some sort of, you know, agreement between the two systems about how translation between one and the other has to occur. And so there are ways of making it so you can validate the other ledger state natively on your chain. I think some of those are stronger from a trust architecture standpoint, but it's clearly there's business need for this as a, as a solution with the companies we're seeing sponsor it and having this kind of tool set to make those types of adapters gets us closer to those steps that I think are farther along in kind of how we evolved this in terms of interoperability going forward. And I don't think the intention is to solve every one of these data model problems. I mean, because you're pulling out something that's an extreme example, it may be common, but it's extreme. The question isn't, can we solve all problems? The question is, is it useful for solving some problems? Or maybe enough problems to justify being a project? And, and, and I think that's probably the case. Sorry. Yeah. So to follow up on that, I wanted to keep and try to give some answers to, to Angelo's questions about, you know, what are the criteria? I mean, the kind of information we've been looking at before to try to assess whether, you know, we should approve a proposal project proposal like that. We're things like, of course, you know, does that fit within hypervisor? That's an obvious one. But beyond that, it was like, is there enough support to make it a viable project? And I think, you know, having two companies was always considered to be a good sign, which is the case here.  That's, that was the whole idea of lab. They are very cheap to, to have projects are more expensive. They, they are under the governance of the, the TSE. And there is, you know, they have all these resources are located to it in terms of the IT infrastructure, but also, you know, communication and so on. So like the security audits, all these things cost money. And that's why there's a difference between just a lab and a project. So hopefully that helps a lot. Yeah, I don't know. I think the same. And I was thinking to myself, I was asking my, to myself, why, why then hypervisor fabric private chain code is still, it's still a lab project. So it has a massive amount of source code. So it has sponsored by two companies, IBM Intel. It's very, it's full. So there is code there. You can run something. So, but this project is just a proposal. It's sorry if, if I say that, but it's very questionable because it doesn't say how to solve the huge problems.  Thank you. That's, of course, that's a tautology. We can plug privacy, but how? I mean, you are, that's a hard problem. How to make, how to, to, to realize privacy, you know, that's the hard problem. So to me, if we accepted this to become a project, maybe there are also other projects that needs to become automatically project other labs projects that needs to become projects automatically. So this was my, my, my, this is personally what struggles me to understand. So either we set criteria precisely. There is also in terms of a code availability. So for example, it's important that there must be something running that they should this, they have to show. We have to pretend them to show a game. Give us something. You say that this is useful. Give us something that we can evaluate and say, oh yeah, you give us something that is showing is promising. It's going this direction. Notice also that fabric private chain code. Now, of course, I'm, I'm sorry, I'm, I'm from IBM. So maybe I'm, I'm, I'm definitely biased, but there is also a publication accepted at the, at the conference. So the, the, the work has been also being reviewed, which I don't see for this, for, for this project. Okay. But Angelo, so let, let me say one thing first. The private chain code, you know, there's not been a request made to the TSC to turn this into a project. I think in fact, if anything is going to, you won't hear one. Not to distract, but I think the point was nobody said no to FPC. So saying that FPC isn't a project. Therefore this shouldn't be a project doesn't make logical. Exactly. That's beside the pot. So let's leave that aside just for the sake of it. And then the, you know, so then there is not going to be more specific criteria for you to make the decision. I gave you as much as I can. If anybody else has additional information, please go ahead and provide it. But if fundamentally, you know, if you believe there's not enough, well, then you shouldn't vote in favor of it. That's just the way it is. And by the way, this is a lab, right? So, you know, people may decide, you know what, it's not, they haven't convinced me that it's, they have made, they have enough to be worthy of a project yet. And we can say, you know what, keep making progress as a lab first, show me that you can actually achieve something. And then we'll talk again about making it a project. That's a reasonable position as far as I'm concerned. So, and at this point it's up to every one of us to make their own call. So let me turn again to everybody before I call for a vote. If, does anybody have any other questions they need to get answered as much as possible before they make that decision? This is Troy. I was putting into the chat that I think the difficulty is evaluating earlier projects or projects that have less sponsors. So the decision seems to become very subjective. And I haven't really resolved that issue at least for me. Yeah. No, but that's true. And I mean, I've pointed that out before and I think heart was frank enough. And he said, you know, if anything, hopefully this will make it more visible and attract people to the table. One of the challenges they have is they want to create this like super API kind of thing. And they want to have as many people involved early on as possible so that they don't have to redo it as people become aware and interested and come in and say, yeah, your API is good, but not quite right for me. Can you make it so and so and so. And every time they have to refactor everything. So I can understand where they're coming from. But that's the way it is. So any other questions or remarks? Otherwise, I'd like to go. I think looking at this as a portfolio decision, which is not something that we necessarily do, but we feel like we need more kinds of projects that look at integrations or look at ways to stitch things together. And so it should never just be a blank check that if you, if you're trying to solve that problem, you get in as a project. But we don't have a lot of strength in that area right now. And we could say that we do have quilt, but I would not put all of our eggs into the quilted basket to make some metaphors. That's all I have on that. All right. Anything else? Any other wise comments? Well, let's try again. The other comment I made is I still see struggle with this labs designation. And, you know, this bullying category of labs versus projects seems to be a bit problematic. I'm interested in that. Why is that a problem? It just seems that maybe project or lab projects are seeing an advantage from being a lab. And I guess the key concern I saw in the proposal was they don't want to just be a lab. So I don't know what to do about that, but it just seems like a problem. Well, we can ask them what, you know, again, hot. Maybe you can speak for the Tracy for the group on that one. What's the primary motivation at this point in time to try to move from a lab to a project? Tracy, would you like to talk or should I? I mean, I think it really does come down to the community. Right. Getting the, the wide diverse set of opinions and contributions to the community that maybe we're not getting currently as a lab. It feels to me like some people on this call are saying labs are bad, which I, I don't think is the case, right? Or they're lesser in some way. I think it's just a way to start begin or to start building that community. But, you know, I think there's a obviously, you know, we weren't getting this kind of discussion before we brought it up as a project proposal, right? We weren't getting the opinions, the people looking at it in a different way until it was brought up as a proposal. So, uh, yeah, that's, I guess where my brain is right now and heart, please add to that. Yeah.  And, you know, we, it would be, you know, easier for us if we could just do that once, uh, in hyperledger and didn't have to like do it now. And then, you know, do it later. It's some other status and change everything if we became a project. So, so some of the tooling is, is also a reason, but, um, Yeah. I think Tracy said it. All right. So with that said, I would like to call for a vote. So, um, would like to make the motion to call, to approve because that's the proposal, uh, moving the blockchain integration framework lab to a project. This is Dan. I second. Thank you. Okay. So we're going to call for a vote. Right. Uh, Angela. No, I'm against. I know. Actually I'm going to abstain and I'll comment a little bit because it's not to come on to abstain, but, uh, I'm really torn and, and on the one end I feel like, yeah, this sounds like interesting enough that it might be worth a project at the same time. I feel like a bit more work could be done in the lab, especially since there is two code bases, trying to show a little bit how you integrate those things already would be a good first step. And I'm hoping that having raised this already as a proposal will have given it more exposure and attracted more interested parties that you can actually at least achieve some of what you were trying to achieve by moving to pro to project. Chris. Well, I guess I'll say, okay. Um, I want to say non-committal or something. I don't know. I, I, I. I'm not overly thrilled with it. I mean, I tend to be very skeptical about any integration, but, um, I don't want to get in the way. Okay, Dan. Can I just say approve or do I have to? Sure. Okay. Gary. I don't know if Gary. If I can get him off of his other call. I have him. I have one slack. Hold on. He said on the chat that the, let's move on and then we'll see if he catches up. Hart. Yes, Mark. Uh, yes. I hope that will bring extra visibility and, you know, that the team will welcome more input from a wider diverse audience. Okay. Yeah. Yeah. Yes. Yes. Yes. Tracy. Yes. Troy. I'm staying for the same reason as I know. Um, so I was just chatting with Gary who's still on the other call and he says he's not against it. So is that a yes. Yes. Yeah. It's really simple. Like yes, no. He says here, are we voting on the Biff and he says, I'm okay with that. It seems like there's no harm. Okay. So I think we're done. There's no objections. There's only approves and a couple of abstain. So therefore the motion is passed. Angela. Yeah. Angela voted against it, but. Oh yeah. Yeah. Sorry. Yep. You're right. My bad. There's one vote against it. But so that's done enough. Okay. It's not unanimous, but the motion is passed anyway. Mazel tov. Thank you. All right. Okay. Congratulations. Let's move on. So I, I would like to continue the discussion. We started a little bit. And I tried to. Put a bit more meat around the bones. In putting up together an issue in the decision log. And at least a few existing policies regarding how the projects are maintaining. Or managing their maintainers. Least. And there are variations for sure. The issue for me is, you know, in keeping with what we try to do with the common repository structure. Is, you know, trying to provide some consistency across the different projects. And to be clear, I don't mean necessarily that there is one policy that's very like, you know, constraining and that's adopted by everybody. I think at least I would like to have some basic policy that would be the default for projects that do not have one. And, you know, happy to adopt whatever sounds reasonable. And, and then, you know, maybe it will influence some of the existing projects to have some to, to, to align their policy. And then, you know, I think it's bad that so many projects do not document how maintainers are being, you know, elected or selected. And, and so at the very least, we should have some kind of documentation of how this is being managed at the project level. And so as part of that, we have some kind of documentation of how this is being managed at the project level. And so as part of that, we have to kind of define, you know, what are the key elements of management policy that you would expect to find in that, in that kind of policy. And so at this point, I don't have a specific proposal again. I just started the, the, the, the, you know, trying to gather information about what the current state is. I only found like a handful of projects that actually are found, like a handful of projects that actually have one. So there are quite a few projects for which I even found any, I don't know if they have one. If you do, there's a list there. It's, you know, it's a wiki. You can update the page. And once we have gathered enough, I think we can start putting together the elements that are common and maybe what is missing and what seems to be reasonable. And together we can kind of start building what seems reasonable, you know, and, and again, we don't have to decide this is the one and only one, but we can at least have some common ground. So that's the premise. And this is what I'm trying to achieve here. I saw there are several people have actually started commenting on the issue. Thank you for doing that. I would like to open it to everybody to discuss and share what they think about this. No, no takers. I have to say, I will add, if you look at the list, in fact, there are three different ones, different policies. We have one for Bezu, which is actually, I have to say whether you agree with it or not, it's very well written, very detailed, and they explain exactly the process they go through. Fabric is a pretty good one, too. So-tooth is a good one, too. But then, you know, all the other projects are basically, we're built out of so-tooth and they all share the same. And I don't mean to say it's not as good as the others. I just want to point out that, in fact, we don't have so many different variations. We only have three different types of policies in the works today. In use today, I should say. Yeah, I think so. This is Chris. Oh, sorry. Go ahead.  No, you're good. Okay. So I was just going to suggest. That what really needs to happen here is that we get the maintainers of the various projects together, like we did in October. And virtually, obviously. We're not going to let them, let them hash it out and come up with something rather than us telling them what it is. Does that make sense? No, but we have. A lot of us how maintainers too, right? Yeah, that's true. But not for every project. That's true. Okay. Yeah, I was going to. Yeah, I was going to think, I believe Gary commented on there and it made a lot of sense. That we have some kind of like core. Policy that, that people can adopt. I mean, sometimes we need like a slightly different policy. And I mentioned Ursa as an example there. Where, you know, You want to sort of break out into like types of maintainer and other stuff like that, but I think Gary's suggestion was excellent. And. You know, that, that sounds like a good way to go. So it's Gary on. I'm here. Can you hear me? Yes. So to speak up to this. Yeah, I mean, I guess what I was sort of proposing was it was kind of all on the lines of what you said. I thought that maybe we could at least have a set of, you know, a couple of like standard. Types of policies at least like what, you know, the. How do you become a maintainer? Right. Like, you know, what's going on here? Here's, here's that you become a maintainer. Here's a retirement policy. Like there might be like maybe three or four different types. Like I guess attributes, we can call them attributes or whatever that might be in the policy that people should have. They could know off one if they, if they say, hey, we don't have one for that. But that was the, that was the basic concept, right? Pick a couple of these standard things in a life cycle of being a maintainer and say, Hey, this is what you should at least document. How you do it, right? Here's how you become a maintainer. And it, you know, if you do X, Y, Z and it requires a majority of the maintainers to vote for retirement of a maintainer or whatever we want to call for inactivity. We define inactivity as this amount of period. And again, it's a vote of majority. You know, and maybe if there's something, if there's not maintainers available for something, I don't know, you know, we could. So, I mean, there's at least two. How to become one and how to retire one or make one inactive. That at least people would, you know, that that would be kind of the standard that we would have. And you could pick your own, how you want to do it, but you would at least document those two, at least those two processes of the maintainer. There is one that's not covered here explicitly. And I don't know if that was an oversight, but a Roja does their maintainer elections in GitHub chats. And for the group like a Roja dash iOS dash maintainers, they have a discussion there and they vote there. I know back when we had Garrett, you know, you, you could vote there on it to make everything public. And, you know, you can make your argument, but yeah, I'm totally in favor of making this as explicit as possible. And right. Do you know if there's a documentation about their process somewhere? No, I don't. We have anybody from the project on who could speak up to this. So I think that. So what are we saying? Are we saying that we're going to have a framework that you need to have? How do you become one? What are your responsibilities? How are they removed or retired or whatever is that? I think what we're, what Gary was saying is that at least we should have, you know, a requirement that every project has a policy that's documented that that and the least of items that you expect to be covered in the policy. A framework, right? Exactly. Yeah. I'm good with that, but I guess coming up with that framework, I mean, maybe it's not that hard. I don't think it is because we already have some, so, you know, I'm happy to. But I still think that you want some buy-in from the main thing. We want to impose anything. I'm not hearing that we have to have a unified one. Yeah. Okay. But I still would like to. It wasn't unified. It was, I think it was to say, one, you should have a policy. Here's some common policy stuff that we expect you to have. And you can do it. And we can, you know, like, like our government likes to do, we can make it a recommendation, but not a mandate. Right. I like Chris's idea of bringing it to the maintainers, but I think, you know, we are a technical steering committee. We are not a technical governing board. So there's a balance we have to do there. Yeah, I can see us saying here's some guidelines that we hope projects would follow and steer them in that direction versus thou shall have all of these covered. Yeah. Well said. I kind of like that. And are we also making a recommendation as to where that policy is defined? I mean, we see there's a number of different places here. Well, it's for us to decide. Personally, I actually kind of like the basic approach. I actually kind of like the basic approach, to be honest. To have it in the maintainers file. Yeah, I like that. I think at least having a link from there, if it's not there, is an obvious place you look for. Another thing worth noting about our maintainer policy is we also do our governance on GitHub. If you want to add someone, you do a poll to the maintainers and the discussions and the votes are in the GitHub comments. So it provides a semi-permanent record for it there too. So we're kind of like a Rohan in that sense. Fabric is the same. Yeah, because it's the easiest way to get a voting mechanism and an auto log, as you said. So at least we could point that out as a way to do it. Right. And that might influence those who don't have a way yet. And not like, how do we do this? Whether they reinvent the wheel every time they might say, hey, that sounds like a reasonable way. Let's just do this.  I really believe that a lot of the disparity we have, the variations are more accidental than, you know, intended. It's just because there is no single way to do it or not even a recommended way. So people say, oh, we should do this. Let's invent a way. If we even showed one way as a possibility, I think people would naturally adopt it at least for a new project. They don't have one. So I'm going to suggest that I'll take a stab at creating a PR against the TSE repo. And we can review that for next go round. Oh, that's great. Thank you. And I mean, to get back to Chris's point about getting the maintainers involved, I agree. And I think once we have at least the beginning of an answer, we can definitely, you know, highlight it to the maintainers app to send an email to the maintainers list and tell people, Hey, we are working on this. It will impact the way you work. So you might, you know, if you care, please comment on the proposal. And so we can include them in the process. Speaking of the, the. The hypernager repo. Right. I know you were working on this for the, the document. The governance document we're supposed to start putting together any updates on this, the repo exists. I would defer to Brian on that. Yeah, that's, that's on me. No progress on that yet. Okay. All right. So I think anything else we want to add to this question. I think we have a plan. Thank you. Tracy for volunteering. If nobody else has anything to say on this yet, let me ask, if there's anything else somebody wants to bring up before we close the call, we have 10 minutes. And I don't think anybody minds closing 10 minutes early. I'm happy to do so. But if you have a burning needs to share something with the TSE, now is your chance. All right. If not, then I'm going to call it. So thank you all for joining and we'll talk again next week.


So, the talk I wanted to do today was about heat and how to build environments with heat and actually go deeper into building scalable and highly available environments. And so, I'm going to start a little bit with presentation and then we're actually going to go into Hensown Lab where you're going to have to team up because there's quite a few people here. And you'll try to launch a stack and see how that looks and how that actually works. I was going back and forth into, okay, so what do I want to talk about? Do I want to jump in straight into tools and like talk about all the, you know, okay, so that's what we use for load balancers, that's what we use for databases and what not, or do I want to start slow? And when they actually scheduled the stock as the first one, I figured I'll start slow and kind of give you a general overview of heat and other tools. And there's a lot actually, there's a lot of talks in the summit about heat and what it does and there's, right after this one, there's a talk from actually heat core developers about the new features in Juneau, which are really cool. So if you are interested into orchestration, you should definitely go to that one. But we'll start slow and so when we deploy applications in production, they go through multiple stages. So the first thing, before you deploy something, you have to get infrastructure, right? So you have to get some environments, well, some VMs, so some compute, network, storage, all of that to run. And well, after that is set up, typically you would install operating system, you would install the platform services, they are often called platform services, it's just databases, maybe web servers, maybe anything else that your application needs, but it's not actual application code, it's maybe it's PHP or Python or Django, whatever is your preferred, whatever your application requires. And then after that, the next stage is actually deploying application and artifacts here is typically the application code itself, there's config files and at this stage, we also typically configure HA for those applications. When we have them up and running, or during configuration of those applications, there's some changes, some extra configurations to HA tool that happen. And then there's the work, so your application is up and running, it's all good, it's great, it's working, hopefully it's working for a while and hopefully this work stage is longer than the rest of them, it's ideal. And here there's a lot of data that gets collected, so applications write logs, they produce metrics, history, and the actual data. And again, hopefully they run for a while, but at some point, almost every application fail, it doesn't necessarily mean it's a faulty application, it just, that's life. And here ideally what we want to know yet is we actually want to know when the application failed, so we could either manually react to it or the tools that we use or the tool chain we use for monitoring could trigger some events to fix the application. Sometimes if it is an application fault, you have to patch or upgrade or do some code writing. When we talk about availability for applications, there's the most common, you would hear a lot of things like active passive HA or active active HA, what's the difference there? Well, the difference there is that for active passive, even though you have multiple instances of application, there's only one active, there's one working. And the other one is deployed, ready to go, but it's not working. So when our main master application fails, the reaction is to start the second one. Active active, both of them work, both of them work simultaneously. They accept requests for data you want to replicate or synchronize data between them. And when one of them fails, the other one still works. And that's an ideal solution for us. So when we look at this kind of application in production lifecycle, there's different tools and different groups of tools and names people typically use. And if we kind of go and look at OpenStack and where OpenStack plays most of the time. So there's provision resources, so provisioning compute, network, block storage, that's where the OpenStack core programs work. And HEAT helps here to orchestrate. During deploying platform services and deploying the application, you typically have some repositories either they're really defined or just somebody's laptop has a code that you have to SCP or something like that. There's deployment tools that possibly help and they use this repository to deploy the same configuration over and over. So there's also configuration management tools that help us in this stage. During the work stage, there's a lot of log, well, there are typically applications do logging and you want to collect that logging. You don't really use it typically when the application is running because while it's running, why do I care? You use it when the application fails because that's where the logs are typically analyzed, what is the reason of the failures and whatnot. Also during the work stage, you collect the metrics, possibly you plug in them somewhere like graphite so you can have pretty graphs to show you management. Again, nobody really cares if it works. The only time people start caring if it fails. And this work fail stage is where Solometer in OpenStack plays a crucial role because it collects the metrics and it also allows to trigger a reaction to those. Monitoring tools, Solometer is a relatively new program in OpenStack that gets more and more features, more and more functionality. There's still a lot of things missing. It helps you to monitor the cloud resources but on the side of the underlying hardware infrastructure, there's a lot of work that's still not there. So if you really want to have everything covered, you're probably going to have to run some extra monitoring tools. And work stage is also, again, where if we have multiple instances of application, that's where the replication, so the data is synchronized between them. Maybe you take back up, maybe not. And it's all good until it actually fails. So if we look here, HEAT helps us on this initial stage of provisioning resources. It also helps with deployment. HEAT by itself doesn't really deploy applications on top of VMs. We'll see what helps HEAT to do that or what HEAT can trigger. But by itself, if we just take the straight HEAT, it's not actually doing anything on your virtual machines. So what is HEAT? There is a definition that you can find on OpenStack.org and OpenStack documentation where HEAT implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like a lot. If I have my own definition of HEAT that was kind of collected from multiple resources, a lot of them are OpenStack.org documentation, a lot of them are not. And where HEAT as a template-driven agent that helps deployers, so people who deploy things, deploy the infrastructure and trigger deployments of applications. When we look at HEAT architecture, HEAT consists of several demons. So there's HEAT API and HEAT API, CFN, both of them are web servers. They accept requests. They process those requests by sending them to a message queue for HEAT Engine. So HEAT Engine is actually the main, that's the worker guy. That's the busy guy. So APIs, they are really, again, just rascal web servers that don't really do a lot of things. HEAT Engine is the one that does all the work deploying infrastructure. And it does that by talking to OpenStack services. So it talks to all of the OpenStack services, other services like NOVA, Sender, Neutron to create resources and to create what's called a HEAT stack. So stack is a combination of multiple things and multiple resources that the environment typically consists of. HEAT also works closely with Solometer because they kind of, they add to each other. So HEAT can create Solometer metrics and alarms and whatnot, whereas Solometer alarms can lead to something happening with HEAT. And in the end, we have our cloud resources, which are, again, computes of VMs, networks, storage, whatnot, that are kind of managed by HEAT and monitored and metered by Solometer. So if we look at HEAT from the point of view of virtual machine, I mentioned that HEAT by itself doesn't really do anything on your virtual machines. So typically, on the virtual machine, there's a number of scripts or tools or demons or whatever that run that get the information from HEAT and then they apply that work on the VM locally. One of the, I guess, most not common, simple, not simple, something that you can find in a lot of references and when people talk about, like, HEAT and here's template, they use images that have CFN tools. So CFN tools is a collection of multiple scripts that you install in the image and that they can talk to HEAT. So HEAT can talk to them to give instructions and they can talk back to give either signals or which are, hey, something happened, that HEAT can continue processing its stacks. When we look at HEAT, so it's a template-based engine. So HEAT operates on templates. And template typically consists of three main parts. So parameters, which is optional, those are some variables you want to include in your template. So if you want to reuse the same template over and over, you possibly want to have something that a user is going to enter. Again, if we take, like, one of the examples a lot of articles talk about is WordPress applications and it makes you enter a bunch of parameters, including database passwords and whatnot. So that's the part of the template where you define the input parameters for your template. The main part is resources. So it's a description of OpenStack entities, OpenStack resources that HEAT creates and joins them together and operates on them. And then in the end, you can have outputs. Again, outputs are optional. It's some extra information that you want to give back to the user after the stack or the environment is deployed. When we try to apply HEAT to scalable applications, so there's two useful features. So one is HEAT autoscaling. HEAT autoscaling is a feature that allows you to specify and template a scaling group. A scaling group is set of resources that either, that you apply the scaling policy to. So again, you can identify different scaling policies. You can say, well, I want to grow or I want to reduce the number of resources. And for autoscaling, another important part is integration with something like Solometer or CloudWatch that is actually going to monitor those resources and trigger the policy. And the way how those Solometer alarms and the HEAT resources, how they know about each other is because when you create the Solometer alarm, you just add metadata to it. And that's the connection. That's the missing connection. So that's kind of a little bit short about HEAT. So we're going to move to the hands-on part. There is quite a few people here. I don't really have that many environments. I also have good news and bad news. So good news, you're actually going to get environments and you're going to launch stack. Bad news, I broke the floating IPs. So when you get the stack up and running, it returns you a web server IP address, the floating IP. It's not going to be available. So that's kind of bad news. The environment we're going to spin up is relatively simple, where you have two-tire applications. So it consists of web server and database. And web server, there's two VMs. Each of them just runs Apache. They are front-ended by Neutron Load Balancer. And that's where the floating IP was supposed to be attached. Well, it is attached. It's just not accessible over Port 80. There is Solometer alarm that gets created for that group. And the web servers, they connect to databases. And the databases, there's also two of them. So it's two VMs, and they are behind the load balancer. So whenever one of them fails, the other one is still accessible because connection happens over the virtual IP of load balancer. After we kind of start the environments, because it's going to take a little bit of time to provision all the resources, I'll talk a little bit about the problems I personally had was that, and what I personally don't like. And most of it, well, all of that talk is my personal opinion. But let's get to it. So I have 35 environments. It's a lot more than 35 people here. So what we're going to do is we're going to try to join into groups of four, five people, maybe. So I'll do mine on the screen as a demo.  So if you open your web browser and go to that URL, you'll get to the page that asks for name, email. You can enter or whatever. It's really just a unique identifier so we can give you a unique environment. And then this page is going to return you the information and how to log into Horizon and where the heat template is and open the heat template. And I'll go through it a little bit and they'll talk what is happening on every stage. And then we can launch it. For those of you who are not going to get environment after they run out, you can still get just access the template so you can see and follow what's happening and see what's happening in the template. No, so it's going to be a heat number is a login and then Paris is a password. It's login slash password. Okay, so for this particular demonstration, we're actually using two types of images. So there is an image called Apache and an image called MariaDB. So we're running that on Fedora. Fedora 20 doesn't have MySQL out of the box anymore so it is MariaDB. You can install MySQL if you want to but that's what they get out, give you out of the box from the repository. To save some internet, what we did is we created those images, not just with Fedora but already did the YAM install for MySQL and YAM install for Apache. Just because I'll show you exactly where in template you add those lines. Just imagine if all of you start doing YAM installs, I mean internet is finite, maybe. So when you look at this template, so it starts with the description and, well, the other really important part in template that you should never forget because it's actually not gonna allow you to spin it up as the template format version. It's something you have to specify always. But there is three input parameters here because even though we're not installing the MySQL server, well, MariaDB server itself, we're still creating databases there. So we are simulating the deployment of actual application. And here you can specify the name, user, so the database name to create the database user and the password. And in parameters, when you specify the input parameters, you can specify default values. You could also specify allowed, so create some regular expression to validate those input parameters. And then there's gonna be a really, really long part that is resources, so it's a definition of all the different resources. And so the two first ones are, it's something that allows heat to kind of talk to your instances. When you start the instances and go to the log, you'll see that it has operations and SSH keys. The important part here is the VAP server group. So I mentioned that for auto-scaling, you have to specify the group, which is a group of resources that you want to perform scaling policy on. So here what we're gonna do is we're gonna have a group of resources, minimum size two, maximum size two, because we always want to have two. You can, again, depending what use case you're trying to implement, you can have different minimum and maximum. So for the actual scaling, when people use it to scale for performance, typically they have different minimum and maximum here. So the next one is scale up policy. If you want to do what, that's a definition of the policy that's gonna apply. And then the instance down is basically a salameter alarm description, what to do, what alarm to create in salameter. So if you look at the VAP server group, part of what it does, it has this property called launch configuration name. So we are specifying the configuration we want to do, and then we're just referring to that configuration. And the configuration is specified here. And what you can see, there is metadata associated with that, and then the properties. So the properties, so the configuration we're doing as for this as creating virtual machines was the image idea patchy and the instance set. So this is a, this configuration basically consists of the VAP servers. So this part, if you look at it, it's just a script, that's a bash script. And what this bash script really does is just creates the MySQL database. I remember I told you we already pre-installed MariaDB, but on the images, but if you would want to make it happen, you can actually just add here a line, saying yum and style, something like that. Another use, so we, again, here we're using CFN tools to do all the things. One of the examples you can find for heat templates with triple O is where they're using pop it to do things. It's good and I mean, pop it obviously has a lot more features than CFN tools. The problem is when you create the instances, you create them in private networks. So if you're running pop it in a server agent mode, where you have a pop it server and multiple agents that have to contact the server for the instructions or the cold pop it manifest, they all have to be in same network or your pop it server needs to be somewhere, so somewhere where it can reach the agents or agents can reach it. Since we're creating virtual machine and private network, what you have to do is pretty much spin up another VM that is a pop it server. Again, if you look at example heat templates, you'll find where they create the pop it server first and then each of the images has just pop it agent that talks to that server. And then the script that would be executed here is basically configuring pop it agent to where to talk to the server. Okay, so after we have two web servers, virtual machines, web servers, what happens here is we want to frontend them with the load balancer. So those three are, the three resources are related to load balancer. So the first one is creating the pool, just a group and then the last one, the floating IP, that's the one that is assigning the floating IP addresses to the virtual IP of the load balancer. I said I'm gonna give you my opinion on some things. So one of the things I don't like is in a lot of places when you use heat templates, you have to plug in the network IDs. Something that was changed thankfully in ice houses before when you create the instance before ice house you used to have to always use IDs, couldn't use name. So if you try to start a template in a tenant that has more than one network, it will just tell you no, I can't, you have to specify the network. So that was, that some of the problems was heat where when you use heat, you really have to know everything, how the open stack is configured, what are the networks, what not. So it doesn't really provide this ease of use for end user because end users ultimately don't really know what are the networks and where they should get this ID. That's where a lot of other application components come in that take care of those things. Okay, so the second part, this part is really similar to web servers, but it does same things on the database servers. So it creates a database group at lunches to VMs, does a little bit more because it creates the databases and configures the databases to be accessible to grants permissions for a user. And then we do the same thing with load balancer just using a different port. So we just configure a load balancer for TCP 3306. And in the end, it provides the output of HTTP IP address. So that's where the URL of the website is. And that's something that is not really there. So let me, so I'll show, I'll show you for those of you who didn't get access to play around with it, I'll show you here. So how that looks. And then look at the monitor of your neighbor. If your neighbor has horizon open, should just kick him. So I want to do it too. So we'll launch the stack. And what we do here is we just plug in this URL. So one again, another thing was heat is, heat is not really a repository for templates. So it kind of assumes that you store templates somewhere or have access to templates. And then you can either plug in, like use a URL, if it's a direct URL, or you upload the file or you provide a direct input. So you just type in there, which is good for debugging small ones, but you probably still want to use something to type them. And so you plug in URL and you specify the stack name. And so this stack name is actually important because one kilometer alarm gets created. That's something that gets referenced in metadata as well. So it's the stack name itself. I mean, you can specify any, but it's just a connection between several components. So I'll just gonna leave the password user named by default and I'm gonna do a lunch. And it's gonna take some time to start. So one of the other things, again, that we are using versionize house here. And there's a lot of work been done in Juno. And I believe the next talk at 1230 actually touches that as well as permissions. So if you know how OpenStack works, to touch any API server, you have to be authenticated. And for this server to continue operations, it has to be authenticated and it has to kind of verify and validate your authentication token. Was heat, it's interesting because heat is trying to execute a lot of things on behalf of the user. And it was this kind of idea was driving feature in Keystone called trust. So if you do notice, like here's some talks about Keystone trust, a lot of it is, like one of the use cases for that is actually using heat. Why am I talking about that? Because if you look, if you have access to horizon, I am an admin, because it's my user, but even your users, I actually had to give admin permissions because otherwise it wouldn't create some of the resources. So this is, again, something to know about, some of the resources are totally fine, doesn't care, any user can do that, but not all of them. So this is a pretty thing that got created. Rise your hands if you actually got access to horizon and managed to get same results. So we do have pretty powerful servers under it, but it's a limited number. So creating, spawning the VMs and then applying things is my take, but it should finish. Okay. That is something I didn't see, but part of what I tried was creating 140 instances and it took a while, but it actually finished all of them in the end. So it is surprising, but yeah. So this is HelloMonster, and what you can see is a lot of resources are actually tied together. And since there's a few people actually rise your hands, you can try and again, go to this URL, plug in whatever and get the environment because it doesn't seem that a lot of people actually tried to do that. You can see here all the resources, you can also see the list of the resources and their status here, and it's slow. I'm not gonna wait for that. So when it's done creating, what you'll see here is the output and there's like HTTP, blah, blah, blah, floating IP. It is pretty slow. Somebody ate all the internet. Yay. Anyways, okay, so we're pretty much almost done. So what's gonna happen is this all is actually gonna be up today. Don't trash it too much, okay? But you can try and come later, we'll see what's happening there. So you can do it later today. You know where to get the environments if they're any free and where to get the templates. So just come back later. Does anybody have any questions? So what happens was, there was a question about the alarm. So what happens with that alarm, it actually waits for the count and it's not really working correctly. So the other thing was CFN tools that kinda annoys me too is it always tries, so it tries to look for your EC2 metadata and it's not always something that you have, you need to have, because it can go like, you can use Nova API that provides metadata as well. So I actually had to hack Cloud in it a couple of times. Well, not hack, you can, when you reinstall it, it allows you to like deselect EC2. But yeah, I know what, and the problem is like, if it tries to connect to EC2 and it's not there, you sit there and wait for five minutes to instance to boot. Right, let's say exactly the same thing. Yes. Yeah, so there is a config file where you can actually modify a lot of values, including like what to do, for example, like one of the things, it changes the host name based on the VM name. So you can turn it off. What else I used? Static IPs, so if you like you can turn, so there's a config file, it depends on distribution, it's under EC2, look at ETC, I'm sorry, look for under ETC for Cloud or CFN or something like something related to any of those. There's gonna be a config file there where you can actually set like major things. There's not that much documentation about it. So again, you kind of have to like look at the code and... What happens if the point of process takes a few hours? So depends on what you use, so for if you use something like CFN, for example, the cloud name or any of those things, we also provide what you are, what you don't see in the app. Yes, yes, but you don't see yes in the app, or is it not? So, depends what distribution you have, so you have to do that. What do you direct to the cloud? Directing to the cloud? Yes, when you're comfortable. For example, when you're going to, when you're going to grab something, you know, that's why. So when you can be like the cloud, you want to be able to really, really open-set in a cloud, it's just something that you call a cloud, your iPhone, a console. That's it, that's it, I can move it out, so far.


Peren abayachicho, what's your preferred method for cannabis consumption? Bong bowl and rolling something up? It used to be rolling Joints right and I go I used to go through phases of bongs and stuff like this But I'm older. I want to save the lungs. So for the last 10 years vaping for the last 10 years I guess I've been vaping mainly only really only Take puffs of joints Random right more than 10 years. I spent vaping Save the lungs save the lungs BG Chester, what happens if a NATO country goes to war with another NATO country? They can That they can't It's it's not that they can't it's just NATO whatever thing is not going to be triggered We're half NATO feists the other half of NATO miss Bluehouse. Do you have a device? I use a riser solo I have the original and number two and they just put out a riser solo number three expensive I have the first version the second version and and Risers a Canadian company in Ontario and I'm not being paid for them up promoting them. I should contact them and say Yeah, man. I want to promote you stop pay me Or send me the new risers riser solo number three. I'll try it out I'll do a little testing for marketing, but I really like the riser solo Yeti pang salutations. Hope you're doing well on censor, dude I know yeti. Hope all is well, bro says I used to love dipping my chicken nuggets in honey. So delicious. So delicious. So delicious Vaping flower vaping flower. Yeah, just vaping flower. No extract or anything. Just vaping flower bud. Just vaping bud I don't like the the chemical contractions. I like to keep it as pure as possible No, no concentrates Parent I just grow my own cannabis and vape my own bud. That's it. I'm a big fan of decent hash or hasher as a nice Galaxy one says I can recommend the mighty plus vape 10 out of 10. That's how I feel about the riser solo 10 out of 10 Really like it The question must be referred to Greece and Turkey. Yeah Yeah Thanks chicho and galaxy one nice galaxy one chicho. Do you smoke a lot till you're really high or do you keep it low key? Really depends really depends depends what I feel like, you know, it's like No, I don't drink too much anymore, but Dosage matters John X the riser feels harsh on the back of my throat does it If you're if you're vaping flower All of oils and concentrates they they tickle my throat. I don't like it. I don't like it, but bud Feels Noticling the throat Bro, how does the THC vaping differ between nicotine vaping and or dabbing? I figured it was bad for your lungs. Nonetheless, it's probably still bad for your lungs, but not as bad as Smoking and I personally don't trust the oils Or the dabs and all this jazz. I don't know what they were made. I know you can make oil but butane I don't want to be vaping smoking butane. I've made it myself as well So only but I had finger hash right pretty mighty and crafty or both solid flower vaporizers for sure anything from stores and Bickel is top-notch. I want to save up and buy a volcano. That's been a long time dream purchase. Nice Elder God random information Jean-Claude is back with a new movie Darkness of man. Seriously. I like Jean-Claude Van Damme. Jean-Claude Van Damme. Jean-Claude Van Damme Yeah, real friends saying you have to plant garlic in the fall. Yeah, I always miss it I always miss it. I do a cleaning in my yard in the fall But then I miss the garlic season, which is crazy because everything is usually pretty clean I could just put garlic in and we're done Right. It is what it is You ever tried a live Live resin, I'm assuming they're supposed to say resin from Ken. No The solvent list one that's cold pressed like oh, no, no, I've never tried. I don't think I've tried Volcano is nice galaxy one says but requires too much weed does it I've had volcano before But I've never had it at home. I've had always had it different places No butanes are chemical cold pressed. Okay, I've never tried Sanchez have you grown any with? Alivir plants I've grown alivir. Oh, we actually don't have alivir right now We always did but then our all of our alivir got hit with bugs and couldn't get rid of it So we got rid of the alivir But we need to grow alivir, but I've never grown cannabis with alivir Live rosin live rosin is really nice. It tastes like just like The flower does it I've never tried Yeah, I'll do God saying it. She chose does not endorse drug use. I don't endorse the use of anything Okay, that's it. Not even tequila This balloon has first time using a volcano. We ended up getting a tsunami warning and I was turned my Turned out to be not a big deal though. Nice Galaxy one says yeah, rosin is fire, but expensive. Is it nice Again We're almost into two hours and we were able to do the live stream without rain coming in But it will be coming in at some point. Let's call it a stream. Let's call the stream game I hope Cheryl oh chicho and for your information aloe can be yuck For cats. Oh, but they usually won't eat enough For it to be a big issue. Okay. I didn't know that I didn't know that We've had cat here or previous cat and we had aloe. He never Attacked him any other plants really. He was a really good kitty cat. I really like that kitty cat. I wish I Like shown him as much love as I do salin via. That's one regret I have Should have shown more love to our previous kitty cat Lesson learned lesson learned nice Some 80 90 martial arts nostalgia Yeah, John Claude van der Yeah, let's call the stream. Thank you for being here. I hope you have a fantastic Rest of your week Piran chicho for reference resin and rosin are two different kinds of concentrates Resin typically means this has had some kind of solvent like butane involved in the process rosin means Solventless. Okay. Okay. Thank you for letting me know rosin. Okay parent. I'll keep that in mind gang just for a quick outro we're on Patreon substack subscribe star. You're definitely welcome to follow us there We do have a gilded survey. You're definitely welcome to join us there.  We are on twitter minds vk gab So true social sub stack notes and getter for those of you that are here supporting this work gang I'll cheer you with some electrolytes. Salute. Thank you for being here. Thank you for the Super chat the I forget what it's called again on censored too. I think it was meme that did it And thank you gang for the subs for the support for sharing for liking for being here for the conversations Fantastic fantastic times and to the mods gang salute to the mods because there's no way we could be doing this without the mods Gang, I hope you have a fantastic week and we'll talk next weekend. Okay. Bye everyone


Hello everyone, myself C. L. Rathod, assistant professor of department of mechanical engineering world change use of technology, Solapur. Today we are going to start a new topic that is orthographic projection of simple object. Coming to the learning outcomes at the end of this session student will be able to draw the orthographic projections of simple object. So this is the simple object which we have selected for the today's lecture. So here we are going to draw the front view of the given object. So problem is given that draw the orthographic view of the given drawing. In that one first we are interested to draw the front view and here you can see here when we see the object. So this is the object. In this one we are interested to draw the front view, top view and side view. But in this problem we are interested to draw only the front view. So when we see from the front side here the x direction is given. So here in this direction by this direction we are going to see the front view and this is this x direction is given at the left side of the your image. So for that one we are going to interested to draw the front view in this one. So before going to start this drawing the your orthographic view here the length is 70 plus 14 and 14. This 14, this is the 70 and this is the 14. So total length is 98, total length of base of this image is 98 and width is 42. It means height we are going to interested to calculate the height. So here height is 20 and 21 and 21 is the radius is given here. So total height is 62 and we are interested to draw the in this one is 98 by 62. So when we see from the front side here what are the parts which we are going to visible from the x direction. So for that one we are going to hash the parts. So when we see from the x direction, so from the here we are going to from this side we are going to draw the front view. So for that one when we see from the x direction we are going to see this part clearly this slot and this slot we are going to see completely. So now in order to draw the our diagram we require the reference line. So for that one we are going to draw the one reference line. This is the x, y and this one another line we are going to draw. This is the another perpendicular to this one. This is the x one and y one. So when we see from this side so we are interested in the left side we are going to see the left side here our object will be visible in this direction here we are going to interested to draw the front view here and here is top view and here is the side view. So now so first we are going to see here we are interested to draw this block complete block and its base is 98. So we are going to take the 98 mm total first we are going to take not total 98 mm we are going to take first 14 mm. So from this we are going to draw the 14 mm this is the 14 mm and then 70 mm we are going to leave from this one. So from this 70 mm here is the 70 mm and from this one we are going to take another 14 mm this 14 mm we are going to take. So this is the 14 mm. So now and the block height is 20 mm so we are going to interested to draw the 20 mm from this. So this is the 20 mm here also and here also we are going to take the 20 mm and you can see here the depth of this diagram is given 6 mm. So we are going to take 6 mm is the depth from this we are going to take the 6 mm depth on both side here also we are going to take the 6 mm depth and then we are going to draw the our complete slot and here you can see here it is symmetric on both side. So from this one we are going to take one axis line and total height is 98. So we are going to take symmetry means we are going to take 98 by 2 is 49. So from this one we are going to take 49 mm is the length.  So now from the axis line you can see this block and you can see here it is total height is here you can see width is 14 mm so for that one we are going to take 7 mm each side from here we are going to take 42. So from this we are going to take 42 and we are going to complete the our block. So now here only what we have done here whatever the parts which is visible when we see from the x direction we have completed and now pause the video and think that which part is not visible I hope you have understood the part which is not visible here when we see from the front side we are not going to visible this hole and this hole its length is from this side is 24 and it helps because it is symmetry it has 24 mm both side. So and its diameter is 12 mm and another one hole here is also it is not visible same diameter that is 12 mm is the diameter is given and another hole is not visible when we see from the front side in the x direction that is this hole that is its diameter is 20 mm diameter is given. So now what we are going to do here is that so here from this side we are going to take 24 from here I am going to take 24 mm. So here is the 24 and from this side also I am going to take 24 mm.   So this is the axis line we are going to draw and then 6 6 mm both side. So from this 6 mm here and another 6 mm here and in this also we are going to take the 6 mm both side its diameter and the whatever the part which is not visible. So we are going to draw with the help of dotted line. So I am going to complete this dotted line. So now we have completed these two holes of diameter 12 mm and another hole is not visible that is what I have to do its diameter is given 12 mm. So I am going to take 21 mm from this.   So for that one I have to take 10 mm both upper side and lower side. So here is the 10 mm and here also 10 mm and for that one as I said that we have when we draw the hole we have to which is not visible then we have to draw the dotted line on both side. So this is the how we are going to complete the our front view and now we are interested to dimension all the time. So here from this it is the 14 mm and here also 14 mm and this length is 70 mm and its diameter is block height is 20 mm it is given and from this length is 24 mm and its length from this base to here it is given here to here is 21 and from here to here is 21 and its diameter its width is given 14 mm so from this we are going to draw the 14 mm and here the depth is given from this depth we have taken 6 mm here we have taken the 6 mm depth of cut and the hole diameter is given sorry 20 mm diameter of 20 mm and here also another hole is given 2 holes are given so its diameter is 12 mm. So this is how we are going to complete the our front view. So these are the references I have taken for this given problem Engineering Graphics by Sri Thakur Dinesing Malakshmi Publication House, thank you.


When will you learn how to handle my thought, how to handle my emotion? We will give you tools how to figure this machine out. Whatever the issue will do our best, but this should not be the issue. In life there are many phrases where we feel that we are depressed, we are lonely and when everybody is against us and there is no one to, you know, guide us or talk about it. So at that moment how should we handle it or how should we deal with it? See, this is an unfortunate condition that a whole lot of human beings are in, in their experience. In their personal experience, life is like me versus the universe.  That's not a competition you must get into, hello? Me versus the universe is a bad competition to get into. What do you also agree with? So this is why yoga, yoga does not mean twisting and turning your body. The word yoga means union. Right now it's me versus the universe. This is just your psychological condition. This is not the reality. Even when you feel utterly lonely, are you still breathing? So you're transacting with the world, isn't it? You only can't get along with the people around you, but the atmosphere is okay with you. Food is okay if it tastes good. Water is okay. You have transaction with the world, isn't it? Your existence is constantly an engagement with the universe, but your mind becomes against the universe. If you create a psychological condition that you're against or you're in competition with the universe or the cosmos, obviously you will feel crushed for small things.   These are all small things between life and death because you came here with nothing, isn't it? When you die, there is no container service for you.  In spite of that, most people have turned their homes into warehouses.  This is their own psychological condition. Your thought and emotion is what you're talking about, right? When are you going to figure out how to handle your thought and emotion, not hers, not hers, not his, yours? When are you going to learn how to handle my thought and my emotion at the end of your life? The only problem really with life is just this, most human beings have taken themselves too seriously. They don't understand. You've seen on the computer screen these pop-ups?  You pop up for two seconds and pop out. No, no, you must see, countless number of people like you and me have walked this planet. They were also big people. Where are they? All? Topsoil? Topsoil or no? Unless they… somebody, your friends decide to bury you real deep. Fearing that you may raise from the dead. You know, there have been such instances. Or maybe you're planning to go to heaven. Hello? Anybody who talks about a place, other than this place has a better place than this, this is a crime against humanity. My fundamental work is to destroy all heavens. So that people will learn to live well here.  They made a mess out of this place and then they want to go to heaven. I'm asking you, do you have any proof? Do you have any proof that you are not already in heaven and messing it up? Do you have any proof? You're already in heaven making a mess out of it? Yes, simply because you are not even learning how to handle your basic faculties of thought and emotion, isn't it? Your only justification is everybody is like this only, that's how it is in a madhouse. That is how it is in a madhouse, only a doctor looks crazy. So when are you going to handle it? Slowly, at the age of sixty, I'm asking, when will you learn how to handle my thought, how to handle my emotion, how to handle my body, how to handle my chemistry, when are you going to figure this at the end of your life? Because this culture has grown, when to do spirituality means when you're seventy, when you're no good for anything else. No, at the earliest possible time, whatever is most profound about you, not about heavens, about this life, everything that you need to know, you must know soonest, isn't it?   Because this is the most serious crowd I've ever seen in the last few years. How many of them are journalism? Most of them, okay. This happened, Shankar and Pillai, when he was in Paris, was married to a French woman. One day it was their anniversary, first anniversary. So she invited a bunch of friends and she wanted to cook something really fresh, everything fresh. So from morning she was driving him to this market, that market, he got this fresh vegetables, fresh meat, fresh chicken, this, that, everything. Then in the evening she said, because the French have this, you know, snail appetizer, she said, go to the beach and get some snails, fresh. And I will make some appetizers for all the friends who are coming. So Shankar and Pillai went to the beach and he was picking up all the snails and putting it in a bucket. Then he met an old friend, an Indian guy. They hit it off and they were talking about their old times. He just forgot that he's married. You know, when you meet old friends it happens and both of them went to a bar and they had a few drinks and he just forgot, then he realized, then the snails were just climbing out and talk, one snail fell out of the bucket. He realized, oh my God, I'm supposed to take the snails, my wife, French wife, she's waiting. So he said, I need to go and he went. By then it was already very late. He went, he knew it's not going to be pleasant. So he came near the house and spilled all the snails on the ground, threw away the bucket and went and knocked on the door. The French fury came. He turned back and said, come on you guys, we're almost there, come on, let's go. So when are you going to pick your snails and put them in the bucket and fix them? Your problems, you must fix them, isn't it? These are not problems.  You're only suffering two fantastic faculties that only... it's a privilege of being human that we have these two fantastic faculties. One is we have a vivid sense of memory. This is because of this memory our life is so rich. Unlike any other creature and we have a fantastic sense of imagination. Now this is what you're suffering. What happened ten years ago, you can still suffer. Why? Are you suffering life or memory? Hello? Memory. Memory? What may happen day after tomorrow, you're already suffering? Are you suffering life or imagination?  So what are you asking for? You want to become once again an earthworm. An earthworm is a very eco-friendly creature. I have nothing against it. But it took millions of years of evolution to get you at this size of brain and now you're suffering it. If we take away half your brain, of course you will sit there without any anxiety, without any suffering peacefully.  Yes or no? Yes. Because we gave you a very complex machine, you have not bothered to read even the user's manual. You want to just blunder around. No, young people, it's time, you figure out a few things about you. If you don't know how, we will give you tools how to figure this machine out. Because in your life, many issues will come. More issues come up in your life means you're living a more active life. Nothing came up means you're not living. Yes? Lots of issues every day. I have the maximum number of trouble going on in my life on a daily basis. Because so much of activity around the world, global level of activity, only with volunteers, okay? Volunteers means nobody's qualified for the job and you can't fire them for inefficiency and they love you. What to do? This one thing you must fix, that is in your life, you are not the issue, okay? Whatever the issue will do our best, but this should not be the issue.


Everybody forced here ripping a box of 2021 or sorry, excuse me 2022 is like UFC hobby hybrid This box is for Matt P. Thank you, Matt Yep, good luck, man. See a big color parallel here. All right concourse silver max Holloway Panthers listen offers in the Capri Rams are trying to trade cam acres rookie concourse disco, Paul Craig Silver premier level Nadia's Capri is gonna be tough because I Concourse disco Henry C. Udo Premier level disco John Jones They also don't have many pics to give up And on the back is an octagon side disco Curtis blades You go Matt. Thank you again for the order. We'll get those cards right out to you


What's up everybody? James here with JasperJasperys.com. Win four spots in our basketball mixture with this 1920 Panini Mosaic hangar box to one box break random teams number one. Third two spots, everybody gets a random team in the NBA. Just remember, no veteran common ship will randomize customer names teams, distribute hits out of the hangar. And at the end of the break, we'll randomize only the 30 customer names and top four will win a spot in the 17 box basketball mixer. So pay 40 bucks to potentially win a spot in this mixer here, which was a pretty pricey mixer guys. It's 240 and 17 boxes. So save yourself a good amount of change there. Chunk of change, sorry. So let's do the break first. Good luck, let's roll it. And we've got a five and a three for eight times. One, two, three, four, five, six, seven and eight. And again, try one look close for this too guys. They're just gonna go through the list, but no one really trades in this. Just a quick hangar, eight here now. One, two, three, four, five, six, seven pelicans at number one down on the spurs. So Scott, you got the pelicans. I'm gonna Eric with the Lakers last one module. Matthew the Jazz, Sean with the Cavs, Matthew the Bulls, Zach Jeevan with the Raptors. Nick, you got the Pacers, Jason with the Knicks. Ties with the Celtics, Eric with the Hawks, Jeremy with the Hornets, Matthew the Wizards. Sean with the Nets, Jeremy with the Heat, Mark with the Magic, Cole with the Rockets, Scott with the Clippers, as well as the Mavericks, Matthew the Wars, JD with the Grizzlies, Nick with the Thunder, Zach with the T-Wills and Blazers, Mark with the Suns, Scott with the Pistons, Mark with the 76ers, Matthew with the Nuggets, Scott with the Kings, Gabriel, you have the Bucks. Jeremy with the San Antonio Spurs, it's quickly. Print this out, and it's quickly open up the one hanger box here. See what you guys get, get those orange reactive parallels in here, Paul George, Lonzo Wall, P.J. Tucker, Paul Millsap, you got the Braun James, you got game T.J. McCullum, you got a John Moran, NBA debut, Cody Martin, Vince Carter and Jared Colver. All right, sweet guys. Now let's see who's gonna get to the spots in the mixer. Remember it's four spots, so top four get in, let's roll it, and we got a five and a six for 11 times this time. One, two, three, four, five, six, seven, eight, nine, 10 and 11. Jeremy, Mark, Scott, and Jeremy, wow, there you go. After 11 times, top four get in, congratulations. You are now in the mixer, another way to win on the website again, number two's already down to 22 left. Guys, appreciate it.


Hello and welcome back here to the channel. I'm EvilRabbit We are in one of the 2.5 cars We're testing something different which brings the question I bring up to you guys here today Do you think the 2.5 should get a power boost? Do you think we should increase the power a little bit from the street cars we have now? This car is currently at about 451 452 horsepower So do you think the 2.5 should get a boost in power before they get released? Let me know what you guys think down in the comment section down below We are at a track that is kind of local to me being from Ohio killcare So we're gonna go test the new flow layout that they have Here in a set of Corsa and have a little fun with this 13 so if you guys have been on the actual like tandem Comp track you would be hooking it in around here, but this is actually a flow track So it's great for tandems and things of that nature, which is what we are going to be probably switching on to the server I'm going to kick it this way. I definitely love The bump up onto the bank and the cutting in on the track. It's definitely a fun track first time actually out here on this layout in This 451 horsepower s13 v2.5 physics. Oh Yeah, I like this track. It's small, but it's kind of flowy I like going up onto the bank that's definitely a lot of fun So like I said in the beginning do you guys think? We should do a power bomb on the 2.5 before I release them Do you think I should up them up to about 450 horsepower make them a little bit more powerful than the street cars? But a little less powerful than the original street cars that I brought out a long time ago with the a90 super that was about 570 so 450 horsepower I feel is a pretty achievable horsepower when it comes to a real-world drift car especially with Turbos and everything of that nature or v8's so I think I Want to bump the power up, but I want to get everybody's kind of opinion on it Before I actually go ahead and change all the two flies over to winning power band that bump is definitely crazy This this track is a lot of fun I'm having a blast on this track and I think the server is gonna be going to this track and We're gonna be doing a little bit of local drifting because like I said, I am from Ohio So this is kind of I guess you would say a local style track to me And it's definitely be fun to get some tandems on a track that You could actually go and drift if you were from you know in Ohio or around it and things of that nature We're gonna flip around. I know That'd be running the track backwards, but we're gonna see How this goes in the other direction So I think I definitely like the cars having a little bit more power It allows them to do a little bit bigger courses and things of that nature with you know The evil rabbit drift playground and everything almost near completion the cars with a little bit more power would definitely Be more suitable for The tracks and the bigger layouts and you can run the short layouts as well as the big layouts So it's something I've been dabbling with in my head on upping the power And I'm just having blast with this car Is this actually the way you're supposed to go? I mean it might be we may have went on the track in the wrong direction because If you came that could be the offshoot and This could be the entrance so if you guys know the actual way to run this track because I am not entirely sure Let me know down in the comments. Oh That might be it kick it in. Yep. This way flows so much nicer Like I do like this way flowing a little bit better, but if you guys know the way the track actually flows Let me know down the comments on my Ohio PA New York drifters that may be around on this track Let me know down the comments because I have never actually been to this track in real life So definitely need to get there though So I'm having a lot of fun with this higher power and it's definitely handles very well And I think we may be switching the street cars to a higher power for the 2.5 release still a few little tweaks I need to do to the cars such as adjusting colliders and things that nature to make the colliders a little bit better There's a little bit of wall tap though to make the colliders a little bit better and nicer for the cars to make tandem ain't that much easier? pull Switch it up into first person. Well, I cut that really short back on the bank.  That's gonna be a grass cut. That was a bad That was a bad transition there Definitely enjoying doing a bunch of different tracks and this track is actually so much fun that I Would like to get some tandems with some friends and some of you guys as well on this track So we are in the final Oh Don't try switching views we're drifting in the final testing stages of the 2.5 So it's definitely very close to bringing them out to you guys doing final testing on the evil rabbit playground With hexer to make sure all of that is set because that is also almost done and ready to go Just want to make sure there's no bugs and if we need to make any little tweaks and things of that nature We need to want to catch it before We Drop it because we don't want to drop it and then have all these bugs and everything And you know got to make it as close to perfect as we can even though nothing will ever be perfect because We all know sometimes you can't catch everything and that's what the community will find for you Whether it's constructive criticism or bashing you in the comments about your cars. It's definitely something that will be found So make sure you follow me on all social media which found the description box below Just a quick a little video and talk for you guys here today on Friday and the week so that we can kind of get some Answers from you guys if you guys think I should up the power a little bit to what this car is right now Which is about 453 451 452 I don't know the exact number, but it's a it's over 450 and under 455 so I Hope you guys Will let me know down in the comments what you guys think so as always I think I should come back and watching Homie will rabbit that was way off course. I was looking at the other screen. I'll see you guys on the track