Re: [onap-tsc] M4 Code Freeze for Casablanca Release

[gildas.lani...@huawei.com]

Thanks Ben for the follow up. I will update TSC tomorrow with latest status.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Cheung, Ben (Nokia - US/Murray Hill) [mailto:ben.che...@nokia.com]
Sent: Friday, September 21, 2018 4:19 AM
To: Gildas Lanilis ; onap-release 
; Kang Xi ; Chaker Al Hakim 
; sb4...@att.com; b...@eliacik.com; 
ryan.halla...@att.com; 'Vul, Alex' ; 
mahim...@research.att.com; BLANDFORD, SCOTT ; BEGWANI, VIMAL 
; SUNDARAMURTHY, SHEKAR ; 
oskar.m...@ericsson.com; PUTHENPURA, SARAT (SARAT) ; 
Yang, Bin ; Ramki Krishnan ; 
rra...@ciena.com
Cc: Steve Winslow ; Phil Robb 
; Kenny Paul ; 
onap-tsc@lists.onap.org
Subject: RE: M4 Code Freeze for Casablanca Release

Gildas,

For 5G status, slides 7-12, I updated those with more recent status. (I 
sent you email about those yesterday).
I see the slides were generated before those updates. The wiki is up to 
date now.
There is still one update to be made by Vimal for the PNF/Life Cycle 
Management UC. Thanks.

Best regards,
-Ben Cheung, PhD, DMTS, ALTA
  ATF Architecture Systems Engineer
  Mobile Networks, Nokia
  Tel +1 (908) 679-6615
  Email  ben.che...@nokia.com
  600-700 Mountain Ave, Murray Hill, NJ 07974-0636 USA / #2C-378

From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Thursday, September 20, 2018 2:40 PM
To: onap-release 
mailto:onap-rele...@lists.onap.org>>; Kang Xi 
mailto:kang...@huawei.com>>; Chaker Al Hakim 
mailto:chaker.al.ha...@huawei.com>>; 
sb4...@att.com; 
b...@eliacik.com; 
ryan.halla...@att.com; 'Vul, Alex' 
mailto:alex@intel.com>>; 
mahim...@research.att.com; BLANDFORD, SCOTT 
mailto:cb1...@att.com>>; Cheung, Ben (Nokia - US/Murray Hill) 
mailto:ben.che...@nokia.com>>; BEGWANI, VIMAL 
mailto:vb1...@att.com>>; SUNDARAMURTHY, SHEKAR 
mailto:cs2...@att.com>>; 
oskar.m...@ericsson.com; PUTHENPURA, SARAT 
(SARAT) mailto:sa...@research.att.com>>; Yang, Bin 
mailto:bin.y...@windriver.com>>; Ramki Krishnan 
mailto:ram...@vmware.com>>; 
rra...@ciena.com
Cc: Steve Winslow 
mailto:swins...@linuxfoundation.org>>; Phil Robb 
mailto:pr...@linuxfoundation.org>>; Kenny Paul 
mailto:kp...@linuxfoundation.org>>; 
onap-tsc@lists.onap.org
Subject: RE: M4 Code Freeze for Casablanca Release

Hi All,

Thanks all for your contributions in making Casablanca.
I have posted M4 slide deck and checklist in wiki at 
https://wiki.onap.org/display/DW/TSC+2018-09-20+Meeting+Agenda and also 
attached for your convenience.

Below are the Action Items for the Community to fix within 1 week.

Action Items:

  1.  Slide #4: Michael Lando to review Bugs impacting HPA
  2.  Slide 7-12: Vimal Begwani to provide status on 5 G implementation
  3.  Slide 12: Sarat Puthenpura to provide ETA on 5G Performance Analysis and 
Optimization
  4.  Slide #16: PTLs to update Casablanca Platform Maturity table at 
https://wiki.onap.org/display/DW/Casablanca+Release+Platform+Maturity
  5.  Slide #16: Gildas to add Platform Maturity table in M4 checklist
  6.  Slide #23: Catherine Lefevre to update status on OSAM/PNF (postpone to 
Dublin or not)
  7.  Slide #25: Impacted PTLs to fix CSIT Failure.
  8.  Slide #27: Jonathan Gathman and Michael lando to increase code coverage 
for aaf-auth and sdc master and provide update on repos for which there is no 
report in Sonar.
  9.  Slide #28: Impacted PTLs to publish Vulnerability report. Steven Wright 
to follow up with Gildas for VVP.
  10. Slide #29-30: Impacted PTLs: Clean or Fix Job Failure
  11. Slide #32: OOF team for ensure Healthcheck passes.
  12. Slide # 33 Risks: Jonathan Gathman and Manoop Talasila to address risks 
#3 on CADI.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Friday, September 14, 2018 4:45 PM
To: 'onap-release' 
mailto:onap-rele...@lists.onap.org>>; Kang Xi 
mailto:kang...@huawei.com>>; Chaker Al Hakim 
mailto:chaker.al.ha...@huawei.com>>; 
sb4...@att.com; 'b...@eliacik.com' 
mailto:b...@eliacik.com>>; 'ryan.halla...@att.com' 
mailto:ryan.halla...@att.com>>; 'Vul, Alex' 
mailto:alex@intel.com>>; 'mahim...@research.att.com' 
mailto:mahim...@research.att.com>>; 'BLANDFORD, 
SCOTT' mailto:cb1...@att.com>>; 'ben.che...@nokia.com' 
mailto:ben.che...@nokia.com>>; BEGWANI, VIMAL 
mailto:vb1...@att.com>>; SUNDARAMURTHY, SHEKAR 
mailto:cs2...@att.com>>; 'oskar.m...@ericsson.com' 
mailto:oskar.m...@ericsson.com>>; 'PUTHENPURA, SARAT 
(SARAT)' mailto:sa...@research.att.com>>; 'Yang, Bin' 
mailto:bin.y...@windriver.com>>; 'Ramki Krishnan' 
mailto:ram...@vmware.com>>; 'rra...@ciena.com' 
mailto:rra...@ciena.com>>
Cc: 'Steve Winslow' 
mailto:swins...@linuxfoundation.org>>; 'Phil 
Robb' mailto:pr...@linuxfoundation.org>>; 'Kenny 
Paul' mailto:kp...@linuxfoundation.org>>; 

[onap-tsc] Restart Jenkins soon

[Jessica Wagantall]

Dear ONAP team,

I am seeing a lot of errors in Jenkins while trying to work through the
stalled queue.
Fortunately we are almost all done through the list of pending jobs
but I will need to perform a restart right after.

This should take no longer than 3 mins.

Thanks a ton for your patience!
Jess

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3781): https://lists.onap.org/g/ONAP-TSC/message/3781
Mute This Topic: https://lists.onap.org/mt/26234110/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] TSC Seat Vanacy

[Christopher Donley]

Catherine,

Chaker Al Hakim will be my proxy until there is an election to replace me.

Chris


From: Catherine LEFEVRE
To: ONAP-TSC@lists.onap.org;
Subject: Re: [onap-tsc] TSC Seat Vanacy
Time: 2018-09-26 07:53:46


Good morning TSC members,

I have reviewed the feedback that you have provided so far.

We are all in alignment to enhance the TSC Chart to address how to handle a 
vacancy.

It would be good to learn from other open source communities about how they are 
dealing with such situation while we are considering our ONAP ecosystem: 
reserved seats for operators and non-reserved seats.
We should not re-invent the wheel unnecessarily, there are certainly common 
patterns for some scenarios that you have listed.

I also recommend that we set a deadline to finalize the TSC chart addendum.
Therefore, on Oct 4th, we, the TSC, should present to the ONAP community our 
TSC chart amendment and then immediately act accordingly.
Stephen has already started to draft a new proposal that could be used as our 
starting point.
Jason was also making some suggestions considering our ONAP structure.

As a short-term solution, some of you have suggested that Huawei is identifying 
a proxy.
I believe this is indeed a great temporary solution so the new TSC can continue 
to operate as expected.
Chris, can you please confirm who will be your proxy? Thank you.

TSC members – let me know if you disagree otherwise let’s move forward and work 
on our TSC Chart add-on.

Many thanks and regards
Catherine

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Sunday, September 23, 2018 6:43 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membership criteria, and another full 
month to run an election. Leaving the seat vacant until the next scheduled 
election implies that after all that work the TSC doesn't care about being 
fully functional.  This would be a huge hit to the community's trust of the TSC.


  *   Delay any decision on an election until the TSC amends the Community 
Document to address how to handle a vacancy
This is marginally better than leaving the seat vacant, because who knows how 
long amending the Community Document might take. I would encourage the TSC to 
take up amending the Community Document to cover one or more of the operational 
and governance gaps that exist, however it is unfair to the ONAP community to 
hold the recently vacated seat hostage to those discussions.


  *   Have Chris appoint his replacement
When the TSC was comprised of only appointed individuals doing this would have 
been fine course of action. In fact, there were a couple instances back in 
March where this occurred. Now that we have moved from an appointed TSC to an 
elected TSC, such an appointment by a member is completely inappropriate.


  *   Make the next runner up in the August election the new TSC member
While true the seat does not belong to Huawei, it would be exceeding unfair to 
them, especially as the 2nd largest contributor to the Project, to suddenly be 
out in the cold with absolutely no chance to even compete for a seat they once 
held.

I don't like creating work for myself and a TCS election is indeed a great deal 
of work. The thought of having to run a new election is mind-numbing but I 
welcome it gladly because it is absolutely the right thing to do.

I recommend a one week nomination period, and a one week voting period. (The 
prior election was lengthened to two + two specifically to accommodate summer 
vacations).  I am at ONS-Europe this week and out the first week of October on 
family business. The earliest I can commit to kicking off the process (after 
revalidating qualified Active Community Members) would be Oct. 11th, putting 
the close of the election on 

[onap-tsc] For ONS-EU Attendees

[Kenny Paul]

I noticed this wasn't in Sched this morning.

It is there now. In Emerald Lounge #2

 
https://onseu18.sched.com/event/H36r/onap-tsc-introductions-and-operational-improvements-kenny-paul-the-linux-foundation

 

Best Regards, 
-kenny

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

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3779): https://lists.onap.org/g/ONAP-TSC/message/3779
Mute This Topic: https://lists.onap.org/mt/26229693/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Feed-back about features priority for Dublin

[Alexis de Talhouet]

Here are a few other topics that I forget to mentioned that we would love to 
see prioritized in Dublin:
- support for the applications to be deployed in a geo-redundant fashion 
(either active active/ active passive, ...)
- support and integration of PNDA within DCAE/CLAMP
- support for database as a service. A lot of applications are using SQL or 
Postgres, maybe we could harmonized and have one cluster of each where 
application could own their dB.
- implementation of a proper CI system providing daily feedback using the full 
robot suite (e.g. run distribution and instantiation) on the state of all our 
branches, whether release branches or master. Example of such CI has been 
implemented at various place, but would be good to see that integrated within 
ONAP CI system. This will allow to catch régression way earlier in the 
development cycle.

Regards,
Alexis


> On Sep 26, 2018, at 9:09 AM, Alexis de Talhouët  
> wrote:
> 
> Hello Alla,
> 
> As discussed yesterday, a critical feature we’ve been looking for is the 
> ability to enable self service of ONAP by our operational teams.
> With this in mind, during the Casablanca timeframe, Controller Design Studio 
> has emerged . It’s goal is to create a common platform to all controller 
> providing design capability to define controller blueprint, e.g. the WHAT, 
> and data dictionaries, e.g. the HOW. The blueprint is using a JSON TOSCA 
> based representation.
> it’s leaving under CCSDK, and will be harmonize with APPC CDT. This 
> initiative is well documented here 
> https://wiki.onap.org/plugins/servlet/mobile?contentId=35523521#content/view/35523521
> 
> In order to used the self serve framework, a few new microservices has arised 
> in the Casablanca timeframe. Our deliveries in Casablanca is to augment 
> current vFW assignent orchestration use case to enable name generation at VNF 
> and VF-MODULE level using policy based definition, and to enable 
> auto-assignment of ip addresses within defined pools in an ipam system (we 
> use netbox).
> 
> The enablement of this feature in Casablanca is permitted thanks to new SO 
> building block, and SDNC generic-resource-api DGs.
> 
> There is still a lot of work to do in Dublin and sub-sequent release to 
> properly integrate this within CCSDK and SDC and to be more feature complete. 
> The work items are being listed here: 
> https://wiki.onap.org/pages/viewpage.action?pageId=41422551
> 
> Finally, for those interested, we had a few deep dive sessions in all the 
> components comprising this new feature, the recording can be find here: 
> https://wiki.onap.org/display/DW/ONAP+Controller+Design+Studio+Working+Session
> 
> Another feature that will be valuable for us would be to have TOSCA based 
> orchestration at the SO layer.
> 
> Regards,
> Alexis

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3777): https://lists.onap.org/g/ONAP-TSC/message/3777
Mute This Topic: https://lists.onap.org/mt/26228330/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] TSC Seat Vanacy

[Catherine LEFEVRE]

Thank you Bin Yang for your prompt feedback.
I will extend the deadline by 2 weeks i.e. Oct 18th
I do not want to impact our RC0 Casablanca review planned on Oct 11th.

Many thanks & regards
Catherine

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Yang Bin
Sent: Wednesday, September 26, 2018 8:40 AM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy

Hi Catherine and TSC member,

Oct. 1st- 7th will be national holiday of China, So I would suggest that 
postpone the deadline by 1 week, Thanks.

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org 
[mailto:ONAP-TSC@lists.onap.org] On Behalf Of Catherine LEFEVRE
Sent: Wednesday, September 26, 2018 7:53 AM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy

Good morning TSC members,

I have reviewed the feedback that you have provided so far.

We are all in alignment to enhance the TSC Chart to address how to handle a 
vacancy.

It would be good to learn from other open source communities about how they are 
dealing with such situation while we are considering our ONAP ecosystem: 
reserved seats for operators and non-reserved seats.
We should not re-invent the wheel unnecessarily, there are certainly common 
patterns for some scenarios that you have listed.

I also recommend that we set a deadline to finalize the TSC chart addendum.
Therefore, on Oct 4th, we, the TSC, should present to the ONAP community our 
TSC chart amendment and then immediately act accordingly.
Stephen has already started to draft a new proposal that could be used as our 
starting point.
Jason was also making some suggestions considering our ONAP structure.

As a short-term solution, some of you have suggested that Huawei is identifying 
a proxy.
I believe this is indeed a great temporary solution so the new TSC can continue 
to operate as expected.
Chris, can you please confirm who will be your proxy? Thank you.

TSC members – let me know if you disagree otherwise let’s move forward and work 
on our TSC Chart add-on.

Many thanks and regards
Catherine

From: ONAP-TSC@lists.onap.org 
[mailto:ONAP-TSC@lists.onap.org] On Behalf Of Kenny Paul
Sent: Sunday, September 23, 2018 6:43 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membership criteria, and another full 
month to run an election. Leaving the seat vacant until the next scheduled 
election implies that after all that work the TSC doesn't care about being 
fully functional.  This would be a huge hit to the community's trust of the TSC.


  *   Delay any decision on an election until the TSC amends the Community 
Document to address how to handle a vacancy
This is marginally better than leaving the seat vacant, because who knows how 
long amending the Community Document might take. I would encourage the TSC to 
take up amending the Community Document to cover one or more of the operational 
and governance gaps that exist, however it is unfair to the ONAP community to 
hold the recently vacated seat hostage to those discussions.


  *   Have Chris appoint his replacement
When the TSC was comprised of only appointed individuals doing this would have 
been fine course of action. In fact, there were a couple instances back in 
March where this occurred. Now that we have moved from an appointed TSC to an 
elected TSC, such an appointment by a member is completely inappropriate.


  *   Make the next runner up in the August election the new TSC member
While true the seat does not belong to 

[onap-tsc] Feed-back about features priority for Dublin

[Alexis de Talhouet]

Hello Alla,

As discussed yesterday, a critical feature we’ve been looking for is the 
ability to enable self service of ONAP by our operational teams.
With this in mind, during the Casablanca timeframe, Controller Design Studio 
has emerged . It’s goal is to create a common platform to all controller 
providing design capability to define controller blueprint, e.g. the WHAT, and 
data dictionaries, e.g. the HOW. The blueprint is using a JSON TOSCA based 
representation.
it’s leaving under CCSDK, and will be harmonize with APPC CDT. This initiative 
is well documented here 
https://wiki.onap.org/plugins/servlet/mobile?contentId=35523521#content/view/35523521

In order to used the self serve framework, a few new microservices has arised 
in the Casablanca timeframe. Our deliveries in Casablanca is to augment current 
vFW assignent orchestration use case to enable name generation at VNF and 
VF-MODULE level using policy based definition, and to enable auto-assignment of 
ip addresses within defined pools in an ipam system (we use netbox).

The enablement of this feature in Casablanca is permitted thanks to new SO 
building block, and SDNC generic-resource-api DGs.

There is still a lot of work to do in Dublin and sub-sequent release to 
properly integrate this within CCSDK and SDC and to be more feature complete. 
The work items are being listed here: 
https://wiki.onap.org/pages/viewpage.action?pageId=41422551

Finally, for those interested, we had a few deep dive sessions in all the 
components comprising this new feature, the recording can be find here: 
https://wiki.onap.org/display/DW/ONAP+Controller+Design+Studio+Working+Session

Another feature that will be valuable for us would be to have TOSCA based 
orchestration at the SO layer.

Regards,
Alexis

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3775): https://lists.onap.org/g/ONAP-TSC/message/3775
Mute This Topic: https://lists.onap.org/mt/26228330/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] TSC Seat Vanacy

[Yang Bin]

Hi Catherine and TSC member,

Oct. 1st- 7th will be national holiday of China, So I would suggest that 
postpone the deadline by 1 week, Thanks.

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Wednesday, September 26, 2018 7:53 AM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy

Good morning TSC members,

I have reviewed the feedback that you have provided so far.

We are all in alignment to enhance the TSC Chart to address how to handle a 
vacancy.

It would be good to learn from other open source communities about how they are 
dealing with such situation while we are considering our ONAP ecosystem: 
reserved seats for operators and non-reserved seats.
We should not re-invent the wheel unnecessarily, there are certainly common 
patterns for some scenarios that you have listed.

I also recommend that we set a deadline to finalize the TSC chart addendum.
Therefore, on Oct 4th, we, the TSC, should present to the ONAP community our 
TSC chart amendment and then immediately act accordingly.
Stephen has already started to draft a new proposal that could be used as our 
starting point.
Jason was also making some suggestions considering our ONAP structure.

As a short-term solution, some of you have suggested that Huawei is identifying 
a proxy.
I believe this is indeed a great temporary solution so the new TSC can continue 
to operate as expected.
Chris, can you please confirm who will be your proxy? Thank you.

TSC members – let me know if you disagree otherwise let’s move forward and work 
on our TSC Chart add-on.

Many thanks and regards
Catherine

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Sunday, September 23, 2018 6:43 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membership criteria, and another full 
month to run an election. Leaving the seat vacant until the next scheduled 
election implies that after all that work the TSC doesn't care about being 
fully functional.  This would be a huge hit to the community's trust of the TSC.


  *   Delay any decision on an election until the TSC amends the Community 
Document to address how to handle a vacancy
This is marginally better than leaving the seat vacant, because who knows how 
long amending the Community Document might take. I would encourage the TSC to 
take up amending the Community Document to cover one or more of the operational 
and governance gaps that exist, however it is unfair to the ONAP community to 
hold the recently vacated seat hostage to those discussions.


  *   Have Chris appoint his replacement
When the TSC was comprised of only appointed individuals doing this would have 
been fine course of action. In fact, there were a couple instances back in 
March where this occurred. Now that we have moved from an appointed TSC to an 
elected TSC, such an appointment by a member is completely inappropriate.


  *   Make the next runner up in the August election the new TSC member
While true the seat does not belong to Huawei, it would be exceeding unfair to 
them, especially as the 2nd largest contributor to the Project, to suddenly be 
out in the cold with absolutely no chance to even compete for a seat they once 
held.

I don't like creating work for myself and a TCS election is indeed a great deal 
of work. The thought of having to run a new election is mind-numbing but I 
welcome it gladly because it is absolutely the right thing to do.

I recommend a one week nomination period, and a one week voting period. (The 
prior election was