答复: [onap-tsc] Soliciting interest for ONAP internship projects

[Yan Yang]

HI  Lingli,

 

Following is one proposal  for VF-C Project.

Description: Supporting VNF Initial configuration in VF-C GVNFM

Additional Information: Implement VNF Initial configuration function via SSH in 
VF-C which includes SSH remote connection via username/password, or auth key, 
SSH execution and parse SSH result. 

Study and implement (if time allows) more init configuration method to VNF.

Desirable Skills: Python, SSH, Django

Expected Outcome: Providing the VNF Initial configuration function via SSH in 
VF-C GVNFM

Difficulty: Medium

Desired project timeline/completion date: 2019/03

Mentor(s) & contact info:

Name: Yan Yang

Tel: 86-15210838572

E-mail: yangya...@chinamobile.com

 

Best Regards,

Yan

发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表 Lingli Deng
发送时间: 2018年10月12日 15:06
收件人: onap-tsc
主题: [onap-tsc] Soliciting interest for ONAP internship projects

 

Hi all,

 

Per the discussion during the TSC all earlier today, for the sake of getting a 
rough sense for budgeting internship program for ONAP next year, I am writing 
to solicit interest for related internship project proposals.

If you are interested in proposing an internship project for augmenting ONAP 
and/or willing to help in mentoring it on execution (including defining the 
project scope, developing the implmentation plan for the project, and 
recruting, supervising and reviewing the intern for its execution), please 
reply with your ideas by filling the information in the following template by 
next Monday.

(More description for LFN internship program would be found here: 
https://wiki.lfnetworking.org/display/LN/LF+Networking+Internships#LFNetworkingInternships-ProposingaProject)

 

Description:

Additional Information:

 

Desirable Skills:

 

Expected Outcome:

 

Difficulty:

Hihg/Medium/Low

Desired project timeline/completion date:

 

Mentor(s) & contact info:

Thanks,

Lingli/邓灵莉

中国移动通信研究院

denglin...@chinamobile.com

 




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

View/Reply Online (#3939): https://lists.onap.org/g/onap-tsc/message/3939
Mute This Topic: https://lists.onap.org/mt/27400049/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: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

[Lv Bo]

Thanks Huabing.






Sorry for missing the disccussion.






 > Lv Bo – can you please confirm urgently your engagement, helping AAI team on 
 > Security issues, CII badging? Thank you.


Ok, I will try my best to handle the aai/esr issues. Thanks for your pre works. 
I will be familiar with the work asap.






Regards.


Lv Bo










原始邮件



发件人：赵化冰10201488
收件人：CatherineLEFEVRE ;吕波10185543;
抄送人：onap-tsc@lists.onap.org ;FORSYTH, JAMES 
;
日 期 ：2018年10月18日 09:17
主 题 ：Re: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.




Hi folks,






Loop Lv bo in.






It seems that Lv bo isn't aware of this discussion because he doesn't subscribe 
to the TSC mailinglist.






BR,


Huabing










发件人：CatherineLEFEVRE 
收件人：onap-tsc@lists.onap.org ;
抄送人：FORSYTH, JAMES ;
日 期 ：2018年10月18日 05:28
主 题 ：Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.




Thank you Kenny for bringing this issue to our attention.


Thank you Alexis for your feedback.


 


Speaking to Jimmy, AAI PTL, I understand that no new code was released related 
to AAI/ESR as part of the Casablanca release.


The current challenge is to progress on the Security issues (even if the code 
did not change, the security criteria has increased including Severe).


Therefore the immediate request is not the promotion of any AAI committer but 
the allocation of AA/ESR SME to fix these issues.


 


As stated by Kenny, Lv Bo did not make any contribution yet but it will be a 
great opportunity for him to demonstrate his engagement on AAI/ESR before being 
eligible  for committer election.


 


Lv Bo – can you please confirm urgently your engagement, helping AAI team on 
Security issues, CII badging? Thank you.


 


AAI/ESR Security issues – mainly Tomcat, jquery, bootstrap, dropwizard.jaws and 
our famous fasterxml.jackson, etc.


Additional information can be provided as soon as an AAI/ESR SME starts to be 
engaged.


 


I would also recommend to review the existing committers list in case of some 
of them have not been active during this release.


 


In addition, what will be the future of AAI/ESR sub-project if the engagement 
is not confirmed?


 


Many thanks & regards


Catherine


 



From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
 Sent: Wednesday, October 17, 2018 2:06 PM
 To: onap-tsc@lists.onap.org
 Cc: FORSYTH, JAMES 
 Subject: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.




 


Hi,


 


When it comes to define new committers for a given project, what I’ve seen 
happening before, and it worked fairly well, is to have the PTL of the project 
start a committer election of a week or two.. Contributors to the project can 
self-nominate  themselves, and once nomination period is over, committers vote 
whether each nominee can become committer by assessing their involvement in the 
project (e.g. meritocracy).



It is generally good to perform such committer election at the beginning of 
each release, as it allows to make sure we don’t have an un-healthy project 
with not enough committers, and also to recognize work that has been done 
during previous  release. It is also good practice to refresh project’s 
committer list by making sure all committers are *active*.



 


In this case, I would suggest to run a committer election within the project. 
That way, who ever feels then can take on the committer role can candidate.



In the case no one show up, then it’s a different discussion. In the case ppl 
showing up don’t have any contribution to that specific project is up to the 
actual committers to decide what to do.



Once new committers have been elected within the project, PTL sends a mail to 
TSC asking to vote on whether new committers can be approved or not. Knowing 
the background / history of the project, TSC should be able to judge the 
candidate  accordingly, making sure the project can be in a healthy state.



 


I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo 
should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li 
Zi and Sun QI vote, then PTL present to TSC with new potential committer(s),  
being, among other, Lv Bo. And we can have that as an TSC agenda item to 
discuss briefly whether we agree to have Lv Bo committer knowing the history.



 


Regards,



Alexis




 
 


On Oct 16, 2018, at 10:03 PM, Kenny Paul  wrote:



 


Jimmy tried to pursue the correct channels to resolve the following issue but 
he is stuck, so I'm formally escalating it to the TSC.  



 


Li Zi, (li.z...@zte.com.cn) has been the primary code contributor and Committer 
to the ESR sub project  of AAI. She is no longer participating in the ONAP 
project and security fixes are required for the Casablanca Release.



· Li  Zi requested that Lv Bo (lv.bo...@zte.com.cn) be assigned as her 
replacement. This is not allowed as it violates sections 3.1.1Contributor & 
3.1.2Committer of the ONAP 

Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

[Huabing]

Hi folks,






Loop Lv bo in.






It seems that Lv bo isn't aware of this discussion because he doesn't subscribe 
to the TSC mailinglist.






BR,


Huabing







原始邮件



发件人：CatherineLEFEVRE 
收件人：onap-tsc@lists.onap.org ;
抄送人：FORSYTH, JAMES ;
日 期 ：2018年10月18日 05:28
主 题 ：Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.




Thank you Kenny for bringing this issue to our attention.


Thank you Alexis for your feedback.


 


Speaking to Jimmy, AAI PTL, I understand that no new code was released related 
to AAI/ESR as part of the Casablanca release.


The current challenge is to progress on the Security issues (even if the code 
did not change, the security criteria has increased including Severe).


Therefore the immediate request is not the promotion of any AAI committer but 
the allocation of AA/ESR SME to fix these issues.


 


As stated by Kenny, Lv Bo did not make any contribution yet but it will be a 
great opportunity for him to demonstrate his engagement on AAI/ESR before being 
eligible  for committer election.


 


Lv Bo – can you please confirm urgently your engagement, helping AAI team on 
Security issues, CII badging? Thank you.


 


AAI/ESR Security issues – mainly Tomcat, jquery, bootstrap, dropwizard.jaws and 
our famous fasterxml.jackson, etc.


Additional information can be provided as soon as an AAI/ESR SME starts to be 
engaged.


 


I would also recommend to review the existing committers list in case of some 
of them have not been active during this release.


 


In addition, what will be the future of AAI/ESR sub-project if the engagement 
is not confirmed?


 


Many thanks & regards


Catherine


 



From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
 Sent: Wednesday, October 17, 2018 2:06 PM
 To: onap-tsc@lists.onap.org
 Cc: FORSYTH, JAMES 
 Subject: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.




 


Hi,


 



When it comes to define new committers for a given project, what I’ve seen 
happening before, and it worked fairly well, is to have the PTL of the project 
start a committer election of a week or two.. Contributors to the project can 
self-nominate  themselves, and once nomination period is over, committers vote 
whether each nominee can become committer by assessing their involvement in the 
project (e.g. meritocracy).



It is generally good to perform such committer election at the beginning of 
each release, as it allows to make sure we don’t have an un-healthy project 
with not enough committers, and also to recognize work that has been done 
during previous  release. It is also good practice to refresh project’s 
committer list by making sure all committers are *active*.



 



In this case, I would suggest to run a committer election within the project. 
That way, who ever feels then can take on the committer role can candidate.



In the case no one show up, then it’s a different discussion. In the case ppl 
showing up don’t have any contribution to that specific project is up to the 
actual committers to decide what to do.



Once new committers have been elected within the project, PTL sends a mail to 
TSC asking to vote on whether new committers can be approved or not. Knowing 
the background / history of the project, TSC should be able to judge the 
candidate  accordingly, making sure the project can be in a healthy state.



 



I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo 
should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li 
Zi and Sun QI vote, then PTL present to TSC with new potential committer(s),  
being, among other, Lv Bo. And we can have that as an TSC agenda item to 
discuss briefly whether we agree to have Lv Bo committer knowing the history.



 



Regards,



Alexis




 
 


On Oct 16, 2018, at 10:03 PM, Kenny Paul  wrote:



 


Jimmy tried to pursue the correct channels to resolve the following issue but 
he is stuck, so I'm formally escalating it to the TSC.  



 



Li Zi, (li.z...@zte.com.cn) has been the primary code contributor and Committer 
to the ESR sub project  of AAI. She is no longer participating in the ONAP 
project and security fixes are required for the Casablanca Release.



· Li  Zi requested that Lv Bo (lv.bo...@zte.com.cn) be assigned as her 
replacement. This is not allowed as it violates sections 3.1.1Contributor & 
3.1.2Committer of the ONAP Technical Community document:


Committers cannot be appointed, they must be meritocracy elected from the pool 
of active Contributors to that project's repositories

There is no record of Lv Bo ever making a contribution to the aai/esr-* 
repositories.
 ( There have been numerous code contributions to a different ONAP project:  
msb/service-mesh )


 



The only Committers on the aai/esr-* repos are Li Zi, (li.z...@zte.com.cn) and 
Sun Qi (sun.qi...@zte.com.cn).  Both were the only individuals listed on the 
original project 

Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

[Catherine LEFEVRE]

Thank you Kenny for bringing this issue to our attention.
Thank you Alexis for your feedback.

Speaking to Jimmy, AAI PTL, I understand that no new code was released related 
to AAI/ESR as part of the Casablanca release.
The current challenge is to progress on the Security issues (even if the code 
did not change, the security criteria has increased including Severe).
Therefore the immediate request is not the promotion of any AAI committer but 
the allocation of AA/ESR SME to fix these issues.

As stated by Kenny, Lv Bo did not make any contribution yet but it will be a 
great opportunity for him to demonstrate his engagement on AAI/ESR before being 
eligible for committer election.

Lv Bo – can you please confirm urgently your engagement, helping AAI team on 
Security issues, CII badging? Thank you.

AAI/ESR Security issues – mainly Tomcat, jquery, bootstrap, dropwizard.jaws and 
our famous fasterxml.jackson, etc.
Additional information can be provided as soon as an AAI/ESR SME starts to be 
engaged.

I would also recommend to review the existing committers list in case of some 
of them have not been active during this release.

In addition, what will be the future of AAI/ESR sub-project if the engagement 
is not confirmed?

Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Wednesday, October 17, 2018 2:06 PM
To: onap-tsc@lists.onap.org
Cc: FORSYTH, JAMES 
Subject: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

Hi,

When it comes to define new committers for a given project, what I’ve seen 
happening before, and it worked fairly well, is to have the PTL of the project 
start a committer election of a week or two.. Contributors to the project can 
self-nominate themselves, and once nomination period is over, committers vote 
whether each nominee can become committer by assessing their involvement in the 
project (e.g. meritocracy).
It is generally good to perform such committer election at the beginning of 
each release, as it allows to make sure we don’t have an un-healthy project 
with not enough committers, and also to recognize work that has been done 
during previous release. It is also good practice to refresh project’s 
committer list by making sure all committers are *active*.

In this case, I would suggest to run a committer election within the project. 
That way, who ever feels then can take on the committer role can candidate.
In the case no one show up, then it’s a different discussion. In the case ppl 
showing up don’t have any contribution to that specific project is up to the 
actual committers to decide what to do.
Once new committers have been elected within the project, PTL sends a mail to 
TSC asking to vote on whether new committers can be approved or not. Knowing 
the background / history of the project, TSC should be able to judge the 
candidate accordingly, making sure the project can be in a healthy state.

I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo 
should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li 
Zi and Sun QI vote, then PTL present to TSC with new potential committer(s), 
being, among other, Lv Bo. And we can have that as an TSC agenda item to 
discuss briefly whether we agree to have Lv Bo committer knowing the history.

Regards,
Alexis


On Oct 16, 2018, at 10:03 PM, Kenny Paul 
mailto:kp...@linuxfoundation.org>> wrote:

Jimmy tried to pursue the correct channels to resolve the following issue but 
he is stuck, so I'm formally escalating it to the TSC.

Li Zi, (li.z...@zte.com.cn) has been the primary 
code contributor and Committer to the ESR sub project of AAI. She is no longer 
participating in the ONAP project and security fixes are required for the 
Casablanca Release.
• Li Zi requested that Lv Bo 
(lv.bo...@zte.com.cn) be assigned as her 
replacement. This is not allowed as it violates sections 3.1.1   
Contributor
 & 3.1.2   
Committer
 of the ONAP Technical Community document:

  *   Committers cannot be appointed, they must be meritocracy elected from the 
pool of active Contributors to that project's repositories
  *   There is no record of Lv Bo ever making a contribution to the aai/esr-* 
repositories.
( There have been numerous 

Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a vacancey"

[Jason Hunt]

One case that wasn't in Chaker's list, but might trigger some discussion 

would be:



 An elected TSC member representing Operator A takes a job with a Vendor A 

that does not have a representative on the TSC.



As written, the charter proposal says that the TSC member keeps his/her 

seat and Operator A would be without a representative on the TSC (until 

the next election cycle).  However, the table in the top of the document 

states otherwise (Operator A can appoint a new member and the TSC member 

might keep their seat if the TSC numbers are not exceeded).



We need to sync up the charter language with the table, if the table is 

what we intend.





Regards,

Jason Hunt 

Distinguished Engineer, IBM 



Phone: 314-749-7422

Email: djh...@us.ibm.com

Twitter: @DJHunt

 







From:   "Chaker Al Hakim" 

To: "onap-tsc@lists.onap.org" 

Date:   10/17/2018 03:29 PM

Subject:Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how 

to hanlde a vacancey"

Sent by:onap-tsc@lists.onap.org







Hi Steve,

 

Thanks for the clarifications

 

Regards,

Chaker

 

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf 

Of Stephen Terrill

Sent: Wednesday, October 17, 2018 2:59 PM

To: onap-tsc@lists.onap.org

Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to 

hanlde a vacancey"

 

Hi Chaker,

 

Discussion is always welcome – I wanted to point out though that I believe 

that the cases you proposed are covered in the proposal, which I will 

clarify below:

1.   If an elected TSC member from an Operator A changes jobs and 

moves to Operator B that’s already represented on the TSC board 

a.   Would the ‘TSC Member’ be forced to resign based on the TSC rules 

or Operator(s) make the decision?)

b.  Would the TSC run a new election?

c.   Who would be eligible to run?

Steve: I believe this is covered.  This would violate the TSC composition 

rules, hence the moving TSC member would stepdown or be considered as 

such.

2.   An elected TSC member representing Operator A takes a job with a 

Vendor A that is already represented with an elected TSC member 

a.   Would the ‘TSC Member’ be forced to resign based on the TSC rules 

or Operator/vendor make the decision?

b.  Would the TSC run a new election?

c.   Who would be eligible to run in the new election?

Steve: I believe this is covered.  This would violate the TSC composition 

rules, hence the moving TSC member would stepdown or be considered as 

such.

3.   If an elected TSC member from Vendor A takes a job with vendor B 

which had failed to win a TSC seat during the official TSC election (this 

is an interesting case) 

a.   Would the ‘TSC Member’ be forced to resign based on the TSC rules 

or Operator and/or vendor make the decision?)

b.  Who would be eligible to run in the new election?

c.   Eligibility

Steve: I believe this is covered.  According to this proposal, the TSC 

member is not forced to resign as the TSC composition rules are not 

violated.

 

Of course its another thing if there is disagreement for the basis of the 

proposal. 

 

BR,

 

Steve

 

From: onap-tsc@lists.onap.org  On Behalf Of 

Chaker Al Hakim

Sent: Wednesday 17 October 2018 20:27

To: onap-tsc@lists.onap.org

Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to 

hanlde a vacancey"

 

Hi all,

 

I had sent the attached email back in September proposing a few more cases 

to consider so that we don’t have to work the same exercise again when/if 

they do occur.

I’d like to include them in the discussion tomorrow and decide as a team 

on how we move forward.

 

Thanks,

Chaker

 

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf 

Of Stephen Terrill

Sent: Wednesday, October 17, 2018 4:15 AM

To: onap-tsc@lists.onap.org

Subject: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde 

a vacancey"

 

Hi,

 

As TSC-1 jira is on the TSC agenda, a proposal has been uploaded.  While 

this and previous versions have been shared with the Task force, there is 

still ongoing discussion however I thought that it fair to share the 

latest proposal with the TSC members before the meeting this week.

 

It is attatched in the jira: 

https://jira.onap.org/browse/TSC-1?src=confmacro 

 

BR,

 

Steve

 

 



 

Stephen Terrill 

Senior Expert, Automation and Management

 

TECHNOLOGY SPECIALIST

BDGS RDP Architecture & Technology

Phone: +34913393005

Mobile: +34609168515

stephen.terr...@ericsson.com

 

Ericsson

C/ Via de los Poblados 13. B

28033,Madrid, Madrid

Spain

ericsson.com

 



 

Our commitment to Technology for Good and Diversity and Inclusion 

contributes to positive change.

Follow us on: Facebook LinkedIn Twitter



Legal entity:ERICSSON AB registration number 556056-6258, registered 

office in Stockholm.

This communication is confidential. Our email terms: 

Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a vacancey"

[Chaker Al Hakim]

Hi Steve,

Thanks for the clarifications

Regards,
Chaker


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Wednesday, October 17, 2018 2:59 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi Chaker,

Discussion is always welcome - I wanted to point out though that I believe that 
the cases you proposed are covered in the proposal, which I will clarify below:
1.   If an elected TSC member from an Operator A changes jobs and moves to 
Operator B that's already represented on the TSC board
a.   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator(s) make the decision?)
b.  Would the TSC run a new election?
c.   Who would be eligible to run?
Steve: I believe this is covered.  This would violate the TSC composition 
rules, hence the moving TSC member would stepdown or be considered as such.
2.   An elected TSC member representing Operator A takes a job with a 
Vendor A that is already represented with an elected TSC member
a.   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator/vendor make the decision?
b.  Would the TSC run a new election?
c.   Who would be eligible to run in the new election?
Steve: I believe this is covered.  This would violate the TSC composition 
rules, hence the moving TSC member would stepdown or be considered as such.
3.   If an elected TSC member from Vendor A takes a job with vendor B which 
had failed to win a TSC seat during the official TSC election (this is an 
interesting case)
a.   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator and/or vendor make the decision?)
b.  Who would be eligible to run in the new election?
c.   Eligibility
Steve: I believe this is covered.  According to this proposal, the TSC member 
is not forced to resign as the TSC composition rules are not violated.

Of course its another thing if there is disagreement for the basis of the 
proposal.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Chaker 
Al Hakim
Sent: Wednesday 17 October 2018 20:27
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi all,

I had sent the attached email back in September proposing a few more cases to 
consider so that we don't have to work the same exercise again when/if they do 
occur.
I'd like to include them in the discussion tomorrow and decide as a team on how 
we move forward.

Thanks,
Chaker


From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Wednesday, October 17, 2018 4:15 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi,

As TSC-1 jira is on the TSC agenda, a proposal has been uploaded.  While this 
and previous versions have been shared with the Task force, there is still 
ongoing discussion however I thought that it fair to share the latest proposal 
with the TSC members before the meeting this week.

It is attatched in the jira:
https://jira.onap.org/browse/TSC-1?src=confmacro

BR,

Steve


[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

[http://www.ericsson.com/current_campaign]

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer


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

View/Reply Online (#3931): https://lists.onap.org/g/onap-tsc/message/3931
Mute This Topic: https://lists.onap.org/mt/27378093/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: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

[Robert]

Yes Mike, no problem, but not next week L

What about the week after next??  We are in CET time zone…

The main player is Michal here, he will provide you with all the info and also 
work with you on further development

 

thx

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Mike Elliott
Sent: Wednesday, October 17, 2018 17:32
To: onap-tsc@lists.onap.org
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Catherine & Robert,

 

This is a great contribution Robert and it makes perfect sense to pull it into 
the OOM project.

It aligns very well with OOM’s goals and I believe it may even close off some 
of our Jira tickets .

 

Robert, can we setup a meeting next week so you can educate the OOM team on the 
SI Package Builder and discuss next steps?

 

Thanks,

Mike

 

From:  on behalf of Catherine LEFEVRE 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, October 17, 2018 at 6:18 AM
To: "onap-tsc@lists.onap.org" 
Cc: "m.pta...@partner.samsung.com" 
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Good morning Robert,

 

Thank you so much Robert for sharing this great contribution.

I agree with Stephen and Viswa.

It would be great if your activities are covered under the OOM project umbrella.

 

Mike Elliot – how do you feel about this?

 

Many thanks & regards

Catherine

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Robert
Sent: Wednesday, October 17, 2018 10:11 AM
To: onap-tsc@lists.onap.org
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Viswa,

 

Yes, agree, we should analyze requirements, impact and scope before deciding if 
we need new project or not.

Certainly, at least requirements sync would be necessary between the two (OOM 
and SI).

 

And yes, your understanding is right, currently working OOM deployment is 
necessary for development of SI Package Builder.

 

 

Btw, Michal Ptacek is participating in Integration project weekly calls, hope 
they will discuss it there…

 

 

 

Thx

/robert

 

 

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Viswanath Kumar Skand Priya via Lists.Onap.Org
Sent: Wednesday, October 17, 2018 09:21
To: onap-tsc
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

I second the idea of having standalone / offline mode of ONAP installation. It 
is indeed a requirement for us as we don't really enjoy the luxury of open 
internet even in our labs.

We have similar version of offline repos ( nexus, mvn, cache ) to minimise the 
dependency on external world and this SI is exactly what we would prefer.

 

However I would like to understand the need for starting a different project or 
placement under Integration project. As per my understanding, the proposed 
solution is still based on deploying ONAP via OOM, where the dependencies are 
downloaded one-time, cached and re-used within local ecosystem. In this case, 
why can't this project be annexed within OOM project's scope ? 

 

BR,

Viswa


 

 

 http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$

 

Viswanath Kumar Skand Priya

Senior Architect

Technology, Architecture & Planning

 

 

 

On Wed, Oct 17, 2018 at 12:36 PM Robert  wrote:

Hi Steve,

 

We are open for suggestions…

IHMO, it would not hurt to have 2 different installers to give options for 
customers. i.e.: Openstack for example provides multiply installers.

 

Our approach is clearly targeting narrow carrier requirements, where 
deployments are predictable, repeatable and performed without any external 
connectivity, additionally giving customers comfort knowing exactly what is 
deployed.

 

thx

 

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Tuesday, October 16, 2018 20:51
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

Were you thinking of an additional project to capture this, or under the 
integration project?

 

BR,

 

Steve

 

From: onap-tsc@lists.onap.org  On Behalf Of 
r.re...@samsung.com
Sent: Tuesday 16 October 2018 16:28
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Beijing Offline SI Installer

 

Dear ONAP TSC Members,

 

During the ONAP Casablanca Developer Forum in Beijing we have promised to 
upstream our ONAP offline deployment tool.

 

As of yesterday, finally we did hold to our promise and published SI (Self 
Installer) in ONAP Supporting Tools wiki:

(the delay was due to development of additional the package builder which was 
initially done 

Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a vacancey"

[Stephen Terrill]

Hi Chaker,

Discussion is always welcome - I wanted to point out though that I believe that 
the cases you proposed are covered in the proposal, which I will clarify below:

  1.  If an elected TSC member from an Operator A changes jobs and moves to 
Operator B that's already represented on the TSC board
 *   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator(s) make the decision?)
 *   Would the TSC run a new election?
 *   Who would be eligible to run?
Steve: I believe this is covered.  This would violate the TSC composition 
rules, hence the moving TSC member would stepdown or be considered as such.

  1.  An elected TSC member representing Operator A takes a job with a Vendor A 
that is already represented with an elected TSC member
 *   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator/vendor make the decision?
 *   Would the TSC run a new election?
 *   Who would be eligible to run in the new election?
Steve: I believe this is covered.  This would violate the TSC composition 
rules, hence the moving TSC member would stepdown or be considered as such.

  1.  If an elected TSC member from Vendor A takes a job with vendor B which 
had failed to win a TSC seat during the official TSC election (this is an 
interesting case)
 *   Would the 'TSC Member' be forced to resign based on the TSC  rules or 
Operator and/or vendor make the decision?)
 *   Who would be eligible to run in the new election?
 *   Eligibility
Steve: I believe this is covered.  According to this proposal, the TSC member 
is not forced to resign as the TSC composition rules are not violated.

Of course its another thing if there is disagreement for the basis of the 
proposal.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of Chaker Al 
Hakim
Sent: Wednesday 17 October 2018 20:27
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi all,

I had sent the attached email back in September proposing a few more cases to 
consider so that we don't have to work the same exercise again when/if they do 
occur.
I'd like to include them in the discussion tomorrow and decide as a team on how 
we move forward.

Thanks,
Chaker


From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Wednesday, October 17, 2018 4:15 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi,

As TSC-1 jira is on the TSC agenda, a proposal has been uploaded.  While this 
and previous versions have been shared with the Task force, there is still 
ongoing discussion however I thought that it fair to share the latest proposal 
with the TSC members before the meeting this week.

It is attatched in the jira:
https://jira.onap.org/browse/TSC-1?src=confmacro

BR,

Steve


[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

[http://www.ericsson.com/current_campaign]

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer


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

View/Reply Online (#3928): https://lists.onap.org/g/onap-tsc/message/3928
Mute This Topic: https://lists.onap.org/mt/27378093/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] JIRA TSC-1 "Update TSC Chart to address how to hanlde a vacancey"

[Chaker Al Hakim]

Hi all,

I had sent the attached email back in September proposing a few more cases to 
consider so that we don't have to work the same exercise again when/if they do 
occur.
I'd like to include them in the discussion tomorrow and decide as a team on how 
we move forward.

Thanks,
Chaker


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Wednesday, October 17, 2018 4:15 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a 
vacancey"

Hi,

As TSC-1 jira is on the TSC agenda, a proposal has been uploaded.  While this 
and previous versions have been shared with the Task force, there is still 
ongoing discussion however I thought that it fair to share the latest proposal 
with the TSC members before the meeting this week.

It is attatched in the jira:
https://jira.onap.org/browse/TSC-1?src=confmacro

BR,

Steve


[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

[http://www.ericsson.com/current_campaign]

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer


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

View/Reply Online (#3927): https://lists.onap.org/g/onap-tsc/message/3927
Mute This Topic: https://lists.onap.org/mt/27378093/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]
-=-=-=-=-=-=-=-=-=-=-=-

--- Begin Message ---
Hi everyone,



I believe we also need to define  how and when a TSC seat would “ become 
vacant’ and  define a set of rules/guidelines to handle each and every 
situation; for example



1.   If an elected TSC member from an Operator A changes jobs and moves to 
Operator B that’s already represented on the TSC board

a.   Would the ‘TSC Member’ be forced to resign based on the TSC  rules or 
Operator(s) make the decision?)

b.  Would the TSC run a new election?

c.   Who would be eligible to run?

d.

2.   An elected TSC member representing Operator A takes a job with a 
Vendor A that is already represented with an elected TSC member

a.   Would the ‘TSC Member’ be forced to resign based on the TSC  rules or 
Operator/vendor make the decision?

b.  Would the TSC run a new election?

c.   Who would be eligible to run in the new election?

d.

3.   If an elected TSC member from Vendor A takes a job with vendor B which 
had failed to win a TSC seat during the official TSC election (this is an 
interesting case)

a.   Would the ‘TSC Member’ be forced to resign based on the TSC  rules or 
Operator and/or vendor make the decision?)

b.  Who would be eligible to run in the new election?

c.   Eligibility

4.   ..etc



Perhaps we should consider the above cases as part of the larger discussion so 
that we close some of  the potential future loopholes.



Regards,

Chaker







From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Sunday, September 23, 2018 5:59 PM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy



Hi,



To this effect.  An appointed size was agreed.  I think it makes sense to run a 
new election for that seat – continuing with the previous voting list does not 
take into account the current situation, as the voting was in the context of an 
earlier situation:



We need to take into account two situations as I see it:

-  Any TSC member is no longer able to support the role

-  The TSC member that can no longer support the role is a chair or 
vice chair.

-  We need to cater for the appointed positions as well.



To this effect, can we amend the community charter as follows:

-  Add to section 4.2.3:

o   4.2.3.3 TSC member abdication

•• In the event of a TSC member no longer being able to continue being a member 
of the TSC:

• If the TSC position was from an operator, the operator may appoint a 
member that fulfils the criteria of being an 

Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

[Robert]

Thank you Catherine for your kind comments…

 

Dear TSC Members,

 

If you guys think we should start with our SI under OOM project umbrella, 
certainly we will do that.

Let’s make a sub-project there for now and then see if and how we can fully 
integrate with OOM approach…

 

Is that acceptable to you Ladies and Gentlemen of TSC?

 

Thx

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Wednesday, October 17, 2018 12:16
To: onap-tsc@lists.onap.org
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Good morning Robert,

 

Thank you so much Robert for sharing this great contribution.

I agree with Stephen and Viswa.

It would be great if your activities are covered under the OOM project umbrella.

 

Mike Elliot – how do you feel about this?

 

Many thanks & regards

Catherine

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Robert
Sent: Wednesday, October 17, 2018 10:11 AM
To: onap-tsc@lists.onap.org
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Viswa,

 

Yes, agree, we should analyze requirements, impact and scope before deciding if 
we need new project or not.

Certainly, at least requirements sync would be necessary between the two (OOM 
and SI).

 

And yes, your understanding is right, currently working OOM deployment is 
necessary for development of SI Package Builder.

 

 

Btw, Michal Ptacek is participating in Integration project weekly calls, hope 
they will discuss it there…

 

 

 

Thx

/robert

 

 

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Viswanath Kumar Skand Priya via Lists.Onap.Org
Sent: Wednesday, October 17, 2018 09:21
To: onap-tsc
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

I second the idea of having standalone / offline mode of ONAP installation. It 
is indeed a requirement for us as we don't really enjoy the luxury of open 
internet even in our labs.

We have similar version of offline repos ( nexus, mvn, cache ) to minimise the 
dependency on external world and this SI is exactly what we would prefer.

 

However I would like to understand the need for starting a different project or 
placement under Integration project. As per my understanding, the proposed 
solution is still based on deploying ONAP via OOM, where the dependencies are 
downloaded one-time, cached and re-used within local ecosystem. In this case, 
why can't this project be annexed within OOM project's scope ? 

 

BR,

Viswa


 

 

 

 

Viswanath Kumar Skand Priya

Senior Architect

Technology, Architecture & Planning

 

 

 

On Wed, Oct 17, 2018 at 12:36 PM Robert  wrote:

Hi Steve,

 

We are open for suggestions…

IHMO, it would not hurt to have 2 different installers to give options for 
customers. i.e.: Openstack for example provides multiply installers.

 

Our approach is clearly targeting narrow carrier requirements, where 
deployments are predictable, repeatable and performed without any external 
connectivity, additionally giving customers comfort knowing exactly what is 
deployed.

 

thx

 

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Tuesday, October 16, 2018 20:51
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

Were you thinking of an additional project to capture this, or under the 
integration project?

 

BR,

 

Steve

 

From: onap-tsc@lists.onap.org  On Behalf Of 
r.re...@samsung.com
Sent: Tuesday 16 October 2018 16:28
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Beijing Offline SI Installer

 

Dear ONAP TSC Members,

 

During the ONAP Casablanca Developer Forum in Beijing we have promised to 
upstream our ONAP offline deployment tool.

 

As of yesterday, finally we did hold to our promise and published SI (Self 
Installer) in ONAP Supporting Tools wiki:

(the delay was due to development of additional the package builder which was 
initially done manually,  and the big self-extracting tarball was not suitable 
community – over 60GB)

 

 

 https://wiki.onap.org/display/DW/Beijing+OOM+ONAP+Offline+Deployment

 

the code is already merged in Integration project:

https://gerrit.onap.org/r/70479 

Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

[Alexis de Talhouet]

Hi,

When it comes to define new committers for a given project, what I’ve seen 
happening before, and it worked fairly well, is to have the PTL of the project 
start a committer election of a week or two.. Contributors to the project can 
self-nominate themselves, and once nomination period is over, committers vote 
whether each nominee can become committer by assessing their involvement in the 
project (e.g. meritocracy).
It is generally good to perform such committer election at the beginning of 
each release, as it allows to make sure we don’t have an un-healthy project 
with not enough committers, and also to recognize work that has been done 
during previous release. It is also good practice to refresh project’s 
committer list by making sure all committers are *active*.

In this case, I would suggest to run a committer election within the project. 
That way, who ever feels then can take on the committer role can candidate.
In the case no one show up, then it’s a different discussion. In the case ppl 
showing up don’t have any contribution to that specific project is up to the 
actual committers to decide what to do.
Once new committers have been elected within the project, PTL sends a mail to 
TSC asking to vote on whether new committers can be approved or not. Knowing 
the background / history of the project, TSC should be able to judge the 
candidate accordingly, making sure the project can be in a healthy state.

I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo 
should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li 
Zi and Sun QI vote, then PTL present to TSC with new potential committer(s), 
being, among other, Lv Bo. And we can have that as an TSC agenda item to 
discuss briefly whether we agree to have Lv Bo committer knowing the history.

Regards,
Alexis

> On Oct 16, 2018, at 10:03 PM, Kenny Paul  wrote:
> 
> Jimmy tried to pursue the correct channels to resolve the following issue but 
> he is stuck, so I'm formally escalating it to the TSC.
>
> Li Zi, (li.z...@zte.com.cn ) has been the primary 
> code contributor and Committer to the ESR sub project of AAI. She is no 
> longer participating in the ONAP project and security fixes are required for 
> the Casablanca Release.
> · Li Zi requested that Lv Bo (lv.bo...@zte.com.cn 
> ) be assigned as her replacement. This is not 
> allowed as it violates sections 3.1.1   Contributor 
> 
>  & 3.1.2   Committer 
> 
>  of the ONAP Technical Community document:
> Committers cannot be appointed, they must be meritocracy elected from the 
> pool of active Contributors to that project's repositories
> There is no record of Lv Bo ever making a contribution to the aai/esr-* 
> repositories.
> ( There have been numerous code contributions to a different ONAP project:  
> msb/service-mesh )
>
> The only Committers on the aai/esr-* repos are Li Zi, (li.z...@zte.com.cn 
> ) and Sun Qi (sun.qi...@zte.com.cn 
> ). Both were the only individuals listed on the 
> original project submission form 
> https://wiki.onap.org/pages/viewpage.action?pageId=5734948 
> 
>
> In terms of Committer responsibilities, Sun Qi has made +2 all of Li Zi's 
> contributions to aai/esr-*. Exclusively. There are no records of code reviews 
> being performed for any contributor other than Li Zi.  There is no record of 
> any code contributions being made by Sun Qi.
>
> Based upon the fact that self merges are not permitted, nothing can be done.
>
> The guidance the TSC needs to provide here is:
> Recommend that Jimmy work with Sun Qi to nominate one of the individuals 
> below to Committer status
> 
> Recommend that Jimmy pursue an exception to section 3.2.2.1 Adding 
> Committers 
> 
>  by filling out a Committer Promotion Request for Lv Bo, backed by 
> contributions made outside of the AAI project
> 
> Decide to take action based upon section 3.2.2.2 Adding Committers to 
> moribund projects 
> 
>  to appoint a Committer from the list below.
>
> Contributors to the aai/esr-* repos over the past 6 months:
> Submitter
> 
> Repository
> 
> Status
> 
> created
> 
> Summary
> 
> Bin Yang
> 
> aai/esr-server
> 
> NEW
> 
> 2018-09-03
> 
> Refactor cloud region registration logic
> 
> Gary Wu
> 
> aai/esr-server
> 
> NEW
> 
> 2018-08-24
> 
> Use managed guava version
> 

[onap-tsc] JIRA TSC-1 "Update TSC Chart to address how to hanlde a vacancey"

[Stephen Terrill]

Hi,

As TSC-1 jira is on the TSC agenda, a proposal has been uploaded.  While this 
and previous versions have been shared with the Task force, there is still 
ongoing discussion however I thought that it fair to share the latest proposal 
with the TSC members before the meeting this week.

It is attatched in the jira:
https://jira.onap.org/browse/TSC-1?src=confmacro

BR,

Steve


[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

[http://www.ericsson.com/current_campaign]

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer

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

View/Reply Online (#3922): https://lists.onap.org/g/onap-tsc/message/3922
Mute This Topic: https://lists.onap.org/mt/27378093/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: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

[Robert]

Hi Viswa,

 

Yes, agree, we should analyze requirements, impact and scope before deciding if 
we need new project or not.

Certainly, at least requirements sync would be necessary between the two (OOM 
and SI).

 

And yes, your understanding is right, currently working OOM deployment is 
necessary for development of SI Package Builder.

 

 

Btw, Michal Ptacek is participating in Integration project weekly calls, hope 
they will discuss it there…

 

 

 

Thx

/robert

 

 

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Viswanath Kumar Skand Priya via Lists.Onap.Org
Sent: Wednesday, October 17, 2018 09:21
To: onap-tsc
Cc: m.pta...@partner.samsung.com
Subject: Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

I second the idea of having standalone / offline mode of ONAP installation. It 
is indeed a requirement for us as we don't really enjoy the luxury of open 
internet even in our labs.

We have similar version of offline repos ( nexus, mvn, cache ) to minimise the 
dependency on external world and this SI is exactly what we would prefer.

 

However I would like to understand the need for starting a different project or 
placement under Integration project. As per my understanding, the proposed 
solution is still based on deploying ONAP via OOM, where the dependencies are 
downloaded one-time, cached and re-used within local ecosystem. In this case, 
why can't this project be annexed within OOM project's scope ? 

 

BR,

Viswa


 

  

 

Viswanath Kumar Skand Priya

Senior Architect

Technology, Architecture & Planning

 

 

 

On Wed, Oct 17, 2018 at 12:36 PM Robert  wrote:

Hi Steve,

 

We are open for suggestions…

IHMO, it would not hurt to have 2 different installers to give options for 
customers. i.e.: Openstack for example provides multiply installers.

 

Our approach is clearly targeting narrow carrier requirements, where 
deployments are predictable, repeatable and performed without any external 
connectivity, additionally giving customers comfort knowing exactly what is 
deployed.

 

thx

 

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Tuesday, October 16, 2018 20:51
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

Were you thinking of an additional project to capture this, or under the 
integration project?

 

BR,

 

Steve

 

From: onap-tsc@lists.onap.org  On Behalf Of 
r.re...@samsung.com
Sent: Tuesday 16 October 2018 16:28
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Beijing Offline SI Installer

 

Dear ONAP TSC Members,

 

During the ONAP Casablanca Developer Forum in Beijing we have promised to 
upstream our ONAP offline deployment tool.

 

As of yesterday, finally we did hold to our promise and published SI (Self 
Installer) in ONAP Supporting Tools wiki:

(the delay was due to development of additional the package builder which was 
initially done manually,  and the big self-extracting tarball was not suitable 
community – over 60GB)

 

 

 https://wiki.onap.org/display/DW/Beijing+OOM+ONAP+Offline+Deployment

 

the code is already merged in Integration project:

https://gerrit.onap.org/r/70479 

  Core of ONAP offline installer
https://gerrit.onap.org/r/70480 

  Add downloading scripts of onap artifacts
https://gerrit.onap.org/r/70481 

  Add ONAP specific artifacts lists for download

 

Note: current version of offline SI supports only ONAP Beijing release and is 
script based, for Casablanca we are migrating to Ansible and that will be also 
up streamed.

 

 

We would also like to propose to include similar functionality in ONAP as 
official project (we will follow the formal approval path).

Of 

Re: [E] Re: [onap-tsc] ONAP Beijing Offline SI Installer

[Viswanath Kumar Skand Priya via Lists.Onap.Org]

Hi Robert,

I second the idea of having standalone / offline mode of ONAP installation.
It is indeed a requirement for us as we don't really enjoy the luxury of
open internet even in our labs.
We have similar version of offline repos ( nexus, mvn, cache ) to minimise
the dependency on external world and this SI is exactly what we would
prefer.

However I would like to understand the need for starting a different
project or placement under Integration project. As per my understanding,
the proposed solution is still based on deploying ONAP via OOM, where the
dependencies are downloaded one-time, cached and re-used within local
ecosystem. In this case, why can't this project be annexed within OOM
project's scope ?

BR,
Viswa



Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Wed, Oct 17, 2018 at 12:36 PM Robert  wrote:

> Hi Steve,
>
>
>
> We are open for suggestions…
>
> IHMO, it would not hurt to have 2 different installers to give options for
> customers. i.e.: Openstack for example provides multiply installers.
>
>
>
> Our approach is clearly targeting narrow carrier requirements, where
> deployments are predictable, repeatable and performed without any external
> connectivity, additionally giving customers comfort knowing exactly what is
> deployed.
>
>
>
> thx
>
>
>
> /robert
>
>
>
> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *On
> Behalf Of *Stephen Terrill
> *Sent:* Tuesday, October 16, 2018 20:51
> *To:* onap-tsc@lists.onap.org
> *Subject:* Re: [onap-tsc] ONAP Beijing Offline SI Installer
>
>
>
> Hi Robert,
>
>
>
> Were you thinking of an additional project to capture this, or under the
> integration project?
>
>
>
> BR,
>
>
>
> Steve
>
>
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *
> r.re...@samsung.com
> *Sent:* Tuesday 16 October 2018 16:28
> *To:* onap-tsc@lists.onap.org
> *Subject:* [onap-tsc] ONAP Beijing Offline SI Installer
>
>
>
> Dear ONAP TSC Members,
>
>
>
> During the ONAP Casablanca Developer Forum in Beijing we have promised to
> upstream our ONAP offline deployment tool.
>
>
>
> As of yesterday, finally we did hold to our promise and published SI (Self
> Installer) in ONAP Supporting Tools wiki:
>
> (the delay was due to development of additional the package builder which
> was initially done manually,  and the big self-extracting tarball was not
> suitable community – over 60GB)
>
>
>
> https://wiki.onap.org/display/DW/Beijing+OOM+ONAP+Offline+Deployment
> 
>
>
>
> the code is already merged in Integration project:
>
> https://gerrit.onap.org/r/70479
> 
> Core of ONAP offline installer
> https://gerrit.onap.org/r/70480
> 
> Add downloading scripts of onap artifacts
> https://gerrit.onap.org/r/70481
> 
> Add ONAP specific artifacts lists for download
>
>
>
> Note: current version of offline SI supports only ONAP Beijing release and
> is script based, for Casablanca we are migrating to Ansible and that will
> be also up streamed.
>
>
>
>
>
> We would also like to propose to include similar functionality in ONAP as
> official project (we will follow the formal approval path).
>
> Of course current implementation is not suitable for such, but we are
> planning to submit proposal for ONAP Offline Installer prior Dublin Release
> Developers Forum to be in time for your review (targeting El Alto
> release).  During the forum, we could also answer all the questions related
> and listen to your feedback.
>
>
>
>
>
> In the meantime if you do not mind, we’ll open confluence page to start
> gathering industry and community requirements toward such solution.
>
>
>
>
>
> Thank you very much
>
>
>
> /robert
>
>
>
>
> 
>

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

View/Reply Online (#3920): 

Re: [onap-tsc] ONAP Beijing Offline SI Installer

[Robert]

Hi Steve,

 

We are open for suggestions…

IHMO, it would not hurt to have 2 different installers to give options for 
customers. i.e.: Openstack for example provides multiply installers.

 

Our approach is clearly targeting narrow carrier requirements, where 
deployments are predictable, repeatable and performed without any external 
connectivity, additionally giving customers comfort knowing exactly what is 
deployed.

 

thx

 

/robert

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Tuesday, October 16, 2018 20:51
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP Beijing Offline SI Installer

 

Hi Robert,

 

Were you thinking of an additional project to capture this, or under the 
integration project?

 

BR,

 

Steve

 

From: onap-tsc@lists.onap.org  On Behalf Of 
r.re...@samsung.com
Sent: Tuesday 16 October 2018 16:28
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Beijing Offline SI Installer

 

Dear ONAP TSC Members,

 

During the ONAP Casablanca Developer Forum in Beijing we have promised to 
upstream our ONAP offline deployment tool.

 

As of yesterday, finally we did hold to our promise and published SI (Self 
Installer) in ONAP Supporting Tools wiki:

(the delay was due to development of additional the package builder which was 
initially done manually,  and the big self-extracting tarball was not suitable 
community – over 60GB)

 

  
https://wiki.onap.org/display/DW/Beijing+OOM+ONAP+Offline+Deployment

 

the code is already merged in Integration project:

https://gerrit.onap.org/r/70479 Core of ONAP offline installer
https://gerrit.onap.org/r/70480 Add downloading scripts of onap artifacts
https://gerrit.onap.org/r/70481 Add ONAP specific artifacts lists for download

 

Note: current version of offline SI supports only ONAP Beijing release and is 
script based, for Casablanca we are migrating to Ansible and that will be also 
up streamed.

 

 

We would also like to propose to include similar functionality in ONAP as 
official project (we will follow the formal approval path).

Of course current implementation is not suitable for such, but we are planning 
to submit proposal for ONAP Offline Installer prior Dublin Release Developers 
Forum to be in time for your review (targeting El Alto release).  During the 
forum, we could also answer all the questions related and listen to your 
feedback.

 

 

In the meantime if you do not mind, we’ll open confluence page to start 
gathering industry and community requirements toward such solution.

 

 

Thank you very much

 

/robert 




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

View/Reply Online (#3919): https://lists.onap.org/g/onap-tsc/message/3919
Mute This Topic: https://lists.onap.org/mt/27369863/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]
-=-=-=-=-=-=-=-=-=-=-=-