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 2022.02.14 #2283

Closed
harshad16 opened this issue Jan 26, 2022 · 7 comments
Closed

sprint production release 2022.02.14 #2283

harshad16 opened this issue Jan 26, 2022 · 7 comments
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. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. 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.02.14
/priority important-soon

@harshad16 harshad16 added sig/devops lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jan 26, 2022
@sesheta sesheta added this to the 2022.02.14 milestone Jan 26, 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 Jan 26, 2022
@fridex
Copy link
Contributor

fridex commented Feb 3, 2022

Optimized syncs across deployments in document-sync-job

Our last release introduced a new component called document-sync-job which can sync documents created in one Thoth deployment to another. This release comes with an optimized implementation of document-sync-job which can sync documents concurrently. This optimization was required as the number of documents we need to handle is too large.

@fridex
Copy link
Contributor

fridex commented Feb 3, 2022

Pedantic thamos run feature

Our command line interface, Thamos, now performs pedantic application runs. As thamos run acts as a wrapper for Python interpreter for spawning Python applications (thamos manages virtual environments automatically for users if configured so), it can now also check that the configuration supplied by the user matches the configuration of the runtime environment used. An example can be a requirement on CUDA, eventually in a specific version. If CUDA in the specified version is not present in the runtime environment, thamos run refuses to run the application (by default). This way users can ensure that the requirements on the runtime environment they use match expectations recorded in the Thoth's configuration file. Moreover, thamos run newly also checks that the lockfile respects direct dependencies (no re-locking is needed).

These checks can be suppressed by using --no-pedantic option or by providing THAMOS_RUN_NO_PEDANTIC=1 environment variable to the runtime environment.

@sesheta sesheta added sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. and removed sig/devops labels Feb 4, 2022
@fridex
Copy link
Contributor

fridex commented Feb 4, 2022

thamos run allows specifying environment variables to the Python process run

Starting this release, users can declare their environment variables in .env files configured per overlay. This configuration follows Pipenv's .env file configuration, except Thoth users can declare different environment variables to be supplied to the process based on overlay/runtime environment used.

@pacospace
Copy link
Contributor

Pulp Grafana Dashboard

A new Grafana Dashboard for Pulp deployed on Operate First is avalable at Grafana Operate First: https://grafana.operate-first.cloud/d/B7DLT7anz/pulp-metrics?orgId=1

@pacospace
Copy link
Contributor

pacospace commented Feb 9, 2022

graph-backup-job
New metrics were added to monitor the creation of pg dumps and if any issue appears creating pg dumps.

@pacospace
Copy link
Contributor

graph-metrics-exporter
Introduce a new task for monitoring pg_dumps on Ceph. In this way we can verify if all backups are created correctly.

@harshad16
Copy link
Member Author

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

Features

Optimized syncs across deployments in document-sync-job

Our last release introduced a new component called document-sync-job which can sync documents created in one Thoth deployment to another. This release comes with an optimized implementation of document-sync-job which can sync documents concurrently. This optimization was required as the number of documents we need to handle is too large.

Pedantic thamos run feature

Our command-line interface, Thamos, now performs pedantic application runs. As thamos run acts as a wrapper for Python interpreter for spawning Python applications (thamos manages virtual environments automatically for users if configured so), it can now also check that the configuration supplied by the user matches the configuration of the runtime environment used. An example can be a requirement on CUDA, eventually in a specific version. If CUDA in the specified version is not present in the runtime environment, thamos run refuses to run the application (by default). This way users can ensure that the requirements on the runtime environment they use match expectations recorded in Thoth's configuration file. Moreover, thamos run newly also checks that the lockfile respects direct dependencies (no re-locking is needed).

These checks can be suppressed by using --no-pedantic option or by providing THAMOS_RUN_NO_PEDANTIC=1 environment variable to the runtime environment.

thamos run allows specifying environment variables to the Python process run

Starting this release, users can declare their environment variables in .env files configured per overlay. This configuration follows Pipenv's .env file configuration, except Thoth users can declare different environment variables to be supplied to the process based on overlay/runtime environment used.

Pulp Grafana Dashboard

A new Grafana Dashboard for Pulp deployed on Operate First is available at Grafana Operate First: https://grafana.operate-first.cloud/d/B7DLT7anz/pulp-metrics?orgId=1

graph-backup-job
New metrics were added to monitor the creation of pg dumps and if any issue appears creating pg dumps.

graph-metrics-exporter
Introduce a new task for monitoring pg_dumps on Ceph. In this way, we can verify if all backups are created correctly.

Component Updates

Thanks for the amazing work everyone. 💯

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. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. 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