Goal

Reduce overall release payload byte count by analyizing all images for sources of duplication and eliminating them.

Benefit Hypothesis:

Today the release payload is upwards of 23GiB, in addition to other initiatives linked from the parent we should strive to reduce that through optimizing our layering to eliminate sources of duplication and churn.

Resources

Known sources of duplication / churn

• RPMs that are installed into multiple images but not in a common base image – Those should move up to the base image so that they're not duplicated in images whenever doing so doesn't create a scenario where an AWS specific package with a CVE bleeds over into another platform specific image
• By driving RPM transactions lower we will reduce the churn on files that are decently large and updated everytime the set of RPMs in an image changes, look at this after the first bullet point is fixed by determining the checksum of contents in /var/lib/rpmdb and examining any that are unique

Responsibilities

Indicate which roles and/or teams will be responsible for contributing to the initiative and generally what they might be expected to do.

Success Criteria

Provide some examples of how we will know if we have achieved the goal. What can be measured to determine success? What observable actions/outcomes that can be seen to determine success? Specific, Measurable, Achievable, fits within the Time-box.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.