wasmCloud waSCC Community, 25 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: waSCC Community Call (2020-11-25)

Description

WebAssembly Secure Capability Connector (waSCC) is a dynamic, elastically scalable WebAssembly host runtime for securely connecting actors and capability providers

https://wascc.dev

A

Okay, so we should have a uh pretty fast meeting today, the wednesday before thanksgiving um uh so uh shane. I don't know if you wanna do a quick introduction. You know I know you've been in channel for a little while, maybe like who you are what you work on, what you're passionate about.

B

Yeah absolutely so my name is shane o'donnell, I'm a developer at solo.I o uh and we've been using wasm in the context of envoy proxy, so we're using wasm to create portable dynamic filters that can be applied at runtime. To basically do anything you want http filter to do um and that's a huge boost for you know envoy over writing a c plus plus filter which basically involves maintaining an entire envoy fork. So this is a really awesome alternative that a lot of our users are really excited about.

B

So that's kind of our main interest in in wasm and so far I've been mostly involved in the logistics of building the filters, moving them around and getting them into the deployments. But you know I'm looking to get a little more into the nitty gritty of the awesome stuff itself in the coming weeks. Okay,.

A

That's awesome uh uh and a welcome board glad to have you um so uh as we look into our to-do's, we have pinned out from last week. uh Chris and ralph are both out, so I guess we can pump both of these.

A

For now, uh the microsoft team is, uh has a scheduling, conflict we're uh they're actually uh out this week as well, uh so we're waiting on them to see if we're gonna move this meeting to 12 uh or uh if they're, going to reschedule theirs uh and uh we had a new um architectural uh decision um log submitted kevin. Do you wanna speak to that? Is it number four here.

C

Yep yeah, that's the newest one, there's a couple new ones that we have issues for, creating uh like there's, there's a big one around the use of n keys and so on, but this one uh basically just states that whenever you're using wisem cloud, you know we'll have to change the wording on this one, but whatever you're using wisem cloud, you cannot push or pull uh interacting with an oci registry for either your actors or your capability providers without uh putting the embedded signatures in them.

C

In other words, security is, is mandatory when you uh store and retrieve images that way, the weismcloud runtime can guarantee that if it has pulled an image uh from somewhere that uh he can then go and do its security checks on it.

A

Kevin, can I ask: are there any downfalls to that like in denver, qa or anything like that or is? Would someone just be signing with a local set of test keys or something.

C

Yeah, so we thought about that um and actually letting people not put uh security claims inside their stuff kind of breaks, the wise and cloud runtime, because it assumes the existence of security, credentials and capabilities, and you basically can't dispatch your actor without the security context.

C

So it's far easier just to get into the habit of using dev keys in one place and prod keys somewhere else and to just enforce the existence of uh signed entities everywhere.

A

And where is this enforced? Is this enforced in uh wash or the registry itself is not going to enforce it right.

C

No, the registry itself isn't going to enforce it because the signature is embedded in the files, we're storing it's not metadata for the registry, but uh washing forces. It enforces it when you push and pull and wasm cloud enforces it when it uh opens the artifact before scheduling.

A

It okay good, so we've got multiple checks in case somebody were to use a non-watch client in order to push an artifact and try to get it right. Okay, so any questions on that you know or other feedback.

A

All right, um let's see uh the top 15 uh review, was the sort of uh the next thing. If we wanted to kind of do a roundtable status on um different components here, um you know kevin, you want to start how's the sort of core rewrite with actics coming along here.

C

Like I said, said, the uh sorry, I'm dropping stuff everywhere, the the main rewrite of the the core engine. So the core wasn't cloud stuff is done and it is probably 95 to 99 feature complete on the standalone version.

A

So just the last like 95 is.

C

Just what's left yeah yep there's the the the first 95 percent was easy. It's the last 95 percent. It's gonna take forever. um So that's that's where that is um lattice. Rpc is in there and done, and I'm probably about halfway through adding the control interface to lattice on that and yeah just making my way through there awesome um anything else. The the hardest parts are all are all the ones that are done.

C

So it's just a matter of going through and writing tests to make sure that I didn't forget some piece of functionality that existed in the old version.

A

Great awesome uh and then um anything else kevin.

A

uh No, that's it awesome uh bill. How's, the packaging coming along.

D

Yeah so uh wash the cli uh is pretty much done. I need to do a little extra testing around like the raspberry pi uh distributions and things like that, but we're looking good uh done on um rpm and dev or is uh you're still not working on brew right, correct yeah, so it's working for rpm and deb no homebrew for anything. Yet I'm currently working on the wasc d packaging, uh I'm running into some basic cross compilation errors using that cross tool.

D

So I should have that sorted out pretty soon um just trying to stay as consistent as possible between those two tools uh with how we actually build and ship those packages. Yeah.

C

It probably doesn't impact you too much, but in the the pr that's active right now for the control interface, the binary has been renamed to wasm cloud, not last d beautiful. I was kind of waiting for that, so that works out. Thank you all right, yeah, I'm waiting to rename the repo until after that pr is merged, but then also the wasp repo will become wasmcloud awesome. uh Air is.

A

For um on the cross, compile okay.

D

And so next steps um homebrew packaging for both of those tools. Okay, and I feel like mike, started looking into windows, one I'm not sure, if that's necessary, hopefully, people use anyways.

C

People still use windows, yeah.

D

Hopefully they're easily using the uh I forget what the uh acronym is there, but basically ubuntu on windows.

C

Wow liam's note taking uh brought me back he's using c linked list notation right there yeah that's right next raised to the power of next uh or.

A

C

My own uh isolated world of geekdom here and just pretend like you're you're dereferencing, a like list.

A

I'm all I'm all about referencing this operators, if you're, if you're careful, if you're, not careful, I might just leave one leave one dangling there for you. Oh man.

C

A

Can I ask you know we we have all these, like uh you know little death with the corals and uh you know all the little dev board you know for the jets and the nvidia jetsons. You know what os's are we do. We have on those the corals. Was it the corals or the jetsons was running something on? Is it just dev and rpm compatible.

D

Yes, yes, so it's more about the architectures. I think um I think the quarrel was running and I might be wrong about this. I think it was running some version or variation of debian yeah. The.

B

D

A straight up: arc64 linux, build that's perfect yeah, so that's that's exactly what we have the debian rpms for currently um so our arc 64 and d64 they're, the current builds. We can add them pretty quickly. um So when we once we need more uh it'll, be easy to just add them into the packaging. Okay,.

A

um Would you mind just making sure we run through around a test on those, like you know, just make sure it's on the to-do list? Okay, absolutely all right and then uh so. We've got home brews coming up and for that uh the demo that we have in a couple weeks that we're going to plan um the homebrew will be one of the critical ones for them. It looks like so that's yes, I did oh.

D

I'm sorry, I'm sorry go ahead. I was just going to say I did a tiny bit of research on that already um and it appears like you need a mac to with brew installed to actually develop uh like a brew tap, um which I do not have. That is off the corporate so that.

A

Might be a little interesting, but.

D

I'll get you one, it's no problem. Yeah. We should be able to figure it out, though I don't think it's anything you know complicated, but I.

A

I think the thing we'll want to watch for is the difference between the big sur versus uh court. You know the all the uh old um uh packaging. uh It was a lot of stuff's broken on big sur. Yeah yeah was having issues, so you all kind of that's going to make it.

D

Very interesting, but we'll figure it out we'll get it done. Super uh awesome anything else, though,.

A

Nothing for me, phil how's, um how's, the um the multi-language support coming for ypc.

E

Still holding strong at the three that we've got not much has really moved since then um yeah, I'm trying to think of where we left off kevin with getting things uh baked into the sdks. I think uh that's probably where we're at so.

C

Yeah, if you look at the, uh I forget the name of the repo there's a mega repo that has um is this on water kevin or no. No, it's in mosque.

C

But it has the.

C

Let's see if I can, if you can see it in there.

E

It's got all the whittles and the hooks to do the code. Gently.

C

E

C

um Yeah, there's there's basically one language there and it has a bunch of pre-compiled uh preset uh crates that you can use for uh http server and key value. I'm going to be creating a bunch more based on the you know, the first party providers that we have, but what is what is not? There uh are the equivalent modules uh in tiny, go assembly script.

E

No, that one would take a little a lot more extra work actually because, like there is.

D

E

Had to bring things like string to the party you know so it's you'd have to be a lot more opinionated still possible, but I.

A

Got a tiny go uh silly script and.

C

So we need tiny, go assembly script and then the remainder of the rust crates for the uh for the first party actor interfaces.

A

Yeah now, if I go to add a new, um you know actor or anything or a new capability, I won't need to update the sdk right uh I'll ride. On top of the sdk.

C

So if you build an actor on the existing rust sdk, it will still be binarily compatible with the new stuff that uses the codegen, but your developer experience will be different, so the the 0.15, you know the whole wisem cloud rewrite is also, um instead of coming with a single monolithic, actor sdk, which is what we have today.

C

You will be able to pick and choose the tiny actor interfaces. So if you only want to use an http server, you only declare a dependency on that http server actor interface.

C

Got it got it all right.

A

Got it and then um so when so, who owns uh that kevin? Do you own the sort of templating here or phil? Is that you who's got the um who's, got the to-do hanging on this one? Well, I.

C

Own the rest of the rust ones- and uh I was hoping phil- was going to take a shot at the tiny go and assembly script ones.

E

Yeah, that's on me. uh It's a matter of finding some time, I'm uh deep in some other stuff right now,.

A

Fair enough, fair enough, but I know you've got a lot going on phil. We love all the all the contributions here and then um are we going to you know, move a lot pc to the wash directory um so that it's all the you know together is that one of the things we've got in flight here.

E

In terms of github.

A

E

I didn't didn't think we were doing that, but we can certainly discuss it. Okay,.

A

All right, let me put a pin in that um on combining um uh the github um get up stuff um later we can take that offline uh and then um you know I've been uh go to my update. I've got, we've talked a bit about you know, like um you know, combining a bunch of the messaging into and the the blogging into a wasn't cloud um as a name as like uh the broader name.

A

uh So I took some time here- and I shared this out with a few of you to build out uh what we think the sort of experience will look like on the new website, um with dot 15 we've got sort of a rewrite of the docs here. The stuff in bold are the headers of what I was modeling. This after uh was um zeke.org. Here I thought they did a good job on managing.

A

You know um the sort of like experience and the layout, um including you know, like um you, know, documentation for long-term release and uh some other stuff as part of the documentation rewrite. I've looked at uh docusaurus, um obviously uh sphinx and a few other tools um that.

C

I don't know if you noticed or not, but the the page you pulled up for zeke's documentation uh is a hugo template. um This is spanx. Actually it's still a hugo template. Okay, I mean there's, I don't know what engine they're using to host it or whatever, but that that template uh the css and stuff for it is either hugo or hugo ish. But one of my open questions is: uh have we decided on a layout uh css template for the docs.

A

uh No, I think you know sphinx is pretty pluggable, uh but I think the first thing is sort of to sort of decide. What's the engine we're going to use, whether it's you know sphinx or um I'm not married in any way to docusaurus, it just looks like a very modern way to make um open documentation, websites and some of the uh some of the examples you know, look um look pretty good as far as like the guides here.

C

I think you've already called it out in that spreadsheet, but I think one of the features that we that we really want to have as far as documentation goes, is the ability to separate multiple.

A

Versions, yeah, you got it and that's to me feels like the critical one on you know having you know, there's a long term support release versus a future release um and versus what the master is that what I was really kind of going for here, so being able to version all the apis and having different landing pages, or you know what we launched under wasn't cloud felt right um and then also doing you know trying to pay a little more care on the onboarding experience on how to get into the community.

A

You know the faqs and stuff uh the tutorials linking the demonstrations here, the providers that we have um in day one and then organizing the community stuff a bit better with some upcoming events. So this is the 1.0 for the site.

A

If anybody has any feedback, feel free to just drop it in slack or here for next week, I'm going to try to have a first cut of this, uh so an mvp. I have no idea what technology I'm gonna use to do that it will likely just be a hugo template cabin here um that we can um integrate into um uh integrate into um github actions uh in netlify or um uh cicd. Is that for me it is oh. Thank you. I'm recording a call right now, though. Thank you so much.

A

I appreciate that my wife just brought me a beautiful lunch. Absolutely I'll show you.

A

I don't know: what's on it, maybe just mozzarella nice. I wish it were toasted, I'm going to take it back and put it on the panini press. Whatever it is, I could see all 4k worth of that sandwich.

A

I'm gonna just put the lights inside for right now, uh so any questions, your thoughts about the website plan and, um like you know what we're going to do there.

A

All right- that's my that's my friday, so I'll give you guys I'll start just dropping out early um early feedback and um uh and something else you know the the real intention here with the wasn't cloud stuff is too. We have all of these disparate discussions happening across the crestlet blog, the diaz blog wasp.dev.

A

uh We want to get all those together and wasn't cloud is actually a new llc, because we have a couple of discussions where we want to do some logo exchange. So, for example, if we're able to successfully get through the coral google coral.ai partner program, we want to get our logo there and their logo here. So we want to start getting those compatible with you know: google uh coral compatible with nvidia jetson compatible with you know. Iv.

A

I've got a meeting with ibm cto on monday by the way about um uh getting there doing an interchange with them too, and getting some support across the board. Here, it's look we're getting some really cool adoption of the tooling in various places.

A

You know phil with ypc and uh wasp, and but we're not we're not like reflecting that as a community and saying join us as a team and that's what the goal is with wasn't cloud ultimately wasn't cloud: the will go into a foundation whenever we get that set, but we're all sort of up to speed on with the bytecode alliance's team's transition from mozilla, vastly the linux foundation and the other parties.

A

There's just not a certain core plan out here yet for where we end up at the end of the day and my my point is: it could be another six months or a year before that stuff's ready and the sooner that we, like you, know just collaborate, the better. So that's what I'm trying to organize around lawson cloud, any thoughts or questions on that.

A

um uh uh So I'm super excited about it um and you know like we'll. um You'll start to you know, do things on your um uh backlog there, uh let's see so uh doc's rewriting mentioned, wasn't cloud the adrs uh we've got a crustal update that we're waiting on we'll get the microsoft folks on. Maybe next week um kevin you brought up the coda tutorials.

A

Do you want to speak to that now? Is it still just like just an idea stage.

C

um It's it's more like an idea. That's really uh it's sort of mentally in the backlog in your website map, there's a a section that says play with wasm cloud online yeah and that's essentially where the code of containers are going to go. The idea is that we want to give people a tanker playground that they can use to get over. That initial.

C

You know decision of well, you know how much work do I have to do to get this installed and if, if all they have to do to play with it is just open a tab and they're added terminal ready to roll with the tutorial text on the side, then I think that's probably the best the best way to get people into this tech.

A

I really love that kevin, that's so thoughtful um and that's probably as we you know, go through our you know. Do the we probably want to prioritize this a little bit into the first pass of the docs um a first, because that'll involve a rewrite of liking of the script for the tutorials, and then we can try to run this through uh on um uh on. You know, kinda coda and see how they sort of show up and how they work and stuff like that. But I like that, a lot.

C

I don't know if you have it on your on any of the backlogs anywhere, but the the edx.

C

What the heck is are those things called the mooc, the mooc, the the uh the edx online class for linux foundation, um that that deadline is january ish, so that there will also be another source of learning and documentation for this stuff. Great.

A

Super okay: well, I knew we were gonna have a fast one. Today anybody have any follow-up questions on what's in flight or um how things are coming along.

A

All right well, thank you, everybody I'll, go and stop recording. We can all hang out for a little bit and chitchat if we'd like, but have a great day.