Page Comparison

Attendees

Agenda

Bintray Consumption
Image Removed

failed due to rate-limitation on bintray in the publish stage. @peterpan has reduced the space occupation and applied for reactivation of our account there. https://rackhd.atlassian.net/browse/RAC-5727 and https://rackhd.atlassian.net/browse/RAC-5728 are created for further enhancement on our CI/CD.
AI: Former user (Deleted) Send out more detail to the group on what is consuming space on bintray so we can further discuss a clean-up plan going forward. Will discuss again at next CC.
To overcome the space limitation:
1. What we will put in Bintray ? to understand/forecast our usage.
2. For RackHD, ~200MB for all the debian package for a release (as below table #1 ), and static files there as well without version control (~160MB)
3. @Michael, how many space will you consume for SMI-services , every sprint ?
1. AI: Let’s make decision : How many “Sprint Release” / “Theme Release” (Do we still have it ?) / “Nightly Build” to be kept in Bintray ? Total is 10GB space for OSS free plan.
How about 24 Sprint Release(6 months) + 1 weeks of nightly build ( at most 7 ) ?
1. Moving to glory Katalist, do we think some newer use case of Bintray ?
1. If we found the current plan is not enough. We have to consider upgrade to paid plan.
Image Removed
1. 1. Michael Hepfer MicroServices SMI is using total of 475 MB. This is not per sprint build, it is a replacement of JAR files for each build.
  2. How many sprint/nightly releases do we want to keep. Suggestion is 6 months or 24 sprints. and 2 weeks of nightly builds on bintray. AI Former user (Deleted) to communicate this plan on RackHD Channel. AI Tim Larson to check with leadership if we will have Themed Releases going forward.
  3. Job to cleanup bintray is a regular scheduled run Former user (Deleted) Where is documentation for cleaning schedule?
From QRB meeting notes
1. Agreement at OLT that we will be going fully wsman-based and eliminate racadm from workflow support. AI: Amy Mullins Draft up a proposal on how to move forward with this including testing plan. Looking into how to introduce an idrac simulator. Currently all hw-based testing.
Plugfest demo
1. Amy will ask if we can get a demo for the team
2. Veyron working on getting code polished-up and into master (currently on a fork) - Update Corsair will take point on this code.
Release Notes
1. AI Former user (Deleted) send out email to remind folks that when closing story to make sure the affects community is set appropriately. AI Anchor per team to verify work done by the team that week has affects community set correctly.

Versions Compared

Old Version 2

New Version 3

Key