Re: [onap-tsc] TSC Composition Proposal

[Phil Robb]

Hello ONAP TSC Members:

Regarding the timing of this vote, we will postpone this topic until next
Thursday, the 26th of April.  This Thursday is a national holiday in Israel
and as such impedes on some of our community's ability to participate in
the discussion and vote.

Best regards,

Phil.

On Tue, Apr 17, 2018 at 5:24 PM, Phil Robb 
wrote:

> Hello ONAP TSC Members:
>
> There has not been much discussion on this thread, so I assume that all
> relevant questions and comments have already been expressed regarding this
> topic of how best to populate the TSC and when to do it.  To that end, I
> will be calling for a vote on this topic during the TSC meeting on
> Thursday, April 19th, 2018.  Please review the material below and provide
> comments or questions if you have any.  Also, please be prepared to vote on
> this topic, or have a delegate ready to vote in your stead on Thursday.
> The format of the vote will be similar to the following:
>
> First, we will vote on if we want to change the way we populate the TSC
> after Beijing or after Casablanca.  Remember that in order to change the
> date to after Casablanca (Nov. 2018), we will need a 2/3 super majority to
> modify the Charter with the new date.  So the first vote will be:
>
> Shall the TSC modify the ONAP Charter to change the date in which the
> "Startup Period" ends (as defined in Section 2.b.i) to be November 16th,
> 2018? -1, 0, +1
>
> If this vote passes, we are done for now.  If it does not pass with a 2/3
> approval, we will populate a new TSC shortly after Beijing is released.  To
> do so, we will vote on the following proposals:
>
> Proposal #0
> Abstain from voting on population method.
>
> Proposal #1:
> The TSC Accepts the "TSC Composition Proposal" presented by Chris Donley
> and Stephen Terrill during the TSC Meeting held on April 5th 2018.  The
> proposal in it's entirety is located here: https://wiki.onap.org/
> download/attachments/25439857/TSC%20Composition%20proposal%
> 20v2.pdf?version=1=1522934062000=v2
>
> Proposal #2:
> The TSC Accepts the "TSC Composition Proposal" presented by Chris Donley
> and Stephen Terrill during the TSC Meeting held on April 5th 2018 with the
> following amendment:
> ​That i​
> n addition to
> ​ the​
> 15 elected TSC members
> ​ in the original proposal​
> , each end-user Platinum Member of LFN that ha
> ​s​
> been a part of ONAP and/or LFN for less than 12 months from the time of
> the election,
> ​is​
> allowed to appoint a representative to the TSC.
>
> ​Proposal #3:
> The TSC Accepts the "TSC Composition Proposal" presented by Chris Donley
> and Stephen Terrill during the TSC Meeting held on April 5th 2018 with the
> following amendment:
> ​That in addition to the 15 elected TSC members in the original proposal,
> ​each end-user Platinum Member of LFN who does not otherwise have a
> representative (elected) on the TSC, is allowed to appoint a representative
> to the TSC.
>
> Shall the TSC approve one of the above proposed methods of populating the
> TSC? 0, 1, 2, 3
>
> Please let me know if this sounds reasonable or if there is another way
> you would like to vote on these options or others for this topic.
>
> Thanks,
>
> Phil.
>
> On Wed, Apr 11, 2018 at 4:59 PM, Phil Robb 
> wrote:
>
>> Hello ONAP TSC:
>>
>> I would like to keep the discussion moving regarding how and when we
>> might choose to change the method of populating the TSC.
>>
>> From the discussions thus far, I do not believe I heard much pushback on
>> the population method suggested by Chris D. and Stephen T. at last week's
>> TSC meeting.  In general, it called for a TSC where anyone can
>> self-nominate to run for a TSC seat, and those that are allowed to vote
>> must have demonstrated some form of previous participation in the project
>> including code contributions, wiki contributions, subcommittee
>> participation/leadership, etc.
>>
>> If we were to do something like that, the one significant concern is end
>> user representation, in particular since several of our end users have just
>> joined the project recently and are ramping up their plans, and developer
>> capabilities to directly participate in the project.  Mazin has called for
>> 50% end-user participation in the TSC, others have just expressed the
>> general concern that the end users should still be represented "well" in
>> the new structure.
>>
>> We have also heard from several of the TSC members that now is not the
>> right time to change the makeup of the TSC and we should leave it the same
>> at least until Casablanca (Nov. 2018).  A vote was held on this with a
>> significant number of voters indicating that they would like the TSC to
>> remain the same until Casablanca.  The vote did not pass however because
>> such a change (which affects the ONAP Charter) must pass with a
>> super-majority of 2/3s of the votes.
>>
>> We have agreed to vote on this postponement again to see if it will pass
>> the 

Re: [onap-tsc] [Onap-lf-announce] Jenkins and Nexus downtime

[Alla Goldner]

+1


 Original Message 
Subject: Re: [onap-tsc] [Onap-lf-announce] Jenkins and Nexus downtime
From: Gildas Lanilis 
Date: Apr 18, 2018, 04:29
To: Kenny Paul ,onap-tsc 
Dear TSC member,

Nexus 3 is so slow that it will really help the ONAP community to have that 
work done asap.
This slowness of Nexus 3 is drastically impacting OOM and Heat deployment time. 
It will worth the 90 down time.
Not sure if Kenny is asking for a vote, but please respond asap so the work 
could be done tomorrow as planned.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-lf-announce-boun...@lists.onap.org 
[mailto:onap-lf-announce-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: Tuesday, April 17, 2018 6:21 PM
To: onap-tsc 
Cc: onap-lf-annou...@lists.onap.org
Subject: Re: [Onap-lf-announce] Jenkins and Nexus downtime

Given where we are in the release cycle, I've asked IT to hang off on this 
pending input form the TSC. This down time has been requested as the result of 
a call this morning discussing extremely long durations to pull docker images. 
The expectation is this will improve that issue.

Basically, I'm looking for a thumbs-up from the TSC Members before proceeding 
with scheduling down time.

Best Regards,
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone


From: 
>
 on behalf of Jeremy Phelps 
>
Date: Tuesday, April 17, 2018 at 4:15 PM
To: >
Subject: Re: [Onap-lf-announce] Jenkins and Nexus downtime

Date correction in the year:
Start Date/Time:
  - 8:30 am Pacific April 18, 2018
  - 
https://www.worldtimebuddy.com/?qm=1=8,100,4641239=8=2018-4-18=8.5-10
Systems affected:
  - jenkins.onap.org
  - nexus3.onap.org
Why:
  - LF IT is migrating the nexus3 system to a new node
Expected Downtime:
  - 1.5 hours

On Tue, Apr 17, 2018 at 6:10 PM, Jeremy Phelps 
> wrote:
Start Date/Time:
  - 8:30 am Pacific April 18, 2019
  - 
https://www.worldtimebuddy.com/?qm=1=8,100,4641239=8=2018-4-18=8.5-10
Systems affected:
  - jenkins.onap.org
  - nexus3.onap.org
Why:
  - LF IT is migrating the nexus3 system to a new node
Expected Downtime:
  - 1.5 hours

___ Onap-lf-announce mailing list 
onap-lf-annou...@lists.onap.org 
https://lists.onap.org/mailman/listinfo/onap-lf-announce
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Jenkins down

[Jessica Wagantall]

Dear ONAP team.

Jeremy and myself are working on checking the current issues with Jenkins
not picking the jobs
in the queue.

Thanks so much for your patience.

Jess
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Jenkins down

[Jessica Wagantall]

Dear team.

we are back on track now.

Thanks!
Jess

On Wed, Apr 18, 2018 at 10:28 AM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear ONAP team.
>
> Jeremy and myself are working on checking the current issues with Jenkins
> not picking the jobs
> in the queue.
>
> Thanks so much for your patience.
>
> Jess
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc