VMware Cartographer Community Meetings, 23 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Cartographer Community Meeting - Feb 23rd, 2022

Description

00:00 Intro and welcome
00:57 New Resources page
01:35 Bi-weekly newsletter
03:10 GitHub Discussions enabled (first discussion is live)
04:43 Templates now have options
06:19 What the team is working on? (project board)
09:39 Tutorials
15:03 Convention Service updates
16:28 Tanzu Tuesdays

Community meetings happen each Wednesday at 8:00 AM PT/11:00ET
See the agenda here (https://bit.ly/2Z67z08), add any topic you may want to discuss and join us live!

A

All right welcome everyone to the cryptographer community meeting. um Remember the purpose of this meeting different the office hour sessions is to actually share synchronous.

B

A

With the community on the status and what's new on the project and some other news and also open space where users can come up and ask questions right um all right there, you go okay, uh feel free to add yourself to that in this list, and I would like to see if we have new faces uh well, not much well, mr scott rosenberg welcome and welcome everyone else in the team, all right. uh What's new in the project this week.

A

Well, some um some things here, thanks to raj, for your help, we have a new resources section in the website. It was something missing for a while a single place to collect all the content. That's been created around the project, blog posts, presentations and also playlists for the for the community meetings office hours so we'll be we'll be fitting this space with all the content that is in the content plan of the talks that will be out there in events etc. So we hope you find it useful, also a newsletter.

A

This was also in the plan for for a while.

A

um The plan is to share this brief, summary of again what's new in the project, but for the mainly list every two weeks uh for now with three sections, uh one around rfcs, uh the other around prs and issues um I'm measuring the most active ones. uh I'm not you know.

A

I agree that it's not the most accurate metric of all the most active discussions or the actual focus of the project, but I just wanted to make these uh at least this first version of the newsletter, something that I I could do on my own without having to you know, require time for the maintainers team to fill in here.

A

um It's it's a kind of accurate measure of what's in the product what's being happening, but it's not the best. I agree and also events talks, training blocks, whatever is new in terms of content, will live there right. So plan is again to release it every two weeks to the mailing list. If you're not there, please join the group, so you can receive not only the newsletter but also the calendar update.

A

Thank you. Rush, yeah right.

B

A

Don't have the um agenda handy, it's there in the chat. Also, all right uh also discussions, uh the github discussions feature was enabled for the repo and we have our first actual discussion and thanks again to raj who collected some of the thoughts around a question from a user in the upstream slack channel around retrieving resources.

A

So all the context is there and we welcome your comments, uh your replies there to and reach the conversations I I don't know if raj would like to come in something here.

B

uh Just the tldr, it's about being able to cause a resource to reconcile when it may have failed and doesn't seem to have become eventually consistent. uh Most common cause of that would probably be a techton run because they're not designed to become eventually consistent uh and people want to know how to do it. So I'd love to have a discussion about what the best way to signal those reruns would be.

A

Awesome yeah it was. It was interesting for me to find out that we could even turn issues into discussions, especially according to the github docs. Issues that are in a very, very early stage of development could be converted into a discussion.

A

Interesting all right. um Thank you. Your shotting blades can now have options.

C

Yeah pretty exciting new feature um in the past. A lot of the optionality and templates has been handled by ytt templating, so we are now offering a first class support for providing multiple options for a given template.

C

Do we have a yellow snippet that shows that.

B

Do we need to throw in work to do uh documentation and and or example, work for this.

C

Yeah so an example of adding options to a template shown in the yaml block right there.

C

You can select two different templates based on the existence of a field in the workload.

A

All right, that's great, that's great! Thank you. Joshua.

A

Cool um okay, what team is working on? Well, the best way to see this is in the actual project board.

A

uh Here we have two new cards that I don't know if we should move to just open or what is bom k pack using examples and the um rfc from james uh is there anything here that we need to discuss right now.

A

But this one is closed. All right.

C

I don't think zach's here right.

A

No it'll probably move too close and.

A

The rfc this one is a big one.

A

uh Yeah there's been some discussions there in the pr, but.

D

Yeah, I think the last comment was more about. I think there was starting a discussion around like priorities and whether these things about order of things, I think it would just be good. I think we can work our priorities afterwards. If we can just find out agree on what's correct things to be pulled out, and then we can come up with a plan of how you know how and who does those things community contributions might be able to encourage folks to help out as well.

D

So I think if we can come up with some kind of agreement, then that would just be a good step forward. Of course, this is also um something that's kind of linked to some of the other work we want to get out in the open, as well around convention service proposals.

D

What andrews has been looking at as well? So if we can just come up with some kind of plan also, you know what it is that we want to move out and agree on that. I think that would be really good.

A

All right and yeah you're right rush uh should be on the rsc board.

B

It I mean it is, it is tagged for rfc. I just think it needs to be taken off the development board. There is a button somewhere to do that. I just don't remember where you have to go back to the.

A

B

If you drop that right here.

A

Remove from project.

B

Correct yeah there you go.

A

This will remove this car from the project. All.

E

A

Okay, okay, thank you, uh yeah in terms of, what's being uh what the team is doing right now, we have a good summary here. um This one yeah this one. I think there are some comments needed here. I will touch on this later on. uh We have tutorials work. Well, wish you much not here today, also orphans and some other stuff does anyone else wants to come in something one thing is working right now and.

C

Yeah tutorials yeah. I was just going to touch on the tutorials because I don't think we've talked about them here. Yet the plan is to have a series of tutorials that all build off each other um that are time boxed that each try to achieve a particular outcome.

C

um So yeah, like the first tutorial, is short, build your first supply chain. The second tutorial is going to be replacing a step in the supply chain, then adding new steps and then creating a brand new supply chain that uses the existing templates um yeah. It's kind of like that's the basically the outline. What we want to do all bullets right there so.

A

Okay, yeah see here install stuff um if it does have something to do with prereqs install yeah, that's something that it's already in the works, uh quora and scott. They are working on a blog post. I believe oh scott's here uh regarding uh the three requirements. uh Installation process for cryptographer. Is that correct scott rosenberg.

F

uh That's gonna be one of the blog series that we're gonna be doing on cartographer. One is like how to get started and what the prereqs are in an opinionated way. I would say, like k-pac flux, you know whatever different things that are standard right now in cartographer um and giving a blog post on how you would go about doing that, um and then other ones will be on debugging workloads um and also understanding the nesting and the templates. And all of that. So it's going to be a multi-part series.

F

Awesome, thank you so.

A

Much exciting we're doing that. Yeah! That's awesome!.

B

There is a there is a discussion somewhere in the slack where I think um uh charles muyard um at least was quite curious about.

B

Where are recommended uh tools to use being documented? Obviously there is none at the moment, so that will be a helpful resource to be able to share share with him and with other people who are wondering what to apply in the open source to create a truly serviceable supply chain.

F

B

F

I'm also working on a repo right now of cartographer examples that are using non-standard resources so using kaneko instead of that using argo workflows instead of uh you, know, techton replacing basically, every single integration that exists in the cartographer and tap examples um into other tools, just to show the plugability and using jenkins uh and other things. So that should hopefully be out in a few weeks, I'm building like a whole set of supply chains and templates for other tooling.

F

uh That will be brought into the blog post as well.

D

It's interesting, this isle sounds fantastic scott. I'm really excited about that. um It does in a similar kind of I guess, thoughts, process of the previous rfcc that about spitting out that report as far more focused, but one of the ideas was to spit examples out, um and I know that you're building up these and you know people you want to be able to encourage more folks to contribute other examples, um and so I just wondered is those are those examples that you're working on?

D

Would you see that something that we could move under the you know, the cartographer? You know the wider cartographer ecosystem as a project and then maintain as well yeah if we figure how we figure that out.

F

I am more than happy to contribute that repo, when it's public to wherever would make sense and where would help the project from my perspective. So if that exists, and currently it's in a terra, sky-based repo, if that wanted to be moved to a vmware tenzu one or to whatever it is very happy to you, know, give that repo over um to whoever or if it's in mine. Obviously, anyone can put in a pr for new templates and happy to include those as well, so whatever the team would like. I'm happy to do.

D

That's awesome, brilliant scott, okay. Well, we can follow up more on that. um Obviously, it's very exciting to be able to kind of build a bit more of an ecosystem around cartographer examples of fantastic ways to do that, and that would be really really good. So looking forward.

A

Great, thank you all right uh follow up from previous meeting. We have an outstanding item from previous meeting. Was uh you know the the conversation of what status of the convention service and, if there's anything we could do to help?

A

um So I think I see yeah scott andrews is here sorry to call you ad. I I I don't know if you would like to comment something around there.

G

So going through the final hoops of getting uh basically final sign-offs and approvals to take code that was internal to vmware, make it public um have all the code staged basically just need to get the final like uh approval to flip the switch and make that repository public. And then we can share that repo and start having conversations about actual source code.

G

So soon, but not quite.

C

What's the what's the current plan with docs.

G

The the docs that we had, I don't think, are necessarily up to par, so I want to go through and rewrite them. So that's something I still need to do.

B

We have, we have a ticket in to get a cartographer's site repo and we'll move our docks to there. So it should be the right place to pop them.

G

um Yeah so there's definitely stocks that are in repo and then docs that should be like published on the website. Right.

B

G

Definitely won't contribute docs and it should be appropriate for the website to the website.

C

A

All right, okay, open! My discussion- I didn't have my name here. Okay, it stands tuesdays. um I will be live next, tuesday on panzer, tuesday, right march, 1st, with cora quora.

A

This is the first time I'll be publicly speaking about cryptographer, so I've been observing listening learning and the plan is here to actually do the introduction to the project the why the ideas behind it and cora will do the demo. um So um if you want to join you're welcome to join, you will be just backstage. No one here needs to be on camera, or something like that.

A

So if there are tough technical questions that we couldn't address, which is very likely- and if someone from you or are there will be nice but yeah. Otherwise, um I'm working on refining the message and and trying to make it clear for the audience out there what what what's special around cryptographer all right, um runable bug, moddy put this in the upstream slack uh regarding this book. That is probably not a bug, but uh just a misleading error message.

A

um So the invitation is for users out there to comment. If you have experienced something similar to this um issue, uh it would be nice to have a comment here. I don't know if muddy wants to. I think.

H

We talked about it, there was some discussion on the issue and we have a path forward. That makes more sense thanks to scott, so I don't think we need to discuss it.

A

A

All right, okay, I think that's it so far. Anything else you like to share discuss here.

A

All right folks, thank you for your time. See you next week.