You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "Startrekzky (via GitHub)" <gi...@apache.org> on 2024/04/30 02:43:46 UTC
[I] [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version [incubator-devlake]
Startrekzky opened a new issue, #7415:
URL: https://github.com/apache/incubator-devlake/issues/7415
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement.
### Use case
This is a use case contributed by a DevLake user:
They release a new "cluster chart" at regular intervals, but enterprise customers, each with unique change requirements and schedules, may not upgrade immediately.
As shown in the diagram, they serve multiple customers. Each customer may have one or more management clusters, primarily for georeplication. Each management cluster oversees multiple workload clusters (corresponding to different development stages like dev, staging, prod).
This DevLake user's primary concern is to minimize the number of distinct cluster chart versions in circulation to reduce maintenance costs. They track the time from a new cluster chart release to its deployment across most workload clusters. Additionally, they need to segment deployment data by customer, management cluster name, type (WAS, Azure, VMware, bare metal), and workload cluster name.
To measure the percentage of workload clusters on a specific release version, we need to know how many workload clusters are there in total. We can approximate this number using the total number of workload clusters we have seen in the past.
### Description
_No response_
### Related issues
#6959
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #7415:
URL: https://github.com/apache/incubator-devlake/issues/7415#issuecomment-2322628558
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #7415: [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version
URL: https://github.com/apache/incubator-devlake/issues/7415
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version [incubator-devlake]
Posted by "d4x1 (via GitHub)" <gi...@apache.org>.
d4x1 commented on issue #7415:
URL: https://github.com/apache/incubator-devlake/issues/7415#issuecomment-2085151205
To accomplish this feature. I think these things must be done:
1. Fetch upcoming and historical `releases` automatically. For example, if users are using GitHub to manage releases, then we can fetch release via GitHub's API (https://docs.github.com/en/graphql/reference/objects#release).
Optional: Add a new webhook which can be used to post releases by users.
2. add a new table called `cicd_deployment_attributes`, use it to store the deployments additional attributes. It has three columns `deployment_id` `attribute_name` and `attribute_value` at least.
With these changes, we can calculate deployments's metrics group by custom attributes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature][Version Management] Track the distinct versions across customers and the lead time for the customers to upgrade to the latest version [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #7415:
URL: https://github.com/apache/incubator-devlake/issues/7415#issuecomment-2336492342
This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org