-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add an endpoint that provides an at-a-glance view on installed product freshness #62
Comments
What is a product? A tile, stemcell or buildpack. |
I think that is valuable for all 3. |
* Begins to address issue #62 * Support for installed tiles only
Let's not forget buildpacks, 7f3a2b5 |
Going to leave this open for remarks. I still think stemcells is an interesting case, but maybe not that high-value? |
I can attest the value of having stemcell-related statistics. When internal teams advocate for/have to continually prove the value of CF, they're asked to provide some kind of quantifiable data on "number of operating system patches taken" and speed to which those patches were applied. This data is extremely helpful when CF is squaring up against "traditional" deployment operations (code plopped directly onto VMs which are sometimes patched?). This is the kind of data that's helpful for platform operators when justifying (P)CF to their boss' boss' boss and/or to be used in slide decks. It's actually very helpful. And often the next question is "okay but how many VMs did you repave?" These might seem like silly questions once the corporate culture has higher standards and familiarity with BOSH/upgrades/etc., but until that point, having data which demonstrates number of stemcells ("os patches") and other similar data is so incredibly helpful when establishing a cultural foothold... Plus it's cool to track and to challenge yourself && other platform engineering teams into who can safely take stemcells / repave the fastest. |
Stemcell release metrics now reporting as of f2a8d05. |
Cf-butler already provides endpoints for capturing product and release data from both the Pivotal Network and an Operations Manager. Why not combine this data into a useable report for operators?
Something like
from Operations Manager
from Pivotal Network
For each product calculate the # of days between the installed version and the latest available version.
This would provide operations teams an at-a-glance view of how fresh each installed product is. It might help drive a service level objective on product freshness. E.g., the platform team will ensure through automation or other means that installed product versions available on each managed foundation is only ever N-2 versions behind.
The text was updated successfully, but these errors were encountered: