Versioning functions and images

[mcopik]

Our Docker images should have version prefix attached to mark the current release.

Furthermore, all functions deployed to the cloud should use the deployment prefix to separate resources.

[ojninja16]

Hi @mcopik I would like to work on this ...Is this still open? and if any resources might help me get started with this repo let me know

[mcopik]

@ojninja16 The issue is free to take! We already have resource_id defined in each platform; we just need to use them when deploying functions.

Furthermore, we should define a global suffix storing SeBS version inside config/systems.json. At runtime, it should be stored in the main sebs config, exported with each result, and appended to Docker image names.

[ojninja16]

Hi @mcopik, I am working on the changes. I had a small query: How can I validate if my changes worked as per the requirement? How can I do the testing? If you could point me to documentation to do the same, it would be very helpful.

[mcopik]

For this feature there's no explicit test. You can invoke functions, and after your change, the function in the cloud should have the name that now includes the resource ID as a suffix :)

You can use the regular invocation from our tutorial.
https://github.com/spcl/serverless-benchmarks/blob/master/docs/usage.md

[ojninja16]

Oh right! 😅

You can use the regular invocation from our tutorial.
https://github.com/spcl/serverless-benchmarks/blob/master/docs/usage.md

🙏

[ojninja16]

Hi @mcopik,

I have been reviewing the codebase and, based on the requirements, I have made the following updates:
SeBS Version Handling:

• I added a global suffix storing the SeBS version inside config/systems.json.
• This suffix is now used to append the sebs_version to system_config.benchmark_image_name as well as in build_docker_images.py.

Resource ID in Function Names:

• After thorough investigation, I found that default_function_name is used across all platforms to generate function names.
• Since resource_id is already centralized within the Resources class, we can access it consistently across all platforms.
• To incorporate resource_id into function names, I believe I need to modify the default_function_name method in each platform.

Could you confirm if this approach aligns with the intended requirements?

Please let me know if I have misunderstood anything or if there's a better way to implement this. Your guidance would be greatly appreciated.

[mcopik]

@ojninja16 The implementation sounds about right :) Can you please open PR? Then I will be able to review it and validate.

[ojninja16]

Got it!Yeah, sure on it .....👍

[ojninja16]

hi @mcopik pushed up a PR for review: #232

[mcopik]

Solved with #232