Dear TSC (or proxy),
As you know the Footprint optimization including Container optimization, Component/memory optimization, Global optimization (e.g. shared DB) is a non-functional requirement that we have marked as “Dublin Release – TSC Must Have”.
The Footprint optimization is currently under M1 Conditional because the Dublin Testing Strategy is not yet clarified.
Our aim goal is to reduce the size of our containers.
In order to get the benefits from the Footprint Optimization work, the Integration Team should certify any optimization improvement (if any) that will be available at RC0 (or earlier).
We do not anticipate any additional Jenkins job – the expectations is that the PTL will improve the current build of the container including any optimization improvement i.e. size/memory etc.
I hope this e-mail clarifies the way how to move forward with our ONAP Dev. Project Teams and our ONAP Integration Team.
NOTE: This email (or its attachments) contains information belonging to the sender, which may be confidential. proprietary and/or legally privileged. The information is intended only for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient, you are hereby notified that any disclosure, distribution or taking of any action in reliance on the content of this is strictly forbidden. If you have received this e-mail in error please immediately notify the sender identified above