Hi all,
I think that is a good idea. Deployment resource consumption was an
issue for my company as well.
Do you think it would make sense to support 2 types of deployments in
each ONAP project:
1. full (normal) deployment,
2. barebones deployment.
The point of the "barebone" deployment would be to deploy only the
essential services necessary for proper functioning of that particular
service. For example:
- leaving out redundant services (necessary for H/A)
- leaving out web services that have not yet been integrated (I have
seen web services which are run in the deployment yet they don't do
anything for the last 2 releases and more are coming!)
- leaving out web services that are not part of any external use-case or
scenario (e.g. WS + UI for management of the internal project stuff, PoC ..)
I am not sure how much we would save in terms of memory and deployment
time as there are no numbers or statistics, but I suspect that at least
a discussion would be worthwhile.
Br,
Pavel
On 10/23/18 8:39 PM, Adolfo Perez-Duran wrote:
Alla, Gildas, Jason
Could you advise on the process we should follow to introduce this
non-functional requirement to the Dublin release?
*Requirement: Use ONAP Normative Base Images to Improve deployability
and reduce footprint and resource consumption*
*Rationale:*
Both operators looking to experiment with ONAP and developers
producing ONAP containers report long build times and high resource
consumption. The OOM team also reports long deployment times and high
resource consumption.
Furthermore, small, efficient images also address the issue some
operators have reported when they have attempted to deploy ONAP to
"kick the tires."
*Proposed solution and benefits:*
ONAP's CIA project has identified a set of container base images that,
if adopted, would alleviate the problems of resource consumption and
long build times ONAP projects are experiencing.
Experiments conducted with the proposed base images have produced
container images that were up to two orders of magnitude smaller.
Smaller images translate into smaller build and deploy times as well
as smaller footprint.
*Community support:*
The idea of using these normative base images was presented to the PTL
community on October 8th, 2018. There is consensus and support for
the adoption of these base images and for the introduction of a
non-functional requirement for Dublin.
It was suggested that also cover the requirement under S3P, Jason Hunt
has been made aware of the requirement.
*Timeline:*
We propose that the requirement be met by M3.
Thanks,
Adolfo
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13241): https://lists.onap.org/g/onap-discuss/message/13241
Mute This Topic: https://lists.onap.org/mt/27571472/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
