Kyma Community Meetup, 31 Aug 2020

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Kyma Community Meetup 26.08.2020

Description

This virtual event is designed for end users, a space for our community to meet, get to know each other, and learn more about Kyma. We plan to have at least one demo in every meeting, with allocated time to discuss this in small groups.
Agenda:
🌱 See how can you version your lambda function code in Git and delpy via Git push in Kyma - hands on (Marcin Witalis) - 2:00
🌱 See the status of our Kyma Homepage Redesign :( Valentin Vieriu) - 27:39

Get the meeting agenda to find out what topics are planned for the meeting.
https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8

Find out more about our meetup at : https://kyma-project.io/community/collaboration/#kyma-community-meetup-kyma-community-meetup

A

Hello, everyone welcome to our well another meetup. We managed to to skip to uh it's summertime. I think a lot of people were in vacation, so we had a little bit of a of a crisis for topics, but uh today we have actually a very, very interesting topic, um an interesting topic that was presented before as a preview or more like an idea, and now it's quite advanced into our pipeline and quite soon um this probably would be a tool that you could use in your day-to-day keema pipeline.

A

So um let's not take too much too much time on our agenda. Today we have two topics: marcin we'll talk, the most important one, uh most important topic about versioning lambda functions uh in git and of then deploying them in in our uh serverless environment in kima, and then um I have only a couple of uh topics that I want to share with you regarding our uh homepage redesign.

A

Maybe I should actually clarify this. This is not the entire web page, it's just the home page of uh of keema and I just want to share the preview, and maybe, if you guys want to have give some feedback, uh you can do it asynchronous later. So that's it! That's uh the agenda of the today marcin.

A

The stage is yours.

B

Okay, so let me show my screen guys.

B

B

Okay, you should be able right now to see my my screen. Is it.

A

B

Yes great, so we will, we will talk about versioning under function code via git, in a serverless. uh Let's quickly summarize this one okay, so so, basically, we are changing the functionality of how we manage functions. How can version functions because of couple of problems or limitations, maybe that we had?

B

First of all, there is no version controlling there were no version contribute before uh the second one project structure is uh was a big limitation because of uh actually user could write only in one file and was limited only to it.

B

The thread is uh that the code was directly attached to cid, which which actually was not handy and actually the only the only thing that could work with with this was the web editor, which could actually let you edit the the code, uh and but this was the only tool and before we proceed, we need to meet someone. That's his name is matthew and he's a cloud engineer. His open source, enthusiast and contributor he's keeping this expert and his mother is. Is there any cli for that?

B

So this is the guy who we are addressing this functionality too. uh We want him to have a way to deal with the version actually functions, uh but he's writing uh with git with a continuity, so without further ado, let's jump into the demo. So uh maybe a couple of uh couple of things. Sorry, uh I prepared this this layout, so at the bottom we will get the left the functions that will be created on the right, the repositories that will be created. This is just a description.

B

Okay, so we will go through two scenarios of the functionality to check what matter can do and the first one is the basic one which will uh which in which we will create a function based on the repository repository hosted on github, and we will check if the function will be rebuilt and the function will build in case of changes in the code, so we'll check for code for the head scenario. So let's check the sources that we are going to apply, so I will show you first the function so a couple of changes here.

B

First of all, the new field source type is present. It's optional field that shows that the code is versioned in git.

B

The source property also changed before the entire code was attached to it right now. It shows the reference to git repository object.

B

Reference is a field in which we can specify either the branch or comet that we want to to our function. Sources from. If, if we reference master branch, we will follow the head. So actually any comment will trigger rebuild of the function. In case we put some uh commit, we will be fixed on on some some revision right and the last field is a runtime which is the language of the lambda. Actually, we support, we will support actually three run times. um This is the node.js 12, which was actually before.

B

uh Also, we will support note just 10 and python 3.7, so there will be completely different, let's say, uh platform available soon. uh Let's check also the repository that is corresponding the this function. This is a simple configuration for this uh repo, which is just as I mentioned on github it's publicly available. We are using https protocol, so it's like this is the total of the how how the mechanism will uh check and we require no authentication here. So there is no field of specification, so let's apply those guys.

B

B

Okay, you should be able to see red pawns.

B

Okay, so cup, so uh as you see, the function is uh configured its state of the build is right now it's unknown, but hopefully in a few seconds it will be true, which means that the function was built and now it's been uh we are starting, we think, and then we are deploying it, so it will be available as soon as it will be available. We will jump into web console and we will add up your rule and check if the content of the of the.

B

Laptops, so maybe one more thing before we jump into the console: let's check the code, I've already.

B

Already cloned the public, github surface story and let's check the handler.js this is maybe this is the structure of the of the repository. It has only two files, it has handler and package. So it's like pretty similar to the previous, uh the old, let's say um layout: let's check the content of the handler function, so we are expecting actually, of course, hello world which is like return from this module and let's uh jump into the console and create app rule. Let's call it now off.

B

As you can see, the service is already here. So let's create a payroll and we should be able, in a couple of seconds to access the the hello world function from git. So, uh let's no, let's right now, let's change something to the uh to the handler to demonstrate that it's actually doing stuff.

B

It's checking the change on the changes. So, let's fix it.

B

Okay, so here we have modified it. Those are the changes.

B

Let's commit it: okay and okay: let's push it to the master okay, so it's actually, it was pushed to the public repository right now, the um right now, the function controller will should trigger the rebuild of the functions and since its source code was modified, this mechanism is kicking in like each minute, so it we might. We might need to wait some some time to to observe the reaction, but eventually we'll see the.

B

Changes to the code being applied, so maybe a couple of oh, maybe that's because it's already kicked in so actually we are rebuilding the function right now, as previously right now in the new commit, because we are following the head, so we'll re-run the the entire function and surf new body content.

B

One maybe uh thing worth mentioning is that if in some for some reason we will fail to build the function, we will not stop to serve previous implementation. So in case any errors, we will have the version being served as it was. The uh re-running is only triggered when the function was successfully built, so without further ado, let's check it and we should be able to see- and we will see community hope art. So this covers the first uh scenario that we wanted to. I wanted to demonstrate.

B

The second one is a bit complex because we will use private repository and let me show you the object that we go back.

B

Show you the objects that are going to be applied, so we will create a function again, but it's also under the git source control. This will be the reference to the to the repository that we will create. We will use master as master branch as a reference. Runtime is the same and based there is that directory. Let's check the check, the repository, which will the previous one.

B

So it's like this url is a little bit different, because you can see that we are using a different uh protocol and actually uh also we will have authentication method uh which will which in our case is um key with a password. So we support no elf. We support basic authentication which is using uh password, and we support also the authentication of key with password and with our password. So we have all possible combinations of authenticating.

B

Of course, this approach, the first cell to be because we have a here- you have a secret name, which is a reference to secret. That contains a credentials. So we show this secret, and this is uh this: those keys will be removed after after our presentation, always let's just I just want to show you how it's uh so. This is a secret um which contains uh certain the key and the password to close it. Okay, so obviously.

B

Let's apply the secret first.

B

Secret password, okay, let's apply the.

B

B

Right now we have two repositories available and let's apply the function.

B

Function using our case this key with password, so it should kick in yeah, we are configured, we are building and we are running when, when it's like rolling this, this function is worth to mention that those uh repositories are scoped for namespace. This is because of the security that we think this is because of the security, because it's like we need to have access to all the repository in order to to to to write the code.

B

So so in case you have a multiple namespaces that you need and you have the same repository you need to have each namespace uh this uh this object. So we have it uh running. Let's check, if it's uh accessible via a rule, what's other app, you will create something up. Yeah.

B

We have a function, uh let's, let's just reload, because it's not here yeah. Now we have two.

A

B

Those guys function, key with password great, looks good, let's start it and we should be able to actually see the hello world and I will show you, maybe the um the body of the maybe the body but the repository itself, because it's really interesting so so.

B

Private repository and as you can see, it contains more than two files. It contains also a directory which is referencing, which is a library referenced here in the handler. So actually the handler is requiring this youtube file, which is contains the function capitalize, which will change the this. This word to start with the capital letter, so I'll just quickly show you how it's uh it's implemented so that it's just executing capitalize on the given argument.

B

So basically, as you can see here, this hello message, a word message differs from the one that it's because it's processed yeah, so this uh this is. This is uh access to the photos. That was the access to a private repository via.

B

Our implementation, let's quickly, demonstrate the way how we can change the change the resource, so I will modify the.

B

Function, this key to to point the.

B

Different, so we will change it to point the different base direction. Maybe maybe maybe one more thing before before this, let's jump into the code.

B

Code and change the branch, because this is what we are willing to do so we are already on the statistic.

B

Right now, let's, uh let's check the nested directory, so, as you can see, we have a nested function, which is the same repository so right now from master branch.

B

Right now we are on this right on master, because we configured the function to point this branch. It has a library it has a couple of different files right, but it's like not having this nested folder right. This method, folder, is a lambda, func and say code for a lambda function inside of a other of the functions. So let's, let's change it from uh based here to a stat.

B

It will show this inner directory and the reference also to nested all right until you should leave everything else as it is yep, as you can see, version was changed soon kicked in, and maybe I will also check.

B

Out so previously, we we've seen it was uh showing how word, which was example of how we can extend uh our layout our project and now we change it to a nested function inside this repository and we.

B

Should see different read, which is updated right, so everything seems to be okay, let's just start this and, as you can see, the source was updated.

B

uh I think that covers all the things that I wanted to share with you guys. I would be glad if you have any questions to answer them or comments to address.

A

Cool, thank you marcin uh yeah. That was a really nice demo. I think people that are not so familiar uh with keymob probably got slightly lost in there, but I I think that is for people that know the chemo. They they understand the the power of of this uh approach.

A

um So, let's, let's start with some questions, I have a couple of them on the on paper, but let's see if anybody else, uh there was one question that um I think john had regarding the the the languages that we they will be supported. He asked particularly about python, but so you mentioned that this we will support multiple languages, correct.

B

Yes, yes, this is true that that we are also working on on adding more uh languages for lambda functions since actually right now we are, we are. uh We are developing it, so so we will have more than just a note as a language.

B

A

Cool I mean, if you guys, have questions you can unmute yourself and directly ask or write them in the chat and I'll I'll pick them up.

A

I want to. I have a question regarding the the steps I've seen that you you most of the time, took two steps like creating those. uh There was a repo resource and the function resource right.

A

So all the time, that's how it's going to be. First, you kind of bind the repo and then inside of that repo you can have one or multiple functions: correct, yeah, yeah.

B

Exactly exactly the the relation is that you function, maybe there may be maybe one than more function in one repository.

A

B

Actually, this is this is uh this is uh we can we can try to? Even if you want to to have a life checked, to have a second function that will be uh bound with the other, let's say code in the same repository.

B

So so, actually, yes, the the relationship is, uh you can have multiple functions on the opposite side, so.

A

You could have a monorepo with hundreds of functions.

B

Yeah yeah, actually, yes, but this is, uh I don't think this is a that would be efficient. I mean that we also need to consider that in which, in each time that we are checking if something change, we actually need to detect this change. So the bigger your repository is the bigger it takes to.

B

You know to check it. uh It's like it will be it's slower, so so the more granulated, your the smaller your repository, is, it's actually more performant, I would say, but but it's possible to to have it uh as you, as you mentioned, to have only monorepo with lots of functions.

A

And could be technically even different. Well doesn't sound very, very good as a pattern, but you could have different functions. um You know python and node.js technically in the same right. Yes,.

B

Yes, those the only limitation right now is that you need to refer the.

B

Maybe the the root of the project is the the thing that you are showing on the base deal. This is the route for this for this project, but you can. Let's say you have a reference to any file inside this inside this place.

A

Cool you mentioned something about, namespaces is namespace per per repo, or is it performance.

B

This is this is uh this is both for repo and perf per function, because it's like uh we designed it with a security in mind, because uh it's uh it's the convenient way to to kind of limit access to users, because because it may be that some people.

A

B

Won't have access to every repository, so you can also um granulate this access to to some to someone and without sacrificing security.

B

So this is main, let's say, motivation behind it, but see yes, this is you need to have each repo is in the scope of namespace.

A

So did I understand correct, then the namespace will be per function or per repo.

B

If you want to use the namespace, let's say if you have, if you want to use the same repository in different namespaces, you need to have this object in the namespace data you're using. So you cannot cross.

B

Let's say you reference the repository okay.

A

A

A

A

Okay, so then, then, more on the I would want to ask, and also for for youtube uh people that I will watch later. So this is a feature that we are working on right, so this will be developed and offered as a solution in parallel with the online editor that we have right now correct, so that will be there and also we will have the the option to um so there will be in parallel. It will be both options.

B

This is like, yes, exactly nothing, nothing, nothing nothing's changed to the previous implementation, and it will also support the new runtimes. So you can create those functions within your languages.

A

Perfect and then this is only about the function but not about the bindings. You should demo the bindings. You did it manually in the api.

B

Yes, yes, exactly, this functionality is only related to to say serverless, but not binding. No, exposing, no, no happy rules, no triggers so far, but yeah.

B

This is what actually this discovers.

A

Perfect, I see the opportunity in the future to to to develop maybe in that direction too, or I guess we will have to see for the moment. It's just about storing the functions in a git repo uh to have versioning and also a rollback.

B

A

B

Exactly cool, but it's only about the codes that for the function.

A

Thank you very much, martin. If there are any other questions, one of the things guys, then we move to the next topic.

A

uh The next topic in the agenda is uh actually about the the website, so um we do have- and I just want to share a preview of uh of the website with uh with you guys and show where you can get uh and provide the feedback actually, obviously being an open source project. We have an issue for this issue, 609, actually in the in the keema project uh website, where um we discuss and we propose a design. This is a little bit outdated.

A

We just have a new version right now uh to put it in perspective as we we start to addressing, and we already seen the personas uh being addressed right now in mercy uh talk. So we have two personas that we have in our in our mind. Every time we develop features for our um application, so we have the the cloud native software engineer and the tech lead each which their own pains and gains.

A

We thought of restructuring a little bit the homepage and giving it a fresh look to target those two personas and also to answer their needs or to answer the questions directly on the on the home page so follow.

A

You can follow this issue uh with, for the updates, I'm just going to quickly share a preview on what's the latest date, so this is fresh from our uh from our designers, so I mean nothing uh revolutionary, just a little bit in the in the structure of the page, where we clearly state on the top, what schema about mainly our main kind of punchline, so what we do with keema extensibility application, runtime operational of professional support.

A

We have a section here where we try to explain how it works. This is still in progress as we are looking for some sort of a diagram of high level diagram to uh be able to explain quickly at a glance um how how how does schema work and then we have two separate sections uh targeting the the developer and also here the the tech lead each which their own, um let's say, a little bit metaphorical ui.

A

This is the developer, surrounded by all the clown native uh um ecosystem and his you know he needs to hand speak um what he can use and, of course this is the tech lead uh that oversees a a huge network of of application and he will have to wire them together. So we tried a little bit of a metaphoric look and feel- and here will be the section where we try to um pitch and explain exactly for each persona. What um how do we solve their their problems?

A

We will have a section about installation, so we try to make it a bit more um clearer. Hopefully we will have a one-liner command line that allows you to run it on your local machine. So this goes in parallel with the the previous installation pocs that you've seen with k3d and k3s, and then uh yes, there are a couple of sections here missing in the bottom, like about the team and.

A

Who is using, but that was a preview uh where we are. Please follow the the two issues regarding uh the design and one regarding the development and, of course there is the slack channel where in the project, so in the in the main, stack channel, uh keema project dot io uh is where we. um We also discussed those.

A

Are there any questions regarding this.

A

Okay, well then, that's it. I think that's uh that was our meet up. Today we had a really nice presentation from martin and we are very excited to see how this rolls up into the main application.

A

Thank you guys for joining, and hopefully we see each other in two weeks uh now that vacation is over and more people are coming back so with fresh, fresh topics to share with you. If you want something to be shared, reach up to me, reach up on on the on the slack channel, and we can arrange a topic. It doesn't need to be strictly keema they, as long as it is keema related in the sense of something that is interested interesting to keema and also can be used by keema.

A

It's also a good topic for the meetup. Thank you very much and have a nice day.

B

B