Hi Kenny,
This reads that there should be an update, is that the case?
BR,
Steve
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Kenny Paul
Sent: Saturday, May 05, 2018 12:53 AM
To: Christopher Donley (Chris) ; onap-tsc
Subject: Re: [onap-tsc] TSC
Gildas,
Just an fyi for the TSC – there are several issues here (3)
Docker sync between the 2 ONAP versions needs to be enforced – until we have
the manifest completely automated with heat and OOM extracts.
We are sensitive to the state on nexus3 deleting/retaining old images in
order to f
Hi Chris, all,
I see your point. I think we can have it covered by providing a different
options in the survey, one including overall restriction including PTLs, the
other one restricting it to cross-project initiatives only, as you suggest, the
third one to not have any restriction at all.
BT
If we do proceed with this motion, I think we should separate out PTLs from the
other positions. PTLs are responsible for managing a single project, whereas
the other positions are responsible for cross-project leadership. In some
cases, it makes sense that one of the project leaders also lead
Hi all,
Thanks to all meeting's attendants!
Here is my short summary:
1. Beijing functional requirements status review
a. PNF support was presented. It will not be showcased in Beijing and the
development will continue in Casablanca
b. Manual scaling out status was presented
Hi all,
Also, additional point I’ve been thinking of.
Last year we had some proposals on the table to limit number of positions (e.g.
chairs, vice-chairs, PTLs etc.) to 1 per single person.
It never came to voting, as it was too controversial back then.
Perhaps, we have a more mature community no
