Dear ONAP Community:
We have not yet received any ONAP-focused demos for the LFN Booth at ONS.
Last year, the multiple ONAP demos were some of the popular and
well-trafficked in the booth. If you have an idea for an ONAP demo, please
send an email with the requisite info detailed below or let us
Dear TSC,
Integration team has voted to promote Brian Freeman (5/5 votes) and Mariusz
Wagner(4/5 votes) to Integration committers. Please see their promotion
requests here:
https://wiki.onap.org/display/DW/Integration+Committer+Promotion+Requests+for+Brian+Freemam
Dear ONAP team,
I would like to announce that we are working on a migration for docker
images from Nexus3 to DockerHub.
The main motivation to do so is to allow teams to move towards a model that
will easily allow them to manage their own docker image releases more
independently.
We have several
On Mon, Feb 11, 2019, 11:04 Brian I dont think Disk space is really the main issue – its size of the image
> to download and boot and the memory consumption in the running image.
>
Well, again, if there's a single base then you are only downloading the
delta.
> We arent running into issues with
Thanks Manoop,
I will add an item to our agenda to make the team aware of this.
Adolfo
On Mon, Feb 11, 2019, 12:11 Manoop Talasila
wrote:
> Hello ONAP CIA,
>
>
>
> The “docker-slim” method seems to be another optimization mechanism which
> supposedly reduces image size with no changes on
Dear TSC (or proxy),
Please read "the Integration Team should certify any optimization improvement
(if any) that will be available at RC0 (or earlier)" as
"The Integration Team will use any of these containers that include these
optimization improvements (if any) and that are available at RC0
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
Looks like I have arrived late to the party, but still want to add my 2 cents.
I agree with Tal 100% . If the assumption is that, the docker images available
in ONAP nexus repo will be directly used in production, that that’s a total
invalid assumption. As Tal pointed out, the choice of
I dont think Disk space is really the main issue – its size of the image to
download and boot and the memory consumption in the running image.
We arent running into issues with disk space in our environment but rather in
memory consumption and to some extent the container init delays.
Brian
This conversation has gotten a little bit confusing. Let me try to organize
and separate the core issues:
1. Disk space. If we want to reduce the ridiculous storage requirements
for ONAP's container images, the solution is not to choose a tiny Linux
distribution. Rather, the solution is
Hello Sylvain,
I appreciate your detailed reply..
I am not sure if you were on the call when this topic was discussed. My point
was not whether I favor one Linux distribution over other Linux distributions,.
It was related to whether a specific distribution is commercially supported. As
I
11 matches
Mail list logo
