keptn Developer, 7 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keptn Developer Meeting - Jan 7th, 2021

Description

January 7, 2021
We are starting a slightly new format to make meetings more efficient

Agenda
Keptn 0.8 alpha released https://github.com/keptn/keptn/releases/tag/0.8.0-alpha
We are looking for feedback on this version. Please share your feedback via Github issues or in the Keptn slack
Noteworthy issues and contributions to Keptn
Florian:
Moved build pipelines of keptn-contrib services from travis to GitHub Actions
Include ‘triggeredID’ in remediation events: https://github.com/keptn/keptn/issues/1917
Keptn CLI: Feature to upgrade shipyard files to upcoming version: https://github.com/keptn/keptn/issues/2500
Question:
Should we streamline the versioning of the Spec with the Keptn Versions?
Next meeting on January 14:
Focussing on Keptn 0.8
Niclas Mietz (solidnerd) presenting Keptn CLI via homebrew https://github.com/keptn/keptn/issues/2864

https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit

Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject

A

Hi, everyone welcome to the first captain community and developer meeting uh in 2021 happy new year, everyone uh and welcome to this um slightly condensed version of our um developer meetings. We try to compress the contents a little bit uh to make it a bit more efficient and to save some time in these meetings. We continue to keep them weekly and we continue to start at the same time.

A

So first um change uh as we want to keep track of everyone is also joining these kind of meetings. Please add your name when you're joining.

B

A

Please add your name in the meeting document, so we can also keep track of who is joining these meetings and who is also contributing and maybe giving feedback to the captain community.

A

So I just start right here with my name, and I will also share this document.

B

In the zoom chat, so if.

A

You are online, please just add your name, and so we we will see this list growing, hopefully um for the agenda. For today uh we just have a couple of uh short updates. um So, first of all, we are really excited that a captain in the alpha version for 0.8 has been uh already released.

A

um Please note that it's not a version that should be used in production already. uh It's it's uh intentionally attacked alpha. So it's a it's an alpha version where we really request- and uh we ask for your feedback. So if you want to try it out already, if you want to see all the new features and improvements bug fixes of the latest version, we provide here the link. uh It has also been already shared in our slack channel. So um please be aware that it's an alpha version.

A

It should not be used yet in production, but it has a lot of new and great features. Please give it a try and for the next meeting in one week's time we will also dig deeper into this version and share uh more insights of the new features of this version.

A

I was briefly mentioning the captain's like, but we also shared some information on this version. uh There was a hiccup uh on our shortcut to slack it's always slack.captain.sh and uh thanks to andreas who discovered this, it was not working for a couple of days since the link expired, but this is fixed now and uh should be working um again.

A

So if you're new to captain, uh you can now go to slack.captain.sh and uh you will be automatically um able to sign in uh to the to the captain's line um so with this I'm already handing over to florian. So he can share some of his uh new additions to the captain project and afterwards I will just share on what were you going to see in the next video.

C

All right, thank you. Let me just share my screen, of course, also from my side happy new year to everyone, and today I do not have a lot to show you, because it was my first day back in the office in the new year, but nevertheless I have three points. I want to briefly show you so the first one uh was quite an important one because, as you know, from the previous meetings, we ran out of credits on travis and therefore we started the migration towards github actions for our build pipelines.

C

First, we did that for the captain repository and shortly before christmas, we also did the same for all the captain contrib services, so, for example, for the diner tray service or prometheus service.

C

As you see here and now, if you have a look at a pull request, you will now see that all of the checks and necessary steps used to verify a pull request are now executed on github actions.

C

So now all the review, doc checks and the unit tests, and also, of course, the docker build and the push to docker up, will now be executed on github actions.

C

Do you have any questions about that.

C

All right, if not, let's continue with the next one, so the next one, those was a small extension to the remediation service uh yeah. Basically, uh since we now use a new event format for the upcoming version 0.8, where we link all finished events to the correlating triggered events used by using a triggered id, we also needed to adapt that logic to the events related to the remediation workflow.

C

So now all the remediation.status changed and remediation.finished events will now also contain that triggered id property that will point to the event id of the remediation.triggered event that started the complete remediation workflow.

C

Any questions about that.

D

So this is maybe a little bit unrelated, but have you defined a sequence for for the remediation flow for cadmium 0.8? So is this a sequence which only exists of remediation.

C

Currently, the the remediation workflow is a little bit decoupled from the remain from the remaining remaining shipyard file, because we, basically it uses a different logic, because the remediation workflow is defined in the remediation.yaml file and um all the other task sequences are located in the shipyard file. And basically we did that because uh otherwise, the the amount of changes that we introduced in xero, that it would have gotten too uh extensive and that's why we kept this current uh way of handling uh remediations but going forward.

C

Of course, uh we are going to evaluate how we can streamline the definition of the remediation and uh remaining fast consequences.

D

Right, but still in the ship, yet this would be a single. This would be a sequence with a single entry which is called remediation because the remediation triggered it will be sent out by the shipping controller.

C

Right, uh no, in that case, uh the way it works is when, for example, either the diner tree service or the prometheus service, who send out a problem that open event that will directly go to the remediation service and then that one will check if there is a remediation gamma available and then that one will also send the remediation.triggerdemand right.

D

Okay, thank you all right.

C

Okay and now to my third issue, this is actually a pretty neat one because, as we have pointed out a couple of times, the format of the shipyard yama files will change quite drastically when we are going to switch to captain version 0.8 and that's why we also identified that we have the need of providing upgrade functionality.

C

That is easy to use within the captain cli. In order to upgrade previous projects that have been created with captain version smaller than 0.8 to the upcoming latest version and the way that will work is, you can then be able to say, captain upgrade project, then the name of the project.

C

Then you can specify that you want to upgrade the shipyard file. You can specify a from version and the two version, and what that command will do. It will fetch the current shipyard file from the configuration service or from the git repository for that project, and it will inspect it, try to parse it and check. If everything is uh okay with that and then based on the information within that shipyard file, it will generate a new shipyard fire that will be compatible with captain zero, eight and yeah.

C

Basically, you will also get a lock output that will show you the current version of the shipyard file and then what will come out of it.

C

So basically, here we have this this old format and then the new one, with all the stages that were defined in the previous shipyard and then it will also contain a list of sequences that will enable you to use all the previous use cases, for example, for the artifact delivery or the evaluation.

C

And then you will, if that looks okay to you, you will have the option to confirm the automatic upgrade and then the cli will upload that new generated shipyard to the to your project and from there on you will be able to also use that project with capital 0.8.

C

B

C

Considered the use case of having of using that command within automations, so by providing the minus y flag, you can skip that uh that approval step and the shipyard file will be updated automatically, and I think that's not here in the issue. But if you look at the pro request, you will see that I've also up I've, also added a dry run flag that will uh basically prevent the the generated shipyard from being uploaded automatically.

C

So if you just want to check how your new shipyard file is going to look, you can pass that flag to the command and then nothing will be updated, but you can still check if everything is okay and if you then feel confident that uh this is the shipyard you want to use going forwards, then you can again execute the upgrade command without that flag and then we'll update the device accordingly.

C

All right are there any questions about that feature.

A

um I think it's a.

C

It's really helpful.

A

I have one question, um so: can we see the command again that you will execute and will it look for a local shipyard file or it will use the shipping file? That is part already off the uh of this um project? It will download it.

C

A

And upload it yep.

C

It's a good question, so the latter is the case, so that command will use the captain ap api to fetch the actual shipyard that is stored in the git repository for that project and we'll use that to generate.

A

A new one, okay, so there is no need to have the to make sure that the shipyard is actually the the correct one that is downloaded, and my second question is, I guess it's intentionally, but we um declare it here that we want to move from version 0.1 to version 0.2 instead of using the captain versions here. Something like 7.3 to 0.7.3 to auto 8..

A

um Is this because we have.

C

A different version and scheme.

A

C

um Yeah yeah for the shipyard files. We do have different versions, because basically, all the captain versions up until uh 0.8 used the same shipyard version which we now decided to be 0.1 and the next version that will be compatible with captain 0.8 will be called 0.2.

C

A

D

And but one minor note here- and this boils down to the to the same question- whether we should um use the same versioning number for the captain's back as we do have for captain itself. So captain spec will be version 0.2 and captain itself has version 0.8 and we we asked ourselves when we should streamline this.

A

Yeah, I I can totally understand because it's we do have a lot of different versions. We have the captain version, then we, when we release an erp of the bridge, we have a different bridge version and the character we have the captain installation. We have the captain cli. We have the captain specification, we have the contributions and the sandbox services and all of them can follow their own versioning scheme, which is in general, uh which is by design okay.

A

But uh for all for everything that goes into captain core, it might be a little bit confusing. um So we have also others here joining the call. If you have any ideas, if you experience and conversion schemes um from specification and implementation, just please let us know. I.

B

A

B

All the microphones here so.

A

I'll just speak up: if you have any ideas, any suggestions.

A

Do you have a suggestion, andreas how to approach this.

D

Yeah, we can simply decide to move the new spec version to 0.8, so this is not a.

D

Problem because um it's not ga out yet so we can do this.

A

I edit this in, like question item to our meeting notes that should be followed.

A

A

Okay and one last question: does it in any way check on the cluster version of captain? So if uh there is or how do we think about the transition from captain 7.3 or 0.7 to 0.8?

A

Do we first have to change the shipyard file and then do a an upgrade or do we first do a captain upgrade and then do the upgrade of the shipyard file? uh Is there any sequence that has to be followed if we want to upgrade an already running captain installation?

A

That's a good question.

C

um I think the better approach would be to first update the captain cluster version and the cfi previously of course, and then once that has been done, apply the upgrade command.

A

Maybe this is something that we that this comment should also check if the cluster version is already.8, because if not, then the shipping file would not work anymore and obviously this should go hand in hand, but maybe it's something that we can add as a hint to the user. Please first upgrade the captain cluster version and then upgrade the shifter file.

C

Yeah, we actually already have uh more generic version of that functionality, so, in the upcoming version the cli will always check if its own version matches with the version of the captain cluster and then display a warning message. If that is not the case, so we do have that functionality in place.

D

But still to be fair and so or honest, um the upgrade process or the upgrade steps we need to work on those and we need to define those. So it's not implemented yet and yeah. We will define a list of steps which your user has to take to get from 0.7 to 0.8.

C

Exactly so, this upgrade command is only one piece of the puzzle.

C

All right, if there are no further questions, I think I've discussed all my issues for that week, and that means I will hand over to hearing again.

C

A

um So I'm sharing again, hopefully the right screen.

A

um Okay, so I just uh made a note about this question that uh we should um later discuss it, also in the next meeting or um async on on slack, so that we come up with a solution.

A

um We also have new um members of the captain community joining um so it's uh pratik. Hopefully I pronounced.

B

The name correctly nice to have you also joining.

A

uh In our captain developer meetings, uh if you have any questions or if you want to do a quick introduction, um please feel free to unmute the mic and uh just um yeah say hello to the captain community.

B

Okay, thank you so much hi everyone I am.

B

I have been in the captain slack channel for some time like I joined in december, but this is the first time I'm getting joining your meet and I'm just getting started. I have seen the repo and honestly I don't have much of an experience, but I'm looking forward to contribute and yeah I'll just try and get used to what you people do over here. It'll be late.

A

Cool yeah thanks for joining uh and if you have any questions uh on uh using captain or um starting contributing to captain, just let us know also during the week uh outside of these meetings in the captain's lag, and we are happy to help and uh also next week. um So I'm already moving to the next part of our agenda to the last part. For today, um for next week uh we will have. um I assume we will be in a bit larger group here, because we need to focus a little bit more.

A

On captain sierra note, 8 on the alpha release, sharing insights, how to move external services, move contribution, services and services from the sandbox um to the latest.

B

A

Captain uh and also we have um niklas from the captain community presenting a new addition to captain, which is pretty cool. So, if you're running on mac os, then you can also install the captain cli via homebrew. So I think it only works on mac os, I'm not sure if it only works on linux, but it's a very convenient way to download and install um the captain. Cli- and uh actually I was just talking to him today and hopefully next week he will be available and present this in this week.

A

So basically, this will be our next two um bigger items for the next meeting and uh obviously also uh what is what has been done during the week during the next week. um Are there any questions or comments on pratik? I just go ahead and also mention your name as you have been joining this meeting today.

B

Yeah I'll just get used to and I'll ask you helping you in this slack. Whenever I come across any questions and all right.

A

Cool yeah and thanks everyone uh for for joining uh this week's meeting. um Please also uh note that uh we still have our planning board uh on github. So, if you want to contribute, we have a lot of good first issues that are tagged on our github repository just go to github.com, and you can also find good first issues if you want to start contributing there.

A

So thanks a lot for today have a great rest of the day and rest of the week and see you all next week.

C