VMware Tanzu Community Edition Community Meetings, 11 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tanzu Community Edition Weekly Community Meeting - May 11, 2022

Description

Tanzu Community Edition Weekly Community Meeting - May 11, 2022
We meet every Wednesday at 11am PT. We'd love for you to join us live!

This week we went over the v0.12.0 release with a demo on the Docker Desktop extension, our KubeCon plans for next week, and an updated demo of the kickstarter UI. Check out the agenda here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA?view#May-11-2022-Agenda

A

Hi everyone welcome to this week's edition of the tonzu community edition weekly community meeting. Today's date is: may 11 2022.. If you are watching this recording from home, we do encourage you to come. Join us live we meet every week uh held every wednesday at 11 a.m. Pacific time and we also have opportunity to to come, join us monthly.

A

We meet every second thursday of the month at 9. 00 a.m. India standard time- and these are opportunities for you to come and listen to what the maintainers are working on, uh provide feedback on what they're working on bring up any discussion topics you might have whether that's like a feature request or uh you need help with with anything on how to use the tonsi community edition. It's a really good opportunity to just to have that discussion in a live format.

A

But if you aren't able to join these- and you still want to reach this, there are other ways you can come find us in the kubernetes slack workspace in the tonzo community edition channel. You can find us in the github discussions. You can add your request, question or suggestion into the issue list. You can email us or you can find us on twitter at vmware tce for those that are on today's call and those that want to join us in the future. If you do have a discussion topic, you want to bring up.

A

You just need to add that to the discussion topic section at the end of the agenda and we'll get to it towards the conclusion of the meeting.

A

As a reminder, please read and abide by our code of conduct, which is linked out into our repo whenever you're attending these meetings or interacting with any members of our community, and that includes interacting with us through github or email and any of the other above channels.

A

uh If you are using tanzania community edition, we really want to know more details about how you are using it. So we created this pinned issue, and it just asks you to provide a few details about yourself about how you are using the tons of community edition, and if uh you would like to add your logo to the comment, you would add it to the adopters file here, but that part part is optional.

A

Whatever you share here, it's very helpful for our maintainers as they are working to develop the project, and it's also helpful for the community to understand how others are using it in case they might find it helpful to um to figure out how how they can best use it in a similar use case. So we highly encourage you to fill that out. uh It would be super helpful for us.

A

And for those that are on the call today, just a reminder, please add your name and any organization that you are representing here in the attendees list.

A

Moving on to announcements, so we got several announcements this week. First off we will not be holding our monthly community meeting, that's scheduled to be this week and instead uh we're canceling it and we'll see you june 9th, which is the the second thursday of june and then for the next two weeks. So next week and the week after we are canceling this weekly community meeting and that's in large part to kubecon happening next week, all of the travel and pto that folks are going to be on for the next two weeks.

A

So it just it just made sense for us to hold off on meeting until we have something to bring up and to have make to make sure that people that can answer your questions are going to be present. So we'll see you again on june 1st after this meeting.

A

Moving on to some content stuff, the the big ticket item here is coupon is happening next week in spain, so there are ways to find us at the event. Several several of us are going to be there um informally.

A

Formally, we want to meet you in person, so we will be having lunch every day of the conference in the provided lunch space, those lunch breaks are scheduled to start at 12 30 central european standard time each day, so uh you know be sure to be there, look out on twitter as well as slack for updates on where we are sitting in that lunch space. So so you can come, find us and say hello. We can get to know you um super informal casual stuff.

A

We just want to want to meet folks in person, while when we have the opportunity to do so and now on to some formal ways to to hang out with us and to to listen on some talks, we will have some workshops that are hosted by the devrel team at the vmware booth. We're still ironing out some of those details as to to when uh some of those um went soup.

A

Sorry about that, when some of those workshops are gonna be happening and what the the actual content will be, I know there's going to be several different ones and with several different, um interesting forms of content, so be on the lookout for those details. Well, we'll try to share them in twitter and slack once we have them and uh let you know more uh as soon as we have that information.

A

B

A

B

I said this damn basket um just wanted to give a little more detail there. So so the workshops are are self-service, so there's there'll be three systems set up with uh operations, developer-focused workshops, I believe they'll have six different workshops going and ways to earn swag by going through those workshops.

A

Okay, that's very useful. Thank you cool um and then says robert asks. Will there be tons of tce stickers at the booth?

A

uh I imagine there's going to be some tons of stickers, uh not sure tce stickers, in particular I'll, have to look into that and then uh stephen palsey says whitley lee has a talk on friday at two.

A

uh He thinks it might be about k native and then she's off, also speaking on k-native day, so uh whitney lee is, with the devrel team, um we'll we'll put that information on there as well.

A

uh Once you have a little bit more uh anything else in the vmware booth stuff.

A

Before I move on to the talks, okay, so we have several talks that the team is doing and it's not they're, not necessarily about tce, but these are folks that do work on tce and they're talking about different stuff that they're that relates to stuff that they work on or they're interested in or they're passionate about when it comes to kubernetes, related and cloud native related items. So we have david he's doing a talk at the cloud native rejects.

A

uh We have v, who is doing a keynote at k? Native con that one is particularly about uh tce.

A

We have john mcbride uh one of the maintainers for tce. uh Doing a talk at cubecon on wednesday. Have myself doing a talk about being a community manager on thursday, and then stephen wong has, I think, about five times box he's doing a kubecon between thursday and friday, so be sure to check out. All of uh all of those talks come find us come, say, hello. We would love to see ya anything else. Regarding kubecon before we move forward.

A

All right other announcements, so the team is aware so folks in the community are aware in case they are interested in submitting a talk covering anything related to tons of community edition the kubecon cloud native con north america. Cfp closes may 27th, which is the following week after kubecon europe, and then it's it's coming up really fast. It's gonna, it's gonna, be closing about two and a half weeks. So just keep that in mind. If you are interested in doing a talk over tc e and you're, you know you aren't part of the core team.

A

Please reach out to us. We would love to know more about what you plan on submitting, and maybe we can do a joint talk who knows um but yeah. Let us know on that.

A

Moving on to the release that happened just yesterday, so we released odot 12. We have a link out to the release notes here. There are several blog posts for you to review super really interesting stuff here, covering um uh enhancements to unmanaged clusters and the app toolkit as well as now being able to use tce from the docker desktop extension.

A

So with that, I'm actually going to kick it over to john to show you what that is all about.

C

Yeah, if I could grab the screen.

C

All right and keynote alert your eyes while I start playing- oh, my goodness, all right, uh yeah, 0, 12 0 just released yesterday uh and, as we have kind of noted in a bunch of other demos before this uh there's a bunch of other cool features in our managed cluster and in the packages app toolkit 0.2.0.

C

But one thing that was a bit under wraps uh that, if you missed the dockercon keynote yesterday, is that kansas community edition actually now has a docker desktop extension and the whole extensions. uh I guess framework and sort of feature is new in uh docker desktop. So uh what I want to do is actually, let's take a quick peek uh at this. Let me go over to docker. Desktop uh here is the extension.

C

Let me to the zoom controls- and uh this is the extension here huge shout out to people and other people involved in a devrel team. This was a huge effort on their part sort of getting this bootstrapped and ready. uh But from this tab right here from this extension right here attains community edition. We can create a cluster. So let's just do that.

C

We're going to create cluster and for a lot of people who have uh sort of been tuning in and following along with development through the cycles of all this, these laws, logs that'll pop up here, uh should look pretty familiar. Actually, these are the unmanaged cluster logs and kind of behind the scenes. What's happening is what's getting created, is a unmanaged cluster and it gives the user on docker desktop here.

C

The sort of I guess kubernetes uh right from this extension, uh so this will take just a hot minute again to get going, but uh it might be lagging just because I'm sharing my screen, so uh this is supported on an m1 map which I have right here running. uh Obviously the intel macs windows and then linux docker desktop support is sort of experimental, even beta, but uh in theory it should work there as well. So uh yeah there's any intermittent questions. I see something popped up in chat.

C

uh What's the red green 100 bar at the bottom? Oh, that's my battery yeah, that's a t-mux framework for uh what my battery is on. This laptop go t-box uh yeah. So this will just take a second uh what's happening. Right now is the cluster has bootstrapped again if you've been following along behind the scenes? What's happening, is a kind cluster has been uh created and we're sort of instantiating a lot of the tanzu uh bits and experience things on top of that right now is cap controller.

C

Next is the package repository with the core packages and user manager packages so right away, the users can get going with getting app toolkit installed or observability stuff or really whatever whatever is on there is available.

C

So this will just take another second, any questions about this.

C

uh I can't show we do have docs as well head over to community edition.box.

C

Docs so yeah go ahead.

D

Are we does that put in any more packages than the standard tanzu unmanaged cluster create, or is it basically exactly the same? It is exactly the same.

C

D

Same sorry, go ahead, I thought he did something with routing, though so that, like um you, actually have a routable local host address in the cluster.

C

Yeah yeah, that's that's a great question. We can look at that quick. So if we do docker ps uh that output's a little gross, but you can see that we have uh four four three exposed and uh so uh just 80 looks like uh so those were kind of the same defaults of like okay. If somebody wants to deploy profana, then 80 will just be available on the host into the container so that you know they can see their dashboards or whatever or my web app or something.

C

So those are the two same defaults that we provide just out of the box. As far as other configurations, there's there's not much right now that we can do to configure that cluster deployed via docker desktop, um but uh that is definitely feedback. We're looking for in the future uh to be able to configure this and add. You know an unmanaged cluster config file that you could drop in maybe or something yeah but kind of what I was showing here so yeah.

C

If you go into our docs and then the getting started under getting started is deploy with docker desktop and we'll walk you through all the steps.

C

uh Yeah, I don't know why this is taking a hot minute, but uh once this finishes we will be able to use a cube cuddle to get stuff on the on the uh on the pods uh look at resources, and if you have the tanzania community edition uh cli installed, then from there you can do all the packages and things so say more chat. What else is in here john's awesome, meter over nine thousand? Thank you. Thank you.

C

Yep huge shout out to jorge. He did a great job on this uh and and drove a lot of the uh sort of work getting this out there. The engineering team only came in at the 11th hour to you know, help kind of get this across the finish line. So a huge shout out there.

C

uh Any other questions on this, while this is bootstrapping.

B

C

Oh, is that what it is? Oh you're, totally right? Well, I can't disconnect now uh yeah so for those unaware uh some of some of the images networking takes just not just a tad bit longer uh on the vmware vpn, but uh that's okay, so uh yeah this gives you a pretty good idea. Maybe I'll just continue on this gives you a pretty good idea. You know what you can do uh from this extension uh when it finishes.

C

Oh there, it goes all right. It should be done in just a second now I have to package repositories so when it finishes the other option you get in this dashboard here is an actual delete. uh The delete, then, would just get rid of that cluster. uh If we look at containers, this is interesting. Yeah I have a bunch of buildex stuff, but down here we can see the tanzania community edition control plane. uh This is the actual pod. You know the kind cluster that's running. uh I guess container.

C

That's actually running the kubernetes uh behind the scenes here I have you know uh uh something check mark, so I can see sort of the science behind the scenes here. This is the uh container that is actually doing the bootstrapping from docker extensions, so these are kind of the two behind the behind the scenes things we come back over here still doing the package install.

C

That was my mistake being on vpn good to know for next time. uh I can also show quick those two other demos that I think I linked in here. uh I linked these two youtube demos. uh The first one is one from a few weeks ago with unmanaged clusters, minicube provider that came in.

C

And then also the install packages and uh some of the nice to have features around installing packages is in this demo as well. That was from, I think, just two weeks ago, so definitely check out those demos to get kind of a really good overview of what is a part of this zero 12 release.

C

All right cluster is running uh cool beans. uh Can I get pods now there? They are all right great, so uh everything is up and just like with the unmanaged cluster sort of normal workflow. If you did tanzu and manage cluster create my cluster, it will merge the cubeconfig automatically and uh it also comes with cubecuddle uh when you do this uh from like a brand new system. So if you have a new computer, you get docker desktop. You get the community edition extension.

C

It should have a cube pedal as well, so you can start doing stuff uh and then uh actually might not have tansy on here right now, nope, but in a normal case you do tanzu package, install, etc, etc, and this is the full experience from this point onward. We come back to dr desktop cluster is running everything's. Looking good this tab here is useful if you need to grab the raw cube config with all the secrets and all that stuff in case uh something went wrong or you got like some disconnection or something.

C

This is the cube config, so you can access the container on your host. So then, if I come over here, I do delete and that container uh just gets blown away and there it is it's gone. So that is uh the tanzania community edition. uh Dr desktop extension kind of brings me back to point zero, where we can create a cluster from here uh yeah, any other questions or thoughts from there.

C

Yeah some good discussion on the m1 josh made a good point that not all packages may work with arm, which is the apple m1 computer.

C

Looks like there's some trouble shooting happening as well. Definitely happy to help you try to shoot in the slack as well, but uh that's it for me.

E

So uh just uh putting my pm hatch on just a quick note. um Anything like please try to try this out if you're a docker user uh see if it works for you. If it doesn't like, I can see uh unosa having trouble with it in the chat. um Anything doesn't work. Let us know if there's a feature missing that we really need to work on. Let us know we're actively working on this right now and any any feedback is very much valued. So please don't hesitate to reach out.

A

Yes, awesome good stuff, thanks, john and and thanks v for for bringing that up any uh any other questions or comments.

A

Okay, uh moving on to oh before I move on just want to point out. There are two other demos here for mini cube and install package, so be sure to to look at those as well.

A

Okay, oh whoops.

A

What happens where am I.

A

Please there we go uh okay updates product management, roadmap updates uh v. You want me to just spit this out, or do you have more? You want to stay on it.

E

A

So uh we we are currently working on some some room map updates some more like processes, so once we're back from cubecon and all the traveling that we've been doing so, you know, sometime in june, we will have more details and we're going to present that new process and what we're hoping for is the community have more involvement in um and how the road map is developed, so stay tuned for it for more details regarding that and we hope to have something more to share uh come june.

A

How's that that worked did that work. For me.

E

Yep, that's great um so another. This is another area where I'm looking forward to hear what everyone has to say and their experiences, and you know what's what's working, what's not um we're listening and so we're trying to make the process reflect that um so for the next release for v13 we're already working on some things, v14 is gonna, be basically everyone's fault. uh Whatever we end up doing so we're just trying to. um I was going to make a joke about we're going to spread the blame.

E

If anything goes wrong, I'm not sure that's a good joke to make. So, let's pretend.

A

You can blame me I'll, take it all yeah, it's all about your.

E

A

Yeah I manage the community, I take the blame. You know. uh Okay, moving on to the next point, uh we have a guided ui um demo coming up. Justin want me to.

F

Sure, yeah hi folks um I'll go ahead and share my screen and okay all right, so um it's probably been a little while since um folks who were interested in this project have really heard from us. I know steve and jorge gave us some really valuable feedback early on with some of the mock-ups um and since then we we've been heads down really just uh trying to get a working model up and running. um So a lot of what you'll see here is, you know partially complete.

F

um There are definitely areas that uh need additional work.

F

um You know content copy and so forth, um but just wanted to uh give an idea of where we're at and uh hopefully soon as we have things working uh end to end, we'll we'll be able to uh solicit some more feedback, see how how things feel as folks in the community can can try the plug-in out that we have um so yeah just uh taking a step back, um we do have a working plug-in for the cli that is uh very specific to to ui for for cluster creation, for management, cluster creation uh workload, cluster creation- and uh you know we'll be uh moving forward on um on unmanaged cluster creation.

F

Soon, uh mockups are are currently being worked on there. um So and uh just one other point, I if you guys have feedback, please um just hold off and and we'll take it uh at the end of this walk through here.

F

um But what you're seeing here is uh the the welcome screen or landing page that the the user will will first reach when they uh fire the the plugin up, and uh you know the cli launches a a browser window and this ui comes up. um So what we have here is, you know, very basic intro. uh If folks, are you don't know what they're doing they're ready to jump in, they can go ahead and get started. It's you know clear and right right in front of their face here, additional content on this screen.

F

We have this kind of rollover, banner component, which gives us an opportunity to maybe help answer some of those. uh You know important questions that a first time user might have up front. um Maybe uh you know direct the user towards um information on. You know the community experience, um but some other thoughts we have here were, for maybe uh cross-pollination of of other products and areas of the suite. um Specifically, like you know, managing clusters at scale.

F

uh You know this could potentially be um sort of like a like a call to action for the user to learn a little bit more about tmc or you know, once they've gone ahead and created their managed clusters. um You know learn a little bit more about tap in an application platform, um so we'll we'll work on the content here, but um you know just the the framework is in place, so I'm going to go ahead and click on let's get started now.

F

The next screen that we have here is talks a little bit more in depth about the types of clusters that can be created and is sort of a little bit of a launch pad for for diving into those workflows. um You know the first two obvious ones are management, cluster and workload cluster.

F

The app will detect if management clusters are uh already created, or you know the cli is aware of existing management clusters um and only enable the create workload cluster uh button here.

F

If a management cluster is found, and then we do also have a call out to unmanaged clusters down here, we've worked a fair amount on these graphics, but you know they they are subject to change, uh definitely open to any feedback there, and what I'll do here is jump into the creative management cluster workflow, where the user will then have to select the cloud provider that they want to create the cluster on the workflow that we're working on first right now is aws.

F

Raymond is working on the docker workflow as well, but aws is a bit more complete, so we jump into the aws management. Cluster create workflow, and what we have here is is what we've been calling the simplified workflow, where what we do is uh sort of in the background set as many you know reasonable and recommended defaults as possible, so that we can. We have to expose as few controls to the user as possible later in the development cycle.

F

What we'll be doing is working on sort of an advanced settings view where a more experienced user can uh you know, tweak more of the knobs and switches uh as they see fit, but um what we've done here is try to identify really just the the minimum number of inputs that a user needs to successfully stand up a management cluster.

F

um So the uh the the aws credentials screen here uh somewhat familiar to what folks may have seen in the kickstart ui, whether you select a credential profile or the uh one time or temporary credentials for authentication. So um right now, I'm I'm. I have this ui running just against a mock api server. So a lot of the data that you'll see here is uh is all mock data, although we currently are working on, you know full end-to-end integration and we do have the majority of apis working end to end here.

F

So I'll select a credential profile, I'm going to select a region, I'll connect will likely show, like you know, connection successful uh message here, just haven't gotten to it yet, and then one of the nice features that you might notice on this page is that um sean has helped us add a uh an api for ec2 key pair discovery, which I've tested end to end, and it is working um so I'll just go ahead and select one of the mock key pairs and hit next.

F

So, as you can see, uh really simple only two steps to this wizard um now on the cluster settings screen here uh there are just a couple of uh choices that are required. um You know first setting a cluster name and then the uh control plane, node profile, and what what this does is.

F

It uh simplifies some of the controls that folks might be familiar with in the kickstart ui, where it um makes the selection uh between, like a dev being single node or a production, three node control, plane and ties that, in with a recommended aws instance type underneath. So we have.

F

You know your standard single node deployment, a high availability deployment, which uses the same instance type as the single node and then a production ready, high availability uh control, plane, node profile, which is also you know, production or three nodes, but with a different instance, type underlying one thing that I'll point out on this screen is that, because we are setting so many recommended defaults, the user might want to see what some of those settings are.

F

We haven't implemented it yet, but I threw a uh a clarity flat button in here um to illustrate that the user would be able to click. You know some call to action and will likely bring up a modal window. That shows a lot of the the underlying settings, whether it be you know, service siders, uh you know, ips what the actual instance types are and so forth.

F

So uh once the user's completed this step, we'll go ahead and create the management cluster also a somewhat familiar view as to what uh is seen in the kickstart ui. But in addition, we have called out some next steps for the user. Here um you know a link to the uh the uh location of the management cluster configuration file, maybe uh cli command equivalent for uh generating a workload cluster off of that management cluster, and we could also play with some other useful links down here.

F

So I'm going to go back and let's get started now, I'm going to dive into what we imagine the workload cluster creation workflow might look like, and this is pretty powerful. So um I'm going to just have to ask you to all kind of you know.

F

Look through a creative lens here understand that we haven't gotten around to css styling and making this all look really pretty, um but have done a ton of work um on some of the uh the the underlying technology here that we're building out um so the first step in in creating a workload cluster would be. You know, selecting the management cluster that you want to create it on.

F

So we're going to go ahead and select the first one here.

F

The user will have to add in again some very basic information and selections here being a cluster name, so we'll say my first wc and select a recommended instance type, which will you know likely be as you can see. A slightly different list of uh you know recommended profiles that you might have noticed in management, cluster creation, I'll just select basic demo and move to the next screen, and this is where the magic really happens.

F

So the workload cluster creation workflow is uh based on cluster class, which which folks may or may not be familiar with yet, um but cluster class is uh sort of like a like a well-defined uh you know, format or topology for creating workload clusters um that extends beyond uh what folks have seen with you know a traditional config yaml or legacy style approach.

F

um So what shimon has done here is started on building out a uh a data driven ui, that's based on the cluster class variables, which you know we think in the long run, will be very, very powerful, um and these cluster class variables are categorized a few different ways. There are optional variables, um which you know the user is probably like.

F

50 50 going to want to actually take a look at and and make some tweaks to whether it be the cluster plan, whether it be you know, size, control, plane, size, worker, node, size and so forth.

F

There's another category here which are far more advanced variables, but not required.

F

What I'm going to do is step back and select a. I hope I select the right one, a different management cluster, okay, and we can see that the uh the categories have changed from from two different categories to this additional one which is required variables, and that's because this workload cluster is being deployed on a management cluster which exists on vsphere and therefore there are some required variables that the user absolutely must enter uh to have a successful workload. Cluster creation.

F

So um I think that's the majority of what I have um shimon. If, if I missed anything on the workload cluster workflow, please let me know, but any questions or comments.

A

We do have about just about five minutes left, so if any folks have any any questions or comments, we have about five minutes to discuss.

G

I wanted to just add one thing to what justin was saying: he's absolutely right that that's a data driven um ui there for creating a workload cluster, the idea being that whatever work work, whatever cluster classes on that management, cluster can be used to deploy a workload cluster.

G

Ideally that means that in the future, if somebody created a cluster class on their management cluster, that was custom to the way they do their workflow, they could use our ui to actually create workload clusters using their personalized uh cluster class. That's what we're aiming for.

H

That's amazing. That was what I was just about to ask, because I use core cappy and have a bunch of cluster classes. So that's awesome. This looks amazing um from a user perspective. I'm very excited for this.

F

Great, thank you yeah and, and um you know, once we get the uh the end to end story uh for some of the workflows tested out a little bit more. uh We we definitely want to get this in in the hands of folks.

F

Who are uh you know interested in and uh trying it out, and you know installing the plug-in um providing some feedback, but um definitely just want to have you know that that uh working code, the stake in the ground before um we, uh you know we we get stuck iterating too much over mock-ups and, and uh you know, start to lose, uh lose out on the timeline here.

H

Is the idea down the road to also add package installation from here as well or anything of management of a cluster day? Two upgrades or anything like that, and I know that's far out- and this is already a huge improvement, just wondering what the scope of this is planned.

F

H

F

No, that's a great question, I mean um you know the fact that we're now leveraging um you know an individual component for the ui. I think will give us that flexibility. um I would have to defer to v uh to make the pm call there. um We we absolutely could um you know we're and- and of course you know we're all for it. We we want this ui to be as robust as possible.

E

Yeah so with uh install packages uh introduced now uh that becomes basically it's one more one step closer to that direction.

E

uh We have not planned since you asked specifically what's planned, so we have not planned for this yet, uh but it's definitely like it's definitely something to to be looked at, so don't have any formal plans, but we don't don't have them if that makes sense.

H

Makes sense, yep awesome.

F

Great anyone else, any other questions comments.

F

Okay, I'll stop sharing, and um I I did uh create a um a github issue for this plug-in where we can uh collect some some general feedback uh pre-mvp.

F

um I can share that link out and um you know it's it's. You know really something that's just intended for our ui team and and designers to have a look at and and kind of take that feedback so I'll share that in the chat here.

F

All right, thank you.

E

I'm I'm gonna add this link to the to our meeting notes. So if anyone wants to chime in later um feel free to well, please add your comments. There.

A

Yeah, thank you v read my mind uh and thank you justin for for showing us that it's, it's really awesome to see the the progress y'all have made it's and super exciting, um looking forward to folks that are watching this from home and and hearing all's feedback as well.

A

uh So with that we are at time, and we um are so happy that y'all joined us today. Again, we aren't meeting next week or the week after we'll be meeting again the first week of june on june 1st.

A

If you are attending kubecon, please be sure to come, find us keep uh up to date on where we are and where we'll be at lunch on twitter and on slack, uh and we we're super excited to see everybody in person in spain and we look forward to meeting everybody with that. uh Have a good one see you soon.