Layer5 Meshery Development, 15 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Meshery Development Meeting (June 15th, 2022)

Description

Meshery Development Meeting (June 15th, 2022)

Agenda:
[Aditya.C] Updates on Catalog
Outside of the Catalog UI, in many respects, the catalog acts as a registry.
Need to support user accounts, differentiate support levels for different catalog items, ability to search, version designs,
[Aaditya Narayan Subedy] Related patterns in catalog
[Abhi] Lifecycle Page fixes with multi-context support #5614
[Pranav/Uzair] Progress on Account Extension
Direct sign-in available for https://meshery.layer5.io
[Gaurav] Support for Undeploy designs/patternfile #5617
[Yash] Demo of proposed Meshery cloud page.
[Gaurav] Meshery v0.7.0 Planning
Refactoring Meshery UI: meshery-ui-restructuring | How to contribute
Volunteer Needed: v0.7.0 Roadmap feature champion assignment refresh
[Uzair] Addressed bugs with settings page #5611
[Debopriya] Vote for your favorite MeshMap logo design.
[Jerod] Docker Extension video recording
[Lee] Multi-context support completed: Revisit v0.7.0 roadmap.

Join the community at https://layer5.io/community

Find Meshery on:
GitHub: https://github.com/meshery
Twitter: https://twitter.com/mesheryio
LinkedIn: https://www.linkedin.com/showcase/meshery/
Docker Hub: https://hub.docker.com/u/layer5/

A

Newcomers in the meeting- so we are very uh uh you- know, welcoming uh community, so we want uh every newcomer to you know, get uh get up and speak about themselves so that we and our community know about you. So uh do we have any newcomers or just you know, anyone who is uh joining this call for the first time I'm just checking out the list and it is kanika gola right.

B

Hello: everyone, my name is tanika, I'm a second year student, pursuing b-tech, I'm a full-stack, moan developer and an open source enthusiast, and I'm joining this developer call for the first time, yeah.

A

A

And uh you know I'm very glad to hear that your open source and choose yes to like all of us here so yeah thanks so.

B

Much for joining.

A

Thank you and uh I think you, uh you also forgot to uh get your name in the attendance like uh uh you know you. If you do it, then on the next part too, I I'm gonna tell you to give your introduction otherwise yeah.

B

Sorry, I couldn't understand you, can you, please repeat.

A

Yeah, the meeting minutes are leave and sharing so yeah yeah.

B

Oh okay, you join okay, sorry yeah! I will do it for the next time.

A

uh Nobody, so uh we are moving to our uh next. uh You know list of items, so uh it is uh first by editor uh updates on catalog.

C

uh Yep I'll just share my screen.

C

So yeah, so I just have uh small updates. So uh basically I uh so we were here for the catalog that we have on message.io.

C

We were using uh json as the data file so that we get these cards over here so right now we are moving away from the single json uh data file and moving on to collections like having separate markdowns for all the uh for all the patterns, because, after that it will be easier for us to add new patterns later on, and it will also be easier for us to implement other people adding more patterns to this. So it's just a draft pr right now.

C

I have just added a cover because we have like 34 patterns, so it'll take some time to write them all up. So also, what ha helps us uh like? What this helps us to do is have like a read more button. That would take us to a separate page where these patterns would be there and uh it'll be easier to uh have a link to them wherever we can or or it'll be easier for us to share it with other people as well.

C

If all the patterns have uh have a link to them so yeah, uh just some minor updates here and yeah I'll be working more on the catalog this week, like I'll, probably get it done by tomorrow, so yep, that's all any feedback, or if anyone thinks that this is not the approach that we should be taking.

C

This is my pr inside and link.

C

So any thoughts and thoughts of feedback.

D

Does anyone think that the catalog is not particularly either useful or novel? Like there's a lot of catalogs out there there's a lot of application catalogs, usually the type of catalog you go to is they'll. Let you choose.

D

You know from typical apps, usually it's apps, but sometimes it's it's infrastructure, and by apps I mean something like wordpress or ghost or gatsby or like some. You know.

D

An app like that um it doesn't have to be a blogging system, but those are just the first things that come to mind.

D

Sometimes it's provisioning of other infrastructure.

D

It's a lot of times. That's what you'll find in the app catalog. This one is intended to be and is a little bit different. This one is it's intended to for the most part capture, best practices, so best practices come in a few different forms, so one of those forms that, like the very first design, the very first item in this catalog, it's um a deployment model, and so there might be best practices around deployment models.

D

um Istio as an example is highly configurable and you can run it in a like an overtly, secure way or in a highly telemetric way or or there's lots of various configurations. It depends on how you want to use it and what you want to use it for so. Consequently, there are different deployment models and consequently, there are best practices in those models. There's trade-offs to understand if you're really going to have it emit, distributed traces every single time that a request is received and processed by the service mesh.

D

It's going to cost you it's going to cost you a lot of storage, it's going to cost you a lot of cpu cycle and it might even cost you some latency and that can be totally worth it for you and hence the caveats and considerations, portion or caveats and consideration.

D

Maybe we should put an s after that, but is a section wherein it would describe something like that. So if you have a deployment, an istio deployment in this example that has you know all that telemetry coming out, it could be that the consideration is that you've got enough storage lying around or enough cpu lying around.

D

So I wanted to describe this a little bit differently than some of the other app catalogs that are out there, because I do want to hear from those that are on the call I mean from and that's what aditya is asking as well. Is I'm asking a little more pointedly he's like? Is this a worthwhile exercise?

D

Are these types of things helpful? These are not your stereotypical for the most part like if we were to go look at a different catalog item. I think one of them is called circuit breaker. So this is circuit. Breaking is a capability of like all of the service meshes you configures, you can configure circuit breaking in different ways. You can configure them to be highly sensitive. You can configure them to never to barely ever open or hardly ever close back or there's and there's considerations as you do it and that's.

D

What we're trying to do here is imbue best practices and help people comprehend and understand um what happens when they configure their infrastructure certain ways and what are the best practices around that so again, um so what we're not seeing necessarily here is a bunch of apps. um It's a little bit different.

D

What are you? What are your thoughts like part of the goal of this type of a catalog? Is that um secreta on the call he may end up with?

D

Well, he may end up with a design um that is best practices for him or for his organization or or just one that it isn't really. He doesn't consider it best practice. He considers it just experimental, but but either way he wants to share it.

D

So part of the the consideration for this type of a catalog is that um those in the community, those that are using, measuring um or can come and share these well, these patterns, these designs share their web assembly filters or if there are other types of filters that you might add to your service mesh configurations, you might do in ebpf configurations that you might apply through oppa policies.

D

These in some respects you could think of them as power-ups as add-ons to your service mesh. You can certainly deploy the mesh without turning on a lot of things or you can turn on a number of things and some of those things you turn on again. Part of the point here is that you don't other than just turning them on you're, not quite sure what considerations you need to account for when you enable that feature. How should you configure it and why, like? What are the characteristics?

D

What are the considerations of that configuration, so this should be about people should this should facilitate sharing a lot of times when people share it's kind of nice to receive credit? Sometimes it's nice to be able to say that you know gaurav uploaded this and here's a link back to maybe where they've got that checked in somewhere else. So that's that's a good question. It's like if this is to facilitate sharing.

D

What's the, what are the mechanics by which we would expect people would contribute to the catalog one and then ongoing as they change their design and learn more and update their practices. Should these be versioned as their version? How is it that we would ease the burden of keeping these up to date, the burden on contr? You know contributors here that are creating the catalog and the burden on those publishing into the catalog.

D

So I'll be quiet for a moment. There's a number of other considerations to account for, but I think somebody was going to say something.

A

Yeah, so uh so, since this is a catalog, uh so I we should also have an option to directly import it inside the machine instead of like or downloading it through and then re-uploading it. So uh I think copy url method uh has this option enabled, for example, you can directly import pattern from the catalog itself, since we are already maintaining the code catalog, we don't need to overhead to the user to just download them.

A

C

No, I was just saying that even I think that we should do that.

D

It seemed like people would want some potentially some amount of versioning over their design and over which version of that design that they've deployed. If there are differences between one version of the next and and what that might mean to them.

D

So, anyway, I bring up these potential features, as so that you can reflect on them as you're designing out the catalog, um ideally yeah yeah yep, so that might mean user accounts. That might mean some of these are well supported and kind of the community stands behind, or some of these might be experimental there might be. There might need to be ways to signal that to differentiate those.

D

So, anyway, things to think about.

A

Yeah, I just uploaded a pattern uh imported.

A

Design from the catalog that is suiting their needs for the moment. What they can do is just click on this import button uh grab the url from there, for example, how I got this uh url is uh from there copy one and then paste it here and then just click import. So uh your new pattern will be.

A

So you can check that out and uh you know design according to your needs, based on what are the available adapters you have and so yeah. This is. This is in the different domain, so.

A

uh Should we move only or uh we don't have any further discussions, yeah yeah.

D

Yeah, I think so, hopefully that gives some people some things to chew. On there's one last thing that I would say about the the catalog: that's there so so pranav mentioned um the ability to see the designs potentially in measuring cloud. um Abby mentioned the ability, I think, of zombie, to the see to see the pad the designs inside of measuring, ui and aditya was saying hey. You can see these designs inside of the catalog itself, so so a lot.

D

The parting thought that I would leave you all with is that um it's not insignificant the considering the number of clients that were just mentioned for perusing the catalog. It's not it's noteworthy that the other portion of what this particular catalog provides is a registry.

D

Leaving aside the user-facing interaction, the fact that there's a central registry.

D

Something to think about.

A

A

Do we have any other comments uh on registry and pattern catalog.

C

Yeah I'll share my screen.

C

So, as you can see, there's some changes going on in the catalog page, and one of the changes is that we are dynamically introducing the related patterns field. Earlier it was self referencing like whichever pattern we were showing the related patterns were showing that only but now we have changed the logic a bit and uh the related pattern shows all the patterns that are that have same type. Like suppose. uh The circuit breaker has type traffic management, so related patterns shows all the pattern that has uh traffic management as their type uh so yeah.

C

This was a small that uh fix that. I uh that updates, that made that was made on the catalog.

A

I believe that is very helpful in case uh someone is searching for uh you know something related to traffic management and they are hopping on one design and then they can see the rest of the you know, recommendations or some of the top picks on in the category of traffic management, for example. So I believe it is additional.

E

Yeah, that was it.

A

Yeah, so, okay moving to the next item. So after the multi-context thing, uh we have some problems in the ui with the life cycle, page specifically where our life cycle page was uh what the life cycle page is, for example, uh this is the life cycle. Page uh management, page, where uh you are uh you know, uh trying to install uh service meshes or go through its life cycle, uh apply custom configurations.

A

Do your thing with the service machines right, so uh actually uh it encountered some problems due to uh you know a major level of refactoring in the ui, as well as in the server. So it went unnoticed uh while we are doing refactoring uh thing on the ui and server. So I think uh this pr, uh I get it here, uh uh fixed everything related to the life cycle menu. I have built the pr in the uh chat or sorry in the dark.

A

So uh please do uh review like it's already merged, but then yeah we can get another fixing, nothing and uh yeah. So that was the update. So a lot of cyber states were failing. uh Due to due to this bug, uh we were not able to get through the page, because the uh you know the select service mess uh text thing was also not uh responsive uh on the first load so yeah, all the things are related to service mesh uh and life cycle page uh were fixed yesterday.

A

So if you have, if you are on the previous build uh so.

A

Do you have any comments like uh if you are, if you tried installing some service meshes and then you're not able to do yeah? So if you do have anything, please.

D

Yeah so um abby you were giving that you were speaking about this in context of multiple kubernetes cluster support.

D

Yes, okay, the fact that the dashboard page is the one that benefits, maybe the most from from views from viewing the information back from the contexts, but many of the other pages, where you're taking action and invoking operations, those benefit by way of like deployment or or multi-context operations, which is that deployment model that you're showing okay.

D

Gotcha is there is state maintained, then, across the pages for the selections, the preferences that people have made exactly yeah.

A

There it is uh so you are asking about the uh context or preferences that they have selected through the uh page. So all these things are especially multi-clustered uh things, for example, the selected gates context operator subscriptions and the messaging status subscriptions. They are all managed on the global level. uh They are supplied to all the pages that are in need without re-initializing the subscription. So, yes, we do manage.

A

You know a global state on the multi-context features and the states.

D

Random question: are we still having we're still having challenges around persistence of the subs of the subscription websocket across page reloads? No, no, okay,.

A

So there are quite a few, uh only few number of subscriptions that are required across all the pages. uh One of them is uh the operator part. If you are seeing the uh you know a fully lightened uh activated chip. That means your operator is, are held in healthy state and is successfully you know running in your cluster. uh If it is not, then uh probably you are not good with your operator. Some operations may fail.

A

So uh yes, so because all the subscriptions are are not be initialized or named instantiated on page alerts, they are instantiated when you have uh when you are switching back to different clusters like are selecting another cluster, so probably when, when I did it, I would have flushed the previous subscription so that I should not see the data from uh you know. I should get the updated data from both the cluster.

A

So that's how we are managing you know flashing and then we initializing subscription, so it is even based now, instead of you, know different page routes, so yeah we have quite a vibrant uh with this approach and we are able to get the subscription data quite fast in the dashboard. Also.

A

Okay, uh okay, so uh it's time to move to the next item by product, uh which is progress on account extension, so we are doing some uh recently doing uh doing some changes in measuring cloud. We are thinking to uh provide you know: uh user interface to the users itself, so printer will talk. uh Rest I'll share. My screen.

F

First I'll again give a context like I gave the last time like what actually are the accounts and what the remote provider and what's happened when you're signing into my screen. So whenever you like start mentioning, you see this page, where you select your provider, now you select your provider. Usually you want to go for a remote provider like messy.

F

This is because it provides you with um ability to say process your current instance of measuring, which includes saving your application, saving filters patterns or saving your designs, and more than that, like you can then, um moreover, the more providers necessary, because it provides you with um extensions point which, like further enhances your um user interface in machine so currently like for, like what happens like when I connect with sign in with twitter um github is an external remote provider which provides my um the github, provides my authentication, uh my user name and password to message remote provider and then it's, let me sign into misery and it provides all that information but currently like.

F

We cannot change that information. We cannot see that so I was working on. um I was working on making a new ui, where we can see all that information, um which I already shared and last time I'll quickly share it again like how it looks like.

F

This is the profile which I like last time as well, like it's done where you can see your profile, you can see your username first name. Last name: email provided, okay and.

F

I was learning local instances. I was working on so.

F

So it provides you with how many kubernetes clusters I've ever connected to cuban uh while learning measuring or how many designs I have, and these api tokens are very useful. For example, it gives you the token which you generated while signing into issue instance or the token you generated like the infinite token, which you can use in your bit of actions or your messy cdl um as an infinite token. Now the thing is that I was give.

F

I was working on giving the same ui and measuring measuring ui, where I was working on an external extension point. That's this account like if I show my capability like there's an endpoint in um mercedes, which shows all the capabilities which are provided by the remote provider. So currently I've added a new capability.

F

That is account and it comes with new features like seeing your profile, seeing your account overview and open the old like if I click over it, it will break because, like only few things are left in it like, I have to update the machine server for the new apis so that the new ui which jose created, would be shown here. Like that's the last part which is left um other than that, like that's the update for my site, which would you like to add on to something.

A

You know you mostly called all things. I would like to say that all that, once the extension point is ready, just the linkages with some linkages we have to fix and you will able to complete it.

F

And this is a new thing like earlier it wasn't here. So that's anything! That's that any feedback.

F

And one more thing like right now: you can directly sign into mishki cloud like earlier. It wasn't the case, but right now, whenever you go to this link, um which is already given in the dock meeting minutes like whenever you go here, you would be able to see your profile so right now like why, I'm speaking you I'll just give you the link, go to your profile and see how many things you have worked on two missions as well.

G

By the way, um can you go back to that page where it showed how many clusters you have.

G

So so it says kubernetes clusters and not communities context. So uh you you're using you basically unique context. Ids right here.

F

G

Context ids, uh they are a function of both machine sense as well as your cluster. So if you restart your machine instance, you get a new kubernetes context, but cluster ids remain the same. They are kind of a fingerprint of a cluster.

G

So if you are saying kubernetes clusters shouldn't, we use cluster id instead of that, so that we are only showing the unique clusters or if you are using the context id should we show kubernetes context here, because here it says clusters, but I don't know if that that's kind of a nitpick, but uh it kind of bugged me so I've pointed it out. If someone else has a contrary opinion, then.

F

I'll change it. Actually, I was referring to the unique cuban native server id for getting the servers which a user has used I'll update that I'll change it to contacts.

A

Another thing I can say this right now is that uh you know with the kubernetes cluster. You can give a very short uh captioning with uh it. Like a short brief information of what this kubernetes cluster means to say, uh for example, some users may uh not be fully aware of what it is saying from our perspective, especially so yeah.

A

For example, these many contacts have be uh machine server detected in your cluster.

G

But by the way, which field did you use it pronoun? Were you using.

F

I was using kubernetes server right now.

G

Yeah, that's I think yeah that is, that is the cluster id. uh That is, I'm 99 sure that is the cast id so yeah. These 133 cluster means that you have restarted your cluster these many times. Okay, that makes sense.

A

Okay, uh do we have any other comments.

D

I just wanna like pranav: do you you might have a cluster to spare? Could I borrow one it looked like you might have a few laying around like 133 man.

F

Actually, like restart used several like earlier, I was also working on multi-cluster, so I might have restarted my cluster several times.

D

I mean you know like the bitcoin market. It's, like you, know it's up and down like if you're, if you're mining, I mean we could uh anyway, actually that's a good. So so a question for you uh setting aside all the sarcasm for like one minute, that's about as long as I can probably go.

D

You just mentioned an item when, okay, as you were, doing multi-cluster testing, you might have nuked your cluster re-initialized, the new one, and even if, even though it was on the same machine technically, it's a new cluster, and so it gets treated and tracked differently. Okay, good great yeah. Thanks for explaining.

A

Yeah, yes, so a lot of mystique talks and user account. Okay, let's move on to the next thing uh by gaurav, so uh uh you know support for fun, deploy our design pattern file. I think ashish will be the most happy person right now, if you do have uh yeah sure.

F

Yeah so, apparently for me in message: ui for machine ui for designs. We can perform crud operations on our pattern, file that we upload and we can configure our apps to the action. So we were having the deploy action, but we were missing the undeploy feature for the patterns for the design. So I added it under the action. So if we can, if so, it enables us to undeploy the file that we have uploaded.

F

So I think um it needs to be handled properly with the with the cluster that we have so, and I also will be I'll, be also adding the undeploy button to the configurator as well as the deploy. So it will be a good user experience to undeploy and deploy easily.

F

So yeah ashish or are we.

G

Do you have an adapter running right now.

F

G

Yes, which one yeah you don't have an adapter. That will basically meant that you don't have these two doctors.

E

F

So yeah about the ui changes, so we want this uh deploy and underplay button and design configurator as well.

A

And this uh page also the card house, this page yeah this.

D

B

A

Have undeclared button uh one another thing I want to uh point out is: if you can go to uh this one yeah, so uh the undeploy button and the deploy button are somewhat like very different from each other that they are not uh you know.

A

So if you have play icon, then crossing it will make more sense.

F

uh Or I'll, replace the play icon with double tick marks that we have in extensions for mishna.

G

uh By the way, by the way I didn't see the model come up when you clicked on deploy, is there no modal here and if, yes, then, why.

G

I mean we should have a modal here as well.

F

We should have like uh updated. It was that pr merged. I pulled the latest few hours ago. I guess.

A

No, I think I might have missed this part, because this deploy was added. Deploy was that I might have missed this area. Okay,.

G

And also, did you add the undeploy in the applications pages there.

F

uh No currently, it's just for the designs I'll toss in there also.

G

Yeah, thank you and we would need model both you know at both designs and applications everywhere.

F

Okay yeah, I loved it so like last feedback on the icon, so play button cross or tick for this deploy.

D

So the the play button was just a it's. You know it's a long-standing poor man's band-aid, okay, it's just! It's never meant to be there in the. If we can be consistent with or I would suggest that we would be consistent with the meaning of the check mark in the extensions which only serves to reinforce what the double check mark with the slash through it means. So I guess for so.

D

I guess my suggestion here is that you consider the double check mark for deploy and the double check mark with a cross with a slash through it as the underplay yeah. I don't know if that was that what people were saying already.

D

D

I want to hear cross, I think, of x,.

G

But uh yep, I think, of the christian sign but anyways.

D

Do you yeah, so it seems like it's not a thing like cross. Isn't a thing: it's either an x question mark check, mark double check, mark.

E

Anyway, tilde yeah hyphen.

F

Okay, so yeah, that was all I guess. This list will go too long for the x.

F

Yep back to abi yeah.

A

So uh the next item uh is by just uh which is our demo of proposed machine cloud.

H

So this is one of the previously proposed um login page but hi. I I just made it in the new uh new cloud and uh the old one looks like this. The new one looks like this, and so like abuse, what new changes I can make make it look, make it look better.

H

Because the back end is not connected, so the version is not.

D

Nice yeah and so josh like credit, where it's due right. um This is nikhil's implementation. Is that right.

H

Yeah, so uh previously it was in on, I think, html. Now it's on next yeah, nice.

D

Okay, um good yeah, I mean so you get an icon off in the bottom, um the youtube yeah and then.

I

D

If you would add full name and the email address with this submit that'd be great. We ideally need like um the ability to switch between either signing in or signing up as well. You might leave this one where it is as you head into the alternative version, and, and uh so so for this one, maybe you know like ideally like what's happening here- is that there's a number of places that need to use um authent that we might need to authenticate?

D

So as people go to play.meshary.io, they may need to sign in to have a temporary environment in which to learn, and so they would need an account to do so when they go to to sign in. Maybe we would want to show them uh a picture of play.measure.io like whatever that logo is. I think it's measurey learn, other people might be signing into the catalog and maybe we'd want to show them something. Catalog specific. Just as a nice we can.

D

We can show everyone the same generic thing that might be nice, those that are signing in into measuring cloud as it is today to use it.

D

As you know, remote storage for their mesh recessions, they might see something different, and so the there's kind of two two thoughts to have in the back of your mind and to work toward so one is the additional feature of not just signing up through a social oauth provider, but signing up just with your email address and and name, and then the uh the other component to that is like if you're a returning user or a new signup, we might need to distinguish.

D

um It would be nice if those two things could be one and the same right now they are one and the same if you're new and you click on a button, you'll get a new account if you're old and you're you're returning you click on a button. You just sign into your same account. That's nice! There's, no difference! You don't have to like switch between sign up and sign in, um as we add uh first name and email address, and then we add a like a sign in versus sign up.

D

If those can be one of the same, that's great, I think that they can. Another thing to have here is the notion that.

D

You might be able to use this same page, the same ui, but just have it configurable. So, depending upon what url someone is using to access the page, we could direct them. We can include that as part of the query string or part of the path uh to select the uh appropriate sign-in, whether it was for the catalog for mesh for play.measurey.io from suite cloud.

D

So what I'm saying is, if you can have one that has um a dynamically loadable component that would switch based on where someone is coming from that'd be good.

H

Okay, so for the sign of feature, should I make it in this page only this design only or the other design which you proposed in the sigma file, I'm saying that they would be one of.

D

The same: that's what I'm actually saying.

D

Or I get what you mean that, like this one doesn't have, um maybe just to help make it clear, is just push this one and set it aside as a separate html file or next.js file and then yeah as you work on the other design. That has a split window to take into consideration the things that I just said on that one.

D

E

A

Yeah so yeah after bunch full of.

A

Suggestions- let's move on to the next item, which is why borah about our machinery, structuring branch and point seven of planning yep, I'm.

F

F

Yeah so currently we are at mystery version, dot, six dot at least candidate five, w so parallelly. We are refactoring the mystery ui, using some of the principles that are using material, ui5 and redux as a state management tool. So if you are into front end of doing react, so this one is a good start for you, so you can pick up any of the small components or big one. As per your choice and yeah. Add your name in the state tracker and start working on this, and you can make a pr against this branch.

F

Make sure you you.

A

Should be sharing.

F

D

F

I hope it's visible now. Yes, and I won't be fine for two dollars.

F

Okay, so currently we are okay, yeah! Let me start again so currently we are at uh measuring version dot, six leave standard 5w. So, parallel to it, we are refactoring the whole machinery ui using some of the principles that are using material, ui5, react, 18 and redux as a state management tool. So if you are into react, doing love doing front end, you can just grab one of the component from the current machine, ui and re-implement, using the set of principles that are defined on the readme description.

F

So let me share this link in the chat.

A

From the next thing we'll be talking about this branch: uh let's have the you know localhost 4000 available, uh so that you can see what is the current progress? uh Yes, yeah.

F

H

I can show that I I have it running.

F

Okay, that would be great yes,.

H

Let me share my screen. I have that.

F

Yeah, thank you.

H

So uh in this branch we only have uh the latest thing is, I guess, the nav bar and others. The only thing we have in the branch is the dashboard page and other pages are just nothing.

H

So there's a lot of work here.

A

Exactly yeah yeah, so uh it is a you know, call correction or ask for volunteers so that they can drop into the machine restructuring branch and get some uh things landed in this page so that you can move further.

A

Meanwhile, since we are following the best practices, uh the contributor will also learn the best practices that is applicable everywhere in the uh next job or in the internship here as well. So anything you have to like.

H

So I I also want some suggestions like uh I will start working on this so from where should I start? It will be very helpful.

J

Yeah actually, like I guess, like we already have to have a spreadsheet, mostly like what you're trying to do is to you know, uh split the work that sounds like um we have like.

J

I will want each and every component to be atomic innocence, like every uh every interaction and everything that has to be done inside a component like you can actually take inspiration from the components that are already created as well, so we'll just have to try to replicate the the whole behavior that we have right now uh in the sense like for the home page. We right now have all these components, but, uh as you know, right now, we have the support.

J

We have added the support for multicultural as well, so that also comes into play and you'll uh maybe have to yeah design that and it's yeah. So that's how we'll start with this. That is, to start creating the components one by one.

A

Yes, then go with life cycle as a startup.

H

Okay, thank you. Everyone.

A

Yes, so ah gaurav do we have anything else like. I do have more comments to our television.

F

uh No, I guess, and it is covered a lot.

A

F

A

Yeah so uh yeah so just address some uh bugs in the settings page and uh his pr is, I think, ready too much so uh better. You would be talking about it right. uh You know.

A

A

So, first of all earlier there was like when there was no concrete file selected uh then also success message was popping up, so so this is fixed out. Some of the edge cases were missed, while verifying of the multi-context in ui.

A

And now, if you have no contact selected and you try to undeploy, deploy this message, pops up and if you have no contacts uh connected to measure ui, this motor will display that you don't have any cluster connected.

G

Okay, so that warning pops up, but it still deploys right. It doesn't.

F

No, it doesn't deploy.

G

Oh, I think we should. We should change that, because, okay right now, a lot of things are very community specific okay, but we don't want to restrict us, because this thing will, just if tomorrow we want to support anything out of communities on the back end, we can, but we will be restricting it here. So a watering would surface yeah.

A

I mean means if none of the clusters are connected, where it will deploy the.

G

A

Parameter there will be.

G

Yeah, I know that would be empty and the way it works right now is that it's the responsibility of the handling component, which is the adapter to main. So, for example, we are using using the same rpc call. So if there is no cube config, then it's the responsibility of the adapter to throw the error that hey, I don't have the cube config and I needed the config.

G

So, for example, if you have adapter and we are trying to deploy so kuma supports vm, so you're trying to deploy something on vm with there, we don't need any uh kubernetes context, and in that case the adapter is not going to throw an error. In any other case, of course, the adapter will throw an error, and that error is enough, and so we should not restrict. Basically to that point is.

A

I was not aware of that. Okay.

A

And this button was.

A

Made inside the table as approached.

A

Yeah, okay, so, uh according to you, the pr is complete. I reviewed the changes uh earlier to end uh from the last few. There are uh just few changes that were overwritten, so I think it is fine, uh since we have uh you know approval of uh chronology on this year, so it is fine too much. I will multicultural, so the changes are finally completed from your site. Right.

A

Yes, just one thing: ashish mentioned that user should deploy. Instead, the context are not selected: okay, okay, yeah. So if you can do it quick, then I was not aware of that. Yes, I will do it.

A

Okay, uh so then, let's move on to the uh item by dave here, uh vote for the favorite mesh logo.

I

Yeah we can open the link yeah.

A

I

As you know, we were working towards mesh map, which is an extension for measuring. It, helps us to you, know: visually design, our uh cloud native infrastructure and there's also a visualizer mode, so we are working towards developing a logo for mesh map. So these are some suggestions. Some uh you know these are up for vote. So if you have any preference uh from these options, uh please go over over here so that we can.

I

Finally, uh you know finalize on the logo so yeah, that's all you can vote right right now, if you want, but it'll be very helpful. If you share your opinions with us.

A

Yeah so so the voting lawyer voting lines are open till.

A

And yeah you should would by the way uh so that I you don't uh scold us after you know, we have planted one of these.

A

So that you can just go there and you know, interact and, uh like your favorite measure, give it up.

A

So, let's move on to the next item by each error, our docker.

A

uh I think we are missing jared here right.

A

The docker extension that we have just landed uh not very long ago, so uh it would be helpful in uh all of you to you, know, understand how docker extensions uh work with machine, and you know how it starts and what you can you know achieve by the doctor extension and uh the service machines inside.

A

Docker, so the next item is by lee: multi-context support are completed, so it's just a revisit. uh You would like to take some comments on it.

D

Yeah, just more or less in context of the fact that multi-cluster is the last significant feature to land in the current version of meshary. It's um a little bit confusing to me. Actually, we've been we are measuring, is still in its v0.5 release. Measuring is still a v0.5 project and uh the reason that that's a little bit baffling to me is because we've been so long on the precipice of releasing v0.6 we've had any number of release. Candidates.

D

Being released that it feels like we're already, it feels like we're about to release a dot seven, but in fact we're about to release dot six in context of the fact we're about to make that release. uh That means it's time to look forward toward what would be.

D

See this is a bit confusing yeah. I know what would be in dot seven right, what will go into v0.7? There's a roadmap for it. um It was discussed a few months back. uh There's some people who there's some contributors are still here, and some of those contributors are now maintainers.

D

Some contributors that were here are no longer here, and so we need to a revisit those that are.

D

Do you mind visiting that link for me, if you don't mind, um if you would just for those that are on the call of those that are looking to um and get you know, contribute and engage or just use meshri, please take a moment to review the different categories of functionality that would is intended to be worked on, so these are categorized by mesh reservoir, adapters, cli, etc, and then their top level features to be added or refactoring to be done. Sometimes it's not a feature.

D

Sometimes it's a like, in this case a refactoring of part of the persistence layer of measuring that the database type and what are listed are in individuals names as a feature theme champion as the individual, upon which there's some amount of there's accountability and kind of responsibility for pushing forth the future. They certainly won't be the only one engaged in that particular area, but that's both to help drive accountability, some amount of recognition, some empowerment and ownership for individuals that are here and want to take on those challenges.

D

I I need for my part, I can go through real, quick and empty out a couple of names. There's a few areas where we've got some some blanks for the rest of you.

D

You know I encourage you to take a moment to read through these there's some design specifications there's some mock-ups, there's materials that adjoin. What's here, if you're looking for more detail, please comment on the page and then let's get organized, let's, uh let's, let's go do this thing: let's go get 1.6 out the door and and start here there are a few of you who or most of us here really don't have that much to do in the dot six release because it's the plane is, has landed.

D

It's like it's time to unbuckle your seat belt. You know it's time to get your luggage shove, that old, lady out of the way in the aisle get in front of her. You know what I mean uh give her the elbow come on. I see some of you know what I'm talking about. Okay, maybe assist her with her bag as she exits the plane, but it's time to de-plane the plane has landed it's time to make the release and move on to this next one, and so for most of us.

D

That means what's next, so go. Focus here. Ask your questions: if you would some of the design specs need revisions, if you think that your name should be in one of these spots, raise your hand suggest it. um There will be a number of blank spots.

D

Actually, a lot has changed since this was published in december, which was about six months ago, cool but yeah. That's what I had.

A

Yeah, so of course, uh some names are outdated. uh It was posted six months ago. So if you are, as we suggested like, if you have anything, uh if you are feeling comfortable with any of these and if you are willing to work on any of these just uh comment here, uh uh you know has already given you the link for the discuss forum, uh particularly pointing to this uh page, so yeah, your you know, engagement is highly supported and we would love to get you involved.

A

Yep, so I think we are uh just over time uh just one minute, so uh we can have the rest of the items. uh You know uh as a future item in the next uh development meeting. So it's time to say goodbye to all of you and thanks a lot for joining us again.

A

Thank you. Avi thanks, bye, bye,.

E