Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sprint production release v2022.03.14 #2393

Closed
harshad16 opened this issue Feb 28, 2022 · 4 comments
Closed

sprint production release v2022.03.14 #2393

harshad16 opened this issue Feb 28, 2022 · 4 comments
Assignees
Labels
area/release-eng Issues or PRs related to Release Engineering kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@harshad16
Copy link
Member

Hello, Thoth-station!

This Issue would be used for the current sprint cycle production release.
By the end of the sprint cycle, we will consolidate the information of thoth-station components features upgrade and fixes in this issue.

/kind documentation
/area release-eng
/triage accepted
/milestone 2022.03.14
/priority important-soon

@harshad16 harshad16 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Feb 28, 2022
@sesheta sesheta added this to the 2022.03.14 milestone Feb 28, 2022
@sesheta sesheta added kind/documentation Categorizes issue or PR as related to documentation. area/release-eng Issues or PRs related to Release Engineering triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 28, 2022
@fridex
Copy link
Contributor

fridex commented Feb 28, 2022

Notify users when they use PyTorch index

Newly, the resolver notifies users if they consume releases from the PyTorch index.

@fridex
Copy link
Contributor

fridex commented Feb 28, 2022

Memory optimizer in adviser

If Thoth's adviser consumes too much memory and is killed on OOM in a deployment, a memory optimizer can be turned on. The memory optimizer removes data from some of the internal data structures to optimize memory consumption. This can slow down finding a resolved set of dependencies or making the search not that optimal. Users, however, can get results instead of OOM.

@harshad16
Copy link
Member Author

harshad16 commented Mar 14, 2022

we have completed the release for v2022.03.14 🎉 🎊 🥳

Features

Notify users when they use PyTorch index

Newly, the resolver notifies users if they consume releases from the PyTorch index.

Memory optimizer in adviser

If Thoth's adviser consumes too much memory and is killed on OOM in a deployment, a memory optimizer can be turned on. The memory optimizer removes data from some of the internal data structures to optimize memory consumption. This can slow down finding a resolved set of dependencies or making the search not that optimal. Users, however, can get results instead of OOM.

Created new handler that uses image analysis results and generate new prescriptions

Automatically propagated from the container image analyses - the container image analysis would provide how Pipfile looked like on image build and that information will be part of the image analyses information derived by package-extract (similarly as we propagate information about RPM packages). In this case, we implemented a handler in prescriptions-refresh-job that:

  • checks what ps images are hosted on quay
  • ask what is the container image analysis result and how the Pipfile looked like during the build
  • automatically create prescriptions based on direct dependencies in Pipfile

References:

Automatically bump base image versions to latest available on Quay

A new script integrated in the aicoe-ci pipeline allows to automatically update the base image versions present in configuration files such as .aicoe-ci.yaml to the latest available on Quay. The pipeline is triggered by an action on a repository such as the opening of a pull request or an issue. If the base image versions are not up-to-date compared on available versions on Quay, a pull request is automatically opened for the corresponding update.
For an example, see: thoth-station/package-releases-job#637 which was triggered by thoth-station/package-releases-job#636 on the package-releases-job repository.

Fix method to iterate on thoth files

slo-reporter was not able to provide an analysis of adviser results. advise-reporter logic was not able to read adviser files, due to a method in thoth-storages. Iterating over files in a bucket gives empty lists even if files exist because the prefix used to identify them is using a default value that is not updated. The value RESULT_TYPE is fixed.

Component Updates

Thanks for the amazing work everyone. 💯

@mayaCostantini
Copy link
Contributor

mayaCostantini commented Mar 15, 2022

Automatically bump base image versions to latest available on Quay

A new script integrated in the aicoe-ci pipeline allows to automatically update the base image versions present in configuration files such as .aicoe-ci.yaml to the latest available on Quay. The pipeline is triggered by an action on a repository such as the opening of a pull request or an issue. If the base image versions are not up-to-date compared on available versions on Quay, a pull request is automatically opened for the corresponding update.
For an example, see: thoth-station/package-releases-job#637 which was triggered by thoth-station/package-releases-job#636 on the package-releases-job repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to Release Engineering kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
No open projects
Status: 💯 Releases
Development

No branches or pull requests

4 participants