Goal:

• Track partner actions needed when we deliver a new Manila Flamingo version in a FR release in RHOSO-18

Acceptance Criteria:

• Defined set of actions needed for Manila Partners and either completion of those tasks or a link EPM Jiras as needed
• Netapp would be MVP to recertify, but ideally all Manila partners

Open questions:

• Should partners be required to re-certify?  This is a new case for a major release and we normally do not change OSP versions within a major release AND we do not partner certification is good for the life of a RHOSO/OSP release
• What communications do we need for partners?  We at least need to be sure any custom containers get updated and tested 
•