Re: [onap-discuss] Service registration with MSB //Re: [integration] ONAP installation via Heat

[PLATANIA, MARCO (MARCO)]

Hi Huabing,

Your assumption is correct. How do you want us to pass these variables to the 
container? As part of the docker run instruction?

Also, which container should have access to them?

Thanks,
Marco




On Wed, Sep 20, 2017 at 8:57 PM -0400, "zhao.huab...@zte.com.cn" 
> wrote:


Hi Marco,


So I assume these environment variables can be accessed in the MSB VM?


That should work.


Thanks,

Huabing


Original Mail
Sender:  ;
To: zhaohuabing10201488; ;
CC:  ;
Date: 2017/09/20 21:14
Subject: Re: Service registration with MSB //Re: [onap-discuss] [integration] 
ONAP installation via Heat

Hi Huabing,

Yes, that’s possible. We’ll create a file with all the components and their IP 
addresses. I was thinking about something like this:

export AAI_IP_ADDRESS=10.0.1.1
export DCAE_IP_ADDRESS=10.0.4.1
export POLICY_IP_ADDRESS=10.0.7.1
etc.

What do you think?

Thanks,
Marco

From: "zhao.huab...@zte.com.cn" 
Date: Wednesday, September 20, 2017 at 4:43 AM
To: "PLATANIA, MARCO (MARCO)" , 
"helen.c...@huawei.com" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Service registration with MSB //Re: [onap-discuss] [integration] ONAP 
installation via Heat


Hi Marco,



As we discussed in the meeting, MSB needs to know the VM IP addresses of all 
the onap components so MSB can register the services for them.

Can we pass that information to MSB VM as environment variables?



@Helen,

According to what I heard in this meeting, VFC, Multi-VIM, MSB, UUI will be 
deployed inside one VM? If that's true, MSB will assume these components' IP 
address is the same as MSB itself when registering the  services.



Thanks,

Huabing
Original Mail
Sender:  ;
To:  ; ;
Date: 2017/09/20 07:24
Subject: Re: [onap-discuss] [integration] ONAP installation via Heat


Did. :)

Regards,

Helen Chen

From:  on behalf of "PLATANIA, MARCO 
(MARCO)" 
Date: Tuesday, September 19, 2017 at 3:21 PM
To: onap-discuss 
Subject: [onap-discuss] [integration] ONAP installation via Heat

All,

To support ONAP teams whose components aren’t in Heat yet, I created a wiki 
page that explains how to add new components to the Heat template and  what 
ONAP teams should do to help us during this process: 
https://wiki.onap.org/display/DW/How+to+add+a+new+ONAP+component+to+Heat

I know Helen will schedule a meeting with interested teams soon.

Thanks,
Marco






___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Service registration with MSB //Re: [integration] ONAP installation via Heat

[zhao.huabing]

Hi Marco,




So I assume these environment variables can be accessed in the MSB VM?





That should work.




Thanks,

Huabing










Original Mail



Sender:  
To: zhaohuabing10201488 
CC:  
Date: 2017/09/20 21:14
Subject: Re: Service registration with MSB //Re: [onap-discuss] [integration] 
ONAP installation via Heat 







Hi Huabing,


 


Yes, that’s possible. We’ll create a file with all the components and their IP 
addresses. I was thinking about something like this:


 


export AAI_IP_ADDRESS=10.0.1.1


export DCAE_IP_ADDRESS=10.0.4.1


export POLICY_IP_ADDRESS=10.0.7.1


etc.


 


What do you think?


 


Thanks,


Marco


 



From: "zhao.huab...@zte.com.cn" 
 Date: Wednesday, September 20, 2017 at 4:43 AM
 To: "PLATANIA, MARCO (MARCO)" , 
"helen.c...@huawei.com" 
 Cc: "onap-discuss@lists.onap.org" 
 Subject: Service registration with MSB //Re: [onap-discuss] [integration] ONAP 
installation via Heat 



 


Hi Marco,

 

As we discussed in the meeting, MSB needs to know the VM IP addresses of all 
the onap components so MSB can register the services for them.

Can we pass that information to MSB VM as environment variables?

 

@Helen,

According to what I heard in this meeting, VFC, Multi-VIM, MSB, UUI will be 
deployed inside one VM? If that's true, MSB will assume these components' IP 
address is the same as MSB itself when registering the  services.

 

Thanks,

Huabing


Original Mail



Sender:  



To:   



Date: 2017/09/20 07:24



Subject: Re: [onap-discuss] [integration] ONAP installation via Heat




 


Did. J


 


Regards,


 



Helen Chen


 



From:  on behalf of "PLATANIA, MARCO 
(MARCO)" 
 Date: Tuesday, September 19, 2017 at 3:21 PM
 To: onap-discuss 
 Subject: [onap-discuss] [integration] ONAP installation via Heat



 


All,


 


To support ONAP teams whose components aren’t in Heat yet, I created a wiki 
page that explains how to add new components to the Heat template and  what 
ONAP teams should do to help us during this process: 
https://wiki.onap.org/display/DW/How+to+add+a+new+ONAP+component+to+Heat 


 


I know Helen will schedule a meeting with interested teams soon.


 


Thanks,


Marco___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP Docker(s)?

[fu.guangrong]

Thanks for your information, Varun.




I'll be attending the DMaaP demo meeting and hope that we can get a better 
understanding on how to utilize DMaaP then.




Regards,

Guangrong



















Original Mail



Sender:  
To: fuguangrong10144542
CC: pengcongcong612843tianshiwei10223543  

Date: 2017/09/21 02:39
Subject: RE: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?







Guangrong,


In DMaap MR, port 3904 is used for http and port 3905 is used for https.


 


 


 


From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn] 
 Sent: Wednesday, September 13, 2017 7:54 PM
 To: GUDISENA, VARUNESHWAR 
 Cc: peng.congc...@zte.com.cn tian.shi...@zte.com.cn 
onap-discuss@lists.onap.org KOYA, RAMPRASAD  
fu.guangr...@zte.com.cn
 Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?


 

Sorry for the typo, the zoom ID is 66.

 

 

 

 



Original Mail



Sender: FuGuangRong10144542



To:  



CC: peng//cong/cong612843tianshiwei10223543  
FuGuangRong10144542



Date: 2017/09/14 08:42



Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?




 

Hi Varun,

 

Are you still there? The call on 66888 is available now. I'm in the meeting 
room, waiting for you. :D

 

Guangrong

 

 

 

 


 



 



Sender: FuGuangRong10144542



To:  



CC: peng//cong/cong612843tianshiwei10223543  




Date: 2017/09/14 08:24



Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?




 

Hi Varun,

 

The zoom ID is 66. I'm on it right now.

 

Regards,

Guangrong

 

 



 



Sender:  



To: FuGuangRong10144542



CC: peng//cong/cong612843tianshiwei10223543  




Date: 2017/09/14 08:12



Subject: RE: 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?




 


I downloaded kafka file manually and used your Dockerfile. Kakfa container is 
not starting. Do you want  to join for a quick call. If yes, send me zoom 
invitation.


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUDISENA, VARUNESHWAR
 Sent: Wednesday, September 13, 2017 6:45 PM
 To: fu.guangr...@zte.com.cn
 Cc: peng.congc...@zte.com.cn tian.shi...@zte.com.cn 
onap-discuss@lists.onap.org KOYA, RAMPRASAD 
 Subject: Re: [onap-discuss] 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?




 


***Security Advisory: This Message Originated Outside of AT ***
 Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


Working on it now.


 


 


From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn] 
 Sent: Wednesday, September 13, 2017 5:36 PM
 To: fu.guangr...@zte.com.cn
 Cc: tian.shi...@zte.com.cn peng.congc...@zte.com.cn KOYA, RAMPRASAD 
 GUDISENA, VARUNESHWAR  
onap-discuss@lists.onap.org
 Subject: 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?


 


Greetings Varun,
 
 Is there any progress on this?
 
 Regards,
 Guangrong
 
 


原始邮件



发件人:付光荣10144542 



收件人:vg4...@att.com 



抄送人:田世伟10223543彭聪聪612843KOYA,   
ramprasadonap-disc...@lists.onap.org付光荣10144542 



日期:2017-09-13 15:16:28



主题:Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP Docker(s)? 



 

Hi Varun,

 

Attached is the Dockerfile we used to build the kafka docker. Please download 
kafka_2.9.2-0.8.1.1.tgz manually into the docker-compose directory and copy the 
Dockerfile into this directory as well.

 

I'm not sure whether it is the problem of the kafka binary package we 
downloaded from the apache website. I've tried to download it again. The same 
error occurred over and over when I try to start it. If the docker you build 
using the Dockerfile attached   works, I believe there must be something wrong 
in the MsgRtrApis.properties file. If so, I suggest you send the configuration 
file back to me in order that I could compare with that which is on my local 
machine.

 

Thanks in advance.

Guangrong

 

 

 


Sender: FuGuangRong10144542



To:  



CC: tianshiwei10223543peng//cong/cong612843  




Date: 2017/09/13 08:10



Subject: Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?




 

Varun,

 

I set up a call just now. It'll start from 9:30 am, Sep. 13 (CST). The 
invitation has been sent to your mailbox, please check it for more details for 
the call.

 

Thanks.

Guangrong

 

 

 

 


 



 



Sender:  



To: FuGuangRong10144542



CC: 

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[TALASILA, MANOOP (MANOOP)]

Thanks Jess. Portal-sdk changes are merged now.

Manoop

On 9/20/17, 7:46 PM, "onap-discuss-boun...@lists.onap.org on behalf of Jessica 
Wagantall via RT"  wrote:

Here is the update:

- Common Logging Library - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14009_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=5Mw9HX3F6_6S_30YMJjXDTWd7KgBVWFulQG2oVXF1Uw=
  - PTLs need merge
- Distribution - Addressed
- DMaaP Bus Controller UI (parent) - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_dmaap_job_dmaap-2Dbuscontroller-2Dmaster-2Drelease-2Dversion-2Djava-2Ddaily_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=wFQl3yO7X3Ow7AnCERu9a-9nId2qcoirOGrAzYeEEsc=
  - PTLs need to fix their Jenkins job
- Ecomp Portal SDK Project (parent) - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13249_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=iWGMTrXrnCMuJBmAGu0yyP4DclWdVp4ZUeFEH5BhAGY=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14011_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=Nw_EoyZzU2D95YgXBTo474NG38ufZkCrRsSwNw4fbjo=
  - PTL need to merge
- modeling/toscaparsers/nfvparser - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13247_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=VME9_Q9hmrPibfPYhdWcNPLJ8MtXtQT1oa-xRBqkZFk=
  - PTLs to fix the Jenkins error
- inventory-api - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13985_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=YQ2YSc5vCxNlemvnwZK4lm-b_bykSrqoV7N7RidIiic=
  - PTLs need to merge
- MSO main project - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13983_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=AlCmt-AXB5iyMX9OLff91zRl_EWZ0WTI2JtWGX-KEg8=
  - PTLs need to merge
- OpenStack Java SDK - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13979_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=m7vtt7Lltfle9d-fahDVuO52cQkSBBxY89Uv4NymEXs=
  - PTLs need to merge
- Parent POMs - addressed
- SDN-C Adaptors - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14005_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=zcirvdmr9UYhF3R2hGorO_cWAmZtyEilgvG4aEj1FQs=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14007_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=04SvZUgukqg42H06UWrcurO3Ux0NC_z-gMd6K287w7E=
  - PTLs need merge
- SDN-C Core Components - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13991_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=ef07_lbBXZannqFiP_QhHBBnMoA9UTCmEre2O0IxvEw=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13995_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=i5Jwwxl4Q13yeyE1wM6AFaBG7gXWKck1m98sSXXNYBk=
  - PTLs need to merge 
- SDN-C Core Components - rootpom - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13989_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=BlPLjV3PL_yytFTXR4zmif9fwOtXhr6k3BdyxYH43gY=
  - PTLs need to merge
- SDN-C Java Plugins - addressed
- SDN-C Northbound APIs - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13997_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=AH7ciH_e_mZJGMN7pgEXj1J8fY0D4DskqUZoGikFoeQ=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13999_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=tRVSqqc04TV_-1CmfL1IT9zRomMeEqF0fyTB1gHuTI4=
  - PTLs need to merge
- SDN-C OAM - 

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[talas...@research.att.com via RT]

Thanks Jess. Portal-sdk changes are merged now.

Manoop

On 9/20/17, 7:46 PM, "onap-discuss-boun...@lists.onap.org on behalf of Jessica 
Wagantall via RT"  wrote:

Here is the update:

- Common Logging Library - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14009_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=5Mw9HX3F6_6S_30YMJjXDTWd7KgBVWFulQG2oVXF1Uw=
  - PTLs need merge
- Distribution - Addressed
- DMaaP Bus Controller UI (parent) - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_dmaap_job_dmaap-2Dbuscontroller-2Dmaster-2Drelease-2Dversion-2Djava-2Ddaily_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=wFQl3yO7X3Ow7AnCERu9a-9nId2qcoirOGrAzYeEEsc=
  - PTLs need to fix their Jenkins job
- Ecomp Portal SDK Project (parent) - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13249_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=iWGMTrXrnCMuJBmAGu0yyP4DclWdVp4ZUeFEH5BhAGY=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14011_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=Nw_EoyZzU2D95YgXBTo474NG38ufZkCrRsSwNw4fbjo=
  - PTL need to merge
- modeling/toscaparsers/nfvparser - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13247_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=VME9_Q9hmrPibfPYhdWcNPLJ8MtXtQT1oa-xRBqkZFk=
  - PTLs to fix the Jenkins error
- inventory-api - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13985_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=YQ2YSc5vCxNlemvnwZK4lm-b_bykSrqoV7N7RidIiic=
  - PTLs need to merge
- MSO main project - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13983_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=AlCmt-AXB5iyMX9OLff91zRl_EWZ0WTI2JtWGX-KEg8=
  - PTLs need to merge
- OpenStack Java SDK - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13979_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=m7vtt7Lltfle9d-fahDVuO52cQkSBBxY89Uv4NymEXs=
  - PTLs need to merge
- Parent POMs - addressed
- SDN-C Adaptors - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14005_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=zcirvdmr9UYhF3R2hGorO_cWAmZtyEilgvG4aEj1FQs=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_14007_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=04SvZUgukqg42H06UWrcurO3Ux0NC_z-gMd6K287w7E=
  - PTLs need merge
- SDN-C Core Components - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13991_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=ef07_lbBXZannqFiP_QhHBBnMoA9UTCmEre2O0IxvEw=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13995_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=i5Jwwxl4Q13yeyE1wM6AFaBG7gXWKck1m98sSXXNYBk=
  - PTLs need to merge 
- SDN-C Core Components - rootpom - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13989_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=BlPLjV3PL_yytFTXR4zmif9fwOtXhr6k3BdyxYH43gY=
  - PTLs need to merge
- SDN-C Java Plugins - addressed
- SDN-C Northbound APIs - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13997_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=AH7ciH_e_mZJGMN7pgEXj1J8fY0D4DskqUZoGikFoeQ=
  and 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_13999_=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=dJTUTaVTB09fzfscWrwGdbn3M3-5dG4pp2PCH6-6RYg=tRVSqqc04TV_-1CmfL1IT9zRomMeEqF0fyTB1gHuTI4=
  - PTLs need to merge
- SDN-C OAM - 

[onap-discuss] [integration]OpenStack version support discussion

[Yunxia Chen]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="JI, LUSHEN
 G (LUSHENG)":MAILTO:l...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Gooch, Ste
 phen":MAILTO:stephen.go...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang Xu (Y
 ang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="ROSE, DANI
 EL V":MAILTO:dr6...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="LEFEVRE, C
 ATHERINE":MAILTO:cl6...@intl.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='chinamobi
 le':MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="PLATANIA, 
 MARCO  (MARCO)":MAILTO:plata...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Kang Xi:MA
 ILTO:kang...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, September 21\, 2017 8:00 AM-9:0
 0 AM. (UTC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/446
 666\n\n*~*~*~*~*~*~*~*~*~*\n\nA little bit context:\n\nAt current inte
 gration lab\, it has OpenStack Newton\, however\,\n\n“The version of the
  Cloudify OpenStack plugin that DACEGEN2 uses is not compatible with the I
 dentity API that is current provided by the tenant for DCAE\, which is v3.
   The compatible Identity API version is v2.0.  For example https://${host
 name}:5000/v2.0.\n\nCan the v2.0 
 Identity API be added? “\n\nAnd\n\n“https://review.openstack.org/#/c/2
 51530/  Keystone v2.0 was deprec
 ated after Open Stack Liberty.\n\n“.\n\n\n\nFor this meeting\, we’d li
 ke to bring in related stakeholders together to get a solution for this:\n
 \n   1.   Should DCAE team upgrade cloudify openstack plugin\n\n  
 Or\n\n   2.Pick an earlier Openstack version to support it?\n\nAny
  special requirement from lab or ONAP to support specific version? And wha
 t’s the effort?\n\n\n\n\n\nJoin from PC\, Mac\, Linux\, iOS or Android: 
 https://zoom.us/j/44\nOr iPhone one-tap (US Toll): +16465588656\,
 44# or +14086380968\,44#\nOr Telephone:\nDial: +1 646 558 
 8656 (US Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 44  8\nIn
 ternational numbers available: https://zoom.us/zoomconference?m=CqsAwHx4CS
 yRanCfPHKBvf6Vslgcsn86\n\n\n
SUMMARY;LANGUAGE=en-US:[integration]OpenStack version support discussion
DTSTART;TZID=Pacific Standard Time:20170921T08
DTEND;TZID=Pacific Standard Time:20170921T09
UID:3FA7B0FE-2783-462E-8375-3996EA4A3D20
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170920T235208Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115610215
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT

[onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Jessica Wagantall via RT]

Here is the update:

- Common Logging Library - https://gerrit.onap.org/r/#/c/14009/ - PTLs need 
merge
- Distribution - Addressed
- DMaaP Bus Controller UI (parent) - 
https://jenkins.onap.org/view/dmaap/job/dmaap-buscontroller-master-release-version-java-daily/
 - PTLs need to fix their Jenkins job
- Ecomp Portal SDK Project (parent) - https://gerrit.onap.org/r/#/c/13249/ and 
https://gerrit.onap.org/r/#/c/14011/ - PTL need to merge
- modeling/toscaparsers/nfvparser - https://gerrit.onap.org/r/#/c/13247/ - PTLs 
to fix the Jenkins error
- inventory-api - https://gerrit.onap.org/r/#/c/13985/ - PTLs need to merge
- MSO main project - https://gerrit.onap.org/r/#/c/13983/ - PTLs need to merge
- OpenStack Java SDK - https://gerrit.onap.org/r/#/c/13979/ - PTLs need to merge
- Parent POMs - addressed
- SDN-C Adaptors - https://gerrit.onap.org/r/#/c/14005/ and 
https://gerrit.onap.org/r/#/c/14007/ - PTLs need merge
- SDN-C Core Components - https://gerrit.onap.org/r/#/c/13991/ and 
https://gerrit.onap.org/r/#/c/13995/ - PTLs need to merge 
- SDN-C Core Components - rootpom - https://gerrit.onap.org/r/#/c/13989/ - PTLs 
need to merge
- SDN-C Java Plugins - addressed
- SDN-C Northbound APIs - https://gerrit.onap.org/r/#/c/13997/ and 
https://gerrit.onap.org/r/#/c/13999/ - PTLs need to merge
- SDN-C OAM - https://gerrit.onap.org/r/#/c/14001/ and 
https://gerrit.onap.org/r/#/c/14003/ - PTL need to merge
- VID Parent Project - addressed

Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Thanks Jess for the update. Glad to hear the news. I trust you , we are all 
getting a clean house here +1. :)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 20, 2017 4:26 PM
To: Gildas Lanilis 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Dear Gildas, 

I am noticing that most of these leftovers are due to the fact that we have to 
also change the names in the pom files for the release branches that can be 
causing these ugly names. 

I am almost done uploading all the changes and giving you a new update.. Will 
send it very shortly..
Just wanted to let you know that the delay is due to extra work actually needed.

Thanks!
Jess

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis]

Thanks Jess for the update. Glad to hear the news. I trust you , we are all 
getting a clean house here +1. :)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 20, 2017 4:26 PM
To: Gildas Lanilis 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Dear Gildas, 

I am noticing that most of these leftovers are due to the fact that we have to 
also change the names in the pom files for the release branches that can be 
causing these ugly names. 

I am almost done uploading all the changes and giving you a new update.. Will 
send it very shortly..
Just wanted to let you know that the delay is due to extra work actually needed.

Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[JI, LUSHENG (LUSHENG)]

Both time blocks work for me.

Lusheng


Sent via the Samsung Galaxy S7, an AT 4G LTE smartphone


 Original message 
From: Yunxia Chen 
Date: 9/20/17 7:27 PM (GMT-05:00)
To: "JI, LUSHENG (LUSHENG)" , "Gooch, Stephen" 
, "Yang Xu (Yang, Fixed Network)" 

Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

I have time now until 10:00pm PDT today or after 8:00am PDT tomorrow. How about 
Lusheng, Stephen and Yang?

Regards,

Helen Chen

From: "JI, LUSHENG (LUSHENG)" 
Date: Wednesday, September 20, 2017 at 3:50 PM
To: "Gooch, Stephen" , "Yang Xu (Yang, Fixed 
Network)" , Helen Chen 00725961 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

@Stephen,

Thanks.

@Helen,
@Yang,

Could this be arranged as soon as possible?  We are blocked by this currently.  
Any project needs Ocata for R1?

Thanks,
Lusheng


From: "Gooch, Stephen" 
Date: Wednesday, September 20, 2017 at 5:54 PM
To: "JI, LUSHENG (LUSHENG)" , "Yang Xu (Yang, Fixed 
Network)" , Yunxia Chen 
Cc: "onap-discuss@lists.onap.org" 
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

To support Keystone v2, Ocata will also need to be removed from release 1 
support list.Is there an integration call scheduled to discuss this topic 
and the effects that may waterfall from it?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 17:31
To: Yang Xu (Yang, Fixed Network); Yunxia Chen; Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

That is the setup in our other testing labs too, both v2.0 and v3 are 
supported.  The new developer’s lab only supports v3.
We will move to v3 too.  But with R1 timeline it will be very difficult.

Thanks,
Lusheng


From: "Yang Xu (Yang, Fixed Network)" 
>
Date: Wednesday, September 20, 2017 at 5:04 PM
To: Yunxia Chen >, "Gooch, 
Stephen" >, 
"JI, LUSHENG (LUSHENG)" >
Cc: "onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

In WindRiver Mitaka, even though the identity end point is v3, we used v2 to do 
the testing. Also Mitaka provides two versions of Openstack RC file, one is 
them uses identity v2.

Thanks,
-Yang

From: Yunxia Chen
Sent: Wednesday, September 20, 2017 4:01 PM
To: Gooch, Stephen; JI, LUSHENG (LUSHENG); Yang Xu (Yang, Fixed Network)
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From: 
>
 on behalf of "Gooch, Stephen" 
>
Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/
  Keystone v2.0 was deprecated after Open Stack Liberty. I am assuming the 
Cloudify plugin was previously tested on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 

Re: [onap-discuss] sdnc development environment setup issue

[TIMONEY, DAN]

Ramu,

That error you were seeing was one of the errors associated with the change 
from mysql to mariadb JDBC connectors.  I think if you pull a fresh copy, you 
should have better luck now.

Another option, which is what I use, is to use docker-compose to pull down and 
start up the docker containers.

I attached the docker-compose.yml that I use on my laptop for testing, which is 
a slightly modified version of the one in sdnc/oam/installation/src/main/yaml 
in Gerrit.

Assuming you already have docker and docker-compose installed in your 
environment, you should be able to copy that docker-compose.yml to a local 
directory, and then from that directory type this to start up the SDNC docker 
containers:

docker-compose pull
  docker-compose up –d

To watch the container logs so you can see them come up, you can type 
“docker-compose logs –f”

Once the containers are up, you can login to dgbuilder at http://localhost:3000


Hope this helps!
Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: Ramu n 
Date: Wednesday, September 20, 2017 at 8:57 AM
To: "onap-discuss@lists.onap.org" , 
"onap-s...@lists.onap.org" 
Cc: "TIMONEY, DAN" , "marcus.willi...@intel.com" 
, Kalyankumar Asangi 
Subject: [onap-discuss] sdnc development environment setup issue

Hi,

Can anyone suggest which method can be fallowed to setup SDNC development 
environment, I could find below two options..


  1.  
https://wiki.onap.org/display/DW/Install+Directed+Graph+Builder+on+Ubuntu+Desktop


  1.  
https://git.onap.org/integration/tree/bootstrap/vagrant-onap

I have tried option-2, but getting below error.. Can anyone help me what could 
be the reason.

2017-09-20 07:13:58,423 | INFO  |  | Creating blueprint container for bundle 
org.onap.ccsdk.sli.core.dblib_0.1.2.SNAPSHOT [290] with paths 
[bundleentry://290.fwk161960012/org/opendaylight/blueprint/dblib-blueprint.xml]
2017-09-20 07:13:58,423 | INFO  |  | Creating blueprint container for bundle 
org.onap.ccsdk.sli.core.dblib_0.1.2.SNAPSHOT [290] with paths 
[bundleentry://290.fwk161960012/org/opendaylight/blueprint/dblib-blueprint.xml]
2017-09-20 07:13:58,437 | INFO  |  | Using property file (1) from environment 
variable /opt/onap/sdnc/data/properties/dblib.properties
2017-09-20 07:13:58,437 | INFO  |  | Using property file (1) from environment 
variable /opt/onap/sdnc/data/properties/dblib.properties
2017-09-20 07:13:58,630 | INFO  |  | Recovery Mode disabled
2017-09-20 07:13:58,630 | INFO  |  | Recovery Mode disabled
2017-09-20 07:13:58,734 | ERROR |  | AS_CONF_ERROR: Failed to initialize 
MySQLCachedDataSource . Reason: com.mysql.jdbc.Driver
2017-09-20 07:13:58,734 | ERROR |  | AS_CONF_ERROR: Failed to initialize 
MySQLCachedDataSource . Reason: com.mysql.jdbc.Driver
2017-09-20 07:13:58,783 | ERROR |  | SQL DataSource  test failed. 
Cause : null
2017-09-20 07:13:58,783 | ERROR |  | SQL DataSource  test failed. 
Cause : null
2017-09-20 07:13:58,785 | ERROR |  |
java.lang.NullPointerException
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.getConnection(CachedDataSource.java:97)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.getData(CachedDataSource.java:108)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.isSlave(CachedDataSource.java:543)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.DBResourceManager$DataSourceTester.run(DBResourceManager.java:233)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
2017-09-20 07:13:58,785 | ERROR |  |


Thanks,
Ramu N


docker-compose.yml
Description: docker-compose.yml
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[Yunxia Chen]

I have time now until 10:00pm PDT today or after 8:00am PDT tomorrow. How about 
Lusheng, Stephen and Yang?

Regards,

Helen Chen

From: "JI, LUSHENG (LUSHENG)" 
Date: Wednesday, September 20, 2017 at 3:50 PM
To: "Gooch, Stephen" , "Yang Xu (Yang, Fixed 
Network)" , Helen Chen 00725961 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

@Stephen,

Thanks.

@Helen,
@Yang,

Could this be arranged as soon as possible?  We are blocked by this currently.  
Any project needs Ocata for R1?

Thanks,
Lusheng


From: "Gooch, Stephen" 
Date: Wednesday, September 20, 2017 at 5:54 PM
To: "JI, LUSHENG (LUSHENG)" , "Yang Xu (Yang, Fixed 
Network)" , Yunxia Chen 
Cc: "onap-discuss@lists.onap.org" 
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

To support Keystone v2, Ocata will also need to be removed from release 1 
support list.Is there an integration call scheduled to discuss this topic 
and the effects that may waterfall from it?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 17:31
To: Yang Xu (Yang, Fixed Network); Yunxia Chen; Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

That is the setup in our other testing labs too, both v2.0 and v3 are 
supported.  The new developer’s lab only supports v3.
We will move to v3 too.  But with R1 timeline it will be very difficult.

Thanks,
Lusheng


From: "Yang Xu (Yang, Fixed Network)" 
>
Date: Wednesday, September 20, 2017 at 5:04 PM
To: Yunxia Chen >, "Gooch, 
Stephen" >, 
"JI, LUSHENG (LUSHENG)" >
Cc: "onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

In WindRiver Mitaka, even though the identity end point is v3, we used v2 to do 
the testing. Also Mitaka provides two versions of Openstack RC file, one is 
them uses identity v2.

Thanks,
-Yang

From: Yunxia Chen
Sent: Wednesday, September 20, 2017 4:01 PM
To: Gooch, Stephen; JI, LUSHENG (LUSHENG); Yang Xu (Yang, Fixed Network)
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From: 
>
 on behalf of "Gooch, Stephen" 
>
Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/
  Keystone v2.0 was deprecated after Open Stack Liberty. I am assuming the 
Cloudify plugin was previously tested on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira 

[onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Jessica Wagantall via RT]

Dear Gildas, 

I am noticing that most of these leftovers are due to the fact that we have to 
also change the names in the pom files for the release branches that can be 
causing these ugly names. 

I am almost done uploading all the changes and giving you a new update.. Will 
send it very shortly..
Just wanted to let you know that the delay is due to extra work actually needed.

Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[JI, LUSHENG (LUSHENG)]

@Stephen,

Thanks.

@Helen,
@Yang,

Could this be arranged as soon as possible?  We are blocked by this currently.  
Any project needs Ocata for R1?

Thanks,
Lusheng


From: "Gooch, Stephen" 
Date: Wednesday, September 20, 2017 at 5:54 PM
To: "JI, LUSHENG (LUSHENG)" , "Yang Xu (Yang, Fixed 
Network)" , Yunxia Chen 
Cc: "onap-discuss@lists.onap.org" 
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

To support Keystone v2, Ocata will also need to be removed from release 1 
support list.Is there an integration call scheduled to discuss this topic 
and the effects that may waterfall from it?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 17:31
To: Yang Xu (Yang, Fixed Network); Yunxia Chen; Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

That is the setup in our other testing labs too, both v2.0 and v3 are 
supported.  The new developer’s lab only supports v3.
We will move to v3 too.  But with R1 timeline it will be very difficult.

Thanks,
Lusheng


From: "Yang Xu (Yang, Fixed Network)" 
>
Date: Wednesday, September 20, 2017 at 5:04 PM
To: Yunxia Chen >, "Gooch, 
Stephen" >, 
"JI, LUSHENG (LUSHENG)" >
Cc: "onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

In WindRiver Mitaka, even though the identity end point is v3, we used v2 to do 
the testing. Also Mitaka provides two versions of Openstack RC file, one is 
them uses identity v2.

Thanks,
-Yang

From: Yunxia Chen
Sent: Wednesday, September 20, 2017 4:01 PM
To: Gooch, Stephen; JI, LUSHENG (LUSHENG); Yang Xu (Yang, Fixed Network)
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From: 
>
 on behalf of "Gooch, Stephen" 
>
Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/
  Keystone v2.0 was deprecated after Open Stack Liberty. I am assuming the 
Cloudify plugin was previously tested on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration] ONAP installation via Heat - status update

[PLATANIA, MARCO (MARCO)]

ONAP Team,

This is a status update about adding MSB, VNF-SDK, Multi-VIM, UUI, and VF-C to 
the Heat template for ONAP installation.

In the Heat template, I created a new VM object that contains install scripts 
and configuration data to run the docker containers. I tested it in a private 
OpenStack lab. Some containers are up, but there is still work to do. Please 
see below.

MSB

· What is working

oThe msb_init_script.sh that Huabing provided works (the three MSB 
containers spin up)

oThe config file with IP addresses is ready (/opt/config/onap_ips.txt)

· TODO

oHuabing, please let me know how we can pass these IPs to MSB. Is it OK to 
pass them in the docker run command, e.g.

§  docker run … -e AAI_IP=$AAI_IP_ADDR –e APPC_IP=$APPC_IP_ADDR etc.

oIf so, which container should receive these values (msb_consul, 
msb_discovery, or msb_apigateway)?

VNFSDK

· What is working

oThe two containers are up

· TODO

oNothing for the moment


Multi-VIM

  *   What is working
 *   The two containers are up
  *   TODO
 *   Nothing for the moment

UUI

· What is working

oNo instruction provided yet

· TODO

oI created a skeleton of the uui_vm_init.sh script for you. Please fill it 
up with docker pull and docker run instructions. I cannot find your containers 
in Nexus3. Please help!

VF-C

  *   What is working
 *   No instruction provided yet
  *   TODO
 *   I created a skeleton of the vfc_vm_init.sh script for you. Please fill 
it up with docker run instructions. I already put instructions to pull the 
containers. Please help us complete the script.

UUI and VF-C teams, uui_vm_init.sh and vfc_vm_init.sh skeletons are in Gerrit: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=boot;h=a8ec8377dec772334915d7ad3c79c9195e983d78;hb=refs/heads/master

Tomorrow (EST time) I will set up a VM in the developer lab and give access to 
MSB, VNFSDK, Multi-VIM, UUI, and VF-C teams to check whether their containers 
are running correctly.

Thanks,
Marco

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[Gooch, Stephen]

To support Keystone v2, Ocata will also need to be removed from release 1 
support list.Is there an integration call scheduled to discuss this topic 
and the effects that may waterfall from it?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 17:31
To: Yang Xu (Yang, Fixed Network); Yunxia Chen; Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

That is the setup in our other testing labs too, both v2.0 and v3 are 
supported.  The new developer’s lab only supports v3.
We will move to v3 too.  But with R1 timeline it will be very difficult.

Thanks,
Lusheng


From: "Yang Xu (Yang, Fixed Network)" 
>
Date: Wednesday, September 20, 2017 at 5:04 PM
To: Yunxia Chen >, "Gooch, 
Stephen" >, 
"JI, LUSHENG (LUSHENG)" >
Cc: "onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

In WindRiver Mitaka, even though the identity end point is v3, we used v2 to do 
the testing. Also Mitaka provides two versions of Openstack RC file, one is 
them uses identity v2.

Thanks,
-Yang

From: Yunxia Chen
Sent: Wednesday, September 20, 2017 4:01 PM
To: Gooch, Stephen; JI, LUSHENG (LUSHENG); Yang Xu (Yang, Fixed Network)
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From: 
>
 on behalf of "Gooch, Stephen" 
>
Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/
  Keystone v2.0 was deprecated after Open Stack Liberty. I am assuming the 
Cloudify plugin was previously tested on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[JI, LUSHENG (LUSHENG)]

Stephen,

Yes. The plug-in was originally built for Kilo if I remember correctly.
Would it still be possible to add the authentication path for v2.0 on this 
instance though?   Your help would be really appreciated.

Thanks,
Lusheng


From: "Gooch, Stephen" 
Date: Wednesday, September 20, 2017 at 3:55 PM
To: "JI, LUSHENG (LUSHENG)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: RE: [Integration][OpenLabs] Keystone API version incompatible

Hello,

https://review.openstack.org/#/c/251530/
  Keystone v2.0 was deprecated after Open Stack Liberty. I am assuming the 
Cloudify plugin was previously tested on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[Yang Xu (Yang, Fixed Network)]

In WindRiver Mitaka, even though the identity end point is v3, we used v2 to do 
the testing. Also Mitaka provides two versions of Openstack RC file, one is 
them uses identity v2.

Thanks,
-Yang

From: Yunxia Chen
Sent: Wednesday, September 20, 2017 4:01 PM
To: Gooch, Stephen; JI, LUSHENG (LUSHENG); Yang Xu (Yang, Fixed Network)
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From:  on behalf of "Gooch, Stephen" 

Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/  Keystone v2.0 was deprecated after 
Open Stack Liberty. I am assuming the Cloudify plugin was previously tested 
on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #45655] [vnfsdk] Need a new job template

[Jessica Wagantall via RT]

Dear Murali, 

Can you please give this a try and let me know if it works for you please?
https://gerrit.onap.org/r/#/c/13567/3/jjb/global-templates-java.yaml

Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration]Who will be at next week's Developer F2F from Integration team?

[Yunxia Chen]

Hi, Integration team,
Sorry to broadcast in this way, but I don’t have a better way to do so. ☹ 
Please response to me directly.

I want to check whether we could have face to face Integration meeting next 
week at those unconferenced timeslot, such as Monday evening or Thursday, Paris 
local time. (zoom bridge is still available).

Regards,
Helen Chen

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[Yunxia Chen]

We got the same issue two months back when we deployed it at another lab, which 
is Mitaka.
Yang, do you remember what’s the solution or the workaround?

Regards,

Helen Chen

From:  on behalf of "Gooch, Stephen" 

Date: Wednesday, September 20, 2017 at 12:55 PM
To: "JI, LUSHENG (LUSHENG)" 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [Integration][OpenLabs] Keystone API version 
incompatible

Hello,

https://review.openstack.org/#/c/251530/  Keystone v2.0 was deprecated after 
Open Stack Liberty. I am assuming the Cloudify plugin was previously tested 
on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[Gooch, Stephen]

Hello,

https://review.openstack.org/#/c/251530/  Keystone v2.0 was deprecated after 
Open Stack Liberty. I am assuming the Cloudify plugin was previously tested 
on Kilo or Liberty?

Br,
- Stephen

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, September 20, 2017 15:16
To: Gooch, Stephen
Cc: onap-discuss@lists.onap.org
Subject: [Integration][OpenLabs] Keystone API version incompatible

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [Integration][OpenLabs] Keystone API version incompatible

[JI, LUSHENG (LUSHENG)]

Stephen,

Thanks for providing access to the lab.  We have been trying to bring up 
DACEGEN2 platform inside the WindRiver ONAP developer lab and encountered a 
problem.

The version of the Cloudify OpenStack plugin that DACEGEN2 uses is not 
compatible with the Identity API that is current provided by the tenant for 
DCAE, which is v3.  The compatible Identity API version is v2.0.  For example 
https://${hostname}:5000/v2.0.
Can the v2.0 Identity API be added?

I created a Jira ticket for tracking this:  
https://jira.onap.org/browse/OPENLABS-43

Thanks,

Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP Docker(s)?

[GUDISENA, VARUNESHWAR]

Guangrong,
In DMaap MR, port 3904 is used for http and port 3905 is used for https.



From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn]
Sent: Wednesday, September 13, 2017 7:54 PM
To: GUDISENA, VARUNESHWAR 
Cc: peng.congc...@zte.com.cn; tian.shi...@zte.com.cn; 
onap-discuss@lists.onap.org; KOYA, RAMPRASAD ; 
fu.guangr...@zte.com.cn
Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?


Sorry for the typo, the zoom ID is 66.








Original Mail
Sender: FuGuangRong10144542
To:  >;
CC: peng//cong/cong612843;tianshiwei10223543; 
>; 
>;FuGuangRong10144542;
Date: 2017/09/14 08:42
Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?



Hi Varun,



Are you still there? The call on 66888 is available now. I'm in the meeting 
room, waiting for you. :D



Guangrong












Sender: FuGuangRong10144542
To:  >;
CC: peng//cong/cong612843;tianshiwei10223543; 
>; 
>;
Date: 2017/09/14 08:24
Subject: Re: [onap-discuss]答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?



Hi Varun,



The zoom ID is 66. I'm on it right now.



Regards,

Guangrong






Sender:  >;
To: FuGuangRong10144542;
CC: peng//cong/cong612843;tianshiwei10223543; 
>; 
>;
Date: 2017/09/14 08:12
Subject: RE: 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?


I downloaded kafka file manually and used your Dockerfile. Kakfa container is 
not starting. Do you want to join for a quick call. If yes, send me zoom 
invitation.


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUDISENA, VARUNESHWAR
Sent: Wednesday, September 13, 2017 6:45 PM
To: fu.guangr...@zte.com.cn
Cc: peng.congc...@zte.com.cn; 
tian.shi...@zte.com.cn; 
onap-discuss@lists.onap.org; KOYA, 
RAMPRASAD >
Subject: Re: [onap-discuss] 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get 
Runnable DMaaP Docker(s)?

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Working on it now.


From: fu.guangr...@zte.com.cn 
[mailto:fu.guangr...@zte.com.cn]
Sent: Wednesday, September 13, 2017 5:36 PM
To: fu.guangr...@zte.com.cn
Cc: tian.shi...@zte.com.cn; 
peng.congc...@zte.com.cn; KOYA, RAMPRASAD 
>; GUDISENA, VARUNESHWAR 
>; 
onap-discuss@lists.onap.org
Subject: 答复：Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?

Greetings Varun,

Is there any progress on this?

Regards,
Guangrong

原始邮件
发件人:付光荣10144542
收件人:vg4...@att.com;
抄送人:田世伟10223543;彭聪聪612843;KOYA,  
RAMPRASAD;onap-discuss@lists.onap.org;付光荣10144542;
日期:2017-09-13 15:16:28
主题:Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP Docker(s)?


Hi Varun,



Attached is the Dockerfile we used to build the kafka docker. Please download 
kafka_2.9.2-0.8.1.1.tgz manually into the docker-compose directory and copy the 
Dockerfile into this directory as well.



I'm not sure whether it is the problem of the kafka binary package we 
downloaded from the apache website. I've tried to download it again. The same 
error occurred over and over when I try to start it. If the docker you build 
using the Dockerfile attached  works, I believe there must be something wrong 
in the MsgRtrApis.properties file. If so, I suggest you send the configuration 
file back to me in order that I could compare with that which is on my local 
machine.



Thanks in advance.

Guangrong






Sender: FuGuangRong10144542
To:  >;
CC: tianshiwei10223543;peng//cong/cong612843; 
>; 
>;
Date: 2017/09/13 08:10
Subject: Re:RE: 答复：Re:RE: Re:RE: 答复：[dmaap]Where to Get Runnable DMaaP 
Docker(s)?



Varun,



I set up a call just now. It'll start from 9:30 am, Sep. 13 (CST). The 
invitation has been sent to your mailbox, please check it for more details for 
the call.



Thanks.

Guangrong

[onap-discuss] [DMaaP] Accessing DMaaP For Release 1

[GUDISENA, VARUNESHWAR]

For Release 1, DMaaP Message Router will be supporting both anonymous topics ( 
unauthenticated ) and API keys secured topics. I recommend using anonymous 
topics for Release 1 ( exception to this case is SDC project, which is already 
using API keys secured topics). For Release 2, we will implement AAF secured 
topics.

Thanks
Varun



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration] [MultiCloud]Need help for building docker image by jenkins

[Gary Wu]

Hi Bin,

The errors are:
13:57:52 /tmp/hudson866404773651147693.sh: line 12: 
./newton/docker/build_image.sh: No such file or directory
13:57:52 /tmp/hudson866404773651147693.sh: line 13: 
./ocata/docker/build_image.sh: No such file or directory
13:57:52 /tmp/hudson866404773651147693.sh: line 14: 
./windriver/docker/build_image.sh: No such file or directory

Your JJB is defined to run those scripts via this script: 
https://git.onap.org/ci-management/tree/jjb/multicloud/build-multicloud-openstack-docker-image.sh

However, I don't see any of those scripts in source control.  So, you need to 
either check in those 3 scripts, or modify your JJB definition to not call them.

Thanks,
Gary

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Wednesday, September 20, 2017 1:21 AM
To: Yunxia Chen ; Gary Wu ; 
MORALES RUVALCABA, VICTOR 
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [integration] [MultiCloud]Need help for building docker 
image by jenkins

Hi Helen,

The jjb to build docker image for multicloud openstack plugins keep failing, 
and I don't have the expertise to debug the root cause, could you or someone 
help me to fix this issue? This is urgent since it is a blocking issue for 
integration test.

https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-docker-java-version-shell-daily/lastBuild/console

Thanks.



Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP on Kubernetes with Rancher

[Srinivasa Goda]

Hi,


I'm trying to bring up the ONAP on Kubernetes with rancher. Initially, I could 
bring it up but after sometime, i keep seeing some of the containers entering 
in 'CrashLoopBackOff' state and one container, -aai is in state 
init:0/1 for long time. I tried re-install everything from Ubuntu1604 VM to 
rancher and ONAP. I don't see any change. Any clues, pointers?


Thanks,

Regards,

Srini


[Beta Tester Badge 3]
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration] RE: SNIRO emulator implementation questions

[Geora Barsky]

Hi Gary,

The code has been put into repo, please help with setting up the Jenkins job

Thanks
Geora Barsky
Amdocs Technology
647-688-1039
647-946-5290

[amdocs-a]

Follow us on Facebook, 
Twitter, 
LinkedIn, 
YouTube, 
Google+ and the Amdocs blog 
network.


From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Tuesday, September 19, 2017 11:12 AM
To: Geora Barsky 
Cc: Yoav Kluger ; Kang Xi ; 
onap-discuss@lists.onap.org; PLATANIA, MARCO (MARCO) 
; ROSE, DANIEL V 
Subject: [integration] RE: SNIRO emulator implementation questions

Hi Geora,

Let’s put the emulator docker definition in the integration repo, as a 
subdirectory under integration/test/mocks/.  Once your files are there, 
depending on how it needs to be build (shell script, pom, etc.) I can help with 
setting up the Jenkins jobs.

Thanks,
Gary


From: Kang Xi
Sent: Tuesday, September 19, 2017 7:07 AM
To: Gary Wu >
Cc: Geora Barsky >; Yoav Kluger 
>; PLATANIA, MARCO 
(MARCO) >; ROSE, 
DANIEL V >
Subject: RE: SNIRO emulator implementation questions

Hi Gary,

Would you please help Geora? Thanks.

Regards,
Kang

From: Geora Barsky [mailto:geo...@amdocs.com]
Sent: Tuesday, September 19, 2017 10:02
To: Yoav Kluger >; 
PLATANIA, MARCO (MARCO) 
>; ROSE, DANIEL V 
>; Kang Xi 
>
Subject: RE: SNIRO emulator implementation questions

Hello Kang,

Since we are developing SNIRO emulator as a standalone microservice with its 
own docker image, we would need to perform the following activities:


1.   Add source code to GIT repository

2.   Create Jenkins job to build docker image and upload it into Nexus3

Could you please advise or contact me with the right person who can assist with 
the above and guide through the necessary steps

Thanks
Geora Barsky
Amdocs Technology
647-688-1039
647-946-5290

[amdocs-a]

Follow us on Facebook, 
Twitter, 
LinkedIn, 
YouTube, 
Google+ and the Amdocs blog 
network.

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Service registration with MSB //Re: [integration] ONAP installation via Heat

[Yunxia Chen]

Yes, we plan to deploy them into one vm to save resource unless there's issue, 
it would be easy to separate them later.
Helen


Sent from HUAWEI AnyOffice
From: zhao.huab...@zte.com.cn
To: plata...@research.att.com; Yunxia Chen;
Cc: onap-discuss;
Subject: Service registration with MSB //Re: [onap-discuss] [integration] ONAP 
installation via Heat
Time: 2017-09-20 01:43:31



Hi Marco,


As we discussed in the meeting, MSB needs to know the VM IP addresses of all 
the onap components so MSB can register the services for them.

Can we pass that information to MSB VM as environment variables?


@Helen,

According to what I heard in this meeting, VFC, Multi-VIM, MSB, UUI will be 
deployed inside one VM? If that's true, MSB will assume these components' IP 
address is the same as MSB itself when registering the services.


Thanks,

Huabing

Original Mail
Sender:  ;
To:  ; ;
Date: 2017/09/20 07:24
Subject: Re: [onap-discuss] [integration] ONAP installation via Heat

Did. :)

Regards,

Helen Chen

From:  on behalf of "PLATANIA, MARCO 
(MARCO)" 
Date: Tuesday, September 19, 2017 at 3:21 PM
To: onap-discuss 
Subject: [onap-discuss] [integration] ONAP installation via Heat

All,

To support ONAP teams whose components aren’t in Heat yet, I created a wiki 
page that explains how to add new components to the Heat template and what ONAP 
teams should do to help us during this process: 
https://wiki.onap.org/display/DW/How+to+add+a+new+ONAP+component+to+Heat

I know Helen will schedule a meeting with interested teams soon.

Thanks,
Marco


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration] [MultiCloud]Need help for building docker image by jenkins

[Yunxia Chen]

Please create a jira ticket and assign to Gary.
Helen Chen


Sent from HUAWEI AnyOffice
From: Yang, Bin
To: Yunxia Chen; Gary Wu; MORALES RUVALCABA, VICTOR;
Cc: onap-discuss;
Subject: [onap-discuss] [integration] [MultiCloud]Need help for building docker 
image by jenkins
Time: 2017-09-20 01:20:55


Hi Helen,

The jjb to build docker image for multicloud openstack plugins keep failing, 
and I don’t have the expertise to debug the root cause, could you or someone 
help me to fix this issue? This is urgent since it is a blocking issue for 
integration test.

https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-docker-java-version-shell-daily/lastBuild/console

Thanks.



Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] sdnc development environment setup issue

[Ramu n]

Hi,

Can anyone suggest which method can be fallowed to setup SDNC development 
environment, I could find below two options..


1.  
https://wiki.onap.org/display/DW/Install+Directed+Graph+Builder+on+Ubuntu+Desktop


2.  https://git.onap.org/integration/tree/bootstrap/vagrant-onap

I have tried option-2, but getting below error.. Can anyone help me what could 
be the reason.

2017-09-20 07:13:58,423 | INFO  |  | Creating blueprint container for bundle 
org.onap.ccsdk.sli.core.dblib_0.1.2.SNAPSHOT [290] with paths 
[bundleentry://290.fwk161960012/org/opendaylight/blueprint/dblib-blueprint.xml]
2017-09-20 07:13:58,423 | INFO  |  | Creating blueprint container for bundle 
org.onap.ccsdk.sli.core.dblib_0.1.2.SNAPSHOT [290] with paths 
[bundleentry://290.fwk161960012/org/opendaylight/blueprint/dblib-blueprint.xml]
2017-09-20 07:13:58,437 | INFO  |  | Using property file (1) from environment 
variable /opt/onap/sdnc/data/properties/dblib.properties
2017-09-20 07:13:58,437 | INFO  |  | Using property file (1) from environment 
variable /opt/onap/sdnc/data/properties/dblib.properties
2017-09-20 07:13:58,630 | INFO  |  | Recovery Mode disabled
2017-09-20 07:13:58,630 | INFO  |  | Recovery Mode disabled
2017-09-20 07:13:58,734 | ERROR |  | AS_CONF_ERROR: Failed to initialize 
MySQLCachedDataSource . Reason: com.mysql.jdbc.Driver
2017-09-20 07:13:58,734 | ERROR |  | AS_CONF_ERROR: Failed to initialize 
MySQLCachedDataSource . Reason: com.mysql.jdbc.Driver
2017-09-20 07:13:58,783 | ERROR |  | SQL DataSource  test failed. 
Cause : null
2017-09-20 07:13:58,783 | ERROR |  | SQL DataSource  test failed. 
Cause : null
2017-09-20 07:13:58,785 | ERROR |  |
java.lang.NullPointerException
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.getConnection(CachedDataSource.java:97)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.getData(CachedDataSource.java:108)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.CachedDataSource.isSlave(CachedDataSource.java:543)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
at 
org.onap.ccsdk.sli.core.dblib.DBResourceManager$DataSourceTester.run(DBResourceManager.java:233)[290:org.onap.ccsdk.sli.core.dblib:0.1.2.SNAPSHOT]
2017-09-20 07:13:58,785 | ERROR |  |


Thanks,
Ramu N
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] How to Install dcae-cli?

[fu.guangrong]

Lusheng,




In this case, I think the DCAE team had better proceed with handcrafting the 
TOSCA templates and blueprints using the component-spec files I sent out a 
couple days ago. We meant to do it by ourselves. . But due to the absence of 
the dcae-cli tool, we can hardly complete the task. 




Meanwhile, the CLAMP team is expecting the templates from the DCAE team and 
Policy is waiting for the Holmes configuration policy from the CLAMP team. 
Without the help of the DCAE team, none of this could be done.




What's your opinion and suggestion on this issue?




Guangrong



















Original Mail



Sender:  
To: fuguangrong10144542
CC:  peng//cong/cong612843
Date: 2017/09/20 18:39
Subject: Re: [dcae] How to Install dcae-cli?





Guangrong,
 
Those dependencies require a Pypi server to host them.  We requested LF to set 
up one on their Nexus server more than one month ago.  Last week they set up a 
proxy server, but not exactly working for this purpose (need a hosting server). 
 So at this moment  we are still blocked, and working with LF to resolve.

 
Lusheng

 

 
 Original message 
From: fu.guangr...@zte.com.cn
Date: 9/20/17 3:38 AM (GMT-05:00)
To: "JI, LUSHENG (LUSHENG)" 
Cc: onap-discuss@lists.onap.org, peng.congc...@zte.com.cn
Subject: [dcae] How to Install dcae-cli?

 

Lusheng,


 

We wanted to verify our component spec files using dcae-cli, but unfortunately 
we were trapped by some problems when building the dcae-cli tool.


 

We tried two ways to install dcae-cli:


 

1. Using "python setup.py build" and then "python setup.py install" under the 
directory dcaegen2/platform/cli/dcae-cli. An error occured:

Installed /usr/local/lib/python2.7/dist-packages/dcae_cli-2.9.0-py2.7.egg

Processing dependencies for dcae-cli==2.9.0

Searching for python-dockering<2.0.0,>=1.0.0

Reading https://pypi.python.org/simple/python-dockering/

Couldn't find index page for 'python-dockering' (maybe misspelled?)

Scanning index of all packages (this may take a while)

Reading https://pypi.python.org/simple/

No local packages or download links found for python-dockering<2.0.0,>=1.0.0

error: Could not find suitable distribution for 
Requirement.parse('python-dockering<2.0.0,>=1.0.0')


 

I browsed https://pypi.python.org/simple/ and  found nothing regarding 
python-dockering.


 

2. Using "pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple dcae-cli" which is written in 
the DCAE document to install dcae-cli directly. Another error occured:




[root@localhost dcae-cli]# pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple dcae-cli

Requirement already satisfied: dcae-cli in 
/usr/lib/python2.7/site-packages/dcae_cli-2.9.0-py2.7.egg

Collecting python-consul (from dcae-cli)

  Using cached python_consul-0.7.2-py2.py3-none-any.whl

Requirement already satisfied: six in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting sqlalchemy (from dcae-cli)

  Using cached SQLAlchemy-1.1.14.tar.gz

Collecting SQLAlchemy-Utils (from dcae-cli)

  Using cached SQLAlchemy-Utils-0.32.16.tar.gz

Requirement already satisfied: click in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting jsonschema (from dcae-cli)

  Using cached jsonschema-2.6.0-py2.py3-none-any.whl

Collecting docker-py<2,>=1.10 (from dcae-cli)

  Using cached docker_py-1.10.6-py2.py3-none-any.whl

Collecting terminaltables (from dcae-cli)

  Using cached terminaltables-3.1.0.tar.gz

Collecting psycopg2 (from dcae-cli)

  Using cached psycopg2-2.7.3.1-cp27-cp27mu-manylinux1_x86_64.whl

Collecting genson (from dcae-cli)

  Using cached genson-0.2.2.tar.gz

Collecting python-discovery-client>=2.0.0 (from dcae-cli)

  Could not find a version that satisfies the requirement 
python-discovery-client>=2.0.0 (from dcae-cli) (from versions: )

No matching distribution found for python-discovery-client>=2.0.0 (from 
dcae-cli)


 

Do you have any idea on how to fix the errors above? Is there any other 
approach to install the dcae-cli?
 


 


 

Guangrong___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] How to Install dcae-cli?

[JI, LUSHENG (LUSHENG)]

Guangrong,

Those dependencies require a Pypi server to host them.  We requested LF to set 
up one on their Nexus server more than one month ago.  Last week they set up a 
proxy server, but not exactly working for this purpose (need a hosting server). 
 So at this moment we are still blocked, and working with LF to resolve.

Lusheng


 Original message 
From: fu.guangr...@zte.com.cn
Date: 9/20/17 3:38 AM (GMT-05:00)
To: "JI, LUSHENG (LUSHENG)" 
Cc: onap-discuss@lists.onap.org, peng.congc...@zte.com.cn
Subject: [dcae] How to Install dcae-cli?


Lusheng,


We wanted to verify our component spec files using dcae-cli, but unfortunately 
we were trapped by some problems when building the dcae-cli tool.


We tried two ways to install dcae-cli:


1. Using "python setup.py build" and then "python setup.py install" under the 
directory dcaegen2/platform/cli/dcae-cli. An error occured:

Installed /usr/local/lib/python2.7/dist-packages/dcae_cli-2.9.0-py2.7.egg

Processing dependencies for dcae-cli==2.9.0

Searching for python-dockering<2.0.0,>=1.0.0

Reading 
https://pypi.python.org/simple/python-dockering/

Couldn't find index page for 'python-dockering' (maybe misspelled?)

Scanning index of all packages (this may take a while)

Reading 
https://pypi.python.org/simple/

No local packages or download links found for python-dockering<2.0.0,>=1.0.0

error: Could not find suitable distribution for 
Requirement.parse('python-dockering<2.0.0,>=1.0.0')


I browsed 
https://pypi.python.org/simple/
 and found nothing regarding python-dockering.


2. Using "pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple
 dcae-cli" which is written in the DCAE document to install dcae-cli directly. 
Another error occured:

[root@localhost dcae-cli]# pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple
 dcae-cli

Requirement already satisfied: dcae-cli in 
/usr/lib/python2.7/site-packages/dcae_cli-2.9.0-py2.7.egg

Collecting python-consul (from dcae-cli)

  Using cached python_consul-0.7.2-py2.py3-none-any.whl

Requirement already satisfied: six in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting sqlalchemy (from dcae-cli)

  Using cached SQLAlchemy-1.1.14.tar.gz

Collecting SQLAlchemy-Utils (from dcae-cli)

  Using cached SQLAlchemy-Utils-0.32.16.tar.gz

Requirement already satisfied: click in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting jsonschema (from dcae-cli)

  Using cached jsonschema-2.6.0-py2.py3-none-any.whl

Collecting docker-py<2,>=1.10 (from dcae-cli)

  Using cached docker_py-1.10.6-py2.py3-none-any.whl

Collecting terminaltables (from dcae-cli)

  Using cached terminaltables-3.1.0.tar.gz

Collecting psycopg2 (from dcae-cli)

  Using cached psycopg2-2.7.3.1-cp27-cp27mu-manylinux1_x86_64.whl

Collecting genson (from dcae-cli)

  Using cached genson-0.2.2.tar.gz

Collecting python-discovery-client>=2.0.0 (from dcae-cli)

  Could not find a version that satisfies the requirement 
python-discovery-client>=2.0.0 (from dcae-cli) (from versions: )

No matching distribution found for python-discovery-client>=2.0.0 (from 
dcae-cli)


Do you have any idea on how to fix the errors above? Is there any other 
approach to install the dcae-cli?



Guangrong






___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] R2 preparations: functional and non-functional requirements candidates

[Alla Goldner]

Hi all,

Here is the status of functional and non-functional requirements candidates for 
Beijing Release:


1.   Table with merged functional requirements candidates: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates

2.   Non-functional requirements candidates 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements





And…Chag Sameach and Shana Tova to all our Jewish colleagues!



[#ShanaTova from #Jewish Treats! #RoshHashana #Judaism]

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33168.22665D10]

From: Alla Goldner
Sent: Tuesday, September 19, 2017 5:21 PM
To: 'onap-usecase...@lists.onap.org' 
Cc: 'Kenny Paul' ; 'GILBERT, MAZIN E (MAZIN E)' 
; Yoav Kluger ; Andrei Kojukhov 
; 'onap-...@lists.onap.org' 

Subject: RE: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Please see table with merged requirements here: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates


1.   I marked all pages previously used for gathering of R2 functional 
requirements as OBSOLETE, as we want to have a single source now and update it 
accordingly
Note: Non-functional requirement proposals for R2 remain untouched 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements


2.   We (Alla, Yoav, Andrei) gathered all requirements into a single table 
with the information previously provided by the requirements authors, while 
adding on top of it:

a.   Agreed priority for R2 - this is something to be agreed by the whole 
group (empty for now)

b.  Proposed grouping/harmonization - this is our initial proposal of how 
those requirements may be grouped and this may be used for further requirements 
harmonization

c.   Proposed ownership - would be beneficial if each group/requirement 
gets under responsibility of a project (if it is a single project related) or 
person (i.e. proceeding with that group in the same way as was done with the 
specific use cases in R1) (empty for now)

The AI are:


1.   Requirements authors - please double check all initial information is 
present

2.   Requirements authors - please introduce summary/link to some detail 
requirement description in case it is missing. This is needed

3.   All - please review and provide your comments and suggestions for 
modifications/next step of our discussions, concentrating mostly on 
requirements harmonization/importance/relevancy for R2 goal of making ONAP 
Platform more stable

4.   Luman - please extend this table with E-vCPE additional requirements 
as discussed yesterday


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33168.22665D10]

From: Alla Goldner
Sent: Monday, September 18, 2017 10:22 PM
To: 'onap-usecase...@lists.onap.org' 
>
Cc: 'Kenny Paul' >; 
'GILBERT, MAZIN E (MAZIN E)' 
>
Subject: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Thanks to all meeting’s attendants!
Here is the summary:


1.   All R2 use cases were updated with the list of their corresponding 
functional requirements - thanks a lot to the authors!!! Some of the 
requirements still need more explanation to be added though

2.   Alla will merge all functional requirements into a single table by 
19/09/2017, then we will work with it for:

a.   Removal of the same requirement appearing multiple times/extension of 
one requirement by functional modifications coming from another one

b.  Making a requirements generic

   i.  We must 
target generic platform requirements (e.g. E-vCPE service onboarding, SDWAN 
service onboarding requirements transform to some generic onboarding functional 
requirement which is not supported by R1)

c.   Prioritization proposal of a different requirements for R2

3.   Then, Luman will also add additional E-vCPE requirements discussed 
during the call to this table

4.   Alla will check whether zoom connection is possible during next week 
meeting

5.   Alex will check with Chris whether R2 architecture requirements will 
be included to guide us while prioritizing those functional requirements 
https://wiki.onap.org/display/DW/Architecture+Requirements+for+R2+use+cases

6.   One of the action items to discuss during the next week joint meeting 
with the Architecture subcommittee is NAI/PCE coming from E-vCPE use case (in 
case Luman will be able to connect by zoom)

7.   Non-functional requirements will be discussed jointly by the whole 

[onap-discuss] [integration] [MultiCloud]Need help for building docker image by jenkins

[Yang, Bin]

Hi Helen,

The jjb to build docker image for multicloud openstack plugins keep failing, 
and I don't have the expertise to debug the root cause, could you or someone 
help me to fix this issue? This is urgent since it is a blocking issue for 
integration test.

https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-docker-java-version-shell-daily/lastBuild/console

Thanks.



Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: [SO]SO Maven Build Issue

[Chenchuanyu]

Hi Abhishek,

   Thank you very much, It can be built successful now.

Thanks.
Chuanyu Chen.

发件人: Abhishek Shekhar [mailto:abhishek.shekh...@amdocs.com]
发送时间: 2017年9月20日 15:13
收件人: Chenchuanyu; Elhay Efrat; onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Hi Chuanyu

The artifact is present in autorelease-15451 repository
https://nexus.onap.org/service/local/repositories/autorelease-15451/content/org/openecomp/appc/client/client-kit/1.1.0/client-kit-1.1.0.jar

I think the repository I mentioned below (autorelease-14157) no longer exists, 
it now resides in autorelease-15451.

Please note this artifact is also available in staging repository 
(https://nexus.onap.org/content/repositories/staging/org/openecomp/appc/client/client-kit/1.1.0/
 ) but I have not used this repository in local build.

Thanks
Abhishek Shekhar

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Wednesday, September 20, 2017 12:10 PM
To: Abhishek Shekhar 
>; Elhay 
Efrat >; 
onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue

Hi, Abhishek,
Thanks for your suggestion , I update the settings but it always build failed.
Can you show me where client-kit-1.1.0.pom located?
I think it should be locate at 
https://nexus.onap.org/content/repositories/snapshots/org/openecomp/appc/client/client-kit/1.1.0-SNAPSHOT/
But there is no client-kit-1.1.0.pom there.

Thanks,
Chuanyu Chen.

发件人: Abhishek Shekhar [mailto:abhishek.shekh...@amdocs.com]
发送时间: 2017年9月19日 17:28
收件人: Elhay Efrat; Chenchuanyu; 
onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Hi,

I’ve faced this issue.

Please add ONAP and ODL repositories in your maven settings.




onap-repo
ONAP 
Repository

https://nexus.onap.org/service/local/repositories/autorelease-14157/contenthttps://nexus.onap.org/service/local/repositories/autorelease-14157/content%3c/url>>

default

always



opendayligh-repo

Opendaylight Repository

https://nexus.onap.org/service/local/repositories/opendaylight/contenthttps://nexus.onap.org/service/local/repositories/opendaylight/content%3c/url>>

default

always



If you are behind firewall, please check maven has access to these repositories.

Hope it helps.

Thanks
Abhishek Shekhar

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Tuesday, September 19, 2017 2:01 PM
To: Chenchuanyu >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [SO]SO Maven Build Issue

Please clean .m2 and add to mvn command -U

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Tuesday, September 19, 2017 9:30 AM
To: Elhay Efrat >; 
onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue

The  command I use is ‘mvn install �CDmaven.test.skip=true’. And I have the 
full internet access, it is windows env.

It looks like there is some problem with the below dependency configuration.

client-kit-1.1.0.pom cannot be found at  nexus repo. But I’m not sure why it 
build success in jenkins.
[cid:image001.png@01D33228.BCF06C70]
发件人: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
发送时间: 2017年9月19日 12:00
收件人: Chenchuanyu; 
onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Yes , please send me the mvn command that you are doing ... And second you have 
full internet access ? Is it Linux or windows ?


From: Chenchuanyu
Sent: Tuesday, September 19, 2017 2:20:49 AM
To: Elhay Efrat; onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue
Hi  Elhay,
  Thanks for your reply, I think the jar exists in nexus, the project build 
successful in Jenkins. But failed in my local env. Is there 

[onap-discuss] [dcae] How to Install dcae-cli?

[fu.guangrong]

Lusheng,




We wanted to verify our component spec files using dcae-cli, but unfortunately 
we were trapped by some problems when building the dcae-cli tool.




We tried two ways to install dcae-cli:




1. Using "python setup.py build" and then "python setup.py install" under the 
directory dcaegen2/platform/cli/dcae-cli. An error occured:

Installed /usr/local/lib/python2.7/dist-packages/dcae_cli-2.9.0-py2.7.egg

Processing dependencies for dcae-cli==2.9.0

Searching for python-dockering<2.0.0,>=1.0.0

Reading https://pypi.python.org/simple/python-dockering/

Couldn't find index page for 'python-dockering' (maybe misspelled?)

Scanning index of all packages (this may take a while)

Reading https://pypi.python.org/simple/

No local packages or download links found for python-dockering<2.0.0,>=1.0.0

error: Could not find suitable distribution for 
Requirement.parse('python-dockering<2.0.0,>=1.0.0')




I browsed https://pypi.python.org/simple/ and found nothing regarding 
python-dockering.




2. Using "pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple dcae-cli" which is written in 
the DCAE document to install dcae-cli directly. Another error occured:



[root@localhost dcae-cli]# pip install --extra-index-url 
https://nexus3.onap.org/repository/PyPi/simple dcae-cli

Requirement already satisfied: dcae-cli in 
/usr/lib/python2.7/site-packages/dcae_cli-2.9.0-py2.7.egg

Collecting python-consul (from dcae-cli)

  Using cached python_consul-0.7.2-py2.py3-none-any.whl

Requirement already satisfied: six in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting sqlalchemy (from dcae-cli)

  Using cached SQLAlchemy-1.1.14.tar.gz

Collecting SQLAlchemy-Utils (from dcae-cli)

  Using cached SQLAlchemy-Utils-0.32.16.tar.gz

Requirement already satisfied: click in /usr/lib/python2.7/site-packages (from 
dcae-cli)

Collecting jsonschema (from dcae-cli)

  Using cached jsonschema-2.6.0-py2.py3-none-any.whl

Collecting docker-py<2,>=1.10 (from dcae-cli)

  Using cached docker_py-1.10.6-py2.py3-none-any.whl

Collecting terminaltables (from dcae-cli)

  Using cached terminaltables-3.1.0.tar.gz

Collecting psycopg2 (from dcae-cli)

  Using cached psycopg2-2.7.3.1-cp27-cp27mu-manylinux1_x86_64.whl

Collecting genson (from dcae-cli)

  Using cached genson-0.2.2.tar.gz

Collecting python-discovery-client>=2.0.0 (from dcae-cli)

  Could not find a version that satisfies the requirement 
python-discovery-client>=2.0.0 (from dcae-cli) (from versions: )

No matching distribution found for python-discovery-client>=2.0.0 (from 
dcae-cli)




Do you have any idea on how to fix the errors above? Is there any other 
approach to install the dcae-cli?








Guangrong___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Sonsino, Ofir]

As for VID Parent Project, it was already changed to just “vid” and now for 
somehow it’s back to “parent project” again.
The pom.xml is updated. Any of you knows how to trigger SONAR to update 
accordingly?

Thanks,
Ofir

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Wednesday, September 20, 2017 1:53 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention


Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging 
Library.
 Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/
 Not sure why this is still in Sonar. The Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. 
Distribution

3. DMaaP Bus Controller UI 
(parent)

4. Ecomp Portal SDK Project 
(parent)

5. ECOMP Portal SDK Project 
(parent)

6. 
modeling/toscaparsers/nfvparser

7. 
inventory-api
 should be under dcaegen2/platform

8. MSO main 
project
 should be removed

9. OpenStack Java 
SDK

10. Parent 
POMs

11. SDN-C 
Adaptors

12. SDN-C Core 

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Sonsino, Ofir via RT]

As for VID Parent Project, it was already changed to just “vid” and now for 
somehow it’s back to “parent project” again.
The pom.xml is updated. Any of you knows how to trigger SONAR to update 
accordingly?

Thanks,
Ofir

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Wednesday, September 20, 2017 1:53 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention


Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging 
Library.
 Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/
 Not sure why this is still in Sonar. The Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. 
Distribution

3. DMaaP Bus Controller UI 
(parent)

4. Ecomp Portal SDK Project 
(parent)

5. ECOMP Portal SDK Project 
(parent)

6. 
modeling/toscaparsers/nfvparser

7. 
inventory-api
 should be under dcaegen2/platform

8. MSO main 
project
 should be removed

9. OpenStack Java 
SDK

10. Parent 
POMs

11. SDN-C 
Adaptors

12. SDN-C Core 

Re: [onap-discuss] [SO]SO Maven Build Issue

[Abhishek Shekhar]

Hi Chuanyu

The artifact is present in autorelease-15451 repository
https://nexus.onap.org/service/local/repositories/autorelease-15451/content/org/openecomp/appc/client/client-kit/1.1.0/client-kit-1.1.0.jar

I think the repository I mentioned below (autorelease-14157) no longer exists, 
it now resides in autorelease-15451.

Please note this artifact is also available in staging repository 
(https://nexus.onap.org/content/repositories/staging/org/openecomp/appc/client/client-kit/1.1.0/
 ) but I have not used this repository in local build.

Thanks
Abhishek Shekhar

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Wednesday, September 20, 2017 12:10 PM
To: Abhishek Shekhar ; Elhay Efrat 
; onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue

Hi, Abhishek,
Thanks for your suggestion , I update the settings but it always build failed.
Can you show me where client-kit-1.1.0.pom located?
I think it should be locate at 
https://nexus.onap.org/content/repositories/snapshots/org/openecomp/appc/client/client-kit/1.1.0-SNAPSHOT/
But there is no client-kit-1.1.0.pom there.

Thanks,
Chuanyu Chen.

发件人: Abhishek Shekhar [mailto:abhishek.shekh...@amdocs.com]
发送时间: 2017年9月19日 17:28
收件人: Elhay Efrat; Chenchuanyu; 
onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Hi,

I’ve faced this issue.

Please add ONAP and ODL repositories in your maven settings.




onap-repo
ONAP 
Repository

https://nexus.onap.org/service/local/repositories/autorelease-14157/contenthttps://nexus.onap.org/service/local/repositories/autorelease-14157/content%3c/url>>

default

always



opendayligh-repo

Opendaylight Repository

https://nexus.onap.org/service/local/repositories/opendaylight/contenthttps://nexus.onap.org/service/local/repositories/opendaylight/content%3c/url>>

default

always



If you are behind firewall, please check maven has access to these repositories.

Hope it helps.

Thanks
Abhishek Shekhar

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Tuesday, September 19, 2017 2:01 PM
To: Chenchuanyu >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [SO]SO Maven Build Issue

Please clean .m2 and add to mvn command -U

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Tuesday, September 19, 2017 9:30 AM
To: Elhay Efrat >; 
onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue

The  command I use is ‘mvn install �CDmaven.test.skip=true’. And I have the 
full internet access, it is windows env.

It looks like there is some problem with the below dependency configuration.

client-kit-1.1.0.pom cannot be found at  nexus repo. But I’m not sure why it 
build success in jenkins.
[cid:image001.png@01D3320A.4187B1B0]
发件人: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
发送时间: 2017年9月19日 12:00
收件人: Chenchuanyu; 
onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Yes , please send me the mvn command that you are doing ... And second you have 
full internet access ? Is it Linux or windows ?


From: Chenchuanyu
Sent: Tuesday, September 19, 2017 2:20:49 AM
To: Elhay Efrat; onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue
Hi  Elhay,
  Thanks for your reply, I think the jar exists in nexus, the project build 
successful in Jenkins. But failed in my local env. Is there any other 
suggestion for this?
Jenkins build log:
[INFO] MSOMockServer .. SUCCESS [  1.790 s]
[INFO] MSO REST Client API  SUCCESS [  0.211 s]
[INFO] MSOCommonBPMN .. SUCCESS [01:36 min]
[INFO] MSOInfrastructureBPMN .. SUCCESS [03:50 min]

[onap-discuss] 答复: [SO]SO Maven Build Issue

[Chenchuanyu]

Hi, Abhishek,
Thanks for your suggestion , I update the settings but it always build failed.
Can you show me where client-kit-1.1.0.pom located?
I think it should be locate at 
https://nexus.onap.org/content/repositories/snapshots/org/openecomp/appc/client/client-kit/1.1.0-SNAPSHOT/
But there is no client-kit-1.1.0.pom there.

Thanks,
Chuanyu Chen.

发件人: Abhishek Shekhar [mailto:abhishek.shekh...@amdocs.com]
发送时间: 2017年9月19日 17:28
收件人: Elhay Efrat; Chenchuanyu; onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Hi,

I’ve faced this issue.

Please add ONAP and ODL repositories in your maven settings.




onap-repo
ONAP 
Repository

https://nexus.onap.org/service/local/repositories/autorelease-14157/contenthttps://nexus.onap.org/service/local/repositories/autorelease-14157/content%3c/url>>

default

always



opendayligh-repo

Opendaylight Repository

https://nexus.onap.org/service/local/repositories/opendaylight/contenthttps://nexus.onap.org/service/local/repositories/opendaylight/content%3c/url>>

default

always



If you are behind firewall, please check maven has access to these repositories.

Hope it helps.

Thanks
Abhishek Shekhar

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Tuesday, September 19, 2017 2:01 PM
To: Chenchuanyu >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [SO]SO Maven Build Issue

Please clean .m2 and add to mvn command -U

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Tuesday, September 19, 2017 9:30 AM
To: Elhay Efrat >; 
onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue

The  command I use is ‘mvn install �CDmaven.test.skip=true’. And I have the 
full internet access, it is windows env.

It looks like there is some problem with the below dependency configuration.

client-kit-1.1.0.pom cannot be found at  nexus repo. But I’m not sure why it 
build success in jenkins.
[cid:image001.png@01D3321E.5E894B20]
发件人: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
发送时间: 2017年9月19日 12:00
收件人: Chenchuanyu; 
onap-discuss@lists.onap.org
主题: RE: [SO]SO Maven Build Issue

Yes , please send me the mvn command that you are doing ... And second you have 
full internet access ? Is it Linux or windows ?


From: Chenchuanyu
Sent: Tuesday, September 19, 2017 2:20:49 AM
To: Elhay Efrat; onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue
Hi  Elhay,
  Thanks for your reply, I think the jar exists in nexus, the project build 
successful in Jenkins. But failed in my local env. Is there any other 
suggestion for this?
Jenkins build log:
[INFO] MSOMockServer .. SUCCESS [  1.790 s]
[INFO] MSO REST Client API  SUCCESS [  0.211 s]
[INFO] MSOCommonBPMN .. SUCCESS [01:36 min]
[INFO] MSOInfrastructureBPMN .. SUCCESS [03:50 min]
[INFO] MSO URN Mapping Cockpit Plugin . SUCCESS [  0.284 s]
[INFO] MSOCockpit . SUCCESS [ 10.610 s]
[INFO] MSO Packages ... SUCCESS [  0.004 s]
[INFO] MsoDeliveries .. SUCCESS [ 14.837 s]
[INFO] MSO Docker Deliveries .. SUCCESS [21:44 min]
[INFO] Arquillian Unit Testing on MSO . SUCCESS [01:47 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 32:01 min
[INFO] Finished at: 2017-09-18T03:47:44+00:00
[INFO] Final Memory: 191M/798M
[INFO] 
$ ssh-agent -k
unset